WO2019070618A1 - Methods, devices, and systems for identifying common interests and needs of mobile device users - Google Patents

Abstract

The present invention relates to a web application, a mobile device application and a backbone infrastructure. In particular, methods, devices and systems are provided for providing a connection to at least two users of a plurality of users to facilitate planning a mutual activity. The method includes receiving profile information from a plurality of users, receiving a first preferred activity from a first user of the plurality of users, receiving a second preferred activity from a second user of the plurality of users, determining a match between the first preferred activity and the second preferred activity, and establishing a connection between a first mobile device of the first user and a second mobile device of the second user.

Description

DESCRIPTION

METHODS, DEVICES, AND SYSTEMS FOR IDENTIFYING COMMON

INTERESTS AND NEEDS OF MOBILE DEVICE USERS

PRIORITY CLAIM

[0001] This application claims benefit and priority to U.S. Provisional Patent Application Serial No. 62/673,241 entitled "METHODS, DEVICES, AND SYSTEMS FOR IDENTIFYING COMMON INTERESTS AND NEEDS OF MOBILE DEVICE USERS," (Attorney Docket No. 808/5 PROV) filed May 18, 2018; U.S. Provisional Patent Application Serial No. 62/598,700 entitled "METHODS, DEVICES, AND SYSTEMS FOR IDENTIFYING COMMON INTERESTS AND NEEDS OF MOBILE DEVICE USERS," (Attorney Docket No. 808/4 PROV) filed December 14, 2017; and U.S. Provisional Patent Application Serial No. 62/566,707 entitled "METHODS, DEVICES, AND SYSTEMS FOR IDENTIFYING COMMON INTERESTS AND NEEDS OF MOBILE DEVICE USERS," (Attorney Docket No. 808/3 PROV) filed October 2, 2017 the contents of all of which are incorporated by reference in their entirety.

TECHNICAL FIELD

[0002] The present invention relates to a web application, a mobile device application, and a backend infrastructure; and more specifically to methods, devices, and systems for providing a plurality of users a connection for facilitating planning of a mutual activity.

BACKGROUND

[0003] The popularity of social networking, professional networking, and the on-line marketplace continues to grow. Specifically, mobile users (e.g. smartphone and tablet users) are looking for better ways to meet the right person or group, plan mutual activities, and reduce costs of such activities. Accordingly, a need exists to better facilitate connections between social networking users for efficiently planning a mutual activity including reducing cost via sharing of nonmonetary offers and/or monetary offers. SUMMARY

[0004] The presently disclosed subject matter is directed toward a web application, a mobile device application, and a backend infrastructure. Specifically, methods, devices, and systems are disclosed for solving the problem of facilitating connections between social networking users for efficiently planning a mutual activity including reducing cost via sharing of nonmonetary offers and/or monetary offers.

[0005] According to one embodiment, a method is implemented on a server for providing at least two users of a plurality of users a connection for facilitating a planning of a mutual activity. The method includes receiving profile information from the plurality of users, receiving a first preferred activity from a first user of the plurality of users, receiving a second preferred activity from a second user of the plurality of users, determining a match of the first preferred activity and the second preferred activity, and establishing a connection between a first computing device associated with the first user and a second computing device associated with the second user.

[0006] In some embodiments, the first preferred activity may be a first offer of sharing costs of the mutual activity, and the method may further include transmitting the first offer to the second computing device. The second preferred activity may be a second offer of sharing costs of the mutual activity, and the method may further include receiving the second offer from the second computing device.

[0007] In some embodiments, the method may further include transmitting a plurality of offers to the second computing device and the plurality of offers may be categorized within a plurality of tiers. The plurality of tiers may include a first local activity tier and a second travel based activity tier, wherein each user offers a nonmonetary incentive to facilitate the mutual activity. The plurality of tiers may include a third tier wherein at least one user offers a nonmonetary incentive to facilitate the mutual activity. The plurality of tiers may also include a fourth tier wherein at least two users offer sharing monetary costs to facilitate the mutual activity.

[0008] In some embodiments, the mutual activity may be attending an event. The event may be a concert, a movie, a play, a political rally, a sporting event, a festival, or the like. The mutual activity may be a self -participation activity. The self -participation activity may be hiking, fishing, hunting, shopping, baseball, softball, football, soccer, volleyball, skydiving, surfing, skiing, swimming, visiting a museum, bar hopping, clubbing, dancing, visiting a zoo, taking a tour, taking a cruise, or the like.

[0009] In some embodiments, the method may further include receiving a first offer from the first user for facilitating the mutual activity and receiving a second offer from the second user for facilitating the mutual activity. The first offer may be at least one of a ticket to the event, shared transportation to the event, shared lodging to attend the event, and/or a shared meal on or after the event.

[0010] In some embodiments, first computing device may be a smart phone, a tablet, a laptop, a personal computer, or the like. The second computing device may also be a smart phone, a tablet, a laptop, a personal computer, or the like.

[0011] In some embodiments, the server may be a virtual server hosted in a cloud computing environment and the server may provide a secure web portal for a graphical user interface (GUI) of the second computing device.

