FORM2
THE PATENTS ACT, 1970
(39 OF 1970)
&
THE PATENTS RULES, 2003
COMPLETE SPECIFICATION
[SEE SECTION 10, RULE 13]
MULTI-SERVER USER ADDRESS MANAGEMENT SYSTEM
AND METHOD THERE OF
ADITYABIRLAIDEAPAYMENTSBANK LIMITED
AN INDIAN COMPANY,
A WING, 4TH FLOOR, ADITYA BIRLA CENTER, S K AHIRE MARG,
WORLI, MUMBAI – 400 030, MH, INDIA
THEFOLLOWINGSPECIFICATION PARTICULARLY DESCRIBES THE INVENTIONANDTHE MANNER IN WHICHIT IS TO BE
PERFORMED.

TECHNICAL FIELD
[001] The present invention relates generally to user identification on digital
platforms, and, particularly but not exclusively, to digital user identity management for plurality of user addresses.
BACKGROUND
[002] With the advent of digitization and widespread use of smartphones, a
plethora of digital platforms have evolved to facilitate online transactions including banking transactions, such as securities and fund transfers, on various types of mobile devices. Hence, transacting on smartphones has become a lot more quicker and easier than the conventional web-based online transactions. Furthermore, various service providers have developed proprietary mobile applications to facilitate transactions through the various platforms. This has enabled users to have more than one user accounts on various platforms, with each user account having a different user address. Further, this has also enabled the users to have a unique user account for each of these platforms. This has resulted into duplication of same user information on various platforms as well as plurality of user accounts for the same user. In view of this, there is a scope for misperception as there are possibilities where different user addresses may be used for same user.
[003] Therefore, there is a need of a system and method for digital user identity
management for plurality of user addresses in a multi-server computing environment.
SUMMARY
[004] This summary is provided to introduce concepts related to managing
digital user identity for plurality of user addresses in a multi-server computing environment. More specifically, this summary provides a system and method of searching for plurality of user address in a multi-server system. This summary is

neither intended to identify essential features of the present invention nor is it intended for use in determining or limiting the scope of the present invention.
[005] For example, various embodiments herein may include one or more
systems and methods of searching for user addresses in a multi-server system. In one of the embodiment, the method includes receiving, at a server, a user identifier from a user device. The method includes extracting, by a processor coupled with the server, a plurality of handles stored in a memory coupled with the server. Further, the method includes generating, by the processor, a plurality of user addresses by appending the user identifier to each of the plurality of handles, and generating, by the processor, a plurality of threads corresponding to the plurality of user addresses. To this end, the method further includes generating and transmitting a plurality of search requests through the plurality of threads to a formal server, wherein each thread of the plurality of threads generates a unique search request corresponding to one of the plurality of user addresses and transmits the search request to the formal server. The method includes redirecting, by the formal server, one of the plurality of threads to a secondary database associated with a secondary server. Further, the method includes receiving, at the server through said thread, a registered user name and a registered user address corresponding to the user identifier from the secondary database through the formal server. Upon receiving the user name and registered user address from said secondary database, suspending remaining threads of the plurality of threads. The method, further, includes storing the registered user name and the registered user address in a primary database, and transmitting the registered user name and the registered user address to the user device.
[006] Alternatively, the method further includes the primary database stores the
first set of user addresses, a first set of user identifiers, a first set of user names, and wherein each user address uniquely corresponds to one of the first set of user identifiers, and wherein each user address uniquely corresponds to one of the first set of user names.

[007] Alternatively, the method f urther includes the secondary database stores a
secondary set of user addresses, a second set of user identifiers, a second set of user names, and wherein each user address uniquely corresponds to one of the second set of user identifiers, and wherein each user address uniquely corresponds to one of the second set of user names.
[008] In another embodiment, the method includes generating, by the processor,
a primary user address by appending the user identifier to a primary user handle. Further, the method includes searching, by the server, a first set of user addresses stored in the primary database connected to the server, to determine if any user address of the first set of user addresses matches with the primary user address. Subsequently, the method includes retrieving, by the server, a matching user address and corresponding matching user name from the primary database, and transmitting, by the server, the matching user address and the matching user name to the user device.
[009] In another embodiment, the method includes receiving, at the server from
the formal server by way of the plurality of threads, a plurality of redirection instructions corresponding to a plurality of secondary servers, wherein each thread of the plurality of threads is directed to one of the plurality of secondary servers based on corresponding redirection instruction.
[0010] In another embodiment, the system includes a user device configured to transmit a user identifier and a server in communication with the user device having a memory storing a plurality of handles and a processor coupled with the memory. The processor is configured to receive the user identifier and extract the plurality of handles from the memory. Further, the processor is configured to generate a plurality of user addresses by appending the user identifier to each of the plurality of handles and then generate a plurality of threads corresponding to the plurality of user addresses. Subsequently, the processor is configured to generate and transmit a plurality of search requests through the plurality of threads to a formal server, wherein each thread of the plurality of threads generates a unique search request

