FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR MAPPING A TARGET PERSON IDENTITY TO A USER IDENTITY”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR MAPPING A TARGET PERSON IDENTITY TO A
USER IDENTITY
TECHNICAL FIELD
5
[0001] Embodiments of the present disclosure generally relate to network performance
management systems. More particularly, embodiments of the present disclosure relate to mapping a target person identity to a user identity.
10 BACKGROUND
[0002] The following description of the related art is intended to provide background
information pertaining to the field of the disclosure. This section may include certain aspects
of the art that may be related to various features of the present disclosure. However, it should
15 be appreciated that this section is used only to enhance the understanding of the reader with
respect to the present disclosure, and not as admissions of the prior art.
[0003] In the currently known, identity verification and legal relationship identification
systems, issue of identifying legal heirs and determining their identity is plagued by a lack
20 of standardized methods. Moreover, in land related cases, fraudulent claims to inherit land
and other valuable assets have been on the rise. The huge number of fraudulent claims pose significant challenges for the judicial system in differentiating between genuine and fraudulent claimants. The absence of a reliable and consistent mechanism for establishing the true identity of heirs has exacerbated the problem, leading to prolonged legal disputes
25 and impeding the fair distribution of assets among rightful beneficiaries. Thus, there is an
urgent need for a technical solution that can effectively and accurately map a target person's identity to a user identity, providing a robust framework for identifying legitimate heirs and curbing fraudulent claims.
30 [0004] Further, over the period of time various solutions have been developed to map
a target person identity to a user identity. However, there are certain challenges with existing solutions. The prior solutions available to address the critical issue of identifying legal heirs and determining their identity suffer from a notable technical limitation due to lack of standardized methods and a reliable mechanism for establishing the true identity of heirs.
2

This limitation becomes particularly apparent in the context of India, where the prevalence
of fraudulent claims to inherit valuable assets has created substantial hurdles for the judicial
system. Without a consistent and trustworthy framework in place, it becomes increasingly
challenging to discern between genuine claimants and those attempting to deceive the
5 system. As a result, prolonged legal disputes ensue, impeding the fair distribution of assets
among rightful beneficiaries
[0005] Thus, there exists an imperative need in the art to map a target person identity
to a user identity, which the present disclosure aims to address. 10
SUMMARY
[0006] This section is provided to introduce certain aspects of the present disclosure in
a simplified form that are further described below in the detailed description. This summary
15 is not intended to identify the key features or the scope of the claimed subject matter.
[0007] An aspect of the present disclosure may relate to a method for mapping a target
person identity to a user identity. The method includes receiving, by a transceiver unit at a server, an identity update request associated with a target person, wherein the identity update
20 request is associated with at least one or more identification parameters associated with the
target person. The method further includes initiating, by an authentication unit at the server, a first authentication check request based on the identity update request. Furthermore, the method includes detecting, by a detection unit at the server, a successful first authentication response based on the first authentication check request. Furthermore, the method
25 encompasses initiating, by the authentication unit at the server, a second authentication
check request based on the successful first authentication response. The method further encompasses detecting, by the detection unit at the server, a successful second authentication response based on the second authentication check request. Further, the method includes mapping, by the mapping unit at the server, the target person identity and
30 the user identity based on at least the successful second authentication response.
[0008] In an exemplary aspect of the present disclosure, the one or more identification
parameters associated with the target person is at least one of a target person name, a target person address, and a target person relationship with the user.
3

[0009] In an exemplary aspect of the present disclosure, the successful first
authentication response based on the first authentication check request is detected by the
detection unit based on a first one-time password (OTP) received from the target person
5 associated with the first authentication check request.
[0010] In an exemplary aspect of the present disclosure, the detection of the successful
first authentication response based on the OTP, by the detection unit, validates the one or
more identity parameters associated with the target person.
10
[0011] In an exemplary aspect of the present disclosure, the second authentication
check request is associated with at least the target person relationship identity update request
between the target person and the user, and wherein the successful second authentication
response is detected by the detection unit based on at least retrieving by the transceiver unit,
15 a valid legal relationship document, from the database, associated with the target person and
the user, and on a second OTP received from the user.
[0012] In an exemplary aspect of the present disclosure, the detection of the successful
second authentication response based on the retrieving of at least the valid legal relationship
20 document and the second OTP, by the transceiver unit, validates acknowledgement from the
user for the target person relationship identity update request.
[0013] In an exemplary aspect of the present disclosure, the method further comprises
updating an identification document associated with the target user and an identification
25 document associated with the user at the database.
[0014] Another aspect of the present disclosure may relate to a system for mapping a
target person identity to a user identity. The system includes a server. The server further includes a transceiver unit configured to receive, an identity update request associated with
30 a target person, wherein the identity update request is associated with at least one or more
identification parameters associated with the target person. The server further includes an authentication unit connected to at least the transceiver unit. The authentication unit is configured to initiate, a first authentication check request based on the identity update request. Furthermore, the server includes a detection unit connected to at least the
35 authentication unit. The detection unit is configured to detect, a successful first
4

authentication response based on the first authentication check request. Furthermore, the
server includes the authentication unit, configured to initiate, a second authentication check
request based on the successful first authentication response. The server further includes the
detection unit further configured to detect, a successful second authentication response
5 based on the second authentication check request. The server further includes a mapping
unit connected to at least the authentication unit. The mapping unit is configured to map, the target person identity and the user identity based on at least the successful second authentication response.
10 [0015] Yet another aspect of the present disclosure may relate to a non-transitory
computer readable storage medium storing instructions for mapping a target person identity to a user identity, the instructions include executable code which, when executed by one or more units of a system, cause a transceiver unit of the system to receive an identity update request associated with a target person, wherein the identity update request is associated
15 with at least one or more identification parameters associated with the target person. The
instructions when executed by the system further cause an authentication unit of the system to initiate a first authentication check request based on the identity update request. The instructions when executed by the system further cause a detection unit of the system to detect, a successful first authentication response based on the first authentication check
20 request. The instructions when executed by the system further cause the authentication unit
of the system to initiate, a second authentication check request based on the successful first authentication response. The instructions when executed by the system further cause the detection unit of the system to detect, a successful second authentication response based on the second authentication check request. The instructions when executed by the system
25 further cause a mapping unit of the system to map, the target person identity and the user
identity based on at least the successful second authentication response.
[0016] Yet another aspect of the present disclosure may relate to a user equipment (UE)
for mapping a target person identity to a user identity. The user equipment (UE) includes a
30 transceiver unit configured to send, to a server, an identity update request associated with a
target person, wherein the identity update request is associated with at least one or more identification parameters associated with the target person. The transceiver unit is further configured to send, to the server, a first one-time password (OTP) associated with the target person to validate the identity update request associated with the target person, wherein the
5

