CA2983517A1

CA2983517A1 - Systems and methods for creating events and connecting users based on common liked events

Info

Publication number: CA2983517A1
Application number: CA2983517A
Authority: CA
Inventors: Vikram Bhatia
Original assignee: Go Pb&j Corp
Current assignee: Go Pb&j Corp
Priority date: 2017-10-23
Filing date: 2017-10-23
Publication date: 2019-04-23

Abstract

A technique is provided for connecting a plurality of users based on common liked events. The technique includes determining events of interest from pre-stored events based on attributes associated with a first registered user. A selection input from the first user for selecting an event from the determined events is received. Further, one or more users having selected the same event as the event selected by the first user is determined, arranged, and displayed in a sequential manner according to a correlation between a preference index of the first user and a preference index of the one or more users. A request from the first user for connecting with the second user is received. A connection corresponding to the request is established upon acceptance of the request of the first user, by the second user.

Description

SYSTEMS AND METHODS FOR CREATING EVENTS AND CONNECTING USERS
BASED ON COMMON LIKED EVENTS
TECHNICAL FIELD
[0001] This disclosure relates generally to connecting users based on events, and more particularly to system and method for creating events and connecting users based on their preferred events.
BACKGROUND

[0002] Advancement in the field of digital matchmaking has led to development of various technologies and algorithms that make use of personal preferences of the people being matched. Such personal preferences consider a number of personal attributes. For example, conventional methods of matchmaking make use of personal attributes such as professional qualifications, hobbies, interests, dislikes, ethnicity, religion, political affiliations, etc. The information pertaining to the aforementioned personal preferences may be derived from the profiles of the users present on social media platforms.

[0003] However, being limited to only personality traits, matchmaking based on such methods tends to be superficial without accounting for the deepest and even subconscious traits of the candidates. As a result, the matched personas may not be fully compatible leading to relationships that are short lived and turbulent.

[0004] Therefore, there exists a need to provide a system and/or method that performs matchmaking based on preferences that are authentic reflection of a person's characteristics along with the personality. Matches based on such preferences when used for matchmaking can help forge long lasting and better relationships.
SUMMARY

[0005] In one embodiment, a method of connecting a plurality of users based on common liked events is disclosed. In an example embodiment, the method includes determining, by a matchmaking engine, one or more events of interest from a plurality of pre-stored events based on one or more attributes associated with a first registered user. The method further includes receiving, by the matchmaking engine, a selection input from the first user for selecting an event from the determined one or more events of interest. The method further includes determining, by the matchmaking engine, one or more users having selected the same event as the event selected by the first user.
The one or more users having selected the same event may be arranged and displayed in a sequential manner according to a correlation between a preference index of the first user and a preference index of the one or more users. The method further includes receiving, by the matchmaking engine, a request from the first user for connecting with a second user from the determined one or more users. The method further includes establishing, by the matchmaking engine, a connection between the first user and the second user upon acceptance of the request of the first user by the second user.