[0012] In some embodiments, the GUI may be provided by an application specific program. The application specific program may be an iOS® app, an Android® OS app, or the like. In other embodiments, the GUI may be provided by a web browser. The web browser may be a Microsoft Internet Explorer® browser, a Microsoft Edge® browser, an Apple Safari® browser, a Google Chrome® browser, a Mozilla Firefox® browser, an Opera® browser, or the like.

[0013] According to another embodiment, a server for provides at least two users of a plurality of users a connection for facilitating a planning of a mutual activity. The server includes a processor coupled with a database and a memory. The processor is configured for receiving profile information from the plurality of users, receiving a first preferred activity from a first user of the plurality of users, receiving a second preferred activity from a second user of the plurality of users, determining a match of the first preferred activity and the second preferred activity, and establishing a connection between a first computing device associated with the first user and a second computing device associated with the second user.

[0014] According to another embodiment, a non-transitory computer readable medium includes a plurality of machine-readable instructions. The machine-readable instructions when executed by one or more processors of a server are adapted to cause the server to perform a method server for providing at least two users of a plurality of users a connection for facilitating a planning of a mutual activity. The method includes receiving profile information from the plurality of users, receiving a first preferred activity from a first user of the plurality of users, receiving a second preferred activity from a second user of the plurality of users, determining a match of the first preferred activity and the second preferred activity, and establishing a connection between a first computing device associated with the first user and a second computing device associated with the second user.

[0015] According to another embodiment, a method is implemented on a server. The method includes identifying interface requirements for a set of services to be implemented between service oriented architecture (SOA) front end components and SOA back end components. At least one of the SOA back end components is configured to communicate with at least one of a social networking system, a professional networking system, and/or an on-line marketplace system. At least one of the SOA front end components is configured to communicate with a GUI. The SOA front end components are operable to be combined with the SOA back end components to form an operable SOA solution for providing at least two users of a plurality of users a connection for facilitating a planning of a mutual activity. The operable SOA solution provides a method including receiving profile information from the plurality of users, receiving a first preferred activity from a first user of the plurality of users, receiving a second preferred activity from a second user of the plurality of users, determining a match of the first preferred activity and the second preferred activity, and establishing a connection between a first computing device associated with the first user and a second computing device associated with the second user.

[0016] According to another embodiment, a server includes a processor coupled with a database and a memory. The processor is configured for identifying interface requirements for a set of services to be implemented between service oriented architecture (SOA) front end components and SOA back end components. At least one of the SOA back end components is configured to communicate with at least one of a social networking system, a professional networking system, and an on-line marketplace system. At least one of the SOA front end components is configured to communicate with a GUI. The SOA front end components are operable to be combined with the SOA back end components to form an operable SOA solution for providing at least two users of a plurality of users a connection for facilitating a planning of a mutual activity. The operable SOA solution provides a method including receiving profile information from the plurality of users, receiving a first preferred activity from a first user of the plurality of users, receiving a second preferred activity from a second user of the plurality of users, determining a match of the first preferred activity and the second preferred activity, and establishing a connection between a first computing device associated with the first user and a second computing device associated with the second user.

[0017] According to another embodiment, a non-transitory computer readable medium includes a plurality of machine-readable instructions which when executed by one or more processors of a server are adapted to cause the server to perform a method including identifying interface requirements for a set of services to be implemented between service oriented architecture (SOA) front end components and SOA back end components. At least one of the SOA back end components is configured to communicate with at least one of a social networking system, a professional networking system, and an on-line marketplace system. At least one of the SOA front end components is configured to communicate with a GUI. The SOA front end components are operable to be combined with the SOA back end components to form an operable SOA solution for providing at least two users of a plurality of users a connection for facilitating a planning of a mutual activity. The operable SOA solution provides a method including receiving profile information from the plurality of users, receiving a first preferred activity from a first user of the plurality of users, receiving a second preferred activity from a second user of the plurality of users, determining a match of the first preferred activity and the second preferred activity, and establishing a connection between a first computing device associated with the first user and a second computing device associated with the second user.

BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The present embodiments are illustrated by way of example and are not intended to be limited by the figures of the accompanying drawings. In the drawings:

[0019] FIG. 1 illustrates a flow chart for a method for the KAYU® system implemented on a server for providing at least two users of a plurality of users a connection for facilitating a planning of a mutual activity in accordance with embodiments of the present disclosure. [0020] FIG. 2 illustrates a system as a preferred embodiment of the KAYU® system in accordance with embodiments of the present disclosure.

[0021] FIG. 3 illustrates a smart phone and device graphical user interface (GUI) in accordance with embodiments of the present disclosure.

[0022] FIG. 4A illustrates a GUI representing one embodiment of a home page of a typical user in accordance with embodiments of the present disclosure.

[0023] FIG. 4B illustrates another GUI representing one embodiment of a profile editing page for the typical user in accordance with embodiments of the present disclosure.

[0024] FIG. 4C illustrates another GUI representing another embodiment of a profile editing page for the typical user in accordance with embodiments of the present disclosure.

[0025] FIG. 5 illustrates another GUI representing a settings page of the typical user in accordance with embodiments of the present disclosure.

