WO2017059523A1

WO2017059523A1 - Collaborative networked transaction-building tool

Info

Publication number: WO2017059523A1
Application number: PCT/CA2016/000253
Authority: WO
Inventors: Riaz PISANI
Original assignee: Snowstorm Technologies Inc.
Priority date: 2015-10-07
Filing date: 2016-10-07
Publication date: 2017-04-13

Abstract

Systems, devices, and stored, machine-interpretable instruction sets for the secure, collaborative, efficient, and convenient processing of transaction data, and methods of using them. The invention may be particularly useful for building data sets useful in the purchase, sale, leasing, or other transfer of rights in products, services, and real and intangible properties. Through the use of specifically-assigned persistent resource locators, users are enabled to build individual and group transaction data sets that may be associated with variable levels of access to group and non-group members. When users have established desired transaction data sets, they can optionally execute simultaneously one or more related transactions. Data generated by such processes can be used in conjunction with predictive analytics processes in order to improve transaction building processes and user experiences.

Description

COLLABORATIVE NETWORKED TRANSACTION-BUILDING TOOL

CROSS-REFERENCE TO RELATED APPLICATIONS

AND DISCLAIMER

[0001] This application claims all benefit, including priority, of United States Provisional Patent Application Serial No. 62/238,376, filed 7 October 2015 and entitled Collaborative Networked Transaction-Building Tool; of United States Provisional Patent Application Serial No. 62/323,331 , filed 15 April 2016 and entitled Collaborative Networked Transaction-Building Tool; and of United States Provisional Patent Application Serial No. 62/329,093, filed 28 April 2016 and entitled Collaborative Networked Transaction-Building Tool; the entire contents of each of which are incorporated herein by this reference.

[0002] Aspects of the material disclosed in this application relate to the generation, administration, manipulation, processing, and storage of data useful in processing of payment and other transactions in property, services, and information. Aspects of such generation, administration, manipulation, processing, and storage may be subject to regulation by governmental and other agencies. The disclosure herein is made solely in terms of logical, economic, and physical communications possibilities, without regard to statutory, regulatory, or other legal considerations. Nothing herein is intended as a statement or representation that any system, method or process proposed or discussed herein, or the use thereof, does or does not comply with any statute, law, regulation, or other legal requirement in any jurisdiction; nor should it be taken or construed as doing so. FIELD OF THE INVENTION

[0003] The present disclosure relates to improved electronic data processing and communication systems, and related programming structures and stored media; the implementation of which open up new and very useful possibilities for collaborative transaction building and execution. In particular, the disclosure relates to devices, systems, methods, and machine-interpretable programming and/or other stored data products for the secure, collaborative, efficient, and convenient communication and processing of transaction data between pluralities of networked data processing devices.

BACKGROUND OF THE INVENTION

[0004] Systems for enabling consumers and other users of electronic data processing systems to access electronic communications networks and thereby assess remotely-stored data representing products, services, and other items they might wish to purchase, rent, or otherwise make use of, through, for example, the completion of purchases and other transactions are known. However, such systems are adapted for use by individual purchasers, who, should the wish to consult others about their purchases, are left to find alternate means to communicate with others in order to do.

[0005] In particular, it has not previously been known to effectively enable users of pluralities of geographically or electronically dispersed computers to access transaction resources via a network, and to collaborate in the investigation, negotiation, and execution or other completion of transactions. This is particularly true where multiples of such users may wish to cooperate in a common purchase, or to purchase the same or complementary items for coordinated purposes.

SUMMARY OF THE INVENTION

[0006] In various aspects, the present disclosure provides devices, systems, devices, persistently-stored, machine-interpretable programming and/or other data products for the secure, collaborative, efficient, and convenient processing of transaction data, and methods of using them. In particular, the disclosure provides devices, systems, and computer program products for the secure, collaborative, efficient, and convenient building of executable transaction data sets suitable for use in connection with the purchase, sale, leasing, or other transfer of rights in products, services, and real and intangible properties.

[0007] Among the many advantages offered by the invention is the enablement of the execution of multiple, coordinated, transactions by pluralities of distinct entities or individuals, and/or coordinated execution of a single transaction on behalf of and/or with the authorization of multiple transaction participants.

[0008] For example, in one aspect the invention provides collaborative networked transaction-execution tools. Such a tool can comprise at least one electronic data processor and at least one network communication signal processor. The at least one electronic data processor can be configured to receive, from a networked communication device associated with a transaction request originator, via the at least one network communication signal processor, signals representing a transaction collaboration request data set, the transaction collaboration data set comprising at least one network identifier associated with the transaction request originator and an identifier associated with each of one or more transaction request participant invitees. The data processor can further be configured to, through use of the transaction collaboration data set, establish a stored transaction collaboration data set accessible by the transaction request originator and by each of the one or more transaction request participant invitees via a dedicated persistent network collaboration resource address; establish a transaction request participant data set corresponding to each of the transaction request originator and each transaction request participant invitee, each transaction request participant data set accessible by its corresponding transaction request participant, via a corresponding dedicated persistent participant resource address; generate a transaction collaboration invitation data set corresponding to each transaction request participant invitee; and, using the same or another network communication signal processor, route each said transaction collaboration invitation data set to a networked communication device associated with the corresponding transaction request participant invitee.

[0009] Among other advantages, this aspect of the invention enables both transaction request originators and other transaction collaboration participants to share and collectively (i.e., collaboratively) assess data relating to proposed transactions, while simultaneously maintaining some of the information they have provided, or otherwise designated, for use in such assessments to be stored separately, in privately-controlled data sets.

[0010] In various embodiments, for example, such aspect of the invention further provides collaborative networked transaction-execution tools in which the at least one electronic data processor is configured to receive, from the same or another networked communication device associated with the transaction request originator, via the at least one network communication signal processor, a transaction originator data set pertaining to a proposed collaborative transaction project, the transaction originator data set comprising at least one identifier associated with the proposed collaborative transaction project. At least some of the transaction originator data set can be stored in either or both of memory which controllably associated with the stored transaction collaboration data set and memory controllably associated with the transaction request participant data set corresponding to the transaction request originator. In other words, such data may be stored in a shared, collaborative data set accessible by all or at least some of the transaction request participants and in memory which can be accessed solely by the request originator.

[0011] In such embodiments the data processor(s) can further be configured to receive, from a networked communication device associated with at least a first corresponding transaction request participant invitee via the at least one network communication signal processor, a transaction participant data set pertaining to the proposed collaborative transaction project; and to store at least some of the transaction participant data set in either or both of memory controllably associated with the stored transaction collaboration data set memory controllably associated with the first corresponding transaction request participant invitee. In other words, in some embodiments transaction request participants other than the originator(s) may be enabled both to share data with the larger collaboration group and to keep some or all of the same and other data in memory which is accessible only by the participant(s) who provided it.

[0012] In various aspects and embodiments, the invention further enables the simultaneous, synchronized, and/or otherwise coordinated execution of collaborative transaction(s). For example, in embodiments adapted for the collaborative building of travel itineraries, multiple collaborating travelers may be enable to purchase multiple seats on one or more flights, cruises, and / or other means of conveyance, book lodging, food, and other forms of accommodation, etc., simultaneously, and/or in other synchronized or otherwise coordinate fashion.

