WO2016004468A1

WO2016004468A1 - Frameworks and methodologies configured to enable: person-person matching based on multiple interaction purposes and relationship/companionship dimensions; management of trust ratings to support a person-person matching engine; and voice-based communication sessions between users matched via a person-person matching engine

Info

Publication number: WO2016004468A1
Application number: PCT/AU2015/000467
Authority: WO
Inventors: Andrew Dowling
Original assignee: Tapestry Pty Ltd
Priority date: 2014-07-08
Filing date: 2015-08-05
Publication date: 2016-01-14

Abstract

Described herein are frameworks and methodologies configured to enable person-person matching based on multiple relationship/companionship dimensions. Embodiments have been primarily developed to provide technological platforms configured to assist seniors and persons with disabilities in identifying persons with which whom interact.

Description

FRAMEWORKS AND METHODOLOGIES CONFIGURED TO ENABLE: PERSON-PERSON MATCHING BASED ON

MULTIPLE INTERACTION PURPOSES AND RELATIONSHIP/COMPANIONSHIP DIMENSIONS;

MANAGEMENT OF TRUST RATINGS TO SUPPORT A PERSON-PERSON MATCHING ENGINE; AND VOICE- BASED COMMUNICATION SESSIONS BETWEEN USERS MATCHED VIA A PERSON-PERSON MATCHING ENGINE

FIELD OF THE INVENTION

[0001] The present invention relates to frameworks and methodologies configured to enable person-person matching based on multiple interaction purposes and/or relationship/companionship dimensions. Embodiments have been primarily developed to provide technological platforms configured to assist seniors and persons with disabilities in identifying persons with whom to interact. While some embodiments will be described herein with particular reference to that application, it will be appreciated that the invention is not limited to such a field of use, and is applicable in broader contexts.

BACKGROUND

[0002] Any discussion of the background art throughout the specification should in no way be considered as an admission that such art is widely known or forms part of common general knowledge in the field.

[0003] Numerous online dating platforms are known. These are, generally speaking, designed with an intention of facilitating spontaneous romantic encounters, lifelong partner relationships, and a wide variety of intermediate possibilities. However, whilst ideal for certain segments of the community, existing online dating platforms often fail to meet the needs of other segments, for example seniors. In the context of that example, beyond reluctance to trust and/or embrace technology, the practical relationship/companionship desires of seniors renders existing online dating platforms problematic for a range of reasons. SUMMARY OF THE INVENTION

[0004] It is an object of the present invention to overcome or ameliorate at least one of the disadvantages of the prior art, or to provide a useful alternative.

[0005] One embodiment provides a computer-implemented method for enabling person-person matching, the method including:

[0006] receiving, via networked communications from a user device, data indicative of a plurality of users (Ui U_n), wherein the data includes, for each user:

[0007] user attribute data (UD);

[0008] partner criteria data (PCD); and

[0009] interaction purpose data for a plurality of interaction purposes

;

[0010] operating a matching engine, thereby to identify a plurality of proposed matches between pairs of users, wherein each proposed match is related to a specific interaction purpose, such that a given proposed match for a user U, and a user U_j in respect of an interaction purpose IP_k can be expressed as PM(IP_k)(Ui +U_j);

[001 1] wherein for a given pair of users U_A and U_B, and a given selection of interaction purposes IP_C and IP_D, the matching engine identifies a proposed match PM(IP_C)(U_A +U_B) and does not identify a proposed match PM(IP_D)(U_A +U_B).

[0012] One embodiment provides a computer-implemented method wherein each user defines multiple sets of PCD, wherein each set of PCD is associated with a unique interaction purpose.

[0013] One embodiment provides a computer-implemented method wherein each user defines multiple sets of PCD, wherein each set of PCD is associated with one or more interaction purposes.

[0014] One embodiment provides a computer-implemented method wherein the matching engine is configured to apply interaction-purposes specific weightings to elements of a user's PCD, such that for IP_C a first PCD element is given a first weighting, and I P_D the first PCD element is given a second weighting, such that the matching engine identifies a proposed match PM(I P_C)(U_A +U_B) and does not identify a proposed match PM(I P_D)(U_A +U_B).

[0015] One embodiment provides a computer-implemented method wherein the matching engine is configured to apply interaction-purposes specific weightings to elements of a user's PCD, such that for I P_C a first PCD element is mandatory for matching, and I P_D the first PCD element is optional for matching, such that the matching engine identifies a proposed match PM(I P_C)(U_A +U_B) and does not identify a proposed match PM(I P_D)(U_A +U_B).

[0016] One embodiment provides a computer-implemented method including providing an interface thereby to allow users that are party to a proposed match to review and selectively approve that proposed match, wherein the interface displays for each match an associated interaction purpose or interaction purposes.

[0017] One embodiment provides a computer-implemented method for enabling person-person matching, the method including:

[0018] operating a matching engine, thereby to identify a plurality of proposed matches between pairs of users, such that a given proposed match for a user U, and a user U_j can be expressed as ΡΜ(υ, +U_j);

[0019] providing an interface thereby to allow users that a party to a proposed match to review and selectively approve that proposed match; and

[0020] in the case that a proposed match ΡΜ(υ, +U_j) is approved by both user U, and user U_j, enabling voice-based communications between user U, and user U_j.