[0026] FIG. 6A illustrates another GUI representing one embodiment of a messaging application in accordance with embodiments of the present disclosure.

[0027] FIG. 6B illustrates another GUI representing another embodiment of the messaging application in accordance with embodiments of the present disclosure.

[0028] FIG. 7 illustrates a block diagram of a server for hosting at least a portion of the system in accordance with embodiments of the present disclosure.

[0029] FIG. 8 illustrates a block diagram of an example of a personal computer in accordance with embodiments of the present disclosure.

[0030] FIG. 9 illustrates a block diagram of a smartphone in accordance with embodiments of the present disclosure.

[0031] FIG. 10A illustrates a GUI providing the typical user a method to select another user to message in accordance with embodiments of the present disclosure.

[0032] FIG. 10B illustrates a GUI providing the user a method to accept or decline a message request in accordance with embodiments of the present disclosure. [0033] FIG. 11 A illustrates a diagram wherein two users match and plan a mutual activity in accordance with embodiments of the present disclosure.

[0034] FIG. 11B illustrates another diagram wherein a host user is matched with a hosted user for a monetary exchange in accordance with embodiments of the present disclosure.

[0035] FIG. l lC illustrates another diagram wherein a host user is matched with a hosted user for a nonmonetary exchange in accordance with embodiments of the present disclosure.

[0036] FIG. 1 ID illustrates another diagram wherein a first user is matched with a second user to share lodging costs in accordance with embodiments of the present disclosure.

[0037] FIG. 12 illustrates a diagram of a service oriented architecture (SOA) in accordance with embodiments of the present disclosure.

[0038] FIG. 13 through FIG. 60 illustrate additional GUI diagrams of the KAYU® system in accordance with embodiments of the present disclosure.

DETAILED DESCRIPTION

[0039] The following description and drawings are illustrative and are not to be construed as limiting. Numerous specific details are described to provide a thorough understanding of the disclosure. However, in certain instances, well-known or conventional details are not described in order to avoid obscuring the description.

[0040] Reference in this specification to "one embodiment" 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 disclosure. The appearances of the phrase "in one embodiment" in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others. Similarly, various requirements are described which may be requirements for some embodiments but not for other embodiments.

[0041] The terms used in this specification generally have their ordinary meanings in the art, within the context of the disclosure, and in the specific context where each term is used. Certain terms that are used to describe the disclosure are discussed below, or elsewhere in the specification, to provide additional guidance to the practitioner regarding the description of the disclosure. For convenience, certain terms may be highlighted, for example using italics and/or quotation marks. The use of highlighting has no influence on the scope and meaning of a term; the scope and meaning of a term is the same, in the same context, whether or not it is highlighted. It will be appreciated that same thing can be said in more than one way.

[0042] Consequently, alternative language and synonyms may be used for any one or more of the terms discussed herein, nor is any special significance to be placed upon whether or not a term is elaborated or discussed herein. Synonyms for certain terms are provided. A recital of one or more synonyms does not exclude the use of other synonyms. The use of examples anywhere in this specification, including examples of any terms discussed herein, is illustrative only, and is not intended to further limit the scope and meaning of the disclosure or of any exemplified term. Likewise, the disclosure is not limited to various embodiments given in this specification.

[0043] Unless otherwise indicated, all numbers expressing quantities of components, conditions, and so forth used in the specification and claims are to be understood as being modified in all instances by the term "about". Accordingly, unless indicated to the contrary, the numerical parameters set forth in the instant specification and attached claims are approximations that can vary depending upon the desired properties sought to be obtained by the presently disclosed subject matter.

[0044] Without intent to limit the scope of the disclosure, examples of instruments, apparatus, methods and their related results according to the embodiments of the present disclosure are given below. Note that titles or subtitles may be used in the examples for convenience of a reader, which in no way should limit the scope of the disclosure. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. In the case of conflict, the present document, including definitions, will control.

[0045] The KAYU® system is disclosed herein. The KAYU® system is an all- encompassing central hub (e.g. server) that facilitates users to reduce lodging costs incurred on weekend trips or short duration vacations. The KAYU® system also brings together users of mutual interests in order to help them become real life extroverts as opposed to "fake online extroverts", and in the long run develop their real life networks of friends. [0046] People (e.g. users) love to get away on the weekends. However, lodging costs keeps users from going places more often than not. So the KAYU® system allows users to utilize their networks of family and friends by staying together in order to reduce lodging costs. The KAYU® system expands users' networks to include all users with common interests resulting in planning of mutual activities.

[0047] The KAYU® system is a four tiered system bringing users closer to the activities they enjoy with significant reduction in the typical costs. The KAYU® system provides the matches and connections to facilitate the planning of the mutual activity between the users.

[0048] The KAYU® system has a first "green local tier" and a second "green travel tier". For example, with the "green local tier", a first user may locate a second user to participate in a mutual activity that interests both users. With the "green travel tier", a host user has a place for a hosted user to stay with the understanding that the hosted user will pay for a mutual activity of both users. In a specific example, a hosted user has two tickets to a Red Sox baseball game and a host user has an extra room to provide lodging for the hosted user. The mutual activity for both tiers may be an event such as a concert, a movie, a play, a political rally, a sporting event, a festival or the like. The mutual activity may be a self-participation activity. For example, the self-participation activity may be dining out, dining in, hiking, fishing, hunting, shopping, baseball, softball, football, soccer, volleyball, skydiving, surfing, skiing, swimming, visiting a museum, bar hopping, clubbing, dancing, visiting a zoo, taking a tour, taking a cruise together, or the like.

