Methods and systems for matching device users

Abstract

An example method for execution by a matching system comprises causing the matching system to at least: enable, at or in response to a pre-set time, selection of a second user by a first user using a first device and selection of the first user by the second user using a second device; detect selection of the second user by the first user on the first device and selection of the first user by the second user on the second device; and in response to the detecting, facilitate communication between the first user and the second user. The facilitated communication between the first and second users may be temporary. The first and second users may be attendees of a live in person event held at a location. The first and second users may reserve a spot in or apply for the event prior to the pre-set time.

Description

[0001] METHODS AND SYSTEMS FOR MATCHING DEVICE USERS

[0002] FIELD

[0003] The present disclosure relates generally to methods and systems for matching users of devices.

[0004] BACKGROUND

[0005] Users of devices at a location may wish to interact with one another. Prior to interacting with another person, a user may desire to know that the other person is likewise interested in interacting with the user. Known matching systems and methods do not typically allow a user to verify whether another person is interested with interacting with them at a location in an organized manner. As such, improved methods and systems for matching users of devices are desirable.

[0006] SUMMARY

[0007] According to at least one embodiment, a method for execution by a matching system associated with a matching event comprises causing the matching system to at least: enable, at or in response to a pre-set time, selection of a second user by a first user using a first device and selection of the first user by the second user using a second device; detect selection of the second user by the first user on the first device and selection of the first user by the second user on the second device; and in response to the detecting, facilitate communication between the first user and the second user.

[0008] In some embodiments, the method further comprises causing the matching system to, at least, transmit first prospective match data comprising the second user to the first device of the first user and second prospective match data comprising the first user to the second device of the second user.

[0009] In some embodiments, the matching system is caused to transmit the first and second prospective match data at or in response to the pre-set time.

[0010] In some embodiments, the first and second prospective match data is transmitted simultaneously to the first and second devices. In some embodiments, the method further comprises causing the matching system to, at least, cause the first device to display for the first user the first prospective match data and the second device to display for the second user the second prospective match data.

[0011] In some embodiments, the first device is caused to display the first prospective match data and the second device is caused to display the second prospective match data at or in response to the pre-set time.

[0012] In some embodiments, the method further comprises causing the matching system to, at least, prior to the pre-set time obtain from the first device first profile data representing the first user and from the second device second profile data representing the second user.

[0013] In some embodiments, the first prospective match data comprises at least partially the second profile data and the second prospective match data comprises at least partially the first profile data.

[0014] In some embodiments, the pre-set time corresponds to a start time of the matching event associated with the matching system.

[0015] In some embodiments, the method further comprises causing the matching system to, at least, notify the first and second users of the pre-set time prior to the pre-set time.

[0016] In some embodiments, causing the matching system to, at least, notify the first and second users of the pre-set time comprises causing, at least, the first device to display for the first user the preset time and the second device to display for the second user the pre-set time.

[0017] In some embodiments, causing the matching system to, at least, notify the first and second users of the pre-set time comprises causing the matching system to, at least, display the pre-set time on at least one display.

[0018] In some embodiments, the method further comprises in response to the detecting, causing the matching system to, at least, prevent the first user from selecting users other than the second user on the first device and the second user from selecting users other than the first user on the second device.

[0019] In some embodiments, facilitating communication between the first and second users comprises facilitating, at least, text communication between the first and second users.

[0020] In some embodiments, facilitating communication between the first and second users comprises facilitating, at least, audio communication between the first and second users.

[0021] In some embodiments, facilitating communication between the first and second users comprises facilitating, at least, video communication between the first and second users.

[0022] In some embodiments, facilitating communication between the first and second users comprises causing the matching system to, at least, limit communication between the first and second users to communication for arranging an in-person meeting between the first user of the first device and the second user of the second device.

[0023] In some embodiments, the first profile data comprises first identifying data identifying the first user and first preference data identifying at least one preference of the first user and the second profile data comprises second identifying data identifying the second user and second preference data identifying at least one preference of the second user.

[0024] In some embodiments, the first identifying data comprises a name, a photo or both of the first user.

[0025] In some embodiments, the second identifying data comprises a name, a photo or both of the second user.

[0026] In some embodiments, the method further comprises causing the matching system to, at least, generate the first prospective match data based at least partially on the first preference data and the second prospective match data based at least partially on the second preference data. In some embodiments, the method further comprises causing the matching system to, at least, cease the detecting in response to expiration of an amount of matching time, the matching time starting after the pre-set time.

[0027] In some embodiments, the method further comprises causing the matching system to, at least, initiate a timer to count-down the matching time and cease the detecting in response to expiration of the timer.

[0028] In some embodiments, the first and second devices are communicatively coupled to the matching system with a communication network.

[0029] In some embodiments, the communication network is a public network.

[0030] In some embodiments, the communication network is a private network accessible to devices of users attending the matching event.

[0031] In some embodiments, the first device is communicatively coupled to the second device with the communication network.

[0032] In some embodiments, the first device is communicatively coupled to the second device with a network other than the communication network.

[0033] In some embodiments, the method further comprises causing the matching system to, at least, verify that a first location of the first device and a second location of the second device are proximal to a location of the matching event.

[0034] In some embodiments, verifying the first location of the first device comprises causing the matching system to, at least, compare first global positioning system (GPS) coordinates of the first device against GPS coordinates of the matching event and verifying the second location of the second device comprises comparing second GPS coordinates of the second device against the GPS coordinates of the matching event.

[0035] In some embodiments, the matching system is caused to verify the first location of the first device and the second location of the second device prior to the pre-set time. In some embodiments, the first device is a first mobile device.

[0036] In some embodiments, the first device is a first smartphone.

[0037] In some embodiments, the first device is a first smart watch.

[0038] In some embodiments, the first device is a first tablet computer.

[0039] In some embodiments, the second device is a second mobile device.

[0040] In some embodiments, the second device is a second smartphone.

[0041] In some embodiments, the second device is a second smart watch.

[0042] In some embodiments, the second device is a second tablet computer.

[0043] In some embodiments, the pre-set time is set by an operator of the matching system.

[0044] In some embodiments, the pre-set time may be varied by the operator of the matching system.

[0045] In some embodiments, the pre-set time is repeated periodically.

[0046] In some embodiments, facilitating communication between the first user and the second user comprises facilitating communication between the first and second devices.

[0047] In some embodiments, the method further comprises causing the matching system to, at least, retrieve a first payment token from the first user and a second payment token from the second user.

[0048] In some embodiments, the first and second payment tokens are retrieved prior to the pre-set time.

[0049] In some embodiments, the method further comprises causing the matching system to, at least, return the first payment token to the first user and the second payment token to the second user if selection of the second user by the first user on the first device and selection of the first user by the second user on the second device is not detected.

[0050] According to at least one embodiment, a computer program product comprising a computer readable memory storing computer executable instructions thereon that when executed by a computer perform the method steps described herein.

[0051] According to at least one embodiment, a matching system associated with a matching event comprises a processor configured to at least: enable, at or in response to a pre-set time, selection of a second user by a first user using a first device and selection of the first user by the second user using a second device; detect selection of the second user by the first user on the first device and selection of the first user by the second user on the second device; and in response to the detecting, facilitate communication between the first user and the second user.

[0052] In some embodiments, the processor is configured to, at least, transmit first prospective match data comprising the second user to the first device of the first user and second prospective match data comprising the first user to the second device of the second user.

[0053] In some embodiments, the processor is configured to transmit the first and second prospective match data at or in response to the pre-set time.

[0054] In some embodiments, the first and second prospective match data is transmitted simultaneously to the first and second devices.

