Abstract: Novel tools and techniques are provided for implementing name-based routing through networks. In various embodiments, a broker manager in each of a plurality of networks may receive a subscription request for a network device from a client device, each device being locally accessible or disposed in an upstream or downstream network. The broker manager uses its client broker to communicate with a locally accessible client device, and uses its mediator broker (and, sometimes, an intermediate device(s)) to communicate with a locally accessible network device. The broker manager otherwise uses its messaging brokers to communicate with control channels of one or more networks. Once subscription with the network device has been established, any commands and responses between the client device and the network device may be routed over pub/sub channels via the broker managers and their brokers using name-based routing, without routing based on IP address of the network device.

Abstract: Systems, methods, and apparatuses for automatically logging telematics data are provided herein. An apparatus includes one or more processors, and one or more memory devices storing instructions that, when executed by the one or more processors, cause the one or more processors to: receive access information from a remote computing system, the access information comprising information indicative of a data type and a logging duration; and, log telematics data that corresponds to the data type. Logging the telematics data includes: storing the telematics data that corresponds to the data type in a buffer for the logging duration; monitoring for a fault code; responsive to not detecting the fault code, causing the buffer to delete a portion of the telematics data; and responsive to detecting the fault code, providing the telematics data to the remote computing system.

Abstract: Novel tools and techniques are provided for implementing name-based routing through networks. In various embodiments, a broker manager in each of a plurality of networks may receive a subscription request for a network device from a client device, each device being locally accessible or disposed in an upstream or downstream network. The broker manager uses its client broker to communicate with a locally accessible client device, and uses its mediator broker (and, sometimes, an intermediate device(s)) to communicate with a locally accessible network device. The broker manager otherwise uses its messaging brokers to communicate with control channels of one or more networks. Once subscription with the network device has been established, any commands and responses between the client device and the network device may be routed over pub/sub channels via the broker managers and their brokers using name-based routing, without routing based on IP address of the network device.

Abstract: A method of training a supervised machine learning system to detect anomalies within transaction data is described. The method includes obtaining a training set of data samples; assigning a label indicating an absence of an anomaly to unlabelled data samples in the training set; partitioning the data of the data samples in the training set into two feature sets, a first feature set representing observable features and a second feature set representing context features; generating synthetic data samples by combining features from the two feature sets that respectively relate to two different uniquely identifiable entities; assigning a label indicating a presence of an anomaly to the synthetic data samples; augmenting the training set with the synthetic data samples; and training a supervised machine learning system with the augmented training set and the assigned labels.

Abstract: Novel tools and techniques are provided for implementing real-time fault management or real-time fault management system (“RFM”). In various embodiments, RFM may receive alerts from or associated with network devices (e.g., layer 2, 3, and/or 4 devices, or the like) that are disposed in a plurality of disparate networks that may utilize different alert management protocols and/or different fault management protocols. RFM may collect, enrich, normalize, aggregate, and display the alerts in a user interface to facilitate addressing of the alerts by a user. To enable continuous and real-time functionality, RFM may be implemented in a plurality of siloed platforms in a primary data center, with processing of alerts being load balanced across the siloed platforms, with mirrored group of siloed platforms in a secondary data center located geographically distant from the primary data center and configured to be on “hot standby” and to completely take over RFM processing operations.

Abstract: Various measures to preserve privacy and to train neural network models are provided. A federated learning system comprises a payment decisioning server associated with a payment decisioning entity and a financial institution server associated with a financial institution. A transaction involves a customer of the financial institution. In an example method, the payment decisioning server transmits, to the financial institution server, a query relating to the customer. In the example method, the payment decisioning server receives, from the financial institution server, a response to the query, the response comprising an account embedding, the account embedding having been derived by the financial institution server using account information associated with the customer as input to a financial institution private embedding model.

Abstract: An article is provided for use with an apparatus for heating smokable material to volatilize at least one component of the smokable material. The article has a carrier and smokable material arranged on the carrier. The smokable material has a first layer of smokable material and a second layer of smokable material. The first layer of smokable material is located between the carrier and the second layer of smokable material. The smokable material of the first layer of smokable material has a form or chemical composition that differs from the form or chemical composition, respectively, of the smokable material of the second layer of smokable material.