[0006] In another embodiment, a system for connecting a plurality of users based on common liked events is disclosed. The system includes a plurality of user devices, and a server system comprising one or more processors and one or more storage memories communicatively coupled to the one or more processors. The one or more memories store processor-executable instructions, which, on execution, cause the one or more processors to determine one or more events of interest from a plurality of pre-stored events based on one or more attributes associated with a first registered user. The one or more events of interest may be displayed on the user device associated with the first user. The processor-executable instructions, upon execution, further cause the one or more processors to receive a selection input from the user device of the first user for selecting an event from the determined one or more events of interest. The processor-executable instructions, upon execution, further causing the one or more processors to determine one or more users having selected the same event as the event selected by the first user. The one or more users having selected the same event may be arranged and displayed in a sequential manner according to a correlation between a preference index of the first user and a preference index of the one or more users. The processor-executable instructions, upon execution, further cause the one or more processors to receive a request from the first user for connecting with a second user from the determined one or more users. The processor-executable instructions, upon execution, further cause the processors to establish a connection between the first user and the second user upon acceptance of the request of the first user by the second user.
[00071In yet another embodiment, a non-transitory computer-readable medium storing computer-executable instructions for connecting a plurality of users based on common liked events is disclosed. The computer-executable instructions, when executed by one or more processors, cause the processor to perform operations comprising determining one or more events of interest from a plurality of pre-stored events based on one or more attributes associated with a first registered user. The operations further include receiving a selection input from the first user for selecting an event from the determined one or more events of interest. The operations further include determining one or more users having selected the same event as the event selected by the first user. The one or more users having selected the same event may be arranged and displayed in a sequential manner according to a correlation between a preference index of the first user and a food index of the one or more users.
The operations further includes receiving a request from the first user for connecting with a second user from the determined one or more users. The operations further include establishing a connection between the first user and the second user upon acceptance of the request of the first user by the second user.
[0008] In yet another embodiment, a method for creating one or more events for connecting a plurality of users is disclosed. In one example, the method includes, presenting, by a matchmaking engine, one or more user interface (user interface) objects to a plurality of contributors for creating one or more events. The one or more user interface objects include a user interface object for storing, in a database associated with the matchmaking engine, one or more attributes of an event.
The method further includes receiving, by a matchmaking engine, based on the presented one or more user interface objects, one or more inputs from the contributors for creating a prototype screen related to the one or more events. The method further includes verifying and storing , by the matchmaking engine, the prototype screen in the database to be displayed on user devices of the one or more users based on which a connection is established between one or more users.
[0009] In yet another embodiment, a system for creating one or more events for connecting a plurality of users is disclosed. The system includes a plurality of user devices, and a server system comprising one or more processors and one or more storage memories communicatively coupled to the one or more processors. The one or more memories store processor-executable instructions, which, on execution, cause the one or more processors to present one or more user interface (user interface) objects to a plurality of contributors for creating one or more events. The one or more user interface objects comprise one or more of a user interface object for storing, in a database associated with the matchmaking engine, one or more attributes of an event.
The processor-executable instructions, upon execution, further cause the one or more processors to receive, based on the presented one or more user interface objects, one or more inputs from the contributors for creating a prototype screen related to the one or more events. The processor-executable instructions, upon execution, further causing the one or more processors to verify an identity of the user. The processor-executable instructions, upon execution, further cause the one or more processors to store, based on the verification, the prototype screen in the database to be displayed on user devices of the one or more users, based on which a connection is established between one or more users.
[0010] In yet another embodiment, a non-transitory computer-readable medium storing computer-executable instructions for creating one or more events for connecting a plurality of users is disclosed. The computer-executable instructions, when executed by one or more processors, cause the processor to perform operations comprising to presenting one or more user interface (user interface) objects to a plurality of contributors for creating one or more events. The one or more user interface objects comprise one or more of a user interface object for storing, in a database associated with the matchmaking engine, one or more attributes of an event. The operations further include receiving, based on the presented one or more user interface objects, one or more inputs from the contributors for creating a prototype screen related to the one or more events. The operations further include verifying an identity of the user.
The operations further include storing, based on the verification, the prototype screen in the database to be displayed on user devices of the one or more users, based on which a connection is established between one or more users.
[0011] It is to be understood that both the foregoing general description and the following detailed description are example and explanatory only and are not restrictive of the invention, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS
[0012] The accompanying drawings, Which are incorporated in and constitute a part of this disclosure, illustrate example embodiments and, together with the description, serve to explain the disclosed principles.
[0013] FIG. 1 is a block diagram of a network environment for connecting a plurality of users based on common liked events, in accordance with one or more example embodiments of the present disclosure.
[0014] FIG. 2 is a block diagram of a system for connecting a plurality of users based on common liked events, in accordance with one or more example embodiments of the present disclosure.
[0015] FIG. 3 illustrates a user interface for creating one or more events for connecting a plurality of users based on common liked events, in accordance with one or more example embodiments of the present disclosure.
[0016] FIGs. 4A and 4B collectively illustrate user interfaces for connecting a plurality of users based on common liked events, in accordance with one or more example embodiments of the present disclosure.
[0017] FIG. 5 is a flow diagram of a process for connecting a plurality of users based on common liked events, in accordance with one or more example embodiments of the present disclosure.

7 [0018] FIG. 6 is a flow diagram of a process for creating one or more events for connecting a plurality of users based on common liked events, in accordance with one or more example embodiments of the present disclosure.

8 DETAILED DESCRIPTION
[0019] Example embodiments are described with reference to the accompanying drawings. Wherever convenient, the same reference numbers are used throughout the drawings to refer to the same or like parts. While examples and features of disclosed principles are described herein, modifications, adaptations, and other implementations are possible without departing from the spirit and scope of the disclosed embodiments. It is intended that the following detailed description be considered as an example only, with the true scope and spirit being indicated by the following claims.
[0020] Some embodiments of this disclosure, illustrating all its features, will now be discussed in detail. The words "comprising," "having," "containing," and "including,"
and other forms thereof, are intended to be equivalent in meaning and be open ended in that an item or items following any one of these words is not meant to be an exhaustive listing of such item or items, or meant to be limited to only the listed item or items.
[0021] It must also be noted that as used herein and in the appended claims, the singular forms "a," "an," and "the" include plural references unless the context clearly dictates otherwise. Although any systems and methods similar or equivalent to those described herein can be used in the practice or testing of embodiments of the present disclosure, the preferred, systems and methods are now described.
[0022] FIG. 1 illustrates a block diagram of a network environment for connecting a plurality of users based on common liked events, according to one or more example embodiments. In an embodiment, the network environment 100 may include a

9 first user (hereinafter user 102) that may intend to find a match based on common liked event. In an aspect, the event as mentioned throughout the present disclosure may be an event such as a food related event, a music concert, or any other activity where a two or more people may participate. The present disclosure for convenience purpose describes a food related event, however, such an event has been discussed merely as an example and by no means intends to restrain the various embodiments as described herein to a food related event only.
[0023] The network environment 100 may further include one or more instances of an electronic device 104 that may be associated with the user 102. The network environment 100 may further include an event database 106, a plurality of data contributors 108, a matchmaking engine 110, and/or a plurality of registered users 112.
In an implementation, the electronic device 104, the event database 106, the matchmaking engine 110, and/or a second user from the plurality of registered users 112, may be communicatively coupled via a communication network 114. In an implementation, the plurality of data contributors may include 1081, 1082_108, which may utilize a plurality of electronic devices that enable the data contributors to be communicatively couple with the event database 106 and the matchmaking engine 110.
In an implementation, the second user may correspond to any of the registered users 1121, 1122,...112,, from the plurality of users 112. The registration of the plurality of registered users 112 may be based on one or more attributes provided by the individual users at the time of registration.
[0024] In an aspect, the electronic device 104 may correspond to one or more of a Personal Digital Assistant (FDA), a Smartphone, a laptop, a desktop, and/or any other device that may receive one or more inputs from the user 102 for finding a suitable match.
[0025] The event database 106 may include a medium for storing a plurality of events. The event database 106 may be created based on one or more inputs received from the plurality of data contributors 108. For example in case of a food related event, the details may include but are not limited to, information such as a location of an event and/or one or more attributes associated with the food items available at the location. In an implementation, the event database 106 may be a structured database or an unstructured database that may be implemented in a cloud environment. In another implementation, the event database 106 may be implemented based on Block chain technology. Examples of the event database 106 may include, but are not limited to, SQL Server , Oracle Database , SybaseTM, Informix , and MySQLO, and the like.
In an implementation, the event database 106 may be an entity remote to the matchmaking engine 110, such that the matchmaking engine 110 and the event database 106 may be separate entities hosted in a cloud environment. In another implementation, the event database 106 may be a network entity that may be integrated locally with the matchmaking engine 110.
[0026] The matchmaking engine 110 may include suitable logic, circuitry, and/or interfaces for connecting the user 102 with one or more users from the plurality of registered users 112 based on common liked events from the plurality of pre-stored events. Based on the one or more attributes associated with the user 102, the matchmaking engine 110 may determine one or more events of interest to the user 102 from the events database 106. The matchmaking engine 110 may further establish a connection between the user 102 and a user from the plurality of registered users 112 based on a degree of similarity between the food tastes of the aforementioned users. In an implementation, the matchmaking engine 110 may be based on cloud based services known in the art. In another implementation, the matchmaking engine 110 may be a remotely processing server that performs the aforementioned operations.
Such server may be implemented based on technologies that include, but are not limited to, ApacheTM HTTP Server, Microsoft Internet Information Services (IIS), IBM
Application Server, Sun JavaTM System Web Server, and/or a file server.
[0027] The communication network 114 may include a medium through which the electronic device 104, the event database 106, the plurality of contributors 108, the matchmaking engine 110, and/or the plurality of registered user 112, may be communicatively coupled via a communication network 114, may communicate with each other. Examples of the communication network 114 may include, but are not limited to, the Internet, a cloud network, a Wireless Fidelity (Wi-Fi) network, a Wireless Local Area Network (WLAN), a Local Area Network (LAN), a telephone line (POTS), and/or a Metropolitan Area Network (MAN). Various devices in the network environment 100 may be operable to connect to the communication network 114, in accordance with various wired and wireless communication protocols. Examples of such wired and wireless communication protocols may include, but are not limited to, Transmission Control Protocol and Internet Protocol (TCP/IP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), File Transfer Protocol (FTP), Zigbee, EDGE, infrared (IR), IEEE 802.11, 802.16, cellular communication protocols, and/or Bluetooth (BT) communication protocols [0028] In operation, when the user 102 initiates the method by using the device 104 for finding relevant matching users amongst the plurality of users 112, the matchmaking engine 110 may determine one or more events of interest from a plurality of pre-stored events stored in the events database 106. The determination of the one or more events of interest may be based on based on one or more attributes associated with the user 102. In an example embodiment, the one or more attributes include one or more of a location of the user 102, one or more cuisines preferred by the user 102, a gender of the user 102, sexual orientation of the user 102, a historical record of one or more inputs provided by the user 102 with respect to one or more users 112, information associated with one or more social networking profiles of the user 102. The one or more attributes may be determined either at the time of registering a user (such as the user 102) with the matchmaking engine 110 or at the time of initiating the method via device 104. For example, the general information of the user such as the gender of the user may be provided by the user 102 at the time of registration with the matchmaking engine 110 and the present location of the user 102 may be provided at the time of initiating the method via device 104. A person of ordinary skill in the art will appreciate that the one or more attributes of each of the plurality of registered users 112 may also be received by the matchmaking engine at the time of registering the users.
[0029] In an example embodiment, the plurality of events may be pre-stored in an event database 106 based on one or more data inputs fetched from a plurality of data contributors 108. The plurality of data contributors 108 may include, but are not limited to, electronic devices of one or more of users registered with the matchmaking engine 110, electronic devices of owners of restaurants, or social media data feeds of data contributors 108.
[0030] In an example embodiment, the matchmaking engine 110 may facilitate creation of the plurality of events. The matchmaking engine 110 may present one or more user interface (user interface) objects to the plurality of contributors 108 to enable them to create one or more events. In an example embodiment, the one or more user interface objects include a user interface object for storing (in the event database 106), one or more attributes of food items associated with an event when a name of a location of the event is pre-stored in the event database 106. In an example embodiment, when the name of the location of the event is not pre-stored, the one or more user interface objects may include a first user interface object for storing one or more attributes of a location of the event, and a second user interface object for storing the one or more attributes of food items associated with the location of the event. In an aspect, the location information of the event may be fetched by using a Google MapsTM
application programming interface. A person of ordinary skill in the art will appreciate the name of the location of the name of a location of the event may be stored in a dedicated memory integrated with the matchmaking engine 110.
[0031] Based on the presented user interface objects, the matchmaking engine 110 may further receive one or more inputs from one or more data contributors of the plurality of contributors 108. The matchmaking engine 110 may further create one or more prototype screens of the one or more events based on the received one or more inputs. The created one or more events may be used for establishing connections among the user 102 and one or more users from the plurality of registered users 112.

The matchmaking engine 110 may further verify the identity of the contributor from which the inputs are received. Based on the verification, the matchmaking engine 110 may store the prototype screen in the event database 106. The prototype screen may then be displayed on electronic devices of the plurality of users 112.
[0032] In an example embodiment, the matchmaking engine 110 may receive a selection input from the user 102 for selecting an event from the determined one or more events of interest. The matchmaking engine 110 may determine one or more users having selected the same event as the event selected by the first user 102. Such one or more users may correspond to a set of users (for example user 1121, 1123, 1124) from the plurality of registered users 112. The one or more users having selected the same event may be arranged and displayed in a sequential manner on the electronic device 104. The determination and arrangement of the one or more users may be in accordance with a correlation between a preference index of the first user and a preference index of the one or more users. In an example embodiment, the preference index may be determined based on weighted analysis of the one or more attributes associated with the user 102. The weighted analysis may be based on a plurality of configurable weights assigned to each attribute of the one or more attributes.
It may also be noted that the preference index may be created by means of using an artificial intelligence routine such as IBM WatsonTM.
[0033] In an example embodiment, the determination of the one or more users associated with the selected event of interest may be further based on determination of a degree of similarity between the preference index of the user 102 with that of each of the plurality of registered users 112. For example, the one or more user may be =
determined when the determined similarity score of the user 102 and the one or more users is greater than a pre-defined threshold.
[0034] In an example embodiment, the matchmaking engine 110 may receive a request from the first user 102 (via the electronic device 104) for connecting with a second user from the determined one or more users. In an example embodiment, the matchmaking engine 110 may generate a notification corresponding to the request.
The notification may be rendered on the electronic device 104 associated with the second user. The matchmaking engine 110 may establish a connection between the first user 102 and the second user 112. The connection may be established based on acceptance of the request of the first user 102 by the second user. In an example embodiment, the established connection facilitates exchange of one or more messages between the first user 102 and the second user 112.
[0035] In an example embodiment, the matchmaking engine 110 may receive a confirmation input indicative of physical meeting between the first user 102 and the second user. The confirmation input may be provided by both the first user and the second user. Further, based upon the verification of the geo-spatial coordinates with respect to a location of the selected event of interest, the matchmaking engine 110 may provide discount to the users at the selected event of interest.
[0036] In an example embodiment, the matchmaking engine 110 may further include determining one or more metrics such as number of viewers of a particular event from the plurality of pre-stored events, number of likes or selections of a particular event, total number of connections established between one or more users for a particular event, total number of check-in made at an event, and the like. A
person of ordinary skill in the art will appreciate that aforementioned metrics (such as the number of connections established for particular event) may highlight details such as the food preferred at a particular venue and/or food preferred by users (user 102 and the plurality of users 112) in a geographical region.
[0037] In an example embodiment, the check-in at an event is performed when the matchmaking engine 110 receives geo-spatial coordinates of a user (such as the user 102) from the electronic device 104. Further, upon the receipt of the geo-spatial coordinates, the matchmaking engine 110 may render one or more discounts to the users on their respective associated user devices.
[0038] A person of ordinary skill in the art will appreciate that the matchmaking engine 110 may be further communicatively coupled to one or more cloud based services to create databases of at least the registered users, the pre-defined plurality of events, or relational mapping between the users with each other. The matchmaking engine 110 may further store a plurality of images in the memory based on one or more routines for image compression such as AWS LambdaTM and Amazon S3TM. In an example embodiment, the matchmaking engine 110 may further resize the stored one or more images according to specific resolution of an electronic device associated with a registered user.
[0039] As will be appreciated by one skilled in the art, a variety of processes may be employed for transmitting data over a communication network. For example, the network environment 100 may transmit data over a communication network by the processes discussed herein. In particular, as will be appreciated by those of ordinary skill in the art, control logic and/or automated routines for performing the techniques and steps described herein may be implemented by the network environment 100, either by hardware, software, or combinations of hardware and software. For example, suitable code may be accessed and executed by the one or more processors on the network environment 100 to perform some or all of the techniques described herein.
Similarly, application specific integrated circuits (ASICs) configured to perform some or all of the processes described herein may be included in the one or more processors on the network environment 100.
[0040] FIG. 2 is a block diagram of an example system for connecting a plurality of users based on common liked events, in accordance with some embodiments of the present disclosure. FIG. 2 is explained in conjunction with elements from FIG.
1. With reference to FIG. 2, there is shown the matchmaking engine 110 that may include one or more processors, such as a processor 202, a memory 204, a matchmaking module 206, a machine learning module 208, an input/output (I/O) module 210, and/or a transceiver 212. The memory 204 may include at least an event database 214 and/or a user database 216. The processor 202 may be communicatively coupled to the memory 204, the matchmaking module 206, the machine learning module 208, the Input/Output module 210, and/or the transceiver 212.
[0041] The processor 202 may include suitable logic, circuitry, interfaces, and/or code that may be configured to execute a set of instructions stored in the memory 204.
The processor 202 may be configured to register the plurality of users at respective community clubs. The processor 202 may further track the activities of the community club members and may facilitate selective sharing of data among the plurality of community clubs. Examples of the processor 202 may be an X86-based processor, a Reduced Instruction Set Computing (RISC) processor, an Application-Specific Integrated Circuit (ASIC) processor, a Complex Instruction Set Computing (CISC) processor, and/or other processors.
[0042] The memory 204 may include suitable logic, circuitry, and/or interfaces that may be configured to store a machine code and/or a computer program with at least one code section executable by the processor 202. In an example embodiment, the event database 214 of the memory 204 may be configured to store one or more events created by the plurality of data contributors 108. The user database 216 of the memory 204 may be configured to store one or more attributes associated with the users registered with the matchmaking engine, such as the user 102 and/or the plurality of registered users 112. The memory 204 may be configured to further store determined preference index for each of the users registered with the matchmaking engine 110. The memory 204 may be configured to further store one or more weights and one or more thresholds for determining a preference index and for determining a correlation between the respective preference indexes of the registered users.
The memory 204 may be configured to further store a historical data corresponding to likes and dislikes of a registered user, with respect to the one or more pre-stored events and/or one or more users determined as matches for the user. The memory 204 may be further configured to store databases of at least the registered users, the pre-defined plurality of events, relational mapping between one or more users, relational mapping between one or more users and one or more events, and a relation mapping between the one or more users and one more attributes of one or more events. The memory 204 may be further configured to store a plurality of images based on one or more functions/routines for image compression. Examples of implementation of the memory 204 may include, but are not limited to, Random Access Memory (RAM), Read Only Memory (ROM), Hard Disk Drive (HOD), Solid State Drive (SSD), and/or a Secure Digital (SD) card. A person of ordinary skill in the art will appreciate that the event database 214 may correspond to the event database 106 explained in detail in FIG. 1.
Further, a person skilled in the art would appreciate that the memory 204 may be implemented in a distributed environment wherein there may be a plurality of instances of memory 204 and also the event database 214 and user database 216 may or may not be located in physically disparate mediums.
[0043] The matchmaking module 206 may include suitable logic, circuitry, interfaces, and/or code that may be configured to facilitate the plurality of data contributors to create one or more events, such that the created events include details such as location of the event and/or one or more attributes associated with the food items available at the location. The matchmaking module 206 may be further configured to determine one or more users having food interest similar to that of the first user 102. The matchmaking module 206 may be implemented as one or more processors, based processor technologies known in the art.
[0044] The machine learning module 208 may include suitable logic, circuitry, interfaces, and/or code that may be configured to perform a machine learning analysis on inputs provided by the user 102 and/or the plurality of registered user 112. Based on the machine learning analysis, the machine learning module 208 determines one or more events that are relevant to the user 102 and also determines a preference index associated with each of the users. The machine learning module 208 may be further configured to perform machine learning analysis on the historical selections and attributes of various users thereby calculating a correlation between the preference indexes of a plurality of users. Examples of algorithms implemented in the machine learning module 208 may include, but are not limited to, Naive Bayes Classifier Algorithm, K-Means Clustering Algorithm, Apriori Algorithm, Artificial Neural Networks, Logistic Regression, Linear Regression, Random Forests, and the like. The machine learning module 208 may be implemented as one or more processors, based processor technologies known in the art. In an aspect, the machine learning module 208 may be IBM WatsonTm API. The machine learning module 208 may also facilitate recognizing the images such as food images provided by the data contributors to determine the type and various tags associated with the food.
[0045] The Input/Output module 210 may include suitable logic, circuitry, interfaces, and/or code that may be configured to render one or more user interface objects to the plurality of contributors 108 for creating one or more events.
The Input/Output module 210 may be further configured to render a display to the user 102 for receiving one or more selection inputs with respect to the displayed one or more events that are relevant to the user 102. The Input/Output module 210 may be further configured to provide the user 102 a means for submitting one or more requests for connecting with one or more users that are determined to have similar food preferences with the user 102. To the determined users, the Input/Output module 210 presents an interface for accepting or rejecting a request for establishing a connection, received from the user 102. In an implementation, the aforementioned interface may correspond to a display screen (not shown) associated with the electronic devices of each of the registered users. Examples of the display screen 212a may include, but are not limited to, Liquid Crystal Display (LCD) display, Light Emitting Diode (LED) display, Organic LED (OLED) display technology, and/or the like.
[0046] In an implementation, the Input/Output module 210 may be further equipped with a photographic optical system, such as a photographic lens and/or a zoom lens, as well as one or more image sensors, such as a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS), a digital camera, a camera embedded in a personal digital assistant (PDA), a video camera, and/or a motion camera. Such photographic optical system may facilitate the users to provide one or more attributes relating to the events and/or the personal profiles of the users. A
person of ordinary skill in the art will appreciate that the Input/Output module may further include one or more audio based output devices for enabling communication with the registered users.
[0047] The transceiver 212 may include suitable logic, circuitry, interfaces, and/or code that may be configured to facilitate communication among the plurality of community clubs and the one or more community club members associated with the plurality of community clubs. The transceiver 212 may be implemented based on known technologies to support wired or wireless communication. The transceiver may include, but is not limited to, an antenna, a radio frequency (RF) transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a coder-decoder (CODEC) chipset, a subscriber identity module (SIM) card, and/or a local buffer. The transceiver 212 may communicate via wireless communication with networks, such as the Internet, an Intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN). The wireless communication may use any of a plurality of communication standards, protocols and technologies, such as Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), Long Term Evolution (LTE), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (such as IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE

802.11n), voice over Internet Protocol (VolP), Wi-MAX, a protocol for email, instant messaging, and/or Short Message Service (SMS).
[0048] A person of ordinary skill in the art will appreciate that the aforementioned components of the matchmaking engine 110 may be implemented in a distributed environment comprising a plurality of servers, such as a master server and a slave server along with load balancing mechanism. Each of the servers may comprise a dedicated memory for storing the modules discussed above. Further, such servers may be communicatively coupled with each other via the communication network 114.
[0049] In operation, the processor 202 may be configured to present one or more user interface objects to the plurality of contributors 108 for creation of one or more events. The one or more events may include, but are not limited to, a food served at a restaurant, where the food may correspond to a specific cuisine. As is evident from the aforementioned type of events, each event may be a combination of a location of the event along with food items that may be available at the location of the event.

