Patent classifications
H04L67/2871
METHOD AND SYSTEM FOR SHARING MULTI-PROTOCOL PORT, AND SERVER
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.
Service processing method and apparatus of service-based architecture
This application provides a service processing method and apparatus of a service-based architecture. In the method, a service customer sends a service query request to a network element repository function entity NRF; the NRF receives the service query request, determines a service address of a service proxy that matches a service requested by the service query request, and sends the service address of the service proxy to the service customer; the service customer receives the service address of the service proxy that matches the service requested by the service query request; the service customer sends a service request to the service proxy corresponding to the service address, and establishes a service channel with the service proxy corresponding to the service address. No service function of a service provider needs to be optimized, so that impact on an original service of the service provider can be avoided to some extent.
Service processing method and apparatus of service-based architecture
This application provides a service processing method and apparatus of a service-based architecture. In the method, a service customer sends a service query request to a network element repository function entity NRF; the NRF receives the service query request, determines a service address of a service proxy that matches a service requested by the service query request, and sends the service address of the service proxy to the service customer; the service customer receives the service address of the service proxy that matches the service requested by the service query request; the service customer sends a service request to the service proxy corresponding to the service address, and establishes a service channel with the service proxy corresponding to the service address. No service function of a service provider needs to be optimized, so that impact on an original service of the service provider can be avoided to some extent.
Proxy callback interface supporting multiple webhook channels
In an example, a proxy server includes a proxy callback interface supporting a plurality of webhook channels, each channel of the plurality of webhook channels being identified by a respective webhook channel address. The proxy callback interface receives a webhook call, the webhook call including a specific webhook channel address identifying a specific webhook channel, and payload callback data. The proxy server also includes a database interface to store a callback record that includes the payload callback data in a proxy server database. The proxy server also includes a query interface to receive a callback query, the callback query identifying the specific webhook channel address. The query interface further identifies a plurality of callback records, associated with the specific webhook channel address, that were stored within the proxy server database subsequent to receipt of a previously-received callback query, and returns the plurality of callback records, responsive to the callback query.
Proxy callback interface supporting multiple webhook channels
In an example, a proxy server includes a proxy callback interface supporting a plurality of webhook channels, each channel of the plurality of webhook channels being identified by a respective webhook channel address. The proxy callback interface receives a webhook call, the webhook call including a specific webhook channel address identifying a specific webhook channel, and payload callback data. The proxy server also includes a database interface to store a callback record that includes the payload callback data in a proxy server database. The proxy server also includes a query interface to receive a callback query, the callback query identifying the specific webhook channel address. The query interface further identifies a plurality of callback records, associated with the specific webhook channel address, that were stored within the proxy server database subsequent to receipt of a previously-received callback query, and returns the plurality of callback records, responsive to the callback query.
Systems and methods for establishing highly secure and resilient persistent communication connections
Systems and methods for providing resilient persistent connections for communication are disclosed. Methods include identifying, at a first device, a second device registered with a client connection service; obtaining, from the client connection service, a first resource identifier for delivering request messages to the second device via the client connection service; identifying, based on the obtained first resource identifier, a first target resource for a first request message directed to the second device, wherein the first target resource specifies a first host included in the client connection service; sending, to the client connection service via the data communication network, the first request message to the first target resource for delivery to the second device by the client connection service; and receiving, from the client connection service via the data communication network, a first response message provided by the second device as a response to the first request message.
Communication hub and storage device for storing parameters and status of a surgical device to be shared with cloud based analytics systems
Various surgical hubs are disclosed. A surgical hub comprises a storage device; a processor coupled to the storage device; and a memory coupled to the processor. The memory stores instructions executable by the processor to: receive data from a surgical instrument coupled to the surgical hub; and determine a rate at which to transfer the data from the surgical hub to a remote cloud-based medical analytics network based on available storage capacity of the storage device.
METHOD AND SYSTEM FOR CHANGING THE BEHAVIOR OF A CONNECTED FIELD DEVICE
A method and a system for programming one or more behavior of a field device connected to a network comprising an input programming language to define the one or more behaviors to create an input program, transmitting over the network the input program to a translator coupled to the field device, translating the input program to generate a field program comprising a plurality of tasks and executing said field program by an executor coupled to said field device.
EDGE COMMUNICATION LOCATIONS
Methods, systems, and computer programs are presented for lowering network latency for cloud-based services. Service-delivery edge locations allow customers to improve communication-providers public and private network connectivity for improved performance. One method includes operations for performing, by an edge server, a handshake to establish a communication session between a client and a main server, and for exchanging data between the client and the main server via the edge server. The handshake includes exchanging, by the edge server, communication initiation messages with the client, and validating, by the edge server, authentication credentials for the communication session based on the communication initiation messages. The exchanging data comprises forwarding, by the edge server, data requests from the client to the main server through a private connection between the edge server and the main server, and forwarding, by the edge server, data responses from the main server to the client through the private connection.
Smart routing
Techniques are provided for intelligent routing to a node in a network, such as a transport computer. A gateway server may receive authorization requests from a resource provider computer. There may be multiple potential transport computers to which to potentially route the authorization requests, depending on relationships established between the parties. A routing decision may be made automatically based on real-time network measurements and/or static rules. Real-time network measurements may be obtained by monitoring transport computers for failures, delays, or other undesirable activity. The routing decisions may further be based on expected volumes (e.g., based on analysis of historical spikes in volume). The routing decisions may further be based on user-configured rules and preferences, received via a routing administration interface.