Abstract: Discovery of a network to which a device is in communication and classifying the network is disclosed. The network may be classified as a network already known or a new network signature may be created where the network signature is made up of a network id, a link id and a hop id.

Abstract: A method and apparatus for treating fluid are provided. The fluid treatment device may include a housing having a fluid treatment element therein. The device may further include at least one of (i) an inlet channel coupled to the housing and configured to direct fluid toward the fluid treatment element and (ii) an outlet channel coupled to the housing and configured to direct fluid away from the fluid treatment element. The at least one of the inlet channel and the outlet channel may include a shell member having an inner diameter and defining a fluid passage. The at least one of the inlet channel and the outlet channel may further include a gate member coupled to and arranged at least partially within the shell member and extending longitudinally from a first gate member portion having a diameter less than the inner diameter of the shell member to a second gate member portion having a diameter greater than the inner diameter of the shell member.

Abstract: A method and apparatus for treating fluid are provided. The apparatus may include a housing, a fluid treatment element arranged within the housing, a mat arranged between the housing and the fluid treatment element, and a collar. The collar may have a curved length terminating at first and second ends and may be arranged within the housing proximate the fluid treatment element.

Abstract: An application program interface (API) for sending and receiving endpoint registration data and peer-to-peer network cloud data has a registration call for adding endpoint data to a peer-to-peer network. The API may receive explicit data regarding address information or may be instructed to select and maintain suitable address information as the topology of the peer-to-peer network changes. Blocking and non-blocking calls are exposed for retrieving information peer-to-peer network endpoint data.

Abstract: A method of determining a source address to publish and a destination address to use for a network, including a PNRP network, is disclosed such that the probability of reaching a network node without repeated re-tries is maximized.

Abstract: Disclosed is an authentication mechanism that enables an information recipient to ascertain that the information comes from the sender it purports to be from. This mechanism integrates a private/public key pair with selection by the sender of a portion of its address. The sender derives its address from its public key, for example, by using a hash of the key. The recipient verifies the association between the address and the sender's private key. The recipient may retrieve the key from an insecure resource and know that it has the correct key because only that key can produce the sender's address in the message. The hash may be made larger than the sender-selectable portion of the address. The recipient may cache public key/address pairs and use the cache to detect brute force attacks and to survive denial of service attacks. The mechanism may be used to optimize security negotiation algorithms.

Abstract: A method, identification tag reader and computer program product for communication with an identification tag are disclosed. To communicate with the tag, identification data may be retrieved from an identification tag. A guest identification, compliant with at least a portion of a standard network protocol address, may be assigned to the identification tag. A message addressed to a tag routing address of the tag may be received, and a response to the message may be sent.

Abstract: A unified architecture for enabling remote access to a network is provided. The network may comprise, as examples, a virtual private network (VPN) and/or a peer-to-peer network. In one embodiment, the architecture includes components installed on a client device/node and a gateway/supernode. Components implemented on the client device may facilitate access in a manner similar to that of a traditional VPN, while components on the gateway may facilitate access in a manner similar to an application proxy. Communication between the client device and gateway may occur, as an example, via a Secure Sockets Layer (SSL) communication protocol.

Abstract: A network diagnostics system allows determining a root cause for a network problem caused by a local or a remote component of the network, wherein the network diagnostic system may receive the symptoms of such a problem from an application. The network diagnostic system uses a plurality of helper classes, each of the plurality of helper classes providing diagnostic information about an object or a class of objects on the network. Moreover, the network diagnostic system may also use one or more extensible helper classes that are designed to receive information from third party helper classes.

Abstract: Methods and computer readable mediums are described that facilitate inviting user entities on a network. The method may include initiating a first application for sending an invitation by a first user entity on a first endpoint, selecting a second user entity to receive the invitation, and selecting an activity. The method may also include sending from the first endpoint to the second user entity the invitation to participate in the activity if the first endpoint determines the activity is supported by a computing application on the first endpoint.

Abstract: Systems and methods are described that facilitate the management of contact information, at least some of the contact information related to entities in a serverless, peer-to-peer system. A contact store may store information regarding which other entities of a plurality of other entities are authorized to monitor presence of a user entity. Presence of an entity may generally indicate the willingness and/or ability of the entity to communicate and/or collaborate with other entities, for example. The contact store may also store information regarding which other entities of the plurality of other entities the presence of which should be monitored by the system. A user entity may be able to add contacts to and/or delete contacts from the contact store, for example.