Abstract: Processing a digital bit stream and systems for implementing the methods are provided. The method includes dividing the digital bit stream into a plurality of data packets. In a first processing block performing a carrier recovery error calculation on a first portion of the plurality of data packets, comprising preforming a first phase locked loop (PLL) function on decimated data of the data packets and performing a carrier recovery operation on the first portion of the plurality of data packets. In a second processing block, in parallel with the processing of the first portion of the plurality of packets, performing the carrier recovery error calculation on a second portion of the plurality of data packets, comprising preforming the first PLL function on decimated data of the data packets and performing the carrier recovery operation on second portion of the plurality of data packets.

Abstract: Novel tools and techniques are provided for implementing name-based routing through networks. In various embodiments, a broker manager in each of a plurality of networks may receive a subscription request for a network device from a client device, each device being locally accessible or disposed in an upstream or downstream network. The broker manager uses its client broker to communicate with a locally accessible client device, and uses its mediator broker (and, sometimes, an intermediate device(s)) to communicate with a locally accessible network device. The broker manager otherwise uses its messaging brokers to communicate with control channels of one or more networks. Once subscription with the network device has been established, any commands and responses between the client device and the network device may be routed over pub/sub channels via the broker managers and their brokers using name-based routing, without routing based on IP address of the network device.

Abstract: An autonomous surface vessel includes an elongate body, and a sampling system operatively coupled to the body and including one or more sampling modules, wherein each sampling module includes a housing including a storage container, a sampling material receivable within the storage container, an actuation system operatively coupled to the sampling material via a lead line, and an end cap operatively coupled to the lead line and matable with an open end of the storage container. A computer system is in communication with the sampling system to operate the actuation system, wherein each sampling module is actuatable between a stowed state, where the sampling material is received within the storage container and the end cap sealingly engages the open end, and a deployed state, where the end cap is disengaged from the open end and the sampling material is drawn out of the sampling container.

Abstract: Novel tools and techniques are provided for implementing name-based routing through networks. In various embodiments, a broker manager in each of a plurality of networks may receive a subscription request for a network device from a client device, each device being locally accessible or disposed in an upstream or downstream network. The broker manager uses its client broker to communicate with a locally accessible client device, and uses its mediator broker (and, sometimes, an intermediate device(s)) to communicate with a locally accessible network device. The broker manager otherwise uses its messaging brokers to communicate with control channels of one or more networks. Once subscription with the network device has been established, any commands and responses between the client device and the network device may be routed over pub/sub channels via the broker managers and their brokers using name-based routing, without routing based on IP address of the network device.

Abstract: A graphical user interface for displaying an electronic medical record associated with a patient is provided. The graphical user interface may include an area configured to display patient information, which may include at least a name of the patient. The graphical user interface may also include an indicator displayed in association with the name of the patient. The indicator may include information specifying that the patient is potentially eligible for one or more trials, the patient is participating in one or more trials, or the patient has completed one or more trials.

Abstract: A machine learning system for processing data corresponding to an incoming transaction. The machine learning system comprises a categorical history module which includes a memory configured to store state data for a plurality of categories indexed by a respective category identifier, wherein the state data stored in the memory for each category identifier corresponds to a previous transaction associated with the entity and the respective category. A decay logic stage is configured to modify state data stored in the memory based on a time difference between a time of the incoming transaction and a time of a previous transaction. When the memory contains state data for the entity and category identifier pair associated with the incoming transaction, a decaying function dependent on the time difference is applied to the stored state data to generate a decayed version.

Abstract: Technologies for determining healthcare relationships include a healthcare insight computing device communicatively coupled to multiple patient data providers. The healthcare insight computing device is configured to determine one or more relationships between received data and previously received patient data associated with one or more patients. The healthcare insight computing device is further configured to correlate the ingested data as a function of the determined relationships and enrich the correlated patient data to form a new data element. Additionally, the healthcare insight computing device is configured to transmit the new data element to a raw data cluster such that visual representations of the data elements of the raw data cluster and the relationships there between can be displayed. Additional embodiments are described herein.