corresponding to one of the plurality of user addresses and transmits the search request to the formal server. Further, the processor is configured to redirect, by the formal server, one of the plurality of threads to a secondary database and receive, through said thread, a registered user name and a registered user address corresponding to the user identifier from the secondary database through the formal server. Upon receiving the registered user name and the registered user address from said secondary database, the processor is configured to suspend remaining threads of the plurality of threads. Further, the processor is configured to store the registered user name and the registered user address in a primary database and transmit the registered user name and the registered user address to the user device.
[0011] In another embodiment, the processor is further configured to generate a primary user address by appending the user identifier to a primary user handle and search a first set of user addresses stored in the primary database connected to the server, to determine if any user address of the first set of user addresses matches with the primary user address. Further, the processor is configured to retrieve a matching user address and corresponding matching user name from the primary database and then transmit the matching user address and the matching user name to the user device.
[0012] Alternatively, the system is further configured to receive, from the formal server by way of the plurality of threads, a plurality of redirection instructions corresponding to a plurality of secondary servers, wherein each thread of the plurality of threads is directed to one of the plurality of secondary servers based on corresponding redirection instruction.
[0013] Alternatively, the system includes the registered user address which may be a virtual payment address (VPA) corresponding to the user identifier, wherein the user identifier may include a mobile number registered in the name of the registered user name.

BRIEF DESCRIPTION OF ACCOMPANYING DRAWINGS
[0014] The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the drawings to reference like features and modules.
[0015] Figure 1 illustrates a schematic diagram of a multi-server system (100), according to an exemplary implementation of the present invention.
[0016] Figure 2 illustrates a schematic block diagram (200) of the multi-server system (100) of Figure 1, according to an exemplary implementation of the present invention.
[0017] Figure 3 illustrates a schematic diagram (300) of functioning of the multi-server system (100), according to an embodiment of the present invention.
[0018] Figure 4 illustrates a timing sequence diagram (400) of functioning of the multi-server system (100), according to an embodiment of the present invention.
[0019] Figures 5A-5D illustrates a flowchart (500) depicting a process flow of the multi-server system (100), according to an exemplary implementation of the present invention.
[0020] It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative systems embodying the principles of the present invention. Similarly, it will be appreciated that any flowcharts, flow diagrams, and the like represent various processes which may be substantially represented in computer readable medium and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.

DETAILED DESCRIPTION
[0021] In the following description, for the purpose of explanation, specific details are set forth in order to provide an understanding of the present invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced without these details. One skilled in the art will recognize that embodiments of the present invention, some of which are described below, may be incorporated into a number of systems.
[0022] The various embodiments of the present invention provide a system and a method of searching for user addresses in a multi-server system.
[0023] References in the present invention to “one embodiment” or “an embodiment” mean that a 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 present specification are not necessarily all referring to the same embodiment.
[0024] In one of the implementation, the present invention discloses a multi-server system for searching user addresses which may be stored in a primary database or in one of a plurality of secondary databases. The multi-server system includes a user device that is configured to transmit a user identifier, and a server which is communicatively coupled with the user device and includes a memory and a processor. Further, in the present invention, a user may search for a registered user name of another user by just inputting a user identifier of that registered user with the help of the user device. Upon receiving the user identifier from the user device, the server extracts a plurality of handles and generates a plurality of user address by appending the user identifier to each of the plurality of handles. Based on the generated user addresses, the server generates a plurality of threads corresponding to each of the generated user addresses. Subsequently, the server generates and transmits a plurality of search requests through the plurality of threads to a formal