[0055] In some embodiments, the processor is configured to, at least, cause the first device to display for the first user the first prospective match data and the second device to display for the second user the second prospective match data.

[0056] In some embodiments, the first device is caused to display the first prospective match data and the second device is caused to display the second prospective match data at or in response to the pre-set time. In some embodiments, the processor is configured to, at least, prior to the pre-set time obtain from the first device first profile data representing the first user and from the second device second profile data representing the second user.

[0057] In some embodiments, the first prospective match data comprises at least partially the second profile data and the second prospective match data comprises at least partially the first profile data.

[0058] In some embodiments, the pre-set time corresponds to a start time of the matching event associated with the matching system.

[0059] In some embodiments, the processor is configured to, at least, notify the first and second users of the pre-set time prior to the pre-set time.

[0060] In some embodiments, the processor configured to, at least, notify the first and second users of the pre-set time comprises causing, at least, the first device to display for the first user the preset time and the second device to display for the second user the pre-set time.

[0061] In some embodiments, the processor configured to, at least, notify the first and second users of the pre-set time comprises the processor configured to, at least, display the pre-set time on at least one display.

[0062] In some embodiments, the processor is configured to, at least, in response to the detecting, prevent the first user from selecting users other than the second user on the first device and the second user from selecting users other than the first user on the second device.

[0063] In some embodiments, facilitating communication between the first and second users comprises facilitating, at least, text communication between the first and second users.

[0064] In some embodiments, facilitating communication between the first and second users comprises facilitating, at least, audio communication between the first and second users.

[0065] In some embodiments, facilitating communication between the first and second users comprises facilitating, at least, video communication between the first and second users. In some embodiments, facilitating communication between the first and second users comprises limiting communication between the first and second users to communication for arranging an in- person meeting between the first user of the first device and the second user of the second device.

[0066] In some embodiments, the first profile data comprises first identifying data identifying the first user and first preference data identifying at least one preference of the first user and the second profile data comprises second identifying data identifying the second user and second preference data identifying at least one preference of the second user.

[0067] In some embodiments, the first identifying data comprises a name, a photo or both of the first user.

[0068] In some embodiments, the second identifying data comprises a name, a photo or both of the second user.

[0069] In some embodiments, the processor is configured to, at least, generate the first prospective match data based at least partially on the first preference data and the second prospective match data based at least partially on the second preference data.

[0070] In some embodiments, the processor is configured to, at least, cease the detecting in response to expiration of an amount of matching time, the matching time starting after the pre-set time.

[0071] In some embodiments, the processor is configured to, at least, initiate a timer to count-down the matching time and cease the detecting in response to expiration of the timer.

[0072] In some embodiments, the first and second devices are communicatively coupled to the matching system with a communication network.

[0073] In some embodiments, the communication network is a public network.

[0074] In some embodiments, the communication network is a private network accessible to devices of users attending the matching event. In some embodiments, the first device is communicatively coupled to the second device with the communication network.

[0075] In some embodiments, the first device is communicatively coupled to the second device with a network other than the communication network.

[0076] In some embodiments, the processor is configured to, at least, verify that a first location of the first device and a second location of the second device are proximal to a location of the matching event.

[0077] In some embodiments, verifying the first location of the first device comprises comparing first global positioning system (GPS) coordinates of the first device against GPS coordinates of the matching event and verifying the second location of the second device comprises comparing second GPS coordinates of the second device against the GPS coordinates of the matching event.

[0078] In some embodiments, the processor is configured to verify the first location of the first device and the second location of the second device prior to the pre-set time.

[0079] In some embodiments, the first device is a first mobile device.

[0080] In some embodiments, the first device is a first smartphone.

[0081] In some embodiments, the first device is a first smart watch.

[0082] In some embodiments, the first device is a first tablet computer.

[0083] In some embodiments, the second device is a second mobile device.

[0084] In some embodiments, the second device is a second smartphone.

[0085] In some embodiments, the second device is a second smart watch.

[0086] In some embodiments, the second device is a second tablet computer. In some embodiments, the pre-set time is set by an operator of the matching system.

[0087] In some embodiments, the pre-set time may be varied by the operator of the matching system.

[0088] In some embodiments, the pre-set time is repeated periodically.

[0089] In some embodiments, facilitating communication between the first user and the second user comprises facilitating communication between the first and second devices.

[0090] In some embodiments, the processor is configured to, at least, retrieve a first payment token from the first user and a second payment token from the second user.

[0091] In some embodiments, the first and second payment tokens are retrieved prior to the pre-set time.

[0092] In some embodiments, the processor is configured to, at least, return the first payment token to the first user and the second payment token to the second user if selection of the second user by the first user on the first device and selection of the first user by the second user on the second device is not detected.

[0093] Other aspects and features will become apparent to those ordinarily skilled in the art upon review of the following description of illustrative embodiments in conjunction with the accompanying figures.

[0094] BRIEF DESCRIPTION OF THE DRAWINGS

[0095] While the invention is claimed in the concluding portions hereof, example embodiments are provided in the accompanying detailed description which may be best understood in conjunction with the accompanying figures where like parts in each of the several figures are labeled with like numerals, and where:

[0096] FIG. 1 is a schematic illustration of an event management system according to one embodiment; FIG. 2 is a block diagram showing program codes for matching a user of a device with another user of another device according to one embodiment;

[0097] FIG. 3 is a schematic illustration of user profile data according to one embodiment;

[0098] FIG. 4A is a schematic illustration of prospective match data according to one embodiment;

[0099] FIG. 4B is a schematic illustration of prospective match data according to another embodiment;

[0100] FIG. 5 is a block diagram showing program codes for matching a user of a device with another user of another device according to one embodiment;

[0101] FIG. 6 is a block diagram showing program codes for matching a user of a device with another user of another device according to one embodiment;

[0102] FIG. 7 is a block diagram showing program codes for matching a user of a device with another user of another device according to one embodiment; and

[0103] FIG. 8 is a schematic illustration of an example location of an event.

[0104] DETAILED DESCRIPTION

[0105] The following discussion provides many example embodiments of the inventive subject matter. Although each embodiment represents a single combination of inventive elements, the inventive subject matter is considered to include all possible combinations of the disclosed elements.

[0106] With reference to FIG. 1 , there is shown an event management system 10 according to one example embodiment. The event management system 10 may be associated with an event happening or occurring at a particular location (or across several locations). The event (may also be referred to as a “matching event”) may be an event held to form one or more relationships between attendees of the event (such as romantic relationships, friendships, business relationships, client relationships, etc.). The relationships may be short term (e.g. a couple of hours, a day, a few days, a week, etc.) or long term (e.g. a few months, a year, a few years, more than five years, more than ten years, more than twenty years, etc.). The relationships may be serious relationships or casual relationships. The event may be an in-person event. The location may, for example, be a beach, a park, a coffee shop, a bakery, a theater, a sporting venue, a convention center, a portion of a city, an entire city, a country, etc.

[0107] The event management system 10 includes a matching system 12. A plurality of devices such as devices 14-1 , 14-2, 14-3, ... , 14-N (generally the devices 14) may be communicatively coupled to the matching system 12 with a communication network 16. A particular device 14 may be associated with a particular user (or a particular attendee of the event). The matching system 12 may be configured (or may be operable) to match (or pair) users of the devices 14 with each other as described herein.