[0021] One embodiment provides a computer-implemented method wherein enabling voice-based communications between user U, and user U_j includes providing an instruction to initiate a voice-based communication session between user U, and user U_j.

[0022] One embodiment provides a computer-implemented method wherein, in response to the instruction to initiate a telephony session between user U, and user U_j, an automated telephone call is placed to U, and, following answering of that telephone call, user LI, is placed in a voice-based communication session with user U_j.

[0023] One embodiment provides a computer-implemented method wherein, in response to the instruction to initiate a telephony session between user U, and user U_j, an automated telephone call is placed to U_j and, following answering of that telephone call, user U_j is placed in the voice-based communication session with user U,.

[0024] One embodiment provides a computer-implemented method wherein one of U, and user U_j participates in the voice-based communications session via a land-line telephone, and the other of U, and user U_j participates in the voice-based communications session via an in-app voice-over-data communications platform.

[0025] One embodiment provides a computer-implemented method wherein one of U, and user U_j participates in the voice-based communications session via a cellular telephone, and the other of U, and user U_j participates in the voice-based communications session via an in-app voice-over-data communications platform.

[0026] One embodiment provides a computer-implemented method wherein one of U, and user U_j participates in the voice-based communications session via a cellular telephone, land line telephone or in-app voice-over-data communications platform, and the other of U, and user U_j participates in the voice-based communications session via voice-based communications session via a cellular telephone, land line telephone or in- app voice-over-data communications platform.

[0027] One embodiment provides a computer-implemented method wherein one of U, and user U_j participates in the voice-based communications session via one of a cellular telephone, land line telephone or in-app voice-over-data communications platform, and the other of U, and user U_j participates in the voice-based communications session via the same one of voice-based communications session via a cellular telephone, land line telephone or in-app voice-over-data communications platform.

[0028] One embodiment provides a computer-implemented method for enabling person-person matching, the method including: [0029] operating a matching engine, thereby to identify a plurality of proposed matches between pairs of users, such that a given proposed match for a user U, and a user U_j can be expressed as ΡΜ(υ, +U_j);

[0030] providing an interface thereby to allow users that are party to a proposed match to review and selectively approve that proposed match; and

[0031] operating a trust rating engine thereby to associate each user with a trust rating, wherein the trust rating is derived from an algorithm that accounts for one or more of the followings:

[0032] independent identification verification;

[0033] nature and regularity of interaction with other users;

[0034] user feedback; and

[0035] direct/indirect mutual acquaintances.

[0036] One embodiment provides a computer-implemented method wherein an indirect mutual acquaintance for U, and user U_j includes one of:

[0037] friendship between a social media account SMA-i belonging to a person associated with U, and a social media account SMA₂ belonging to a person associated with U_j; or

[0038] friendship between a social media account SMA-i belonging to a person associated with U, and a social media account SMA₃ belonging to U_j.

[0039] One embodiment provides a computer-implemented method wherein the person associated with U, is associated by virtue of associating SMA-i with U,.

[0040] One embodiment provides a computer-implemented method wherein the person associated with U, is a relative of U,.

[0041] One embodiment provides a computer-implemented method wherein the nature and regularity of interaction with other users is based upon data indicative of: [0042] number of message-based conversations;

[0043] number of message-based conversations having a greater than threshold number of replies; and

[0044] average number of replies in message-based conversations.

[0045] One embodiment provides a computer-implemented method wherein the matching engine is configured to filter based on trust ratings.

[0046] One embodiment provides a computer-implemented method for enabling person-person matching, the method including:

[0047] receiving, via networked communications from a user device, data indicative of a plurality of users (Ui U_n), wherein the data includes, for each user:

[0048] user attribute data (UD);

[0049] partner criteria data (PCD); and

[0050] operating a matching engine, thereby to identify a plurality of proposed matches between pairs of users, such that a given proposed match for a user U, and a user U_j can be expressed as ΡΜ(υ, +U_j);

[0051] wherein the matching engine is configured to identify matches including:

[0052] matches with potential for sexual physicality, based on the users' gender and sexual orientation; and

[0053] matches without potential for sexual physicality, based on the users' gender and sexual orientation, but where the users' respective PCD indicate potential for a non- physical friendship relationship.

[0054] One embodiment provides a computer program product for performing a method as described herein. [0055] One embodiment provides a non-transitive carrier medium for carrying computer executable code that, when executed on a processor, causes the processor to perform a method as described herein.

[0056] One embodiment provides a system configured for performing a method as described herein.

[0057] Reference throughout this specification to "one embodiment", "some embodiments" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases "in one embodiment", "in some embodiments" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment, but may. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner, as would be apparent to one of ordinary skill in the art from this disclosure, in one or more embodiments.

[0058] As used herein, unless otherwise specified the use of the ordinal adjectives "first", "second", "third", etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

[0059] In the claims below and the description herein, any one of the terms comprising, comprised of or which comprises is an open term that means including at least the elements/features that follow, but not excluding others. Thus, the term comprising, when used in the claims, should not be interpreted as being limitative to the means or elements or steps listed thereafter. For example, the scope of the expression a device comprising A and B should not be limited to devices consisting only of elements A and B. Any one of the terms including or which includes or that includes as used herein is also an open term that also means including at least the elements/features that follow the term, but not excluding others. Thus, including is synonymous with and means comprising.