server, wherein each thread of the plurality of threads generates a unique search request corresponding to one of the plurality of user addresses and transmits the search request to the formal server. Upon receiving the plurality of threads, the formal server redirects one of the plurality of threads to a secondary database associated with a secondary server. Once the registered user address is found in any one of the secondary database, the same is communicated to the server through the formal server. Subsequently, the remaining threads of the plurality of threads may be suspended upon receiving the registered user name and registered user address from the secondary database. Further, the registered user name and the registered user address is stored in the primary database and transmits the same to the user devices coupled with the server.
[0025] In the present implementation, the server may be configured to receive, from a formal server by way of a plurality of threads, a plurality of redirection instructions corresponding to a plurality of secondary servers, wherein each thread of the plurality of threads is directed to one of the plurality of secondary databases based on corresponding redirection instruction.
[0026] In the present implementation, the primary database may be configured to store the first set of user addresses, a first set of user identifiers, a first set of user names, and wherein each user address uniquely corresponds to one of the first set of user identifiers, and wherein each user address uniquely corresponds to one of the first set of user names.
[0027] In the present implementation, the secondary database may be configured to store a secondary set of user addresses, a second set of user identifiers, a second set of user names, and wherein each user address uniquely corresponds to one of the second set of user identifiers, and wherein each user address uniquely corresponds to one of the second set of user names.
[0028] In another implementation, the present invention discloses a multi-server system which includes a user device that is configured to transmit a user identifier, and a server which is communicatively coupled with the user device and includes a

memory and a processor. The processor may be configured to generate a primary user address by appending the user identifier to a primary user handle. Subsequently, the server may be configured to perform a search for a first set of user addresses stored in the primary database connected to the server and determine if any user address of the first set of user addresses matches with the primary user address. Upon successful match, the server retrieves a matching user address and corresponding matching user name from the primary database and transmits the matching user address and the matching user name to the user device.
[0029] In another implementation, the present invention discloses a computer implemented method of searching for user addresses in a multi-server system. The computer implemented method includes a step executed by a processor coupled with the server which is directed towards extracting a plurality of handles stored in a memory coupled with the server. Further, the method includes a step executed by the processor for generating a plurality of user addresses by appending the user identifier to each of the plurality of handles and generating a plurality of threads corresponding to the plurality of user addresses. Further, the method includes a step of generating and transmitting a plurality of search requests through the plurality of threads to a formal server, wherein each thread of the plurality of threads generates a unique search request corresponding to one of the plurality of user addresses and transmits the search request to the formal server. The method further includes a step executed at the formal server which is directed towards redirecting one of the plurality of threads to a secondary database associated with a secondary server. Further, the method includes a step executed at the server through said thread which is directed towards receiving a registered user name and a registered user address corresponding to the user identifier from the secondary database through the formal server. Upon receiving the user name and registered user address from said secondary database, the method includes a step of suspending remaining threads of the plurality of threads. To this end, the method includes a step of storing the registered user name and the registered user address in a primary database and

transmitting the registered user name and the registered user address to the user device.
[0030] In another implementation, the method includes a step executed by the processor which is directed towards generating a primary user address by appending the user identifier to a primary user handle. Further, the method includes a step executed at the server which is directed towards searching a first set of user addresses stored in the primary database connected to the server, and to determine if any user address of the first set of user addresses matches with the primary user address. To this end, the method includes a step executed at the server which is directed towards retrieving a matching user address and corresponding matching user name from the primary database and transmitting the matching user address and the matching user name to the user device.
[0031] In the present implementation, the registered user address may be a virtual payment address (VPA) corresponding to the user identifier, wherein the user identifier may be a mobile number registered in the name of the registered user.
[0032] It should be noted that the description merely illustrates the principles of the present invention. It will thus be appreciated that those skilled in the art will be able to devise various arrangements that, although not explicitly described herein, embody the principles of the present invention. Furthermore, all examples recited herein are principally intended expressly to be only for explanatory purposes to help the reader in understanding the principles of the invention and the concepts contributed by the inventor to furthering the art, and are to be construed as being without limitation to such specifically recited examples and conditions. Moreover, all statements herein reciting principles, aspects, and embodiments of the invention, as well as specific examples thereof, are intended to encompass equivalents thereof.
[0033] Figure 1 illustrates a schematic diagram of a multi-server system (100) in accordance with an embodiment of the present invention. The multi-server system (100) includes a plurality of user devices (102) including first and second user devices (102a and 102b), a server (104), a primary database (106), a formal server