validating the identity update request associated with the target person comprises validating
the one or more identification parameters associated with the target person. Furthermore,
the transceiver unit is configured to send, to the server, the target person relationship identity
update request between the target person and the user, based on the validity of the identity
5 check request associated with the target person. The transceiver unit is further configured to
send, to the server, a second OTP associated with the user, wherein the second OTP validates
the target person relationship identity update request. The transceiver unit is further
configured to receive, from the server, a mapping notification, based on the validated target
person relationship identity update request, wherein the mapping notification is associated
10 with a mapping of the target person identity to the user identity.
OBJECTS OF THE INVENTION
[0017] Some of the objects of the present disclosure, which at least one embodiment
15 disclosed herein satisfies are listed herein below.
[0018] It is an object of the present disclosure to provide a system and a method for
mapping a target person identity to a user identity.
20 [0019] It is another object of the present disclosure to provide a solution that initiates a
first authentication check request associated with a target person identity document based on the update request associated with the target person.
[0020] It is another object of the present disclosure to provide a solution that initiates a
25 second authentication check request associated with the target person relationship document
based on the successful first authentication response.
[0021] It is yet another object of the present disclosure to provide a solution to map the
target person with the user based on at least one of the successful first authentication
30 response and the successful second authentication response.
DESCRIPTION OF THE DRAWINGS
6

[0022] The accompanying drawings, which are incorporated herein, and constitute a
part of this disclosure, illustrate exemplary embodiments of the disclosed methods and
systems in which like reference numerals refer to the same parts throughout the different
drawings. Components in the drawings are not necessarily to scale, emphasis instead being
5 placed upon clearly illustrating the principles of the present disclosure. Also, the
embodiments shown in the figures are not to be construed as limiting the disclosure, but the
possible variants of the method and system according to the disclosure are illustrated herein
to highlight the advantages of the disclosure. It will be appreciated by those skilled in the
art that disclosure of such drawings includes disclosure of electrical components or circuitry
10 commonly used to implement such components.
[0023] FIG. 1 illustrates a functional block diagram of a system for mapping a target
person identity to a user identity, in accordance with exemplary implementations of the present disclosure. 15
[0024] FIG. 2 illustrates an exemplary block diagram of a computing device upon
which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
20 [0025] FIG. 3 illustrates a method flow diagram for mapping a target person identity to
a user identity, in accordance with exemplary implementations of the present disclosure.
[0026] FIG. 4 illustrates an exemplary block diagram of a system for mapping a target
person identity to a user identity, in accordance with exemplary implementations of the
25 present disclosure.
[0027] FIG. 5 illustrates an exemplary implementation of the process flow for mapping
a target person identity to a user identity, in accordance with exemplary implementations of
the present disclosure.
30
[0028] FIG. 6 illustrates an exemplary use case of the present disclosure, in accordance
with exemplary implementations of the present disclosure.
7

[0029] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
DETAILED DESCRIPTION
5
[0030] In the following description, for the purposes of explanation, various specific
details are set forth in order to provide a thorough understanding of embodiments of the
present disclosure. It will be apparent, however, that embodiments of the present disclosure
may be practiced without these specific details. Several features described hereafter may
10 each be used independently of one another or with any combination of other features. An
individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.
[0031] The ensuing description provides exemplary embodiments only, and is not
15 intended to limit the scope, applicability, or configuration of the disclosure. Rather, the
ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth. 20
[0032] Specific details are given in the following description to provide a thorough
understanding of the embodiments. However, it will be understood by one of ordinary skill
in the art that the embodiments may be practiced without these specific details. For example,
circuits, systems, processes, and other components may be shown as components in block
25 diagram form in order not to obscure the embodiments in unnecessary detail.
[0033] Also, it is noted that individual embodiments may be described as a process
which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram,
or a block diagram. Although a flowchart may describe the operations as a sequential
30 process, many of the operations may be performed in parallel or concurrently. In addition,
the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.
8

[0034] The word “exemplary” and/or “demonstrative” is used herein to mean serving
as an example, instance, or illustration. For the avoidance of doubt, the subject matter
disclosed herein is not limited by such examples. In addition, any aspect or design described
herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred
5 or advantageous over other aspects or designs, nor is it meant to preclude equivalent
exemplary structures and techniques known to those of ordinary skill in the art. Furthermore,
to the extent that the terms “includes,” “has,” “contains,” and other similar words are used
in either the detailed description or the claims, such terms are intended to be inclusive—in
a manner similar to the term “comprising” as an open transition word—without precluding
10 any additional or other elements.
[0035] As used herein, a “processing unit” or “processor” or “operating processor”
includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose
15 processor, a conventional processor, a digital signal processor, a plurality of
microprocessors, one or more microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or
20 any other functionality that enables the working of the system according to the present
disclosure. More specifically, the processor or processing unit is a hardware processor.
[0036] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a
smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless
25 communication device”, “a mobile communication device”, “a communication device” may
be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other
30 computing device which is capable of implementing the features of the present disclosure.
Also, the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
9

[0037] As used herein, “storage unit” or “memory unit” refers to a machine or
computer-readable medium including any mechanism for storing information in a form
readable by a computer or similar machine. For example, a computer-readable medium
includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk
5 storage media, optical storage media, flash memory devices or other types of machine-
accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
[0038] As used herein “interface” or “user interface refers to a shared boundary across
10 which two or more separate components of a system exchange information or data. The
interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
15 [0039] All modules, units, components used herein, unless explicitly excluded herein,
may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC),
20 Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
[0040] As used herein the transceiver unit include at least one receiver and at least one
transmitter configured respectively for receiving and transmitting data, signals, information
or a combination thereof between units/components within the system and/or connected
25 with the system.
[0041] As discussed in the background section, the current known solutions have
several shortcomings. The present disclosure aims to overcome the shortcomings mentioned
in the background section and other existing problems in this field of technology by
30 providing a method and a system of mapping a target person identity to a user identity.
[0042] FIG. 1 illustrates a functional block diagram of a system [100] for mapping a
target person identity to a user identity, in accordance with exemplary implementations of
10

