Methods and systems for validating real time network communications
First Claim
1. A method for managing network communications, comprising:
- receiving at a ticket management system over a network from a plurality of broker systems substantially real-time status information regarding tickets managed by the broker systems;
maintaining a ticket data store storing ticket identifiers and associated real-time status information;
monitoring the communication status with the plurality of broker systems;
if the communication status of a given broker system is determined to be unsatisfactory, storing an indication that the status of tickets managed by the given broker system is not reliable and inhibiting the offering of tickets from the given broker;
receiving a request for a first ticket from a first requester at the ticket management system;
identifying a first broker system controlling the first ticket using the ticket data store;
formatting a message including an identifier associated with the first ticket and an identifier associated with the first requester;
transmitting the message over the network to the first broker system;
receiving an indication from the first broker system as to whether a hold has been placed on the first ticket for the first requester and/or the first ticket has been identified as sold for the first requester; and
if an indication is received from the broker system that a hold has been placed on the first ticket for the first requester and/or the first ticket has been identified as sold for the first requester, facilitating the transfer of the first ticket to the first 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
57 Claims
-
1. A method for managing network communications, comprising:
-
receiving at a ticket management system over a network from a plurality of broker systems substantially real-time status information regarding tickets managed by the broker systems; maintaining a ticket data store storing ticket identifiers and associated real-time status information; monitoring the communication status with the plurality of broker systems; if the communication status of a given broker system is determined to be unsatisfactory, storing an indication that the status of tickets managed by the given broker system is not reliable and inhibiting the offering of tickets from the given broker; receiving a request for a first ticket from a first requester at the ticket management system; identifying a first broker system controlling the first ticket using the ticket data store; formatting a message including an identifier associated with the first ticket and an identifier associated with the first requester; transmitting the message over the network to the first broker system; receiving an indication from the first broker system as to whether a hold has been placed on the first ticket for the first requester and/or the first ticket has been identified as sold for the first requester; and if an indication is received from the broker system that a hold has been placed on the first ticket for the first requester and/or the first ticket has been identified as sold for the first requester, facilitating the transfer of the first ticket to the first requester. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25)
-
-
26. A ticket management system configured to manage network communications, comprising:
-
a computing system; non-transitory computer readable memory storing instructions that when executed by the computing system are configured to causing the computing system to perform operations comprising; receiving over a network from a plurality of broker systems substantially real-time status information regarding tickets managed by the broker systems; maintaining a ticket data store storing ticket identifiers and associated real-time status information; monitoring the communication status with the plurality of broker systems; if the communication status of a given broker system is determined to be unsatisfactory, storing an indication that the status of tickets managed by the given broker system is not reliable and inhibiting the offering of tickets from the given broker; receiving a request for a first ticket from a first requester; identifying a first broker system controlling the first ticket using the ticket data store; formatting a message including an identifier associated with the first ticket and an identifier associated with the first requester; transmitting the message over the network to the first broker system; receiving an indication from the first broker system as to whether a hold has been placed on the first ticket for the first requester and/or the first ticket has been identified as sold for the first requester; and if an indication is received from the broker system that a hold has been placed on the first ticket for the first requester and/or the first ticket has been identified as sold for the first requester, facilitating the transfer of the first ticket to the first requester. - View Dependent Claims (27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52)
-
-
53. 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 over a network from a plurality of broker systems substantially real-time status information regarding tickets managed by the broker systems; maintaining a ticket data store storing ticket identifiers and associated real-time status information; monitoring the communication status with the plurality of broker systems; if the communication status of a given broker system is determined to be unsatisfactory, storing an indication that the status of tickets managed by the given broker system is not reliable and inhibiting the offering of tickets from the given broker; receiving a request for a first ticket from a first requester; identifying a first broker system controlling the first ticket using the ticket data store; formatting a message including an identifier associated with the first ticket and an identifier associated with the first requester; transmitting the message over the network to the first broker system; receiving an indication from the first broker system as to whether a hold has been placed on the first ticket for the first requester and/or the first ticket has been identified as sold for the first requester; and if an indication is received from the broker system that a hold has been placed on the first ticket for the first requester and/or the first ticket has been identified as sold for the first requester, facilitating the transfer of the first ticket to the first requester. - View Dependent Claims (54, 55, 56, 57)
-
Specification