(108), and a plurality of secondary databases (110) including first through third secondary databases (110a-110c). The plurality of secondary databases (110) may be connected to a plurality of secondary servers (not shown in Figure 2).
[0034] In the present implementation, the primary database (106) may be implemented as enterprise database, remote database, local database, and the like. The primary database (106) may be located within the vicinity of the multi-server system (100) or may be located at different geographic locations as compared to that of the multi-server system (100). Further, the primary database (106) may be implemented inside the multi-server system (100) and the primary database (106) may be implemented as a single database.
[0035] Figure 2 illustrates a schematic block diagram (200) of the multi-server system (100) of Figure 1. The user device (102) is connected to the server (104). The user device may be connected to the server (104) by wired or wireless connections. Examples of connections between the user device (102) and the server (104) include Long-Term Evolution (LTE), LTE Advanced (LTE-A), High-Speed Downlink Packet Access (HSDPA), Global System for Mobile (GSM), General Packet Radio Service (GPRS), Enhanced Data rates for GSM Evolution (EDGE), Wi-Fi, etc. Examples of the user device (102) include mobile phones, smart phones, etc. The user device (102) may operate on various mobile operating systems, such as, but not limited to, Android® or iOS®. The user device (102) is associated with a user that uses the user device (102).
[0036] The user device (102) includes a processor (202), a memory (204), and an input/output (I/O) unit (206). The processor (202), the memory (204), and the I/O unit (206) are interconnected (interconnections not shown in Figure 2). The I/O unit (206) includes input devices such as a touchscreen or a tactile button, output devices such as a display, and input/output components such as an antenna.
[0037] The server (104) is connected to the user device (102) and the primary database (106). The server (104) includes a processor (208), a memory (210), and

an I/O unit (212). The processor (208), the memory (210), and the I/O unit (212) are interconnected (interconnections not shown in Figure 2).
[0038] In the present implementation, the processor(s) (202, 208, 220) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the at least one processor (208) is configured to fetch and execute computer-readable instructions stored in the memory (210).
[0039] In the present implementation, the memory (210) may be coupled to the processor (208). The memory (210) can include any computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes. The memory (210) also includes a cache memory to work with the server (104) more effectively. The cache memory may be updated regularly with the results identified by the server (104) with the help of the formal server (108) and the plurality of secondary databases (110a-110c).
[0040] In the present implementation, the I/O units or interface(s) (206, 212, 224, 230) may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like. For example, in one of the I/O unit (212) may allow the server (104) to interact with a user directly or through the user devices (102a, 102b). Further, the I/O unit (212) may enable the server (104) to communicate with other user devices or computing devices, such as the formal server (108), web servers (not shown) and external data servers (not shown). The I/O unit (212) can facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, LAN, cable, etc., and wireless networks, such as WLAN, cellular, or satellite. The I/O unit (212)

may include one or more ports for connecting a number of devices to one another or to another server.
[0041] The primary database (106) is directly connected to the server (104). The primary database (106) stores registered user names (214), registered user addresses (216), and registered user identifiers (218).
[0042] In an exemplary embodiment, each registered user identifier of the registered user identifiers (218) uniquely corresponds to one of the registered user addresses (216) and one of the registered user names (214).
[0043] The server (104) is further connected to the formal server (108). The formal server (108) includes a processor (220), a memory (222), and an I/O unit (224). The processor (220), the memory (222), and the I/O unit (224) are interconnected (interconnections not shown in Figure 2).
[0044] The formal server (108) is connected to the plurality of secondary databases (110) through the connected through the plurality of secondary servers (not shown in Figure 2). The secondary server includes a processor, a memory, and an I/O unit. The processor, the memory, and the I/O unit are interconnected (interconnections not shown in Figure 2).
[0045] Each of the plurality of secondary servers is further connected to corresponding secondary database (110). The secondary database stores registered user names (226), registered user addresses (228), and registered user identifiers (230).
[0046] In an exemplary embodiment, each registered user identifier of the registered user identifiers (230) uniquely corresponds to one of the registered user addresses (228) and one of the registered user names (226).
[0047] Examples of the registered user identifiers (218) and the registered user identifiers (230) include, but are not limited to, numeric or alpha-numeric values such as a contact number of the user or a mobile number registered in the name of