the present disclosure. The functionality of the system [100] is depicted in one or more steps
as explained below-
[0043] Essentially, in a preferred blockchain system, any person can send the identity
5 update request to the system [100]. The target person identity may relate to a person using
the system [100] to map the user identity with the target person identity. The user identity
may relate to a person whose details may get mapped with the target person identity.
10 [0044] At step 1, the target person [102] may send the identity update request to update
details of the target person [102]. The user [104] may be the spouse or child of the target person [102].
[0045] At step 2, the details of the target person [102] may be verified by a lawful
15 agency [106] using a one-time password (OTP) sent to the target person [102] via a short
message service (SMS) gateway [114]. The lawful agency [106] includes but may not be limited to the authorized legal document issuing authority.
[0046] At step 3, if the OTP entered by the target person [102] matches with the OTP
20 sent by the lawful agency [106] to the target person [102], the update is successful and the
target person [102] may set in the Unique Identification number for the user [104].
[0047] At step 4, to further uphold the identification of the system [100], a smart
contract [108] may validate the identity update request to update the details of the user [104],
25 the spouse in this instance, using the database [112] which may validate the identity update
request with a Marriage Registration database [110]. The smart contract [108] refers to a digital agreement that may be executed automatically when a condition in the contract matches with the identity update request. For instance, if the relationship between the user [104] and the target person [102] is confirmed by the marriage registration database [110],
30 the smart contract [108] may automatically validate the identity update request and proceed
to confirm the same from the user [104].
[0048] At step 5, the marriage registration database [110] may check if the user [104],
the spouse, has also consented for their details to be updated by sending a one-time password
35 (OTP) via the short message service (SMS) gateway [114]. If the validation is also
11

successful, then the spouse details get updated in the unique identity of both the user [402] and the target person [404], and the records may get stored in the Blockchain at step 6.
[0049] In case, the user [104] is the child of the target person [102], the smart contract
5 [108] may validate the identity update request to update the details of the user [104], using
the database [112] to validate the request with a birth registration database [116]. If the
validation is successful, then the child details may get updated in the unique identity of both
the target person [102] and the user [104], and the records may get stored in the blockchain
at step 6. Where the user [104] is the child, and is above 18 years of age, the birth registration
10 database [116] may validate and check if the child has consented for their details to be
updated. Where the user [104], the child is a minor, the validation may be performed by the lawful agency [106] itself.
[0050] Further, the components in the functional block diagram of the system [100]
15 will be explained in detail in the an exemplary block diagram of a system [300] as shown in
FIG. 3.
[0051] FIG. 2 illustrates an exemplary block diagram of a computing device [200]
upon which the features of the present disclosure may be implemented in accordance with
20 exemplary implementation of the present disclosure. In an implementation, the computing
device [200] may also implement a method for mapping a target person identity to a user identity utilising the system. In another implementation, the computing device [200] itself implements the method mapping a target person identity to a user identity, using one or more units configured within the computing device [200], wherein said one or more units
25 are capable of implementing the features as disclosed in the present disclosure. The present
disclosure is implemented by the system [100] (as shown in FIG. 1). In an implementation, the system [100] may include the computing device [200] (as shown in FIG. 2).
[0052] The computing device [200] may include a bus [202] or other communication
30 mechanism for communicating information, and a hardware processor [204] coupled with
bus [202] for processing information. The hardware processor [204] may be, for example, a general-purpose microprocessor. The computing device [200] may also include a main memory [206], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [202] for storing information and instructions to be executed by the
12

processor [204]. The main memory [206] also may be used for storing temporary variables
or other intermediate information during execution of the instructions to be executed by the
processor [204]. Such instructions, when stored in non-transitory storage media accessible
to the processor [204], render the computing device [200] into a special-purpose machine
5 that is customized to perform the operations specified in the instructions. The computing
device [200] further includes a read only memory (ROM) [208] or other static storage device coupled to the bus [202] for storing static information and instructions for the processor [204].
10 [0053] A storage device [210], such as a magnetic disk, optical disk, or solid-state drive
is provided and coupled to the bus [202] for storing information and instructions. The computing device [200] may be coupled via the bus [202] to a display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user.
15 An input device [214], including alphanumeric and other keys, touch screen input means,
etc. may be coupled to the bus [202] for communicating information and command selections to the processor [204]. Another type of user input device may be a cursor controller [216], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [204], and for controlling
20 cursor movement on the display [212]. This input device typically has two degrees of
freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
[0054] The computing device [200] may implement the techniques described herein
25 using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program
logic which in combination with the computing device [200] causes or programs the
computing device [200] to be a special-purpose machine. According to one implementation,
the techniques herein are performed by the computing device [200] in response to the
processor [204] executing one or more sequences of one or more instructions contained in
30 the main memory [206]. Such instructions may be read into the main memory [206] from
another storage medium, such as the storage device [210]. Execution of the sequences of instructions contained in the main memory [206] causes the processor [204] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
13

[0055] The computing device [200] also may include a communication interface [218]
coupled to the bus [202]. The communication interface [218] provides a two-way data
communication coupling to a network link [220] that is connected to a local network [222].
5 For example, the communication interface [218] may be an integrated services digital
network (ISDN) card, cable modem, satellite modem, or a modem to provide a data
communication connection to a corresponding type of telephone line. As another example,
the communication interface [218] may be a local area network (LAN) card to provide a
data communication connection to a compatible LAN. Wireless links may also be
10 implemented. In any such implementation, the communication interface [218] sends and
receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
[0056] The computing device [200] can send messages and receive data, including
15 program code, through the network(s), the network link [220] and the communication
interface [218]. In the Internet example, a server [230] might transmit a requested code for
an application program through the Internet [228], the ISP [226], the local network [222],
the host [224], and the communication interface [218]. The received code may be executed
by the processor [204] as it is received, and/or stored in the storage device [210], or other
20 non-volatile storage for later execution. The computing device [200] may further be able to
perform the steps of a method [400] (as shown in FIG. 4).
[0057] FIG. 3 illustrates an exemplary block diagram of a system [300] for mapping a
target person identity to a user identity, in accordance with exemplary implementations of
25 the present disclosure.
[0058] The system [300] comprises at least one server [120], at least one transceiver
unit [302], at least one authentication unit [304], at least one detection unit [306], at least
one mapping unit [308], at least one database [112], and at least one processing unit [312].
30 Also, all of the components/ units of the system [300] are assumed to be connected to each
other unless otherwise indicated below. As shown in the figures all units shown within the system should also be assumed to be connected to each other. Also, in FIG. 3 only a few units are shown, however, the system [300] may comprise multiple such units or the system [300] may comprise any such numbers of said units, as required to implement the features
14

