A distribution of a content selection being distributed throughout a wireless mesh network may be tracked. A wireless device in the wireless mesh network enables the content selection to be exchanged. Wireless devices then exchange the content, and a network topology is recorded in response. Finally, the network topology is reported to a reporting agent.

In exemplary embodiments of the present invention, a router determines whether or not to establish a stateful routing session based on the suitability of one or more candidate return path interfaces. This determination is typically made at the time a first packet for a new session arrives at the router on a given ingress interface. In some cases, the router may be configured to require that the ingress interface be used for the return path of the session, in which case the router may evaluate whether the ingress interface is suitable for the return path and may drop the session if the ingress interface is deemed by the router to be unsuitable for the return path. In other cases, the router may be configured to not require that the ingress interface be used for the return path, in which case the router may evaluate whether at least one interface is suitable for the return path and drop the session if no interface is deemed by the router to be suitable for the return path.

In exemplary embodiments of the present invention, a router determines whether or not to establish a stateful routing session based on the suitability of one or more candidate return path interfaces. This determination is typically made at the time a first packet for a new session arrives at the router on a given ingress interface. In some cases, the router may be configured to require that the ingress interface be used for the return path of the session, in which case the router may evaluate whether the ingress interface is suitable for the return path and may drop the session if the ingress interface is deemed by the router to be unsuitable for the return path. In other cases, the router may be configured to not require that the ingress interface be used for the return path, in which case the router may evaluate whether at least one interface is suitable for the return path and drop the session if no interface is deemed by the router to be suitable for the return path.

A network device may receive a message. The network device may determine that the message includes return information indicating a path to an initial device that generated the message. The network device may modify the message by adding an upstream device identifier, wherein the upstream device identifier identifies a device from which the message is received. The network device may modify the message by adding an indication of whether the initial device is reachable by the network device using a segment identifier. The network device may provide the modified message to a downstream device.

Embodiments of this application provide a data processing method and apparatus. The method includes: parsing, by a user plane data processing network element, a received packet and determining first service type information of a data flow to which the packet belongs; obtaining, by the user plane data processing network element, second service type information of the data flow from a data analysis network element; and processing, by the user plane data processing network element, the data flow based on the first service type information and the second service type information. With the data processing method and apparatus disclosed herein, accuracy in identifying a service type of transmitted data can be improved.

In one embodiment, a device obtains routing forecasts for a software defined network. The device splits a particular routing policy for the software defined network into two or more routing policies, based on the routing forecasts. The device makes an evaluation as to whether the two or more routing policies should be reverted back into the particular routing policy. The device sends, to a user interface, data indicative of the particular routing policy that was split into the two or more routing policies and the evaluation as to whether the two or more routing policies should be reverted back into the particular routing policy.

The present technology pertains to a group-based network policy using Segment Routing over an IPv6 dataplane (SRv6). After a source application sends a packet, an ingress node can receive the packet, and if the source node is capable, it can identify an application policy and apply it. The ingress node indicates that the policy has been applied by including policy bits in the packet encapsulation. When the packet is received by the egress node, it can determine whether the policy was already applied, and if so, the packet is forward to the destination application. If the egress node determines that the policy has not be applied the destination application can apply the policy. Both the ingress node and egress nodes can learn of source application groups, destination application groups, and applicable policies through communication with aspects of the segment routing fabric.

In one embodiment, a device obtains routing forecasts for a software defined network. The device splits a particular routing policy for the software defined network into two or more routing policies, based on the routing forecasts. The device makes an evaluation as to whether the two or more routing policies should be reverted back into the particular routing policy. The device sends, to a user interface, data indicative of the particular routing policy that was split into the two or more routing policies and the evaluation as to whether the two or more routing policies should be reverted back into the particular routing policy.

In service flow capability updating in a guaranteed bandwidth multicast network may be provided. First, a node may determine that a bandwidth requirement of a flow has changed to a new bandwidth value. Then, in response to determining that the bandwidth requirement of the flow has changed to the new bandwidth value, an ingress capacity value may be updated in an interface usage table for a Reverse Path Forwarding (RPF) interface corresponding to the flow. The RPF interface may be disposed on a network device. Next, in response to determining that the bandwidth requirement of the flow has changed to the new bandwidth value, an egress capacity value may be updated in the interface usage table for an Outgoing Interface (OIF) corresponding to the flow. The OIF may be disposed on the network device.

A node (100) is configured for use in a communication network. The node (100) is configured to obtain a message with a source address and a destination address. The node (100) is also configured to determine whether the message is a type of message that is sent in response to a different message routed from the destination address to the source address, and whether a forward route (16) from the destination address to the source address has been established. The node (100) is also configured to selectively transmit the message on a backward route (18) that is the reverse of the forward route (16), depending on the determining.