the registered user. Examples of the registered user names (214) and the registered user names (226) include first name, initials, or last names of the user.
[0048] The registered user addresses (216) and the registered user addresses (228) are digital addresses for contacting the users, for example, the registered user addresses (216) and the registered user addresses (228) provide unique addresses to digitally contact the users over the internet. Examples of the registered user addresses (216) and the registered user addresses (228) include “abc@xyz”, “abc123@xyz” or “123@xyz”. Each registered user address is composed of a prefix, such as “abc”, “abc123” or “123” and a handle such as “xyz”. In an exemplary embodiment, the handle denotes a service provider that provides said user address to the user. In an example, the registered user address may be a virtual payment address (VPA) of the user at a service provider denoted by the handle of the user address.
[0049] In a preferred embodiment, the server (104) generates all possible handles for all possible service providers and stores said handles in the memory (210). The server (104) may, on timely basis, update the handles stored in the memory (210). The server (104) may modify delete, add, or alter the handles stored in the memory (210) based on change in the service providers.
[0050] Figure 3 illustrates a schematic diagram (300) of functioning of the multi-server system (100) in accordance with an embodiment of the present invention. The functioning of the Figure 3 is described below with help from the Figure 1 and the Figure 2. In many places, the reference numerals which are part of the Figure 1 and the Figure 2 are provided along with the reference numerals of the Figure 3. This indicates the interworking of the structural features which are required to execute the function as provided in Figure 3.
[0051] At step 1, the user device (102) transmits a user identifier to the server (104). In an example, when a first user of the first user device (102a) wishes to initiate an electronic transaction with a second user of the second user device (102b), the first user device (102a) transmits a user identifier of the second user

device (102b) to the server (104) in order to search for the registered user address of the second user. Here, examples of the user identifier of the second user device (102b) include a contact number or a mobile number of the second user.
[0052] At step 2, the server (104) receives the user identifier from the user device (102) and searches the registered user identifiers (218) stored in the primary database (106) to determine if any registered user identifier of the registered user identifiers (218) matches with the received user identifier.
[0053] If the server (104) determines that any registered user identifier of the registered user identifiers (218) matches with the received user identifier, the server (104), at step 3, retrieves a registered user name of the registered user names (214) that uniquely corresponds to the matching registered user identifier. The server (104) also retrieves, at step 3, a registered user address of the registered user addresses (216) that uniquely corresponds to the matching registered user identifier. Thereafter, the server (104) transmits the matching registered user identifier, corresponding registered user name, and corresponding registered user address to the user device (102). The user device (102) receives the matching registered user identifier, corresponding registered user name, and corresponding registered user address and displays the matching registered user identifier, corresponding registered user name, and corresponding registered user address to the user by way of I/O unit (206).
[0054] However, if the server (104) determines that none of the registered user identifiers (218) matches with the received user identifier, the server (104) retrieves the handles stored in the memory (210) and generates multiple user addresses by appending the received user identifier with each handle. Thereafter, the server (104) creates multiple threads, such that each thread dedicated to search for one of the generated user addresses. The server (104) generates multiple search requests by way of the threads, such that each search request is for searching one of the generated user addresses.

[0055] At step 4, the server (104) transmits said search requests to the formal server (108).
[0056] At step 5, the formal server (108) receives the search requests through multiple threads and redirects the threads to multiple secondary servers such that each thread is redirected to a different secondary database (110).
[0057] At step 6, the secondary server receives the search request and searches the secondary database (110) to determine if any of the registered user addresses (228) matches with the user address corresponding to the search request.
[0058] If the secondary server determines that any registered user address of the registered user addresses (228) matches with the user address corresponding to the search request, the secondary server, at step 7, retrieves a registered user name of the registered user names (226) that uniquely corresponds to the user address. The secondary server (110) also retrieves, at step 7, a registered user identifier of the registered user identifiers (230) that uniquely corresponds to the user address.
[0059] At step 8, the secondary server transmits the registered user name and the registered user identifier corresponding to the user address which corresponds to the search request to the formal server (108).
[0060] At step 9, the formal server (108) receives the registered user name and the registered user identifier and relays the registered user name and the registered user identifier to the server (104).
[0061] At step 10, the server (104) receives the registered user name and the registered user identifier and suspends the remaining threads. The server (104) also stores the registered user name and the registered user identifier in the primary database (106), thereby updating the primary database with the registered user name and the registered user address corresponding to the received user identifier.
[0062] At step 11, the server (104) transmits the registered user name and the registered user address corresponding to the received user identifier to user device