[0013] For example, in various aspects and embodiments the invention provides systems in accordance with the foregoing, wherein the at least one electronic data processor is configured to receive, from at least one networked communication device associated with at least one of the transaction request originator and at least one transaction request participant invitee, via the at least one network communication signal processor, at least one collaborated transaction execution instruction; generate, using data stored in the transaction collaboration data set and at least one of transaction originator data and a transaction request participant data set, at least one collaborated transaction execution data set; and, using the at least one communication signal processor, route the at least one collaborated transaction execution data set to at least one networked communication device associated with at least one third-party project fulfillment counterparty such as an airline, cruise line, or other transportation service provider, hotel service provider, or travel agent or broker.

[0014] A further advantageous feature offered by various aspects and embodiments of the invention is the use of predictive analytic engines executing algorithms adapted to monitor participant inputs and build data sets representing helpful suggestions for transaction options and improvements, such as recommended flights, accommodations, etc.

[0015] For example, in various aspects and embodiments data processors in accordance with any or all of the foregoing can be configured to route at least some of the data received from the transaction request originator and the at least one transaction request participant invitee to a predictive analytics engine; cause the predictive analytics engine use such routed data to generate predicted relevant transaction preference data sets associable with the proposed collaborative transaction project, or future collaborative projects of the same and/or other participants; and store the at least one predicted relevant transaction preference data set data set in memory controllably associated with the stored transaction collaboration data set.

BRIEF DESCRIPTION OF THE DRAWINGS

[0016) Various aspects and embodiments of the invention are illustrated in the accompanying drawings, which are meant to be exemplary and not limiting, and in which like references are intended to refer to like or corresponding parts.

[0017] Figure 1 is a schematic block diagram showing an embodiment of a collaborative research tool system in accordance with the invention.

[0018] Figure 2 is a schematic diagram of a process of building a collaborative transaction request data set in accordance with various aspects and embodiments of the invention. [0019] Figures 3 - 14 are schematic diagrams showing embodiment of user interface displays and processes suitable for use in implementing aspects of the invention. DESCRIPTION OF EMBODIMENTS

[0013] In various aspects and embodiments, the disclosure provides devices, systems, and computer program products for the secure, collaborative, efficient, and convenient building of executable transactions suitable for use in connection with the purchase, sale, leasing, or other transfer of rights in products, services, and intangible properties, using networked computer systems and various components thereof, and methods of using such devices, systems, and products. In particular, as will be seen, the invention enables the execution of multiple collaborative or otherwise coordinated transactions among arbitrary numbers of independent parties who are, for example, using separate computer systems.

[0014] Figure 1 is a schematic block diagram showing an embodiment of a system or architecture 1000 suitable for use in implementing various aspects and embodiments of a collaborative networked transaction-building tool in accordance with the invention.

[0015] In the embodiment shown in Figure 1 , a system 1000 comprises a plurality of collaboration participant systems 100; at least one collaborative transaction building and execution system 500; a plurality of social platform systems 401 ; and a plurality of provider or fulfillment systems 301.

