Abstract: A network device (e.g., a server, a domain name system (DNS) server, a DNS over Hypertext Transfer Protocol Secure (HTTPS) server (DoH server), a network management device, etc.) may determine a time duration, such as a time duration, based on a request for a communication session from a device. In response, the network device may determine a modified time duration for the communication session based on a type of the device, type of user associated with the device, and/or type of an application requesting the communication session.

Abstract: A network device (e.g., a server, a domain name system (DNS) server, a DNS over Hypertext Transfer Protocol Secure (HTTPS) server (DoH server), a network management device, etc.) may determine a time duration, such as a time duration, based on a request for a communication session from a device. In response, the network device may determine a modified time duration for the communication session based on a type of the device, type of user associated with the device, and/or type of an application requesting the communication session.

Abstract: A network device (e.g., a server, a domain name system (DNS) server, a DNS over Hypertext Transfer Protocol Secure (HTTPS) server (DoH server), a network management device, etc.) may determine a time duration, such as a time duration, based on a request for a communication session from a device. In response, the network device may determine a modified time duration for the communication session based on a type of the device, type of user associated with the device, and/or type of an application requesting the communication session.

Abstract: A network device (e.g., a server, a domain name system (DNS) server, a DNS over Hypertext Transfer Protocol Secure (HTTPS) server (DoH server), a network management device, etc.) may determine a time duration, such as a time duration, based on a request for a communication session from a device. In response, the network device may determine a modified time duration for the communication session based on a type of the device, type of user associated with the device, and/or type of an application requesting the communication session.

Abstract: A computing device may receive a request to join a multicast of content. The request may comprise a user device identifier associated with the user device. The computer device may receive a second request to leave the multicast of the content. The second request may comprise the user device identifier. The computing device may determine a quantity of data received by the user device from the multicast of the content. The computing device may determine the quantity of data received based on the request and the second request. The computing device may apply the quantity of data to an account associated with the user device.

Abstract: A network device (e.g., a server, a domain name system (DNS) server, a DNS over Hypertext Transfer Protocol Secure (HTTPS) server (DoH server), a network management device, etc.) may determine a time duration, such as a time duration, based on a request for a communication session from a device. In response, the network device may determine a modified time duration for the communication session based on a type of the device, type of user associated with the device, and/or type of an application requesting the communication session.

Abstract: An identifier, for example, an identifier of a domain and/or a host of the domain (e.g., a fully qualified domain name (FQDN), etc.), such as a service management device (e.g., a server, a web server, a computing device, a web host device, a webpage, etc.), may be modified (e.g., hashed, encrypted, etc.) by a network device (e.g., a server, a domain name system (DNS) server, a DNS over hypertext transfer protocol secure (HTTPS) server/gateway (DoH server), DNS over Transport Layer Security (TLS) server/gateway (DoT server), a network management device, a computing device, etc.), sent to a user device (e.g., a client device, a smart device, a mobile device, a content output device, a computing device, a web browser, a search engine, etc.), and reused by the user device to request a service (e.g., a web service, a webpage, a file, content, a content item, etc.).

Abstract: A destination host on a first network may attempt to initiate a communication session with a source host on a second network. The attempt may be intercepted by a first policy enforcement point, which may forward a message to the source host associated with the communication session. The source host may send an acknowledgment to the destination host via the first policy enforcement point. A policy decision point may determine that the communication session is permissible. The policy decision point may send a response to the first policy enforcement point and a second policy enforcement point. The response may indicate an approval of the communication session. The source host may respond to the destination host through either a first connection path and the first policy enforcement point or a second connection and the second policy enforcement point.

Abstract: A destination host on a first network may attempt to initiate a communication session with a source host on a second network. The attempt may be intercepted by a first policy enforcement point, which may forward a message to the source host associated with the communication session. The source host may send an acknowledgment to the destination host via the first policy enforcement point. A policy decision point may determine that the communication session is permissible. The policy decision point may send a response to the first policy enforcement point and a second policy enforcement point. The response may indicate an approval of the communication session. The source host may respond to the destination host through either a first connection path and the first policy enforcement point or a second connection and the second policy enforcement point.

Abstract: A destination host on a first network may attempt to initiate a communication session with a source host on a second network. The attempt may be intercepted by a first policy enforcement point, which may forward a message to the source host associated with the communication session. The source host may send an acknowledgment to the destination host via the first policy enforcement point. A policy decision point may determine that the communication session is permissible. The policy decision point may send a response to the first policy enforcement point and a second policy enforcement point. The response may indicate an approval of the communication session. The source host may respond to the destination host through either a first connection path and the first policy enforcement point or a second connection and the second policy enforcement point.

Abstract: Systems and methods are provided for a pull model for delivery of data such as content metadata among interconnected content delivery networks (CDNi), allowing for accurate metadata information in appropriate edge servers in a large CDNi system. When a request for an asset in a CDN (CDN A) is to be served by another, interconnected CDN (CDN B), a link to the location where the metadata is stored within CDN A can be provided along with the request for CDN B to serve the content to the user. The link can be passed to the appropriate edge device in CDN B, which can retrieve the metadata to set up and support the content session. The encrypted information can also be passed recursively by CDN B to other CDNs with which it is interconnected.