[0060] As used herein, the term "exemplary" is used in the sense of providing examples, as opposed to indicating quality. That is, an "exemplary embodiment" is an embodiment provided as an example, as opposed to necessarily being an embodiment of exemplary quality.

BRIEF DESCRIPTION OF THE DRAWINGS

[0061] Embodiments of the invention will now be described, by way of example only, with reference to the accompanying drawings in which:

[0062] FIG. 1 schematically illustrates a framework according to one embodiment. [0063] FIG. 2A illustrates a method according to one embodiment. [0064] FIG. 2B illustrates a method according to one embodiment. [0065] FIG. 3 illustrates an exemplary client-server framework. DETAILED DESCRIPTION

[0066] Described herein are frameworks and methodologies configured to enable person-person matching based on multiple relationship/companionship dimensions. Embodiments have been primarily developed to provide technological platforms configured to assist seniors and persons with disabilities in identifying persons with which whom interact.

System Level Overview

[0067] FIG. 1 illustrates an exemplary framework according to one embodiment. It should be appreciated that not all features shown in FIG. 1 are present in some embodiments.

[0068] A relationship/companionship matching server 100 is configured to interact with a plurality of user devices. These include devices which load a user interface via a web browser from a web server (for example exemplary user terminal 1 10, which includes a browser application 1 13 which loads code from web server 130 thereby to provide the user interface) and devices which provide a user interface via a proprietary app, for example a mobile app operable via an operating system such as iOS or Android (such as exemplary user terminal 120, which maintains code defining a proprietary application 123). Server 100 includes browser interface modules for 101 for enabling interaction with the former, and app interface modules 102 for enabling interaction with the latter.

[0069] Server 100 maintains a database 103 of user data. Database 103 holds, for each user:

• User registration data (for example a username and password, along with user contact data);

• User attribute data, for example age, sex, location and the like. These are attributes of the user. In some cases user attribute data is defined autonomously, for example by obtaining data from third party databases and/or obtaining data from a user device (for example GPS coordinates);

• User partner criteria data, which is indicative of the user's desires in terms of seeking relationship/companionship. The manner by which user partner criteria data is defined varies between embodiments, and examples are discussed further below.

[0070] This data is used by a matching engine 104 which executes matching algorithms 105, thereby to define user-user matches. In cases where a user-user match is completed, a pair of users identified by that match are enabled to communicate. This may include communication via their respective client devices (for example via communication means provided through the web browser of proprietary application, such as text-based chat), and in some embodiments includes communication via other communication means.

[0071] In terms of other communication means, in some embodiments server 100 includes a telephony management module which interacts with an external telephony system 150. This may be used to coordinate telephonic communications between users, based on their respective contact details, without the contact details being shared between the parties. This is discussed in more detail further below.

Base Matching Methodology

[0072] In embodiments described herein, a two-stage matching process is used, whereby matching engine initially identifies potential matches (PMs) based on matching algorithms, and then based on a user approval/disapproval process converts one or more PMs into Completed Matches (CMs). For example, double opt-in methodology is used, whereby each user is provided with an interface to view and selectively approve or disapprove of each PM involving that user and another user.

[0073] Matching engine 104 is configured to identify a plurality of proposed matches between two users, which for two exemplary users UserA and UserB may be described in the form PM(UserA+UserB). In the case of UserA, assume a plurality of proposed matches are defined, being PM(UserA+(UserB, UserC, UserD, UserE)), and for UserB proposed matches are PM(UserB+(UserA, UserC, UserG, UserH)). From this, UserA is presented, via a match review interface, with data representative of attribute data for UserB, UserC, UserD and UserG. UserB is presented, via a match review interface, with data representative of attribute data for UserA, UserC, UserG and UserH. In the case that UserA provides an "approve" command in respect of UserB, and UserB provides an "approve" command in respect of UserA, then a complemented match CM(UserA+UserB) is defined by matching engine 104. However, if one of those users provides a "disapprove" command in respect of the other, then no completed match is defined.

[0074] Users are only informed in situations where another user approves of a match (resulting in defining of a completed match), and is not informed in the case of disapproval of a proposed match in which they are involved.

[0075] Identification of proposed matches is based, at least in part, on partner criteria data defined by each user, and user attribute data for each user. Partner criteria data may include, as simple examples, age and location. Hence, for a given UserA, having partner criteria data defining X<age<Y, the matching engine may be configured to provide matches with users having user attribute data satisfying X<age<Y.

Purpose-Specific Matching

[0076] Some embodiments of the present make use of matching algorithms that, when identifying proposed matches, take into consideration both a users' specified partner criteria values and the users' specified interaction purpose values. This adds additional depth to matching, in the sense that a user may match with another user in respect of one interaction purpose, but not another. For example, in practice a first user may be a good match for a second user as a tennis partner, but not for a romantic relationship. [0077] In overview, each user defines a plurality of "interaction purposes". These define purposes for which a particular sought, and includes both forms of romantic interaction and non-romantic interaction. These may include the likes of:

• Watching movies;

• Playing board games;

• Outings;

• General companionship;

• Sports;

• Remote chatting (e.g. via telephone);

• Pen pals; and

• Other forms of human interaction.

[0078] These interaction purposes may be defined at varying levels of specificity, depending on implementation details of particular embodiments. For example, an interaction type of "watching movies" may include subcategories based on movie genres.