Abstract: A collaborative services platform may include a connectivity service, an activity service and a contact management service. The connectivity service may provide communicative connectivity between users of the collaborative services platform. The activity service may provide one or more collaborative activities supporting various modes of communication. The contact management service may maintain contact information for each of the users of the collaborative service platform. It may be that not every user is capable of participating in every collaborative activity. The contact information maintained by the contact management service may indicate the collaborative activities in which each user is capable of participating. A set of programmatic objects utilized to implement the collaborative services platform may include contact objects, conference objects, MeContact objects, endpoint objects, published objects and presence objects.

Abstract: Communication functionality is described for conducting communication among a plurality of participants in peer-to-peer fashion. The communication functionality comprises peer-to-peer overlay functionality configured to establish a peer-to-peer overlay network that includes a plurality of participants. The peer-to-peer overlay functionality relies on endpoint provider functionality for physically exchanging information among the plurality of participants in the peer-to-peer overlay network. The endpoint provider functionality exchanges information using a transport mechanism. The transport mechanism accommodates multiple different transport protocols for exchanging information among the plurality of participants, allowing different pairs of participants to communicate with each other using different respective transport protocols.

Abstract: Methods are described that facilitate presence publication which may include authorizing publication of presence at a first endpoint, if the publication is authorized, assembling a presence data structure, and broadcasting the presence data structure from the first endpoint. The method may also include the presence structure including a friendly name, contact information, and endpoint information. The method further including contact information in at least one of XML format, vCard format, and the endpoint information obtained from a peer name resolution protocol. The method may additionally include the presence data structure encoded as at least one of a generic discovery protocol message, a simple service discovery protocol message, and associating a globally unique identifier with the discovery protocol messages.

Abstract: Systems and methods are described for facilitiating collaboration and/or communication in a peer-to-peer serverless system. The system may transmit to other computing systems associated with other entities information regarding presence information associated with a user entity. Also, the system may request of other computing systems associated with other entities information regarding presence information associated with the other entities. Presence information may generally indicate the willingness and/or ability of an entity to communicate and/or collaborate with other entities, for example.

Abstract: A set of collaborative contacts may be selected with an invitation user interface. An invitation to participate in a collaborative activity may be sent to the selected contacts from the invitation user interface or from a collaborative application. The invitation may be received by a collaborative services platform. A user of the collaborative services platform may be presented with the invitation along with an ability to choose one of accept, decline and ignore in response to the invitation. The user may choose to accept, decline or explicitly ignore the invitation, and a response may be sent to the sender of the invitation indicating the user's choice. An application programming interface for a collaborative invitation service of the collaborative services platform may include an invitation element, a send invitation element, a respond to invitation element and a cancel invitation element. The cancel invitation element may be used to cancel issued invitations.

Abstract: Collaboration between collaborative endpoints may be facilitated by a serverless publication service of a collaborative services platform. The serverless publication service may be configured to accept communicative connections from the collaborative endpoints. Users of the collaborative services platform may publish their associated collaborative presences with the serverless publication service. For example, the collaborative presence of a user may include information with respect to valid collaborative endpoints for the user and collaborative capabilities at those endpoints. Subscriptions to published collaborative presences may be placed through the serverless publication service. A collaborative presence subscribe message may specify a subscription to a collaborative presence of a user. Upon receipt of a presence subscribe message, if there is no subscription policy with respect to the sender, the recipient may be queried for a subscription policy with respect to the sender.

Abstract: Enumeration requests are sent from a node in a network. Each node that receives an enumeration request sends an enumeration response at a time determined by the node receiving the enumeration request.

Abstract: According to an exemplary embodiment of the present disclosure, a system for removing matter from a filtering device of a work machine includes a gas pressurization assembly. An element of the gas pressurization assembly is removably attachable to a first orifice of the filtering device without removing the filtering device from a work machine to which the filtering device is connected. The system also includes a heat source fluidly connected to the gas pressurization assembly.

Abstract: An exhaust gas recirculation system for a power source, has at least one inlet port configured to receive at least a portion of a flow of exhaust produced by the power source. The exhaust gas recirculation system also has an electrode disposed upstream of the at least one inlet port and configured to charge particulate matter in the flow of exhaust. The exhaust gas recirculation system further has at least one collection surface configured to allow the at least one electrode to repel the charged particulate matter away from the at least one inlet port towards the at least one collection surface.