[0108] The matching system 12 includes a processor circuit 20. The processor circuit 20 includes a central processing unit (CPU) 21. However, alternative embodiments may include one or more alternatives to the CPU 21 , such as one or more microprocessors, one or more analog circuits, one or more configurable logic blocks, one or more application-specific integrated circuits (ASICs), or one or more field programmable gate arrays (FPGAs), for example. The processor circuit 20 also includes a network interface (or network interface controller) 22 and a data-storage device 23 in communication with the CPU 21.

[0109] The network interface 22 is configured to communicatively couple the CPU 21 with the communication network 16. The network interface 22 may include various signal interfaces, analog-to-digital converters (ADCs), receivers, transmitters and / or other circuitry to receive, produce and transmit signals over the communication network 16.

[0110] The data-storage device 23 may include one or more of the same or different computer-readable and / or computer writable data-storage media, which in various embodiments may include one or more of a read-only memory (ROM), a random access memory (RAM), a hard disc drive (HDD), a solid-state drive (SDD) and other computer-readable and / or computer-writable data-storage media. The data-storage device 23 includes a program-codes store 24 storing program codes that, when executed by the CPU 21, cause the processor circuit 20 to implement functions of the matching system 12 such as those described herein, for example.

[0111] The processor circuit 20 is an example only, and alternative embodiments may differ. For example, alternative embodiments may include more, fewer, or different components. Also, in alternative embodiments, components described herein may be combined or separated into separate components. Alternative embodiments may include one or more alternatives to components as described herein. Further, an alternative to the matching system 12 may include multiple devices that collectively function as the matching system 12.

[0112] A device 14 is a computing device and may, in various embodiments, include a user computing device, a smartphone, a tablet computer, a smart watch, a mobile device, a laptop computer, a personal computer, or one or more other computing devices.

[0113] In the illustrated example embodiment, a device 14 includes a central processing unit (CPU) 26. However, alternative embodiments may include one or more alternatives to the CPU 26, such as one or more microprocessors, one or more analog circuits, one or more configurable logic blocks, one or more application-specific integrated circuits (ASICs), or one or more field programmable gate arrays (FPGAs), for example. The device 14 also includes an input / output (I / O) interface 27 in communication with the CPU 26.

[0114] The I / O interface 27 may include various signal interfaces, analog-to-digital converters (ADCs), receivers, transmitters, and / or other circuitry to receive, produce, and transmit signals as described herein, for example. In general, signals as described herein may include one or more radio signals, one or more optical signals, one or more electronic signals, or a combination of two or more thereof. In the embodiment shown, the I / O interface 27 is operable to, at least, transmit signals to, and receive signals from, the communication network 16.

[0115] The I / O interface 27 may also be operable to receive signals from one or more input devices, such as an input device 28 that may include a touchscreen, a keyboard, a mouse, a microphone, a camera, another user-input device, another input device, or a combination of two or more thereof to receive inputs, such as user inputs from a user of the device 14 for example. Also, the I / O interface 27 may be operable to transmit signals to one or more output devices such as an output device 29 that may include a display screen, an audio speaker, a projector, another user-output device, another output device, or a combination of two or more thereof to control one or more such output devices to produce output, for example for the user of the device 14. In the illustrated embodiment, the input device 28 and the output device 29 are shown as separate devices, but may be collectively one device such as a touchscreen or a combined microphone and audio speaker, for example. Also, the input device 28 and the output device 29 are shown in FIG. 1 as part of the device 14, but in alternative embodiments one or more input devices, one or more output devices, or both may be separate from the device 14.

[0116] Different ones of devices 14 may be the same or different.

[0117] The communication network 16 may include, or be, a computer network. The communication network 16 may include one or more networks such as the Internet, one or more wireless networks, one or more wired networks, or a combination of two or more thereof, for example. The communication network 16 may be a network (or networks) that is private to the matching system 12 and the devices 14. In some embodiments, the communication network 16 is associated with the event of the event management system 10 (e.g. is a network such as a local area network (LAN) set-up and operable for the event).

[0118] The matching system 12 may be operable to transmit signals to, and / or receive signals from, the devices 14 using the communication network 16. Likewise, the devices 14 may be operable to transmit signals to, and receive signals from, the matching system 12 using the communication network 16.

[0119] For a user to participate in (or join) the event of the event management system 10, the user’s device 14 may be communicatively coupled to the matching system 12. To communicatively couple the device 14 to the matching system 12, the device 14 may be caused to provide one or more credentials corresponding to the communication network 16, the matching system 12, the event of the event management system 10 or a combination of two or more thereof. The one or more credentials may include, or be, a name of the communication network 16, a password of the communication network 16, a network ID of the communication network 16, an identifier of the event, a password of the event, an identifier of the matching system 12, a password of the matching system 12 or a combination of two or more thereof, for example. In some embodiments, the matching system 12 is caused to verify or authenticate the one or more credentials provided by the device 14 prior to the device 14 being communicatively coupled to the matching system 12. Additionally, or alternatively, the communication network 16 may verify or authenticate the one or more credentials provided by the device 14 prior to the device 14 being connected to the communication network 16. In some embodiments, the matching system 12 is caused to verify that the device 14 is communicatively coupled to the matching system by the communication network 16.

[0120] If the communication network 16 is a LAN configured for the event, connecting a device 14 to the communication network 16 may, for example, communicatively couple the device 14 to the matching system 12. A device 14 may be connected to the LAN by, for example, providing a name of the LAN and a password of the LAN. The name and password of the LAN may be displayed for the event attendees (i.e. users of the devices 14) at the location of the event such as on one or more printed displays, one or more electronic displays, printed on one or more handouts, etc.

[0121] As another example, if the communication network 16 is a public network such as the Internet, a user of a device 14 may be prompted through, for example, a user interface such as a graphical user interface (GUI), to provide at least one credential associated with the event. Upon the provided at least one credential being authenticated by the matching system 12, the device 14 may be communicatively coupled with the matching system 12. The at least one credential may likewise be displayed for the event attendees (i.e. users of the devices 14) at the location of the event such as on one or more printed displays, one or more electronic displays, printed on one or more handouts, etc.

[0122] In some embodiments, one or more credentials for communicatively coupling a device 14 to the matching system 12 are encoded within a barcode. In some embodiments, the barcode includes, or is, a one-dimensional barcode. In some embodiments, the barcode includes, or is, a two- dimensional barcode. In some embodiments, the barcode includes, or is, a quick-response (QR) code. A device 14 may, for example, be communicatively coupled to the matching system 12 by scanning the barcode with the device 14 (e.g. with a built-in camera of the device 14) and following (or carrying out) any prompted instructions after the barcode is scanned. The prompted instructions may, for example, be displayed for a user of the device 14 on a display of the device Referring to FIG. 2, program codes stored in the program-codes store 24 may include blocks of program codes shown generally at 40 that, when executed by the CPU 21 , cause the processor circuit 20 of the matching system 12 to match (or pair) users of devices 14 together.

[0123] The blocks 40 may begin at a block 41 including program codes that, when executed by the CPU 21 , cause the processor circuit 20 to obtain profile data 42-1 , 42-2, 42-3, ... , 42-N (generally profile data 42) representing corresponding users of the corresponding devices 14-1 , 14-2, ... , 14-N. Causing the matching system 12 to obtain the profile data 42 may include causing the matching system 12 to cause the corresponding device 14 to collect required information or data from the corresponding user. For example, a CPU 26 of a device 14 may be caused to display a user interface such as a GUI on a display of the I / O interface 27 of the device 14. Through the GUI, the device 14 may prompt the user to provide the required information or data and the user may input the requested information or data. The device 14 may transmit the collected user information or data to the matching system 12 as it is collected. In some embodiments, the device 14 transmits to the matching system 12 the collected user information or data collectively at once upon all the required information being collected from the user.