[0079] For a given user, UserA, the interaction purpose interaction purposes may be defined as (UserA)(IP₁, IP₂, IP₃, .... IP_n)- Each proposed match is associated with one or more interaction purposes. Hence, for UserA, proposed matches might be defined as follows:

• PMyP^iUserA+UserB) for a proposed match with UserB in respect of IP-i ;

• PM(IPi, IP₂)(UserA+UserC) for a proposed match with UserC in respect of IP1 and IP₂;

• PM(IP₃,)(UserA+(UserD, UserE, UserF)) for a proposed matches with UserD, UserE and UserF in respect of IP₃; and • ΡΜ(ι IP₄, IP₅,)(UserA+(UserG, UserH, Userl)) for proposed matches with UserG, UserH and Userl in respect of IP₄ or IP₅.

[0080] In terms of how the matching algorithms determine purpose specific matches responsive to partner criteria data, there are a number of approaches that may be implemented across embodiments. These include:

(i) Defining partner criteria data for each interaction purpose. For example, a user may set a different age range, distance, sex, and so on for each interaction purpose.

(ii) Weightings based on interaction purpose. Weightings may be set for matching algorithms 105 such that a given partner criteria value (PCV). PCVi is given a first weighting W-i for an interaction purpose IP-i, and a second weighting W₂ for an interaction purpose IP₂. In general terms, the weightings are set based upon objective assessment of how important a particular PCV is for a particular interaction type. For example, assume that IP-i is defined by "heterosexual sexual relationship", and IP₂ is defined by "playing backgammon", and that PCVi defines a person's sex. In this scenario, W-i and W₂ are set such that a direct match in respect of PCVi (i.e. a match with users having description date indicative of opposite sexes) is mandatory for a match in respect of IP-i, but not mandatory for a match in respect of IP₂. This, whilst possibly less accurate than the previous option, may be preferable in the sense that it requires less user input.

(Hi) Hybrids Options. These use a combination of requiring some additional partner criteria values for specific interaction purposes, but using weighting in respect of other partner criteria values when identifying potential matches.

[0081] One method includes receiving, via networked communications from a user device, data indicative of a plurality of users (U-i U_n), wherein the data includes, for each user:

• user attribute data (UD);

• partner criteria data (PCD); and

• interaction purpose data for a plurality of interaction purposes IP1 IPn . [0082] The matching engine operates thereby to identify a plurality of proposed matches between pairs of users, wherein each proposed match is related to a specific interaction purpose, such that a given proposed match for a user U, and a user U_j in respect of an interaction purpose IP_k can be expressed as PM(IP_k)(Ui +U_j).

[0083] Based on one of approaches (i) to (iii) above, for a given pair of users U_A and U_B, and a given selection of interaction purposes IP_C and IP_D, the matching engine identifies a hypothetical proposed match PM(IP_C)(U_A +U_B), but does not identify a hypothetical proposed match PM(IP_D)(U_A +U_B). In plain language, this means that a given pair of users might be matched for one interaction purpose, but not matched in respect of another interaction purpose. For example, in one hypothetical pairing there might be a match for hiking activities, but not for a romantic relationship, and in another hypothetical pairing there might be a match for hiking activities and for a romantic relationship.