[0016J As will be readily appreciated by those skilled in the relevant arts, components 100, 301 , 401 , 500, etc., may be implemented using any electronic signal/data processors, such as smart phones and other mobile network communications systems, desktop or server-class networked stationary platforms, etc., suitable for configuration to accomplish the purposes disclosed herein; and they may be implemented in any numbers desired. They may each or all be communicatively linked using any suitable wireline or wireless communications systems, including any or all of any suitable radio, cellular telephone, public switched telephone, and local and/or wide-area network technologies and protocols 150, including for example the internet and IP protocols such as hypertext transfer protocol (HTTP).

[0017] Transaction participant systems / devices 100 can include one or more request originator devices 101 and one or more collaborator devices 102a, 102b, etc.

[0018] Collaborative transaction system(s) 500 in accordance with the invention can comprise one or more CPUs or other electronic data processors 507 and network communication signal processors 503; and can comprise or otherwise have access to one or more social platform servers 506 and predictive analytic engines or applications 504. They can be configured to generate, maintain, and otherwise process transaction collaboration data sets 501 and participant data sets 502 as described herein.

[0019] As will be appreciated by those skilled in the relevant arts, a collaboration service provider 500 in accordance with the invention can be implemented on a single device, such as a standalone desktop or server-class computer; and/or it can be implemented using a distributed architecture, so that any or all of its components 501 , 502, 504, 506, etc., may be hosted partly or entirely on one or more communicatively-linked distributed data processing systems. System 500 is shown in a single broken box in Figure 1 merely as a convenience in aiding understanding of the invention.

[0020] A user 104 such as an individual; broker, agent, or other business; consumer; or other entity wishing to collaborate with one or more friends, colleagues, business partners, etc., 250a, 250b, etc. in investigating and completing a purchase or other transaction of any product, service, or other real or intangible property may use a suitably-configured system 1000 to access an internet- or otherwise-networked resource using a user system or device 100, 101 such as a smart phone or mobile or desktop computer. For example, such a user may use a browser or other application operating on a user device 100, 101 to navigate a network 150 to a network resource operated by a collaborative transaction service provider system 500. Collaborative transaction service provider system 500 can enable the user 104 to access resources adapted to generate one or more transaction collaboration data sets 501 , invite one or more participants/collaborators 250 to collaborate in building a collaborative transaction request data set, and requesting execution of one or collaborative transaction requests through data exchanges with one or more provider / fulfillment systems 301.

[0021] Optionally, collaborative transaction service provider system(s) 500 can, in addition, provide predictive analytic applications or functionalities 504, to enable generation and presentation to some or all of users 104, 250 of helpful transaction proposals.

[0022] Collaboration between users 104, 250 in building transaction request data sets can be facilitated through provision by the collaborative transaction system 500 of integrated social platform functionalities by means of social platform server(s) or application(s) 506. For example, collaborating participants 104, 250 can be enabled to conveniently text or chat with each other, post proposals, etc., by building off familiar social platform features.

[0023] For example, a collaboration service provider 500 can interpret instruction signals received from a request originator device 101 to cause generation of a suitably-configured shared user interface, and thereby enable the user 104 to navigate through any one or more social platform provider(s) 401 , etc., to invite any number of collaborator(s) 250a - 250x to participate in a search and optional transaction execution process to purchase travel tickets, consumer appliances, real estate, or any other suitable product, service, or property, from any one or more providers 301 -30n. As described in further detail below, such user(s) 104, 205x can use the tool 500 to build a virtual network space that provides links and/or full or redacted information pertaining to any one or more products, etc., which may be viewed and saved for purposes of comparison, selection, and purchase, etc.

[0024] As described below, the invention may be readily adapted for use among individual users 104, 250, in "business to consumer" or "B2C" embodiments; and/or between professional agents or purchasers, such as travel agents or corporate purchase departments, and goods or services providers, in "business-to- business" or "B2B" embodiments.

[0025] In various B2C and other embodiments, collaborators 250x and collaborator systems 201 , 20n may simply be thought of as additional user(s) 104 and system(s) 100. In such cases, the user 104 may simply be thought of as the first of the several collaborators 250 to initiate a collaborative transaction.

[0026] In various B2B or B2B2C embodiments, participants 101 , 102 can include agents, brokers, and other service providers engaged in assisting individuals or businesses 104, 250 in collaborative transaction building processes.

[0027] Figure 2 is a schematic diagram of a process 2000 of building a collaborative transaction request data set in accordance with various aspects and embodiments of the invention. Process 2000 of Figure 2 is suitable, for example, for implementation by one or more users 104, 250 of a system 1000 such as that shown in Figure 1.

[0028] At 2002, a computer or other electronic data processor of a collaborative networked transaction-execution tool 500 can, by accessing and executing locally and / or remotely-stored data representing suitably-configured machine-executable instructions, receive or otherwise access, via network communication signal processor(s) 503, a transaction collaboration request data set generated or otherwise routed to the collaborative transaction system 500 by a transaction request originator system 100.

[0029] For example, a user 104 of a desktop or mobile device 100, 101 wishing to initiate a collaborative process for generating a collaborated transaction request can use a network browser application resident on the device to navigate to a collaborative transaction service hosted by a collaborative transaction system 500 and access a user interface 3000 such as that shown in Figure 3. Using a touchscreen, keyboard, pointing device, or other input device, the user 104 can initiate a variety of operations to begin building a collaborative transaction execution data set.

[0030J For example, in the embodiment shown in Figure 3, the user 104 can start by selecting one of interactive command items 3004 to invoke processes for inviting one or more friends, business partners, or other participant invitees 102 to join in a collaboration process using e-mail or any of a variety of social platforms. Selection of an interactive command item 3004, 3014 "E-mail", for example, can cause the collaborative transaction system 500 to generate and route to the user 104's device 100, 101 a data set suitable for causing the device 100, 101 to display a user interface screen 4000 such as that shown in Figure 4. Using interactive command input devices 4002, the user 104 can input names, e-mail and/or other network addresses, and/or other identifiers associated with a plurality of participant invitees 250, and if desired can use field(s) 4004 to add text messages, images, and/or other information to be routed to such users as part of a transaction collaboration invitation data set. In the event the user 104 decides to use another form of communication to invite the prospective participants 250, the user 104 can select any of command devices 4010 to select from one or more social media platforms, etc. , in order to generate and route suitable invitation(s).

[0031] An originating user 104 can also provide information about a proposed collaborative transaction, for consideration by invitee participants 250. For example, using a text field 4004 or other devices, the originating user 104 can name a proposed transaction (e.g., "Pilgrimage to Guadalupe") and share the name with the invitees, both as a means of identifying corresponding data set(s) 501 , 502, and helping to differentiate the transaction in the minds of the individual participants. For example, an originating user, upon navigating to a collaborative transaction service hosted by a collaborative transaction system 500 can access a user interface 5000 such as that shown in Figure 5 and may be invited to provide command inputs adapted to access an existing transaction proposal or propose a new collaborative transaction (e.g. , by selecting an interactive item 5002, or using search device(s) 5004.

[0032] When the user 104 is satisfied with the identification of desired invitee(s) and information to be communicated to them, the user 104 can, by selecting command item 4006, cause his or her device 100, 101 to generate a transaction collaboration data set comprising at least one network identifier (e.g., a an e-mail or other network address entered at 4002) associated with the originating user 104 (i.e., the transaction request originator), and one or more network identifiers (e.g., an e-mail address entered at 4002) associated with the desired invitee(s). Any further desired information, such as one or more identifiers associated with the proposed collaborative transaction may also be included. The transaction collaboration request data set can then be routed to the collaborative transaction system 500, where it can be interpreted and further processed by CPU(s) or other processors 507 of the system 500, as noted above. [0033] Among other actions, at 2004 processor(s) 507 can establish a transaction collaboration data set 501 which is accessible by the request originator 104 and by some or optionally all participants or invitees 250. For example, the processor(s) 507 can cause generation of a persistent network collaboration resource by generating a corresponding shared resource address, in order to enable storage of data representing information related to the transaction request in conjunction with the shared resource address, and enabling access to the shared data 501 by participants 104, 250 authorized to access the shared resource address. Access to the shared transaction collaboration data set 501 can be controlled, for example, by associating unique combinations of one or more participant identifiers provided at 2002, including for example identifiers provided through a device 4002 as shown in Figure 4, with individual data sets 501 , 502. Such identifiers can, for example, including identifiers uniquely associated with one or more corresponding participants 104, 250, and one or more proposed transactions. For example, a participant 104, 250 can be required to present proper combinations of such identifier(s), establish passwords, etc., in order to be granted access to specific data sets 501 , 502.

[0034] Among options for persistent network resources to be used for the building of collaborative transaction data sets 501 , 502 in accordance with the invention, a preferred option is the use of persistent uniform resource locators (PURLs, or Persistent URLs). As is known by those skilled in the relevant arts, a persistent URL is a network address, typically referring to a resource on the World Wide Web, that causes redirection of a data request, such as might be received from a user device 100, to another network resource. If, in for example a distributed data storage architecture, a network resource changes virtual or physical storage location(s), and hence uniform resource locator(s) (URL(s)), a PURL pointing to it can be automatically updated, and the requesting resource can be directed to it seamlessly. Thus, a requesting user or device can always use the same network address for seeking desired information, even though the resource in question may have moved.

[0035] A simple PURL can work, for example, by responding to an HTTP GET request with a type 302 response (equivalent to the HTTP status code 302, meaning "Found"). The response can contain an HTTP "Location" header, the value of which is a current URL to be used by the requesting resource to retrieve the desired data via a new HTTP GET request.

[0036] PURLs constitute one form of persistent identifier for virtual resources, i.e., persistent networked resource address. Other persistent identifier schemes include Digital Object Identifiers (DOIs), Life Sciences Identifiers (LSIDs) and "INFO" uniform resource identifiers (URIs). Any identifier(s) suitable for the purposes suggested or disclosed herein will serve for implementing various aspects and embodiments of the invention.

[0037] A further action that can be taken by processor(s) 507, once the collaborative transaction system 500 has received a collaborative transaction request, is the establishment, at 2006, 2008, of a plurality of transaction request participant data sets 502, optionally including one such data set 502 for the transaction request originator 104 as well as one for each transaction request participant invitee 250. In other words, a separate transaction request participant data set 502 can be established for each transaction request participant 104, 250. Each transaction request participant data set 502 is accessible by its corresponding transaction request participant 100 via a corresponding dedicated persistent participant resource address, and can be used to store and otherwise manage data related to the corresponding request participant 100. Access to the separate participant data sets 502 can be controlled, for example, through use of participant identifiers provided at 2002, including for example identifiers provided through a device 4002 as shown in Figure 4. For example, a participant 104, 250 can be required to present such identifier(s), establish passwords, etc., in order to be granted access.

[0038] In various embodiments, access to data sets 501 , 502 will most advantageously be tied to individual participants 104, 250, through the use of personal identifiers (e.g. , e-mail addresses and personal passwords), rather than participant systems 100, 101 , 102. In other embodiments, however, access can be tied to individual systems 100; or, in other embodiments, to defined combinations of users 104, 250 and systems 100.

[0039] Access to data sets 501 , 502 can further be facilitated through use of identifiers associated with the corresponding proposed transaction(s), such as any identifiers entered by the requestor 104 in response to interface devices 5000, etc., as described above.

[0040] For example, unique persistent resource identifiers such as PURLs can be uniquely associated with any or all of individual users 104, 250, sets of users 104, 250, and proposed transactions; and provision of such identifiers, and/or combinations thereof, by corresponding users 104, 250 can be required in order to for the users to be granted access.

[0041] A further action that can be taken by processor(s) 507, once the collaborative transaction system 500 has received a collaborative transaction request, is the generation by processor(s) 507, at 2010, of a plurality of transaction collaboration invitation data sets, optionally including one such set for each participant 250 identified in the request data set received by system 500 at 2002. Such invitation data sets can include network address information for routing the request, any further identifiers required or desired for aiding the invitees 250 to access and evaluate the shared collaboration data set 501 and any proposals identified therein, and the individual participant data set(s) 502 the invitee 250 is authorized to access.

[0042J Generated collaboration invitation data sets may be routed by processor(s) 507 to network addresses associated with the desired participants 250, using network communication signal processor(s) 503.

[0043] Once the collaboration invitation data sets have been routed to network addresses as described above, they may be accessed by invitees 250, using their respective participant devices 102, and data provided with the invitation data sets can be used by the participants 250 to access both the shared transaction collaboration data set 501 and their corresponding individual participant data sets 502.

[0044] Optionally, in order to participate in collaborative transaction processes, some or all of participants 104, 250 can be required to register with the collaboration system 500 by providing any required or otherwise useful identfiers. For example, such participants may be required to provide e-mail or other network address information, their personal name or a preferred user name, credit, debit, or other financial account information, etc. Alternatively, or in addition, some or all of participants 104, 250, may be granted access to data sets 501 , 502 and other functionality provided by system 500 without registering, i.e., without providing such information.

(0045] With data sets 501 , 502 generated, and associated with individual users or sets of users 104, 250 and specific proposed transactions (i.e., a proposed collaborative transaction project), a process 2012 - 2026 of collaboration among users 104, 250 in building a collaborated transaction execution data set can begin.

[0046] In general, users 104, 250 are enabled to access data sets 501 , 502 and store therein any desired information pertaining to the proposed collaborative transaction project. Such information can include data files such as data sets representing electronic documents (e.g., .pdf, .jpg and other types of data files); hypertext links and/or other active or inactive network resource identifiers; user- generated text; text, chat, and other messages generated, shared, or otherwise provided by social platforms or otherwise in accordance with social platform protocols, etc.

[0047] For example, as shown schematically in Figure 6, a set of collaborators

104, 250 have agreed, through a process 2002 - 2010 of proposing a collaboration, generating and routing invitations, and optionally either or both of accepting invitations and registering with a collaboration service provided by a system 500 to collaborate on a project related to the purchase of a new television by the originator 104. The project is identified by a title 6004 "My New TV"; a collaborative transaction system 500 has generated a specific corresponding shared data set 501 associated with the project 6004 and the users 104, 250. The system 500 has further generated individual participant data sets 501 a, 501 b, 501 c associated with the originating user 104 and with invited participants 250 "Friend 1 " and "Friend 2," respectively.

[0048] Using his/her device 100, 101 , the originating user 104 navigates to a user interface generated by the system 500, and through that interface to a third- party network resource (e.g., an e-shopping site) operated by a first electronic retailer 301 a, and has identified a Samsung 40" television, offered at $999.99 as one proposed purchase option. Having identified the television as an option, the user can cause data pertaining to the option to be used in generating a transaction originator data set and saved in the shared collaboration data set 501 , and optionally displayed on a corresponding user interface generated by system 500 and the user's device 100, 101. For example, processor(s) 507 of a system 500 can recognize at 2012 that new participant data pertaining to the Samsung television has been received, and at 2014 can cause the data to be saved in the collaborative data set 501. In addition, at 2016-2018 the system 500 can parse the received participant data to determine that it was provided by, or on behalf of, originating user 104, and at 2020 can cause the transaction originator data set to be saved in a participant data set 502a associated with the originating user 104.

[0049] The processor 507 can then return to a state of waiting for further input data.

[0050] In the meantime, user a user 250 "Friend 1 " can use her/his device

100, 102a to navigate to a user interface generated by the system 500 using data from the shared data set 501 and/or the user's specific participant data set 502b, and through that interface to a fourth-party network resource (e.g., an e-shopping site) operated by a first electronic retailer 301 b, and identifies a Vizio television offered at $259.99 as a second proposed purchase option. Having identified the television as an option, the user can cause data pertaining to the option to be routed to the system 500, where at 2012 it can be recognized and at 2014 saved in the shared collaboration data set 501. Optionally, at 2016-2018 the received participant data can be parsed, and at 2020 directed to the user 250's invitee participant data set 502b for storage and later use.

[0051] Similarly, a user 250 "Friend 2" can use her/his device 100, 102, to navigate to a user interface generated by the system 500 using data from the shared data set 501 and/or the user's specific participant data set 502c, and through that interface to a fifth-party network resource (e.g., an e-shopping site) operated by a first electronic retailer 301 c, and identifies a television offered at $329.99 and two Sony products offered at further prices as further proposed purchase options. Having identified these televisions as options, at 2014-2020 the user can cause data pertaining to the option to be saved in the shared collaboration data set 501 and optionally in the user 250's participant data set 502c.

[0052] Data added to the shared data set 501 and individual data sets 502a, 502b, 502c can be provided and/or stored in any desired forms, including for example ASCII characters, text documents (e.g. Word documents); text image documents (e.g., .pdf, .jpg, etc.) hypertext, and/or image or other media files.

[0053] Thus it is seen that processor(s) 507 of a system 500 can be configured to receive, from the same or another networked communication device 100, 101 associated with the transaction request originator 104, via the at least one network communication signal processor 503, a transaction originator data set pertaining to a proposed collaborative transaction project, the transaction originator data set comprising at least one identifier associated with the proposed collaborative transaction project (e.g., the project identifier "My New TV" and data pertaining to the 40" Samsung television set). The system 500 can further store at least some of the transaction originator data set in memory associated with the stored transaction collaboration data set 501 , access to which data is controlled through use of specific identifiers so as to allow access by all participants 104, 250 in the "My New TV" project, as described above. The processor(s) 507 can further be configured to store the same or another portion of the transaction originator data set in memory controllably associated with the transaction request participant data set 501 a corresponding to the transaction request originator.

[0054] It is further seen that the processor(s) 507 can further be configured to receive, from networked communication devices 100, 102a, 102b associated with each of a plurality of corresponding transaction request participant invitees 250 ("Friend 1 " and "Friend 2") via the at least one network communication signal processor 503, a transaction participant data set pertaining to the proposed collaborative transaction project; store at least some of the transaction participant data set in memory controllably associated with the stored transaction collaboration data set 501 ; and store the same or another portion of the transaction originator data set in memory 503b, 502c controllably associated with the corresponding transaction request participant invitee 250.

[0055] As noted previously, further options for collaboration in building execution request data sets pertaining to proposed transactions can comprise sharing of text, image, and other types of data by the participants 104, 250. For example, in the example of Figure 6, originator 104 and friends 250 can chat about their proposals, weigh pros and cons, photograph themselves or other objects with their proposed purchases, etc., and share them through shared data set 501. |0056] Users 104, 250 can also delete, replace, or otherwise modify their own previous postings, and optionally data sets posted by others. This functionality allows the users 104, 250 to negotiate different options, coordinate schedules, etc., until everyone is happy with proposed details of the transaction project.

[0057] When users 104, 250 are sufficiently agreed on proposed details of the transaction project, at 2022 - 2026 the originating user 104 and or one or more other participants or collaborators 250 can invoke processes for execution of some or all of the required purchases. In preferred embodiments of the invention, purchases of multiple parts of a transaction project - for example, multiple seats on an airplane, together with one or more hotel rooms and tour packages - can be executed simultaneously, or in other synchronized or coordinated fashion.

[0058] For example, agreed data stored in a transaction collaboration (shared) data set 501 can be presented on a device 100 of a user 104, 250 authorized to execute the transaction, with a suitable selectable command item for 'purchase' or 'execute'. Selection of the 'purchase' or 'execute' command item can cause the user's device 100 to generate a collaborated transaction execution instruction and route it to the system 500 via the network communication signal processor 503. Upon receipt of the collaborated transaction execution instruction at 2026 processor(s) 507 can review all data stored in the collaborated data set 501 , add any purchase details or authorizations (e.g., credit or other payment credentials) from one or more participant data sets, and/or from real-time touchscreen or keypad input, and at 2028 can generate a collaborated transaction execution instruction data set, the data set comprising identifiers related to corresponding provider/fulfillment system(s) 301 , purchased items (e.g., products or services), payment information (e.g. , credit, debit, or loyalty accounts); and routing information such as physical or network delivery addresses for products, paper or e-tickets, invoices, receipts, etc.; and can route pertinent portion(s) of the execution instruction data set to corresponding providers 301.

[0059] Thus, for example, one or more electronic data processors 507 of a system 500 can be configured to receive, from at least one networked communication device 100 associated with at least one of the transaction request originator 104 and/or at least one transaction request participant invitee 250, via the at least one network communication signal processor 503, at least one collaborated transaction execution instruction; generate, using data stored in the transaction collaboration data set and at least one of transaction originator data set 501 and a transaction request participant data set 502, at least one collaborated transaction execution data set; and, using the at least one communication signal processor 503, route the at least one collaborated transaction execution data set to at least one networked communication device 301 associated with at least one third-party project fulfillment counterparty.

[0060] Upon receipt of such a collaborated transaction execution data set, a receiving provider fulfillment counterparty can parse the data set to identify goods or services to be purchased, and can take suitable action to fulfill the request. For example, the fulfillment counterparty can contact an associated financial institution such as a bank, credit card service provider, or other payment service provider, have the transaction request adjudicated and approved, and route instructions for fulfillment of the request by shipping of goods and/or routing data confirming the purchase. Such data may be routed to user(s) 104, 250 directly or indirectly, e.g., through the collaborative transaction system 500 and/or via one or more financial service providers.

[0061] As noted above, a particularly advantageous feature offered by various aspects and embodiments of the invention is the use of predictive analytic engines 504 to execute algorithms adapted to monitor participant inputs and build data sets representing helpful suggestions for transaction options and improvements, such as recommended flights, accommodations, etc., for presentation to users 104, 250, etc., through data sets 501 , 502, or by routing such suggestions directly to one or more suitable user devices 100 via text, e-mail, audio, or other messages.

[0062] For example, in various aspects and embodiments data processors 507 in accordance with the foregoing can be configured to route at least some of the data received from the transaction request originator 104 and/or the at least one transaction request participant 250 to a predictive analytics engine 504; cause the predictive analytics engine 504 use the routed data to generate predicted relevant transaction preference data sets associable with the proposed collaborative transaction project, or future collaborative projects of the same and/or other participants 104, 250; and store the at least one predicted relevant transaction preference data set data set in memory 510 or otherwise controllably associated with the system 500 and/or the stored transaction collaboration data set 501 and/or one or more participant data sets 502.

[0063] In various preferred embodiments, all data interchanges between systems and devices 100, 301 , 401 , 500 are monitored, and relevant data stored and analyzed by predictive analytics engine(s) 504, through all steps 2002 - 2028 of process(es) 2000, and beyond.

(0064] As will be appreciated by those skilled in the relevant arts, data forwarded to a system 500 by users 104, 250 of devices 100 may be of many types: personal identifiers such as names, physical and network addresses (eg. e-mail and social media, telephone numbers, etc.); purchase preferences (types of products or services, sources of products and services, delivery preferences such as timing, etc.); and financial information such as account numbers, payment protocol preferences (credit or debit, loyalty accounts, etc), and purchase patterns. All of such data may be used to predict near- or long-term user purchase preferences, and thereby enable the offering of solicited or unsolicited helpful purchase suggestions.

|0065] As will be further appreciated by those skilled in the relevant arts, for rapid, high-volume purchase negotiation and execution processes, a computational system capable of processing, aggregating, and providing predictive analytics on uninterrupted high-volume (>500,000 records/second) data streams that are continuously changing in real-time is preferable. Therefore models for real-time aggregation of data streams from heterogeneous sources (text, audio, video, social media, mobile devices, GPS, etc.) without a predefined schema with the ability to detect relevant patterns in the streaming data are preferred for many embodiments. It can be advantageous for the processing speed of such architectures to remain substantially insensitive to the number of invoked third party API transmissions - i.e., receipt of data from any or all of devices 100, 101 , 102, 301 , 401 .

[0066] In various embodiments, predictive analytics engines 504 in accordance with the invention operate using solely or primarily data stored in data stores 501 , 502, and not on uninterrupted data streams from devices 100, 300, 400, etc., that are continuously or continually changing in real time.

[0067] Data streams which are generated by the sources 100, 301 , 401 , etc. and aggregated by a system 500 can be expected to have a significantly better success rate of achieving any aggregation process at a very fast speed - in the orders of megabytes of data within a couple of milliseconds, at least partly because the system 500 can cause the devices 100, 301 , 401 , etc., to structure the data in a way that suits the aggregation process. However, in processing streaming data. |0068] In various embodiments, the invention further provides rapid processing by predictive analytics engine 504 through the splitting of incoming data streams into two groups, namely one for continually-changing data and the other consistently-formatted data. It is found, for example, that this can reduce reduce the number of required API interrogations at any given time, and thereby provide improved response times.

[0069] In the same and other embodiments, the invention provides improved processing by i) relaxing the data selection criteria original to the data stream APIs; ii) giving these APIs a broader selection; iii) moving more focused selection rules following a data aggregation process could improve the latency in calls to the external APIs by reducing the data selection (or filtering) response time at the API level; and/or iv) balancing data selection control between API levels and an intermediary layer connecting a data aggregation and harmonization process.