[0050] The processor 202, in conjunction with the Input/Output module 210 may be configured to present one or more user interface objects on the electronic device (not shown) that may be associated with a contributor from the plurality of contributors 108. The plurality of contributors 108 may include, but are not limited to, one or more of users registered with the matchmaking engine, owners of restaurants, or food bloggers.
[0051] In an example scenario, a data contributor 108 such as a food blogger may upload an image of a food item on social media along with certain tags say for example uploading a food item on lnstagramTM along with an appropriate hashtag. The matching engine 110 upon determining that a pre-approved contributor has uploaded an image with a key hashtag may fetch the food item image along with one or more related hashtags and geo-spatial coordinates related to that image. The data contributor may then be sent a notification for creating an event. Further, the image fetched by the matching engine 110 may be utilized by the machine learning module 208 to recognize the image and determine one or more tags or keywords related to the image such as an image of sushi may enable the machine learning module 208 to determine tags such as Japanese cuisine, seafood, non-vegetarian, and the like. The data contributor may then provide further details for creating an event related to the food as described further in the present disclosure.
[0052] In an example scenario, a data contributor (such as 1081) of the plurality of contributors may enter a string to search a location of an event. When the location of the event is present in the memory 204 of the matchmaking engine 110, a user interface object for storing one or more attributes of food items associated with an event may be presented to the contributor 1081. When the location of the event is not present in the memory 204 of the matchmaking engine 110, a first user interface object for storing one or more attributes of the location of the event may be presented to the contributor 1081.
Subsequently, upon the receipt of the said location details, a second user interface object for storing one or more attributes of food items associated with the event may be presented to the contributor 1081. In an aspect, the machine learning module 208 upon analyzing the one or more attributes of the food item may further associate one or more tags relevant to the food item or the venue where such as food item is available.
[0053] In an example embodiment, the one or more attributes associated with the food items may include, but are not limited to, a picture of a food item, a cuisine type of the food item, a cost of the food item, one or more tags describing the taste and flavor associated with the food item, and availability information of the food item with respect to time and day. Further, the one or more attributes associated with the location of the event may include, but are not limited to, a name of a restaurant, a URL of the restaurant, a photo of the location, and a description of the location.
[0054] In an example embodiment, the one or more attributes associated with the food items and/or the location of the event may be retrieved from a social media profile of the contributor 1081. Further, in an example embodiment, the retrieval process may be automatic. In another example embodiment, the retrieval process may be based on one or more inputs provided by the contributor 1081.
[0055] Based on the presented user interface objects, the processor 202, in conjunction with the Input/Output module 210, may be configured to receive one or more inputs for creating the event, from the contributor 1081. The processor 202 may be further configured to create one or more prototype screens related to one or more events based on the received one or more inputs. The created one or more events may be used for establishing connections between the plurality of registered users 112. In such an embodiment, the one or more events may be created after a verification and authentication performed on the identity of the contributor 1081 to avoid misuse or spamming. The processor 202 may be configured to further verify the identity of the contributor from which the inputs are received. Based on the verification, the processor 202 may store the prototype screen in the event database 214 of the memory 204. The prototype screen may upon verification may be made live such that the event screen is displayed on electronic devices of the plurality of users 112 having attributes related to that event.
[0056] In an example embodiment, the procedure for connecting one or more users from the plurality of registered users 112 may include determining, by the processor 202, one or more events of interest from a plurality of pre-stored events stored in the events database 216. The determination of the one or more events may be based on one or more attributes associated with the user 102. In an example embodiment, the one or more attributes may be determined at the time of registering a user (such as the user 102) with the matchmaking engine 110 and also based on the historical selection of events by the user. A person of ordinary skill in the art will appreciate that the one or more attributes of each of the plurality of registered users 112 may also be received by the matchmaking engine at the time of registering the users.
[0057] In an example embodiment, for determining the one or more events of interest, the processor 202 may refer to one or more pre-defined rules, pre-stored in the memory 204. The one or more pre-defined rules may include, but are not limited to, selection of events within pre-defined location, excluding events marked as abuse, excluding food events that are still being processed, excluding food events that have expired (are passed their end date), and considering events that are newest first.
[0058] In an example embodiment, the Input/Output module 210 may be configured to render the determined one or more events of interest on the electronic device 104 of the user 102. Further, the processor 202 may be configured to sort the determined events before rendering. Such sorting may be based on assigning a higher order to the most liked events (based on user interface related gestures swipe-right), assigning a higher order to the events based on proximity to the location of the user 102, and the like.
[0059] In an example embodiment, the processor 202 may be configured to receive a selection input from the user 102. The input may be indicative of selection or liking an event from the one or more events of interest. The matching module 206 may be configured to determine one or more users associated with the selected event of interest. Such one or more users may correspond to a set of users (for example user 1121, 1123, 1124) from the plurality of registered users 112. The matching module 206 may be configured to determine, arrange, and display (in a sequential manner on the electronic device 104) the one or more users having selected the same event as the user 102. The one or more users having selected the same event are arranged and displayed in a sequential order based on the correlation between a preference index of the first user and a preference index of such one or more users. In other words, the determination may be based on a comparison of a preference index of the user 102 with a preference index of each of a plurality of users associated with the selected event of interest. In an example embodiment, the preference index may be determined based on weighted analysis of the one or more attributes associated with the user 102 and the historical data related to the events selected in the past. The weighted analysis may be based on a plurality of configurable weights (stored in the memory 204) assigned to each attribute and each past event.
[0060] In an example embodiment, the matching module 206 in conjunction with the machine learning module 208 may be further configured to determine the one or more users associated with the selected event of interest based on a degree of similarity or correlation between the preference index of the user 102 and the each of the plurality of registered users 112. For example, the one or more users may be determined when the correlation between the user 102 and the one or more users is greater than a pre-defined threshold. In an example, such a pre-defined threshold may be stored in the memory 204.
[0061] In an example embodiment, the matching module 206 may refer to one or more pre-defined rules, pre-stored in the memory 204. The one or more pre-defined rules may be such as selection of users within pre-defined location, excluding users that have been marked for abuse, excluding users profiles marked as fake, excluding users profiles that are still being processed (not yet signed in), excluding users for which the user 102 has not expressed interest for a pre-defined time, excluding users with the connection is already established, and the like.