[0084] In some embodiments, when a proposed match is presented to a user (for example, where UserA is presented PM(IP )(UserA+UserB), the user is specifically informed of the interaction purpose (or purposes). For example, a match review interface may suggest User B with a comment "suggested as a hiking partner", thereby to make it clear to the user for which interaction purposes a match is being proposed. In some cases a high level of match detail is provided, including details of which partner criteria are precisely matched, and which are not.

Management of Sexuality, Gender and Purpose

[0085] In some embodiments the matching engine is configured to implement a protocol whereby matching takes into account each of sexuality, gender and preference. This is configured such that proposed matches are identified in each of the following situations:

(a) Male-female matching for heterosexual users where the proposed match is predicated on a desire for relationship physicality;

(b) Male-male matching and female-female matching for homosexual users where the proposed match is predicated on a desire for relationship physicality; and

(c) Male-female matching for heterosexual users where the proposed match is not predicated on a desire for relationship physicality; and (d) Male-male matching and female-female matching for heterosexual users where the proposed match is not predicated on a desire for relationship physicality.

[0086] This is implemented via a number of approaches in various embodiments. For example, in one example, each match is associated with a physicality score, indicative of the extent to which sexual physicality is necessary for a given match. A threshold is set, and in the case that the physicality score meets/exceeds that threshold, only matches of type (a) or (b) above are provided to a user. Another approach is to use interaction purposes as an alternative or in combination with physicality score.

[0087] One embodiment provides multiple slider interfaces which allow for separate user input relating to desire for individual relationship aspects, including desire/lack of desire for sexual physicality, desire/lack of desire for exclusivity, and desire/lack of desire for physical activity.

Telephonic Communication

[0088] As shown in FIG. 2A, once a match is completed, a contact phase is entered. In some embodiments, whilst in the contact phase, two parties to a completed match are enabled to communicate via one or more communications channels. Preferably the communications channels include voice (e.g. telephonic) communications channels. In terms of telephonic communication, one user's contact details (for example phone number) are kept hidden from all other users, with coordination of a telephonic sessions being performed as a back-end functionality which eliminates the need for either user to directly know the other user's direct contact details.

[0089] Voice communications are, in some embodiments, configured using in-built voice communication functionalities (for example in-app functionalities, or browser- embedded functionalities). In further embodiments, an external telephony system is leveraged, such that each party is contacted via an automated service using respective known contact addresses (for example land-line or cellular telephone numbers). This is used to initiate a voice-communication session between the parties.

[0090] In some embodiments a voice-based communications session is initiated on an instant on-demand basis. In some embodiments a scheduling functionality is provided, such that parties to a completed match are enabled to set up a time to speak, and when that time arrives each party receives a notification (for example a telephone call) at their respective device of choice. In some embodiments this is coordinated such that one user interacts in the voice-based session via a mobile app, whereas the other uses a land-line telephone.

[0091] In each of these examples, system 100 acts as a coordinating intermediary of voice communications, such that no party is provided with contact details for another party that would enable the initiation of a voice based session other than through system 100. This allows a user to conveniently selectively block contact with another user, even after a completed match is defined.

Trust Ratings

[0092] In some embodiments, each user is associated with a "trust rating" which may be defined as a numerical score. This score is defined using a selection of the following criteria:

• Independent identification verification. For example, this may include identity checks, background checks, verification via other accounts with social media sites.

• Nature and regularity of interaction with other users of system 100. For example, this may include a rating derived from an algorithm that accepts as input parameters including length of time using the system, behaviour on the system (for example number of conversations, number of conversational messages per interaction, number of people contacted, level of content in a personal profile, and complaints).

• Feedback from other users of system 100. For example a user may be invited to rate another user (based on "trust" or another criteria) after a threshold level of interaction has occurred.

• Mutual acquaintances (optionally defined using external social media platforms).

In one embodiment this is configured such a user account is able to be linked to one or more social media accounts, for example accounts belonging to relatives. Friend relationships in those social media accounts are then analysed to establish connections, resulting in identification of indirect mutual acquaintances. This allows a wider range of links to be identified, without requiring direct social media (e.g. Facebook) use. For example, such an approach may identify that two users have grandchildren who are friends via Facebook.

[0093] The trust ratings may be used in the contest of identifying proposed matches, for example a user may require a second user have a threshold trust score before a proposed match is identified. Alternately, trust scores (and optionally context to those scores) may be displayed during the proposed match review phase.

Exemplary Client-Server Framework

[0094] In some embodiments, methods and functionalities considered herein are implemented by way of a server, as illustrated in FIG. 3. In overview, a web server 302 provides a web interface 303. This web interface is accessed by the parties by way of client terminals 304. In overview, users access interface 303 over the Internet by way of client terminals 304, which in various embodiments include the likes of personal computers, PDAs, cellular telephones, gaming consoles, and other Internet enabled devices.

[0095] Server 303 includes a processor 305 coupled to a memory module 306 and a communications interface 307, such as an Internet connection, modem, Ethernet port, wireless network card, serial port, or the like. In other embodiments distributed resources are used. For example, in one embodiment server 302 includes a plurality of distributed servers having respective storage, processing and communications resources. Memory module 306 includes software instructions 308, which are executable on processor 305.

[0096] Server 302 is coupled to a database 310. In further embodiments the database leverages memory module 306.

[0097] In some embodiments web interface 303 includes a website. The term "website" should be read broadly to cover substantially any source of information accessible over the Internet or another communications network (such as WAN, LAN or WLAN) via a browser application running on a client terminal. In some embodiments, a website is a source of information made available by a server and accessible over the Internet by a web-browser application running on a client terminal. The web-browser application downloads code, such as HTML code, from the server. This code is executable through the web-browser on the client terminal for providing a graphical and often interactive representation of the website on the client terminal. By way of the web- browser application, a user of the client terminal is able to navigate between and throughout various web pages provided by the website, and access various functionalities that are provided.

[0098] Although some embodiments make use of a website/browser-based implementation, in other embodiments proprietary software methods are implemented as an alternative. For example, in such embodiments client terminals 304 maintain software instructions for a computer program product that essentially provides access to a portal via which framework 100 is accessed (for instance via an iPhone app or the like).

[0099] In general terms, each terminal 304 includes a processor 31 1 coupled to a memory module 313 and a communications interface 312, such as an internet connection, modem, Ethernet port, serial port, or the like. Memory module 313 includes software instructions 314, which are executable on processor 31 1. These software instructions allow terminal 304 to execute a software application, such as a proprietary application or web browser application and thereby render on-screen a user interface and allow communication with server 302. This user interface allows for the creation, viewing and administration of profiles, access to the internal communications interface, and various other functionalities.

Conclusions and Interpretation

[00100] Unless specifically stated otherwise, as apparent from the following discussions, it is appreciated that throughout the specification discussions utilizing terms such as "processing," "computing," "calculating," "determining", analyzing" or the like, refer to the action and/or processes of a computer or computing system, or similar electronic computing device, that manipulate and/or transform data represented as physical, such as electronic, quantities into other data similarly represented as physical quantities.

[00101 ] In a similar manner, the term "processor" may refer to any device or portion of a device that processes electronic data, e.g., from registers and/or memory to transform that electronic data into other electronic data that, e.g., may be stored in registers and/or memory. A "computer" or a "computing machine" or a "computing platform" may include one or more processors.

[00102] The methodologies described herein are, in one embodiment, performable by one or more processors that accept computer-readable (also called machine-readable) code containing a set of instructions that when executed by one or more of the processors carry out at least one of the methods described herein. Any processor capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken are included. Thus, one example is a typical processing system that includes one or more processors. Each processor may include one or more of a CPU, a graphics processing unit, and a programmable DSP unit. The processing system further may include a memory subsystem including main RAM and/or a static RAM, and/or ROM. A bus subsystem may be included for communicating between the components. The processing system further may be a distributed processing system with processors coupled by a network. If the processing system requires a display, such a display may be included, e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT) display. If manual data entry is required, the processing system also includes an input device such as one or more of an alphanumeric input unit such as a keyboard, a pointing control device such as a mouse, and so forth. The term memory unit as used herein, if clear from the context and unless explicitly stated otherwise, also encompasses a storage system such as a disk drive unit. The processing system in some configurations may include a sound output device, and a network interface device. The memory subsystem thus includes a computer-readable carrier medium that carries computer-readable code (e.g., software) including a set of instructions to cause performing, when executed by one or more processors, one of more of the methods described herein. Note that when the method includes several elements, e.g., several steps, no ordering of such elements is implied, unless specifically stated. The software may reside in the hard disk, or may also reside, completely or at least partially, within the RAM and/or within the processor during execution thereof by the computer system. Thus, the memory and the processor also constitute computer-readable carrier medium carrying computer-readable code.

