A method for communicating in real-time to users of a provider of Internet access service, without requiring any installation or set-up by the user, that utilizes the unique identification information automatically provided by the user during communications for identifying the user to provide a fixed identifier which is then communicated to a redirecting device. Messages may then be selectively transmitted to the user. The system is normally transparent to the user, with no modification of its content along the path. Content then may be modified or replaced along the path to the user. For the purposes of establishing a reliable delivery of bulletin messages from providers to their users, the system forces the delivery of specially-composed World Wide Web browser pages to the user, although it is not limited to that type of data.

A modular surgical system is disclosed that comprises a modular hub and a computer system that includes instructions to retrieve medical records associated with a patient from an EMR database based on a key, delete data associated with the patient's identity from the retrieved medical records, extract relevant patient data from the retrieved medical records, and store an anonymous data file with the extracted relevant patient data by a unique procedure identification number. Within a hospital data barrier, the modular hub is configured to combine the anonymous data file with the patient EMR stored on the EMR database by using the key associated with the patient EMR and the unique procedural identification number associated with the anonymous data file and delete from the modular hub the data associated with the patient's identity to maintain anonymity of the patient.

A modular surgical system is disclosed that comprises a modular hub and a computer system that includes instructions to retrieve medical records associated with a patient from an EMR database based on a key, delete data associated with the patient's identity from the retrieved medical records, extract relevant patient data from the retrieved medical records, and store an anonymous data file with the extracted relevant patient data by a unique procedure identification number. Within a hospital data barrier, the modular hub is configured to combine the anonymous data file with the patient EMR stored on the EMR database by using the key associated with the patient EMR and the unique procedural identification number associated with the anonymous data file and delete from the modular hub the data associated with the patient's identity to maintain anonymity of the patient.

A system, method, and computer readable medium for communicating at least one real-time specially-composed bulletin message to at least one subscriber of a provider of Internet services, comprising a first device, and a second device communicably coupled to the first device, wherein the first device: accesses only subscriber upstream traffic to a destination web site requested by the subscriber, wherein the first device inter-connects between the at least one subscriber and the destination web site, identifies the at least one subscriber's identification based on the accessed subscriber upstream traffic automatically provided by the subscriber, and provides the unique subscriber identification to the second device located at the provider of Internet services providing data services and management control to the first device, wherein the second device determines the subscriber associated with the unique subscriber identification.

An NVMeoF gateway system includes a physical host device that communicates using a host NVMeoF protocol, and a physical target device that communicates using a target NVMeoF protocol. A networking device generates proxy host and target devices that are included in the same zone for the physical host and target devices, respectively. The networking device then converts first host NVMeoF protocol communications from the physical host device to first target NVMeoF protocol communications and provides them to the physical target device using the proxy host device, and converts second target NVMeoF protocol communications from the physical target device to second host NVMeoF protocol communications and provides them to the physical host device using the proxy target device. The first target NVMeoF protocol communications and the second host NVMeoF protocol communications configure the physical host device to exchange data with the physical target device.

An NVMeoF gateway system includes a physical host device that communicates using a host NVMeoF protocol, and a physical target device that communicates using a target NVMeoF protocol. A networking device generates proxy host and target devices that are included in the same zone for the physical host and target devices, respectively. The networking device then converts first host NVMeoF protocol communications from the physical host device to first target NVMeoF protocol communications and provides them to the physical target device using the proxy host device, and converts second target NVMeoF protocol communications from the physical target device to second host NVMeoF protocol communications and provides them to the physical host device using the proxy target device. The first target NVMeoF protocol communications and the second host NVMeoF protocol communications configure the physical host device to exchange data with the physical target device.

Various methods, apparatuses/systems, and media for integrating incompatible open identity connect (OIDC) implementations are disclosed. A processor creates a custom protocol within an API gateway that understands data coming in from the aIDC protocol; receives data from the OIDC protocol; and determines, based on analyzing the data received from the aIDC protocol, any communication gap between an application and an identity layer, wherein the API gateway is implemented between the application and the identity layer. The processor then converts, in response to determining a communication gap, the data received from the aIDC protocol into a formatted data that is understandable by the application; transmits the formatted data to the application; and automatically eliminates any communication gap between the application and the identity layer based on the received formatted data.

Various methods, apparatuses/systems, and media for integrating incompatible open identity connect (OIDC) implementations are disclosed. A processor creates a custom protocol within an API gateway that understands data coming in from the aIDC protocol; receives data from the OIDC protocol; and determines, based on analyzing the data received from the aIDC protocol, any communication gap between an application and an identity layer, wherein the API gateway is implemented between the application and the identity layer. The processor then converts, in response to determining a communication gap, the data received from the aIDC protocol into a formatted data that is understandable by the application; transmits the formatted data to the application; and automatically eliminates any communication gap between the application and the identity layer based on the received formatted data.

The present disclosure discloses a method and system for sharing a multi-protocol port and a server, where a designated field for storing a listening structure is newly added to a listening structure of an HTTP protocol. The method includes: writing, with respect to a target port, a listening structure of an RTMP protocol into the designated field of the HTTP protocol if the HTTP protocol and the RTMP protocol share the target port; detecting a target protocol corresponding to a connection request when the connection request is received by the target port; and reading the listening structure of the RTMP protocol from the designated field to obtain configuration information of the RTMP protocol if the target protocol is the RTMP protocol, and processing the connection request using the configuration information of the RTMP protocol.

Examples described herein relate to apparatuses and methods for managing caching for a content delivery system, which may include receiving a content request indicating that the caching agent is requesting content data for a client, filling the content data in a first cache storage of the business logic agent, providing the cached content data to the caching agent, and while a second cache storage of the caching agent is being filled with the content data, maintaining the cached content data in response to receiving additional content requests from the caching agent. The additional content requests may indicate that the caching agent is requesting the same content data for additional clients.