Patent classifications
H04L45/306
Mesh-based home security system
A network management system manages the operation of a home security system in a communication network, such as a mesh network. The home security system can include multiple components such as a camera, a lighting device, a security alarm, a doorbell switch and doorbell chime, and a fingerprint sensor, which connect with the communication network to perform various operations. The network management system monitors environmental parameters of the communication network, such as parameters associated with the access points and components of the home security system, determines an access point to which a component of the home security system is to be connected for efficient operation of the home security system, and connects the component to the communication network via the determined access point.
Multi-sensor motion detection
Use of multiple sensors to determine whether motion of an object is occurring in an area is described. In one aspect, an infrared (IR) sensor can be supplemented with a radar sensor to determine whether the determined motion of an object is not a false positive.
Smart cascading security functions for 6G or other next generation network
In a 6G network, microservices can be utilized in the absence of a core network. For example, after a mobile device has authenticated, through its carrier network, with a transport service layer, microservices can be allocated to the mobile device without having to be transmitted via the core network. Thus, removing the core network from the process can generate a direct line of microservices from the transport layer to the end-user. Furthermore, additional microservices and/or resources can be access through a microservices library. Consequently, packets can be securely transmitted be a wireless network facilitating sending packet profile data from one to many node devices in anticipation of the packet traversing the various node devices.
Customizable router for managing traffic between application programming interfaces
A customizable router manages traffic between application programming interfaces (APIs) of microservice applications (apps) that make up various features of a website. Various datastores may also be used to store information, such as information related to certain products, pricing, users, etc. In order for the website to function properly, the microservice apps communicate with one another and with the datastores. The customizable router is used to manage and route traffic between the microservice apps and/or datastores. The customizable router may, for example, route a universal resource indicator (URI) request for a webpage of a website to particular versions or revisions of a microservice app based on rules established for the customizable router. For example, a certain percentage of traffic may be routed to a first version of a microservice app, while a different percentage of traffic may be routed to a second version of the microservice app.
QOS CONFIGURATION UPDATE BASED ON BEHAVIORAL APPLICATION CORRELATION
In one embodiment, a device obtains behavioral metrics for application traffic in a network for a plurality of applications. The device identifies a first application and a second application from among the plurality of applications as fate sharing applications, based on a correlation between the behavioral metrics for their application traffic. The device generates a configuration change for the network that would prevent the first application and the second application from being fate sharing applications, when application traffic for the first application negatively affects the behavioral metrics for the application traffic of the second application. The device causes the configuration change to be implemented in the network.
Packet processing method and system, and device
The application disclose a packet processing method that includes: receiving, by a service distribution node, service routing information sent by a controller, where the service routing information includes a flow identifier, a service identifier, and a next-hop address, the flow identifier is used to identify a packet flow, the service identifier is used to identify a sequence of a service node instance that processes the packet flow, and the next-hop address is used to identify the service node instance that processes the packet flow; receiving a first packet; acquiring a first flow identifier according to the first packet, and searching the service routing information according to the first flow identifier to acquire a matched service identifier and a matched next-hop address; and sending a second packet to a first service node instance that has the matched next-hop address, which implements service processing on a packet flow.
Systems and methods for mapping resource blocks to network slices
A RAN node may determine an aggregate signal-to-noise ratio (SNR) of each resource block of a plurality of resource blocks, where the aggregate SNR of a given resource block of the plurality of resource blocks is based on SNRs of subcarrier frequencies of the given resource block. The RAN node may determine, based on a type of network traffic on each network slice of a plurality of network slices, an index value of each network slice of the plurality of network slices. The RAN node may map, based on the aggregate SNR of each resource block, based on the index value of each network slice, and for each resource block of the plurality of resource blocks, a resource block of the plurality of resource blocks to a network slice of the plurality of network slices.
Implementation of service function chain on basis of software-defined network
Example embodiments of the present disclosure relate to enablement of a service function chain based on a software defined network. In some embodiments, there is provided a method implemented at a service function chain controller. The method comprises creating a service function chain for a packet, the service function chain comprising a set of ordered service functions that are to process the packet; and configuring respective forwarding rules associated with the service function chain directly or indirectly to a plurality of network nodes in a software defined network, the respective forwarding rules indicating how the plurality of network nodes forward the packet to the set of ordered service functions in the service function chain. In this way, it is possible to enable the service function chain in the software defined network.
Mesh-based event broker for distributed computing
A method to broker events of event-driven application components, within a distributed computing environment and using a mesh broker, is described. The mesh broker is instantiated as several mesh agents, the mesh agents being provisioned to support mediation activities relating to a plurality of computational nodes within the distributed computing environment. The mesh agents are further deployed as a mesh network among the computational nodes of the distributed computing environment. A connectivity catalog stores cost data associated with transmission of an event notification between each of multiple pairs of computational nodes of the computational nodes. Routes across the mesh network are automatically selected, by the mesh agents and using the cost data to determine low-cost routes across the mesh network.
Service function chaining network services
The disclosed technology relates to forwarding a packet in a network. The packet is received at a node, where the packet is encapsulated by a network service header (NSH) including a service path header that identifies a service path. The service path is associated with a treatment value that directs subsequent nodes to treat the encapsulated NSH packet with a quality of service treatment. A forwarding table stored in the node is evaluated to identify the service path and the treatment value of the encapsulated NSH packet and a quality of service treatment is determined for the encapsulated NSH packet. The encapsulated NSH packet is forwarded to the subsequent nodes based on the service path indicated in the forwarding table and in accordance with the quality of service treatment corresponding to the treatment value identified in the forwarding table.