Abstract: Novel tools and techniques are provided for implementing name-based routing through networks. In various embodiments, a broker manager in each of a plurality of networks may receive a subscription request for a network device from a client device, each device being locally accessible or disposed in an upstream or downstream network. The broker manager uses its client broker to communicate with a locally accessible client device, and uses its mediator broker (and, sometimes, an intermediate device(s)) to communicate with a locally accessible network device. The broker manager otherwise uses its messaging brokers to communicate with control channels of one or more networks. Once subscription with the network device has been established, any commands and responses between the client device and the network device may be routed over pub/sub channels via the broker managers and their brokers using name-based routing, without routing based on IP address of the network device.

Abstract: Novel tools and techniques are provided for implementing software-based network probes for monitoring network devices for fault management. In various embodiments, a computing system may receive, from at least one software-based network probe, a first alert associated with a first device among layer 4 devices disposed in a plurality of networks; may parse and store first alert data from the received first alert in a database, in a standardized format; may perform, using an enrichment system, enrichment of the first alert data, by retrieving first enrichment data from one or more second databases and adding the first enrichment data to the parsed and formatted first alert data in the first database to form first consolidated alert data; and may send the first consolidated alert data to a fault management system for display to a user to facilitate addressing of the first alert by the user.

Abstract: Novel tools and techniques are provided for implementing global Internet Protocol management system (“GIMS”) for monitoring network devices for fault management. In various embodiments, a computing system may receive a first alert associated with a first device among layer 2 and/or layer 3 devices disposed in a plurality of networks; may collect first alert data and/or first device data; may store the first alert together with the collected first alert data and/or first device data as first consolidated alert data in a first database; may perform, using an enrichment system, enrichment of the first alert, by retrieving first enrichment data from one or more second databases and adding the first enrichment data to the first consolidated alert data in the first database; and may send the first consolidated alert data to a fault management system for display to a user to facilitate addressing of the first alert by the user.

Abstract: Novel tools and techniques are provided for implementing name-based routing through networks. In various embodiments, a broker manager in each of a plurality of networks may receive a subscription request for a network device from a client device, each device being locally accessible or disposed in an upstream or downstream network. The broker manager uses its client broker to communicate with a locally accessible client device, and uses its mediator broker (and, sometimes, an intermediate device(s)) to communicate with a locally accessible network device. The broker manager otherwise uses its messaging brokers to communicate with control channels of one or more networks. Once subscription with the network device has been established, any commands and responses between the client device and the network device may be routed over pub/sub channels via the broker managers and their brokers using name-based routing, without routing based on IP address of the network device.

Abstract: Novel tools and techniques are provided for implementing name-based routing through networks. In various embodiments, a broker manager in each of a plurality of networks may receive a subscription request for a network device from a client device, each device being locally accessible or disposed in an upstream or downstream network. The broker manager uses its client broker to communicate with a locally accessible client device, and uses its mediator broker (and, sometimes, an intermediate device(s)) to communicate with a locally accessible network device. The broker manager otherwise uses its messaging brokers to communicate with control channels of one or more networks. Once subscription with the network device has been established, any commands and responses between the client device and the network device may be routed over pub/sub channels via the broker managers and their brokers using name-based routing, without routing based on IP address of the network device.

Abstract: Novel tools and techniques are provided for implementing real-time fault management or real-time fault management system (“RFM”). In various embodiments, RFM may receive alerts from or associated with network devices (e.g., layer 2, 3, and/or 4 devices, or the like) that are disposed in a plurality of disparate networks that may utilize different alert management protocols and/or different fault management protocols. RFM may collect, enrich, normalize, aggregate, and display the alerts in a user interface to facilitate addressing of the alerts by a user. To enable continuous and real-time functionality, RFM may be implemented in a plurality of siloed platforms in a primary data center, with processing of alerts being load balanced across the siloed platforms, with mirrored group of siloed platforms in a secondary data center located geographically distant from the primary data center and configured to be on “hot standby” and to completely take over RFM processing operations.