[0124] A device 14 may be caused, by the matching system 12, to collect the required information or data from the corresponding user immediately upon the device 14 being communicatively coupled to the matching system 12. Alternatively, a device 14 may be caused, by the matching system 12 to collect the required information or data from the corresponding user at a time that is after the device 14 is communicatively coupled to the matching system 12 but prior to a time that the event goes live.

[0125] In some embodiments, the matching system 12 causes a plurality of devices 14 to simultaneously collect the required information or data from their corresponding users.

[0126] Referring to FIG. 3, example profile data 42-M corresponding to an Mth user of a device 14-M is shown. The illustrated example profile data 42-M includes user identifying data 42A-M which identifies the Mth user. The user identifying data 42A-M (generally user identifying data 42A) may, for example, include a name of the user, a photo of the user (e.g. a head shot of the user), an age of the user, a gender of the user, a combination of two or more thereof, etc. In some embodiments, a photo of the user is obtained by capturing a photo of the user with a built-in camera of the device 14. In some embodiments, the photo is a live photo of the user (e.g. a photo taken in real-time at a location of the event). The profile data 42-M may also include user preference data 42B-M (generally user preference data 42B) which identifies at least one preference of the Mth user. As described elsewhere herein, other users may be identified as prospective matches of the Mth user based at least partially on the user preference data 42B-M. The user preference data 42B- M may include a preferred gender of a prospective match, preferred age of a prospective match, preferred occupation of a prospective match, etc. In some embodiments, the profile data 42-M also includes user device data 42C-M (generally user device data 42C) which identifies the device 14-M which the Mth user is using. The user device data 42C-M may include, or be, a network identifier of the device 14-M.

[0127] In some embodiments, the profile data 42 for a user includes a limited amount of information or data about the user. For example, the profile data 42 for a user may be limited to a single photo of the user, gender of the user and a preferred gender of users to be matched with the user.

[0128] In some embodiments, the profile data 42 for a user is at least partially obtained by the matching system 12 and / or a device 14 collecting information or data from one or more online accounts or profiles (e.g. social media accounts, website profiles, etc.) that are associated with the user.

[0129] Returning to FIG. 2, block 43 includes program codes that, when executed by the CPU 21 , cause the processor circuit 20 to generate prospective match data 44-1 , 44-2, 44-3, ... , 44-N (generally prospective match data 44). Prospective match data 44 includes data identifying other users which are a prospective match for a user. For example, for a Kth user the prospective match data 44-K includes data identifying other users which are a prospective match for the Kth user. The prospective match data 44 may also include data identifying a device (such as a network identifier of the device) for which the prospective match data 44 corresponds to (such as device identifier 61 shown in FIGS. 4A and 4B). For example, the prospective match data 44-K may include data identifying that the prospective matches are prospective matches for the Kth user of the device 14-K.

[0130] Whether another user is a prospective match to the user or not may at least partially be based on the user preference data 42B corresponding to the user. For example, if the user preference data 42B corresponding to a user identifies that a preferred gender for matches is male, then only other users which are male may be included in the prospective match data 44 for the user. As another example, if the user preference data identifies that a preferred age for matches is thirty to forty years old, then only other users which are thirty to forty years old may be included in the prospective match data 44 for the user. In some embodiments, the prospective match data 44 for a user includes all other users.

[0131] To generate the prospective match data 44 for a user, the matching system 12 may be caused to group the other users based on the user preference data 42B of the user. For example, the other users may be grouped into a first group including users which have a characteristic or trait that matches a characteristic or trait identified in the user preference data 42B, and a second group including users which do not have a characteristic or trait that matches a characteristic or trait identified in the user preference data 42B.

[0132] In some embodiments, prospective matches for a user are ordered in a manner that reflects how well the prospective matches correspond to the user preference data 42B for the user. For example, another user that best matches the user preference data 42B of the user may be included first (or at a top of a list) in the prospective match data 44 for the user.

[0133] If the user preference data 42B includes a plurality of preferences, different ones of the preferences may have the same priority or weight or a different priority or weight when the prospective match data 44 is being generated.

[0134] In some embodiments, the prospective match data 44 for a user is generated on a rolling basis (e.g. is generated as the matching system 12 receives user profile data 42 from the different devices). The prospective match data 44 may also be updated as the matching system 12 receives user profile data 42 from the different devices or if user profile data 42 corresponding to a device 14 has been updated by the user.

[0135] In some embodiments, the prospective match data 44 for a user is generated once the matching system 12 has obtained the user profile data 42 from all of the devices 14.

[0136] In some embodiments, the matching system 12 is caused to generate a single data set including prospective match data 44 for all of the devices 14 (e.g. as shown in FIG. 4A). In some embodiments, the matching system 12 is caused to generate a separate data set for different ones of the devices 14 (e.g. prospective match data 44-1 corresponding to device 14-1 , prospective match data 44-2 corresponding to device 14-2, prospective match data 44-3 corresponding to device 14-3, prospective match data 44-N corresponding to device 14-N) (e.g. as shown in FIG. 4B).

[0137] Although block 43 is illustrated after block 41 , block 43 need not occur after block 41. Block 43 may occur simultaneously with block 41. Additionally, or alternatively, block 41 may be ongoing until profile data 42 from all of the devices 14 has been obtained. Likewise, block 43 may be ongoing until prospective match data 44 for all of the devices 14 has been generated.

[0138] Block 45 includes program codes that, when executed by the CPU 21 , cause the processor circuit 20 to determine whether a current time of the matching system 12 is equal to a pre-set time of the matching system 12. The current time of the matching system 12 may be the same as the actual time of day. The pre-set time may be a time at which the matching system 12 is configured to commence the event associated with the event management system 10 (e.g. the pre-set time may correspond to a time when the event begins or “goes live”). The pre-set time may be set or configured by, for example, an operator of the matching system 12, an organizer of the event, etc. The pre-set time may be any time. In some embodiments, the pre-set time is set to a start of an hour (e.g. midnight, 1 :00am, 4:00am, 6:00am, 10:00am, noon, 3:00pm, 5:00pm, 9:00pm, 10:00pm, etc.). In some embodiments, the pre-set time is consistently set across different hours such that the hour value is different while the minute value stays the same (e.g. 6:08am, 8:08am, 12:08pm, 2:08pm, 5:08pm, 7:08pm, 10:08pm, 11 :08pm, etc.). In some embodiments, the pre-set time is periodically reset at a constant interval (e.g. every 30 minutes, every 1 hour, every 2 hours, every 3 hours, every day, every week, every month, etc.). In some embodiments, the pre-set time may be varied by, for example, an operator of the matching system 12. In some embodiments, the pre-set time may be varied remotely by, for example, connecting to the matching system 12 and varying the pre-set time.

[0139] If the current time is not equal to the pre-set time, the blocks 40 may remain at block 45. In some embodiments, if the current time is not equal to the pre-set time, the blocks 40 may return to block 41 and / or block 43. In some embodiments, a count-down timer configured to count down the time until the pre-set time is displayed on the devices 14. In some embodiments, the matching system 12 causes the devices 14 to display the count-down timer on the devices 14.

[0140] When the current time of the matching system 12 is equal to the pre-set time, the blocks 40 may continue at a block 46 including program codes that, when executed by the CPU 21 , cause the processor circuit 20 to transmit to the plurality of devices 14 the prospective match data 44. As described above, the prospective match data 44 includes data identifying prospective matches for a user of a particular device 14. The prospective match data 44 may be simultaneously sent to the plurality of devices 14. In some embodiments, all of prospective match data 44 is sent to each device 14 (e.g. each device 14 receives all of the prospective match data 44 and retrieves the prospective match data corresponding to the particular device from the prospective match data 44). In some embodiments, a device 14 receives only the prospective match data 44 corresponding to the particular device 14 (e.g. the particular device 14 does not receive prospective match data for the other devices 14).