[0049] The KAYU® system has a third "blue tier". For example, a host user has a spare room. A hosted user wants to obtain a match with the host user and negotiate an agreed amount for the rental. This third "blue tier" may provide a host user a much more efficient method to rent a vacant room or residence as a last minute effort to avoid an Airbnb type of rental going vacant for a weekend.

[0050] The KAYU® system also has a fourth "orange tier". For example, two users are looking to be hosted in one location but are unable to find any vacant lodging. The KAYU® system allows the users to match, go to the location desired, and share lodging costs. The KAYU® system further allows users to be match as having mutual interests and may be likely to participate in mutual activities as with the "green local tier" and "green travel tier". [0051] The KAYU® system provides rating stars for locations, host users, and hosted users on a per activity and/or a per trip basis. For example if a host user or a hosted user gets two out of five stars on two different rating opportunities the given user may be banned or deactivated from the KAYU® system.

[0052] The KAYU® system is implemented as a client/server architecture wherein a plurality of users may communicate using their computing device with a central hub (e.g. server). The server may be a physical server or a virtual server. In other embodiments the server may be located on a company premise, or located in any other type of datacenter. The server may also be configured as a plurality of physical servers and/or virtual servers. In some embodiments, an Ubuntu® server may provide the virtual server and may be implemented as a separated operating system (OS) running on one or more physical (i.e. hardware implemented) servers. Any applicable virtual server may by be used for the Ubuntu® Server function. The Ubuntu® server may be implemented within the Microsoft Azure® cloud computing data center environment or the like.

[0053] A computing device may be a fixed device or a mobile device. For example, a fixed device may be an interactive kiosk, a personal computer, or the like. A mobile device may be any computing device capable of being transported easily from a one location to another location without undue difficulty and one that is capable of functional connection with a remote server regardless of its location. For example a mobile device may be a smart phone, a tablet, a personal digital assistant, a laptop, or the like. In general, a computing device as used with the KAYU® system may be any computing device providing a user input, display, and connectivity to one or more servers over a personal area network (PAN), a local area network (LAN) and/or a wide area network (WAN). The PAN may include Bluetooth® or Universal Serial Bus (USB). The LAN may include any combination of wired Ethernet and/or Wi-Fi access points. The WAN may include the Internet and/or another wide area private network. The WAN may also include any combination of 2G, 3G, 4G, and 5G networks. In some embodiments the WAN may include Data Over Cable Service Interface Specification (DOCSIS) networks and/or fiber networks such as passive optical networks (PONs). Access to the one or more servers may also be provided via a virtual private network (VPN) within any of the previously described networks. [0054] The KAYU® system may communicate with the computing devices via an app or through a website. In use, a user first downloads the app or goes to the website to register and log onto the KAYU® system. In some embodiments, the user registers by creating a unique ID and/or password that identifies the user in the system. The KAYU® system may be combined with mobile technology, such that a user may enter the system with a mobile device by simply going to the website and/or opening the app.

[0055] FIG. 1 illustrates a flow chart 100 of a method for the KAYU® system implemented on a server for providing at least two users of a plurality of users a connection for facilitating a planning of a mutual activity. The server may be a physical server or a virtual server hosted in a cloud computing environment, a server located on a company premise, or a server located within any other type of datacenter.

[0056] In step one 102, the server receives profile information from a plurality of users. The profile information may include a user's name, a user's nickname, a user alias specific to the system, an age of the user, and address of the user. The profile information may also include a user's preferred activities and preferences for types of events.

[0057] The profile information may be received directly from users' computing devices via a graphical user interface (GUI). In other embodiments, the profile information may be received indirectly from a third party social networking system, a professional networking system, and/or an on-line market place. For example, the profile information may be received from a Facebook®, a Linkedln®, and/or an EBay® backend interface.

[0058] In step two 104, the server receives a first preferred activity from a first user of the plurality of users. In step three 106, the server receives a second preferred activity from a second user of the plurality of users. In step four 108, the server determines a match of the first preferred activity and the second preferred activity that may result in planning of a mutual activity between the first and second users.

[0059] In step five 110, the server establishes a connection between a first device of the first user and a second device of the second user. The connection may be a text type connection such as a short message service (SMS), a multimedia messaging service (MMS), an iMessage® service, or the like. The connection may be application specific message internal to a provided app of the KAYU® system. In other embodiments the connection may be a voice and/or video connection. The voice and/or video connection may be provided directly by the KAYU® system or one or more third party applications. For example the connection may be a FaceTime® connection and/or a Voice over Internet Protocol (VoIP) connection.

[0060] Other steps not shown in FIG. 1 may include the server transmitting a plurality of offers to the second computing device. The plurality of offers may be categorized within the four tiers. Within the first two tiers, users offer a nonmonetary incentive to facilitate the mutual activity. Within the second tier, at least one user offers a nonmonetary incentive to facilitate the mutual activity. Within the fourth tier, at least two users may offer sharing monetary costs to facilitate the mutual activity.

