WO2014201537A1 - Système et procédé de génération de sites internet personnalisés - Google Patents

Système et procédé de génération de sites internet personnalisés Download PDF

Info

Publication number
WO2014201537A1
WO2014201537A1 PCT/CA2013/000579 CA2013000579W WO2014201537A1 WO 2014201537 A1 WO2014201537 A1 WO 2014201537A1 CA 2013000579 W CA2013000579 W CA 2013000579W WO 2014201537 A1 WO2014201537 A1 WO 2014201537A1
Authority
WO
WIPO (PCT)
Prior art keywords
content data
purl
computer
customer
unique customer
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CA2013/000579
Other languages
English (en)
Inventor
Riaz PISANI
Paul MALCOM
Dan GRIJZENHOUT
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
CONTAC SERVICES Inc
Original Assignee
CONTAC SERVICES 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 CONTAC SERVICES Inc filed Critical CONTAC SERVICES Inc
Priority to PCT/CA2013/000579 priority Critical patent/WO2014201537A1/fr
Publication of WO2014201537A1 publication Critical patent/WO2014201537A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0201—Market modelling; Market analysis; Collecting market data
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0241—Advertisements
    • G06Q30/0251—Targeted advertisements
    • G06Q30/0255—Targeted advertisements based on user history
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • H04L67/5681—Pre-fetching or pre-delivering data based on network characteristics