[0141] Upon receiving the prospective match data 44, devices 14 may be caused to display for their corresponding users, the corresponding users’ prospective matches. For example, a CPU 26 of a device 14 may be caused to display a GUI on a display of the I / O interface 27 of the device 14 which displays prospective matches of the user of the device 14. Through the I / O interface 27 of the device 14 the user may browse through the prospective matches and select which ones of the prospective matches the user would like to be (or may like to be) matched or paired with. Displaying the prospective match data may include displaying at least partially user identifying data 42A corresponding to the prospective matches such as names, photos, at least one characteristic or trait of each prospective match, etc. In some embodiments, displaying the prospective match data includes only displaying a photo of each prospective match. In some embodiments, the user selecting prospective matches includes the user browsing and selecting the prospective matches through a GUI displayed through the I / O interface 27 of the device 14. A user may select matches sequentially or non-sequentially. In some embodiments, a user may browse through their prospective match data several times. In some embodiments, a user may vary their match selection (e.g. unselect a previously selected user as a match, select a previously unselected user as a match, etc.).

[0142] In some embodiments, prospective matches of a user are displayed one at a time (i.e. one prospective match is displayed for the user at a time). Before being shown the next prospective match, the user may need to make a selection with respect to the currently displayed prospective match. Making a selection may include the user selecting to “like” the prospective match (e.g. indicate that they would be open to being matched with the prospective match), “dislike” the prospective match (e.g. indicate that they would not be open to being matched with the prospective match), or “pass” by electing not to yet “like” or “dislike” the prospective match at that time. As described elsewhere herein, once the user has browsed through all of their prospective matches, the user may choose to browse through their prospective matches again. In some embodiments, once a user indicates a “dislike” for a prospective match, that prospective match is removed from the user’s corresponding prospective match data 44 (e.g. the “disliked” match would not be displayed again if the user browses through their prospective matches again).

[0143] The prospective match data 44 may be transmitted to the devices 14 over the communication network 16.

[0144] Block 47 includes program codes that, when executed by the CPU 21 , cause the processor circuit 20 to detect a mutual match between a user of a device 14 and another user of another device 14. A mutual match between two users may occur when a first user selects a second user from the prospective matches of the first user using a first device 14 (e.g. device 14-1) and the second user selects the first user from the prospective matches of the second user using a second device 14 (e.g. device 14-2). The second user may select the first user prior to the first user selecting the second user or vice versa. The users may select other users which they would like to be matched with through their corresponding devices 14 (e.g. through the I / O interfaces 27 of their corresponding devices 14).

[0145] In some embodiments, when a user selects another user as a match, the user’s device 14 is caused to transmit to the matching system 12 data indicating the user’s selection. The matching system 12 may be caused to keep track of different users’ selections. By comparing user selections, the matching system 12 may determine when a mutual match between two users occurs.

[0146] In some embodiments, block 47 includes program codes that, when executed by the CPU 21 , cause the processor circuit 20 to detect a first mutual match between a user of a device 14 and another user of another device 14 (i.e. the very first mutual match between two users is detected).

[0147] If a match is not detected, the blocks 40 may remain at the block 47.

[0148] In some embodiments, processor 20 is configured to provide a limited amount of time for users to match with one another. If a match does not occur within the limited amount of time, the matching process may end. For example, processor 20 may be caused to implement a countdown timer which measures a remaining amount of time for users to match with one another. In some embodiments, devices 14 are caused to display the countdown timer (or a remaining amount of time).

[0149] Upon a mutual match between users of devices 14 being detected by the matching system 12, the blocks 40 may continue at a block 48 including program codes that, when executed by the CPU 21 , cause the processor circuit 20 to facilitate communication between the matched users (or devices 14 corresponding to the matched users). Facilitating communication between the matched users (or devices 14) may include facilitating text communication between the matched users (or devices 14), audio communication between the matched users (or devices 14), video communication between the matched users (or devices 14) or a combination of two or more thereof. In some embodiments, causing the processor circuit 20 to facilitate communication between the matched users (or devices 14) includes the processor circuit 20 causing each of the devices 14 corresponding to the matched users to display a GUI (e.g. causing the CPU 26 of the devices 14 to using the I / O interfaces 27 of the devices 14 to display the GUI) through which the matched users may communicate with each other.

[0150] In some embodiments, the communication between the matched users is limited to communication related to arranging a physical meeting at the location of the event between the matched users and / or locating a matched user at the location of the event. The communication may be limited by limiting a number of total characters that the communication may include (e.g. 400 characters or less, 300 characters or less, 200 character or less, etc.), limiting the communication to specific phrases (e.g. a user may use only one of a few pre-configured phrases designed to arrange a physical meeting, etc.), limiting an amount of time that the communication is enabled (e.g. three minutes or less, two minutes or less, etc.) or a combination of two or more thereof, for example. In some embodiments, the communication interface is first used by the users to arrange a physical meeting. Subsequently, the communication interface may be used by at least one of the users to locate a user they have been matched with.

[0151] The blocks 40 may include a block 49 after block 47 (as shown in FIG. 5) including program codes that, when executed by the CPU 21 , cause the processor circuit 20 to remove access to prospective matches other than the mutually matched user from the corresponding device(s) 14. Once a mutual match between, for example, two users is detected, all other prospective matches may be removed for the matched users. In some embodiments, prospective match data 44 is only available until the first mutual match occurs. Once the first mutual match occurs, the processor circuit 20 may be caused to remove access to the remaining prospective match data 44 for the corresponding matched user(s). In some embodiments, the processor circuit 20 causes the corresponding devices 14 to remove access to the prospective match data 44.

[0152] The block 49 may occur before, simultaneously with, or after the block 48.

[0153] Additionally, or alternatively, the blocks 40 may include a block 50 prior to block 45 (as shown in FIG. 6) including program codes that, when executed by the CPU 21 , cause the processor circuit 20 to verify a location of the devices 14. Participation in an event associated with the event management system 10 may be conditional on a user being physically present at a location of the event. The processor circuit 20 of the matching system 12 may be caused to verify the location of the devices 14 in order to verify whether users are physically present at the event. In some embodiments, the processor circuit 20 is caused to cause the devices 14 to transmit their current location. The processor circuit 20 may be configured to receive the transmitted current locations and compare the received locations against a location of the event. If the current location of a device 14 of a user corresponds to the location of the event within a threshold amount (e.g. within 1 m, 5m, 10m, 50m, 100m, 500m, etc.) the processor circuit 20 may verify the user as being physically present at the event. If, however, a current location of a device 14 of a user is not within a threshold amount of the location of the event, the processor circuit 20 may determine that the user is not physically present at the event. If the user is not physically present at the event, then the processor circuit 20 may, for example, be caused to remove the user from any prospective match data 44 (e.g. since the user is not physically present at the event, the user will not be a prospective match for any other user).

[0154] In some embodiments, a device 14 includes a location module 51. The location module 51 may be configured to (or be operable to) provide a current location of the device 14. In some embodiments, the location module 51 includes a global positioning system (GPS) module configured to provide GPS coordinates locating the device 14. In some embodiments, the processor circuit 20 is configured to cause the location module 51 of a device 14 to provide the current location of the device 14.