Abstract: A network monitoring and network congestion analysis can be performed based on a comparison of data packets at multiple different network nodes installed at different locations on a communication path. A downstream network node may be installed at a user location while an upstream network may be installed at an access router further up the network. A network congestion analyzer may receive data packet information including timestamps from both network nodes, and may compare the data packet information to group the data packets into application flows and match the corresponding packets from the different network nodes. Based on the data packet matching, the network congestion analyzer may calculate packet loss, packet delay, packet delay variation, and perform other network congestion analysis techniques for the application flows corresponding to a user's various devices and the applications executing on those devices.

Abstract: A network monitoring and network congestion analysis can be performed based on a comparison of data packets at multiple different network nodes installed at different locations on a communication path. A downstream network node may be installed at a user location while an upstream network may be installed at an access router further up the network. A network congestion analyzer may receive data packet information including timestamps from both network nodes, and may compare the data packet information to group the data packets into application flows and match the corresponding packets from the different network nodes. Based on the data packet matching, the network congestion analyzer may calculate packet loss, packet delay, packet delay variation, and perform other network congestion analysis techniques for the application flows corresponding to a user's various devices and the applications executing on those devices.

Abstract: A network monitoring and network congestion analysis can be performed based on a comparison of data packets at multiple different network nodes installed at different locations on a communication path. A downstream network node may be installed at a user location while an upstream network may be installed at an access router further up the network. A network congestion analyzer may receive data packet information including timestamps from both network nodes, and may compare the data packet information to group the data packets into application flows and match the corresponding packets from the different network nodes. Based on the data packet matching, the network congestion analyzer may calculate packet loss, packet delay, packet delay variation, and perform other network congestion analysis techniques for the application flows corresponding to a user's various devices and the applications executing on those devices.

Abstract: Systems and methods are provided for a pull model for delivery of data such as content metadata among interconnected content delivery networks (CDNi), allowing for accurate metadata information in appropriate edge servers in a large CDNi system. When a request for an asset in a CDN (CDN A) is to be served by another, interconnected CDN (CDN B), a link to the location where the metadata is stored within CDN A can be provided along with the request for CDN B to serve the content to the user. The link can be passed to the appropriate edge device in CDN B, which can retrieve the metadata to set up and support the content session. The encrypted information can also be passed recursively by CDN B to other CDNs with which it is interconnected.

Abstract: A network monitoring and network congestion analysis can be performed based on a comparison of data packets at multiple different network nodes installed at different locations on a communication path. A downstream network node may be installed at a user location while an upstream network may be installed at an access router further up the network. A network congestion analyzer may receive data packet information including timestamps from both network nodes, and may compare the data packet information to group the data packets into application flows and match the corresponding packets from the different network nodes. Based on the data packet matching, the network congestion analyzer may calculate packet loss, packet delay, packet delay variation, and perform other network congestion analysis techniques for the application flows corresponding to a user's various devices and the applications executing on those devices.

Abstract: A network monitoring and network congestion analysis can be performed based on a comparison of data packets at multiple different network nodes installed at different locations on a communication path. A downstream network node may be installed at a user location while an upstream network may be installed at an access router further up the network. A network congestion analyzer may receive data packet information including timestamps from both network nodes, and may compare the data packet information to group the data packets into application flows and match the corresponding packets from the different network nodes. Based on the data packet matching, the network congestion analyzer may calculate packet loss, packet delay, packet delay variation, and perform other network congestion analysis techniques for the application flows corresponding to a user's various devices and the applications executing on those devices.

Abstract: A network monitoring and network congestion analysis can be performed based on a comparison of data packets at multiple different network nodes installed at different locations on a communication path. A downstream network node may be installed at a user location while an upstream network may be installed at an access router further up the network. A network congestion analyzer may receive data packet information including timestamps from both network nodes, and may compare the data packet information to group the data packets into application flows and match the corresponding packets from the different network nodes. Based on the data packet matching, the network congestion analyzer may calculate packet loss, packet delay, packet delay variation, and perform other network congestion analysis techniques for the application flows corresponding to a user's various devices and the applications executing on those devices.

Abstract: A hair trimmer 1 has a lower housing 2 with a battery or battery set 9, a motor 7, a first blade driver 10 and a first trimmer blade 11. A first blade driver 10 drives both the first trimmer blade 11 and a first lever 12. The first lever 12 is used to drive a second blade assembly 8 for fine trimming. The upper housing 4 includes a second blade assembly 8 located on a sliding platform 14 in the upper housing 4 and is driven by the first lever 12 through its blade driver 15. The two housings and cover 2, 3, 4 are moveable between engaged and disengaged positions with their respective drive assemblies for being selectively driven by the motor so that either of the blade assemblies 6,8 are activated, respectively.

Abstract: A new prefix, an international mobile call prefix, is provided in a telecommunications network, such as PSTN, for routing the PSTN originating international call to a foreign mobile subscriber. When a local PSTN exchange receives the international mobile call prefix in the dialed telephone number, it will route the call to a predetermined destination in the same country. The predetermined destination is a network element having a capability of making international routing information interrogation to a home PLMN of a called foreign mobile subscriber. Upon receiving the routing information from the home PLMN the call will be routed to the current location of the called foreign mobile subscriber according to the routing information. As a result, unnecessary international legs in the call can be avoided when the called mobile subscriber is roaming abroad.