Definitions

  • the present disclosure relates generally to a system and method for generating personalized websites.
  • companies with an online presence may make attempts to directly market to Customers by collecting information about a Customer's preferences, and providing suggestions for related goods or services that correlate to the user's preferences. For example, some online retailers will make suggestions for related goods or services as a Customer browses an item on a website, based on what the Customer has purchased before or based on what other Customers have purchased after browsing the same item online.
  • the present disclosure relates to a system and method for generating a personalized uniform resource locator (PURL) for a Customer that is regularly updated.
  • PURL uniform resource locator
  • the PURL is regularly updated over an extended period of time for the life- cycle of products or services delivered to a Customer.
  • a computer-implemented method for generating a personalized universal resource locator (PURL") for a customer comprising: identifying a unique customer; collecting content data from a plurality of data sources; pre-caching the content data for access by the unique customer; and generating a PURL with one or more links to the pre-cached content data prepared for access by the unique customer.
  • PURL personalized universal resource locator
  • the computer-implemented method further comprises collecting the content data in one or more landing databases.
  • pre-caching the content data comprises preparing the content data in one or more staging databases prior to access by the unique customer.
  • pre-caching the content data further comprises preparing the content data based on the unique customer's profile.
  • the computer-implemented method further comprises retrieving the pre-cached content data from the one or more staging databases in dependence upon interaction by the unique customer with the one or more links to the pre-cached content data in the PURL.
  • a computer-implemented system for generating a personalized universal resource locator (PURL") for a customer the system adapted to: identify a unique customer; collect content data from a plurality of data sources; pre- cache the content data for access by the unique customer; and generate a PURL with one or more links to the pre-cached content data prepared for access by the unique customer.
  • PURL personalized universal resource locator
  • system is further adapted to collect the content data in one or more landing databases.
  • system is further adapted to pre-cache the content data by preparing the content data in one or more staging databases prior to access by the unique customer.
  • system is further adapted to pre-cache the content data by preparing the content data based on the unique customer's profile.
  • FIG. 1 shows a schematic block diagram of a system architecture in accordance with an embodiment.
  • FIG. 2 shows a schematic block diagram of a generic computer device in accordance with an embodiment.
  • FIG. 3 shows a schematic block diagram of a macro level depiction of the system from a Customer facing perspective.
  • FIG. 4 shows a schematic block diagram of an architecture for rendering personalized URLs to a Customer website.
  • FIG. 5 shows a schematic block diagram of a PURL skin architecture in accordance with an embodiment.
  • FIG. 6 shows a schematic flow chart of a PURL generation system flow in accordance with an embodiment.
  • FIG. 7 shows a schematic block diagram of a "services bus” architecture in accordance with an embodiment.
  • FIG. 8 shows a schematic flow chart of a booking e-mail system flow in accordance with an embodiment.
  • FIG. 9 shows a schematic flow diagram that illustrates a content data rendering system and method in accordance with an embodiment.
  • FIG. 10 shows a schematic flow diagram that illustrates a content data normalizer and learning engine in accordance with an embodiment.
  • FIG. 11 shows a schematic flow diagram that illustrates how third party content is gathered and rendered to a Customer PURL with an embodiment.
  • FIG. 12 shows a schematic flow diagram of an illustrative airline booking process for a travel excursion life-cycle in accordance with an embodiment.
  • the present disclosure relates to a system and method for generating a personalized website or URL ("PURL") for a Customer, and more particularly to a PURL that is regularly updated over the life-cycle of a product or service.
  • PURL personalized website or URL
  • the “Client” refers to the client of a system vendor providing the present system and method.
  • the “Customer” or Customers” refers to their buyers or end users of the Client's services. It will of course be appreciated that in an alternative embodiment the Client may itself be the system vendor.
  • a system and method for generating personalized websites that are highly customized for a particular identified Customer based on a Customer profile.
  • This is made possible by a system architecture which significantly reduces direct end user load upon a core database system, and instead utilizes a series of Landing or Staging databases or Data Marts that are separate from the core system.
  • Landing or Staging databases are used to pre-stage a PURL for a Customer and can be dispersed across different clustered servers to be able to harness more power to serve up data and web pages to many more concurrent users without appreciable performance degradation.
  • the system and method effectively separates components of the database by function point so as to reduce the I/O footprint to the core database system itself - reducing direct end user loads upon it.
  • the system and method collects most third party data to be served up locally from local servers, as opposed to having to serve up this data remotely from third parties directly to the user while they are in an on-line session. This may drastically reduce screen rendering time to a few seconds to display third party data on personalized websites.
  • FIG. 1 shows a generic computer device 100 that may include a central processing unit (“CPU") 102 connected to a storage unit 104 and to a random access memory 106.
  • the CPU 102 may process an operating system 101 , application program 103, and data 123.
  • the operating system 101, application program 103, and data 123 may be stored in storage unit 104 and loaded into memory 106, as may be required.
  • Computer device 100 may further include a graphics processing unit (GPU) 122 which is operatively connected to CPU 102 and to memory 106 to offload intensive image processing calculations from CPU 102 and run these calculations in parallel with CPU 102.
  • An operator 107 may interact with the computer device 00 using a video display 208 connected by a video interface 105, and various input/output devices such as a keyboard 110, mouse 12, and disk drive or solid state drive 114 connected by an I/O interface 109.
  • the mouse 112 may be configured to control movement of a cursor in the video display 108, and to operate various graphical user interface (GUI) controls appearing in the video display 108 with a mouse button.
  • GUI graphical user interface
  • the disk drive or solid state drive 114 may be configured to accept computer readable media 116.
  • the computer device 100 may form part of a network via a network interface 111 , allowing the computer device 100 to communicate with other suitably configured data processing systems (not shown).
  • One or more different types of sensors may be used to
  • the present system and method may be practiced on virtually any manner of computer device including a desktop computer, laptop computer, tablet computer or wireless handheld.
  • the present system and method may also be implemented as a computer- readable/useable medium that includes computer program code to enable a computer device to implement each of the various process steps in a method in accordance with the present invention.
  • computer-readable medium or computer useable medium comprises one or more of any type of physical embodiment of the program code.
  • the computer-readable/useable medium can comprise program code embodied on one or more portable storage articles of manufacture (e.g. an optical disc, a magnetic disk, a tape, etc.), on one or more data storage portioned of a computing device, such as memory associated with a computer and/or a storage system.
  • FIG. 2 shown is a schematic block diagram of a system architecture 200 in accordance with an embodiment.
  • the overall operational system 200 contains a number of inter-relating Abstraction Layers that cohesively and seamlessly communicate with each other to deliver the desired functionality at the desired levels of performance and scalability.
  • these layers can be categorized as follows: (i) Integrated Systems Architecture; (ii) Application Architecture; (iii) Enterprise Data Environment; and (iv) Enterprise Computing Environment.
  • Key components of this logical architecture include a "Client Configuration" Module which creates Client profile settings in a Client configuration database. Settings in this profile create the rules for accessing third party data stores for that Client, its sales agents and its Customers.
  • processing rules for all queries are stored as callable stored procedures in the system's Rules Engine.
  • the system may further include a Configuration/Setup module which Clients will be accessing to perform various functions.
  • the system includes a "WEB API" to receive booking information in the formats preferred by the system.
  • custom retrieval and initial processing may be designed and coded into a custom front-end retrieval process.
  • Personalized URL or PURL screen activity also triggers system activities, and the Rules Engine is a repository of common "Stored Procedures" with backend database interfaces and "Processing rules" that are triggered as PURL events occur.
  • the Content Server manages the final selection and rendering of information to a PURL when an end user event is triggered.
  • One important function of the Content Server is in its relationship with Booking Notifications.
  • the system When the system receives a Booking Notification from a Client, the system will send out a marketing e-mail to the end user Customer. The Customer receiving the e-mail then has the opportunity to click on a link that will take him to a custom generated PURL specific to him/her.
  • the Content Server will generate the custom PURL and will render the appropriate content to the created PURL. This related content to the Home PURL page will be "fetched" from internal databases.
  • the Content Server also manages the retrievals, sorting, selecting and rendering of content back to the PURL screens on user initiated queries.
  • the mail server manages the distribution and tracking of all e-mails sent out by the system to Customers of the system. Beyond standard distribution capabilities as found in COTS (Common Off The Shelf Systems), this server processes outbound marketing messages created by the system. It also tracks message "Opens" for reporting purposes and further contact with Customer sales messages that can be sent out.
  • COTS Common Off The Shelf Systems
  • This server processes outbound marketing messages created by the system. It also tracks message "Opens" for reporting purposes and further contact with Customer sales messages that can be sent out.
  • One solution deployable by the system is discussed in more detail further below.
  • the system is a multi-language system at the PURL level. Initial deployment incorporates language translation capabilities for all deployed web pages using available tools (e.g. Google Translate) but the underlying Architecture Database has been designed for multi-language deployment which can be turned on at any time as desired. This database supports the changing of text at the PURL levels - both for Customers and for sales agents. At the PURL Level, an end user can thus change the language, and the web page will re
  • the system module takes revenues earned from Customers via both internal and external shopping carts and, based on revenue sharing rules built with Clients (see Client Configuration Module), allocates commissions to all revenue sharing parties.
  • This system "renders" in a reporting fashion, revenue share information to sales agent dashboards, Client Activity web page and an internal reporting web page so all parties can view sales results and their share of revenues.
  • this also interfaces with the "Account Reconciliation" module to reconcile when purchases are modified - such as when there are hotel cancellations, or stays are shorter than originally booked/paid for, etc.
  • This revenue splitting feature also directly ties the Agent to an integrated, third party payment service capability which they can use at their request within the system to trigger physical payouts to themselves globally.
  • the platform includes an internal Shopping Cart interfaced with a payment mechanism and setup to also interface with a payment authorization system, such as Authorize.net, as needed for merchant account processing.
  • a service provider can process financial transactions for third party purchases and can even push financial transactions, hotel booking confirmations and third party shopping cart purchase to external business partners where business rules warrant it.
  • This shopping cart is able to obtain Client purchase information that is then analyzed for "gross profit margin" amounts so that these amounts can be distributed among the stakeholders when revenue sharing procedures built into the system take place.
  • the system defines certain business rules for business events.
  • An example is - who does a Customer belong to if he is using the PURL system if several Clients send him PURL triggering "bookings" resulting in e-mails being sent to him?
  • the Customer becomes the Customer of the Client from whom he receives an e-mail which he opens and initiates a transaction.
  • the User Directory registers the different classes of users of the system and assigns/documents their access permissions. Users are attached to Clients and sales agents within this system, depending on if they are Customers or sales agents themselves. Note: Customers can belong to both sales agents and Clients - and sales agents can belong to Agencies, Customers and Clients.
  • the "meta data” environment is now managed and controlled by a data modeler, such as the "CA ERwin Data Modeler” provided by Computer Associates.
  • a data modeler such as the "CA ERwin Data Modeler” provided by Computer Associates.
  • ERwin used as a "Meta Data” repository within the architecture, allows techni ' ca) staff members to quickly understand how the system works at a database level, and it provides "Point of Truth" information on all database elements and attributes, provides important VARCHAR, key and foreign key knowledge to the developer, is a repository for all "Stored Procedure” code used within the system, and provides database management services and "change control" support to developers working with the system.
  • these databases represent for the most part "Landing Databases/Data Marts" resident on internal servers to initially receive third party content prior to this content being made available to Customers and other users of the platform. These databases do not attempt to change any information/data received from third parties. Rather, they “pull” this data from the third parties and then store it in the same definitions as provided from the third parties. "Data Transformation” then occurs as this landed data is passed across to the "Staging Databases/Data Marts discussed in the Internal Database section below.
  • the system is designed to be a sophisticated marketing engine whose core characteristics include: (i) Importation of Booking Records; (ii) Bulk E-mail and SMS/IM Marketing system capable of high-volume delivery; (iii) A web experience facility that is "Personalized" for each Customer; (iv) A sophisticated “Content Rendering” workflow system tied in to multiple third party content providers; (v) “Target Marketing” capabilities based on “Profiling” algorithms built into the system for each Customer; (vi) A subscription/membership signup system built for "Sales Agencies", “Sales Agents” and repeat “Customers”; and (vii) A purchasing and shopping cart system usable globally.
  • FIG. 1 A sophisticated marketing engine whose core characteristics include: (i) Importation of Booking Records; (ii) Bulk E-mail and SMS/IM Marketing system capable of high-volume delivery; (iii) A web experience facility that is "Personalized" for each Customer; (iv) A sophisticated “Content Rendering” workflow system tied in to multiple third party content providers; (
  • FIG. 3 shown is a macro level depiction of this system from a "Customer" facing perspective.
  • delivery of content requires process, architecture, presentation and management services in addition to availability of the content.
  • the core Client Facing systems components of the system are primarily delivered by the Internet.
  • several architectural strategies have been employed by the inventors, including some of the following:
  • Web pages should load quickly, so they need to be built thin. That is, content rendering logic would not be contained within the web page as this slows down the page loading process. Rather, the strategy is to decouple this programmed logic so it is only called via a "web service" when specifically requested by a Customer or when an internal rule requires it.
  • third party data will be stored and rendered from internal data servers as opposed to live third party interfaces - this to save web page loading and content rendering speeds - to improve the Customer experience and to as a result, increase sales conversions.
  • Web page development strategies must employ the latest strategies in technical innovations. This strategy is important to improve greater Openness" to wider ranges of user computer configurations, to improve rendering speeds, and also to improve longevity of the system code and designs.
  • the system may utilize web development technologies such as Windows Communication Foundation (WCF), and others, to significantly reduce lines of code per screen.
  • WCF Windows Communication Foundation
  • the lines of code may be reduced to about a quarter of the lines of code of web pages using previous technology.
  • the framework shown in FIG. 4 is physically instantiated into the design through some further architectural design strategies that have been employed.
  • the system separates the "Design Skins" used for each "Client” and even “Agencies" from the web rendered content and associated programming logic so as to be able to setup individual "Skins'VCSS folders by business entity thus allowing ease of customization and reuse of "Skin” designs.
  • it is only necessary to change each instance of a "Skin - Type", which greatly reduces the amount of work required to make changes to a website design.
  • the "Web Server” farm (see physical topology documentation) will manage the skins and the rendering of the PURLs and their related content to "Cache" memory.
  • EAE Enterprise Data Environment
  • the key to the target data architecture is the definition and implementation of an integrated enterprise wide database. It provides a common data architecture for all business functions reducing data redundancy, promoting shared data, and eliminating inconsistencies.
  • This common data architecture with the appropriate data management technologies facilitates the integration of data from multiple sources, guarantees consistency of data, maintains end-user transparency, supports a flexible transaction framework, is extensible and dynamic, and supports standards-based APIs.
  • FIG. 5 shown is a schematic block diagram of a Customer PURL skin architecture in accordance with an embodiment.
  • a key to the target data architecture is the definition and implementation of an integrated enterprise wide database. It will provide a common data architecture for all business functions reducing data redundancy, promoting shared data, and eliminating inconsistencies.
  • This common data architecture with the appropriate data management technologies facilitates the integration of data from multiple sources, guarantees consistency of data, maintains end-user transparency, supports a flexible transaction framework, is extensible and dynamic, and supports standards-based APIs.
  • program logic in the system has been decoupled as far as possible from core system driving business objects/attributes.
  • attributes instead of attributes being instantiated in code, the system calls key attribute values from database tables instead - allowing for much greater flexibility and extensibility in operational implementation. This has allowed the inventors to construct very sophisticated, parameter driven "Rules Engines" within the design of the new system. Shown in example below are just a few of the key attributes to this new system that are now supporting the new "Parameter Driven Design”.
  • the entire EDE environment setup for the system is geared towards managing the delivery of content in relation to Client, Agent and Customer generated “Events”.
  • Clients "push” booking record “events” to the system - which as a result of the event, sends out related marketing messages to Customers.
  • Customers trigger "PURL Generation” events by responding to messages sent to them. Once initial PURL's are requested by a Customer, they then request additional "Content” which the servers and systems provide to them in such a manner that the Customer is enabled and hopefully interested to generate a product or service Transaction" which the system then manages for them, supported by the EDE.
  • the databases are modularized - designed by function point so the system can be easily modified and new or additional functionality to the system can be easily implemented.
  • the scope of the Enterprise Computing Environment is to provide a suite of common services and consistent access to those services across all components of the enterprise.
  • the intent of the ECE is to make these enterprise services available to authorized users and processes within the context of a single systems image.
  • the ECE environment provides these enterprise available services through a series of "technology layers" and is comprised of-
  • NSM Network and Systems Management
  • a multi-tiered architecture model (both physical and logical) has been designed to provide location transparency of data and processing resources. This approach allows for differing degrees of centralization and decentralization of processing and information based upon efficiency and effectiveness considerations.
  • This framework utilizing standard API's provides benefits from advances in technology, rapidly adapt to a changing enterprise and evolving operations concept, and support a variety of deployed configurations.
  • a common enterprise information model will support different but logically integrated views for each level of operations: Global, Regional and Local. Support for higher level views is provided through replication, summarization, or transformation of certain data, while other data is accessible transparently from source levels as necessary or upon demand.
  • the system is adapted to send out e-mail messages to prospective Customers, and monitor the success of messages sent while simultaneously collating user usage statistics.
  • Sender Policy Framework SPF
  • This framework has operationally been instantiated and configured in our third party purchased and deployed message management system.
  • the system therefore implements individual interfacing and downloading strategies with each third party provider. Downloading data can be time consuming - and once it has been downloaded, it needs to be "Transformed" before it can be served up to Customers from within the system. Core strategies employed to get this data to where it is usable from within the system include the following mechanisms:
  • a separate server from the production server(s) is employed to initially capture third party data.
  • Data is initially downloaded in "Native" formats as defined by the third parties so as to minimize the downloading times from the third parties.
  • Each third party's data is stored initially in a "Landing Database” designed specifically for their data.
  • the Landing Database is "Mapped" to the new data definitions required for use in the production system and data transformation rules are instantiated into event triggered stored procedures setup in the Landing data base so that new or changed/updated records that appear in the Landing Database are automatically transformed and loaded across to the Staging Database.
  • Scheduled programs/routines run against the Staging Database to load changed (including notified deletions) or new records only across to the production database in "Batch" uploads.
  • the timing of each of these upload interface programs run using a system “Scheduler” according to business rules/requirements that have been defined for each third party.
  • a separate server from the production server(s) is employed to initially capture native booking record data so as to minimize the downloading times from Clients.
  • Each Client's data is stored initially in a "Landing Database" designed specifically for their data.
  • the Landing Database is "Mapped" to the new data definitions required for use in the production system and data transformation rules are instantiated into event triggered stored procedures setup in the Landing data base so that new or changed/updated records that appear in the Landing Database are automatically transformed and loaded across to the Staging Database.
  • Scheduled programs/routines run against the Staging Database to load changed (including notified deletions) or new records only across to the production database in "Batch" uploads.
  • the timing of each of these upload interface programs run using a system “Scheduler” according to business rules that have been defined for Booking Records.
  • the "Booking Marketing" E-mail may be initiated that goes out to Agents and Customers letting them know that a Customer PURL site has been created. Templates for these e-mails are constructed and stored in our Lyris message management system whereas the business rules relating to the use of these templates and mail outs are stored within the Staging Database as stored procedures. Please be aware that this strategy has been designed so as to minimize performance impacts against the primary Architecture Database - which processes and manages all Customer PURL requests and purchases. The system may send out 1 million PURL e-mails from this Staging database and by utilizing this strategy, all these PURL's do not have to be individually loaded to the primary Architecture Database - which saves considerable I/O against that DB.
  • FIG. 6 shown is an illustrative schematic flow diagram of an architectural system flow for PURL generation.
  • the second method is to receive a booking notification via an XML message and then go back to their system to get the full booking record.
  • the third is to have a full booking record sent via the new Web Service/Booking Record Receipt API that asks the "Clients" to use when sending booking records to us. This will be the preferred method of receiving booking records moving forward.
  • the PURL Generation process is triggered when Proc02 inserts a booking record or a batch of booking records (it can do both) into the Architecture Database.
  • the mapping of data from the Staging Database to what is inserted into Arch DB should be the same as all data transformation takes place in the prior processes of loading data to the Staging Database from Client data.
  • FIG. 6 shown is a schematic system flow diagram of a PURL generation system flow.
  • Booking Records are imported to the Architecture Database and remain there ready for use until such time as a Customer clicks on a PURL link received via e-mail through the Create Booking Marketing E-mail process.
  • content rendering activities There are two types of content rendering activities that take place once this link is triggered:
  • Subsequent PURL Generation This is a Customer triggered event where a Customer selects a secondary screen from which he/she can make purchase decisions or get more information. Some screen selections lead to additional direct viewable content (text and images directly rendered from the Architectural Data Base. Some screens pass the Customer directly to a third party website, passing certain parameters with the query to the new site so that financial interests are protected and so that searches can be completed using the "Data parameters" passed; and finally, some events bring the Customer to a "Search Screen" wherein they can enter search parameters so a search can be completed relating to third party data stores managed by Vendor internally.
  • the second requirement is that, on rendering the first PURL, some Clients desire that hotels and/or car rentals, etc. be rendered on the first PURL even though the Customer may have already purchased these from the Client prior to the Customer using the system - and other Clients do not wish to render these items in the first PURL in such a situation.
  • the program checks the PURL_Parameter field in the Primary_Client_PURL_Parameters table to see if this attribute has an attribute value of "PURL_Refresh". If it does, then the program knows that the program needs to access the Client booking system to "Refresh" the booking record details for this PID/event prior to rendering the first PURL.
  • the XX represents a numeric value that denotes the time "Delta" between when the booking record was first created in the system and when the system will require booking record refreshment based on when the Customer is accessing the initial PURL via the link he/she received in the Booking Notification/Marketing E-mail. Only one of these records will be resident in the table below - on setup the record that best fits a particular Client's defined rule will be implemented. For example, if the requirement is that if the Customer is accessing the initial PURL via the link within 5 minutes of initial record creation then no refreshment is necessary, then the record in this table will read Min05. If the requirement is no refreshment within an hour, it would read HourOI . If the requirement is no refreshment within an hour and a half, then the record would read Min90 - etc.
  • the PURL Rendering "Parameter" capability is included as part of Proc04 illustrated in FIG. 7.
  • some Clients desire that hotels and/or car rentals, etc. be rendered on the first PURL even though the Customer may have already purchased these from the Client prior to the Customer using the system - and other Clients do not wish to render these items in the first PURL in such a situation.
  • Proc04 on being passed the initial parameter "Client_No", and the system checks for that Client in the Primary_Client_PURL_Parameters table for attribute "PURL_Parameter” and value "Always_Show". If this value is found, then Proc 04 includes a rendering of hotels and car rentals when rendering the initial PURL even though a hotel and/or car rental has already been booked by the Customer through the Booking Record. If this "Always_Show" value does not appear here for this Client, then it does not render a selection of hotels/and or car rentals on the initial PURL if they have already been purchased through the booking record.
  • Proc04 passes this callout request on to ProcO - Request Hotel or Car Content after first getting all required Client Configuration and Preferences parameters so they can be utilized in ProcO to search for, select, sort and render content to the web page.
  • FIG. 8 shown is a schematic system flow diagram of a booking e-mail notification design flow.
  • Method one is to first "parse” either the body of an e-mail (current method employed with Travelport), or the subject line of an e-mail and then go back to these Clients to pull down a complete booking record.
  • the second method is to receive a booking notification via an XML message and then go back to their system to get the full booking record.
  • the third method is to have a full booking record sent via the internally constructed Web Service/Booking Record Receipt API. This is our preferred method of receiving complete booking records from our clients. Important design principles contained within this interface include the following:
  • Client_No attributes are set up in the Arch. DB as the system sets up new Clients and that as each new Client is added to use this system, the program that inserts new booking records into the Staging Database must be updated/kept in alignment with each new Client set up in the Arch DB system. For example, if a new Client is entered as Client_No "6", then all booking records received from that Client and inserted into the Staging DB must be assigned to Client_No "6" in order for the system to work properly.
  • GUID Global Unique Identifier
  • the Staging DB contains database triggered programming logic contained within it that generates e-mail requests which are sent to the message management system to be merged with e-mail templates resident there for the purpose of sending out the appropriate PURL link e-mail message to the Customer.
  • the Client_Nodata attribute registered on the insertion of the booking record into the staging database defines which template is to be used for the e-mail being sent out to the Customer.
  • the Client checks the "Select_To_Do settings for both PURL_Event_No attributes 1 and 2 to see if e-mails are to be sent out to both the agent and the Customer or to the Agent only - so they can forward it to the Customer later using the TAD feature for this purpose.
  • the template is first grabbed by the procedure, and then is populated with the "personalized” content contained in the booking record and then sent it off to the messaging system to generate the required e-mail.
  • a "Client Profile" table in the Staging Database is kept and maintained. Information that is needed to create a booking marketing e-mail from the Staging DB are listed below.
  • a stored procedure in the Architecture DB passes information across to the Staging DB for instances when Client information is updated within that system. This procedure captures and inserts to the Staging DB the following data attributes relating to a Client when new records are created or values are updated.
  • the booking record plus related PID plus related GUID are also passed to the Architecture DB through another procedure.
  • the mapping of data from the Staging Database to what is inserted into Arch DB is the same as all data transformation takes place in the prior processes of loading data to the Staging Database from Client data stores as per booking record designs.
  • This is a timed server resident procedure that reads the Staging Database for new records and then inserts them into the Architecture Database. Timing for the procedure to be run is set externally by the server's "Scheduling" system.
  • the interface is designed to create “batches” of new records and it imports all new records at one time/by batch to the Architecture Database. So an indicator of last "Date/Timestamp” is kept in a log and records captured there ensure subsequent running(s) of the program only capture new records inserted into the Staging Database.
  • This procedure is written in such a way that it can be set by a programmer to run against a single, defined Client or for several at a time, or for all Clients at one time.
  • the present system and method delivers a personalized, consumer targeted website containing real time and near-real time gathered, sorted and rendered content delivered from both internal databases and external third party content suppliers.
  • the presentation layer of the system built on the newest of technologies, programming languages and databases, is dynamically rendered to the user in "Cache" Memory to speed up page rendering to the consumer.
  • each page rendered is custom "skinned" to reflect the business entity or entities that offer the services. For example, in the Travel Industry, skins reflect the airline and/or the agency relating to the initial consumer purchase.
  • the database layer of the architecture is very complex and utilizes a series of "Landing” and “Staging” databases that continually receive, process and transform "disparate" content data from external content providers so that this data can be imported to the core processing system to be rendered to consumers as freshly and as accurately as it is possible to render it.
  • internally derived data is often coupled with real-time imported and delivered external data (within a user session) and delivered to the consumer rapidly enough so that the user experience is not appreciably compromised.
  • the infrastructure providing these end user services makes use of a number of deployment strategies geared also to supporting the maximization of rendering speeds to the consumer, and its deployment design ensures that user entered data is kept safe and that systems are quickly recovered and again usable to a consumer should some form of system failure occur.
  • FIG. 9 shows a schematic flow diagram that illustrates a content data rendering system and method in accordance with an embodiment.
  • Content when rendered to the consumer needs to be accurate and timely.
  • a Travel Industry Client showing a hotel with availability at a certain price in real-time involves a number of steps.
  • the system and method needs to match this disparately received data from different source points prior to rendering to the web page, otherwise, the same hotel might appear several times on the same screen for the user.
  • the system and method utilizes a filtering module to match data from disparate source points to ensure only one purchase option for a particular hotel is rendered to the user viewable web page. The system and method thus gathers, sorts and selects data prior to rendering including.
  • the system and method executes one or more of (i) name splitting to improve searches for content (various content attributes searched), (ii) parsing algorithms strategies, and (iii) absolute and partial match calculation routines including Soundex matching for indexing names by phonetic sound.
  • the system and method utilizes an internal Learning Engine that utilizes context to determine what type of data is most appropriate to render. For example, if a tickets purchase indicates that a traveler is travelling with a family, the system and method renders family oriented activities rather than adult oriented hotels, shows, activities, etc. If the traveler purchased a first class airfare, then the system renders 4 and 5 star hotels rather than 2 and 3 star hotels, etc.
  • the Learning Engine uses one or more of "Weighted Averaging", Aggregate Match Scoring, Lookup Matching and other "Fuzzy logic" approaches to filter and then render appropriate content to the targeted user.
  • FIG. 10 shown is a schematic flow diagram that illustrates a Content Data Normalizer and a Learning Engine in accordance with an embodiment.
  • the system and method should obtain and process third party data to web pages fast enough such that end user Customers are not frustrated waiting for the web page to appear with the appropriate, targeted content inserted. Interfacing to this data directly from code written in web pages, as is done on most websites generally does not work as the complexities introduced to the rendering rules and fWtenng logic cause speeds to slow.
  • the present system and method renders web pages to many concurrent users by rendering content from internal databases to cached web pages, rather than physically storing web server resident web pages.
  • system and method utilizes internal systems logic (Content Data Normalizer, Learning Engine, Rules Engine, etc.), then stages, sorts and matches data at different points in the rendering process and at various levels of data abstraction to render "timely" selected data quickly.
  • internal systems logic Content Data Normalizer, Learning Engine, Rules Engine, etc.
  • Some data may be pre-staged into new caches, inheriting the related business rules of the obtained data without corrupting (i.e. forgetting/changing) any element of the original rules.
  • the system then flattens the cache and work with only one set of combined rules to deal with at only one Abstraction Layer level - this all done to help minimize negative performance impacts.
  • Showtime tickets require a composite match-up of pre-staged and rendered content to content obtained during the user session through a real-time interface.
  • Some of this real-time data is downloaded and cached within the session prior to an user requesting it, and some of the real-time data is rendered as a result of a query or transactional process initiated by the end user.
  • the following data access layers may be involved in a system event: Data Access Layer (DAL) 1 : Nightly download of events, locations, times, standard pricing, etc.
  • DAL Data Access Layer
  • Data Access Layer (DAL) 2 Real time query to Show Time within the user session to get and book available seats and up to the minute pricing involves several sequential interactive queries to Showtime Tickets:
  • Event Listing (eg., Artist)
  • the present system and method significantly flattens the process by retrieving and pre-caching beforehand a significant amount of data in the hopes of minimizing the communications between Abstraction Layers on user request. By having a significant amount of data flattened, the rendering times may be greatly reduced.
  • the system can learn things about the traveller, including Airline, destination, age, family, etc. Using this information, the system can query a local content database and the third party content database to get content in advance of the end user Customer accessing the site.
  • pre-caching the data and having it ready to transmit may greatly increase the speed with which a Customer query may be rendered when he/she logs on or enters a query at the site.
  • FIG. 11 shown is a schematic flow diagram that illustrates how third party content is gathered and rendered to a Customer PURL with an embodiment.
  • the system knows the following, as certain parameters have been passed along with the screen request: (i) The Client Profile (in the case of a PURL generation request); (ii) The Customer and his/her/their trip details (in the case of a PURL generation request); (iii) The booking details define which third party "Types" are to be included and the Client Profile tells us which third parties to use along with their "Priority" settings as related to that Client; and the agent involved when a B2B event exists. These parameters define what third party data will be selected and rendered to the screen within the PURL generation procedure.
  • the definitions/rules within the system and method further include how many records of each third party type are to be rendered to the screen, and preference rules relating to third party data selection.
  • the process flow for this event may be as follows:
  • an internal shopping cart procedure Upon selection by the Customer of an item to purchase, an internal shopping cart procedure then manages the remaining purchasing steps.
  • system and method may be configured to render initial queries for third party data from within the system where possible. This requires that third party data will be loaded and refreshed to the system database regularly - preferably during non-peak hours.
  • a parameter driven server resident program manages all data retrievals for third party data - except for when a shopping cart purchase is being made.
  • the system allows a travel agent to manually request and create for a currently non-travelling Customer, a "Planning PURL" - which is to say a created PURL site for the Customer to visit without the Customer having to book a flight first.
  • This PURL will appear on the Agent's screen and he/she can then forward the access link for the PURL to the Customer via e-mail.
  • the Customer On receipt of this e-mail, the Customer will be able to click on a "linked URL" button that will take the Customer to his or her created PURL website. Once there, the Customer may choose to use a "Forward to a Friend" feature that sends an invitation to a friend to come and view the Customer's PURL site. In this way, Customers may review a possible travel excursion before purchasing, or multiple Customers can review and plan a travel excursion together based on a PURL created for one Customer.
  • the platform is a complete "end to end" enhanced itinerary system that provides travel agencies with a suite of next generation communication and 1 :1 marketing tools to enhance their traveler experience and drive incremental revenues.
  • the platform dynamically creates a highly personalized website (PURL) as previously described, based on any number of available variables from their profile, itinerary or destination. Additionally, the platform provides the ability to access/edit their Universal Profile and manages the traveler's itinerary before, during and after travel.
  • the platform customizes and personalizes each traveler website including the design, branding, messaging, graphics, e-commerce vendors, content, destination information and merchandising.
  • Planning Travel The platform provides travel agencies with the industry's first interactive and digital planning sales tool.
  • the purpose of the Planning PURL is to enable travel agents to professionally present travel options and improve their close ratios.
  • the platform offers the ability to present itinerary options, selected through Client business events, to their Customers via a personal website.
  • Each "Planning PURL" will couple the detailed itinerary options with customized destination content (e.g. destination information, excursions, merchandise etc.) to build excitement and engagement.
  • the agency can select a call to action or the ability to book directly from the platform under their credentials.
  • the traveler will receive a completed enhanced itinerary.
  • the PURL acts as the traveler's final travel documentation and includes the Customer's comprehensive itinerary, accounting, e-ticket and expense data. All other content is now customized to this itinerary/ destination and the e-commerce and merchandising vendors are triggered and embedded in the PURL.
  • Several other features are also activated including a "Communication Corner" to enable direct notifications of schedule change, alerts or other travel information and the mobile version is available for access via any smartphone.
  • the mobile application enables in destination purchases and communication via the same platform.
  • the platform automatically manages the "after travel” experience with a "Welcome Home” site timed for guest return. This provides the travel agent an enhanced Customer service opportunity to survey the guest, enrol them in a loyalty program and most importantly to generate the next Customer inquiry/booking. Again all content, advertising and messaging is customized to this phase of the trip and offers the Customer the opportunity to upload photos and share with friends and family via their social media network.
  • Each enhanced itinerary is both emailed to the travel agent and/or traveler and deposited to the travel agent's wallet within the TAD dashboard.
  • This dashboard can be embedded into the Client platform and provides the agent with the full status of itineraries, send final PURLs, track Customer open rates and view commission statements.
  • the dashboard also provides administrative access to travel agency owners for the management of any configurable components of the Customer email and itinerary platform as determined by the Agency or Client.
  • the 1 :1 marketing capabilities of the platform offer travel agencies and their Customers one or more of the following advantages:
  • the platform provides airlines with a suite of next generation itinerary, merchandising and 1:1 marketing tools to enhance the Customer experience and drive incremental ancillary revenues throughout the travel journey.
  • the itinerary is a sophisticated and dynamic web platform providing Airlines traveller's with a customized website for each trip.
  • An itinerary can be initiated by passing information electronically via API or any other system.
  • Each itinerary provides Airlines the ability to personalize and customize the design, messaging, graphics, content, offers and information by the business rules chosen
  • Ability to dynamically customize each site based on Enrich Frequent Flyer Status or any other Customer segment variable Airlines can self-configure and control the branding, user interface and design elements through simple configurability tool available in the TAD dashboard
  • the wallet acts as a single repository for all Customer bookings with Airlines and can feed valuable information to the Client's CRM platform
  • an itinerary never expires and can be updated several times throughout the journey... before, during and after travel Full destination information via Lonely Planet or Guiomatic including videos Calendar integration with Outlook, i-cal etc. Flight status and tracking Enhanced hotel images, text and video
  • the Communication Corner allows Airlines to stay in constant communication with the traveller for schedule changes, alerts, notifications etc. 60% of those canvassed define the user experience as very appealing with information easy to find and purchase
  • the platform provides an enhanced tool to drive new incremental revenues... Airline seats, bags, meals, mileage etc. Hotels, Cars, Insurance, Rail, excursions, events, ski, golf, limo etc. and guides Dynamic messaging can be automatically delivered at predefined intervals to drive purchasing behaviour: 48 hours prior upgrade to business class Hotel / car booking reminders In destination activates and excursions Check in 24 hours prior to departure. Customer Retention
  • a welcome home site is automatically generated and timed for guest return.
  • an automated email from travel consultant may provide the opportunity for feedback via a Customer survey and promote the next purchase with repeat guest promotions.
  • the itinerary is mobile enabled for the following: Blackberry, i-Phone, Android Tablet Bookable Mobile Content Insurance Hotels Car, Limos, Transfers Shows, Sporting Events, Concerts Excursions Ability to drive pre-trip and in-destination messaging: Upgrade to business class prior to departure Limousine transfers Destination excursions Traveler services Check in online Flight Status Destination content and weather Share a PURL with friends and family via any social media site.
  • the communication platform will automatically deliver a number of rules based consumer communications...
  • Email with the itinerary to the Customer can be co-branded if booked by a travel agency.
  • Timed emails (7, 14, 21 days prior to departure) promoting the purchase of intelligent merchandising including insurance, hotel, car, limo, excursions, shows, concerts etc.
  • the advertising platform is adapted to significantly improve targeted advertising in order to increase revenue generation.
  • An advertising capability is built into the system and advertising space on web pages is being sold to approved advertisers.
  • the system generates a significant number of statistical reports, metrics and key performance indicators including but not limited to the following:
  • Metrics such as CTR per content provider & ad impressions.
  • Demographics age, income, gender, ethnicity, education level, etc.
  • an e-mail is created and automatically sent out by the system to invite the Friend to create their own Planning PURL with a link provided in the e-mail to do so.
  • the originating Travel Agent for the Customer is then notified that this has occurred by being copied on this e-mail sent to the Friend so that the process has now also generated a new opportunity for the Agent to be of service to the Friend as well. Consequently, a planning PURL can be easily created and shared between different users, who may then use the Planning PURL as the basis for their travel excursion.
  • a computer-implemented method for generating a personalized universal resource locator (PURL") for a customer comprising: identifying a unique customer; collecting content data from a plurality of data sources; pre-caching the content data for access by the unique customer; and generating a PURL with one or more links to the pre-cached content data prepared for access by the unique customer.
  • PURL personalized universal resource locator
  • the computer-implemented method further comprises collecting the content data in one or more landing databases.
  • pre-caching the content data comprises preparing the content data in one or more staging databases prior to access by the unique customer.
  • pre-caching the content data further comprises preparing the content data based on the unique customer's profile.
  • the computer-implemented method further comprises retrieving the pre-cached content data from the one or more staging databases in dependence upon interaction by the unique customer with the one or more links to the pre-cached content data in the PURL.
  • the computer-implemented method further comprises: identifying one or more stages of a life-cycle for a product or service in relation to the unique customer; pre-caching content data relevant to the current life-cycle of the product or service in relation to the unique customer; and rendering personalized content data relevant to the current life-cycle of the product or service for the unique customer.
  • the computer-implemented method further comprises retrieving pre-cached content data from one or more staging databases in dependence upon interaction by the unique customer with the one or more links to the pre-cached content data in the PURL.
  • the product or service relates to a travel excursion, and the life- cycle of the product or service relates to the stages of the travel excursion.
  • the life-cycle of the travel excursion includes planning travel, booked travel, and after travel.
  • the computer-implemented method further comprises generating a personalized itinerary of all products and services booked through the PURL by the unique customer.
  • the computer-implemented method further comprises selecting a PURL skin associated with a product vendor or service provider; and rendering personalized content data corresponding to the product vendor or service provider.
  • the personalized content data corresponding to the product vendor or service provider is connected to products or services offered by the product vendor or service provider.
  • the computer-implemented method further comprises generating a planning PURL for access by the unique customer prior to purchase of a product or service.
  • the computer-implemented method further comprises sharing the planning PURL such that others can review the PURL prior to purchase of the product or service.
  • a computer-implemented system for generating a personalized universal resource locator (PURL") for a customer the system adapted to: identify a unique customer; collect content data from a plurality of data sources; pre- cache the content data for access by the unique customer; and generate a PURL with one or more links to the pre-cached content data prepared for access by the unique customer.
  • PURL personalized universal resource locator
  • system is further adapted to collect the content data in one or more landing databases.
  • system is further adapted to pre-cache the content data by preparing the content data in one or more staging databases prior to access by the unique customer.
  • system is further adapted to pre-cache the content data by preparing the content data based on the unique customer's profile.
  • system is further adapted to retrieve the pre-cached content data from the one or more staging databases in dependence upon interaction by the unique customer with the one or more links to the pre-cached content data in the PURL.
  • system is further adapted to: Identify one or more stages of a life-cycle for a product or service in relation to the unique customer; pre-cache content data relevant to the current life-cycle of the product or service in relation to the unique customer; and render personalized content data relevant to the current life-cycle of the product or service for the unique customer.
  • system is further adapted to retrieve pre-cached content data from one or more staging databases in dependence upon interaction by the unique customer with the one or more links to the pre-cached content data in the PURL.
  • the product or service relates to a travel excursion, and the life- cycle of the product or service relates to the stages of the travel excursion.
  • the life-cycle of the travel excursion includes planning travel, booked travel, and after travel.
  • the system is further adapted to generate a personalized itinerary of all products and services booked through the PURL by the unique customer.
  • system is further adapted to: select a PURL skin associated with a product vendor or service provider; and render personalized content data corresponding to the product vendor or service provider.
  • the personalized content data corresponding to the product vendor or service provider is connected to products or services offered by the product vendor or service provider.
  • system is further adapted to generate a planning PURL for access by the unique customer prior to purchase of a product or service.
  • system is further adapted to share the planning PURL such that others can review the PURL prior to purchase of the product or service.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Accounting & Taxation (AREA)
  • Development Economics (AREA)
  • Finance (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Game Theory and Decision Science (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne un système et un procédé de génération d'un localisateur de ressources universel personnalisé (PURL) pour un client. Dans un aspect, le procédé consiste à : identifier un client unique; recueillir des données de contenu depuis plusieurs sources de données; mettre en pré-cache les données de contenu en vue de l'accès par le client unique; et générer un PURL avec un ou plusieurs liens vers les données de contenu en pré-cache préparées pour un accès par l'utilisateur unique. Les données de contenu sont recueillies dans une ou plusieurs bases de données de base, et sont mises en pré-cache dans une ou plusieurs bases de données de stade avant l'accès par le client unique en fonction du profil du client unique. Un ou plusieurs stades d'un cycle de vie peuvent être identifiés pour un produit ou un service concernant le client unique afin de déterminer les données de contenu à mettre en pré-cache et à rendre dans le PURL.
PCT/CA2013/000579 2013-06-17 2013-06-17 Système et procédé de génération de sites internet personnalisés Ceased WO2014201537A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CA2013/000579 WO2014201537A1 (fr) 2013-06-17 2013-06-17 Système et procédé de génération de sites internet personnalisés

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CA2013/000579 WO2014201537A1 (fr) 2013-06-17 2013-06-17 Système et procédé de génération de sites internet personnalisés

Publications (1)

Publication Number Publication Date
WO2014201537A1 true WO2014201537A1 (fr) 2014-12-24

Family

ID=52103723

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CA2013/000579 Ceased WO2014201537A1 (fr) 2013-06-17 2013-06-17 Système et procédé de génération de sites internet personnalisés

Country Status (1)

Country Link
WO (1) WO2014201537A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020142803A1 (fr) * 2019-01-07 2020-07-16 Messageby Pty Ltd Système et procédé de messagerie personnalisés et interactifs
US11126340B2 (en) 2019-02-20 2021-09-21 Mastercard International Incorporated Systems and methods for dynamically generating customized web-based payment interfaces
US20220284451A1 (en) * 2021-03-04 2022-09-08 Walmart Apollo, Llc Methods and apparatus for electronic mapping of customer data
WO2023129691A1 (fr) * 2021-12-31 2023-07-06 Starkeys Llc Architectures et systèmes de réseau de commande basés sur une autorisation, ayant des composants et des éléments de réseau cellulaire modifiés pour héberger des schémas de commande d'autorisation conçus pour faciliter des sessions de communication poste à poste électroniques entre des dispositifs informatiques membres sur la base de signaux de communication cellulaire conformément à de nouveaux protocoles de communication cellulaire, et leurs procédés d'utilisation
US11968727B2 (en) 2022-07-11 2024-04-23 Starkeys Llc Permission-based controlling network architectures and systems, having cellular network components and elements modified to host permission controlling schemas designed to facilitate protocol mediated payment activities via cellular networks methods for use thereof
US12197504B2 (en) 2022-04-22 2025-01-14 International Business Machines Corporation Techniques for predicting a personalized URL document to assist a conversation

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090271259A1 (en) * 2008-04-28 2009-10-29 Blair Fish Method and system for directed personalized marketing
US20100211448A1 (en) * 2008-12-18 2010-08-19 American Express Travel Related Services Company, Inc. Systems, methods, and computer program products for rewards integration for an online tool
US20110131341A1 (en) * 2009-11-30 2011-06-02 Microsoft Corporation Selective content pre-caching

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090271259A1 (en) * 2008-04-28 2009-10-29 Blair Fish Method and system for directed personalized marketing
US20100211448A1 (en) * 2008-12-18 2010-08-19 American Express Travel Related Services Company, Inc. Systems, methods, and computer program products for rewards integration for an online tool
US20110131341A1 (en) * 2009-11-30 2011-06-02 Microsoft Corporation Selective content pre-caching

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020142803A1 (fr) * 2019-01-07 2020-07-16 Messageby Pty Ltd Système et procédé de messagerie personnalisés et interactifs
US11126340B2 (en) 2019-02-20 2021-09-21 Mastercard International Incorporated Systems and methods for dynamically generating customized web-based payment interfaces
US20220284451A1 (en) * 2021-03-04 2022-09-08 Walmart Apollo, Llc Methods and apparatus for electronic mapping of customer data
WO2023129691A1 (fr) * 2021-12-31 2023-07-06 Starkeys Llc Architectures et systèmes de réseau de commande basés sur une autorisation, ayant des composants et des éléments de réseau cellulaire modifiés pour héberger des schémas de commande d'autorisation conçus pour faciliter des sessions de communication poste à poste électroniques entre des dispositifs informatiques membres sur la base de signaux de communication cellulaire conformément à de nouveaux protocoles de communication cellulaire, et leurs procédés d'utilisation
US12197504B2 (en) 2022-04-22 2025-01-14 International Business Machines Corporation Techniques for predicting a personalized URL document to assist a conversation
US11968727B2 (en) 2022-07-11 2024-04-23 Starkeys Llc Permission-based controlling network architectures and systems, having cellular network components and elements modified to host permission controlling schemas designed to facilitate protocol mediated payment activities via cellular networks methods for use thereof
US12302420B2 (en) 2022-07-11 2025-05-13 Starkeys Llc Permission-based controlling network architectures and systems, having cellular network components and elements modified to host permission controlling schemas designed to facilitate electronic peer-to-peer communication sessions between member computing devices based on cellular communication signals in accordance with novel cellular communications protocols, and protocol mediated automated teller machine (ATM) payment activities via cellular networks methods for use thereof

Similar Documents

Publication Publication Date Title
JP7618079B2 (ja) アクション可能なウィジェットカード
US11922338B2 (en) Devices, systems and methods for providing ancillary objects from a cache and categorized provider objects
US11582276B1 (en) Distributed messaging communication system integrated with a cross-entity collaboration platform
US8839232B2 (en) Customer relationship management portal system and method
CA2726733C (fr) Plateforme pour communiquer a travers de multiples canaux de communication
US7111007B2 (en) Real-time aggregation of data within a transactional data area of an enterprise planning environment
US20090313053A1 (en) Guest Relationship Management System
US20230113369A1 (en) Distributed messaging communication system integrated with a cross-entity collaboration platform
GB2557522A (en) Digital ticketing system including a server and multiple mobile smartphone computing devices each including a respective digital ticketing application
US20120004936A1 (en) Method and system for facilitating ancillary services
WO2014201537A1 (fr) Système et procédé de génération de sites internet personnalisés
EP4713803A1 (fr) Système et procédé d'intégration d'interaction de modèle améliorée dans un système de construction de site web
CA2711909A1 (fr) Systeme de reservation de voyages en ligne et procede offrant des opportunites de voyage avec certaines restrictions
EP3809279A1 (fr) Dispositif, système et procédé de formation de modèles d'apprentissage machine à l'aide de messages associés à des objets fournisseur
US20130166330A1 (en) Seamless travel hive engine and method of same
US12614021B2 (en) System and method for integrated temporal external resource allocation
FR3094809A1 (fr) Procédé et dispositif pour la gestion d’évènements
FR3102278A1 (fr) Dispositif, système et procédé pour former des modèles d’apprentissage automatique en utilisant des messages associés à des objets de fournisseur
WO2001065445A1 (fr) Systeme d'assistance de gestion internet
Khliupko Enterprise

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

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

Country of ref document: EP

Kind code of ref document: A1