WO2009028970A1 - Contact system and method - Google Patents
Contact system and method Download PDFInfo
- Publication number
- WO2009028970A1 WO2009028970A1 PCT/NZ2008/000226 NZ2008000226W WO2009028970A1 WO 2009028970 A1 WO2009028970 A1 WO 2009028970A1 NZ 2008000226 W NZ2008000226 W NZ 2008000226W WO 2009028970 A1 WO2009028970 A1 WO 2009028970A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- information
- encounter
- parties
- location
- time
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/29—Geographical information databases
Definitions
- the present invention relates to a contact system and method, more specifically, to a contact system and method that facilitates contact between people based on an encounter between two parties.
- the present invention may be said to consist in a method of facilitating contact between at least two parties based on an encounter between the two parties comprising: retrospectively receiving first information specifying the encounter, the first information identifying at least one party to the encounter and at least the time and location of the encounter, identifying stored retrospectively received second information specifying an encounter, the second information identifying at least one party to the encounter and at least the time and location of the encounter, facilitating contact between the two parties if the second information correlates to the first information.
- the method further comprises, prior to checking for stored second information, retrospectively receiving second information specifying an encounter.
- the first and second information is associated with and/or received from respective parties to the encounter.
- the first and/or second information identifying the location of the encounter is received via a graphical interface depicting geographical locations.
- the first information and the second information may or may not specify the same encounter.
- the first and/or second information identify a range of times and/or locations that encompass the encounter, wherein the first information correlates to the second information if one or more of the locations and/or times specified by the ranges match to within a tolerance level.
- the first and or second information comprises a code for specifying the location.
- a range of times and/or locations are specified using a slider on a graphical interface.
- the first and or second information are received via text messaging or email.
- the present invention may be said to consist in a method of facilitating contact between at least two parties based on an encounter between the two parties comprising retrospectively receiving information on a plurality of encounters, each information specifying the time and location of an encounter, receiving a request for a match to an encounter, searching to identify information specifying one or more encounters that correlate to that encounter, and conveying the identified information.
- the present invention may be said to consist in a system for facilitating contact between at least two parties based on an encounter between the two parties comprising: a computer adapted to process and store data, and to connect to and communicate over a network to one or more remote interfaces, a storage device in or remote to the computer, wherein the computer is programmed to: retrospectively receive first information specifying the encounter over a network, the first information identifying at least one party to the encounter and at least the time and location of the encounter, identifying from the storage device retrospectively received second information specifying an encounter, the second information identifying at least one party to the encounter and at least the time and location of the encounter, facilitating contact between the two parties if the second information correlates to the first information.
- the computer is programmed to, prior to checking for stored second information, retrospectively receive second information specifying the encounter.
- the first and second information is associated with and/or received from respective parties to the encounter.
- the computer is programmed to transferring contact information to facilitate contact between the two parties via the network.
- the first and/or second information is received via a one or more remote interfaces being one or more of: a website interface, a mobile device interface.
- the first and/or second information identifying the location of the encounter is received via a graphical interface on the remote interface depicting geographical locations.
- the second information correlates to the first information if one or more of the time, location and/or party specified by both the first and second information matches to within a tolerance level.
- the first information and die second information may or may not specify the same encounter.
- the computer is programmed to identify further correlation between the first and/or second information to determine if they specify the same encounter.
- the first and/or second information identify a range of times and/or locations that encompass the encounter, wherein the first information correlates to the second information if one or more of the locations and/or times specified by the ranges match to within a tolerance level.
- the first and or second information comprises a code for specifying the location.
- the computer is programmed to provide a slider on a graphical interface to receive input specifying a range of times and/or locations.
- the first and or second information are received via text messaging or email.
- the present invention may be said to consist in a method of obtaining contact information on a third party you have previously met in person comprising the steps of: providing graphical interface in the form of a map that allows a user to enter details of a meeting that took place; storing information on the meeting including the location on die map and die time of the meeting; searchi7ng for a similar meeting and presents matches to users.
- the method comprises providing details of the other matched party.
- the meeting details are received via a SMS, web interface and/or email.
- the meeting details include a security question known to the users who entered the meeting details.
- the system provides details of the other matched party.
- the system comprises an interface to obtain permission of the parties to swap details.
- the system comprises an SMS gateway and the system may receive meeting details via
- the system comprises at least one communication interface selected from a web interface, an email server interface and an SMS gateway interface and said system communicates with system users via at least one of said communication interfaces.
- die present invention may be said to consist in a method of facilitating contact between at least two parties based on an encounter between the two parties comprising: retrospectively receiving first information specifying the encounter, the first information identifying at least one party to the encounter and at least the time and location of the encounter, advising a group of system users of the encounter, receiving input from one or more system users of a match, and facilitating contact between the parties.
- the present invention may be said to consist in a system for facilitating contact between at least two parties based on an encounter between the two parties comprising: a computer adapted to process and store data, and to connect to and communicate over a network to one or more remote interfaces, a storage device in or remote to the computer, wherein the computer is programmed to: retrospectively receive first information specifying the encounter, the first information identifying at least one party to the encounter and at least the time and location of the encounter, advise a group of system users of die encounter, receive input from one or more system users of a match, and facilitate contact between the parties.
- the present invention may be said to consist in a method of facilitating contact between at least two parties based on an encounter between the two parties comprising: retrospectively receiving first information specifying the encounter, the first information identifying at least the time and location of the encounter, identifying stored retrospectively received second information specifying an encounter, the second information identifying at least the time and location of the encounter, facilitating contact between two parties associated with the information if die second information correlates to the first information.
- Figure 1 is a diagram of a system according to one embodiment
- Figure 6 is a flow chart depicting a method for finding matching encounters
- Figure 20 is a diagram of the graphical data entry screen showing a number of existing entries
- Figure 21 is a diagram of the graphical data entry interface of the present invention
- Figure 22 is a graphical data entry interface of the present invention illustrating a meeting being entered
- Figure 24 is a graphical data entry interface of the present invention illustrating a match being displayed
- Figure 26 is a graphical data entry interface of the present invention illustrating the display of information that there are too many matches
- Figure 27 is an example email from the system requesting a shared secret question be answered
- Figure 28 is an example email from the system confirming a match
- Figure 29 is an example email from the system including the match information
- Figure 30 is an example email from the system notifying the user that a match has not been found
- Figure 31 is an example email from the system notifying the user that too many matches have been found
- Figure 32 is an example SMS screen that a user could submit
- Figure 33 is an example SMS screen requesting the secret question answer from the user
- Figure 34 is an example SMS screen confirming a match to a user
- Figure 35 is an example SMS screen passing details of the other party onto a user
- Figure 36 is an example SMS screen that a user would receive when too many matches are identified
- Figure 37 is a flow diagram of the process of the present invention.
- Encounter information relates to information provided by a party that can identify/specify/define an associated encounter. Encounter information will comprise at least time and location information of the encounter. It can optionally further comprise additional information such as: identification of the parties to the encounter, distinguishing information, or the like. A particular "bundle" of encounter information that specifies an encounter can be termed an instance of encounter information.
- source encounter information is encounter information that is used as the basis for finding matching encounter information.
- Source encounter information can also be reciprocal encounter information in different circumstances.
- reciprocal encounter information is encounter information that matches source information and relates to the same encounter as the source encounter information. Reciprocal encounter information can also be source encounter information in different circumstances.
- associated party is an entity that was a party to an encounter specified by some encounter information. In most cases, an associated party will be a person who was actually at the encounter specified by the encounter information. However, the associated party possibly could be another related person where this may assist contact between parties. Encounter information comprises information identifying an associated party. The encounter information may be entered into the system by the associated party, or any other third party who may or may not have been involved in the encounter.
- a "match" is where some encounter information is found that correlates to some source encounter information. The information correlates if the time and location specified by bodi sets of encounter information are the same to within a specified tolerance. Matched encounter information might be reciprocal encounter information, although this is not necessarily the case.
- the invention could also be used in an instance where people who do not know each other have an encounter, and may wish to contact each other for a new relationship. This would be particularly useful as a means for dating. It might also cover the situation where the parties to the encounter are not actually the people that want to establish contact, but are in some way associated with people who might want to make contact.
- Figure 1 shows in general form an overview of one embodiment of a system that could be used to implement the invention.
- the system implements the method and software applications of the invention. It will be appreciated that the invention might also be considered to comprise just some of the system shown.
- the invention might comprise portions of the system and/or the relevant method and/or software implemented by those portions.
- the systeml comprises a server 10 stationed at an appropriate location.
- the server comprises a web server 10a, application server 10b, database server 10c, email server and interface 1Od, and sms server and interface 1Oe. Together these form the server that provide the system functionality.
- the server 10 can also comprise other suitable additional interfaces for communication with parties accessing the system remotely.
- the server is coupled to a wide area network, such as the internet via a local ISP 11. Users (usually subscribers or registered users of the system) of the system can access the functionality (services) provided by the server through the internet or other wide area network.
- users will access the server 10 through a remote PC 13 using an internet browser, which enables them to access the services provided by the server.
- users could access die server via a mobile device, such as a mobile telephone 14. This could be done through text messaging via an sms gateway 12 that interacts with the server 10 through the internet 11.
- the interaction could take place with the server via a suitable communication protocol over a GSM, GPRS or any other mobile communications network.
- Other remote devices and computers could be also used to access and interact with the services provided by the server, and those mentioned here should not be considered limiting.
- the system allows two parties to establish or re-establish contact based on time and location information.
- the time and location information will relate to respective the time and location of the parties when they have an encounter, or people associated with them have an encounter.
- An encounter for example, could be a chance meeting on the street.
- the invention is not restricted to establishing contact based on time and location information of physical encounters. Time and location of any type of encounter event could be utilised. "
- the system 1 either allows or facilitates communication between the two parties via a communications service. This could be one or more of: chat rooms, instant messaging, email, text messaging or the like.
- the server alternatively, or additionally, also allows for transfer of contact details between the two parties so they can make their contact via alternative communication means independently from the system. Security /identification confirmation methods are preferably undertaken before the server transfers contact details or allows contact. However, this is not essential.
- the system 1 may implement a mediod via software in website that operates in the following manner.
- Two parties who used to know each other, may have a chance encounter at a location, like an airport. They may have only seen each other at a distance, and therefore could not exchange contact details. If both parties were interested in re-establishing contact, they could utilise the system. They could both independendy enter the time and location of the encounter into the system through a PC 13, mobile device 14 or the like. This information is received, processed and stored by the server 10.
- the server 10 can be triggered to perform a match on time and location details. For example, if first party to the encounter enters the time and location details (termed "encounter information") of the encounter, they can then request the server to search for any other instances of encounter information it has received from another party that specifies the same time and location (to within a suitable tolerance). If the server 10 locates such other encounter information, and the subsequent security /identification confirmations are successful, the server will alert one or both the parties who entered the corresponding encounter information. They can then be put in contact via the server communications services, or the server can transfer contact information between the two.
- time and location details termed "encounter information”
- the server 10 will receive numerous separate entries (or instances) of encounter information over time, each encounter information instance being received from one of a number of users. Each instance will relate to an encounter. For any particular instance of encounter information, the server might have received (or in the future might receive) one or more reciprocal instances of encounter information from one or more other users.
- a reciprocal instance of encounter information is information that relates to the same encounter. Such reciprocal instances of encounter information will specify the same time and location (to within the required tolerance) of the encounter in question. However, for any particular instance of encounter information, the server might not have any reciprocal instances of encounter information. This could be because the other party to the encounter does not use the system, or did not enter the information for some reason.
- die server When triggered to do a match on a "source" instance of encounter information, die server will attempt to determine one or more matching reciprocal instances of encounter information from a large number of instances of encounter information.
- the server also might match instances of encounter information that specify the same time and location of the base encounter information, yet those instances might not be reciprocal, i.e. they might not relate to the same encounter as the base encounter information.
- the encounter information might relate to a different encounter with a coincidentally similar time and location. In this case, further filtering can be done by the server and/or users to determine the reciprocal instances of encounter information (and therefore whether communication can be established)
- the system also allows "broadcasting" of encounter information. This is where only one party enters encounter information and broadcasts it to all users to see if someone wants to respond.
- both the viewer and the person on TV enter the TV information (e.g. time and programme name) as an "encounter” and make contact. This demonstrates that an encounter need not be physical.
- the server uses the web server to provide an access point to die functionality/ services of die server 10 via the internet 11 and web browsers running on remote machines 13, 14.
- the server also has email server 1Od and sms server 1Oe and other interfaces for providing access to the server functionalities through other remote interface devices such as mobile telephones, devices and the like.
- the application server 1 Ob which forms part of the server, implements the services provided by the server though software.
- the application server operates in conjunction widi the interface servers. The interface severs' operation will be known to those skilled in the art.
- the application server 10b is adapted to receive encounter information from users of the system via any of the interface means, step 20. It will receive uiis encounter information via the appropriate interfaces as and when users of the system desire to use die system. Upon receiving an instance of encounter information, the application server 1 Ob will store the encounter information in a database, step 21.
- the encounter information will comprise location of the corresponding encounter (which may be a geographical location, specified in any suitable text, visual, ID code or other form) and time information.
- the geographical location information specifies the geographical location of die encounter.
- the time comprises the time of the encounter or die date of the encounter or both the time and date of the encounter.
- the term "time" can therefore broadly be considered to cover time and date where appropriate. It will be appreciated that the time and location information received from the user will be based on the user's perception of die encounter, and therefore may not be entirely accurate.
- the received encounter information will also comprise information identifying an associated party, being a party to the encounter. This may or may not be the same as the entity actually providing the information that is received by the server. For example, a third party might enter encounter information for an encounter experienced by another party. Typically, the encounter information will be related to the information experienced by one of the parties to the encounter. Information received from one or more other parties to the encounter may be similar but not exactly the same, due to differing experiences or perceptions of the time,
- the encounter information may optionally comprise other identifying information, such as the name of die person, details of the encounter, activities that occurred during the encounter, clothes or other distinguishing features of the parties, security questions and any other suitable information.
- Any of the encounter information may be specified as an exact portion of data, or a range of data.
- the time and location might be entered as a range to allow for tolerance or inaccuracies.
- the time might be specified as 9:30-9:45 am, and/or the location might be Queen street/Vulcan lane.
- the location might be specified as a suburb or region or other area, to allow for an easier match. Or, it could be specific to a house, building business or other location.
- an ID location code could be used.
- and particular restaurant might have an office ID location code for use with the system. This means a user does not need to know the actual address.
- Instances of encounter information will be received by the server in an ad hoc manner, as and when parties to encounters decide to enter the corresponding encounter information.
- the server is simply receiving encounter information and storing it for later processing.
- the server can be triggered by a user to find a match to source instance of encounter information, step 22.
- This may be an encounter that the user has personally been involved in as a party, or some other encounter that they have an association with. Triggering a search to find reciprocal encounter information could happen in any suitable manner. It may happen at the time of the user entering the encounter information, or it may happen at a later time, and may form part of the encounter information entry process or as a separate process. It should be noted that at the time of entering encounter information, the reciprocal encounter information from one or more other users may not yet have been entered, so any attempt to find that reciprocal encounter information may not be successful at that point in time. Therefore, it may be necessary to instigate a search at a later stage when such information may have been entered.
- the server 10 Upon receiving an instruction from a user to carry out a match, the server 10 does the following to find matching information, step 23. First, it identifies the relevant encounter information for the party triggers the match process — this will be the information they entered. This becomes the source encounter information. It then searches through its database for any previously received encounter information from other users that may match the source encounter information. An instance of encounter information in the database matches the source encounter information if there is some correlation between the two. The correlation might occur, for example, when the times and location of specified by both instances of encounter information (source and potential match) match to within a degree of tolerance (or exacdy) depending on settings. A match might only require correlation between the key bits of information, such as location and time, or alternatively, all the encounter information.
- the instance When an instance of encounter information in the database is determined to match or correlate with the source encounter information, the instance is flagged up as a possible match. That is, the instance found in the database may be reciprocal encounter information to the source encounter information. This does not necessarily mean that the party associated with that flagged encounter information is the person or associated party to the encounter in question. It could be that the matched encounter information specifies an unrelated encounter, but by coincidence had a similar time and location.
- the server will find all encounter information matches, irrespective of whether they are an instance of reciprocal encounter information or not. These are conveyed to the user initiating the match process, step 25.
- a filter process either by the application server and/or actions by the user can reduce the matched encounter information to those that are or are more likely to be related to the encounter in question, step 24. Alternatively, all the potential matches might be provided and the user can determine through other means which are relevant.
- the server 10 can then receive input from the user indicating which of the instances of matched encounter information might actually relate to the encounter in question. At that point the server can facilitate contact between the associated parties to the selected encounter information, step 26. This can either be directly through the server, for example through chat rooms or the like, or alternatively and/or by facilitating transfer of contact information.
- the application server 1Od runs software (see Figure 3) that provides the services and functionality of the system 1. In particular it provides for the interaction and transfer of data between a remote user and the server, and the backing processing for matching encounter information.
- the software comprises a user interface layer. This comprises a service to download email messages 30, a web service 31 for integration with the internet, a website user interface 32 that provides for interaction with a user over a pc and browser. It also comprises a geo-coding service/http/xml functionality 33.
- the software also comprises a business logic layer. This comprises the following objects /modules: static objects 34, error handling 36, session handlers 35 , global helper functions 37, moments (encounter information) 38, members 39 and a geo-transform 27.
- the software comprises a data access module 28 and an SQL database 29. This is where the encounter information is stored.
- Figure 4 shows the method for receiving information at the server from a remote PC running a browser connected to the server via the internet.
- the browser will open up a session between a server and download information from the server to provide a user interface for interaction with the server, step 40. Through this interface, the user can create logins, enter encounter information and trigger the matching process.
- the encounter information is entered on a form, step 41 , and upon submission, step 42, this information is transferred over the internet and received by the server application.
- the information is retrieved and processed by the server application, step 43.
- the encounter information defines a "moment" (which is the encounter). If the location is specified by a location ID code, then the moment is created directly, step 45 and the encounter information defining that moment is stored, step 51. If, alternatively, the location is specified by an address or other geographical information, then the details are reverse geo-coded, step 44. If this results in a single result then the location information is stored along with the other encounter information, steps 47, 51.
- geographical location options are created and conveyed to the user over the internet, via email, step 49, via text message, step 48, or via any other suitable means, step 46.
- a selection can then be made by the user either through text or email, step 50, and the selected location along with the other encounter information is stored, step 51.
- the information could be received by a text message or sms gateway process from a mobile telephone in Figure 5.
- the encounter information is sent via a text message and comprises a location (either as an address, a location ID or geographical indication) and the time, step 52.
- This encounter information is received via a gateway, step 53, and then the information or data is processed and sent via email to the server, step 54.
- the server retrieves the email and processes this information, step 55. If the location is specified by a location ID code, then the moment is created directly, step 45, and the encounter information defining that moment is stored, step 51. If, alternatively, the location is specified by an address or geographical indication, then the details are reverse geo-coded, step 44.
- step 47 the location information is stored along with the other encounter information, step 51. If multiple results are found, geographical location options are created and conveyed to the user over the internet, via email, step 46, via text message, step 48. or via any other suitable means. A selection can then be made by the user, step 50, and the selected location along with the_other encounter information is stored, step 51.
- Figure 6 shows one possible matching process that occurs to identify encounter information instances that correlate to the encounter information forming the basis of the match.
- the matching process occurs immediately after encounter information is entered, although this is not essential. It could happen at another time upon trigger from the user, step 60.
- the server application will search the database, step 61, for matches being encounter information instances that specify a location and time that is within 15 minutes and 500 metres radius of the basis encounter information, step 62.
- Any suitable algorithm could be used to make this match.
- the algorithm might involve searching for all encounter information instances which have times that fall within the specified tolerance (in this case 15 minutes), and then of those, searching for encounter information instances in which the location is within a 500 metre radius. The reverse could be done, wherein the filter via the location radius is done first. Any other suitable tolerances and/or algorithms could be used, and matching could be done on other information in addition.
- step 63 If an instance of encounter information correlates to the source information, it is flagged as a match, step 63. If not, it is discarded as not relevant, step 64.
- the system then processes/parses the next instance of encounter information in the database, if there is any further such information, step 65. This process is done until all encounter information is parsed.
- the flagged matches are then conveyed to the user, step 66. From here they can select appropriate matches and the contact facilitation process can occur.
- a first embodiment of the invention will be described from a user perspective as shown in Figures 7-19.
- the embodiment will be described with reference to an example encounter. This example will relate to an encounter between Jack and Matt; two people who used to work together but have lost contact. They briefly saw each other- across the street in Downtown Auckland on the morning of 22 August 2008.
- the user accesses the system via a user interface on a PC.
- First a user can register on the system (if they have not already done so) by providing their contact details 70 as shown in Figure 7. Details are shown for_a new user "Jack".
- a summary page 80 shows all the encounters entered by the user, Figure 8. In this case there are none.
- the user, Jack can then enter encounter information specifying an encounter ("moment") at any appropriate time. They do this by clicking on the "new moment" icon 81 in the encounter summary page.
- a screen 90 (see Figure 9) that comprises a map 91 or other representation of a relevant geographical area.
- the map can be manipulated (by panning and/or zooming) to display the relevant area of the encounter.
- the user Jack can then put a flag 92 at the location of the encounter along with the time in the appropriate fields 93. In this case, the location is "Queen Street” and the time (that is, date and time) is 22 August 2008 at 9:15 am.
- Jack can then enter further information 95 relating to the encounter as shown in Figure 10. He can indicate what he was wearing (a baseball cap), what Matt was wearing (a t-shirt), and the type of relationship they are looking for (in this case business). Other useful information could also be entered, for example a situation quote.
- a security/identification/challenge question can also be entered as shown along with the answer. Here, Jack has asked where they used to work, the answer being "Post Office". The security question will assist in ensuring the system only facilitates contact between people who genuinely were part of the encounter. The information will then be stored in the server database. The information entered in the screens on Figures 9, 10 constitutes encounter information. When the encounter information is stored, Jack will be recorded as the associated party to the encounter information.
- the server application will then automatically search for other instances of encounter information that match Jack's encounter information just entered.
- the default situation is that the server will search for any other encounter information that has a location within 500 metres of Jack's entered location and within 15 minutes of his entered time.
- a screen is then displayed 110, as shown in Figure 11 , that indicates any instances of encounter information that match Jack's encounter information. As can be seen there are no matches. This is because Matt has not yet entered his reciprocal encounter information, and also because there are no other unrelated instances of encounter information matching Jack's that have been previously entered by parties.
- a slider 111 is shown that enables the matching tolerance for the time of encounter to be extended or contracted from the default of 15 minutes.
- Figure 13b Matt is already registered as a user. Matt then creates an encounter moment, step 130. He does the following to do so. As shown in Figure 13a, he opens the encounter creation screen 90 and enters the time 93 (22 August 2008, 9:35am) of the encounter, and also indicates the location 97 on the map 91. The zoom and pan of the map may also be increased to capture more or fewer locations by expanding the radius shown on the screen. It will noted in this case Matt enters the time of 9.35am, which is 20 minutes after Jack's entered time. This might not be unusual as both parties might not be entirely aware or may not have an accurate recollection of the time of meeting.
- Matt can then also enter encounter information 95 relating to what he was wearing, what Jack was wearing and a situation quote which is "I passed you on the other side of the street". He enters a security question, which is in essence the same as Jack's although it does not necessarily have to be.
- step 131 Upon entering the encounter information the system is automatically triggered to look for matches, step 131. Initially a screen will be shown but no match will be found. This is because Matt's entered time and Jack's entered time differ by more than the default 15 minutes. But, matt can manipulate the matching criteria, step 134. If Matt adjusts the time slider as shown in Figure 15 to 21 minutes this will extend the time search back to 9.14am. Jack's entered time will dierefore fall within this range of times.
- the server is receiving information on the relevant locations and triangulating the results and displaying the on the map, steps 135, 136. As can be seen in Figure 15, Jack's reciprocal instance of encounter information 92 is now marked on the map. In general, all "rough" matches will be displayed, step 132.
- any "close” matches can be sent via an opt in email to other waiting users, step 133. It should be noted that while the encounter matching is triggered upon entering the encounter information, this is not necessary. The encounter matching could be triggered at some other time by a separate process.
- Matt's entered encounter information is shown on his summary page 180.
- the number of encounter information matches that appear on the geographical map can be reduced by manipulating die slider to reduce die number of "hits" therefore making the review of the encounter information easier.
- the number of encounter hits could be reduced by reducing the search area by manipulating the zoom/pan on the map.
- FIG. 7-18 utilises a graphical user interface on a web browser. It will be appreciated that this could be provided at any suitable manner, for example on a PC or via a suitably adapted mobile telephone or other mobile device. Alternatively, the information could be provided in text or graphical form via a mobile phone using some other suitable type of protocol, such as text messaging, GPRS or the like.
- the system might also be adapted to provide a broadcast function, as shown in Figure 19.
- This function is useful where, for example a person may have seen someone they wish to contact, but it is unlikely that that person will not have recognised or known the first person and therefore is unlikely to enter encounter information. Therefore, the first person can broadcast to see if that person might decide to make contact, or a person who knows them might pass on the message to make contact.
- a user creates an encounter information instance (moment), step 190, and dien chooses the broadcast functionality, step 191. It can also specify a window or tolerance of time, a radius of search and also a message, step 192.
- matches are found of people who have entered encounter information instances that match that moment, step 193.
- the system then broadcasts to those people. This can be done by either sending an email message, step 195, to those who have opted in to the broadcast function, or a text message, step 196 or some other suitable means. If the user who receives the email, text or other message is die person in question being sought then that user can respond to a link, step 198, or respond widi a text message, step
- step 200 to create a match, step 200, and then be put in contact.
- that person may forward the message, step 194 or step 197, to someone who they believe is the person being sought. That person might say we received the email or text can respond in the suitable manner.
- the broadcast may be sent only to those who have entered encounter information that matches the source encounter information.
- the plead may be sent to all those who have opted in to this functionality, irrespective of whether they have entered encounter information that is relevant or not.
- the server uses a graphical interface 100 illustrated in Figure 1 to allow a user to enter information on a person or persons they have met. It is assumed that users using the system have created an account using known online account creation systems. Other features such as address verification may be used. Users may be charged for the service offered by the present system.
- the user interface 100 presented to a user On a web browser is an adaptation of known graphical mapping software such as Google earth, AA road mapping, or Wises Street mapping.
- die server 1701 stores records according to x and y coordinates with a time range as a third 'coordinate'. This combination of data enables the system to display graphical maps 102 with the addition of event data 101. This display can be refined according to a specific date or date range as seen in Figure 21
- the server 1701 Once the server 1701 has authenticated the user against stored registration data the authenticated user may enter a meeting or contact, the server 1701 presents the user with graphical maps 102 as illustrated in Figure 21 and Figure 20. The server 1701 then provides navigation tools so the user can select the location that a meeting took place. Once a user has selected a location on the map 102 the server 1701 records this location. In cases where the mapping software is not sufficiently granular such that the exact location cannot be pinpointed, the server 1701 creates a location range as selected by the user or according to pre-defined system defaults. The server 1701 then prompts die user to input a date and time range and records the input.
- the server 1701 can prompt the user to select whether this marker will be visible to all users or only to those who subsequently enter corresponding time and location data and, optionally, corresponding miscellaneous information, such as a password or the answer to the secret question known to both parties.
- the server 1701 records and stores the selection.
- the number of days 201 the record is stored for is received from the user.
- the server 1701 compares the data to data that it has captured and stored previously and, where the location (latitude and longitude range) and time range correspond, displays the corresponding data in the form of a marker 101 containing the miscellaneous data.
- Each user is then able to review this marker 101 and miscellaneous data and, should they wish to proceed with an exchange of contact details, click on the marker. Markers 101 are illustrated in Figure 20 and Figure 21.
- the server 1701 then records the match and sends notification to the corresponding user that it has captured matching data.
- the server 1701 When the corresponding user then visits the web site the server 1701 will display both markers, as seen in Figure 24. .
- the server 1701 records this and sends each user the others contact details via the users preferred means.
- the matching data 401, 402 can be displayed on the graphical user interface as seen in Figure 24, via an email as seen in Figure 29 or via SMS as seen in Figure 34.
- the data 502,503 For a user who had previously authorised a contact and was awaiting authorisation from the other party the data 502,503 will be displayed as illustrated in Figure 25 on the web interface. Alternatively or additionally the data may be sent via email as illustrated in Figure 29, or SMS as illustrated in Figure 35.
- the server 1701 can display graphical maps according to a user specified, or system defaulted time range.
- the server 1701 will display markers containing user specified information corresponding to a specific location and time range where the user has specified that it may be displayed to all users.
- the server 1701 records where users have specified that markers may only be viewed by other users who have entered data for corresponding locations and time ranges. SMS Input
- a user many also use a mobile telephone to interface with the present invention.
- Registration in the case of a user using a mobile telephone may be via the web site or via a registration agent. Users may use both the mobile and web interface of the present invention.
- mobile phone users send SMS messages containing authentication and meeting data, including location, time and miscellaneous data, to a predefined number which diverts the data to an SMS gateway.
- An example SMS message 1201 can be seen in Figure 32.
- the server 1701 receives this data via the SMS gateway or via an interface file and authenticates the sender by comparing the data to stored registration data. Authentication may be via the mobile number of the mobile device identification number. Upon authentication, the server 1701 parses the data.
- server 1701 When searching die server 1701 then compares this record to previously created records. Whenever the server 1701 matches records based on time range, location and miscellaneous data, the server 1701 creates a match record and assigns a unique match code. If the server 1701 finds more than a predefined number of matching records then the server 1701 will generate a text message 1601 illustrated in Figure 36 to inform the user to resend their meeting data with more miscellaneous data or a shorter time range.
- SMS message 1401 contains both sets of location and miscellaneous data and the unique match code.
- the server 1701 stores it and the data is searched according to latitude and longitude extracted from the graphical software.
- the system searches within a range as different users may not select the exact same latitude and longitude position.
- each word is a meta-tag and the record is stored and searched by these meta-tags.
- users entering data via the web interface are provided with an option to enter free form key word data to describe the location 203 specifically to match SMS entries. This will allow the server to match the meta-tags.
- the server may provide suggested key words based on the location selected by the user.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Entrepreneurship & Innovation (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Strategic Management (AREA)
- Databases & Information Systems (AREA)
- Remote Sensing (AREA)
- General Engineering & Computer Science (AREA)
- Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
Claims
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2008293140A AU2008293140A1 (en) | 2007-08-31 | 2008-08-29 | Contact system and method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
NZ561111 | 2007-08-31 | ||
NZ561111A NZ561111A (en) | 2007-08-31 | 2007-08-31 | Contact system and method |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2009028970A1 true WO2009028970A1 (en) | 2009-03-05 |
WO2009028970A9 WO2009028970A9 (en) | 2009-07-09 |
Family
ID=40387524
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/NZ2008/000226 WO2009028970A1 (en) | 2007-08-31 | 2008-08-29 | Contact system and method |
Country Status (3)
Country | Link |
---|---|
AU (1) | AU2008293140A1 (en) |
NZ (1) | NZ561111A (en) |
WO (1) | WO2009028970A1 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2011011809A1 (en) * | 2009-07-30 | 2011-02-03 | Handbury Nominees Pty Ltd | Method, apparatus and system for arranging a meeting |
WO2011116505A1 (en) * | 2010-03-26 | 2011-09-29 | Nokia Corporation | A method, devices and a system for communication |
NL1040977B1 (en) * | 2014-10-01 | 2016-10-03 | Peterus Leonardus Klerkx Stephanus | Method for establishing further contact between two people as a result of a meeting between the two of them at a specific meeting location and time. |
WO2022135772A1 (en) * | 2020-12-22 | 2022-06-30 | Relayts Ug | Computer-implemented communications system having syntax-free and user-controlled producible and manageable address features |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080270908A1 (en) * | 2007-04-26 | 2008-10-30 | David Hope | Systems And Methods For Contacting An Acquaintance |
-
2007
- 2007-08-31 NZ NZ561111A patent/NZ561111A/en not_active IP Right Cessation
-
2008
- 2008-08-29 WO PCT/NZ2008/000226 patent/WO2009028970A1/en active Application Filing
- 2008-08-29 AU AU2008293140A patent/AU2008293140A1/en not_active Abandoned
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080270908A1 (en) * | 2007-04-26 | 2008-10-30 | David Hope | Systems And Methods For Contacting An Acquaintance |
Non-Patent Citations (2)
Title |
---|
30 August 2007 (2007-08-30), WAYBACK ENGINE, Retrieved from the Internet <URL:Http://web.archive.org/web/20070830155424/http://www.facebook.com> [retrieved on 20081117] * |
9 June 2005 (2005-06-09), WAYBACK ENGINE, Retrieved from the Internet <URL:http://web.archive.org/web/20050609075240/http://www.aftertheclub.co.uk/people-finder.asp> [retrieved on 20081117] * |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2011011809A1 (en) * | 2009-07-30 | 2011-02-03 | Handbury Nominees Pty Ltd | Method, apparatus and system for arranging a meeting |
WO2011116505A1 (en) * | 2010-03-26 | 2011-09-29 | Nokia Corporation | A method, devices and a system for communication |
CN102835074A (en) * | 2010-03-26 | 2012-12-19 | 诺基亚公司 | A method, devices and a system for communication |
NL1040977B1 (en) * | 2014-10-01 | 2016-10-03 | Peterus Leonardus Klerkx Stephanus | Method for establishing further contact between two people as a result of a meeting between the two of them at a specific meeting location and time. |
WO2022135772A1 (en) * | 2020-12-22 | 2022-06-30 | Relayts Ug | Computer-implemented communications system having syntax-free and user-controlled producible and manageable address features |
Also Published As
Publication number | Publication date |
---|---|
NZ561111A (en) | 2010-02-26 |
AU2008293140A1 (en) | 2009-03-05 |
WO2009028970A9 (en) | 2009-07-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11831595B2 (en) | Methods, systems, and devices for generating a unique electronic communications account based on a physical address and applications thereof | |
US20190155426A1 (en) | Method, System, and Graphical User Interface for Meeting-Spot- Related Introductions | |
US9071932B2 (en) | Focused and semi-private location based asynchronous thread communications | |
US7797642B1 (en) | Method, system, and graphical user interface for meeting-spot-related contact lists | |
US20180032535A1 (en) | System and Method for Alerting a First Mobile Data Processing System Nearby a Second Mobile Data Processing System | |
US20090319361A1 (en) | Web-based communication system | |
US20210133679A1 (en) | System and method of optimizing the routing and delivery of services and goods, and notifications related to same | |
US20140057591A1 (en) | System for providing alerts to members of defined local geographical groups | |
CN100450266C (en) | Location determining system for wireless network and associated methods | |
Weld et al. | eKichabi: information access through basic mobile phones in rural Tanzania | |
US10805387B2 (en) | Multiple-network-community management system and method of managing multiple network communities | |
US20180276618A1 (en) | Mobile app connecting employee and employer through gps | |
WO2009028970A9 (en) | Contact system and method | |
US20180352428A1 (en) | Reporting service hybrid web/mobile application platform system and methods | |
US20110055340A1 (en) | Mobile Social Networking Systems and Methods | |
US20190102847A1 (en) | System and method for connecting a potential buyer and an available realtor in real time | |
US11483169B2 (en) | Automated message recipient identification with dynamic tag | |
KR100714191B1 (en) | A location-based messenger system, and a method for providing a service thereof | |
CA3147119A1 (en) | System and method for facilitating contact between parties | |
FR3040579A1 (en) | METHOD AND SYSTEM FOR SOCIAL RELATIONSHIP ANONYMOUS AND SECURE AT EVENT | |
WO2018161105A1 (en) | Shared contextual data transfer between preconfigured location devices | |
US20230130143A1 (en) | Real estate search and transaction system and method | |
JP4736945B2 (en) | Status information management system and status information management server | |
KR101572680B1 (en) | Location-based searching service system and method | |
KR20010104806A (en) | Question / answer method using internet |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 08828637 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2008293140 Country of ref document: AU |
|
ENP | Entry into the national phase |
Ref document number: 2008293140 Country of ref document: AU Date of ref document: 20080829 Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112 (1) EPC (EPO FORM 1205A DATED 29/06/2010) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 08828637 Country of ref document: EP Kind code of ref document: A1 |