of the present disclosure. Further, in an implementation, the system [300] may be present in
a user device to implement the features of the present disclosure. The system [300] may be
a part of the user device / or may be independent of but in communication with the user
device (may also referred herein as a UE). In another implementation, the system [300] may
5 reside in a server or a network entity. In yet another implementation, the system [300] may
reside partly in the server/ network entity and partly in the user device. Further, the system [300] is intended to be read in conjunction with the functional block diagram of the system [100] as shown in FIG. 1. The systems in FIG. 1 and FIG. 3 complement each other.
10 [0059] The system [300] is configured to map a target person identity to a user identity,
with the help of the interconnection between the components/units of the system [300]. In an implementation of the present disclosure, the target person identity may relate to a person using the system [300] to map the user identity with the target person identity. The user identity may relate to a person whose details may get mapped with the target person identity.
15
[0060] The system [300] includes the server [120]. In an implementation of the present
disclosure, the server [120] may be a blockchain that may provide platform-as-a-service (PaaS) functionality. The PaaS functionality may help the system to use blockchain technology. The server [120] may help in quick deployment of the method to map a target
20 person identity to a user identity through PaaS. The server [120] further comprises a
transceiver unit [302] configured to receive, an identity update request associated with a target person [102]. The identity update request is associated with at least one or more identification parameters associated with the target person [102]. The identity update request refers to a request by the target person [102] to add the one or more identification parameters
25 of the target person [102] and a user [104] to establish a relationship between the target
person [102] and the user [104]. The target person [102] may be one of an heir, head of the family, and the like. The user [104] may be one of a spouse, a child, a father, a mother, and any other person associated with the target person [102]. The one or more identification parameters associated with the target person [102] is at least one of a target person name, a
30 target person address, and a target person relationship with the user [104]. For instance, Mr.
X initiates the identity update request for his spouse- Mrs. Y, by sending the identity update request through the transceiver unit [302] of the server [120]. The identity update request is a request sent by Mr. X along with identification parameters for processing of the request as shown below:
15

Name: Mrs. Y
Address: C-14, City ABCD
Relationship with Y of the target person [102]: Spouse 5
[0061] The one or more identification parameters are not limited to the mentioned
parameters. The solution outlined herein is intended to cover a wide range of the identity update request and may not be limited solely to the user [104].
10 [0062] The server [120] of the system [300] further includes an authentication unit
[304] connected to at least the transceiver unit [302]. The authentication unit [304] is configured to initiate a first authentication check request based on the identity update request. When the identity update request is sent to the authentication unit [304] by the transceiver unit [302], the authentication unit [304] may trigger the first authentication
15 check request after validating the details in the identity update request. In an implementation
of the present disclosure, the first authentication check request includes authentication, by the authentication unit [304], of the one or more identification parameters sent to the transceiver unit [302] by the target person [102]. The first authentication check request may be sent to the target person [102] for authentication. The process of first authentication check
20 may include verifying the one or more identification parameters and comparing the one or
more identification parameters against stored parameters in the database [112], and the like.
[0063] The server [120] of the system [300] further includes a detection unit [306]
connected to at least the authentication unit [304]. The detection unit [306] is configured to
25 detect a successful first authentication response based on the first authentication check
request. For detecting the successful authentication check request, the detection unit [306] may monitor the authentication unit [304]. The successful first authentication response is to authenticate the one or more identification parameters sent by the target person [102]. The successful first authentication response is detected by the detection unit [306] based on a
30 one-time password (OTP) received from the target person [102] associated with the first
authentication check request. The detection unit [306] may generate the OTP and the transceiver unit [302] may send the OTP to the target person [102] to authenticate the target person [102]. The detection of the successful first authentication response based on the OTP, by the detection unit [306], validates the one or more identity parameters associated with
16

the target person [102]. For instance, the detection unit [306] may generate the OTP and the
transceiver unit [302] sends the OTP to the Mr. X. Further, Mr. X enters the OTP in the
transceiver unit [302]. The detection unit [306] may compare and check if the OTP entered
by Mr. X is same. If the OTP is matched, the detection unit [306] may validate the one or
5 more parameters associated with the target person [102].
[0064] In an implementation of the present solution, the first authentication check
request based on the identity update request is initiated by the authentication unit [304]. The detection unit [306] may detect the successful first authentication response detected based
10 on the OTP received from target person [102]. The successful first authentication response
based on successful authentication of the valid identity associated with the target person [102] is received at the transceiver unit [302]. For instance, the detection unit [306] may check for the authenticity of the target person [102] via OTP confirmation. The detection unit [306] may generate an OTP, if the OTP entered by the target person [102] successfully
15 matches with the OTP generated at the detection unit [306], the first authentication check
request may be considered as the successful first authentication response. If the OTP match is unsuccessful at the detection unit [306], the transceiver unit [302] of the server [120] may send a response ‘INVALID USER’ to the target person [404].
20 [0065] The authentication unit [304] is further configured to initiate, a second
authentication check request based on the successful first authentication response. For initiating the second authentication check request, the authentication unit [304] may monitor the transceiver unit [302] for the successful first authentication response. The authentication unit [304] may trigger the second authentication check request after validating the details in
25 the successful first authentication response. In an implementation of the present disclosure,
after the authentication of the target person [102] in the successful first authentication response, the second authentication check request may include authenticating the relationship between the target person [102] and the user [104], by requesting a validation from the user [104]. The first authentication check request is for validating the identity of
30 the target person [102] based on the one or more identification parameters entered by the
target person in the system [300]. The first authentication check request is for receiving validation by the target person [102]. Whereas, in the second authentication check request, after the authentication of the target person [102] in the successful first authentication response, the second authentication check request may include authenticating the
17