[0061] FIG. 2 illustrates a system 200 as a preferred embodiment of the KAYU® system. The system includes a KAYU® server application 202 hosted on a server 204. The server may be resident in a cloud based computing environment 206. The server 204 may communicate with a plurality of mobile devices 208A-C, hosting a plurality of KAYU® mobile apps 210A-C. In some embodiments the server 204 may communicate with fixed devices such as an interactive kiosk, a personal computer, or the like. The KAYU® mobile apps 210A-C may also be replaced by a web browser in both the fixed and mobile devices. The mobile apps 210A-C may communicate with the KAYU® server application 202 over a network 212. The network 212 may be any type or combination of wired, wireless, or optical networks as previously described in this disclosure.

[0062] The server 204 with KAYU® server application 202 may perform any of the methods described in the summary, the claims, and the flowchart/description of FIG. 1. The KAYU® server application 202 transforms the server 204 from a generic computer function into a machine for facilitating connections between social networking users for efficiently planning a mutual activity including reducing cost via sharing of nonmonetary offers and/or monetary offers.

[0063] FIG. 3 illustrates a smart phone 300 and device graphical user interface (GUI) 302 in accordance with embodiments of the KAYU® system. The smart phone 300 may be representative of any of the mobile devices 208A-C of FIG. 2. The GUI provides a user a means of selecting preferred activities. [0064] FIG. 4A illustrates a GUI 400 representing one embodiment of a home page of a typical user (e.g. Sarah) of the KAYU® system. As shown, the typical user's first name, age, and photo are displayed. Additionally, the preferred activities of "Hiking, Shopping, Drinking" are also displayed

[0065] FIG. 4B illustrates another GUI 402 representing one embodiment of a profile editing page for the typical user (e.g. Sarah) of the KAYU® system. Profile information such as name, age, location, and preferred activities may be modified from the GUI 402. Tools to add photographs are also provided.

[0066] FIG. 4C illustrates another GUI 404 representing another embodiment of a profile editing page for the typical user (e.g. Sarah) of the KAYU® system. For example, offers such as an available house may be entered.

[0067] FIG. 5 illustrates another GUI 500 representing a settings page of the typical user (e.g. Sarah) of the KAYU® system. The GUI 500 allows the typical user to select a distance range to locate other users, to filter on gender, and search options for the multi-tier feature of the KAYU® system.

[0068] FIG. 6A illustrates another GUI 600 representing one embodiment of a messaging application within the KAYU® system. The GUI 600 may be representative of message examples the typical user (e.g. Isaac) may receive from other users (e.g. Josh, Hannah, Jerry, and Lexi).

[0069] FIG. 6B illustrates another GUI 602 representing another embodiment of the messaging application within the KAYU® system. The GUI 602 may be representative of a message thread of the typical user (e.g. Isaac) with another user (e.g. Hannah).

[0070] FIGs. 7-9 provide examples of hardware components that may be used to implement one or more portions of the system 200 for FIG. 2.

[0071] FIG. 7 illustrates a block diagram of a server 700 for hosting at least a portion of the system 200. The remote server 700 may include at least one of a processor 702, a main memory 704, a storage memory (e.g. database) 706, a datacenter network interface 708, and an administration user interface (UI) 710. The remote server 700 may be configured to host the Ubuntu® server as discussed earlier. In some embodiments Ubuntu® server may be distributed over a plurality of hardware servers using hypervisor technology.

[0072] The processor 702 may be a multi-core server class processor suitable for hardware virtualization. The processor may support at least a 64-bit architecture and a single instruction multiple data (SIMD) instruction set. The main memory 704 may include a combination of volatile memory (e.g. random access memory) and non-volatile memory (e.g. flash memory). The database 706 may include one or more hard drives.

[0073] The datacenter network interface 708 may provide one or more high-speed communication ports to the data center switches, routers, and/or network storage appliances. The datacenter network interface 708 may include high-speed optical Ethernet, InfiniBand (IB), Internet Small Computer System Interface (iSCSI), and/or Fibre Channel interfaces. The administration UI may support local and/or remote configuration of the remote server 700 by a datacenter administrator.

[0074] FIG. 8 depicts a block diagram illustrating an example of a personal computer 800. In some embodiments, the personal computer 800 may host the web application. The personal computer 800 may include at least a processor 802, a memory 804, a network interface 806, a display 808, and a user interface (UI) 810. The personal computer 800 may include an operating system (OS) to run a web browser or a computer application specific to the disclosure. The operating system (OS) may be a Windows® OS, a Macintosh® OS, a Linux® OS, or the like. The web browser may be a Microsoft Internet Explorer® browser, a Microsoft Edge® browser, an Apple Safari® browser, a Google Chrome® browser, a Mozilla Firefox® browser, an Opera® browser, or the like. The memory may include a combination of volatile memory (e.g. random access memory) and non-volatile memory (e.g., solid state drive and/or hard drives).