[0155] In some embodiments, a location of a device 14 is verified by the device 14 taking at least one action which can be completed only at the location of the event. For example, the device 14 may be caused to scan a barcode (e.g. a QR code) or capture an image of an object present only at the location of the event. The device 14 may be caused to provide the scanned barcode or captured image to the processor circuit 20 of the matching system 12 to verify the location of the device 14.

[0156] Block 50 may occur immediately prior to block 45. In some embodiments, block 50 occurs immediately prior to the start of an event (e.g. within 10 minutes, within 5 minutes, within 1 minute, etc. of the start of an event).

[0157] FIG. 8 illustrates an example location 80 (i.e. an example beach) at which an event may be held. A boundary 81 may enclose the location 80 (or generally correspond to the periphery of the location 80). The devices 14 located within the boundary 81 (i.e. devices 14-1 , 14-2 and 14-3) may be verified by the matching system 12 as being located at the location 80. The devices 14 located outside of the boundary 81 (i.e. devices 14-4 and 14-5) may be identified or characterized by the matching system 12 as devices 14 not present at the location 80.

[0158] In some embodiments, the blocks 40 include both of blocks 49 and 50.

[0159] Referring to FIG. 7, program codes stored in the program-codes store 24 may include blocks of program codes shown generally at 70 that, when executed by the CPU 21 , cause the processor circuit 20 of the matching system 12 to match (or pair) users of devices 14 together.

[0160] The blocks 70 may begin at a block 71 including program codes that, when executed by the CPU 21 , cause the processor circuit 20 to enable selection of other users by users using their devices 14. For example, a first user may select a second user by using a first device 14 (e.g. device 14- 1) and the second user may select the first user using a second device (e.g. device 14-2). The selection may be enabled at or in response to a pre-set time as described elsewhere herein. The pre-set time may be set, for example, by an operator of the matching system 12 as described elsewhere herein. The pre-set time may also, for example, be varied by the operator of the matching system 12 as described elsewhere herein.

[0161] In some embodiments, enabling selection of other users by users using their devices 14 includes causing the processor circuit 20 (or matching system 12) to transmit prospective match data 44 to the devices 14 as described elsewhere herein (e.g. block 46 described elsewhere herein). In some such embodiments, the prospective match data 44 is transmitted at or in response to the pre-set time. In some embodiments, enabling selection of other users by users using their devices 14 includes causing the processor circuit 20 (or matching system 12) to cause the devices 14 to display the prospective match data 44. In some such embodiments, the devices 14 are caused to display the prospective match data 44 at or in response to the pre-set time. As described elsewhere herein, in some embodiments, prospective matches are displayed to a user of a device 14 one at a time.

[0162] A block 72 includes program codes that, when executed by the CPU 21 , cause the processor circuit 20 to detect selection of other users by the users of the devices 14. For example, block 72 may include program codes that, when executed by the CPU 21 , cause the processor circuit 20 to detect selection of the second user by the first user on the first device (e.g. device 14-1) and to detect selection of the first user by the second user on the second device (e.g. device 14-2). In some embodiments, selection of other users by the users of the devices 14 is detected as described elsewhere herein (e.g. block 47 described elsewhere herein). In some embodiments, the first mutual selection or match is detected as described elsewhere herein. In some embodiments, a user is limited to a single match with another user (e.g. the user can only be mutually matched with one other user during the event and is limited to the first mutual match which occurs).

[0163] A block 73 includes program codes that, when executed by the CPU 21 , cause the processor circuit 20 to facilitate communication between matched users (or between the devices 14 of the matched users). For example, the processor 20 (or matching system 12) may be caused to facilitate communication between the first user and the second user by facilitating communication between the first device (e.g. device 14-1) and the second device (e.g. device 14-2). In some embodiments, communication is facilitated as described elsewhere herein (e.g. block 48 described elsewhere herein).

[0164] The blocks 70 may include any feature or combination of features of the blocks 40 described elsewhere herein. The blocks 70 may include block 41 , block 43, block 45, block 49, block 50 or a combination of two or more thereof, for example. In some embodiments, the blocks 70 may include program codes which cause the processor circuit 20 to obtain profile data (e.g. block 41 described elsewhere herein), generate prospective match data (e.g. block 43 described elsewhere herein) or both prior to block 71 .

[0165] In some embodiments, the blocks 70 may include program codes which cause the processor circuit 20 to verify locations of the devices 14 (e.g. block 50 described elsewhere herein) prior to block 71.

[0166] In some embodiments, the blocks 70 may include program codes that prevent selection of users after an amount of time as described elsewhere herein. In some embodiments, the blocks 70 may include program codes that prevent selection of users after an amount of time after block 71.

[0167] In some embodiments, the blocks 70 may include program codes that remove prospective match data 44 (e.g. block 49) after block 71. In some embodiments, the blocks 70 may include program codes which remove prospective match data 44 (e.g. block 49) after block 72.

[0168] In some embodiments, the matching system 12 is configured to facilitate communication between matched users for a limited amount of time. For example, the matching system 12 may disable communication between matched users at the end of a day on which an event is held. As another example, the matching system 12 may disable communication between matched users if at least one of the matched users participates in another matching event.

[0169] In some embodiments, the matching system 12 is configured to facilitate communication for a user with only one other user at any given time (i.e. a user cannot simultaneously communicate with multiple mutual matches in such embodiments).

[0170] In some embodiments, a user may cause (e.g. through their device 14) the matching system 12 to remove or cease any facilitated communication with another user. For example, if a user no longer wishes to communicate with another user they were mutually matched with, the user may cause (e.g. through their device 14) the matching system 12 to cease the facilitated communication between the two users.

[0171] In some embodiments, prior to a user being able to participate in an event, the user provides a payment token (or other form of payment) for participating in the event. For example, a device 14 of a user may be caused to transmit a payment token from the device 14 to the matching system 12. If the user is not matched with another user, the payment token may be refunded to the user. For example, the matching system 12 may be caused to transmit the payment token back to the device 14 of the user. As another example, the matching system 12 may maintain an account of payment tokens corresponding to a user. The matching system 12 may be caused to remove a payment token from the account when the user participates in an event and may refund the payment token to the account if the user is not matched with another user. In some embodiments, the matching system 12 may be caused to provide one or more payment tokens to users of devices 14 free of charge.

[0172] In some embodiments, a user reserves (or registers) a spot for an event prior to the event starting. For example, the matching system 12 may maintain data representing registered users for an event. In some embodiments, only registered users (e.g. users who reserved a spot in advance) may participate in the event. In some embodiments, only registered users (e.g. users who reserved a spot in advance) are included in prospective match data 44. In some embodiments, users may reserve a sport for an event for a limited amount of time. Devices 14 and / or the matching system 12 may, for example, be caused to display an amount of time that is remaining to reserve a spot for the event.

[0173] In some embodiments, a user may automatically reserve a spot for (or be enrolled in) an event based on the user’s location. For example, the user’s device 14 may be configured such that once the user’s device 14 is at (or proximal to) a location corresponding to the event, the user may be automatically enrolled for the event. If the user’s device 14 is no longer at (or proximal to) the location of the event, the user may be unenrolled for the event.

[0174] In some embodiments, a user may be enrolled for an event in response to the user’s device 14 being communicatively coupled to the matching system 12.

[0175] In some embodiments, a user may join or be enrolled in an event after the pre-set time but prior to a time for mutually matching with another user in the event expiring. In such embodiments, such user may provide their profile data and / or the matching system 12 may update the prospective match data 44 to include the user upon the user being enrolled in the event.

[0176] A user may join or enroll in an event personally. In some cases, a user joins or enrolls in an event as an ambassador or agent of a group of persons.