[0062] In an example embodiment, the Input/Output module 210 may be configured to present the list of the one or more users having liked the same event on the electronic device 104 of the user 102. The list may be ordered based on proximity of a user with the location of the user 102. In another example embodiment, list may be ordered based on a degree of correlation in the preference indices. The list may be ordered based on one or more criteria that include, but are not limited to, number of common food events with person (users having more number of common events to be placed first), newest users first (user who has recently liked user 102 and the user 102 may not have liked them back), newness of a registration of a user, users that have been active most recently (currently active on top) and/or by most liked users (based on a count of user interface gestures swipe-right).
[0063] In an example embodiment, the Input/Output module 210 may be configured to receive a request from the user 102 (via the electronic device 104) for connecting with a user (such as the user 1121) from the determined one or more users.
In an example embodiment, the machine learning module 208 may be configured to record and update one or more classifiers based on each of the selection inputs/requests provided by the user 102. Such inputs/requests may be used by the machine learning module 208 to determine preference index of the user 102.
Similarly, the inputs/selections made by each of the plurality of registered users may be recorded and may be used for determining respective food preference indices. A person of ordinary skill in the art will appreciate that the recorded inputs/requests/selections of all the users registered with the matchmaking engine may be stored in the user database 216 of the memory 204.

[0064] In an example embodiment, the matching module 206 may be configured to generate a notification corresponding to the request. The Input/Output module 210 may be configured to rendered the notification on an electronic device associated with the user selected from the determined one or more users. Further, based on the received request, the matching module 206 may establish a connection between the user 102 and the user 1121. The connection may be established based on acceptance of the request of the user 102 by the user 1121. In an example embodiment, the established connection facilitates exchange of one or more messages between the user and the user selected from the determined one or more users. In an example, the matching module 206 may be further configured to store the details of the established connections (user to user mapping) in the user database 216 of the memory 204.
The connection data may be stored based on one or more data structures, known in the art.
[0065] In an example embodiment, the processor 202, via the Input/Output module 210, may be configured to receive a confirmation input indicative of physical meeting between the user 102 and the user 1121. In an example embodiment, the confirmation input may be provided by both the user 102 and the user 1121.
[0066] In an example embodiment, the processor 202 may be configured to verify the geo-spatial coordinates of both the users with respect to a location of the selected event of interest. Based on successful verification, the processor 202 may be configured to provide one or more discounts to be provided to the user 102 and the user 1121. Such discounts may be provided by means of one or more coupon codes that can be utilized at the event. The Input/Output module 210 may be configured to render such coupons on the electronic devices associated with the users. In another example embodiment, the processor 202 may be configured to instruct an administrative authority at the event to provide monetary rebate to the users.
[0067] In an example embodiment, based on the activities performed by the registered users (selection/requests/inputs) the processor 202 may be configured to determine one or more metrics such as number of viewers of a particular event from the plurality of pre-stored events, number of likes for the event, total number of connections established between the user registered with the matchmaking engine 110, and total number of check-in made at the event. A person of ordinary skill in the art will appreciate that aforementioned metrics (such as the number of connections established) may highlight the food preferred at a particular venue and/or food preferred by users (user 102 and the plurality of users 112) in a geographical region.
[0068] In an example embodiment, the check-in at an event is performed when the processor 202 receives geo-spatial coordinates of a user from a related electronic device 104. Further, upon the receipt of the geo-spatial coordinates, the processor 202, in conjunction with Input/Output module 210, may be configured to render one or more discounts to the users on the associated electronic devices 104.
[0069] FIG. 3 illustrates an example user interface for creating one or more events for connecting a plurality of users based on common liked events, in accordance with some embodiments of the present disclosure. The elements of FIG. 3 have been described in conjunction with elements of FIG's. 1 and 2.
[0070] With reference to FIG. 3, there is shown an example user interface 300 presented to the plurality of contributor's 108, for adding an event. As explained in FIG.

