Methods and systems for validating real time network communications
First Claim
1. A method for managing network communications, comprising:
- receiving a first request for a ticket from a requester at a ticket system, wherein the ticket system comprises a search user interface for performing a search using one or more search criteria specified by the requester;
sending a second request for a resource from the ticket system, the ticket system coupled to a plurality of broker systems, wherein;
the ticket system is an independent platform which is physically separate from the plurality of broker systems,at least one broker system in the plurality of broker systems is operated by a different entity than an entity operating the ticket system, andthe at least one broker system in the plurality of broker systems maintains a different inventory of resources than another broker system in the plurality of broker systems;
maintaining a ticket data store storing ticket identifiers and associated real-time status information;
monitoring a communication status with each of the plurality of broker systems that reflects whether one or more expected signals have been received over a communication link between the ticket system and the broker system;
identifying a communication status with a first broker system from amongst the plurality of broker systems as being unsatisfactory;
inhibiting the offering of tickets from the first broker system;
identifying a second broker system, from amongst the plurality of broker systems and using the ticket data store, that controls the ticket;
querying the second broker system controlling the ticket;
formatting a message comprising discounted price associated with the ticket;
transmitting the message over a network to the requester using the ticket system;
receiving a third request to purchase the ticket;
receiving payment information for the ticket from the requester at the ticket system;
verifying the payment information for the ticket from the requester at the ticket system;
receiving an indication from the ticket system that indicates that the ticket has been identified as sold for the requester; and
facilitating the transfer of the ticket with a barcode to the requester.
3 Assignments
0 Petitions
Accused Products
Abstract
Methods and systems for managing network communications are described. An example resource management system includes a communications manager configured to access information regarding communication protocols used by corresponding broker systems and to provide message translations based on an origin and/or destination of the message to be transmitted. A message processor is coupled to the communications manager and is configured to serialize incoming and/or outgoing broker messages and to facilitate queuing of incoming and outgoing message traffic with broker systems. A communications configurer is configured to track one or more communication attributes of broker systems and changes thereto to ensure communications between the resource management systems are broker systems are conducted in accordance with the communication attributes of the broker systems. A communications rules provider is configured to determine which broker system is to be communicated with in order to fulfill a resource request.
-
Citations
20 Claims
-
1. A method for managing network communications, comprising:
-
receiving a first request for a ticket from a requester at a ticket system, wherein the ticket system comprises a search user interface for performing a search using one or more search criteria specified by the requester; sending a second request for a resource from the ticket system, the ticket system coupled to a plurality of broker systems, wherein; the ticket system is an independent platform which is physically separate from the plurality of broker systems, at least one broker system in the plurality of broker systems is operated by a different entity than an entity operating the ticket system, and the at least one broker system in the plurality of broker systems maintains a different inventory of resources than another broker system in the plurality of broker systems; maintaining a ticket data store storing ticket identifiers and associated real-time status information; monitoring a communication status with each of the plurality of broker systems that reflects whether one or more expected signals have been received over a communication link between the ticket system and the broker system; identifying a communication status with a first broker system from amongst the plurality of broker systems as being unsatisfactory; inhibiting the offering of tickets from the first broker system; identifying a second broker system, from amongst the plurality of broker systems and using the ticket data store, that controls the ticket; querying the second broker system controlling the ticket; formatting a message comprising discounted price associated with the ticket; transmitting the message over a network to the requester using the ticket system; receiving a third request to purchase the ticket; receiving payment information for the ticket from the requester at the ticket system; verifying the payment information for the ticket from the requester at the ticket system; receiving an indication from the ticket system that indicates that the ticket has been identified as sold for the requester; and facilitating the transfer of the ticket with a barcode to the requester. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13)
-
-
14. A system for managing network communications, comprising:
-
a computing device; programmatic code stored in a non-transitory computer readable medium, that when executed by a computing system comprising one or more computing devices is configured to cause the computing system to perform operations comprising; receiving a first request for a ticket from a requester at a ticket system, wherein the ticket system comprises a search user interface for performing a search using one or more search criteria specified by the requester; sending a second request for a resource from the ticket system, the ticket system coupled to a plurality of broker systems, wherein; the ticket system is an independent platform which is physically separate from the plurality of broker systems, at least one broker system in the plurality of broker systems is operated by a different entity than an entity operating the ticket system, and the at least one broker system in the plurality of broker systems maintains a different inventory of resources than another broker system in the plurality of broker systems; maintaining a ticket data store storing ticket identifiers and associated real-time status information; monitoring a communication status with each of the plurality of broker systems that reflects whether one or more expected signals have been received over a communication link between the ticket system and the broker system; identifying a communication status with a first broker system from amongst the plurality of broker systems as being unsatisfactory; inhibiting the offering of tickets from the first broker system; identifying a second broker system, from amongst the plurality of broker systems and using the ticket data store, that controls the ticket; querying the second broker system controlling the ticket; formatting a message comprising discounted price associated with the ticket; transmitting the message over a network to the requester using the ticket system; receiving a third request to purchase the ticket; receiving payment information for the ticket from the requester at the ticket system; verifying the payment information for the ticket from the requester at the ticket system; receiving an indication from the ticket system that indicates that the ticket has been identified as sold for the requester; and facilitating the transfer of the ticket with a barcode to the requester. - View Dependent Claims (15, 16, 17, 18)
-
-
19. Non-transitory computer readable memory storing instructions that when executed by a computing system are configured to cause the computing system to perform operations comprising:
-
receiving a first request for a ticket from a requester at a ticket system, wherein the ticket system comprises a search user interface for performing a search using one or more search criteria specified by the requester; sending a second request for a resource from the ticket system, the ticket system coupled to a plurality of broker systems, wherein; the ticket system is an independent platform which is physically separate from the plurality of broker systems, at least one broker system in the plurality of broker systems is operated by a different entity than an entity operating the ticket system, and the at least one broker system in the plurality of broker systems maintains a different inventory of resources than another broker system in the plurality of broker systems; maintaining a ticket data store storing ticket identifiers and associated real-time status information; monitoring a communication status with each of the plurality of broker systems that reflects whether one or more expected signals have been received over a communication link between the ticket system and the broker system; identifying a communication status with a first broker system from amongst the plurality of broker systems as being unsatisfactory; inhibiting the offering of tickets from the first broker system; identifying a second broker system, from amongst the plurality of broker systems and using the ticket data store, that controls the ticket; querying the second broker system controlling the ticket; formatting a message comprising discounted price associated with the ticket; transmitting the message over a network to the requester using the ticket system; receiving a third request to purchase the ticket; receiving payment information for the ticket from the requester at the ticket system; verifying the payment information for the ticket from the requester at the ticket system; receiving an indication from the ticket system that indicates that the ticket has been identified as sold for the requester; and facilitating the transfer of the ticket with a barcode to the requester. - View Dependent Claims (20)
-
Specification