194 results about "Event object" patented technology

Mechanisms and techniques provide the system that allows a sending computer system to capture and store event information related to events that transpire on a sending computer system in event batches. The event information can include event functionality related to event object in the timestamp related to the event. Periodically, in response to the occurrence of the batch transfer condition, the sending computer system transmits an event batch monthly computer network for receipt by a receiving computer system. The event batch may be processed through a collaboration adapter on the networks while prior to being send to the receiving computer system. Upon receipt of an event batch at the receiving computer system, the receiving computer system can compute a lag time required to receive the event batch. The receiving computer system can then recreate events based on the event information in the event batches while compensating for network lag time incurred during transmission of the event batch between a sending and receiving computer systems. By compensating for network lag during the recreation or playback of events, the system of the invention avoids the receiving computer system from reproducing events in a choppy or discontinuous manner or from getting left behind during event recreation due to accumulations of network lag time.

An embodiment includes a computer system for detecting and monitoring network intrusion events from log data received from network service devices in a computer network. An embodiment may include an event parser in communication with multiple network service devices. The event parser may parse information to create corresponding event objects concerning intrusion events. The system may include an event manager in communication with the event parser. The event manager may be configured to evaluate the event objects according to at least one predetermined threshold condition. The system may include an event broadcaster in communication with the event manager for receiving event objects designated by the event manager for broadcast. The event broadcaster may be able to transmit the event objects in real time. The system may also include means for alerting the user that a network intrusion event has occurred.

Systems and methods are provided for processing and analyzing signals reflecting, physiologic processes and events in a monitored subject, especially cardio-pulmonary signals. The input signals are analyzed by in a physiological domain by creating structured data representing the physiological events reflected in the signals. Preferably, first, primitive event objects are created representing physiologically-significant portions of these input signals; second, the primitive event objects are grouped into primary event objects representing actual physiologic processes and events. Next, all objects are stored in databases, and organized in containers for efficient searching. Information may be retrieved by creating view objects which associate physiologic event objects having selected properties specified directly in physiological terms. This invention includes methods for performing the above analysis, systems and program products for carrying out these methods, and databases configured with the stored objects and views.

A method and system are provided for synchronizing a plurality of calendars on a mobile device. An embodiment includes responsive to receiving a plurality of event objects, parsing each event object into event information and a calendar identifier. The method includes associating each event object with a calendar based on the calendar identifier. The method includes displaying the event objects on a calendar client executing on the consumer device, wherein each event object indicates the calendar with which it is associated.

Methods, systems, and computer-readable media are disclosed for event processing with a query based on a reusable XML query template. A particular method includes receiving a plurality of events from a source and generating a plurality of event objects based on the plurality of events. A query represented by an XML file based on a reusable XML query template is executed with respect to the plurality of event objects to produce a plurality of result objects. Each result object is produced based on an application of at least one operator of the query. A plurality of results is generated based on the plurality of result objects, and the plurality of results is transmitted to a sink.

An automated financial market communication apparatus executes actions as desired, and includes a facility for selecting parameters including: event category, event object, object attribute, attribute comparison, and comparison value. These parameters establish a condition or conditions of operation of the apparatus. Actions may be selected and logged for execution given one or another of the conditions. The actions are then executed manually or automatically in managing a financial market portfolio.

A system, method and article of manufacture are provided for creating a synchronizer object in order to playback an event simultaneously on a plurality of a client apparatuses. First, a request is received utilizing a network for viewing an event. Next, the request is queued in memory. In response to the request, an object is created which is adapted to playback the event on a client apparatus simultaneous with the playback of the event on the remaining client apparatuses upon the receipt of an activation signal. The object is sent to one of the client apparatuses utilizing the network for being stored therein.

Coverage metrics are expressed with an intuitive graphical interface based upon data flow. Coverage analysis and presentation objects are integrated to produce coverage results which enable device functionality in a device under test to be modeled as objects, subject to event occurrence. Event objects are introspected at run-time, allowing the user to determine the event object's attributes with specification of coverage metrics subject to a selected combination of the event object's attributes. The event objects are serialized into permanent storage, allowing the user to specify and execute new coverage metrics at any time after simulation. Operations used to describe coverage metrics are modeled as analysis objects. Such analysis objects accept event objects as inputs, using a predetermined, well-defined interface. The combination of event objects and analysis objects allows coverage metrics to be specified in a simple data flow manner. With such a coverage metric, the user attaches or wires (metaphorically) the analysis objects together in a visual builder environment. Using the analysis objects, the user specifies desired coverage metrics, such as coverage of sequences of events and/or coverage of events that occur during the same time window of a simulation. The display functionality of the coverage tool is expandable because the presentation objects use the same event object interface as the analysis operator objects. Coverage metrics are subject to specification either before or after event occurrence. The user specifies coverage metrics using an intuitive graphical interface based upon data flow, without any specific programming language skills being necessary. Functional events in the device under test are treated as event objects. Each event object may be passed to selected analysis tools chosen by the user, such as analyzers, logic gates, and coincidence counters.

An incident response system and method for tracking data security incidents in enterprise networks is disclosed. An Incident Manager application (IM) stores incident objects and incident artifacts (IAs) created in response to the incidents, where the incident objects include the information for the incident and the IAs are associated with data resources (e.g. IP addresses and malware hashes) identified within the incident objects. In response to creation of the IAs, the IM issues queries against one or more external threat intelligence sources (TISs) to obtain information associated with the IAs and augments the IAs with the obtained information. In examples, the IM can identify known threats by comparing the contents of IAs against TIS(s) of known threats, and can identify potential trends by correlating the created incident objects and augmented IAs for an incident with incident objects and IAs stored for other incidents.