[0070] In some embodiments, the use of white noise filters and the aggregation and harmonization of data streams into consistent formats by predictive analytics engines 504, in order to generate blocks of data of uniform protocol, are also provided in order to improve the quality and efficiency of data collection processes.

[0071] The aggregation and harmonization of data APIs (i.e. changing data formats or protocols) by engine(s) 504 to generate unified blocks of data is in some embodiments improved by breaking down the aggregation and harmonization into smaller groups rather than using a single aggregation approach. Without imposing a restriction on the number of groups, each group of data in such embodiments can require segmentation based on content type only. In such embodiments, the use of mathematical algorithms to identify and sort data types can provide improvements over more cognitively-centered processes (e.g., categorizing data into groups of flight data, hotel data, car data, etc. and creating a harmonized data object to transform the response into). [0072] In further embodiments, predictive analytics engine(s) 504 in accordance with the invention implement temporary-key-value pairing approaches for streaming data selection; and fuzzy match algorithms for pairing data on the basis of percentage of accuracy.

[0073] In various embodiments, predictive analytics engines 504 in accordance with the invention employ harmonization layers to amalgamate different data splitting groups in real time, prior to analysis for generation of proposals for users 104, 250. For example, use of core XML-based data structures to permit grouping of heterogeneous data, such as data form-specific (specialized) XML objects for data extraction have been used advantageously, as have reflection techniques, which can enable development of processes to identify object types.