relationship between the target person [102] and the user [104], by requesting a validation from the user [104].
[0066] The detection unit [306] further configured to detect, a successful second
5 authentication response based on the second authentication check request. For detecting the
successful second authentication check request, the detection unit [306] may monitor the authentication unit [304]. The second authentication response is for receiving the validation to confirm the relationship between the user [104] and the target person [102] from the user [104] for a target person relationship identity update request . The target person relationship
10 identity update request refers to validation of the relationship between the user [104] and
the target person [102], based on a validation response received from the user [104]. The successful second authentication response is detected by the detection unit [306] based on at least retrieving by the transceiver unit [302], a valid legal relationship document from a database [112] and on the OTP received from the user [104]. In an implementation of the
15 present solution, the valid relationship document associated with the user [104] and the
target person [102] includes but may not be limited to a valid marriage registration document or a valid birth registration certificate issued by an authorized issuing authority. Based on the successful second authentication response from the user [104], the transceiver unit [302], validates consent of the user [104] for the target person [102] relationship identity update
20 request.
[0067] In an implementation of the present solution, the transceiver unit [302] may
retrieve the valid legal relationship document from the database [112].The process of retrieving may include sending a query to the database [112] by the transceiver unit [302].
25 Based on the valid legal relationship document, the detection unit [306] may detect the
successful second authentication response. The valid legal relationship document may be one of a marriage registration document, a birth registration document, and the like. The valid legal relationship document may be issued by an authorized document issuing authority. The authorized document issuing authority may be one of a centralized identity
30 document issuing authority. For instance, the transceiver unit [302] of the server [120]
retrieves the valid legal relationship document associated with the user [104] and the target person [102] based on the one or more identification parameters sent by the target person [102]. The relationship between Mr. X and Mrs. Y is established by confirming the details from the valid legal relationship document from the database [112]. The authentication unit
18

[304] may initiate the second authentication check request by sending the OTP to Mrs. Y,
if the OTP entered by Mrs. Y matches with the OTP sent by the transceiver unit [302] of the
server [120], it will be considered as validation of the successful second authentication
response, and the relationship between the target person [102] and the user [104] is
5 established successfully. If the user [104] does not validate the identity update request or
the OTP does not match, a message may be sent to the target person [102] and the user [104] ‘INVALID REQUEST’.
[0068] In another embodiment, Mr. X is using the system [100] to map his child Z. The
10 transceiver unit [302] may confirm and establish the relationship by confirming the details
by retrieving the valid legal relationship document from the database [112]. The valid legal
relationship document may be the birth registration document of the child Z. The
authentication unit [304] may initiate the second authentication check request. If the child
Z is above the age of 18 years, the transceiver unit [302] may generate and send the OTP to
15 the child Z, whereas if the child Z is below the age of 18, the second authentication check
response may not be required from the child Z. If the child Z sends the OTP to the transceiver
unit [302], and the OTP is matched successfully with the OTP generated by the transceiver
unit [302], it may be considered as the validation of the successful second authentication
response.
20
[0069] The server [120] of the system [100] further includes a mapping unit [308]
connected to at least the authentication unit [304]. The mapping unit [308] is configured to
map, the target person identity and the user identity based on at least the successful second
authentication response.
25
[0070] In an implementation of the present disclosure, once the relationship between
the target person [102] and the user [104] is established based on the valid legal relationship
document, the mapping unit [308] may map the user [104] with the target person [102].
Mapping the user [104] with the target person [102] may include mapping the one or more
30 parameters from the valid identity document associated with the user [104] and to the one
or more parameters of the target person [102]. Further, the mapping unit [308] may store
the one or more parameters from the valid identity document in a blockchain.
19

[0071] The server [120] further comprises the processing unit [312] configured to
update an identification document associated with the target person [102] and an
identification document associated with the user [104] at the database [112]. The
identification document may be a document issued by an authorized document issuing
5 authority. The authorized document issuing authority may be one of a centralized identity
document issuing authority. The identification document may be the Adhaar card, Passport,
driving license, and the like. In an implementation of the present disclosure, once the user
[104] is mapped with the target person [102], the processing unit [312] of the server [120]
may update the identification document of the user [104] to the identification document of
10 the target person [404]. The processing unit [312] may further send a notification via the
transceiver unit [302] to the user [104] and the target person [102] of a successful mapping of the user [104] to the target person [102].
15 [0072] Referring to FIG. 4, an exemplary method flow diagram [400] for mapping a
target person identity to a user identity, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [400] is performed by the system [300]. Further, in an implementation, the system [300] may be present in a server device to implement the features of the present disclosure. In an implementation of the
20 present disclosure, the method [400] may be performed at the server [120]. The server [120]
may be a blockchain that may provide platform-as-a-service (PaaS) functionality. The PaaS
functionality may help the system to use blockchain technology. The server [120] may help
in quick deployment of the method to map a target person identity to a user identity through
PaaS. Also, as shown in FIG. 4, the method [400] starts at step [402].
25
[0073] At step [404], the method [400] comprises receiving, by a transceiver unit [302]
at a server [120], an identity update request associated with a target person [102]. The
identity update request is associated with at least one or more identification parameters
associated with the target person [102]. The identity update request refers to a request by
30 the target person [102] to add the one or more identification parameters of the target person
[102] and the user [104] to establish a relationship between the target person [102] and the
user [104]. The user [104] may be one of a spouse, a child, a father, a mother, and any other
person associated with the target person [102]. The one or more identification parameters
associated with the target person [102] is at least one of a target person name, a target person
20