Systems and methods for electronic simulation of events via computer-based gaming technologies are provided. Data relating to an event such as a sports games is received containing event object information. Events objects can be, for example, players on a field or objects relating to the event environment. A game object processing module correlates the event objects to game event objects. A video game console performs a game simulation using the game event objects, by applying the event data to the event objects, and then displaying the game simulation on the game console. The result is a simulation of the event via the game console.

A vault controller in an electronic business system includes a dispatcher for servicing browser requests initiated by a user for conducting business with an enterprise or organization using a vault process. The dispatcher further responds to a secure depositor receiving requests from other vault processes running in the controller. The request is in the form a URL containing an application domain/local context and application name. The request is detected and processed by event creator which forms an event object definitive of the request in the URL. An event handler parses the event object and enters a vault system application registry to locate the application in a shared memory. The location of the application is passed to a server pool, which assign a processing thread to handle the request. The thread engages a context manager which decrypts and imports application domain, application function and local context information from external storage to process the request. The application is located in the shared memory and the request implemented. The context manager encrypts and exports the processed information to external storage and provides a return code in the response to the user. The return code is used to locate the context information in a subsequent request by the user. The requests received from other vault processes through the secure depositor are handled in like manner to the user request. After execution of a user request, the vault process loops for some defined time during which other requests are received from the user. The absence of requests causes the vault process to shut down and store the variables for the next user request which retraces the steps of the original request.

The present invention envisages a system and method for converting a voluminous stream of unstructured short text messages into event-objects of specific event type that may be of potential interest to users at far away locations. The method of structuring involves detecting long tail of events in spite of their sparsity. This is followed by extracting and correlating detected short text messages that describe same event type to create structured event objects.

One embodiment of the present invention provides an enterprise system that automatically executes a rule associated with an event. During operation, the system receives an event object at the enterprise system. Next, the system creates an intermediate event object based on the event object, wherein the intermediate object is an invocation context for the rule. The system also filters a set of rules with the intermediate event object to obtain a subset of rules. The system then selects a rule that is associated with the event from the subset of rules. Finally, the system executes the rule.

A system and method for responding to incidents in an enterprise network is disclosed. The system tracks incidents by creating, in an incident Manager, incident objects for each incident. Each incident object includes details for the incidents, also known as incident characteristics. The system also creates one or more indicators of compromise (IOCs) associated with the incident characteristics for each incident. When processing a new incident or an update to an incident, the system compares IOCs associated with the incident object for the incident being processed to stored IOCs for other incidents to determine if other incidents are related to the incident being processed. In embodiments, the system can then generate tasks for responding to new incidents based on incident characteristics of and IOCs associated with the new incidents, and can regenerate tasks for responding to incidents based on updates to incident characteristics of and IOCs associated with the incidents.

A platform (1) allows end users to engage in a session with servers such as content providers, corporate systems, commercial services or ASPs. A session object is associated with each session, attributes of which include the channel—thereby allowing changing of a channel during a session. Request/event objects are associated with the session object as requests/notifications arise, and these objects are shared with other modules. Hosted services may be physically resident on the platform or may be accessed transparently via interfaces. A device/channel neutral mark-up language extended from a presentation mark-up language is used as a single common form from which the delivered content is derived. The content from a service is generated by an executable process, normally (but not exclusively) in the extended mark-up language. The derivation of deliverable content is performed via a dynamic and configurable sequence of providers that manipulate the original content in stages.

Methods and apparatus, including computer program products, for generating a data input template. A system captures data objects and event objects communicated between a client and an application program, stores a copy of the captured objects, and generates a template based on the stored objects. The client interface has a hierarchical structure. Each data object includes an address identifier specifying a location within this hierarchical structure with which it is associated, and metadata is generated based on this address identifier. Each event object includes a record of one or more actions performed by a user, and metadata is generated based on this record. The metadata is used in structuring the template, enabling the template to correspond to the hierarchical structure of the client interface. The template can be used to generate a web services description language document, which can be provided to third party users over a network.

In a plant information management system (PIMS, 1), data received from a process device (PCC, 10) is cached by a data logger (2) in blocks. A database controller (4) receives, for each data event, a time string, a value string, and a data quality indicator. The quality indicator is stored by exception only (if "bad"). MSBs of the time string are encoded in a hierarchical database structure of item (process device)-year-day levels. LSBs of the time string, the value string, and quality exceptions are stored as event objects in linked list arrays referenced to a day array object. There is thus no need for an index and the structure provides hierarchical compression.

Methods, systems, and computer-readable media are disclosed for time-based event processing using punctuation events. A particular method includes receiving a first event object comprising a first validity start time and a first validity end time, where the first validity end time is initially undefined. A punctuation object is received after the first event object. The punctuation event object has a punctuation timestamp indicating a time subsequent to the first validity start time. The punctuation event object indicates that event objects to be received at the computer system after the punctuation event object have validity start times later than the time indicated by the punctuation timestamp. The method includes setting the first validity end time to a value later than or equal to the time indicated by the punctuation timestamp.

Systems and methods for aggregating, processing, and displaying historical data—including actions and ideas—are provided. Based on a singular endpoint event or range of endpoint events, a plurality of historical threads both forward and backward looking in time are computed and displayed to the user via an interface in a manner that can assist the user in determining the relative importance of events along a thread. Event objects are created from data aggregated from cameras, global positioning software, social networking sites, direct user input, news feeds, and other sources. Connections between the objects are based on historical attributes including actors, descriptions, places, and time.