[0074] Preferred analytics engines 504 in accordance with the invention further use dynamic data objects capable of fast navigation, rather than on-the-fly reflection.

[0075] As previously noted, in various aspects and embodiments the invention is suited to the building and execution of collaborative transactions pertaining to a wide variety of goods, services, etc. In addition to the collaborative purchase of consumer items such as televisions, as shown in Figure 6, a particularly advantageous application of the invention is to the building of travel itineraries, and purchase of corresponding tickets, services, and reservations.

[0076] An example of application of a process 2000 to the collaborative building of a travel itinerary and coordinated purchase of tickets and reservations is provided with reference to Figures 3, 4, and 7 - 12.

[0077] In such a case a process 2000 can start at 2002, with receipt by a collaborative networked transaction-execution tool 500 of a transaction collaboration request data from a device 101 of an originating participant 104. For example, a user 104 of a desktop or mobile device 100, 101 wishing to initiate a collaborative process for generating a collaborated transaction request can use a network browser application resident on the device to navigate to a collaborative transaction service hosted by a collaborative transaction system 500 and access a user interface adapted for registration or log-in. Once the user 104 has provided sufficient identifiers (e.g., a name and e-mail or other network address), the user can be presented with an interface screen 3000 such as that shown in Figure 3. Using a touchscreen, keyboard, pointing device, or other input device, the user 104 can initiate any one or more of a variety of operations to begin building a collaborative transaction execution data set related to the desired travel project.

