Patent classifications
H04L41/02
Device configuration method and apparatus that are based on network configuration protocol
A device configuration method, apparatus, and system based on Network Configuration Protocol (NETCONF), and belong to the field of communications technologies. The method includes establishing, by a network management device, a model of configuration data using a predefined Yet Another Next Generation (YANG) model, and sending the configuration data to a managed device based on NETCONF. The predefined YANG model includes n reference fields and one or more object fields separately corresponding to each reference field. Hence, resolves problems that when an extension field is added to a NETCONF message to indicate a target lower-level device of configuration data in the NETCONF message in a device cascading scenario, solution universality is relatively poor, configuration processing efficiency is relatively low, and a data storage processing procedure is relatively complex.
SERVICE LAYER RESORCE MANAGEMENT FOR GENERIC INTERWORKING AND EXTENSIBILITY
Lightweight, dynamic mechanisms are provided to support service layer interworking and resource extensibility. For example, one mechanism disclosed herein comprises defining a new service layer (SL) resource definition registration procedure that allows for specifying custom attributes of service layer resources to represent third party technology resources. A second mechanism disclosed herein comprises defining a new SL data model mapping registration procedure to map service layer resources to third party data models and to provide a new interworked retargeting indicator to the service layer. Further, a third mechanism disclosed herein comprises defining a SL generic interworking procedure to intelligently retarget requests toward interworked resources based on the interworked retargeting indicator provided by the data model mapping.
SERVICE LAYER RESORCE MANAGEMENT FOR GENERIC INTERWORKING AND EXTENSIBILITY
Lightweight, dynamic mechanisms are provided to support service layer interworking and resource extensibility. For example, one mechanism disclosed herein comprises defining a new service layer (SL) resource definition registration procedure that allows for specifying custom attributes of service layer resources to represent third party technology resources. A second mechanism disclosed herein comprises defining a new SL data model mapping registration procedure to map service layer resources to third party data models and to provide a new interworked retargeting indicator to the service layer. Further, a third mechanism disclosed herein comprises defining a SL generic interworking procedure to intelligently retarget requests toward interworked resources based on the interworked retargeting indicator provided by the data model mapping.
NETWORK DATA MANAGEMENT FRAMEWORK
A method includes receiving a plurality of inputs comprising data corresponding to a plurality of network elements, confirming presence of a given network element of the plurality of network elements on at least one network, and adding the given network element to a network element database. The method also includes interfacing with one or more network integration services of a plurality of network integration services to receive data corresponding to the given network element. The network element database is automatically updated with the received data, and the interfacing is performed via a message bus.
Systems and methods for managing on-site communications for latency-dependent applications
The present disclosure is directed to systems and methods for managing on-site communications of a machine with a latency-dependent application installed. The method includes, for example, (i) receiving geographical information associated with a work site; (ii) receiving historical communications information associated with the work site; (iii) analyzing the historical communications information and the geographical information; (iv) generating an instruction for implementing the latency-dependent application of the machine based on a latency requirement of the latency-dependent application; and (v) implementing the latency-dependent application of the machine based on the instruction. The historical communications information includes a communications event, a duration of the communications event, and a frequency of the communications event.
Systems and methods for managing on-site communications for latency-dependent applications
The present disclosure is directed to systems and methods for managing on-site communications of a machine with a latency-dependent application installed. The method includes, for example, (i) receiving geographical information associated with a work site; (ii) receiving historical communications information associated with the work site; (iii) analyzing the historical communications information and the geographical information; (iv) generating an instruction for implementing the latency-dependent application of the machine based on a latency requirement of the latency-dependent application; and (v) implementing the latency-dependent application of the machine based on the instruction. The historical communications information includes a communications event, a duration of the communications event, and a frequency of the communications event.
Web services for smart entity management for sensor systems
One or more non-transitory computer readable media contain program instructions that, when executed by one or more processors, cause the one or more processors to perform operations including generating a database of interconnected smart entities. The smart entities include sensor object entities representing each of the plurality of sensors and data entities representing measurements received from the sensors. The smart entities are interconnected by relational objects indicating relationships between the smart entities. The instructions cause the one or more processors to receive a new measurement from a first sensor, identify a first data entity from a relational object for the first sensor, the first data entity including a plurality of past measurements received from the first sensor, and modify the first data entity within the database of smart entities to include the new measurement received from the first sensor.
STRUCTURED DATA DISCOVERY AND CRYPTOGRAPHIC ANALYSIS
Structured Data Discovery and Cryptographic Analysis. In an embodiment, transport sessions are assembled from raw packets captured in network traffic. Data is extracted from two or more encapsulation layers of each transport session. In particular, each encapsulation layer may be classified into a protocol, and data may be extracted from the encapsulation layer based on the protocol. For example, cryptographic metadata may be extracted from a cryptographic encapsulation layer. The extracted data is incorporated into a data model of the network, which comprises tallies of traffic within the network, grouped according to a plurality of dimensions. Analytic model(s) may be applied to the data model to, for example, generate a data web of the network that represents structured data stores and data flows to and/or from the data stores within the network.
Web services for creation and maintenance of smart entities for connected devices
One or more non-transitory computer readable media containing program instructions that, when executed by one or more processors, cause the one or more processors to perform operations: generating a database of interconnected smart entities, the smart entities including object entities representing each of the plurality of physical devices and data entities representing data generated by the devices, the smart entities being interconnected by relational objects indicating relationships between the object entities and the data entities; receiving data from a first device of the plurality of physical devices; determining a second device from a relational object for the first device based on the received data; and modifying a data entity connected to an object entity of the second device within the database of smart entities based on the received data for the first device.
Message queue architecture and interface for a multi-application platform
Non-volatile memory may contain definitions of: (i) a plurality of message queue implementations respectively associated with different queue behaviors, the different queue behaviors specified by corresponding sets of modes, and (ii) an application programming interface (API) through which applications can access one or more message queues. One or more processors may be configured to: create a message queue of a particular message queue type, supported by a corresponding message queue implementation, by specifying a set of modes corresponding to a queue behavior; receive, from a producing application and by way of the API, one or more messages for the message queue; store the one or more messages in a data structure associated with the message queue; receive, from a consuming application and by way of the API, a request to read from the message queue; and provide a message from the message queue to the consuming application.