[0075] The network interface 806 may be a wired Ethernet interface or a Wi-Fi interface. The personal computer 800 may be configured to access remote memory (e.g. network storage and/or cloud storage) via the network interface 806. The display 808 may be an external display (e.g. computer monitor) or internal display (e.g. laptop). The UI 810 may include a keyboard, and a pointing device (e.g. mouse). [0076] FIG. 9 illustrates a block diagram of a smartphone 900 in accordance with embodiments of the present disclosure. In some embodiments, the smartphone 900 may host the web application. In some embodiments, a web browser or a mobile app specific to the disclosure may provide the user interface to the system 200. The smartphone 900 may include at least a processor 902, a memory 904, a UI 906, a display 908, WAN radios 910, LAN radios 912, and personal area network (PAN) radios 914. In some embodiments the smartphone 900 may be an iPhone® or an iPad®, using iOS® as an OS. In other embodiments the smartphone 900 may be a mobile terminal including Android® OS, BlackBerry® OS, Windows Phone® OS, or the like.

[0077] In some embodiments, the processor 902 may be a mobile processor such as the Qualcomm® Snapdragon™ mobile processor. The memory 904 may include a combination of volatile memory (e.g. random access memory) and non-volatile memory (e.g. flash memory). The memory 904 may be partially integrated with the processor 902. The UI 906 and display 908 may be integrated such as a touchpad display. The WAN radios 910 may include 2G, 3G, 4G, and/or 5G technologies. The LAN radios 912 may include Wi-Fi technologies such as 802.11a, 802.1 lb/g/n, and/or 802.11ac circuitry. The PAN radios 912 may include Bluetooth® technologies.

[0078] FIG. 10A illustrates a GUI 1000 providing the typical user a method to select another user (e.g. Lexi, Jerry, Josh, and/or Hannah) to message within the KAYU® system.

[0079] FIG. 10B illustrates a GUI 1002 providing the user a method to accept or decline a message request within the KAYU® system.

[0080] FIG. 11 A illustrates a diagram wherein two users match and plan a mutual activity (e.g. visiting the zoo) in accordance with embodiments of the present disclosure.

[0081] FIG. 11B illustrates another diagram wherein a host user is matched with a hosted user for a monetary exchange in accordance with embodiments of the present disclosure.

[0082] FIG. l lC illustrates another diagram wherein a host user is matched with a hosted user for a nonmonetary exchange in accordance with embodiments of the present disclosure. [0083] FIG. 1 ID illustrates another diagram wherein a first user is matched with a second user to share lodging costs in accordance with embodiments of the present disclosure. As a result the first and second user may plan a mutual activity via the KAYU® system.

[0084] In another embodiment, the KAYU® system may be implemented as a system 1200 as illustrated in FIG. 12, wherein middleware or more specifically a service oriented architecture (SOA) 1202 shown in accordance with embodiments of the present disclosure. The SOA 1202 includes SOA back end components 1204A-C and SOA front end components 1206A-B. The SOA 1202 also includes a user database 1208. The SOA 1202 may be implemented on a server within the cloud based computing environment 206 of system 200 of FIG. 2. The server may be a physical server or a virtual server. In other embodiments the server may be located on a company premise, or located in any other type of datacenter. The server may also be configured as a plurality of physical servers and/or virtual servers. An Ubuntu® server may provide the virtual server and may be implemented as a separated operating system (OS) running on one or more physical (i.e. hardware implemented) servers. Any applicable virtual server may by be used for the Ubuntu® Server function. The Ubuntu® server may be implemented within the Microsoft Azure® cloud computing data center environment.

[0085] The back end component 1204A may be configured to communicate with one or more professional networking systems 1210. For example, the one or more professional networking systems 1210 may include Linkedln ®, Twylah ®, Opprtunity®, TPartnerUp®, or the like. The back end component 1204A may also be implemented as a plurality of backend interfaces.

[0086] The back end component 1204B may be configured to communicate with one or more social networking systems 1212. For example, the one or more social networking systems 1212 may include Facebook®, Twitter®, Instragram®, Pinterest®, Google+®, Tumblr®, Snapchat®, or the like. The back end component 120BA may also be implemented as a plurality of backend interfaces.

[0087] The back end component 1204C may be configured to communicate with one or on-line marketplace systems 1214. For example, the one or more on-line marketplace systems 1214 may include Airbnb®, eBay®, Craigslist®, or the like. The back end component 1204C may also be implemented as a plurality of backend interfaces. [0088] The back end components 1204A-C may be coupled with the one or more professional networking systems 1210, the one or more social networking systems 1212, and/or the one or the one or more on-line marketplace systems 1214 by a combination of the Internet, wide area network (WAN) interfaces, local area network (LAN) interfaces, wired interfaces, wireless interfaces, and/or optical interfaces.

[0089] The front end component 1206A may be configured to communicate with a plurality of KAYU® apps 1216. In certain embodiments, KAYU® apps 1216 may include an iOS® app and/or or an Android® OS app. The front end component 1206B may be configured to communicate with a plurality of web browsers 1218. In certain embodiments, the web browsers 1218 may include a Microsoft Internet Explorer® browser, a Microsoft Edge® browser, an Apple Safari® browser, a Google Chrome® browser, a Mozilla Firefox® browser, and/or an Opera® browser. . The KAYU® apps 1216 and/or web browsers 1218 may provide any of the previously disclosed GUIs and functionality as described in this application.