[00103] Furthermore, a computer-readable carrier medium may form, or be included in a computer program product.

[00104] In alternative embodiments, the one or more processors operate as a standalone device or may be connected, e.g., networked to other processor(s), in a networked deployment, the one or more processors may operate in the capacity of a server or a user machine in server-user network environment, or as a peer machine in a peer-to-peer or distributed network environment. The one or more processors may form a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.

[00105] Note that while diagrams only show a single processor and a single memory that carries the computer-readable code, those in the art will understand that many of the components described above are included, but not explicitly shown or described in order not to obscure the inventive aspect. For example, while only a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

[00106] Thus, one embodiment of each of the methods described herein is in the form of a computer-readable carrier medium carrying a set of instructions, e.g., a computer program that is for execution on one or more processors, e.g., one or more processors that are part of web server arrangement. Thus, as will be appreciated by those skilled in the art, embodiments of the present invention may be embodied as a method, an apparatus such as a special purpose apparatus, an apparatus such as a data processing system, or a computer-readable carrier medium, e.g., a computer program product. The computer-readable carrier medium carries computer readable code including a set of instructions that when executed on one or more processors cause the processor or processors to implement a method. Accordingly, aspects of the present invention may take the form of a method, an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of carrier medium (e.g., a computer program product on a computer-readable storage medium) carrying computer-readable program code embodied in the medium.

[00107] The software may further be transmitted or received over a network via a network interface device. While the carrier medium is shown in an exemplary embodiment to be a single medium, the term "carrier medium" should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term "carrier medium" shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by one or more of the processors and that cause the one or more processors to perform any one or more of the methodologies of the present invention. A carrier medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media includes, for example, optical, magnetic disks, and magneto-optical disks. Volatile media includes dynamic memory, such as main memory. Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise a bus subsystem. Transmission media also may also take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications. For example, the term "carrier medium" shall accordingly be taken to included, but not be limited to, solid-state memories, a computer product embodied in optical and magnetic media; a medium bearing a propagated signal detectable by at least one processor of one or more processors and representing a set of instructions that, when executed, implement a method; and a transmission medium in a network bearing a propagated signal detectable by at least one processor of the one or more processors and representing the set of instructions.

[00108] It will be understood that the steps of methods discussed are performed in one embodiment by an appropriate processor (or processors) of a processing (i.e., computer) system executing instructions (computer-readable code) stored in storage. It will also be understood that the invention is not limited to any particular implementation or programming technique and that the invention may be implemented using any appropriate techniques for implementing the functionality described herein. The invention is not limited to any particular programming language or operating system.

[00109] It should be appreciated that in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, FIG., or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this invention.

[001 10] Furthermore, while some embodiments described herein include some but not other features included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the invention, and form different embodiments, as would be understood by those skilled in the art. For example, in the following claims, any of the claimed embodiments can be used in any combination.

[001 1 1 ] Furthermore, some of the embodiments are described herein as a method or combination of elements of a method that can be implemented by a processor of a computer system or by other means of carrying out the function. Thus, a processor with the necessary instructions for carrying out such a method or element of a method forms a means for carrying out the method or element of a method. Furthermore, an element described herein of an apparatus embodiment is an example of a means for carrying out the function performed by the element for the purpose of carrying out the invention.

[001 12] In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In other instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

[001 13] Similarly, it is to be noticed that the term coupled, when used in the claims, should not be interpreted as being limited to direct connections only. The terms "coupled" and "connected," along with their derivatives, may be used. It should be understood that these terms are not intended as synonyms for each other. Thus, the scope of the expression a device A coupled to a device B should not be limited to devices or systems wherein an output of device A is directly connected to an input of device B. It means that there exists a path between an output of A and an input of B which may be a path including other devices or means. "Coupled" may mean that two or more elements are either in direct physical or electrical contact, or that two or more elements are not in direct contact with each other but yet still co-operate or interact with each other.