address, and a target person relationship with the user [104]. For instance, Mr. X initiates
the identity update request for his spouse- Mrs. Y, by sending the identity update request
through the transceiver unit [302] of the server [120]. The identity update request includes
Mr. X to send identification parameters for processing of the request:
5
Name: Mrs. Y
Address: C-14, City ABCD
Relationship with Y of the target person [102]: Spouse
10 [0074] The solution outlined herein is intended to cover a wide range of the identity
update request and may not be limited solely to the user [104].
[0075] Next, at step [406], the method [400] includes initiating, by an authentication
unit [304] at the server [120], a first authentication check request based on the identity
15 update request.
[0076] In an implementation of the present disclosure, the first authentication check
request includes authenticating, by the authentication unit [304], of the one or more
identification parameters sent to the transceiver unit [302] by the target person [102]. The
20 first authentication check request may be sent to the target person [102] for authentication.
[0077] Next, at step [408], the method [400] includes detecting, by a detection unit
[306] at the server [120], a successful first authentication response based on the first authentication check request. The successful first authentication response is to authenticate
25 the one or more identification parameters sent by the target person [102]. The successful
first authentication response based on the first authentication check request is detected by the detection unit [306] based on a first one time password (OTP) received from the target person associated with the first authentication check request. The detection unit [306] may generate the OTP and the transceiver unit [302] may send the OTP to the target person [102]
30 to authenticate the target person [102]. The detection of the successful first authentication
response based on the OTP, by the detection unit [306], validates the one or more identity parameters associated with the target person [102]. For instance, the detection unit [306] may generate the OTP and the transceiver unit [302] sends the OTP to the Mr. X. Further, Mr. X enters the OTP in the transceiver unit [302]. The detection unit [306] may compare
21