[0078] For example, in the embodiment shown in Figure 3, the user 104 can start by selecting an interactive command item 3002 to browse or otherwise identify one or more proposed destinations. Alternatively, the user can browse hotels, flights, rail connections, etc., by selecting one or more of command items 3006, 3008, etc. By selecting one of interactive command items 3004, the user 104 can invoke processes for inviting one or more friends, business partners, or other participant invitees 102 to join in a collaboration process using e-mail or any of a variety of social platforms. Selection of an interactive command item 3004, 3014 Έ- mail", for example, can cause the collaborative transaction system 500 to generate and route to the user 104's device 100, 101 a data set suitable for causing the device 100, 101 to display a user interface screen 4000 such as that shown in Figure 4. Using interactive command input devices 4002, the user 104 can input names, e- mail and/or other network addresses, and/or other identifiers associated with a plurality of participant invitees 250, and if desired can use field(s) 4004 to add text messages, images, and/or other information to be routed to such users as part of a transaction collaboration invitation data set. In the event the user 104 decides to use another form of communication to invite the prospective participants 250, the user 104 can select any of command devices 4010 to select from one or more social media platforms, etc., in order to generate and route suitable invitation(s).

[0079] The originating user 104 may also provide information about the proposed collaborative project for consideration by invitee participants 250. For example, using a text field 4004 or other devices, the originating user 104 can name a proposed transaction (e.g., "My Trip to Las Vegas") and share the name with the invitees, both as a means of differentiating the transaction in the minds of the individual participants / invitees (in case, for example, they are planning more than one trip together) and of enabling system 500 to establish and uniquely identify corresponding data set(s) 501 , 502.

[0080] When the user 104 is satisfied with the identification of desired invitee(s) and information to be communicated to them, the user 104 can, by selecting a command item 4006, cause his or her device 100, 101 to generate a transaction collaboration data set and comprising at least one network identifier (e.g., a an e-mail or other network address entered at 4002) associated with the originating user 104 (i.e., the transaction request originator), and one or more network identifiers (e.g., an e-mail address entered at 4002) associated with each of the desired invitee(s). Any further desired information, such as one or more identifiers associated with the proposed collaborative transaction, may also be included. The transaction collaboration request data set can then be routed to the collaborative transaction system 500, where it can be interpreted and further processed by CPU(s) or other processors 507 of the system 500, as noted above.

[0081] At 2004, as described above, the processor(s) 507 can establish a transaction collaboration data set 501 which is accessible by the request originator 104 and by some or optionally all participants or invitees 250 associated with the project "My Trip to Las Vegas." The processor(s) 507 can also establish, at 2006, 2008, a plurality of transaction request participant data sets 502, including one for each participant who has been invited to accept user 104's invitation and optionally including one such data set 502 for the transaction request originator 104 as well. In other words, a separate transaction request participant data set 502 can be established for each transaction request participant 104, 250.

[0082] Once the collaborative transaction system 500 has received the collaborative transaction request, at 2010 processor(s) 507, can generate a plurality of transaction collaboration invitation data sets, optionally including one such set for each participant 250 identified in the request data set received by system 500 at 2002, and can route them to the desired participants 250, using network communication signal processor(s) 503 as described above.

[0083] With the invitations sent, transaction system 500 can enter a state 2012 - 2026 of gathering responses from participants 250 to the invitations routed to them at 2010, and of gathering input from participants 104, 250 relating to options and selections for building their travel itinerary. In addition to posting of data related to travel options to data sets 501 , 502, the system 500 can facilitate discussions between participants 104, 250 using native social platforms (i.e., internal chat functions) and/or by interfacing with third-party social platforms 401 such as Facebook, Twitter, etc. [0084] For example, as shown in Figure 7, system 500 can generate a data set useable by devices 100 accessed by each of participants 104, 250 for presenting to such participants an interactive user interface 7000 comprising command items 7001 , 7002, 7010, 7090, etc.

[0085] Selection of any command items 7002 can open a separate display window, or section, adapted for text chatting with a participant identified, for example, by display of a photograph of the user. Alternatively, or in addition, item(s) 7002 can offer options of voice, e-mail, or any other desired forms of communication with participants 104, 250.

[0086] Command items 7090 can comprise images, text, and or other information generated by predictive analytics engine(s) 504, representing useful suggestions generated by the engine 504 and related to predicted preferences for travel, accommodation, or other anticipated desires of the user 104, 250 to whom the interface 7000 has been presented. As previously discussed, information presented in items 7090, and the corresponding underlying suggestions, can be based on any or all inputs made by the user 104, 250 to whom the display is presented, and/or any other participant(s) 250, 104 associated with the collaborative transaction project which is the subject of the current collaboration session.