2, the Input/Output module 210 may be configured to render one or more user interface objects on electronic devices associated with the plurality of contributor's 108, for enabling them to add one or more attributes associated with the event.
[0071] In an example user interface, a user interface titled Add Event 302, the user interface object may include a prompt "Search Restaurant" 304 for searching a Restaurant (one or more locations of an event). The search may be performed based on an auto-complete form 306. As soon as a contributor, such as the contributor 1081 starts entering a string, one or more restaurant names having the characters of the search string may be suggested by the matchmaking engine 110. In another example scenario, the suggested names of the restaurant may have attributes that are similar to that of the restaurant whose name has been entered by the contributor 1081.
[0072] When the contributor hits the tab "Go" 308, one or more user interface objects for adding the food items and its attributes, may be rendered on the display of the electronic device associated with the contributor 1081. In an example scenario, a user interface object "upload photos" 310 may be rendered for uploading photos of the food item. The photos may be browsed in the electronic device of the contributor 1081 based on the "Browse" 312. Upon selection of a file, the contributor 1081 may click on the "upload" 314 user interface object to upload the image. In an example scenario, the image may be browsed from a social media profile of the contributor 1081. In another aspect, the data contributor may be enabled to take an image using a camera module available in the electronic device associated with the contributor 1081.

[0073] Upon uploading an image of the food item, the contributor 1081 may provide description of the food item based on the user interface object "Food Item description" 316. The contributor 1081 may further provide a location at which the photograph of the food item is available or a location where an event related to the food item may be created based on the user interface object "Photo Location" 320.
The contributor 1081 may further provide one or more relevant hashtags associated with the food item based on the user interface object "Hashtags" 322. The contributor 1081 may further provide a sale price associated with the food item based on the user interface object "Sale Price" 324. The contributor 1081 may further provide an availability status of the food item based on the user interface object "Availability" 326. In an example scenario, the food item availability may correspond to availability on a daily basis, on specific days of a week, on specific occasions, and the like.
[0074] The data contributor 1081 may further provide an input corresponding to a prompt 328 asking the contributor to "confirm whether the food item is available at all the locations of a restaurant chain" that may have a plurality of outlets. The inputs may be provided on user interface object 330 that corresponds to "Yes" or user interface object 332 that corresponds to "No". The contributor 1081 may further provide permission corresponding to a prompt 334 asking the contributor 1081 to "confirm whether the details of social media can be shared with the uploaded attributes". The permission may be provided on user interface object 336 that corresponds to "Yes" or user interface object 338 that corresponds to "No".
[0075] In an example scenario, when the name of the searched restaurant is not present in the event database 214, the Input/Output module 210 may be configured to present one or more user interface objects for adding one or more attributes of the location of the event. The one or more user interface objects for searching the location of the event based on internet based web services such as Google Maps . The Input/Output module 210 may be further configured to present one or more user interface objects for adding one or more attributes of the location of the event, such as, a description, one or more photos, a URL of a website associated with the location of the event (restaurant), and the like.
[0076] In an example scenario, the aforementioned user interface objects may be collated in a separated view dedicated for owner of the restaurants (location of the events). In such a scenario, the owner may act as contributors and may add specific details about the restaurant such as new food items, offered discounts, offered promotions, live events, and/or the like.
[0077] In an alternate embodiment, a data contributor 108 such as a food blogger may upload an image of a food item on social media along with certain tags say for example uploading a food item on lnstagramTM along with an appropriate hashtag.
The matching engine 110 upon determining that a pre-approved contributor has uploaded an image with a key hashtag may fetch the food item image along with one or more related hashtags and geo-spatial coordinates related to that image. The data contributor may then be sent a notification for creating an event and the user interface 300 may then be displayed. In such a scenario, the data related to the upload photos 310 may be replaced by the image uploaded on lnstagramTM. Further, the image fetched by the matching engine 110 may be utilized by the machine learning module 208 to recognize the image and determine one or more tags or keywords related to the image such as an image of sushi may enable the machine learning module 208 to determine tags such as Japanese cuisine, seafood, non-vegetarian, and the like. Such tags or keywords may be automatically filled in the hashtags 322. Moreover, data fields such as restaurant name 306, and photo location 320 may be automatically determined and the filled. The remaining fields may be filled as discussed in the previous paragraph.
[0078] FIGs. 4A and 4B collectively illustrate example user interfaces for connecting a plurality of users based on common liked events, in accordance with some embodiments of the present disclosure. The elements of FIGs. 4A and 4B have been described in conjunction with elements of FlG's. 1 and 2.
[0079] With reference to FIGs. 4A and 4B, there are shown example user interface 400a and 400b presented on the electronic device 104 of the user 102. As explained in FIG. 2, the Input/Output module 210 may be configured to render one or more events of interest (such as "Event 1", "Event 2", "Event 3", and "Event 4") based on one or more attributes associated with the user 102. In an example scenario, the one or more attributes, such as the location of the user 102, may be displayed using the user interface object 402. Further, the Input/Output module 210 may be configured to include an option for the user 102 for selecting (via radio buttons) an event of interest, via the user interface objects 404 to 410. In an example scenario, the user 102 may select "Event 1" and "Event 3" from the displayed list.
[0080] Based on the inputs provided by the user 102, another example user interface 400b may be presented. The user interface 400b may display a list of one or more users from the plurality of registered users 112. The selection of the one or more users has been explained in detail in FIGs. 1 and 2. In an example scenario, the one or more users may include the user 1121 to 1124. Furthermore, user interface objects 420 to 426 may display one or more attributes, such as a profile picture, associated with the one or more users. The user interface 400b may further provide an option to the user 102 for selecting a user from the displayed list based on the user interface objects 428 to 434 that may correspond to a set of radio buttons. Based on the selected users from the list, the processor 202 may be configured to notify the selected users, and based on their acceptance of the request; a connection may be established between the user 102 and a selected user from the displayed list of users.
[0081] FIG. 5 is a flow diagram of a detailed example process for connecting a plurality of users based on common liked events, in accordance with some embodiments of the present disclosure. With reference to FIG. 5, there is shown a flow chart 500. The flow chart 500 is described in conjunction with FIGs. 1 to 4B.
The process starts at step 502 and proceeds to step 504.
[0082] At step 504, one or more events of interest from a plurality of pre-stored events based on one or more attributes associated with a first registered user, may be determined by the processor 202. At step 506, a selection input from the first user 102 for selecting an event from the determined one or more events may be received by the Input/Output module 210.
[0083] At step 508, one or more users having selected the same event as the event selected by the first user, may be determined by the matching module 206. At step 508a, the one or more users having selected the same event may be arranged and displayed in a sequential manner according to a correlation between a preference index of the first user and a preference index of the one or more users having selected the same event. In an embodiment, the correlation may be based on a comparison of the preference index of first user (user 102) with the preference index of each of a plurality of registered users 112 associated with the selected event, by the matching module 206 in conjunction with the machine learning module 208. Further, a degree of similarity or correlation between the preference index of the user 102 and the preference index of a plurality of users having selected the same event may be determined by the matching module 206.
[0084] At step 510, a request from the first user (user 102) for connecting with a second user from the determined one or more users, may be received by the Input/Output module 210. At step 512, a connection between the first user and the second user, may be established by the matching module 206. The connection is established upon acceptance of the request of the first user by the second user. The control passes to step 514.
[0085] FIG. 6 is a flow diagram of a detailed example process for creating one or more events for connecting a plurality of users based on common liked events, in accordance with some embodiments of the present disclosure. With reference to FIG.
6, there is shown a flow chart 600. The flow chart 600 is described in conjunction with FIGs. 1 to 4B. The process starts at step 602 and proceeds to step 604.

