WO2014210162A1 - Système et procédé pour une promotion d'événement en ligne et une panification de groupe - Google Patents

Système et procédé pour une promotion d'événement en ligne et une panification de groupe Download PDF

Info

Publication number
WO2014210162A1
WO2014210162A1 PCT/US2014/044108 US2014044108W WO2014210162A1 WO 2014210162 A1 WO2014210162 A1 WO 2014210162A1 US 2014044108 W US2014044108 W US 2014044108W WO 2014210162 A1 WO2014210162 A1 WO 2014210162A1
Authority
WO
WIPO (PCT)
Prior art keywords
event
web page
gathering
link
transaction
Prior art date
Application number
PCT/US2014/044108
Other languages
English (en)
Inventor
Farid SHIDFAR
Original Assignee
Rundavoo, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Rundavoo, Inc. filed Critical Rundavoo, Inc.
Publication of WO2014210162A1 publication Critical patent/WO2014210162A1/fr

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
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/01—Social networking
    • 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

Definitions

  • This disclosure relates to a system and method for event promotion and group activity planning through the use of public/private events and private gathering web pages, enabling on-line collaboration amongst potential event participants, and allowing transactions related to an event to be made.
  • This disclosure relates to methods and systems for event planning, wherein the methods and systems include defining an information object including an event and a plurality of event attributes for a proposed event of a defined group of people, the information object including at least one multimedia presentation of at least one attribute of the event.
  • the information object is sent to at least one member of the group.
  • At least one vote as to the value of at least one of the plurality of event attributes is solicited and received from at least one member of the group.
  • the votes are used to select a value for at least one event attribute for the proposed event; and the event information object is transformed to present a modified event based on the voting.
  • the disclosure also relates to methods and systems for event planning including adding a gathering creation link to a public event web page for creating a private web page; receiving information via the gathering creation link to define a proposed gathering related to the event; and creating, with the received information, a private web page accessible to a defined group of potential participants of the proposed gathering, wherein the private web page includes a link for performing a transaction related to the event.
  • Figure 1 is a flow diagram for event planning according to an exemplary and non-limiting embodiment
  • Figure 2 is an illustration of a suggestion home page web page according to an exemplary and non-limiting embodiment
  • Figure 3 is an illustration of an interactive plan web page according to an exemplary and non-limiting embodiment
  • Figure 3a is an illustration of an interactive plan web page according to an exemplary and non-limiting embodiment
  • Figure 4 is an illustration of a login authenticate page according to an exemplary and non-limiting embodiment
  • Figure 5 is an illustration of a share with friends web page according to an exemplary and non-limiting embodiment
  • Figure 6 is an illustration of an ask question web page according to an exemplary and non-limiting embodiment
  • Figure 7 is an illustration of a suggestion web page according to an exemplary and non-limiting embodiment
  • Figure 8 is a flow diagram for an invitee of an event according to an exemplary and non-limiting embodiment
  • Figure 9 is a block diagram of a system for promoting events by accessing and populating a plan web page template according to an exemplary and non-limiting
  • Figure 10 is an illustration of a public plan template/link generation web page according to an exemplary and non-limiting embodiment
  • Figure 11 is an illustration of a generated plan web page according to an exemplary and non-limiting embodiment
  • Figures 12-16 illustrate a mobile application for event planning according to an exemplary and non-limiting embodiment
  • Figures 17-22 are examples of web pages that are involved in an exemplary process for event promotion and group planning
  • Figure 23 is a schematic illustration of the integration of an event planning tool with various other websites/tools
  • FIGS 24-41 illustrate a mobile application for the iPhone for event planning according to an exemplary and non-limiting embodiment
  • Figure 42 is an illustration of the process of event planning and generation of public and private plan web pages
  • Figures 43-45 are examples of web pages that are used to generate public or private plan web pages.
  • Figure 46 is an example of analytic and reporting data related to the
  • One aspect of this disclosure relates to a system and method for enabling online collaboration among a group of people, such as a group of friends, an affinity group, a fan club, a group of co-workers, a team, or the like, to arrive at a decision, such as a decision as to the nature of an event in which the group wishes to participate.
  • a web-based platform allows users to interact with one another via the visual elements of a web page to engage in numerous facets of planning around a group decision, such as a decision related to an event, a social gathering, or the like.
  • Fig. 1 illustrated is a flow diagram of an interactive event planning process showing various activities enabled by the system according to exemplary and non-limiting embodiments. Access to the system may be enabled by entering data into a web-based suggestion home page.
  • Fig. 2 illustrated is a suggestion home page for suggesting a social gathering or event according to exemplary and non-limiting embodiments.
  • suggestion home page comprises a text input box that allows for an alphanumeric input and a submission button. Data entered into the text input box becomes the title of a social gathering/event.
  • a background of the web pages displayed to a user may be customizable.
  • users may be provided access to a tutorial explaining the features of the system and providing examples.
  • FIG. 3 there are illustrated interactive plan pages according to exemplary and non- limiting embodiments.
  • An interactive plan page functions as a canvas whereupon interactions amongst authenticated users take place for a social gathering.
  • the interactive plan page is a visual summary of the entire social gathering which may include, dates, times, locations, questions, timers associated with questions, answers, votes, decisions, who is involved, and the like.
  • an interactive plan page may have a customizable background as well as a summary of user related or social gathering related events. Events so summarized may include dates, times, locations, questions, answers, votes, vote tallies, decisions (made and pending), and a decision countdown timer associated with each decision showing days, hours, minutes and seconds remaining until the window to make a selection has expired.
  • an interactive plan page may enable users to create new events, view a user's events and access a user's account.
  • a user upon receiving display of the interactive plan page, a user may proceed to, for example, share a social gathering with other users, ask questions, add suggestions and the like.
  • a login authenticate page functions to authenticate a user to the system.
  • authentication may be performed utilizing a third party API.
  • third party APIs such as those of Facebook, Twitter, Linkedln and Google+, may be utilized for authentication purposes.
  • the system builds a profile for the user and stores the profile in the system.
  • profiles may include data such as name, gender, age, location, email address, mobile number, etc.
  • a user may proceed to share a social gathering or event with other users.
  • a share with friends page there is illustrated a share with friends page according to exemplary and non-limiting
  • a Share with friends page allows users operating as social gathering planners to invite their friends to a social gathering.
  • the system pulls friends of the user from a Facebook API, displays the friends, and allows a planner to select those friends which they would like to join their social gathering.
  • planners are enabled to include a private message with their invitation.
  • the ability to send a private message is enabled when an email is sent to an existing user of the system.
  • the share with friends page includes an invite button which executes and sends the actual invitation. When a friend is invited by a planner to a social gathering, they are sent, for example, a Facebook App notification. If they are already a user of the system, they may also be sent an email.
  • a user having a large number of friends to whom he/she wishes to invite to join in planning and executing a social gathering may do so in an unstructured manner.
  • the user may send a link to an invite by email to all of his/her friends without having to select a specific set of people from a pre-defined list, as would be necessary with an invite-specific system.
  • An Ask question page allows users, each acting as a social gathering planner, to ask questions, suggest answers, and come to a decision around group gatherings. The first step of this process is asking a question.
  • a sample question could be "Which hotel should we stay at?” or "How should we get there?" or "What kind of shoes should we wear?" Every question has a title that is simply an alphanumeric description.
  • Every question also has a timer associated with it which is essentially a time and date for when a decision must be made. Planners can also decide whether or not they want others to be able to suggest answers to their question.
  • a user may proceed to add a suggestion to or answer a question from one of the other users engaged in the social gathering.
  • a suggestion page there is illustrated a suggestion page according to exemplary and non-limiting embodiments.
  • a suggestion is a potential option that answers a proposed question.
  • An example of this might be "Planet Hollywood Hotel and Resort” or “The Cosmopolitan of Las Vegas” to the question of "Where should we stay (in Las).
  • a custom answer may include a description, image/video, a link and the like.
  • An example of a description could be "@Planet Hollywood $200/night for 2 #queen beds” where "@” signifies a place or person, "#” signifies products or things, and $ signifies a price.
  • An image may be a bitmap (jpg, png, gif) and may be, for example, 150px in width/height.
  • a video can be uploaded/recorded in, for example, mpg format and may be less than perhaps 15 seconds in length.
  • a link may be a hyperlink to a webpage that relates to the suggestion.
  • the suggestion when a suggestion is received from a user, such as via a suggestion page, the suggestion may be assigned a rank.
  • Ranking suggestions helps to reduce the occurrence of no one suggestion receiving majority approval as may occur when there are various options given to a group and the group is asked to make a decision.
  • Decision ranking helps to ensure that a group comes to a decision around a given question by the deadline for that question.
  • Decision ranking takes into account votes for an answer as well as factors specific to the planner voting including, but not limited to, a time at which the planner voted, hierarchy, a number of social gatherings a planner has been involved in, a number of questions a planner has asked, a number of suggestions a planner has made, and a number of purchases a planner has made in the system.
  • the system may take into account various attributes of each user/planner.
  • attributes include, but are not limited to, a time when the user voted, a number of events the user participated in, a number of questions asked by the user, a number of answer suggestions made by the user, a number of votes cast by the user and a number of purchases made by the user.
  • Other factors may include public vs. private voting, sequential voting, veto/black-ball, utility/% allocation voting, iterative voting, Poison pill - deliberate sabotage, Zero sum (user can't attend if he/she chooses losing option), shared pot (reward for voters who choose winner) and the like.
  • a user may be directed to a read only plan page from an external link such as a hypertext link on an external website directing the user to a specific social gathering on the system.
  • This Read only plan page may be similar to the interactive plan page but it does not actually allow the viewer to interact with other users until they login and become a participant or planner.
  • a user may join, such as by activating a "join" button on the read only plan page.
  • users/planners can control which users may invite other users. Users can control which users may suggest questions. Users can control which users may suggest answers. Users can control which users may vote. Users can control user's decision timers for posted questions. Users can delete a user and their respective votes. Users can set a social gathering to be Private in which only the invited users can join. Users can set a social gathering to be Public in which anyone can join.
  • a user or users can setup a "piggy-bank" for each social gathering wherein a plurality of users contribute monies for sharing group expenses.
  • monies are allocated from the "piggy-bank" to the individual incurring the expenses. Participants may be paid once the group approves payment to a participant.
  • the system enables Person-to-Person Money Transfers. For example, participants may upload expense receipts and select who is responsible for sharing the expenses. In this manner, participants can settle outstanding payments.
  • exemplary embodiments of the system described above enable a visual based communication platform for group decision-making comprising a collaborative and organized information exchange.
  • the system enables a plurality of users each associated with a particular social gathering to ask questions, post answers, cast votes before a timer expires and the like.
  • Such capabilities are enabled via a plurality of user interfaces and web pages that are visually engaging, intuitive, easy to use, collaborative, customizable, fun, and convenient.
  • the system may be beneficially applied to various forms of planning including, but not limited to, social planning, event planning, activity planning, vacation planning, holiday planning, trip planning, party planning, celebration planning, reunion planning, nightlife planning, concert planning, tradeshow planning, conference planning, festival planning, political campaign planning and special occasion planning.
  • the system may be beneficially applied to various forms of business enterprises including, but not limited to, external enterprises, such as marketing events, product surveys and customer surveys, and internal events, such as meetings, corporate retreats and employee surveys.
  • Other applications include, but are not limited to game shows, reality shows and audience surveys, music fan surveys, celebrity fan surveys and the like.
  • exemplary embodiments are drawn broadly to encompass any and all uses of the elements and functionality described herein including, but not limited to, the use by businesses to perform product development research and/or customer engagement.
  • a music band may utilize the system to engage fans in a survey of questions for choosing concerts dates, cities to perform, album art, promotional products to create (i.e., hat, t-shirt designs) and the like.
  • a celebrity may engage fans in a survey of questions for choosing which outfit and/or jewelry to wear to a red carpet event or what charitable foundation to support or when and where to hold a book signing.
  • a brand may engage customers in a survey of questions for market research or product development. For example, a cosmetic company may survey what colors to offer in the coming season or a handbag designer may survey what size, shape and materials to use for new products.
  • the system may enable various monetization options.
  • home pages and their backgrounds may be branded and geo-targeted for advertising & sponsorships.
  • the interactive plan page may present or otherwise display "Partner" options and deals such as flights, hotels, cars/rails, cruises, travel deals, vacation packages, activities (e.g. golfing, Whitewater rafting, etc.), event tickets (e.g., sports, concerts, theater, film, festivals, etc.), dining, consumer products (e.g. gifts, clothing, shoes, jewelry, books, music, video games, electronics, home & household, health & beauty, etc.), services (e.g. spa, bottle service, etc.), foundations (e.g.
  • the system may collect user data.
  • User data may be usage data, decision data, purchase and transaction data, friends data, influence data, other statistical data, other analytics data, other reporting data, and the like.
  • Usage data may include how often the user logs into the system, how active the user is when logged into the system, and the like.
  • Decision data may be what choices a user may have made related to a single event, what decisions a user may have made related to a group of events, and the like.
  • Purchase and transaction data may be how many purchases and transactions a user defines, initiates, completes, abandons and the like.
  • Friends data may be how many friends a user has, how many friends a user invites, how many invitations a user receives from a friend, and the like.
  • Influence data may include how many other users sign up for an event that the user creates or signs up for, how many other users complete a transaction that the user creates or completes, and the like.
  • Other statistical data may include information used to calculate probabilities for the system on a per-user basis, on an aggregate user basis, and the like.
  • Other analytics data may include information used to calculate analytical information for the system on a per-user basis, on an aggregate user basis, and the like.
  • Other reporting data may include information used compile reports for the system on a per-user basis, on an aggregate user basis, and the like.
  • user data may be sold.
  • This disclosure further relates to a system and method for event promotion by businesses, event organizers, or the like ("event promoters') using a web-based platform for enabling on-line planning among a pre-defined group of people, such as a group of friends, an affinity group, a fan club, a group of co-workers, a team, or the like, to plan and participate in an event being promoted.
  • event promoters' a web-based platform for enabling on-line planning among a pre-defined group of people, such as a group of friends, an affinity group, a fan club, a group of co-workers, a team, or the like, to plan and participate in an event being promoted.
  • the web-based platform allows users such as event promoters to create a public event plan web page to advertise and promote an event, and from which a user, such as a potential event participant, can create a private plan web page relating to the event to allow a group of potential event participants to interact with one another via the visual elements of the web page to engage in numerous facets of planning, such as described above, and to also perhaps complete a transaction related to the event.
  • Figure 9 illustrates one embodiment of such a system for event promotion and group planning, in which a plan template is accessed by an event promoter and populated to create a populated plan web page ("Populated Rundavoo" or "Rundavoo") with details of an event, such as a visual representation of the attributes of the event, and possible times and dates for the event, and an option to execute event-related transactions, either on the populated plan web page directly, or by selecting a link to a partner website.
  • the event related transaction may include a ticket purchase, transportation booking, lodging booking, dining booking, and the like.
  • the boxes on the right in Figure 9 represent the tools used to generate the Populated plan web page (Populated Rundavoo) template as well as the links to point traffic to the Populated plan web page (Populated Rundavoo), called "R-Links". Further, the boxes on the left in Figure 9 represents how user traffic can be directed by different sources and then fed to a Populated plan web page (Populated
  • FIGs 10 and 11 illustrate embodiments of populated plan web pages.
  • the populated plan web page may include event specific information such as the date of the event, time of the event, location of the event and the like.
  • the populated plan web page may include links to social networks such as Facebook, Twitter, Google+, and the like.
  • the populated plan web page may display a list of visitors that will be attending the event.
  • the populated plan web page may allow visitors to make decisions related to the event, such as choosing a flight to the event, and the like.
  • the populated plan web page may allow visitors to indicate their attendance.
  • the populated plan web page may allow visitors to execute a transaction related to the event, such as purchasing tickets related to the event, and the like.
  • the populated plan web page may allow visitors to the populated plan web page to comment on the event.
  • the populated plan web page may include a Link/Widget button that allows visitors to generate their own private web plan web pages and share the private web plan web pages with friends, allowing friends to sign-up for the event, providing a multiplication effect on the number of visitors to the public and private plan web pages.
  • an event promotion process through the use of link generation and facilitation of group event planning, helps businesses increase traffic to specific web pages promoting various events, helping to lower the cost of acquiring customers.
  • the ease of use of the provided LINK/WIDGET button allows users to easily organize a group activity or event and coordinate all aspects of participation.
  • a single Public plan web page generated by an event or venue owner using the Link/Widget button, can be distributed as multiple copies of the public plan web page, creating multiple collection points for public visitor traffic.
  • the ease of distribution provided by information made accessible by a URL/link allows an event or venue owner to easily distribute these multiple copies of the Public plan web page, illustrated in Figure 42 as Public Plan Web Page A, Public Plan Web Page B, Public Plan Web Page C.
  • each copy of each Public plan web page allows visitors to the Public plan web page to generate multiple copies of a Private plan web page, generated by a Link/Widget button.
  • the ease of distribution provided by information made accessible by a URL/link allows a visitor to a private plan web page to easily distribute these multiple copies of the Private plan web page, illustrated in Figure 42 as Private Plan Web Page Copy A, Private Plan Web Page Copy B, Private Plan Web Page Copy A, and Private Plan Web Page Copy B.
  • Distribution of a plan web page may originate from and be made to, a wide range of environments.
  • a provider of services such as trip planning, hotel booking, transportation, or ticketing services, may allow creation of a plan web page using a Link/Widget button as described herein within the interface (e.g., a web site) of the service provider, such that a proposed plan web page for an event may originate within that environment and be distributed to other environments.
  • a user might initially review upcoming events in a ticketing site, then, within that site, create a plan web page using a Link/Widget button that is distributed to the user's social network for commentary among a decision-making group.
  • the plan web page generated using The Link/Widget button might be modified and/or copied for distribution to other environments, such as to a site for booking travel to an event.
  • the plan web page generated using the Link/Widget button may be carried through different environments, allowing collaboration among the decision-making group about selecting an event to attend (e.g., at a concert or sporting event site), arranging to travel together to the event (e.g., at an airline site), arranging to stay at the same
  • the plan web page generated using The Link/Widget button may be integrated, as noted above, with the transactions infrastructure of each of a range of third party services, so that once consensus is reached on an aspect of an event (the event, date, travel, accommodations, related services, etc.), the booking or purchase of the related services can be executed seamlessly, either facilitated (such as through an API) from the plan web page generated using the Link/Widget itself, or by handoff to the transaction infrastructure of the environment of a service provider within which the plan web page generated using the Link/Widget resides.
  • analytic and reporting data related to the Link/Widget button may be available.
  • Such data may include filter data, plan pages or undavoos data, people data, and the like.
  • Filters data may include name data and the like.
  • Plan pages or Rundavoos data may include number of plan pages or Rundavoos, average number of people per plan page or Rundavoo, number of people who viewed a plan page, number of people who joined an event or gathering, number of people who purchased something, and the like.
  • People information may include gender and location information.
  • Gender information may include the number or percentage of males, the number or percentage of females, total number of people, and the like.
  • Location information may include city, state, country, and the like.
  • Analytic and reporting data may be available for download or export from the system.
  • a user such as an event promoter can access a Link/Widget button generation web page.
  • access to the Link/Widge button generation web page can be done via various forms of authentication, such as allowing a user to input user credentials associated with other websites (e.g. Facebook, Twitter, Linkedln, Google, etc.), in a manner such as is provided by a service like https://www.loginradius.com/.
  • the user can enter event information into a form on the Link/Widget generation web page.
  • Event information may include event logistic information, event specific information, as well as event integration information, and the like.
  • event logistic information can include for example: Event Name, Event Image URL, Event Description, Date/Time, Venue Name, Street Address, City, State, Zip Code, and Purchase Link (or Transaction Link).
  • Event specific information may include event name, cover image URL, description, date/time, venue name, address, city, state, and zip code, and the like.
  • Integration information may include information required to integrate with third-party services.
  • Third party services may include ticket purchasing services, transportation booking services, lodging booking services, dining booking services, other reservation booking services, or the like.
  • Information required to integrate with third party services may include links to the third party service, login information for the third party service, other identification for the third party service, or the like.
  • This information can be entered into the Link/Widget button generation web page by a variety of parties including, but not limited to: business owners, event holders, and Rundavoo staff.
  • This information may be managed via a secured form. Access via the secured form allows a party to change or update the event and transaction information associated with the Link/Widget button, using the Link/Widget generation web page, without requiring the help of a technical resource. Access via the secured form allows parameters of the Link/Widget button to be easily changed or updated, which allows the same Link/Widget button to be used to promote subsequent events without having to regenerate a new
  • Link/Widget button for each event or require that the Link/Widget button be removed from a website when an event expires, for example.
  • a default destination location can be configured for the Link/Widget button to send any user who clicks on the Link/Widget button after the event has passed to be sent to a different URL, i.e. .
  • a user can bypass the Link/Widget button generation web page and create a Link/Widget button simply by passing a URL to Rundavoo. In this case, the information that would have been entered in the link/Widget button generation page would simply be passed as arguments within the URL.
  • the platform will create a Link/Widget button with the event information embedded in it, which can be accessed via the link (R-link) Link/Widget button created by the platform.
  • the Link/Widget button can be integrated directly or indirectly with many other web services, such as
  • Web services may include ticket purchasing services, transportation booking services, lodging booking services, dining booking services, activity booking services, other ticket booking services, other transaction-based services, other reservation-based services, donation collection services, other web services or the like.
  • Transportation booking services may include orbitz.com, kayak.com, travelocity.com, expedia.com, cheapflights.com, hotwire.com, amtrak.com, megabus.com, boltbus.com, greyhound.com, peterpanbus.com, delta.com, united.com, aa.com, britishairways.com, southwest.com, emirates.com, App.com, enterprise.com, uber.com and the like.
  • Lodging booking services may include transportation booking services that also provide lodging booking services, hotels.com, booking.com, bookit.com, spg.com, marriott.com, hilton.com, ritzcarlton.com, mandarinoriental.com, choicehotels.com, and the like.
  • Dining booking services may include opentable.com, savored.com, and the like.
  • Activity booking services may include golfnow.com, meetup.com, and the like.
  • Other ticket booking services may include eventbrite.com, ticketmaster.com, stubhub.com, livenation.com, and the like.
  • Other transaction-based system web sites or web pages may include apple.com/itunes, amazon.com, Nordstrom.com, and the like.
  • Donation collection services may include clickandpledge.com, blackbaud.com, wwwactivegiving.com, www.donortools.com, and the like.
  • Donation collection services may include clickandpledge.com, blackbaud.com, www. activegiving.com, www.donortools.com, and the like.
  • the other web services may be directly integrated, indirectly integrated, and the like.
  • a directly integrated web service may display its content directly on the plan web page and allow the user to interact with the content, such as complete a transaction, without having to leave the plan web page.
  • the content of an indirectly integrated web service may be accessed when a user clicks on a link that has been displayed on the plan web page. The user is then taken to a third-party site where the content of the indirectly integrated web service is displayed. The user can then interact with the content, such as complete a transaction, on the third-party site.
  • An organizer such as an event/venue owner accesses a Link/Widget generation web page and completes a form, such as the form illustrated in Figure 17.
  • the Link/Widget generation web page allows the event/venue owner to enter event specific information.
  • Event specific information may include event logistic information, as well as event integration information, and the like.
  • Event logistic information may include event name, cover image, URL, description, date/time, venue name, address, city, state, and zip code, and the like.
  • Event integration information may include information required to integrate with other web services such as ticket purchasing services, transportation booking services, lodging booking services, dining booking services, an auxiliary or related event, or other reservation services, or the like.
  • Information required to integrate with other web services may include links to the other web service, login information for the other web service, other identification for the other web service, and the like.
  • a public Rundavoo is a public plan web page which includes an embedded Link/Widget button.
  • the embedded link/Widget button In this example, the embedded
  • Link/Widget button says “Do it with Friends", and is integrated with a ticket purchasing web service, where the ticket purchasing service is integrated with the public plan web page that has been generated by the organizer.
  • Figures 43 and 44 illustrate a form 4302 that may be used by the organizer to generate an event link button 4304.
  • Form 4302 may allow the organizer to make it easy for an organizer to increase traffic to the event of the organizer at no cost to the organizer.
  • Form 4302 may allow the organizer to generate event link button 4304 in two process steps. From 4302 may allow the organizer to enter event related data. Event related data may include event name, cover image URL, description, date, time, venue Foursquare ID, venue name, address, purchase link, EventBrite ID, and the like. Address may include street name, city, state, zip code and the like.
  • Form 4302 may include a generate button 4306. Clicking generate button 4306 may generate event link button 4304.
  • Event link button 4304 may include a title. Title may be do it with friends, bring your friends, dine here with friends, meet here with friends, and the like.
  • Figure 45 illustrates an interface 4502 which may allow an organizer to add event link button 4304 to the website of the event, organizer, and the like.
  • Interface 4502 may include event link buttons 4304 and event link button source code 4504.
  • Event link button source code may be embedded by organizer into the website of the event, organizer, and the like to add link button 4304 to the website.
  • Source code 4306 may include source code to create an event link button 4304 or a custom event link 4506.
  • the organizer distributes the public plan web page information, such as to their customers or to other individuals or websites as desired, such that other public plan web pages can be generated, such as the one illustrated in Figure 20.
  • the distribution of the public plan web pages facilitates the collection of additional potential attendees, by multiplying the number of sites that can attract such attendees.
  • the organizer, recipients of, or visitors to the public plan web page invite friends through the creation of private plan pages or private Rundavoos, such as the private plan web pages illustrated in Figure 21, which are accessible to a pre-defined group of people and define a group gathering related to the event, and may include direct integration with a ticket purchasing service, where the ticket purchasing service is directly integrated with the private plan web page that has been generated by the organizer, as illustrated in Figure 21.
  • the generation of private plan web pages also facilitates the collection of additional potential attendees, by multiplying the number of sites that can attract such attendees.
  • the private plan web pages are sent to a defined group of people, typically with some association with the generator of the private plan web pages, which also increases the likelihood that a visitor to one of the private plan web pages becomes a participant in the event being promoted by the private plan web page.
  • the group members confirm or decline attendance.
  • the private plan web page or private Rundavoo includes buttons to indicate who is in and out.
  • the group can also collaborate on any decisions that may need to be made related to the group gathering.
  • an Order Now button on the private web page such as illustrated in Figure 22 can be used to facilitate such a transaction through direct integration of a booking service into the environment where the plan web page is hosted, through a link to the other web service, and the like.
  • a WordPress content management platform hosted by Godaddy or other web hosting provider is utilized as the web platform.
  • a link/widget button or plan web page can be hosted on tickets .rundavoo . com, a subdomain of Rundavoo (i.e., Rundavoo.com).
  • users such as event promoters can generate, as illustrated in Figure 42, a so-called public plan web page or public Rundavoo, which is accessible to the public (or other targeted group), which can include information and purchasing links related to the event, and which includes a link or ability for a group to create, as illustrated in Figure 42, a so-called private plan web page or private Rundavoo, which is a private web page accessible by invitation describing a group gathering related to the event.
  • the private plan web page or private Rundavoo can also facilitate group collaboration, such as described above with respect to Figs. 1-8, and elaborated upon below with respect to Fig. 11 for items related to the event.
  • an event organizer can generate a public event plan web page for a concert or a racing event, and visitors to the public plan web page can generate their own private plan web page for a group gathering related to the event, which is accessible by a private defined group.
  • This private plan web page can include information and/or purchasing links to one or more other websites or web pages associated with the event itself (such as to buy tickets for the event) and for other planning associated with the social gathering, such as which tickets to buy, or additional logistics decisions related to the event.
  • Other web sites or web pages may include ticket purchasing web sites or web pages, transportation booking web sites or web pages, lodging booking web sites or web pages, donation collection services, dining booking web sites or web pages, activity booking web sites or web pages, other ticket booking web sites or web pages, other transaction-based system web sites or web pages, other reservation-based web sites or web pages, other web sites or web pages or the like.
  • Transportation booking web sites or web pages may include orbitz.com, kayak.com, travelocity.com, expedia.com, cheapflights.com, hotwire.com, amtrak.com, megabus.com, boltbus.com, greyhound.com, peterpanbus.com, delta.com, united.com, aa.com, britishairways.com, southwest.com, emirates.com, App.com, enterprise.com , and the like.
  • Lodging booking web sites or web pages may include transportation booking services that also provide lodging booking services, hotels.com, booking.com, bookit.com, spg.com, marriott.com, hilton.com, ritzcarlton.com,
  • Dining booking services may include opentable.com, savored.com, and the like.
  • Activity booking web sites or web pages may include golfnow.com, meetup.com and the like.
  • Other ticket booking services may include fandango.com, eventbrite.com, ticketmaster.com, stubhub.com, livenation.com, and the like.
  • Other transaction-based system web sites or web pages may include apple.com/itunes, amazon.com, nordstrom.com, and the like.
  • Donation collection services may include clickandpledge.com, blackbaud.com, www.activegiving.com, www.donortools.com, and the like.
  • Other web sites or web pages may include Foursquare.com and the like.
  • the other web sites or web pages may be directly integrated, indirectly integrated, and the like.
  • Directly integrated web sites or web pages may display content directly on the plan web page and allow the user to interact with the content, such as complete a transaction, without having to leave the plan web page.
  • the content of an indirectly integrated web site or web page may be accessed when a user clicks on a link that has been displayed on the plan web page. The user is then taken to a third-party site where the content of the indirectly integrated web site or web page is displayed. The user can then interact with the content, such as complete a transaction, on the third-party site.
  • FIG 10 another example public plan web page is illustrated in Figure 10, and includes various ticket buying options for an event. Further, this public plan web page includes an option to create a private plan web page, such as by use of a "Bring your Friends" button or an "Invite Others” button such as illustrated therein, wherein a private plan web page defining a social gathering relating to the event can be created to be accessed. Multiple copies of the private plan web page can then be easily distributed, as illustrated in Figure 42, providing multiple collection points for private visitor traffic.
  • FIG. 11 An embodiment of another private plan web page or private undavoo is illustrated in Figure 11 for a social gathering related to a Formula 1 Grand Prix event.
  • This private undavoo facilitates on-line planning for a group and includes collaboration tools in addition to those described above with respect to Figures 1-8.
  • the illustrated web page can include features such as a lockdown button, a buy button, and a comments section.
  • the illustrated example lockdown button includes the text "Lock It Down", and allows an organizing user to prevent other users from voting on or making additional suggestions to a question, such as the illustrated question "What flight should we get?"
  • an answer is locked, it is displayed as the decision for that particular question and highlighted for the group (displayed at the top of the plan page), and no additional answers can be suggested at that point.
  • the lock can be turned on or off at will by the organizing user. When the lock is turned off, users can suggest additional answers and vote again.
  • the answer that is locked can also be based on a number of votes, an organizing user's preference, or the like.
  • the plan web page can also include one or more buy buttons with links to external websites (each buy button associated with an individual link), which allow users to take actions essential to participating in the plan.
  • the "Buy Tickets Now" button links to an affiliate selling Grand Prix tickets.
  • Other buy button links could also be included, for example, to link to tickets on stubhub.com, make dinner reservations on opentable.com, make a flight reservation on kayak.com, or book a hotel room on hotels.com.
  • These links can be generated by the Rundavoo platform or manually created by users.
  • a comments section of a plan web page allows users to share comments with the group, such as at the bottom of the plan web page.
  • the user making each comment can be represented by a name and an image. These can be supplied by Rundavoo's user account data or the Facebook API from Facebook Inc. of Menlo Park, California. Comments can be highlighted by the organizer, which can change their experience and/or move them to a position of prominence.
  • Figures 12-16 illustrate a mobile application for creating and using a
  • the process includes initiating an event, inviting friends, and suggesting and collaborating on details, such as time and place.
  • the application allows for the addition and communication of group member comments, and for selected comments to be highlighted for the group.
  • the details of the event can be locked down, and the members can indicate whether they are in or out.
  • the application also allows for a convenient way to keep track of all events in one place.
  • FIG. 23 is a diagram of the integration of an event/group planning tool such as Rundavoo with other travel, expense management and compliance, and payment tools.
  • Rundavoo event planning is integrated with a travel booking and expense management and compliance tool (such as Concur - as described at www.concur.com), an itinerary organizer and travel plan manager tool (such as Tripit - as described at
  • the event planning tool can be used to manage corporate business travel plans in a manner, such as described above, to allow users to connect, collaborate and decide on various aspects of business travel. These users can plan which cities to travel to, which hotels to stay at, which flights to take, which cars to rent, which restaurants to go to, etc.
  • This tool facilitates planning the what, when, and where of business travel, and can also be modified to provide options that comply with company travel policy as well as preferred merchants and partners (such as American Express merchants and partners in the illustrated example).
  • Concur is also a tool which allow expenses to be captured so that business travellers can reduce the time they spend recording and accounting these expenses.
  • Concur includes automatic payment capability for electronically transferring payments to corporate card vendors and reimbursements to employees. Additional features include the ability for manager to verify line item expenses against submitted receipts, ensuring compliance, while reducing the risk of fraud.
  • a further tool which can be integrated in this system is a travel itinerary organizer, such as Tripit, which allows trip details to be organized into one master online itinerary to ensure that a user has all pertinent information organized and made accessible on a per-trip basis.
  • a payment processor tool can also be included.
  • American Express can perform this function, and benefit from the system as well by promoting merchant and travel partners, increasing issued credit card adoption, and adding value for both merchant and business card accounts.
  • FIGs 24-41 illustrate a mobile application for an iPhone for creating and using a undavoo planning tool.
  • the process includes initiating an event, inviting friends, suggesting and collaborating on details, such as time and place (i.e., determining what, who, when, and where).
  • a separate screen can be used for each of the who, what, where and when determinations, in a linear or staggered process, with a review screen provided as well.
  • a toolbar can include a calendar button which opens a calendar view, and menu button that opens a filter menu pop-over. An application navigation bar appears at the bottom of the screen.
  • options include My Rundavoos, locations, new Rundavoo launcher, group chats, and notifications/settings.
  • Figure 27 illustrates at 1 a filter menu appears when the user taps on the filter title. At 2, all options (other than Search) immediately filter the Rundavoos list. Tapping search on the filter menu displays the search bar and keyboard. Rundavoos that match search criteria appear below the search bar when the user taps "search" on the keyboard.
  • a calendar button opens the calendar view.
  • a menu button opens the filter menu pop-over.
  • a back button returns to the "my rundavoos" view.
  • days with Rundavoos appear with small dots under the date on the calendar. Different dot shadings or colors can indicate various things such as a) invited with no RSVP, b) I'm in, c) I'm out, d) Facebook event, e) iPhone calendar event.
  • Figure 29 illustrates a way to initiate a Rundavoo based on location.
  • a user can select where he/she is and initiate the Rundavoo based on the selected location, such as via a map or location determination, such as by GPS.
  • a Rundavoo is initiated based on a location (suggested location or firm location)
  • other participants can be invited, and time and event can be determined.
  • the location can be changed or other locations can be suggested.
  • Figures 30-33 show various screens for determining the who, what, where, and when of an activity, screens for determining and locking down details of an activity, as well as Review and Event detail screens.
  • Figures 34-36 illustrate messaging features including the ability for Group Text.
  • a button to view and manage groups At 1 in Figure 34 is a button to view and manage groups.
  • a button for composing new messages At 2 is a button for composing new messages.
  • messages can be categorized as one of three types:
  • Rundavoo invitees Group not tied to a specific Rundavoo, and user to user messages.
  • a button to view Rundavoos is a button to view Rundavoos.
  • Figure 35 illustrates features/screens for creating and viewing groups. This allows for a Rundavoo to be initiated based on participants selected to receive group text(s). Various suggestions as to event attributes (where, when etc.) can be made.
  • Figure 36 illustrates various other features, including: at 1 a button for viewing group settings; at 2 a button to create a new Rundavoo with group members; at 3, a button to go back to previous view (e.g., group chat or group list); at 4, a name - visible to creator only - a tap allows the group name to be edited; at 5 a private toggle which is visible to only the group creator and allows for the ability to allow or disallow invitees to invite others; at 6, a conversations notifications toggle, which is visible to all group members, is on by default, and can be changed to disable notifications of new messages; at 7, a delete this group button is shown which can be visible to only the group creator - a tap allow opening confirmation dialog asking a user if they are sure they want to delete the group - if tapped then a group is deleted. A leave group button can also be included, which would be visible to all group members with the exception of the group creator. At 8, a Save button is show to allow changes to be made to group settings.
  • Figure 37 illustrates Notifications.
  • a profile button opens the user profile view.
  • a setting button opens the application setting view.
  • a Rundavoo time/location locked notification At 3 is a Rundavoo time/location locked notification.
  • a friend request notification with the ability to confirm or decline request.
  • a Rundavoo invitation notification select "I'm in” or "I'm out”.
  • a Rundavoo time/location locked notification is a Rundavoo time/location locked notification.
  • Figure 38 illustrates User Profile and Account Settings screen.
  • Figure 39 illustrates a splash page, and sign in pages that allow for various login credentials such as described above.
  • Figure 40 illustrates Address book
  • Figure 41 illustrates a Mobile Rundavoo details page, and a download app mobile page.
  • users who are sent a text or email link will be redirected to a Rundavoo page with a unique URL. Users can select "I'm In” or "I'm Out", and their vote will be tallied on the Rundavoo pages.
  • Users sent a text or email link can view who is invited and the proposed times and locations.
  • users try to vote on a time or location on the mobile site they will be redirected to a download app mobile page.
  • At 5 is a button to Open in Rundavoo, which launches the Rundavoo iPhone application.
  • the methods and systems described herein may be deployed in part or in whole through a machine that executes computer software, program codes, and/or instructions on a processor.
  • the present invention may be implemented as a method on the machine, as a system or apparatus as part of or in relation to the machine, or as a computer program product embodied in a computer readable medium executing on one or more of the machines.
  • the processor may be part of a server, cloud server, client, network infrastructure, mobile computing platform, stationary computing platform, or other computing platform.
  • a processor may be any kind of computational or processing device capable of executing program instructions, codes, binary instructions and the like.
  • the processor may be or include a signal processor, digital processor, embedded processor, microprocessor or any variant such as a co-processor (math co-processor, graphic coprocessor, communication co-processor and the like) and the like that may directly or indirectly facilitate execution of program code or program instructions stored thereon.
  • the processor may enable execution of multiple programs, threads, and codes. The threads may be executed simultaneously to enhance the performance of the processor and to facilitate simultaneous operations of the application.
  • methods, program codes, program instructions and the like described herein may be implemented in one or more thread.
  • the thread may spawn other threads that may have assigned priorities associated with them; the processor may execute these threads based on priority or any other order based on instructions provided in the program code.
  • the processor may include memory that stores methods, codes, instructions and programs as described herein and elsewhere.
  • the processor may access a storage medium through an interface that may store methods, codes, and instructions as described herein and elsewhere.
  • the storage medium associated with the processor for storing methods, programs, codes, program instructions or other type of instructions capable of being executed by the computing or processing device may include but may not be limited to one or more of a CD-ROM, DVD, memory, hard disk, flash drive, RAM, ROM, cache and the like.
  • a processor may include one or more cores that may enhance speed and performance of a multiprocessor.
  • the process may be a dual core processor, quad core processors, other chip-level multiprocessor and the like that combine two or more independent cores (called a die).
  • the methods and systems described herein may be deployed in part or in whole through a machine that executes computer software on a server, client, firewall, gateway, hub, router, or other such computer and/or networking hardware.
  • the software program may be associated with a server that may include a file server, print server, domain server, internet server, intranet server, cloud server, and other variants such as secondary server, host server, distributed server and the like.
  • the server may include one or more of memories, processors, computer readable media, storage media, ports (physical and virtual), communication devices, and interfaces capable of accessing other servers, clients, machines, and devices through a wired or a wireless medium, and the like.
  • the methods, programs, or codes as described herein and elsewhere may be executed by the server.
  • other devices required for execution of methods as described in this application may be considered as a part of the infrastructure associated with the server.
  • the server may provide an interface to other devices including, without limitation, clients, other servers, printers, database servers, print servers, file servers, communication servers, distributed servers, social networks, and the like. Additionally, this coupling and/or connection may facilitate remote execution of program across the network. The networking of some or all of these devices may facilitate parallel processing of a program or method at one or more location without deviating from the scope of the disclosure.
  • any of the devices attached to the server through an interface may include at least one storage medium capable of storing methods, programs, code and/or instructions.
  • a central repository may provide program instructions to be executed on different devices.
  • the remote repository may act as a storage medium for program code, instructions, and programs.
  • the software program may be associated with a client that may include a file client, print client, domain client, internet client, intranet client and other variants such as secondary client, host client, distributed client and the like.
  • the client may include one or more of memories, processors, computer readable media, storage media, ports (physical and virtual), communication devices, and interfaces capable of accessing other clients, servers, machines, and devices through a wired or a wireless medium, and the like.
  • the methods, programs, or codes as described herein and elsewhere may be executed by the client.
  • other devices required for execution of methods as described in this application may be considered as a part of the infrastructure associated with the client.
  • the client may provide an interface to other devices including, without limitation, servers, other clients, printers, database servers, print servers, file servers, communication servers, distributed servers and the like. Additionally, this coupling and/or connection may facilitate remote execution of program across the network. The networking of some or all of these devices may facilitate parallel processing of a program or method at one or more location without deviating from the scope of the disclosure.
  • any of the devices attached to the client through an interface may include at least one storage medium capable of storing methods, programs, applications, code and/or instructions.
  • a central repository may provide program instructions to be executed on different devices.
  • the remote repository may act as a storage medium for program code, instructions, and programs.
  • the methods and systems described herein may be deployed in part or in whole through network infrastructures.
  • the network infrastructure may include elements such as computing devices, servers, routers, hubs, firewalls, clients, personal computers, communication devices, routing devices and other active and passive devices, modules and/or components as known in the art.
  • the computing and/or non-computing device(s) associated with the network infrastructure may include, apart from other components, a storage medium such as flash memory, buffer, stack, RAM, ROM and the like.
  • the processes, methods, program codes, instructions described herein and elsewhere may be executed by one or more of the network infrastructural elements.
  • SaaS software as a service
  • PaaS platform as a service
  • IaaS infrastructure as a service
  • the methods, program codes, and instructions described herein and elsewhere may be implemented on a cellular network having multiple cells.
  • the cellular network may either be frequency division multiple access (FDMA) network or code division multiple access (CDMA) network.
  • FDMA frequency division multiple access
  • CDMA code division multiple access
  • the cellular network may include mobile devices, cell sites, base stations, repeaters, antennas, towers, and the like.
  • the cell network may be a GSM, GPRS, 3G, EVDO, mesh, or other networks types.
  • the methods, program codes, and instructions described herein and elsewhere may be implemented on or through mobile devices.
  • the mobile devices may include navigation devices, cell phones, mobile phones, mobile personal digital assistants, laptops, palmtops, netbooks, pagers, electronic books readers, music players and the like. These devices may include, apart from other components, a storage medium such as a flash memory, buffer, RAM, ROM and one or more computing devices.
  • the computing devices associated with mobile devices may be enabled to execute program codes, methods, and instructions stored thereon. Alternatively, the mobile devices may be configured to execute instructions in collaboration with other devices.
  • the mobile devices may communicate with base stations interfaced with servers and configured to execute program codes.
  • the mobile devices may communicate on a peer-to-peer network, mesh network, or other
  • the program code may be stored on the storage medium associated with the server and executed by a computing device embedded within the server.
  • the base station may include a computing device and a storage medium.
  • the storage device may store program codes and instructions executed by the computing devices associated with the base station.
  • the computer software, program codes, and/or instructions may be stored and/or accessed on machine readable media that may include: computer components, devices, and recording media that retain digital data used for computing for some interval of time; semiconductor storage known as random access memory (RAM); mass storage typically for more permanent storage, such as optical discs, forms of magnetic storage like hard disks, tapes, drums, cards and other types; processor registers, cache memory, volatile memory, non-volatile memory; optical storage such as CD, DVD; removable media such as flash memory (e.g.
  • RAM random access memory
  • mass storage typically for more permanent storage, such as optical discs, forms of magnetic storage like hard disks, tapes, drums, cards and other types
  • processor registers cache memory, volatile memory, non-volatile memory
  • optical storage such as CD, DVD
  • removable media such as flash memory (e.g.
  • USB sticks or keys floppy disks, magnetic tape, paper tape, punch cards, standalone RAM disks, Zip drives, removable mass storage, off-line, and the like; other computer memory such as dynamic memory, static memory, read/write storage, mutable storage, read only, random access, sequential access, location addressable, file addressable, content addressable, network attached storage, storage area network, bar codes, magnetic ink, and the like.
  • the methods and systems described herein may transform physical and/or or intangible items from one state to another.
  • the methods and systems described herein may also transform data representing physical and/or intangible items from one state to another.
  • the depicted elements and the functions thereof may be implemented on machines through computer executable media having a processor capable of executing program instructions stored thereon as a monolithic software structure, as standalone software modules, or as modules that employ external routines, code, services, and so forth, or any combination of these, and all such
  • implementations may be within the scope of the present disclosure.
  • machines may include, but may not be limited to, personal digital assistants, laptops, personal computers, mobile phones, other handheld computing devices, medical equipment, wired or wireless communication devices, transducers, chips, calculators, satellites, tablet PCs, electronic books, gadgets, electronic devices, devices having artificial intelligence, computing devices, networking equipment, servers, routers and the like.
  • the elements depicted in the flow chart and block diagrams or any other logical component may be implemented on a machine capable of executing program instructions.
  • the methods and/or processes described above, and steps associated therewith, may be realized in hardware, software or any combination of hardware and software suitable for a particular application.
  • the hardware may include a general- purpose computer and/or dedicated computing device or specific computing device or particular aspect or component of a specific computing device.
  • the processes may be realized in one or more
  • microprocessors microcontrollers, embedded microcontrollers, programmable digital signal processors or other programmable device, along with internal and/or external memory.
  • the processes may also, or instead, be embodied in an application specific integrated circuit, a programmable gate array, programmable array logic, or any other device or combination of devices that may be configured to process electronic signals. It will further be appreciated that one or more of the processes may be realized as a computer executable code capable of being executed on a machine-readable medium.
  • the computer executable code may be created using a structured programming language such as C, an object oriented programming language such as C++, or any other high-level or low-level programming language (including assembly languages, hardware description languages, and database programming languages and technologies) that may be stored, compiled or interpreted to run on one of the above devices, as well as heterogeneous combinations of processors, processor architectures, or combinations of different hardware and software, or any other machine capable of executing program instructions.
  • a structured programming language such as C
  • an object oriented programming language such as C++
  • any other high-level or low-level programming language including assembly languages, hardware description languages, and database programming languages and technologies
  • methods described above and combinations thereof may be embodied in computer executable code that, when executing on one or more computing devices, performs the steps thereof.
  • the methods may be embodied in systems that perform the steps thereof, and may be distributed across devices in a number of ways, or all of the functionality may be integrated into a dedicated, standalone device or other hardware.
  • the means for performing the steps associated with the processes described above may include any of the hardware and/or software described above. All such permutations and combinations are intended to fall within the scope of the present disclosure.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Theoretical Computer Science (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • General Physics & Mathematics (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Health & Medical Sciences (AREA)
  • Data Mining & Analysis (AREA)
  • Computing Systems (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention concerne des systèmes et des procédés pour permettre une planification et une promotion d'événement à l'aide d'outils de collaboration en ligne parmi un groupe de personnes, le groupe arrivant à une décision, telle qu'une décision quant à la nature et/ou la logistique correspondant à un événement auquel le groupe souhaite participer, et les outils de collaboration comprenant la capacité de fournir des liens pour réaliser des transactions associées à l'événement défini.
PCT/US2014/044108 2013-06-25 2014-06-25 Système et procédé pour une promotion d'événement en ligne et une panification de groupe WO2014210162A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201361838963P 2013-06-25 2013-06-25
US61/838,963 2013-06-25

Publications (1)

Publication Number Publication Date
WO2014210162A1 true WO2014210162A1 (fr) 2014-12-31

Family

ID=52142648

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2014/044108 WO2014210162A1 (fr) 2013-06-25 2014-06-25 Système et procédé pour une promotion d'événement en ligne et une panification de groupe

Country Status (1)

Country Link
WO (1) WO2014210162A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114006768A (zh) * 2021-11-18 2022-02-01 浙江小易信息科技有限公司 一种基于第三方平台的信息交互方法
US11403312B2 (en) 2016-03-14 2022-08-02 Microsoft Technology Licensing, Llc Automated relevant event discovery
US11763222B2 (en) 2020-08-22 2023-09-19 Stellar Idea Labs System and method for event planning and management

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20060114986A (ko) * 2005-05-03 2006-11-08 에스케이커뮤니케이션즈 주식회사 인터넷을 이용한 모임 생성, 관리 및 평가 시스템, 방법 및이를 구현할 수 있는 컴퓨터로 읽을 수 있는 기록 매체
US20090006111A1 (en) * 2007-06-29 2009-01-01 Microsoft Corporation Event negotiation
US20100153284A1 (en) * 2008-12-17 2010-06-17 Black Drumm, Inc. Methods and systems to use an aggregated contact list for sharing online information
US20120136689A1 (en) * 2010-11-30 2012-05-31 Microsoft Corporation Event planning within social networks
US20120179981A1 (en) * 2011-01-07 2012-07-12 Meetup, Inc. Collaboration Meeting Management in a Web-Based Interactive Meeting Facility

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20060114986A (ko) * 2005-05-03 2006-11-08 에스케이커뮤니케이션즈 주식회사 인터넷을 이용한 모임 생성, 관리 및 평가 시스템, 방법 및이를 구현할 수 있는 컴퓨터로 읽을 수 있는 기록 매체
US20090006111A1 (en) * 2007-06-29 2009-01-01 Microsoft Corporation Event negotiation
US20100153284A1 (en) * 2008-12-17 2010-06-17 Black Drumm, Inc. Methods and systems to use an aggregated contact list for sharing online information
US20120136689A1 (en) * 2010-11-30 2012-05-31 Microsoft Corporation Event planning within social networks
US20120179981A1 (en) * 2011-01-07 2012-07-12 Meetup, Inc. Collaboration Meeting Management in a Web-Based Interactive Meeting Facility

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11403312B2 (en) 2016-03-14 2022-08-02 Microsoft Technology Licensing, Llc Automated relevant event discovery
US11763222B2 (en) 2020-08-22 2023-09-19 Stellar Idea Labs System and method for event planning and management
CN114006768A (zh) * 2021-11-18 2022-02-01 浙江小易信息科技有限公司 一种基于第三方平台的信息交互方法

Similar Documents

Publication Publication Date Title
US20140052485A1 (en) System and method for on-line event promotion and group planning
US10742433B2 (en) Web-based interactive meeting facility, such as for progressive announcements
US11449859B2 (en) System and method for enabling a user to choose how to redeem a gift credit
US9654425B2 (en) System and method for communicating among members of meeting groups
US10298410B2 (en) Progressive announcements in a web-based interactive meeting facility
US9264462B2 (en) System and method for confirming attendance for in-person meetings or events
US9117220B2 (en) Web-based interactive meeting facility with revenue generation through sponsorship
US8904295B2 (en) Web-based interactive meeting facility with recommendations to users
US9947053B2 (en) System and method for conditional group membership fees
US20120179981A1 (en) Collaboration Meeting Management in a Web-Based Interactive Meeting Facility
US8359206B2 (en) Web based interactive meeting facility
US20140310046A1 (en) System and method for on-line event promotion and group planning
US20110289142A1 (en) Web-Based Interactive Meeting Event Facility
US20130346226A1 (en) Systems and methods for event planning and participation and a ballot platform for transactions for goods and services
US20140200942A1 (en) Method and system for managing schedules
CA2823256C (fr) Gestion collaborative de reunions dans une fonctionnalite de reunion interactive par web
CA2799838A1 (fr) Fonctionnalite web interactive pour la gestion d'evenements collaboratifs
WO2014210162A1 (fr) Système et procédé pour une promotion d'événement en ligne et une panification de groupe
Crnkovic Invited article: the future of CRM is UX
US11763222B2 (en) System and method for event planning and management
Berndt E-procurement for destination management companies within the tourism industry in South Africa: digital era trends, challenges and responses
Roldan ADAPTABILITY TO DIGITAL TOURISM BY THE TRAVEL AND TOUR OPERATORS IN ALBAY
WO2009152227A2 (fr) Fonctionnalité de réunion interactive sur le web
WO2012016112A2 (fr) Commande automatique d'un groupe de réunion dans une installation de réunion interactive sur internet
Ortiz Social media in e-government: Social media utilization by municipal governments to enhance transparency, participation and collaboration among all generations of users

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: 14818361

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14818361

Country of ref document: EP

Kind code of ref document: A1