[0087] Command items 7001 can be used to control generation of an interactive search panel 7010 adapted for searching for flights, automobiles, lodging, entertainment, cruises, or other types of possible transactions in goods or services related to the current project (in this case, "My Las Vegas Trip"). Selection of an item 7001 , 7003, for example, can result in generation of a search panel configured to enable a search for flights meeting one or more specific criteria. Depending upon the type of transaction selected from options 7001 , fields 701 1 may be displayed in panel 7010 in order to elicit input by the participant 104, 250 of relevant search parameters. In the example shown in Figure 7, for example, a panel 7010 adapted for searching for flight options can include input items 701 1 for selection of one-way, round-trip, or multi-city flights; corresponding proposed destinations; preferred dates of travel; and numbers of passengers and type or class of travel (e.g., economy, business class, etc.). [0088] As shown in Figure 8, selection of a "radio-button" type input command device 7004 "multi-city" can result in display of a search panel 7010, 7012 configured for input of cities or airports corresponding to three or more legs of a multi-city flight plan.

[0089] As shown in Figure 9, selection of input command items 701 1 in a search panel 7010 can result in presentation of pop-up, pull-down, or other types of input devices configured to aid in rapid and unambiguous input of relevant search criterial. For example, selection of a device 7005 "date" can result in presentation of an interactive calendar configured to enable the user 104, 250 to designate one or more preferred travel dates to be used in the search. Selection of an item 7006 "passengers & coach" can result in presentation of an interactive panel adapted for input of a number of adult, child, or other types of passengers, and selection of preferred class(es) of travel for one or more of the flight legs.

[0090] When the user 104, 250 has entered valid data relating to all required and/or otherwise desired criteria at fields 701 1 of panel 7010, the user can invoke a search function of system 500 by selecting search command ("Find Flights") 7070.

[0091] Invocation of search command icon (or "item") 7070 can cause the user's device 100 to generate and route to system 500 one or more command signals adapted to initiate any or all of several functions.

[0092] For example, invocation of a search command icon 7070 can cause processor(s) 507 of system 500 to search any internal databases comprising any data pertinent to the requesting user's search request. For example, in embodiments of the invention in which a system 500 comprises internal database(s) 510 of goods or services pertinent to the transaction the user 104, 250 is preparing to request, invocation of icon 7070 can cause a search of such database(s) 510 for data sets comprising one or more of the designated search criteria.

[0093] Alternatively, or in addition, invocation of a search command icon 7070 can cause processor(s) 507 of system 500 to generate and route search inquiry data sets configured for searching databases of external provider or fulfillment system(s) 301 . Such search inquiry data sets can, for example, comprise data representing criteria designated by the user 104, 250 through panel 7010, and can be formatted in accordance with any protocol(s) useable by the corresponding systems 301. Generated search inquiry data sets can be routed to corresponding provider / fulfillment system(s) 301 via network communication signal processor(s) 503.

[0094] When received by the corresponding provider / fulfillment system(s) 301 , the routed search inquiry data sets can cause the system(s) 301 to search any databases accessibly by the system(s) 301 comprising data sets comprising one or more of the designated search criteria.

[0095] In addition, invocation of a search command icon 7070 can cause processor(s) 507 of system 500 to route data representing the identity of the searching participant 104, 250, the date and time of the search request, the criteria designated, and/or any other desired information to predictive analytics engine(s) 504, for use in further internal and external search processes and generation of data sets representing recommendations for further refinements of the proposed transaction project, different transactions, or any other desired information that may be of use or interest to the user 104, 250, and/or any other participants in the transaction project.

[0096] Results of any resulting internal and/or external searches generated by internal processor(s) 507 and/or external system(s) 301 can be used to by processor(s) 507 to generate a search results data set configured for display by the device 100 of the participant 104, 250 who initiated the search, showing results of the search request.

[0097] For example, as shown in Figure 10, a user interface 7000 generated in response to a search request can comprise an interactive search results panel 7050 comprising any of a very wide variety of data related to the results of the requested search. In the embodiment shown, search results panel 7050 comprises a table 7052 of tabulated search results, comprising rows of flights satisfying some or all of the criteria used in the search request. As will be understood by those skilled in the relevant arts, such data may be presented in any one or more of a very wide variety of formats, according to the nature of the goods or services searched, the preferences of the requesting user, the quality, quantity, and/or relevance of returned results, etc. In the embodiment shown in Figure 9, each row corresponds to a flight meeting the user's c terial along a horizontal timeline showing the time of flight origination and termination, along with other relevant data. [0098] In addition, search results panel 7050 comprises one or more Option selection' icons 7054, which can enable the user to select one or more of the displayed options for inclusion in a collaborated transaction data set 501 , for consideration by the group of participants 250 participating in collaboration on the designated transaction project (e.g., "My Trip to Vegas").

[0099] Invocation of an option selection command icon (or "item") 7050 can cause the user's device 100 to generate and route to system 500 one or more command signals adapted to initiate any or all of several functions.

I00100] For example, invocation of a search command icon 7050 can cause processor(s) 507 of system 500 to send a corresponding option selection data set to the transaction collaboration data set associated 501 , as described with reference to process step 2014 above, so that the various participants' devices 100 can access the data and present it on user interface screens for consideration by participants 104, 250 for inclusion at 2028 in a collaborated transaction execution data set as described herein.

[00101] Alternatively, or in addition, invocation of a search command icon 7070 can cause processor(s) 507 of system 500 to send a corresponding option selection data set to the participant's participant data set 502, as described with reference to process steps 2016 - 2020 above, so that the various participants' devices 100 can access the data and present it on user interface screens for consideration by the corresponding participant 104, 250 for any further purposes.

[00102] In addition, invocation of a search command icon 7050 can cause processor(s) 507 of system 500 to route data representing the identity of the selecting participant 104, 250, the date and time of the selection request, criteria of the option(s) designated, and/or any other desired information to predictive analytics engine(s) 504, for storage in a predicted relevant transaction preference data set in, for example, a memory 510, and for use in further internal and external search processes and generation of data sets representing recommendations for further refinements of the proposed transaction project, different transactions, or any other desired information that may be of use or interest to the user 104, 250, and/or any other participants in the transaction project. [00103] As will be appreciated by those skilled in the relevant arts, search results panels 7050 can comprise any type(s) of data useful for aiding a participant 104, 250 to consider whether a given option should be included in the shared collaborative data set 501 for consideration by other participants. For example, in the embodiment shown in Figure 1 1 , a comparative analytics panel 7060 provides bar- graph comparisons of characteristics of various options, such as price, relatively availability, etc. for consideration by the searching participant 104, 250.

[00104] At any time during the collaborative transaction building process 2012 - 2026, any collaboration participant 104, 250 can view consolidated results of the collaborative process. For example, as shown in Figure 12, a user 104, 250 can select a current transaction command item 8002 (labelled in this case "My Trip to Vegas") to cause generation of a display 9000 showing information relating to proposed transaction options or features selected by any or all of participants 104, 250. From such a display 9000, any one or more of participants 104, 250 having binding authority can select any or all of the presented options for inclusion in a collaborated transaction data set for final review, and when ready for execution of the collaborated transaction, at 2026 can cause the final collaborated transaction results to be associated with a collaborated transaction execution instruction. Such a collaborated transaction execution instruction can be used by the system 500 to generate a collaborated transaction execution data set and route the collaborated transaction execution data set to one or more providers / fulfillment systems 301 for execution.