(102). Thereafter, the user device (102) receives the registered user name and the registered user address corresponding to the user identifier and displays the registered user name, the registered user address, and the user identifier to the user of the user device (102) by way of I/O unit (206).
[0063] Figure 4 illustrates a timing sequence diagram (400) of functioning of the multi-server system (100) in accordance with an embodiment of the present invention. The Figure 4 can be described with the help of the Figure 3 wherein the Figure 3 has been described in abovementioned paragraphs with the details of each steps. The time sequence diagram merely discloses a time interval at which the steps of the Figure 3 have been executed.
[0064] Figures 5A-5D illustrates a flowchart (500) depicting a process flow of the multi-server system (100), according to an exemplary implementation of the present invention.
[0065] Figure 5A, Step (502) discloses a step executed at a server which includes receiving a user identifier from a user device.
[0066] Step (504) discloses a step executed by a processor which is communicatively coupled with the server which includes extracting a plurality of handles stored in a memory coupled with the server.
[0067] Step (506) discloses a step executed by the processor which includes generating a plurality of user addresses by appending the user identifier to each of the plurality of handles.
[0068] Step (508) discloses a step executed by the processor which includes searching a user address in a primary database.
[0069] Step (510) discloses a step which includes if the search operation of step (508) is positive, then proceed to step (520) (depicted in Figure 5B) which is directed towards retrieving a user address and user name from the primary database and directed to step (528). Step (528) (depicted in Figure 5D) discloses a step

executed by the processor which includes displaying the user identifier, the user address, and the user name on the user device. However, if the search operation of step (508) is negative, then proceed to step (512).
[0070] Step (512) discloses a step executed by the processor which includes generating a plurality of threads corresponding to the plurality of user addresses.
[0071] Step (514) discloses a step executed by the processor which includes generating and transmitting a plurality of search requests through the plurality of threads to a formal server, wherein each thread of the plurality of threads generates a unique search request corresponding to one of the plurality of user addresses and transmits the search request to the formal server.
[0072] Step (516) discloses a step executed at the formal server which includes redirecting one of the plurality of threads to a secondary database associated with a secondary server.
[0073] Step (518) discloses a step executed at the server, through the thread, which includes receiving a registered user name and a registered user address corresponding to the user identifier from the secondary database through the formal server.
[0074] Figure 5B, step (522) discloses a step which includes suspending remaining threads of the plurality of threads after receiving the registered user name and the registered user address from the secondary database.
[0075] Step (524) discloses a step executed by the processor which includes storing the registered user name and the registered user address in a primary database and transmitting the registered user name and the registered user address to the user device.
[0076] Figure 5D, step (528) discloses a step executed by the processor which includes displaying the user identifier, the user address, and the user name on the user device.

[0077] It should be noted that the description merely illustrates the principles of the present invention. It will thus be appreciated that those skilled in the art will be able to devise various arrangements that, although not explicitly described herein, embody the principles of the present invention. Furthermore, all examples recited herein are principally intended expressly to be only for explanatory purposes to help the reader in understanding the principles of the invention and the concepts contributed by the inventor to furthering the art, and are to be construed as being without limitation to such specifically recited examples and conditions. Moreover, all statements herein reciting principles, aspects, and embodiments of the invention, as well as specific examples thereof, are intended to encompass equivalents thereof.