[001 14] Thus, while there has been described what are believed to be the preferred embodiments of the invention, those skilled in the art will recognize that other and further modifications may be made thereto without departing from the spirit of the invention, and it is intended to claim all such changes and modifications as falling within the scope of the invention. For example, any formulas given above are merely representative of procedures that may be used. Functionality may be added or deleted from the block diagrams and operations may be interchanged among functional blocks. Steps may be added or deleted to methods described within the scope of the present invention.

Claims

CLAIMS:

1 . A computer-implemented method for enabling person-person matching, the method including:

receiving, via networked communications from a user device, data indicative of a plurality of users (Ui U_n), wherein the data includes, for each user:

(i) user attribute data (UD);

(ii) partner criteria data (PCD); and

(iii) interaction purpose data for a plurality of interaction purposes

; operating a matching engine, thereby to identify a plurality of proposed matches between pairs of users, wherein each proposed match is related to a specific interaction purpose, such that a given proposed match for a user U, and a user U_j in respect of an interaction purpose I P_K can be expressed as PM(I P_k)(Ui +U_j); wherein for a given pair of users U_A and U_B, and a given selection of interaction purposes I P_C and I P_D, the matching engine identifies a proposed match PM(I P_C)(UA +U_b) and does not identify a proposed match PM(I P_D)(U_A +U_B).

2. A method according to claim 1 wherein each user defines multiple sets of PCD, wherein each set of PCD is associated with a unique interaction purpose.

3. A method according to claim 1 wherein each user defines multiple sets of PCD, wherein each set of PCD is associated with one or more interaction purposes.

4. A method according to claim 1 wherein the matching engine is configured to apply interaction-purposes specific weightings to elements of a user's PCD, such that for I P_C a first PCD element is given a first weighting, and I P_D the first PCD element is given a second weighting, such that the matching engine identifies a proposed match PM(I P_C)(U_A +U_B) and does not identify a proposed match PM(I P_D)(U_A +U_B).

5. A method according to claim 1 wherein the matching engine is configured to apply interaction-purposes specific weightings to elements of a user's PCD, such that for I P_C a first PCD element is mandatory for matching, and I P_D the first PCD element is optional for matching, such that the matching engine identifies a proposed match PM(I P_C)(U_A +U_B) and does not identify a proposed match PM(I P_D)(U_A +U_B).

6. A method according to any preceding claim including providing an interface thereby to allow users that are party to a proposed match to review and selectively approve that proposed match, wherein the interface displays for each match an associated interaction purpose or interaction purposes.

7. A computer-implemented method for enabling person-person matching, the method including:

(i) user attribute data (UD);

(ii) partner criteria data (PCD); and

operating a matching engine, thereby to identify a plurality of proposed matches between pairs of users, such that a given proposed match for a user U, and a user U_j can be expressed as ΡΜ(υ, +U_j);

wherein the matching engine is configured to identify matches including:

(a) matches with potential for sexual physicality, based on the users' gender and sexual orientation; and

(b) matches without potential for sexual physicality, based on the users' gender and sexual orientation, but where the users' respective PCD indicate potential for a non-physical friendship relationship.

8. A computer system configured to perform a method according to any one of claims 1-7.

9. A computer readable carrier medium carrying code that, when executed by one or more processors, configures a computer system to perform a method according to any one of claims 1 -7.

10. A computer-implemented method for enabling person-person matching, the method including:

providing an interface thereby to allow users that are party to a proposed match to review and selectively approve that proposed match; and operating a trust rating engine thereby to associate each user with a trust rating, wherein the trust raring is derived from an algorithm that accounts for one or more of the followings:

independent identification verification;

nature and regularity of interaction with other users;

user feedback; and

direct/indirect mutual acquaintances.

1 1. A method according to claim 10 wherein an indirect mutual acquaintance for U, and user U_j includes one of:

friendship between a social media account SMA-i belonging to a person associated with U, and a social media account SMA₂ belonging to a person associated with \J , or

friendship between a social media account SMA-i belonging to a person associated with U, and a social media account SMA₃ belonging to U_j.

12. A method according to claim 1 1 wherein the person associated with U, is associated by virtue of associating SMA-i with U,.

13. A method according to claim 1 1 wherein the person associated with U, is a relative of U,.

14. A method according to claim 1 1 wherein the nature and regularity of interaction with other users is based upon data indicative

number of message-based conversations;

number of message-based conversations having a greater than threshold number of replies; and

average number of replies in message-based conversations.

15. A method according to any one of claims 10-14 wherein the matching engine is configured to filter based on trust ratings.

16. A method according to any one of claims 10-15 including:

receiving, via networked communications from a user device, data indicative of a plurality of users (Ui U_n), wherein the data includes, for each user: (iii) user attribute data (UD);

(iv) partner criteria data (PCD); and

(v) interaction purpose data for a plurality of interaction purposes

; operating a matching engine, thereby to identify a plurality of proposed matches between pairs of users, wherein each proposed match is related to a specific interaction purpose, such that a given proposed match for a user U, and a user U_j in respect of an interaction purpose IP_k can be expressed as PM(IP_k)(Ui +U_j); wherein for a given pair of users U_A and U_B, and a given selection of interaction purposes IP_C and IP_D, the matching engine identifies a proposed match PM(IP_C)(U_A +U_B) and does not identify a proposed match PM(IP_D)(U_A +U_B).