[0177] In one example case, the event management system 10 is configured to host an in-person dating event at a location such as a beach or coffee shop. Upon arriving at the event, users interested in participating in the event may use their devices (e.g. devices 14) to join the event (e.g. smartphones, tablets, laptops, etc.). To join the event, the users may locate one or more event credentials located on site and use them to communicatively couple their devices to a matching system associated with the event (e.g. matching system 12). Knowing the one or more event credentials may prove to the matching system that the user is physically present at the location of the event. Additionally, or alternatively, the devices may provide their current location to the matching system to verify that the user is physically present at the location of the event. The matching system may prompt a user to provide information such as their name, a photo, at least one preference for their matches, etc. At or in response to a pre-set time corresponding to the start of the event, the matching system of the example case will enable selection of users’ prospective matches using the users’ devices. By using their devices, the users may browse through their prospective matches and select other users they are interested in matching with. Upon the matching system detecting mutual matches (e.g. both users have indicated that they would like to match with each other), the matching system will facilitate communication between the matched users (e.g. through the matched users respective devices). Through the facilitated communication, the users may locate each other at the event and / or arrange an in-person meeting at the event. As described herein, the communication may be limited to communication for locating each other and / or arranging an in-person meeting at the event. As described herein, the matching system may be configured to remove all other prospective matches once the first mutual match is detected for the mutually matched pair of users.

[0178] By users matching through the event management system 10 described herein prior to meeting in-person at the event, the matched users may receive a confidence boost knowing that their match would like to interact with them. Additionally, the likelihood of an event participant being rejected by initiating an in-person interaction is reduced since the users have mutually matched with one another prior to meeting in-person at the event.

[0179] Although the above example case was described in a romantic dating context, the systems and methods described herein are not limited to romantic matches. The systems and methods described herein may be used to form friendship matches, business matches, client matches, or any other potential match between users of devices.

[0180] It will be appreciated by those skilled in the art that changes could be made to the various aspects of the subject application described above without departing from the inventive concept thereof.

[0181] It is to be understood, therefore, that this subject application is not limited to the particular aspects disclosed, but it is intended to cover modifications as defined by the appended claims. Also, it should be appreciated that not all features are required in all embodiments. When introducing elements of the present invention or the embodiments thereof, the articles “a,” “an,” “the,” and “said” are intended to mean that there are one or more of the elements. The terms “comprising,” “including,” and “having” are intended to be inclusive and mean that there may be additional elements other than the listed element.

Claims

CLAIMS1. A method for execution by a matching system associated with a matching event comprising causing the matching system to at least: enable, at or in response to a pre-set time, selection of a second user by a first user using a first device and selection of the first user by the second user using a second device; detect selection of the second user by the first user on the first device and selection of the first user by the second user on the second device; and in response to the detecting, facilitate communication between the first user and the second user.

2. The method of claim 1 further comprising causing the matching system to, at least, transmit first prospective match data comprising the second user to the first device of the first user and second prospective match data comprising the first user to the second device of the second user.

3. The method of claim 2 wherein the matching system is caused to transmit the first and second prospective match data at or in response to the pre-set time.

4. The method of claim 2 or 3 wherein the first and second prospective match data is transmitted simultaneously to the first and second devices.

5. The method of any one of claims 2 to 4 further comprising causing the matching system to, at least, cause the first device to display for the first user the first prospective match data and the second device to display for the second user the second prospective match data.

6. The method of claim 5 wherein the first device is caused to display the first prospective match data and the second device is caused to display the second prospective match data at or in response to the pre-set time.

7. The method of any one of claims 1 to 6 further comprising causing the matching system to, at least, prior to the pre-set time obtain from the first device first profile data representing the first user and from the second device second profile data representing the second user.

8. The method of claim 7 when dependent on any one of claims 2 to 6 wherein the first prospective match data comprises at least partially the second profile data and the second prospective match data comprises at least partially the first profile data.

9. The method of any one of claims 1 to 8 wherein the pre-set time corresponds to a start time of the matching event associated with the matching system.

10. The method of any one of claims 1 to 9 further comprising causing the matching system to, at least, notify the first and second users of the pre-set time prior to the pre-set time.

11. The method of claim 10 wherein causing the matching system to, at least, notify the first and second users of the pre-set time comprises causing, at least, the first device to display for the first user the pre-set time and the second device to display for the second user the pre-set time.

12. The method of claim 10 wherein causing the matching system to, at least, notify the first and second users of the pre-set time comprises causing the matching system to, at least, display the pre-set time on at least one display.

13. The method of any one of claims 1 to 12 further comprising in response to the detecting, causing the matching system to, at least, prevent the first user from selecting users other than the second user on the first device and the second user from selecting users other than the first user on the second device.

14. The method of any one of claims 1 to 13 wherein facilitating communication between the first and second users comprises facilitating, at least, text communication between the first and second users.

15. The method of any one of claims 1 to 14 wherein facilitating communication between the first and second users comprises facilitating, at least, audio communication between the first and second users.

16. The method of any one of claims 1 to 15 wherein facilitating communication between the first and second users comprises facilitating, at least, video communication between the first and second users.

17. The method of any one of claims 1 to 16 wherein facilitating communication between the first and second users comprises causing the matching system to, at least, limit communication between the first and second users to communication for arranging an in-person meeting between the first user of the first device and the second user of the second device.

18. The method of claim 7 or any one of claims 8 to 17 when dependent on claim 7 wherein the first profile data comprises first identifying data identifying the first user and first preference data identifying at least one preference of the first user and the second profile data comprises second identifying data identifying the second user and second preference data identifying at least one preference of the second user.

19. The method of claim 18 wherein the first identifying data comprises a name, a photo or both of the first user.

20. The method of claim 18 or 19 wherein the second identifying data comprises a name, a photo or both of the second user.

21. The method of any one of claims 18 to 20 when dependent on any one of claims 2 to 6 further comprising causing the matching system to, at least, generate the first prospective match data based at least partially on the first preference data and the second prospective match data based at least partially on the second preference data.

22. The method of any one of claims 1 to 21 further comprising causing the matching system to, at least, cease the detecting in response to expiration of an amount of matching time, the matching time starting after the pre-set time.

23. The method of claim 22 further comprising causing the matching system to, at least, initiate a timer to count-down the matching time and cease the detecting in response to expiration of the timer.

24. The method of any one of claims 1 to 23 wherein the first and second devices are communicatively coupled to the matching system with a communication network.

25. The method of claim 24 wherein the communication network is a public network.

26. The method of claim 24 wherein the communication network is a private network accessible to devices of users attending the matching event.

27. The method of any one of claims 24 to 26 wherein the first device is communicatively coupled to the second device with the communication network.

28. The method of any one of claims 24 to 26 wherein the first device is communicatively coupled to the second device with a network other than the communication network.

29. The method of any one of claims 1 to 28 further comprising causing the matching system to, at least, verify that a first location of the first device and a second location of the second device are proximal to a location of the matching event.

30. The method of claim 29 wherein verifying the first location of the first device comprises causing the matching system to, at least, compare first global positioning system (GPS) coordinates of the first device against GPS coordinates of the matching event and verifying the second location of the second device comprises comparing second GPS coordinates of the second device against the GPS coordinates of the matching event.

31. The method of claim 29 or 30 wherein the matching system is caused to verify the first location of the first device and the second location of the second device prior to the pre-set time.

32. The method of any one of claims 1 to 31 wherein the first device is a first mobile device.

33. The method of claim 32 wherein the first device is a first smartphone.