[0090] The front end components 1204A-B may be coupled with KAYU® apps and/or the web browsers 1218 by a combination of the Internet, wide area network (WAN) interfaces, local area network (LAN) interfaces, wired interfaces, wireless interfaces, and/or optical interfaces.

[0091] The user database 1208 may be configured to synchronize with at least one of the professional networking systems 1210, the social networking systems 1212, and the on-line marketplace systems 1214. The synchronization process may provide profile information for a plurality of users to the user database 1208. In some embodiments, the user database 1208 may be an open source database such as the PostgreSQL® database.

[0092] The SOA front end components 1204A-B are operable to be combined with the SOA back end components 1204A-C to form an operable SOA solution for providing at least two of a plurality of users a connection for facilitating planning of a mutual activity. The SOA solution may include a method comprising receiving profile information from a plurality of users, receiving a first preferred activity from a first user of the plurality of users, receiving a second preferred activity from a second user of the plurality of users, determining a match of the first preferred activity and the second preferred activity, and establishing a connection between a first mobile device of the first user and a second mobile device of the second user.

[0093] The SOA 1202 may be implemented as a non-transitory computer readable medium including a plurality of machine-readable instructions which when executed by one or more processors of one or more servers are adapted to cause the one or more servers to provide at least two users of a plurality of users a connection for facilitating planning of a mutual activity. In a preferred embodiment, the SOA 1202 is implemented on a virtual (i.e. software implemented) server in a cloud based computing environment 206.

[0094] The SOA 1202 transforms the virtual server or the one or more servers from a generic computer function into a machine for facilitating connections between social networking users for efficiently planning a mutual activity including reducing cost via sharing of nonmonetary offers and/or monetary offers. Specifically, the SOA front end components are operable to be combined with the SOA back end components to form an operable SOA solution.

[0095] FIG. 13 through FIG. 60 illustrate additional diagrams 1300 through 6000 of GUIs of the KAYU® system. These additional GUIs illustrate many additional features of the KAYU® system. These features include, but are not limited to: login via Facebook® or Instagram®, local and travel options, gender preferences, lodging and pricing, distance to travel preferences, additional activity details, matched interests, potential connections, group creation and management capabilities, survey and ratings, and a splash screen.

[0096] As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "circuit," "module," or "system." Furthermore, aspects of the present invention may take the form of a computer program product (e.g. KAYU® server application 202 of FIG. 2 or SOA 1202 of FIG. 12) embodied in one or more computer readable medium(s) having computer readable program code embodied thereon. [0097] Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium (including, but not limited to, non-transitory computer readable storage media). A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0098] A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

[0099] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[00100] Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including object oriented and/or procedural programming languages. Programming languages may include, but are not limited to: Ruby, JavaScript, Java, Python, Ruby, PHP, C, C++, C#, Objective-C, Go, Scala, Swift, Kotlin, OCaml, or the like. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer, and partly on a remote computer or entirely on the remote computer or server.

[00101] Aspects of the present invention are described in the instant specification with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions.

[00102] These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[00103] These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

[00104] The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[00105] The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

[00106] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms "a," "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Thus, for example, reference to "a user" can include a plurality of such users, and so forth. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

[00107] The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.

[00108] The descriptions of the various embodiments of the present invention have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

What is claimed is:

1. A method implemented on a server for providing at least two users of a plurality of users a connection for facilitating a planning of a mutual activity, the method comprising: receiving profile information from the plurality of users;

receiving a first preferred activity from a first user of the plurality of users;

receiving a second preferred activity from a second user of the plurality of users; determining a match of the first preferred activity and the second preferred activity; and

establishing a connection between a first computing device associated with the first user and a second computing device associated with the second user.

2. The method of claim 1, wherein the first preferred activity is a first offer of sharing costs of the mutual activity, and the method further includes transmitting the first offer to the second computing device.

3. The method of claim 2, wherein the second preferred activity is a second offer of sharing costs of the mutual activity, and the method further includes receiving the second offer from the second computing device.

4. The method of claim 1, wherein the method further includes transmitting a plurality of offers to the second computing device and the plurality of offers are categorized within a plurality of tiers.

5. The method of claim 4, wherein the plurality of tiers includes a first local activity tier and a second travel based activity tier wherein each user offers a nonmonetary incentive to facilitate the mutual activity.

6. The method of claim 5, wherein the plurality of tiers includes a third tier wherein at least one user offers a nonmonetary incentive to facilitate the mutual activity.

7. The method of claim 6, wherein the plurality of tiers includes a fourth tier wherein at least two users offer sharing monetary costs to facilitate the mutual activity.

8. The method of claim 1, wherein the mutual activity is attending an event.

9. The method of claim 8, wherein the event is at least one of a concert, a movie, a play, a political rally, a sporting event, and a festival.

10. The method of claim 8, wherein the method further comprises receiving a first offer from the first user for facilitating the mutual activity and receiving a second offer from the second user for facilitating the mutual activity.

