WO2021173028A1 - Method and system for generating ticket offer alerts - Google Patents
Method and system for generating ticket offer alerts Download PDFInfo
- Publication number
- WO2021173028A1 WO2021173028A1 PCT/RU2020/000107 RU2020000107W WO2021173028A1 WO 2021173028 A1 WO2021173028 A1 WO 2021173028A1 RU 2020000107 W RU2020000107 W RU 2020000107W WO 2021173028 A1 WO2021173028 A1 WO 2021173028A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- ticket
- data
- user
- gateway
- parameters
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/02—Reservations, e.g. for tickets, services or events
Definitions
- Prior art patent application JP2005018369A "Seat reservation system for train, seat reservation server, program, and seat reservation method for train" (Applicant: Nec Corp, publication date: 20.01.2005).
- the present invention relates to a system for booking seats on a train, a server for booking seats, a program and a method for booking seats on a train.
- the user can indicate various requests for a designated place, and the system searches for the most comfortable place for him upon request.
- the station window terminal 3 and the travel agency terminal 4 request input of seat conditions and priority, including train designation, vehicle location classification, vehicle position classification, and user contact information for transmission to the seat reservation server and reservation instruction means to display the received information about the free space.
- the seat reservation server uses the received data and conditions and develops conditions until a seat is found.
- the disadvantage of this technical solution is that the system needs a database with all available places for sale.
- the system can work with any provider of data on available seats, both with those that allow you to get all available seats at once in all directions and for all dates, and with those that give the availability of seats for a specific flight on a specific date. ...
- An additional disadvantage of the solution is that the system does not allow using this system from any client device (browser, mobile device, etc.), but only from a physical terminal. [006] In the claimed solution, the system allows you to receive notifications for the appearance of places and thus buy them in any system that the user likes. In the JP2005018369A application system, the client is tied to the system through which he searches for the necessary places for himself.
- the technical problem or the technical problem solved in this technical solution is the implementation of the method and system for generating notifications about the appearance of ticket offers.
- the technical result achieved by solving the above technical problem is to increase the likelihood of a user receiving a ticket offer.
- An additional technical result is to improve the reliability of generating notifications about the appearance of ticket offers.
- the specified technical result is achieved by implementing a method for generating notifications about the appearance of ticket offers, which is performed by at least one computing device and in which his data and parameters of at least one offer required for him are received on the server from at least one user ticket; form in the data storage of the server at least one data structure, the fields of which correspond to the parameters of the required at least one ticket offer for the user obtained in the previous step; all previously formed data structures are unloaded from the data storage at a predetermined frequency; sending a request to at least one ticket booking gateway to search for offers based on the data structures obtained in the previous step; receive a response from at least one ticket booking gateway, and if the response from the gateway contains ticket offers that satisfy the values of the fields of at least one data structure, send a notification about the appearance of the ticket offer to the user using his contact information from this data structure.
- user data includes an email address and / or telephone number and / or name and / or nickname.
- the parameters of the ticket offer include a departure date or date range and / or class of service and / or number of seats required.
- the user's data and parameters of the required ticket offer are obtained from a website or a mobile communication device.
- the server data store is persistent and / or non-persistent.
- the non-persistent store is located in the RAM of the computing device.
- memcache is used as the persistent storage of MariaDB rather than the persistent storage.
- the data structure, the fields of which correspond to the parameters of the required ticket offer for the user is a row of a database table. [0018] In some embodiments of the technical solution, the data structure, the fields of which correspond to the parameters of the required ticket offer for the user, additionally includes a status, next check date, priority.
- the data structures generated in the data store of the server are combined into groups.
- the data structures are combined into groups if the fields coincide with the point of departure and arrival, and / or the date of departure, and / or the class of service and the number of passengers.
- the request to the ticket booking gateway to search for offers is an HTTP request (or HTTPS) to the gateway API.
- the response from the ticket booking gateway comes in XML or JSON format.
- FIG. 1 shows an example of the implementation of the method for generating notifications about the appearance of ticket offers, shown in the form of a block diagram.
- FIG. 2 shows an implementation option for the user to form a request for a ticket, send it to the server, and store it in a persistent and non-persistent data store.
- FIG. 3 shows a variant of the implementation of the formation in the data storage of the server of the data structure, the fields of which correspond to the parameters of the required ticket offer for the user.
- FIG. 4 shows a variant of the implementation of the system for generating notifications about the appearance of ticket offers.
- FIG. 5 shows an embodiment of sending a request to a ticket booking gateway to search for offers based on data structures unloaded from the storage and grouped.
- a system means a computer system, a computer (electronic computer), CNC (numerical control), PLC (programmable logic controller), computerized control systems and any other devices capable of performing a given, well-defined sequence of operations. (actions, instructions), centralized and distributed databases, smart contracts.
- An instruction processing device means an electronic unit or an integrated circuit (microprocessor) executing machine instructions (programs), a smart contract, an Ethereum virtual machine (EVM), or the like.
- a command processor reads and executes machine instructions (programs) from one or more storage devices.
- Data storage devices can be, but are not limited to, hard disks (HDD), flash memory, ROM (permanent storage device), solid state drives (SSD), optical drives.
- a program is a sequence of instructions for execution by a computer control device or command processing device.
- a method 100 for generating notifications of the appearance of ticket offers shown in block diagram form in FIG. 1, will be described in detail below. 1 and below through a series of computational steps.
- Step 110 receive on the server from at least one user his data and parameters required for him at least one offer of a ticket.
- the functionality of this technical solution allows the user 200 to subscribe to receive notifications when tickets are on sale, as shown in FIG. 2.
- the user leaves his contact information (for example, an email address or phone number, or a nickname or ID in the messenger, etc., not limited to) and subscribes to the transport he needs (for example, railway or air) or a whole direction , and also selects a specific date or range of dates, class of service, number of seats required and other necessary requirements for seats for the trip.
- the user leaves his data on the user's website or mobile application, and also selects the notification parameters (for which train, date, etc. he wants to receive a ticket).
- the parameters of the request 210 he has generated for notifications of emerging ticket offers are sent to the server 220 (for example, in an exemplary implementation this may be an AJAX request from a web browser).
- this can be any communication device configured to transmit data to the server 220.
- it can be a mobile application installed on the user's phone. It can also be terminals for travel by bus, which are installed at train stations.
- Server 220 receives requests 210 with notification parameters on its side.
- a record is created in persistent storage 230 (for example, in a database), which is a row of a database table (for example, in a MySQL database) as well as an entry in a non-persistent storage 240 (for example, in a database located in the operational memory, without writing to disk), because fetching from it will be faster than from persistent store 230, after which processing is finished.
- Non-persistent storage 240 resides in the RAM of the computing device, so if server 220 is turned off and on, all data is lost. However, accessing data in RAM is faster than in the case of a regular persistent database such as MySQL.
- Two data stores are used in a particular implementation so that if the non-persistent store 240 is zeroed (i.e., the data is lost), it is possible to load data from the persistent store 330.
- the non-persistent store 240 in a particular implementation uses memcache, and the persistent store 230 is MariaDB. After the appearance of places that are tracked according to the algorithm below, the user 200 is notified of the opportunity to buy tickets through the contact information left earlier on any data transmission channel, as shown in FIG. 2.
- the user through the graphical user interface is given the opportunity to issue an application for notification of the appearance of ticket offers for the previously selected transport on sale.
- the user selects the parameters of the application from the drop-down list or enters it on his own.
- the parameters of the application can be, but are not limited to, the mode of transport of interest, the date of departure or the range of dates of the direction, the point of departure, the point of arrival, the number of tickets or the number of passengers, the class of service (can be presented as "economy / economy + / business” or for railway transport in Russia as "seated / reserved seat / shared / compartment, luxury / sleeping car"), flight number optional, contact information for notification: SMS / e-mail or other types.
- the user through the interface confirms his agreement with the provided application parameters and these parameters are sent to the server via the Internet communication channel via the HTTP or HTTPS data transfer protocol.
- HTTP HyperText Transfer Protocol
- Other protocols from the TCP / IP protocol stack may be used without being limited to HTTP.
- Step 120 at least one data structure is generated in the server data store, the fields of which correspond to the parameters of the required at least one ticket offer for the user obtained in the previous step.
- a structure 310 is created in the data store, the fields of which correspond to the parameters of the application, as shown in FIG. 3.
- the parameters of the request 210 are automatically entered into this structure 310 (a class object in programming).
- this structure 310 there are additional fields that do not correspond in any way with the notification parameters received from the user, but are filled on the server side 220.
- These additional the fields of structure 310 may include the status of the application (created, verified, completed, canceled), next verification date, priority.
- the priority may depend on the strategy for searching for ticket offers. For example, trains will leave soon or this is the beginning of sales, so it is better to process them first.
- the field "application status” is initially set to the value “created” - this means that the application has just been created and nothing has happened to it.
- the status "verified” means that at least one attempt was made to “verify” the application (more on this below).
- “Completed” means that a notification has been triggered for the user and nothing else needs to be done with this application. "Canceled” - for some reason this application was canceled, for example, at the request of the user or if they could not find offers of tickets on demand (for example, the train has already left).
- the "next check date” field means what date and time the application will be “checked”, as detailed below. To fill this date, the closest date is selected from as many dates as the next poll date selection strategies are used. Strategies are algorithms that, based on input parameters, output the date and time of the ticket offer. Below, as an example of implementation, there are strategies for searching for ticket offers for railway transport.
- a set is obtained from the number of hours before departure (this set may differ for different directions, ticket booking systems, type of transport, but in a specific implementation example for railway transport, this set is as follows: "24 hours before departure”, “in 6 hours”, “in 4", “in 2", “in 0 hours”).
- a set of dates with time is compiled by subtracting from the date and time of departure of the train the number of hours from the set with added, for example, five minutes (this is the time for issuing a ticket on the site). In fact, this should be the average time it takes for a user to issue a ticket on the website or in a mobile application. This time is chosen empirically.
- This set of dates is further filtered by removing all dates that have already occurred. Filtering can be implemented as follows. For example, at the moment the time is 19:00, and the train leaves tomorrow at 18:00. If you take the time "24 hours before departure", you get the date "today at 18:00". But it has already come, because it is now 19:00. Therefore, this date is removed from the sample and proposals are considered further. For example, they take for "6 hours", etc. As a result, only those dates will remain that have not yet come. From the remaining dates, the closest to the current date and time is selected. For example, the set of dates remained as follows: “today at 21:00", “today at 23:00". And now it is 19:00. The closest date is "today at 21:00".
- a set of dates (date + time) is generated by subtracting the following segments from the departure date and time: "40 days” “35 days” “25 days” “20 days” “15 days” “10 days” “7 days” “5 days” “3 days”. Further, from the resulting set of dates with time, only those that have not yet come are left and then the nearest date with time is taken from them
- a set of dates with time is returned based on the date and time of opening sales for a particular direction.
- the date and time of opening sales for a specific direction are taken.
- this date with time 5, 10, 15, 25, 45, 105 and 145 minutes, we get a set of 7 dates with time, of which we leave only those that have not yet come and from them we take the closest date with time.
- the Priority field specifies the priority for the bid, i. E. how much more priority this application is than another. By default, we set the "normal" priority.
- Persistent store 230 is only used to populate non-persistent 240 in a situation where the latter was reset as a result of clearing RAM, for example, in a server 220 reboot situation or in abnormal situations.
- Step 130 all previously generated data structures are unloaded from the data store at a predetermined frequency.
- Server 220 runs a daemon process 500 (ie, a computer program on UNIX-class systems that is launched by the system itself and runs in the background without direct user interaction) as shown in FIG. 5, which, for example, every minute or several seconds, but not limited to, unloads from non-persistent storage 240 (because it is much faster than persistent) all previously saved structures 310, which have the content of the "next check date" field less than the current date and time, those. it's time to check.
- the daemon process 500 may be disabled during non-running hours of the booking gateway 530 if known in advance. For example, it is known that gateways 530 do not work from 3 to 4 am and there is no point in polling them.
- These structures are formed into groups (510, 520, etc.) as shown in FIG. 5.
- groups 510, 520, etc.
- they In order for the structures to be in the same group, they must have the same fields with the point of departure and arrival (overlap), as well as the dates of departure, class of service and the number of passengers must intersect.
- grouping options are possible that will reduce the number of requests to gateways 530 and process similar requests at once.
- Step 140 requesting at least one ticket reservation gateway to search for offers based on the data structures obtained in the previous step.
- a request is made by the server 220 to the ticket reservation gateway 530.
- a request is generated in the API gateway 530, which is an HTTP request (or HTTPS) 530 tickets in the booking gateway API.
- the booking gateway 530 tickets is a third-party system that provides information via an API about current ticket offers by direction and date. Made earlier the grouping of structures 310 can reduce the number of requests to the gateway 530 and make one request for each group, instead of a separate request for each structure. For example, one user ordered notifications for the Moscow-St. Russia direction for tomorrow - any class of service, 1 passenger, and the second user also ordered Moscow-St. Russia for tomorrow, but for a specific train 056A - any class of service. In the group, respectively, there will be both of these requests, since they have overlapping dates and directions, as well as the class of service. [0054] Step 150: receive a response from at least one ticket reservation gateway.
- the response from the gateway 530 contains ticket offers that match the field values of at least one data structure 310, notify the user of the ticket offer appearance by his contact information from this data structure. [0056] Since the grouping was made by actually matching request parameters, therefore, the response from the ticket booking gateway simultaneously matches each data structure within the group (for example, in XML or JSON format).
- the daemon process matches the response from the gateway with all structures within the group.
- the fields of the application from the structure are compared with the answer whether such a ticket is there or not. If the response from the gateway contains ticket offers that satisfy the values of the fields of a specific structure from the group (that is, the departure date, arrival date, departure and arrival point, class of service and optionally a flight match), then the structure is given the status "Completed", after whereupon it is saved back to the two vaults.
- the client's contact information is taken from the same structure and the client is notified via the appropriate communication channels. Those structures for which none of the offers from the response from the gateway were matched are assigned the "verified” status, and the value of the "next verification date” field is filled in again by the algorithm described earlier. After that, these structures are also saved back to two storages.
- this technical solution can be implemented in the form of a computer system 400 for generating notifications about the appearance of ticket offers, which contains one or more of the following components:
- a processing component 401 comprising at least one processor 402
- the processing component 401 generally controls all of the operations of the system 400, such as processing data about the user or their ticket search request, and also controls the display, phone call, data communication, camera operation, and recording operation of the mobile communication device.
- the processing component 401 may include one or more processors 402 that implement instructions to complete all or part of the steps of the above methods.
- the processing component 401 may include one or more modules for convenient communication between other processing modules 401 and other modules.
- the processing component 401 may include a media module for convenient, lightweight interaction between the media component 405 and the processing component 401.
- Memory 403 is configured to store various types of data to support the operation of system 400, such as a user profile database. Examples of such data include instructions from any application or method, contact information, address book data, messages, images, videos, etc., and they all work. on system 400.
- Memory 403 may be implemented as any type of volatile memory, nonvolatile memory, or a combination thereof, such as static random access memory (SRAM), Electrically Erasable Programmable Read Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable read only memory (PROM), read only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk, and others, but not limited to.
- SRAM static random access memory
- EEPROM Electrically Erasable Programmable Read Only Memory
- EPROM Erasable Programmable Read Only Memory
- PROM Programmable read only memory
- ROM read only memory
- magnetic memory flash memory
- flash memory magnetic disk or optical disk, and others, but not limited to.
- the multimedia component 405 includes a screen providing an output interface between a system 400 that may be installed on a user's mobile communications device and a user.
- the screen may be a liquid crystal display (LCD) or a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen for receiving input from a user.
- the touch pad includes one or more touch sensors in terms of gestures, touching, and sliding across the touch pad. The touch sensor can not only sense the subject's touch boundary or swipe gesture, but also detect the length of time and pressure associated with touch and slide behavior.
- the media component 405 includes one front camera and / or one rear camera. When the system 400 is in an operating mode, such as shooting mode or video mode, the front camera and / or the rear camera can receive media data from the outside. Each front camera and rear camera can be one fixed lens optical system or can have focal length or optical zoom.
- the audio component 406 is configured to output and / or input an audio signal.
- the audio component 406 includes a single microphone (MIC) that is configured to receive an external an audio signal when the system 400 is in a mode of operation, such as a call mode, a recording mode, and a speech recognition mode.
- the resulting audio signal can be further stored in memory 403 or routed to data transfer component 409.
- the audio component 406 also includes a single speaker configured to output an audio signal.
- An input / output (I / O) interface 407 provides an interface between the processing component 401 and any peripheral interface module.
- the above peripheral interface module may be a keyboard, steering wheel, button, etc. These buttons may include, but are not limited to, a start button, a volume button, a start button, and a lock button.
- the sensor component 408 comprises one or more sensors and is configured to provide various aspects of assessing the state of the system 400.
- the sensor component 408 can detect on / off states of the system 400, the relative position of components, such as a display and a keypad, of a single component. system 400, presence or absence of contact between a subject and system 400, and orientation or acceleration / deceleration and temperature change of system 400.
- Sensor component 408 comprises a proximity sensor configured to detect the presence of an object in the vicinity when there is no physical contact.
- Touch component 408 includes an optical sensor (eg, CMOS or CCD image sensor) configured for use in rendering an application.
- sensor component 408 includes an acceleration sensor, gyroscope sensor, magnetic sensor, pressure sensor, or temperature sensor.
- Communication component 409 is configured to facilitate wired or wireless communication between system 400 and other devices.
- System 400 can access a wireless network based on a communication standard such as WiFi, 2G, 3G, 5G, or a combination thereof.
- communication component 409 receives a broadcast signal or broadcast related information from an external broadcast control system via a broadcast channel.
- communication component 409 comprises a Near Field Communication (NFC) module to facilitate near field communication.
- NFC Near Field Communication
- the NFC module may be based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
- RFID radio frequency identification
- IrDA infrared data association
- UWB ultra-wideband
- Bluetooth Bluetooth
- system 400 may be implemented by one or more Application-Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Units (DSPs), Programmable Logic Devices (PLCs), a logic chip programmed into operating conditions (FPGA), controller, microcontroller, microprocessor, or other electronic components, and can be configured to implement the method 500 for generating notifications about the appearance of ticket offers.
- ASICs Application-Specific Integrated Circuits
- DSPs Digital Signal Processors
- DSPs Digital Signal Processing Units
- PLCs Programmable Logic Devices
- FPGA logic chip programmed into operating conditions
- controller microcontroller, microprocessor, or other electronic components
- the non-volatile computer-readable medium comprises memory 403 that includes instructions where instructions are executed by processor 401 of system 400 to implement the above-described smart flight search methods.
- nonvolatile computer readable media can be ROM, random access memory (RAM), compact disc, magnetic tape, floppy disks, optical storage devices, and the like.
- Computing system 400 may include a display interface that transmits graphics, text, and other data from a communications infrastructure (or from a framebuffer, not shown) for display on a media component 405.
- Computing system 400 further includes input devices or peripherals.
- Peripheral devices may include one or multiple devices for interacting with the user's mobile communication device, such as a keyboard, microphone, wearable device, camera, one or more audio speakers, and other sensors.
- Peripheral devices can be external or internal to the user's mobile communications device.
- a touchscreen can display, typically graphics and text, and also provides a user interface (such as, but not limited to, a graphical user interface (GUI)) through which a subject can interact with a user's mobile communication device, such as access and interact with applications running on the device.
- GUI graphical user interface
- All blocks used in the system can be implemented with electronic components used to create digital integrated circuits, which is obvious to a person skilled in the art. Not limited to, microcircuits, the logic of which is determined during manufacture, or programmable logic integrated circuits (FPGA), the logic of which is set through programming, can be used.
- FPGA programmable logic integrated circuits
- programmers and debugging environments are used that allow you to set the desired structure of a digital device in the form of a circuit diagram or a program in special hardware description languages: Verilog, VHDL, AHDL, etc.
- FPGAs programmable logic controllers
- BMK basic matrix crystals
- ASICs specialized custom large integrated circuits (LSIs), which are significantly more expensive for small-scale and single-piece production.
- the FPGA itself consists of the following components: • configurable logic blocks that implement the required logic function;
- Blocks can also be implemented using read-only memory devices.
- aspects of the present technical solution may be implemented as a system, method, or computer program product. Accordingly, various aspects of the present technical solution may be implemented solely as hardware, as software (including application software, and so on), or as an embodiment combining software and hardware aspects, which may generally be referred to as a "module” , “System” or “architecture”. In addition, aspects of the present technical solution may take the form of a computer program product implemented on one or more computer-readable media having computer-readable program code that is implemented thereon.
- the computer-readable storage medium can be, without limitation, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or any suitable combination thereof. More specifically, examples (non-exhaustive list) of computer-readable storage media include: one or more wire connection; portable computer diskette; hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or Flash memory), fiber optic connection, compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any combination of the above.
- a computer-readable storage medium can be any flexible storage medium that can contain or store a program for use by the system itself, device, apparatus, or in connection therewith.
- Program code embedded in a computer-readable medium can be transmitted using any medium, including, without limitation, wireless, wired, fiber optic, infrared, and any other suitable network or combination of the above.
- Computer program code for performing operations for the steps of this technical solution may be written in any programming language or combinations of programming languages, including an object-oriented programming language such as Python, R, Java, Smalltalk, C ++, and so on, and conventional procedural programming languages such as "C" programming language or similar programming languages.
- the program code can be executed on the user's computer in whole, in part, or as a separate software package, partially on the user's computer and partially on the remote computer, or completely on the remote computer.
- the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN), a wide area network (WAN), or a connection to an external computer (for example, via the Internet using Internet service providers).
- LAN local area network
- WAN wide area network
- Internet service providers for example, via the Internet using Internet service providers.
- These computer program instructions may also be stored on a computer-readable medium that can control a computer other than a programmable data processing device or devices that function in a particular way, such that the instructions stored on the computer-readable medium create a device including instructions that perform the functions / actions specified in the block diagram and / or diagram.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Human Resources & Organizations (AREA)
- Data Mining & Analysis (AREA)
- Development Economics (AREA)
- Computational Linguistics (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Databases & Information Systems (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Information Transfer Between Computers (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
RU2020108799A RU2748177C1 (en) | 2020-02-28 | 2020-02-28 | Method and system for generating notifications about ticket offers |
RU2020108799 | 2020-02-28 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021173028A1 true WO2021173028A1 (en) | 2021-09-02 |
Family
ID=75919744
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/RU2020/000107 WO2021173028A1 (en) | 2020-02-28 | 2020-02-28 | Method and system for generating ticket offer alerts |
Country Status (2)
Country | Link |
---|---|
RU (1) | RU2748177C1 (en) |
WO (1) | WO2021173028A1 (en) |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
RU2324221C2 (en) * | 2002-08-21 | 2008-05-10 | Боокит Ой | Order receiving method and system |
US8930449B1 (en) * | 2000-02-22 | 2015-01-06 | Harvey Lunenfeld | Metasearch engine for ordering at least one travel related item returned in combined search and database results using at least one query on multiple unique hosts and at least one database |
US9218413B2 (en) * | 2011-06-13 | 2015-12-22 | Opus Deli, Inc. | Venue-related multi-media management, streaming, online ticketing, and electronic commerce techniques implemented via computer networks and mobile devices |
US20170061487A1 (en) * | 2008-10-31 | 2017-03-02 | Stubhb, Inc. | System and methods for upcoming event notification and mobile purchasing |
US9807092B1 (en) * | 2013-07-05 | 2017-10-31 | Dcs7, Llc | Systems and methods for classification of internet devices as hostile or benign |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
RU2600864C1 (en) * | 2014-04-03 | 2016-10-27 | Павел Михайлович Малышев | Automated method for searching transportation services and automated system to implement such method |
-
2020
- 2020-02-28 WO PCT/RU2020/000107 patent/WO2021173028A1/en active Application Filing
- 2020-02-28 RU RU2020108799A patent/RU2748177C1/en active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8930449B1 (en) * | 2000-02-22 | 2015-01-06 | Harvey Lunenfeld | Metasearch engine for ordering at least one travel related item returned in combined search and database results using at least one query on multiple unique hosts and at least one database |
RU2324221C2 (en) * | 2002-08-21 | 2008-05-10 | Боокит Ой | Order receiving method and system |
US20170061487A1 (en) * | 2008-10-31 | 2017-03-02 | Stubhb, Inc. | System and methods for upcoming event notification and mobile purchasing |
US9218413B2 (en) * | 2011-06-13 | 2015-12-22 | Opus Deli, Inc. | Venue-related multi-media management, streaming, online ticketing, and electronic commerce techniques implemented via computer networks and mobile devices |
US9807092B1 (en) * | 2013-07-05 | 2017-10-31 | Dcs7, Llc | Systems and methods for classification of internet devices as hostile or benign |
Also Published As
Publication number | Publication date |
---|---|
RU2748177C1 (en) | 2021-05-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10852903B2 (en) | Optimizing transportation networks through dynamic user interfaces | |
CN110073384B (en) | Systems, methods, and media for providing a digital assistant | |
US20180253806A1 (en) | System and process for managing preparation and packaging of food and/or beverage products for a precise delivery time | |
US10708733B1 (en) | Initiating transportation requests | |
US20210083924A1 (en) | System and method for a unified connected network | |
US10311530B2 (en) | System and process for managing preparation and packaging of food and/or beverage products for a precise delivery time | |
CN111656324B (en) | Personalized notification agent | |
US20130132102A1 (en) | Smart parking space allocation system and method | |
CN107251065A (en) | Personalized notifications | |
EP3622459B1 (en) | Method and apparatus for generating workflow | |
US20140142948A1 (en) | Systems and methods for in-vehicle context formation | |
US8933822B2 (en) | Method and apparatus for extra-vehicular emergency updates following an accident | |
US20150235332A1 (en) | Realtor-client connection solutions | |
CN107251066A (en) | Personalization is reminded | |
US20240098685A1 (en) | Customizing user experiences based on transportation irregularities | |
RU2748177C1 (en) | Method and system for generating notifications about ticket offers | |
EP4239540A1 (en) | Travel prompting method and apparatus | |
RU2683188C1 (en) | Method and system for automatic connection of shipper and cargo carrier | |
US11055670B1 (en) | Systems and methods for generating a travel smartlist | |
US20210374650A1 (en) | Ride assignment system | |
RU2766062C1 (en) | Method and system for processing group trip of users without access to personal data | |
US20240143353A1 (en) | Systems and methods for improved graphical user interfaces based on contextual information | |
US12014617B2 (en) | Contextual item discovery and pattern inculcated reminder mechanism | |
CN114819228A (en) | Parking space reservation method and equipment and computer readable storage medium | |
WO2020204743A1 (en) | Method and system for paying rewards on the internet |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 20922208 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: 20922208 Country of ref document: EP Kind code of ref document: A1 |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205N DATED 20/10/2022) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20922208 Country of ref document: EP Kind code of ref document: A1 |