[0086] At step 604, one or more user interface (user interface) objects may be presented by the Input/Output module 210 to a plurality of contributors 108 for creating one or more events. At step 606, it may be determined whether a name of a location of the event is pre-stored in the event database 214. In scenarios, when the name of the location of the event is pre-stored in the event database 214, the control passes to step 608. In scenarios, when the name of the location of the event is pre-stored in the event database 214, the control passes to step 610.
[0087] At step 608, a user interface object for storing one or more attributes of food items associated with an event in the event database 214, may be presented by the Input/Output module 210. The control passes to step 614.
[0088] At step 610, a first user interface object for storing one or more attributes of a location of the event in the event database 214, may be presented by the Input/Output module 210. At step 612, and a second user interface object for storing one or more attributes of food items associated with the location of the event in the event database 214, may be presented by the Input/Output module 210. The control passes to step 614.
[0089] At step 614, based on the presented one or more user interface objects, one or more inputs from the contributors for creating a prototype screen related to the one or more events may be received by the Input/Output module 210. At step 616, identity of the contributors may be verified. In an aspect, the contributors may be verified at the time receiving a request for creating an event. At step 618, based on the verification, the prototype screen to be displayed on one or more user devices of the users may be stored in the database (event database 214). The connection between one or more users of the plurality of users may be established based on the stored prototype screen. The control passes to end step 620.
[0090] As will be also appreciated, the above described techniques may take the form of computer or controller implemented processes and apparatuses for practicing those processes. The disclosure can also be embodied in the form of computer program code containing instructions embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, or any other computer-readable storage medium, wherein, when the computer program code is loaded into and executed by a computer or controller, the computer becomes an apparatus for practicing the invention.
The disclosure may also be embodied in the form of computer program code or signal, for example, whether stored in a storage medium, loaded into and/or executed by a computer or controller, or transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via electromagnetic radiation, wherein, when the computer program code is loaded into and executed by a computer, the computer becomes an apparatus for practicing the invention. When implemented on a general-purpose microprocessor, the computer program code segments configure the microprocessor to create specific logic circuits.
[0091] The specification has described system and method for creating events and connecting a plurality of users based on common liked events. The illustrated steps are set out to explain the example embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description.
Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0092] Furthermore, one or more computer-readable storage media may be utilized in implementing embodiments consistent with the present disclosure. A

computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor may be stored. Thus, a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein. The term "computer-readable medium"
should be understood to include tangible items and exclude carrier waves and transient signals, i.e., be non-transitory. Examples include random access memory (RAM), read-only memory (ROM), volatile memory, nonvolatile memory, hard drives, CD ROMs, DVDs, flash drives, disks, and any other known physical storage media.
[0093] It is intended that the disclosure and examples be considered as example only, with a true scope and spirit of disclosed embodiments being indicated by the following claims.

Claims

THE EMBODIMENTS OF THE INVENTION IN WHICH AN EXCLUSIVE PROPERTY
OR PRIVILIGE IS CLAIMED ARE DEFINED AS FOLLOWS:

1. A method for creating one or more events for connecting a plurality of users based on common liked events, the method comprising:
presenting, by a matchmaking engine, one or more user interface (user interface) objects to a data contributor for creating one or more events, wherein the one or more user interface objects comprise one or more of:
a user interface object for storing, in a database associated with the matchmaking engine, one or more attributes of an event; and receiving, by a matchmaking engine, based on the presented one or more user interface objects, one or more inputs from the data contributor for creating a prototype screen related to the one or more events; and storing, the prototype screen in the database to be displayed on user devices of the one or more users, based on which a connection is established between one or more users.

2. The method of claim 1, wherein the one or more attributes of food items associated with an event comprise one or more of: a picture of a food item, a cuisine of the food item, a cost of the food item, one or more tags associated with the food item, one or more geo-spatial coordinates of a location associated with the food item, and availability information of the food item with respect to time and day.

3. The method of claim 2, wherein the one or more attributes of food items and/or the one or more attributes of the location of the event may be retrieved from a social media profile associated with the one or more contributors, based on a confirmation input provided by the one or more contributors.

4. The method of claim 1, wherein the one or more user interface objects are presented to a data contributor based on authentication of the identity of the data contributor based on the social media profile of the data contributor.

5. A system for creating one or more events for connecting a plurality of users based on common liked events, the system comprising:
a plurality of user devices;
a server comprising one or more processors; and one or more storage memories communicatively coupled to the one or more processors, configured to store instructions for execution by the one or more processors, which on execution by the one or more processors, is configured to:
present one or more user interface (user interface) objects to a data contributor for creating one or more events, wherein the one or more user interface objects comprise one or more of:
a user interface object for storing, in a database associated with the matchmaking engine, one or more attributes of an event; and receive, based on the presented one or more user interface objects, one or more inputs from the data contributor for creating a prototype screen related to the one or more events; and store, the prototype screen in the database to be displayed on user devices of the one or more users, based on which a connection is established between one or more users.

