The present disclosure is directed to a scalable, extensible, fault-tolerant system for stateful joining of two or more streams that are not fully synchronized, event ordering is not guaranteed, and certain events arrive a bit late. The system can ensure to combine the events or link the data in near real-time with low latency to mitigate impacts on downstream applications, such as ML models for determining suspicious behavior. Apart from combining events, the system can ensure to propagate the needed entities to other product streams or help in entity resolution. If any of the needed data is yet to arrive, a user can configure a few parameters to achieve desired eventual and attribute consistency. The architecture is designed to be agnostic of stream processing framework and can work well with both streaming and batch paths.

A system and method for securing authenticated patient communication through a device that is able to trigger a patient related event through a simple online communication process. The trigger(s) determined by the device are preferably controlled through a separate application, which may be controlled through a medical user computational device and/or a server. The separate application sets the one or more triggers accessible to the device and also determines one or more conditions for activating the one or more triggers. Upon detection of one or more conditions by the device, one or more triggers are activated. The medical user computational device receives a notification of the activation of the trigger. The medical user computational device may modify the trigger, the activation of the trigger or the one or more downstream actions which occur upon activation of the trigger. Such modification may occur before activation of the trigger or after activation of the trigger. The trigger causes a patient related action to be taken, for example to call the patient back on a separate telephonic device. Preferably the device features a plurality of buttons or other simple, easy to use initiators. Each initiator preferably activates a trigger.

It is made possible to realize bidirectional communication safely on the cloud side, and on-premises side in a job execution system.

It is checked whether or not there is an agent with the same logical name at time of agent registration. In a case that there is the same logical name, transfer performance required of each agent is checked, and communication is performed by rewriting a logical name during transfer by using an existing logical name for an agent required of the highest transfer performance, and using a logical name which is a new unique alias for the other agent.

It is made possible to realize bidirectional communication safely on the cloud side, and on-premises side in a job execution system.

It is checked whether or not there is an agent with the same logical name at time of agent registration. In a case that there is the same logical name, transfer performance required of each agent is checked, and communication is performed by rewriting a logical name during transfer by using an existing logical name for an agent required of the highest transfer performance, and using a logical name which is a new unique alias for the other agent.

A communication apparatus comprises a TCP terminating part that terminates TCP communication with an apparatus of data transmission destination, a monitoring part that monitors network status of the apparatus of data transmission destination on a per-session basis, and a transferring rate controlling part that changes size of a transmission buffer that is adopted to the session based on the network status.

Systems and methods for configuring and launching a marketplace are described. A method may include identifying an opportunity for a new marketplace, receiving marketplace opportunity data, determining configuration parameters, and determining a feasibility of implementing the new marketplace configuration. An architecture of the new marketplace may be determined, and marketplace objects configured. Data resources and their configuration in a model may be determined and the data resources connected to marketplace objects. The new marketplace may then be launched.

A transaction management platform may partition an amount associated with a group service plan into a plurality of portions. The transaction management platform may provide a graphical user interface to a primary user device of the plurality of user devices. The transaction management platform may receive, from the primary user device, a request for a transaction associated with a portion of the plurality of portions. The portion may be attributable to a secondary user device of the plurality of user devices. The transaction management platform may provide to the secondary user device of the plurality of user devices a unique link that has been generated based on one or more parameters and that enables the secondary user device to complete the transaction. Based on the secondary user device completing the transaction, the transaction management platform may process the transaction to provide an updated amount.

In order to allow for improvement on a case where data of a cellular network is transmitted and/or received through a wireless local area network (WLAN), a base station of the present invention includes: a first communication processing unit configured to add a header of a framing protocol to downlink data transmitted to a terminal apparatus; and a second communication processing unit configured to transmit the downlink data to which the header is added to a gateway that is used for transmission from the base station to the terminal apparatus through a wireless local area network. The framing protocol is a protocol for communication between the base station and the gateway and the header includes identification information corresponding to quality of service for the downlink data.

A remote node device including a hardware layer, a hardware abstraction layer, and a software stack operating on the hardware abstraction layer. The software stack including an open-source cloud-based operating system integrated with a service provider defined abstraction layer configured to coordinate functionality of the software stack, virtualized software components such as a virtualized Converged Cable Access Platform (vCCAP) implemented in docker containers where the vCCAP is configured to command and control the remote node device with respect to a customer premise equipment. The software layer of the remote node device includes different types of YANG data models for model-driven management and model-driven telemetry from the remote node device and a customer premise equipment to a service provider back-office system.

A remote node device including a hardware layer, a hardware abstraction layer, and a software stack operating on the hardware abstraction layer. The software stack including an open-source cloud-based operating system integrated with a service provider defined abstraction layer configured to coordinate functionality of the software stack, virtualized software components such as a virtualized Converged Cable Access Platform (vCCAP) implemented in docker containers where the vCCAP is configured to command and control the remote node device with respect to a customer premise equipment. The software layer of the remote node device includes different types of YANG data models for model-driven management and model-driven telemetry from the remote node device and a customer premise equipment to a service provider back-office system.