Patent classifications
H04L41/0233
Apparatus for transmitting broadcast signals, apparatus for receiving broadcast signals, method of transmitting broadcast signals and method of receiving broadcast signals
The present invention proposes a method for providing a broadcast content in an apparatus, the method comprising: requesting a filter code to an application running on the apparatus by using a first Application Programming Interface (API); receiving a JavaScript Object Notation (JSON) object from the application in response to the first API; storing the filter code; receiving an Extended File Delivery Table (EFDT) having a first filter code associated with a first file; and selectively downloading the first file by comparing the stored filter code with the first filter code in the EFDT.
Apparatus for transmitting broadcast signals, apparatus for receiving broadcast signals, method of transmitting broadcast signals and method of receiving broadcast signals
The present invention proposes a method for providing a broadcast content in an apparatus, the method comprising: requesting a filter code to an application running on the apparatus by using a first Application Programming Interface (API); receiving a JavaScript Object Notation (JSON) object from the application in response to the first API; storing the filter code; receiving an Extended File Delivery Table (EFDT) having a first filter code associated with a first file; and selectively downloading the first file by comparing the stored filter code with the first filter code in the EFDT.
Multi-tenant event sourcing and audit logging in a cloud-based computing infrastructure
Examples described herein include systems and methods for multi-tenant event sourcing and audit logging in a cloud-based computing infrastructure. In an example method, an event package can be received from a first microservice of an application. The event can describe any action performed within the computing infrastructure and can include various types of information. For example, it can include an event type, event ID, object type, object ID, and parent event ID. The event package can be associated with a tenant and only provided to tenant-approved recipients. The recipient can use the event package to automatically carry out steps to recreate and configure an object, or to determine the source of an event or failure within the system.
Multi-tenant event sourcing and audit logging in a cloud-based computing infrastructure
Examples described herein include systems and methods for multi-tenant event sourcing and audit logging in a cloud-based computing infrastructure. In an example method, an event package can be received from a first microservice of an application. The event can describe any action performed within the computing infrastructure and can include various types of information. For example, it can include an event type, event ID, object type, object ID, and parent event ID. The event package can be associated with a tenant and only provided to tenant-approved recipients. The recipient can use the event package to automatically carry out steps to recreate and configure an object, or to determine the source of an event or failure within the system.
Techniques for interfacing between web services and interface description language (IDL)-based remote procedure call (RPC) services and an optical communication system implementing same
An embodiment of the present disclosure includes an RPC architecture that includes a central manager gateway with a client-facing side that allows for client access via web services protocols such as SOAP and REST. The central manager gateway further includes a server-facing side that can communicate with a plurality of network elements, with each network element implementing a common IDL architecture and RPC manager instance. Each of the network elements, and in particular their RPC manager instance, may communicate with other RPC manager instances to ‘learn’ the network topology for the system and maintain a topology database for purposes of exposing a naming service, e.g., a CORBA naming service. The network elements may elect one master element while the others remain as slaves. The central manager gateway may automatically locate the master network element and forward client requests to the same for servicing.
Techniques for interfacing between web services and interface description language (IDL)-based remote procedure call (RPC) services and an optical communication system implementing same
An embodiment of the present disclosure includes an RPC architecture that includes a central manager gateway with a client-facing side that allows for client access via web services protocols such as SOAP and REST. The central manager gateway further includes a server-facing side that can communicate with a plurality of network elements, with each network element implementing a common IDL architecture and RPC manager instance. Each of the network elements, and in particular their RPC manager instance, may communicate with other RPC manager instances to ‘learn’ the network topology for the system and maintain a topology database for purposes of exposing a naming service, e.g., a CORBA naming service. The network elements may elect one master element while the others remain as slaves. The central manager gateway may automatically locate the master network element and forward client requests to the same for servicing.
Systems and methods for data linkage and entity resolution of continuous and un-synchronized data streams
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.
Systems and methods for data linkage and entity resolution of continuous and un-synchronized data streams
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.
NETWORK MANAGEMENT APPARATUS, METHOD, AND PROGRAM
A network management apparatus according to an embodiment includes: a storage device configured to store information indicating a correspondence relationship between information objects related to a logical layer, information objects related to a physical layer in a network configuration, and information objects related to a facility layer which are objects in which the information objects related to the physical layer are housed; an acquisition unit configured to acquire an information object related to an occurrence path of a failure in the logical layer of the network configuration, from the storage device; and a search unit configured to search for, among the information objects related to the facility layer stored in the storage device, an information object related to the facility layer and the physical layer associated with the information object related to the occurrence path of the failure acquired from the acquisition unit, as a candidate for a facility that causes the failure.
Systems and methods for managed services provisioning using service-specific provisioning data instances
A technical solution for an electronic information exchange platform is disclosed. Services provided by the platform may be described in a uniform way via service-specific provisioning descriptors. To provision services for a client system, a managed services provisioning system provides a service configuration interface through which a service associated with a tuple of a particular sender, receiver, and document type can be selected for further configuration. A service provisioning interface is dynamically generated for obtaining service-specific provisioning information from a user for generating a service-specific provisioning data instance that can be deployed to a backend system. At runtime, the backend system utilizes the service-specific provisioning data instance to provide the provisioned service for a client system. In this way, a variety of services can be efficiently provisioned for a diverse set of clients in a scalable, streamlined, and cost-effective manner.