6. The system of claim 5, wherein the one or more attributes of food items associated with an event comprise one or more of: a picture of a food item, a cuisine of the food item, a cost of the food item, one or more tags associated with the food item, one or more geo-spatial coordinates of a location associated with the food item, and availability information of the food item with respect to time and day.

7. The system of claim 5, wherein the one or more attributes of food items and/or the one or more attributes of the location of the event may be retrieved from a social media profile associated with the data contributor, based on a confirmation input provided by the data contributor.

8. The system of claim 7, wherein the one or more processors are configured to create the one or more events based on authentication of the identity of the data contributor based on the social media profile of the data contributor.

9. A non-transitory computer-readable storage medium storing instructions which when executed by a processor enable the processor to execute a method for creating one or more events for connecting a plurality of users based on common liked events, the method comprising:
presenting one or more user interface objects to a plurality of contributors for creating one or more events, wherein the one or more user interface objects comprise one or more of:
a user interface object for storing, in a database associated with the matchmaking engine, one or more attributes of an event; and receiving based on the presented one or more user interface objects, one or more inputs from the contributors for creating a prototype screen related to the one or more events;
verifying an identity of the user; and storing, based on the verification, the prototype screen in the database to be displayed on user devices of the one or more users, based on which a connection is established between one or more users.

10. A method of connecting two or more users based on common liked events, the method comprising:
determining, by a matchmaking engine, one or more events of interest from a plurality of pre-stored events based on one or more attributes associated with a first user;
receiving, by the matchmaking engine, a selection input from the first user for selecting an event from the determined one or more events of interest;

determining, by the matchmaking engine, one or more users having selected the same event as the event selected by the first user, wherein the one or more users having selected the same event may be arranged and displayed in a sequential manner according to a correlation between a preference index of the first user and a preference index of the one or more users;
receiving, by the matchmaking engine, a request from the first user for connecting with a second user from the determined one or more users; and establishing, by the matchmaking engine, a connection between the first user and the second user, wherein the connection is established upon acceptance of the request from the first user by the second user.

11. The method of claim 10, wherein the plurality of events are pre-stored in an event database based on one or more data inputs fetched from a plurality of data contributors.

12. The method of claim 10, wherein one or more attributes comprise one or more of: a location of a user, one or more cuisines preferred by the user, a gender of the user, sexual orientation of the user, a historical record of events liked by the user, a historical record of one or more inputs provided by the user with respect to determined one or more users, and information associated with one or more social networking profiles of the user.

13. The method of claim 10, wherein the preference index is determined based on weighted analysis of the one or more attributes associated with the user, and the historical record of events liked by the user.

14. The method of claim 10, wherein the correlation comprises comparing a preference index of the first user with a preference index of each of a plurality of users associated with the one or more event of interest.

15. The method of claim 10, wherein a notification is generated corresponding to the request, and wherein the notification is rendered on a user device associated with the user from the determined one or more users.

16. The method of claim 15, wherein the established connection facilitates exchange of one or more messages between the user and the user from the determined one or more users.

17. The method of claim 10, further comprising receiving a confirmation input indicative of physical meeting between the user and the user from the determined one or more users, wherein the confirmation input is provided by both the user and the determined user.

18. The method of claim 17, wherein the received confirmation input comprises at least one or more geospatial coordinates of the users.

19. The method of claim 18, wherein upon verification of the geo spatial coordinates with respect to a location of the selected event of interest, the matchmaking engine provides discount to the users at the selected event of interest.

20. The method of claim 10, further comprising determining one or more metrics such as number of viewers of a particular event from the plurality of pre-stored events, number of likes for the event, total number of connections established between the user registered with the matchmaking engine, and total number of check-ins made at the event.

21. A system for connecting two or more users based on common liked events, the system comprising:
a plurality of user devices;
a server comprising one or more processors; and one or more storage memories communicatively coupled to the one or more processors, configured to store instructions for execution by the one or more processors, which on execution by the one or more processors, is configured to:
determine one or more events of interest from a plurality of pre-stored events based on one or more attributes associated with a first user, wherein the one or more events of interest may be displayed on a user device associated with the first user;
receive a selection input from the user device of the first user for selecting an event from the determined one or more events of interest;

determine one or more users having selected the same event as the event selected by the first user, wherein one or more users having selected the same event may be arranged and displayed in a sequential manner according to a correlation between a preference index of the first user and a preference index of the one or more users;
receive a request from the first user for connecting with the second user from the determined one or more users; and establish a connection between the first user and the second user, wherein the connection is established upon acceptance of the request of the first user by the second.

22. The system of claim 21, wherein the plurality of events are pre-stored in an event database based on one or more data inputs fetched from a plurality of data contributors.

23. The system of claim 21, wherein one or more attributes comprise one or more of:
a location of a user, one or more cuisines preferred by the user, a gender of the user, sexual orientation of the user, a historical record of events liked by the user, a historical record of one or more inputs provided by the user with respect to determined one or more users, and information associated with a social networking profile of the user.

24. The system of claim 21, wherein the one or more processors are configured to determine the preference index based on weighted analysis of the one or more attributes associated with the user, and the historical record of events liked by the user.

25. The system of claim 21, wherein the one or more processors are configured to determine the correlation based on comparing a preference index of the first user with a preference index of each of a plurality of users associated with the one or more event of interest.

26. The system of claim 21, wherein the one or more processors are configured to generate a notification corresponding to the request, and wherein the notification is rendered on a user device associated with the user from the determined one or more users.

27. The system of claim 26, wherein the established connection facilitates exchange of one or more messages between the user and the user from the determined one or more users.

28. The system of claim 21, wherein the one or more processors are configured to receive a confirmation input indicative of physical meeting between the user and the user from the determined one or more users, wherein the confirmation input is provided by both the user and the determined user.

29. The system of claim 28, wherein the received confirmation input comprises at least one or more geospatial coordinates of the users.

30. The system of claim 29, wherein upon verification of the geo spatial coordinates with respect to a location of the selected event of interest, the matchmaking engine provides discount to the users at the selected event of interest.

31. The system of claim 21, wherein the one or more processors are configured to determine one or more metrics such as number of viewers of a particular event from the plurality of pre-stored events, number of likes for the event, total number of connections established between the user registered with the matchmaking engine, and total number of check-ins made at the event.

32. The system of claim 21, wherein the one or more processors are further configured to resize the stored one or more images according to specific resolution of an electronic device associated with a registered user.

33. A non-transitory computer-readable storage medium storing instructions which when executed by a processor enable the processor to execute a method for connecting two or more users based on common liked events, the method comprising:
determining, by a matchmaking engine, one or more events of interest from a plurality of pre-stored events based on one or more attributes associated with a first user;
receiving, by the matchmaking engine, a selection input from the first user for selecting an event from the determined one or more events of interest;

determining, by the matchmaking engine, one or more users having selected the same event as the event selected by the first user, wherein the one or more users having selected the same event may be arranged and displayed in a sequential manner according to a correlation between a preference index of the first user and a preference index of the one or more users;
receiving, by the matchmaking engine, a request from the first user for connecting with a second user from the determined one or more users; and establishing, by the matchmaking engine, a connection between the first user and the second user, wherein the connection is established upon acceptance of the request from the first user by the second user.