and check if the OTP entered by Mr. X is same. If the OTP is matched, the detection unit [306] may validate the one or more parameters associated with the target person [102].
[0078] In an implementation of the present solution, the first authentication check
5 request based on the identity update request is initiated by the authentication unit [304]. The
detection unit [306] may detect the successful first authentication response detected based on the OTP received from target person [102]. The detection unit [306] may generate the OTP, and the transceiver unit [302] may send the OTP to the target person [102] to authenticate the target person [102]. The successful first authentication response based on
10 successful authentication of the valid identity associated with the target person [102] is
received at the transceiver unit [302]. For instance, the detection unit [306] may check for the authenticity of the target person [102] via OTP confirmation. The detection unit [306] may generate an OTP, if the OTP entered by the target person [102] successfully matches with the OTP generated at the detection unit [306], the first authentication check request
15 may be considered as the successful first authentication response. If the OTP match is
unsuccessful at the detection unit [306], the transceiver unit [302] of the server [120] may send a response ‘INVALID USER’ to the target person [404].
[0079] Next, at step [410], the method [400] includes initiating, by the authentication
20 unit [304] at the server [120], a second authentication check request based on the successful
first authentication response.
[0080] In an implementation of the present disclosure, after the authentication of the
target person [102] in the successful first authentication response, the second authentication
25 check request may include authenticating the relationship between the target person [102]
and the user [104], by requesting a validation from the user [104].
[0081] Next, at step [412], the method [400] includes detecting, by the detection unit
[306] at the server [120], a successful second authentication response based on the second
30 authentication check request. The second authentication response is for receiving the
validation from the user [104] associated with the target person [102]. The successful second authentication response is detected by the detection unit [306] based on at least retrieving by the transceiver unit [302] a valid legal relationship document, from the database [112 and on the OTP received from the user [104]. In an implementation of the present solution, the
35 valid relationship document associated with the user [104] and the target person [102]
22

includes but may not be limited to a valid marriage registration document or a valid birth registration certificate issued by an authorized issuing authority. Based on the successful second authentication response from the user [104], the transceiver unit [302], validates consent of the user [104] for the target person [102] relationship identity update request. 5
[0082] In an implementation of the present solution, the transceiver unit [302] may
retrieve the valid legal relationship document from the database [112]. Based on the valid legal relationship document, the detection unit [306] may detect the successful second authentication response. The valid legal relationship document may be one of a marriage
10 registration document, a birth registration document, and the like. The valid legal
relationship document may be issued by an authorized document issuing authority. The authorized document issuing authority may be one of a centralized identity document issuing authority. For instance, the transceiver unit [302] of the server [120] retrieves the valid legal relationship document associated with the user [104] and the target person [102]
15 based on the one or more identification parameters sent by the target person [102]. The
relationship between Mr. X and Mrs. Y is established by confirming the details from the valid legal relationship document from the database [112]. The authentication unit [304] may initiate the second authentication check request by sending the OTP to Mrs. Y, if the OTP entered by Mrs. Y matches with the OTP sent by the transceiver unit [302] of the server
20 [120], it will be considered as validation of the successful second authentication response,
and the relationship between the target person [102] and the user [104] is established successfully. If the user [104] does not validate the identity update request or the OTP does not match, a message may be sent to the target person [102] and the user [104] ‘INVALID REQUEST’.
25
[0083] In another embodiment, Mr. X is using the system [300] to map his child Z. The
transceiver unit [302] may confirm and establish the relationship by confirming the details by retrieving the valid legal relationship document from the database [112]. The valid legal relationship document may be the birth registration document of the child Z. The
30 authentication unit [304] may initiate the second authentication check request. If the child
Z is above the age of 18 years, the transceiver unit [302] may generate and send the OTP to the child Z, whereas if the child Z is below the age of 18, the second authentication check response may not be required from the child Z. If the child Z sends the OTP to the transceiver unit [302], and the OTP is matched successfully with the OTP generated by the transceiver
23

unit [302], it may be considered as the validation of the successful second authentication response.
[0084] Next, at step [414], the method [400] includes mapping, by a mapping unit [308]
5 at the server [120], the target person identity and the user identity based on at least the
successful second authentication response.
[0085] In an implementation of the present disclosure, once the user [104] is mapped
with the target person [102], the processing unit [312] of the server [120] may update the
10 identification document of the user [104] to the identification document of the target person
[404]. The processing unit [312] may further send a notification via the transceiver unit [302] to the user [104] and the target person [102] of a successful mapping of the user [104] to the target person [102].
15 [0086] The method [400] further comprises, updating, by the processing unit [312] an
identification document associated with the target user and an identification document associated with the user at the database [112]. In an implementation of the present disclosure, once the user [104] is mapped with the target person [102], the processing unit [312] of the server [120] may update the identification document of the user [104] to the
20 identification document of the target person [404]. The processing unit [312] may further
send a notification via the transceiver unit [302] to the user [104] and the target person [102]
of a successful mapping of the user [104] to the target person [102]. Further, the mapping
unit [308] may store the one or more parameters from the valid identity document in a
blockchain.
25
[0087] The method [400] terminates at step [416].
[0088] Further, in accordance with the present disclosure, it is to be acknowledged that
the functionality described for the various components/units can be implemented
30 interchangeably. While specific embodiments may disclose a particular functionality of
these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the
24

intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
[0089] Further, to implement the exemplary implementation of the system [300], the
5 implementation of a method flow [500] is depicted in FIG. 5. The method [500] is a process
flow for mapping the target person identity to the user identity. The method [500] is in
conjunction with the system [300]. In an exemplary scenario, the method [500] may be
performed in the following steps-
10 [0090] At step [501], the target person [102] logs into the server [120] to link the user
[104] into family. The target person [102] may initiate the identity update request for the
user [104]. The user [104] may be the spouse, the child, or any other person related to the
target person [102].
15 [0091] At step [502], the lawful agency [106] may check for the authenticity of the
target person [102] via an OTP confirmation.
[0092] At step [503], if the OTP matches successfully, the identity update request may
proceed to step 5 further accordingly.
20
[0093] At step [504], if the OTP match is unsuccessful, the user [104] may receive a
response ‘INVALID USER’ from the server [120].
[0094] At step [505], once the OTP match is successful, the validation is passed.
25
[0095] At step [506], the target person [102] may set in the Unique Identification
number for the user [104]. For instance, the user [104] in this case is the spouse of the target
person [102].
30 [0096] At step [507], the smart contract [108] may validate the request to update the
details of the target person [102] using the database [112]. The database [112] may validate
the identity update request with the Marriage Registration database [110]. The marriage
registration database [110] may check if the user [104], the spouse, has also consented for
their details to be updated.
35
[0097] At step [508], the marriage registration database [110] may check if the
validation is successful or not from the side of the target person [102].
25

[0098] At step [509], if the user [104] does not validate the identity update request, a
message may be sent to the target person [102] and the user [402] ‘INVALID REQUEST’.
5 [0099] At step [510], if the user [104] validates the identity update request to update
the details, the relationship between the target person [102] and the user [104] may be
established, and details may get updated in the unique identity of both the target person
[102] and the user [104], and the records may get stored in the Blockchain. The method
[500] ensures that the relationship of the target person [102] with the user [104], who may
10 be the heir or head, is easily established without long processes of proving and
documentations.
[0100] For Example- the target person [102] may set spouse_ID (identification
Number) for the user [104]. The identification number is verified by the Marriage
15 Registration database [110]. If true, and the user [104] also acknowledges the same (via
OTP confirmation), the target person [102] gets set to the identification number of the user
[104] and vice versa, the user [104] may get set to the identification number of the target
person [102] identification number. The identification number may get written to the
blockchain and a notification may be sent to both the target person [102] and the user [104].
20
[0101] In another instance, the target person [102] may act as the initiator and initiates
the request to update the details for the child. The lawful agency [106] may check for the
authenticity of the target person [102] via OTP confirmation. The smart contract [108] may
be used to check the request against the database [112] to validate the target person’s [102]
25 spouse consent too.
[0102] For example- the user may set child_ID. The identification number may get
verified by the Birth Registration database [116]. If true, and the child also acknowledge the
same then the target person [102] and their spouse are set to the child’s identity number and
30 vice versa. In case of the child being a minor, the lawful agency [106] may acknowledge the
same on behalf of the child. The identity numbers are stored in the blockchain, and a notification may be sent to the target person [102], the spouse, and the child.
[0103] FIG. 6 illustrates an exemplary use case of the present disclosure, in accordance
35 with exemplary implementations of the present disclosure.
26

[0104] As shown in FIG. 6, a first identity card [602] belongs to the target person [102].
Further, a second identity card [604] may belong to a first user. For example, the first user
may be spouse of the target person [102]. A third identity card [606] and a fourth identity
card [608] may be of a second user and a third user. In an embodiment, the second user and
5 the third user maybe the children of the target person [102] and the first user.
[0105] The system [600] is configured to perform mapping of the first user with the
target person [102]. The mapping may include mapping the one or more parameters from
the second identity card [604] associated with the first user to the one or more parameters
10 of the first identity card [602].
[0106] Further, the system [600] is configured to perform mapping the third identity
card [606] and the fourth identity card [608] with the first identity card [602] and the second
identity card [604]. The system [600] facilitates identifying the legal heirs of the target
15 person [102], as all the users associated with the target person [102] are mapped with the
first identity card [602] of the target person [102].
[0107] The present disclosure further discloses a non-transitory computer readable
storage medium storing instructions for mapping a target person identity to a user identity,
20 the instructions include executable code which, when executed by one or more units of a
system, causes a transceiver unit [302] of the system to receive an identity update request associated with a target person. The identity update request is associated with at least one or more identification parameters associated with the target person. The instructions when executed by the system further causes an authentication unit [304] of the system to initiate
25 a first authentication check request based on the identity update request. The instructions
when executed by the system further causes a detection unit [306] of the system to detect, a successful first authentication response based on the first authentication check request. The instructions when executed by the system further cause the authentication unit [304] of the system to initiate, a second authentication check request based on the successful first
30 authentication response. The instructions which, when executed, causes the detection unit
[306] of the system to detect, a successful second authentication response based on the second authentication check request. The instructions when executed by the system further causes a mapping unit [308] of the system to map, the target person identity and the user identity based on at least the successful second authentication response.
27

[0108] The present disclosure further discloses a user equipment (UE) for mapping a
target person identity to a user identity. The user equipment (UE) includes a transceiver unit
[302] configured to send, to a server, an identity update request associated with a target
5 person, wherein the identity update request is associated with at least one or more
identification parameters associated with the target person. The transceiver unit [302] is further configured to send to the server [120], a first one time password (OTP) associated with the target person to validate the identity update request associated with the target person. The validating the identity update request associated with the target person
10 comprises validating the one or more identification parameters associated with the target
person. Furthermore, the transceiver unit [302] is configured to send to the server [120], a target person relationship identity update request between the target person [102] and the user [104], based on the validity of the identity check request associated with the target person [102]. The transceiver unit [302] is further configured to send, to the server, a second
15 OTP associated with the user, wherein the second OTP validates the target person
relationship identity update request. The transceiver unit [302] is further configured to receive, from the server [120], a mapping notification, based on the validated target person relationship identity update request, wherein the mapping notification is associated with a mapping of the target person identity to the user identity.
20
[0109] As is evident from the above, the present disclosure provides a technically
advanced solution for mapping a target person identity to a user identity. The present solution provides a solution initiates a first authentication check request associated with a target person identity document based on the update request associated with the target
25 person. The present solution further provides a solution that initiates a second authentication
check request associated with the target person relationship document based on the successful first authentication response. The present solution further provides a solution to map the target person with the user based on at least one of the successful first authentication response and the successful second authentication response.
30
[0110] While considerable emphasis has been placed herein on the disclosed
implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present
28

disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

We Claim,
1. A method for mapping a target person identity to a user identity, the method comprising:
- receiving, by a transceiver unit [302] at a server [120], an identity update request
5 associated with a target person, wherein the identity update request is associated with at
least one or more identification parameters associated with the target person;
- initiating, by an authentication unit [304] at the server [120], a first authentication check
request based on the identity update request;
- detecting, by a detection unit [306] at the server [120], a successful first authentication
10 response based on the first authentication check request;
- initiating, by the authentication unit [304] at the server [120], a second authentication check request based on the successful first authentication response;
- detecting, by the detection unit [306] at the server [120], a successful second authentication response based on the second authentication check request; and
15 - mapping, by a mapping unit [308] at the server [120], the target person identity and the
user identity based on at least the successful second authentication response.
2. The method as claimed in claim 1, wherein the one or more identification parameters
associated with the target person [102] is at least one of a target person name, a target
20 person address, and a target person relationship with a user [104].
3. The method as claimed in claim 1, wherein the successful first authentication response
based on the first authentication check request is detected by the detection unit [306] based
on a first one time password (OTP) received from the target person [102] associated with
25 the first authentication check request.
4. The method as claimed in claim 3, wherein the detection of the successful first
authentication response based on the OTP, by the detection unit [306], validates the one or
more identity parameters associated with the target person [102].
30
5. The method as claimed in claim 2, wherein the second authentication check request is
associated with at least the target person relationship identity update request between the
target person [102] and the user [104], and wherein the successful second authentication

response is detected by the detection unit [306] based on at least retrieving by the transceiver unit [302] a valid legal relationship document, from a database [112], associated with the target person [102] and the user [104], and on a second OTP received from the user [104]. 5
6. The method as claimed in claim 5, wherein the detection of the successful second
authentication response based on the retrieving of at least the valid legal relationship
document and the second OTP, by the transceiver unit [302], validates acknowledgement
from the user [104] for the target person relationship identity update request.
10
7. The method as claimed in claim 1, further comprising:
updating, by a processing unit [312], an identification document associated with the
target person [102] and an identification document associated with the user [104] at the
15 database [112].
8. A system for mapping a target person identity to a user identity, the system comprising a
server [120], the server [120] further comprising:
- a transceiver unit [302] configured to receive, an identity update request associated with
20 a target person, wherein the identity update request is associated with at least one or
more identification parameters associated with the target person [102];
- an authentication unit [304] connected to at least the transceiver unit [302], the
authentication unit [304] configured to initiate, a first authentication check request based
on the identity update request;
25 - a detection unit [306] connected to at least the authentication unit [304], the detection
unit [306] configured to detect, a successful first authentication response based on the first authentication check request;
- the authentication unit [304] further configured to initiate, a second authentication check
request based on the successful first authentication response;
30 - the detection unit [306] further configured to detect, a successful second authentication
response based on the second authentication check request; and
- a mapping unit [308] connected to at least the authentication unit [304], the mapping
unit [308] configured to map, the target person identity and the user identity based on at
least the successful second authentication response.
31

9. The system as claimed in claim 8, wherein the one or more identification parameters
associated with the target person [102] is at least one of a target person name, a target
person address, and a target person relationship with a user.
5
10. The system as claimed in claim 8, wherein the successful first authentication response
based on the first authentication check request is detected by the detection unit [306] based
on a one time password (OTP) received from the user [104] associated with the first
authentication check request.
10
11. The system as claimed in claim 10, wherein the detection unit [306] is configured to
detection unit [306]validate the one or more identity parameters associated with the target
person [102] based on the detection of the successful first authentication response based on
the OTP, by the detection unit [306].
15
12. The system as claimed in claim 8, wherein the second authentication check request is
associated with at least the target person relationship identity update request between the
target person [102] and the user [104], and wherein the successful second authentication
response is detected by the detection unit [306] based on at least retrieving by the
20 transceiver unit [302], a valid legal relationship document from a database [112] associated
with the target person and the user, and on a second OTP received from the user [104].
13. The system as claimed in claim 12, wherein the transceiver unit [302] is further configured
to validate consent of the user for the target person relationship identity update request
25 based on the detection of the successful second authentication response based on the
retrieving of at least the valid legal relationship document and the second OTP.
14. The system as claimed in claim 8, further comprising a processing unit [312] configured to
update an identification document associated with the target person [102] and an
30 identification document associated with the user [104] at the database [112].
15. A user equipment (UE) for mapping a target person identity to a user identity, the user
equipment (UE) comprising:

a transceiver unit [302] configured to:
- send, to a server [120], an identity update request associated with a target person [102],
wherein the identity update request is associated with at least one or more identification
parameters associated with the target person [102];
5 - send, to the server [120], a first one-time password (OTP) associated with the target
person [102] to validate the identity update request associated with the target person
[102], wherein the validating the identity update request associated with the target
person [102] comprises validating the one or more identification parameters associated
with the target person [102];
10 - send, to the server [120], the target person relationship identity update request between
the target person [102] and a user [104], based on the validity of the identity check request associated with the target person [102];
- send, to the server [120], a second OTP associated with the user [104], wherein the
second OTP validates the target person relationship identity update request;
15 - receive, from the server [120], a mapping notification, based on the validated target
person relationship identity update request, wherein the mapping notification is associated with a mapping of the target person identity to the user identity.