[00105] For example, a consolidated collaboration display 9000 can comprise one or more command icons for removing non-preferred transaction options from the transaction execution data set, and a transaction execution icon 9002. Selection of the transaction execution icon 9002 by an authorized participant 104, 250 can cause generation and routing to system 500 of a transaction execution command, which command may in turn cause system 500 to generate a collaborated transaction execution data set for routing to the one or more providers / fulfillment systems 301 for execution. The collaborated transaction execution data set may comprise any desired or required information, including for example identifiers associated with the purchaser(s) of the goods/services involved in the transaction; payment information such as funding account identifiers; routing and delivery information, etc. [00106] As mentioned above, upon receipt from system 500 of a collaborated transaction execution data set, the fulfillment / provider system(s) 301 can complete execution of the requested transaction(s), provide receipts or other confirmation, and fulfill the requested terms of the transaction by delivering products, tickets, etc. to designated recipients.

[00107] An important advantage offered by various embodiments of this aspect of the invention is the simultaneous, synchronized, or otherwise coordinated routing of collaborated transaction execution instructions to multiple provider / fulfillment systems. Such coordinated execution processes can be implemented whether multiple parts of a single purchase are to be executed through the use of single or multiple funding means.

[00108] For example, in an example in which three individuals who wish to join a single flight wish to pay for their own airfares, the invention enables the simultaneous or otherwise-synchronized routing of purchase instructions to multiple ticket providers 301 , so that the three travelers can join the same flight, sit together or separately, as desired, etc. For example, each of three such participants 104, 250 can provide payment credentials (funding account identifiers, etc,) to the system 500 for storage in their respective individual participant data sets 502. When at 2026 they have reached agreement on their flight arrangements, the system 500 can consolidate their flight information, payment information, and other desired or required information, and route it to one or more travel service providers 301.

[00109] A significant advantage afforded by this aspect of the invention is the ability to purchase from such multiple service providers simultaneously, or in other synchronized fashion. For example, if each of three different travel service providers has rights to a different one of the last three seats available on a desired flight, then simultaneous routing of execution instructions can enable the three travelers to secure reservations or tickets for the came flight.

[00110] In addition, invocation of a search command icon 9002 can cause processor(s) 507 of system 500 to route data representing the identity of the selecting participant 104, 250, the date and time of the execution request, details of the transaction to be executed, and/or any other desired information to predictive analytics engine(s) 504, for storage in a predicted relevant transaction preference data set in, for example, a memory 510, and for use in further internal and external search processes and generation of data sets representing recommendations for further refinements of the proposed transaction project, different transactions, or any other desired information that may be of use or interest to the user 104, 250, and/or any other participants in the transaction project.

[00111] As noted above, systems 500 in accordance with the invention may be implemented in a wide variety of variations. For example, request originators 104 and other collaboration participants 250 can be, represent, or otherwise include individual consumers, business consumers, and/or brokers or agents for various types of goods or services.

[00112] As a specific example, as shown in Figures 13 and 14, a travel agent or travel agency can act as originator 104, and facilitate collaboration amongst groups of travelers through the use of data sets 501 , 502, etc. Optionally, such agents can benefit from synchronized multiple third-party execution processes as described above.

[00113] While the disclosure has been provided and illustrated in connection with specific, presently-preferred embodiments, many variations and modifications may be made without departing from the spirit and scope of the invention(s) disclosed herein. The disclosure and invention(s) are therefore not to be limited to the exact components or details of methodology or construction set forth above. Except to the extent necessary or inherent in the processes themselves, no particular order to steps or stages of methods or processes described in this disclosure, including the Figures, is intended or implied. In many cases the order of process steps may be varied without changing the purpose, effect, or import of the methods described. The scope of the invention is to be defined solely by the appended claims, giving due consideration to the doctrine of equivalents and related doctrines.

Claims

CLAIMS What is claimed is:

1. A collaborative networked transaction-execution tool, comprising:

at least one electronic data processor and at least one network communication signal processor; the at least one electronic data processor configured to:

receive, from a networked communication device associated with a transaction request originator, via the at least one network communication signal processor, one or more signals representing a transaction collaboration request data set, the transaction collaboration data set comprising at least one network identifier associated with the transaction request originator and an identifier associated with each of one or more transaction request participant invitees;

using the transaction collaboration data set,

establish a stored transaction collaboration data set accessible by the transaction request originator and by each of the one or more transaction request participant invitees via a dedicated persistent network collaboration resource address;

establish a transaction request participant data set corresponding to each of the transaction request originator and each transaction request participant invitee, each transaction request participant data set accessible by its corresponding transaction request participant, via a corresponding dedicated persistent participant resource address;

generate a transaction collaboration invitation data set corresponding to each transaction request participant invitee; and using the same or another network communication signal processor, route one or more signals representing each said transaction collaboration invitation data set to a networked communication device associated with the corresponding transaction request participant invitee.

2. The collaborative networked transaction-execution tool of claim 1 , the at least one electronic data processor configured to: receive, from the same or another networked communication device associated with the transaction request originator, via the at least one network communication signal processor, one or more signals

representing a transaction originator data set pertaining to a proposed collaborative transaction project, the transaction originator data set comprising at least one identifier associated with the proposed

collaborative transaction project;

store at least some of the transaction originator data set in memory controllably associated with the stored transaction collaboration data set;

store the same or another portion of the transaction originator data set in memory controllably associated with the transaction request participant data set corresponding to the transaction request originator;

receive, from a networked communication device associated with at least a first corresponding transaction request participant invitee via the at least one network communication signal processor, a transaction participant data set pertaining to the proposed collaborative transaction project;

store at least some of the transaction participant data set in memory controllably associated with the stored transaction collaboration data set; and

store the same or another portion of the transaction originator data set in memory controllably associated with the first

corresponding transaction request participant invitee.

3. The collaborative networked transaction-execution tool of claim 2, the at least one electronic data processor configured to:

receive, from at least one networked communication device associated with at least one of the transaction request originator and at least one transaction request participant invitee, via the at least one network communication signal processor, signals representing at least one collaborated transaction execution instruction; generate, using data stored in the transaction collaboration data set and at least one of transaction originator data set and a transaction

request participant data set, at least one collaborated transaction

execution data set; and

using the at least one communication signal processor, route to at least one networked communication device associated with at least one third-party project fulfillment counterparty one or more signals

representing the at least one collaborated transaction execution data set.

4. The collaborative networked transaction-execution tool of any of claims 1 - 3, the at least one electronic data processor configured to:

route at least some of the data received the transaction request originator and the at least one transaction request participant invitee to a predictive analytics engine;

causing the predictive analytics engine to generate at least one predicted relevant transaction preference data set associable with the proposed collaborative transaction project; and

store the at least one predicted relevant transaction preference data set data set in memory controllably associated with the stored transaction collaboration data set.

5. The collaborative networked transaction-execution tool of any of claims 1 - 4, wherein some or all of the dedicated persistent network collaboration resource addresses comprise persistent uniform resource locators (PURLs).

6. The collaborative networked transaction-execution tool of any of claims 1 - 5, configured for building of travel itineraries, and purchase of corresponding tickets, services, and reservations.

7. The collaborative networked transaction-execution tool of any of claims 1 - 6, wherein at least one of the transaction request originator and the at least one transaction participant is an agent or broker acting on behalf of others.