We claim:
1. A computer implemented method of searching for user addresses in a multi-
server system, the method comprising:
receiving, at a server, a user identifier from a user device;
extracting, by a processor coupled with the server, a plurality of handles stored in a memory coupled with the server;
generating, by the processor, a plurality of user addresses by appending the user identifier to each of the plurality of handles;
generating, by the processor, a plurality of threads corresponding to the plurality of user addresses;
generating and transmitting a plurality of search requests through the plurality of threads to a formal server, wherein each thread of the plurality of threads generates a unique search request corresponding to one of the plurality of user addresses and transmits the search request to the formal server;
redirecting, by the formal server, one of the plurality of threads to a secondary database associated with a secondary server;
receiving, at the server through said thread, a registered user name and a registered user address corresponding to the user identifier from the secondary database through the formal server;
suspending remaining threads of the plurality of threads after receiving the registered user name and the registered user address from said secondary database;
storing the registered user name and the registered user address in a primary database; and
transmitting the registered user name and the registered user address to the user device.
2. The method as claimed in claim 1, further comprising:
generating, by the processor, a primary user address by appending the user identifier to a primary user handle;

searching, by the server, a first set of user addresses stored in the primary database connected to the server, to determine if any user address of the first set of user addresses matches with the primary user address;
retrieving, by the server, a matching user address and corresponding matching user name from the primary database; and
transmitting, by the server, the matching user address and the matching user name to the user device.
3. The method as claimed in claim 2, wherein the primary database stores the first set of user addresses, a first set of user identifiers, a first set of user names, and wherein each user address uniquely corresponds to one of the first set of user identifiers, and wherein each user address uniquely corresponds to one of the first set of user names.
4. The method as claimed in claim 1, wherein the secondary database stores a secondary set of user addresses, a second set of user identifiers, a second set of user names, and wherein each user address uniquely corresponds to one of the second set of user identifiers, and wherein each user address uniquely corresponds to one of the second set of user names.
5. The method as claimed in claim 1, further comprising receiving, at the server from the formal server by way of the plurality of threads, a plurality of redirection instructions corresponding to a plurality of secondary servers, wherein each thread of the plurality of threads is directed to one of the plurality of secondary databases based on corresponding redirection instruction.
6. The method as claimed in claim 1, wherein the registered user address is a virtual payment address corresponding to the user identifier.
7. A multi-server system for searching user addresses, the system comprising:
a user device configured to transmit a user identifier; and
a server in communication with the user device, said server comprising:
a memory storing a plurality of handles;
a processor, coupled with the memory, said processor configured
to:

receive the user identifier,
extract the plurality of handles from the memory,
generate a plurality of user addresses by appending the user identifier to each of the plurality of handles,
generate a plurality of threads corresponding to the plurality of user addresses,
generate and transmit a plurality of search requests through the plurality of threads to a formal server, wherein each thread of the plurality of threads generates a unique search request corresponding to one of the plurality of user addresses and transmits the search request to the formal server,
redirect, by the formal server, one of the plurality of threads to a secondary database associated with a secondary server,
receive, through said thread, a registered user name and a registered user address corresponding to the user identifier from the secondary database through the formal server,
suspend remaining threads of the plurality of threads after receiving the registered user name and the registered user address from said secondary database,
store the registered user name and the registered user address in a primary database, and
transmit the registered user name and the registered user address to the user device.
8. The system as claimed in claim 7, wherein the processor is further configured to:
generate a primary user address by appending the user identifier to a primary user handle,
search a first set of user addresses stored in the primary database connected to the server, to determine if any user address of the first set of user addresses matches with the primary user address,

retrieve a matching user address and corresponding matching user name from the primary database, and
transmit the matching user address and the matching user name to the user device.
9. The system as claimed in claim 8, wherein the primary database stores the first set of user addresses, a first set of user identifiers, a first set of user names, and wherein each user address uniquely corresponds to one of the first set of user identifiers, and wherein each user address uniquely corresponds to one of the first set of user names.
10. The system as claimed in claim 7, wherein the secondary database stores a secondary set of user addresses, a second set of user identifiers, a second set of user names, and wherein each user address uniquely corresponds to one of the second set of user identifiers, and wherein each user address uniquely corresponds to one of the second set of user names.
11. The system as claimed in claim 7, wherein the processor is further configured to receive, from the formal server by way of the plurality of threads, a plurality of redirection instructions corresponding to a plurality of secondary servers, wherein each thread of the plurality of threads is directed to one of the plurality of secondary databases based on corresponding redirection instruction.