34. The method of claim 32 wherein the first device is a first smart watch.

35. The method of claim 32 wherein the first device is a first tablet computer.

36. The method of any one of claims 1 to 35 wherein the second device is a second mobile device.

37. The method of claim 36 wherein the second device is a second smartphone.

38. The method of claim 36 wherein the second device is a second smart watch.

39. The method of claim 36 wherein the second device is a second tablet computer.

40. The method of any one of claims 1 to 39 wherein the pre-set time is set by an operator of the matching system.

41. The method of claim 40 wherein the pre-set time may be varied by the operator of the matching system.

42. The method of any one of claims 1 to 41 wherein the pre-set time is repeated periodically.

43. The method of any one of claims 1 to 42 wherein facilitating communication between the first user and the second user comprises facilitating communication between the first and second devices.

44. The method of any one of claims 1 to 43 further comprising causing the matching system to, at least, retrieve a first payment token from the first user and a second payment token from the second user.

45. The method of claim 44 wherein the first and second payment tokens are retrieved prior to the pre-set time.

46. The method of claim 44 or 45 further comprising causing the matching system to, at least, return the first payment token to the first user and the second payment token to the second user if selection of the second user by the first user on the first device and selection of the first user by the second user on the second device is not detected.

47. A computer program product comprising a computer readable memory storing computer executable instructions thereon that when executed by a computer perform the method steps of any one of claims 1 to 46.

48. A matching system associated with a matching event comprising a processor configured to at least: enable, at or in response to a pre-set time, selection of a second user by a first user using a first device and selection of the first user by the second user using a second device; detect selection of the second user by the first user on the first device and selection of the first user by the second user on the second device; and in response to the detecting, facilitate communication between the first user and the second user.

49. The system of claim 48 wherein the processor is configured to, at least, transmit first prospective match data comprising the second user to the first device of the first user and second prospective match data comprising the first user to the second device of the second user.

50. The system of claim 49 wherein the processor is configured to transmit the first and second prospective match data at or in response to the pre-set time.

51. The system of claim 49 or 50 wherein the first and second prospective match data is transmitted simultaneously to the first and second devices.

52. The system of any one of claims 49 to 51 wherein the processor is configured to, at least, cause the first device to display for the first user the first prospective match data and the second device to display for the second user the second prospective match data.

53. The system of claim 52 wherein the first device is caused to display the first prospective match data and the second device is caused to display the second prospective match data at or in response to the pre-set time.

54. The system of any one of claims 48 to 53 wherein the processor is configured to, at least, prior to the pre-set time obtain from the first device first profile data representing the first user and from the second device second profile data representing the second user.

55. The system of claim 54 when dependent on any one of claims 49 to 53 wherein the first prospective match data comprises at least partially the second profile data and the second prospective match data comprises at least partially the first profile data.

56. The system of any one of claims 48 to 55 wherein the pre-set time corresponds to a start time of the matching event associated with the matching system.

57. The system of any one of claims 48 to 56 wherein the processor is configured to, at least, notify the first and second users of the pre-set time prior to the pre-set time.

58. The system of claim 57 wherein the processor configured to, at least, notify the first and second users of the pre-set time comprises causing, at least, the first device to display for the first user the pre-set time and the second device to display for the second user the pre-set time.

59. The system of claim 57 wherein the processor configured to, at least, notify the first and second users of the pre-set time comprises the processor configured to, at least, display the preset time on at least one display.

60. The system of any one of claims 48 to 59 wherein the processor is configured to, at least, in response to the detecting, prevent the first user from selecting users other than the second user on the first device and the second user from selecting users other than the first user on the second device.

61. The system of any one of claims 48 to 60 wherein facilitating communication between the first and second users comprises facilitating, at least, text communication between the first and second users.

62. The system of any one of claims 48 to 61 wherein facilitating communication between the first and second users comprises facilitating, at least, audio communication between the first and second users.

63. The system of any one of claims 48 to 62 wherein facilitating communication between the first and second users comprises facilitating, at least, video communication between the first and second users.

64. The system of any one of claims 48 to 63 wherein facilitating communication between the first and second users comprises limiting communication between the first and second users to communication for arranging an in-person meeting between the first user of the first device and the second user of the second device.

65. The system of claim 54 or any one of claims 55 to 64 when dependent on claim 54 wherein the first profile data comprises first identifying data identifying the first user and first preference data identifying at least one preference of the first user and the second profile data comprises second identifying data identifying the second user and second preference data identifying at least one preference of the second user.

66. The system of claim 65 wherein the first identifying data comprises a name, a photo or both of the first user.

67. The system of claim 65 or 66 wherein the second identifying data comprises a name, a photo or both of the second user.

68. The system of any one of claims 65 to 67 when dependent on any one of claims 49 to 53 wherein the processor is configured to, at least, generate the first prospective match data based at least partially on the first preference data and the second prospective match data based at least partially on the second preference data.

69. The system of any one of claims 48 to 68 wherein the processor is configured to, at least, cease the detecting in response to expiration of an amount of matching time, the matching time starting after the pre-set time.

70. The system of claim 69 wherein the processor is configured to, at least, initiate a timer to count-down the matching time and cease the detecting in response to expiration of the timer.

71. The system of any one of claims 48 to 70 wherein the first and second devices are communicatively coupled to the matching system with a communication network.

72. The system of claim 71 wherein the communication network is a public network.

73. The system of claim 71 wherein the communication network is a private network accessible to devices of users attending the matching event.

74. The system of any one of claims 71 to 73 wherein the first device is communicatively coupled to the second device with the communication network.

75. The system of any one of claims 74 to 73 wherein the first device is communicatively coupled to the second device with a network other than the communication network.

76. The system of any one of claims 48 to 75 wherein the processor is configured to, at least, verify that a first location of the first device and a second location of the second device are proximal to a location of the matching event.

77. The system of claim 76 wherein verifying the first location of the first device comprises comparing first global positioning system (GPS) coordinates of the first device against GPS coordinates of the matching event and verifying the second location of the second device comprises comparing second GPS coordinates of the second device against the GPS coordinates of the matching event.

78. The system of claim 76 or 77 wherein the processor is configured to verify the first location of the first device and the second location of the second device prior to the pre-set time.

79. The system of any one of claims 48 to 78 wherein the first device is a first mobile device.

80. The system of claim 79 wherein the first device is a first smartphone.

81. The system of claim 79 wherein the first device is a first smart watch.

82. The system of claim 79 wherein the first device is a first tablet computer.

83. The system of any one of claims 48 to 82 wherein the second device is a second mobile device.

84. The system of claim 83 wherein the second device is a second smartphone.

85. The system of claim 83 wherein the second device is a second smart watch.

86. The system of claim 83 wherein the second device is a second tablet computer.

87. The system of any one of claims 48 to 86 wherein the pre-set time is set by an operator of the matching system.

88. The system of claim 87 wherein the pre-set time may be varied by the operator of the matching system.

89. The system of any one of claims 48 to 88 wherein the pre-set time is repeated periodically.

90. The system of any one of claims 48 to 89 wherein facilitating communication between the first user and the second user comprises facilitating communication between the first and second devices.

91. The system of any one of claims 48 to 90 wherein the processor is configured to, at least, retrieve a first payment token from the first user and a second payment token from the second user.

92. The system of claim 91 wherein the first and second payment tokens are retrieved prior to the pre-set time.

93. The system of claim 91 or 92 wherein the processor is configured to, at least, return the first payment token to the first user and the second payment token to the second user if selection of the second user by the first user on the first device and selection of the first user by the second user on the second device is not detected.

Images