17. A method according to claim 16 wherein each user defines multiple sets of PCD, wherein each set of PCD is associated with a unique interaction purpose.

18. A method according to claim 16 wherein each user defines multiple sets of PCD, wherein each set of PCD is associated with one or more interaction purposes.

19. A method according to claim 16 wherein the matching engine is configured to apply interaction-purposes specific weightings to elements of a user's PCD, such that for IP_C a first PCD element is given a first weighting, and IP_D the first PCD element is given a second weighting, such that the matching engine identifies a proposed match PM(IP_C)(U_A +U_B) and does not identify a proposed match PM(IP_D)(U_A +U_B).

20. A method according to claim 16 wherein the matching engine is configured to apply interaction-purposes specific weightings to elements of a user's PCD, such that for IP_C a first PCD element is mandatory for matching, and IP_D the first PCD element is optional for matching, such that the matching engine identifies a proposed match PM(IP_C)(U_A +U_B) and does not identify a proposed match PM(IP_D)(U_A +U_B).

21. A method according to any one of claims 10-20 including providing an interface thereby to allow users that are party to a proposed match to review and selectively approve that proposed match, wherein the interface displays for each match an associated interaction purpose or interaction purposes.

22. A computer-implemented method for enabling person-person matching, the method including:

providing an interface thereby to allow users that are party to a proposed match to review and selectively approve that proposed match; and

in the case that a proposed match ΡΜ(υ, +U_j) is approved by both user U, and user Uj, enabling voice-based communications between user U, and user Uj.

23. A method according to claim 22 wherein enabling voice-based communications between user U, and user U_j includes providing an instruction to initiate a voice- based communication session between user U, and user U_j.

24. A method according to claim 23 wherein, in response to the instruction to initiate a telephony session between user U, and user U_j, an automated telephone call is placed to U, and, following answering of that telephone call, user U, is placed in a voice-based communication session with user U_j.

25. A method according to claim 24 wherein, in response to the instruction to initiate a telephony session between user U, and user U_j, an automated telephone call is placed to U_j and, following answering of that telephone call, user U_j is placed in the voice-based communication session with user U,.

26. A method according to claim 23 wherein one of U, and user U_j participates in the voice-based communications session via a land-line telephone, and the other of Uj and user U_j participates in the voice-based communications session via an in- app voice-over-data communications platform.

27. A method according to claim 23 wherein one of U, and user U_j participates in the voice-based communications session via a cellular telephone, and the other of U, and user U_j participates in the voice-based communications session via an in-app voice-over-data communications platform.

28. A method according to claim 23 wherein one of U, and user U_j participates in the voice-based communications session via a cellular telephone, land line telephone or in-app voice-over-data communications platform, and the other of U, and user U_j participates in the voice-based communications session via voice-based communications session via a cellular telephone, land line telephone or in-app voice-over-data communications platform.

29. A method according to claim 23 wherein one of U, and user U_j participates in the voice-based communications session via one of a cellular telephone, land line telephone or in-app voice-over-data communications platform, and the other of U, and user U_j participates in the voice-based communications session via the same one of voice-based communications session via a cellular telephone, land line telephone or in-app voice-over-data communications platform.

30. A method according to any one of claims 22-29 including:

(vi) user attribute data (UD);

(vii) partner criteria data (PCD); and

(viii) interaction purpose data for a plurality of interaction purposes IP₁....IP_n ; operating a matching engine, thereby to identify a plurality of proposed matches between pairs of users, wherein each proposed match is related to a specific interaction purpose, such that a given proposed match for a user U, and a user U_j in respect of an interaction purpose IP_k can be expressed as PM(IP_k)(Ui +U_j); wherein for a given pair of users U_A and U_B, and a given selection of interaction purposes IP_C and IP_D, the matching engine identifies a proposed match PM(IP_C)(U_A +U_B) and does not identify a proposed match PM(IP_D)(U_A +U_B).

31. A method according to claim 30 wherein each user defines multiple sets of PCD, wherein each set of PCD is associated with a unique interaction purpose.

32. A method according to claim 30 wherein each user defines multiple sets of PCD, wherein each set of PCD is associated with one or more interaction purposes.

33. A method according to claim 30 wherein the matching engine is configured to apply interaction-purposes specific weightings to elements of a user's PCD, such that for IP_C a first PCD element is given a first weighting, and IP_D the first PCD element is given a second weighting, such that the matching engine identifies a proposed match PM(I P_C)(U_A +U_B) and does not identify a proposed match

34. A method according to claim 30 wherein the matching engine is configured to apply interaction-purposes specific weightings to elements of a user's PCD, such that for I P_C a first PCD element is mandatory for matching, and I P_D the first PCD element is optional for matching, such that the matching engine identifies a proposed match PM(I P_C)(U_A +U_B) and does not identify a proposed match PM(I P_D)(U_A +U_B).

35. A method according to any one of claims 22 to 34 including providing an interface thereby to allow users that are party to a proposed match to review and selectively approve that proposed match, wherein the interface displays for each match an associated interaction purpose or interaction purposes.

36. A computing device configured to perform a method according to any preceding claim.

37. A tangible non-transitory computer-readable medium carrying code that, when executed by a processor, causes performance of a method according to any one of claims 1 -35.