11. The method of claim 10, wherein the first offer is at least one of a ticket to the event, shared transportation to the event, shared lodging to attend the event, and a shared meal on or after the event.

12. The method of claim 1, wherein the mutual activity is a self -participation activity.

13. The method of claim 12, wherein the self-participation activity is a least one of hiking, fishing, hunting, shopping, baseball, softball, football, soccer, volleyball, skydiving, surfing, skiing, swimming, visiting a museum, bar hopping, clubbing, dancing, visiting a zoo, taking a tour, and taking a cruise.

14. The method of claim 1, wherein the first computing device is at least one of a smart phone, a tablet, a laptop, and a personal computer.

15. The method of claim 14, wherein the second computing device is at least one of a smart phone, a tablet, a laptop, and a personal computer.

16. The method of claim 1, wherein the server is a virtual server hosted in a cloud computing environment.

17. The method of claim 1, wherein the server provides a secure web portal for a graphical user interface (GUI) of the second computing device.

18. The method of claim 17, wherein the GUI is provided by an application specific program.

19. The method of claim 18, wherein the application specific program is at least one of an iOS® app and an Android® OS app.

20. The method of claim 17, wherein the GUI is provided by a web browser.

21. The method of claim 20, wherein the web browser is at least one of a Microsoft Internet Explorer® browser, a Microsoft Edge® browser, an Apple Safari® browser, a Google Chrome® browser, a Mozilla Firefox® browser, and an Opera® browser.

22. A server for providing at least two users of a plurality of users a connection for facilitating a planning of a mutual activity, the server comprising

a memory;

a database; and

a processor configured for:

receiving profile information from the plurality of users;

receiving a first preferred activity from a first user of the plurality of users; receiving a second preferred activity from a second user of the plurality of users;

determining a match of the first preferred activity and the second preferred activity; and

establishing a connection between a first computing device associated with the first user and a second computing device associated with the second user.

23. A non-transitory computer readable medium comprising a plurality of machine- readable instructions which when executed by one or more processors of a server are adapted to cause the server to perform a method server for providing at least two users of a plurality of users a connection for facilitating a planning of a mutual activity, the method comprising: receiving profile information from the plurality of users;

receiving a first preferred activity from a first user of the plurality of users;

receiving a second preferred activity from a second user of the plurality of users; determining a match of the first preferred activity and the second preferred activity; and

establishing a connection between a first computing device associated with the first user and a second computing device associated with the second user.

24. A method implemented on a server, the method comprising:

identifying interface requirements for a set of services to be implemented between service oriented architecture (SOA) front end components and SOA back end components, wherein:

at least one of the SOA back end components is configured to communicate with at least one of a social networking system, a professional networking system, and an on-line marketplace system;

at least one of the SOA front end components is configured to communicate with an application graphical user interface (GUI); and

the SOA front end components are operable to be combined with the SOA back end components to form an operable SOA solution for providing at least two of a plurality of users a connection for facilitating planning of a mutual activity, wherein the SOA solution provides a method comprising:

receiving profile information from the plurality of users;

receiving a first preferred activity from a first user of the plurality of users; receiving a second preferred activity from a second user of the plurality of users;

determining a match of the first preferred activity and the second preferred activity; and

establishing a connection between a first computing device associated with the first user and a second computing device associated with the second user. server comprising

memory; a database; and

a processor configured for:

identifying interface requirements for a set of services to be implemented between service oriented architecture (SOA) front end components and SOA back end components, wherein:

at least one of the SOA back end components is configured to communicate with at least one of a social networking system, a professional networking system, and an on-line marketplace system;

at least one of the SOA front end components is configured to communicate with an application graphical user interface (GUI); and

the SOA front end components are operable to be combined with the SOA back end components to form an operable SOA solution for providing at least two of a plurality of users a connection for facilitating planning of a mutual activity, wherein the SOA solution provides a method comprising:

receiving profile information from the plurality of users;

receiving a first preferred activity from a first user of the plurality of users;

receiving a second preferred activity from a second user of the plurality of users;

determining a match of the first preferred activity and the second preferred activity; and

establishing a connection between a first computing device associated with the first user and a second computing device associated with the second user.

26. A non-transitory computer readable medium comprising a plurality of machine- readable instructions which when executed by one or more processors of a server are adapted to cause the server to perform a method comprising:

identifying interface requirements for a set of services to be implemented between service oriented architecture (SOA) front end components and SOA back end components, wherein:

at least one of the SOA back end components is configured to communicate with at least one of a social networking system, a professional networking system, and an on-line marketplace system; at least one of the SOA front end components is configured to communicate with an application graphical user interface (GUI); and

the SOA front end components are operable to be combined with the SOA back end components to form an operable SOA solution for providing at least two of a plurality of users a connection for facilitating planning of a mutual activity, wherein the SOA solution provides a method comprising:

receiving profile information from the plurality of users;

receiving a first preferred activity from a first user of the plurality of users; receiving a second preferred activity from a second user of the plurality of users;

determining a match of the first preferred activity and the second preferred activity; and

establishing a connection between a first computing device associated with the first user and a second computing device associated with the second user.