Abstract: A presence server in a network can receive capability information about a UE in a publish message, and make that capability information available to other UEs on the network. When the UE later deregisters from the network, the UE can send an unpublish message. However, the presence server can at least partially disregard the unpublish message and continue to make the capability information about the UE available to other UEs. The presence server can also filter capability information of one or more target UEs provided to a watcher UE based on a registration status of a target UE, capabilities of the watcher UE, and/or whether a set of target UEs associated with a single user share certain capabilities.

Abstract: A presence server in a network can receive capability information about a UE in a publish message, and make that capability information available to other UEs on the network. When the UE later deregisters from the network, the UE can send an unpublish message. However, the presence server can at least partially disregard the unpublish message and continue to make the capability information about the UE available to other UEs. The presence server can also filter capability information of one or more target UEs provided to a watcher UE based on a registration status of a target UE, capabilities of the watcher UE, and/or whether a set of target UEs associated with a single user share certain capabilities.

Abstract: A presence server in a network can receive capability information about a UE in a publish message, and make that capability information available to other UEs on the network. When the UE later deregisters from the network, the UE can send an unpublish message. However, the presence server can at least partially disregard the unpublish message and continue to make the capability information about the UE available to other UEs. The presence server can also filter capability information of one or more target UEs provided to a watcher UE based on a registration status of a target UE, capabilities of the watcher UE, and/or whether a set of target UEs associated with a single user share certain capabilities.

Abstract: A presence server in a network can receive capability information about a UE in a publish message, and make that capability information available to other UEs on the network. When the UE later deregisters from the network, the UE can send an unpublish message. However, the presence server can at least partially disregard the unpublish message and continue to make the capability information about the UE available to other UEs. The presence server can also filter capability information of one or more target UEs provided to a watcher UE based on a registration status of a target UE, capabilities of the watcher UE, and/or whether a set of target UEs associated with a single user share certain capabilities.

Abstract: A request from a watcher client to obtain presence information of a presentity client may be processed at a presence server using a system configuration of the presence server that stores local presence authorization rules (“pres-rules”). By storing pres-rules locally at the presence server, these pres-rules may be used by the presence server in lieu of, or in combination with, other pres-rules that may be maintained by a separate pres-rules storage server, such as an eXtensible Markup Language (XML) Document Management Server (XDMS). The system configuration may specify configurable parameters that control the behavior of the presence server in engaging the XDMS when processing requests from watcher clients, as well as the behavior of the presence server in merging pres-rules retrieved from the XDMS with the local pres-rules maintained by the presence server.

Abstract: A request from a watcher client to obtain presence information of a presentity client may be processed at a presence server using a system configuration of the presence server that stores local presence authorization rules (“pres-rules”). By storing pres-rules locally at the presence server, these pres-rules may be used by the presence server in lieu of, or in combination with, other pres-rules that may be maintained by a separate pres-rules storage server, such as an eXtensible Markup Language (XML) Document Management Server (XDMS). The system configuration may specify configurable parameters that control the behavior of the presence server in engaging the XDMS when processing requests from watcher clients, as well as the behavior of the presence server in merging pres-rules retrieved from the XDMS with the local pres-rules maintained by the presence server.

Abstract: A seed meter and accelerator comprises a stationary housing, a stationary axially extending dispensing rim, a radially extending flange and a rotating disc. The stationary housing is provided with an axially extending metering rim. The meter rim is provided with a metering gap. The stationary axially extending dispensing rim is located radially outward from the metering rim and is provided with a dispensing gap. The radially extending flange extends between the axially extending metering rim and the axially extending dispensing rim. The rotating disc is provided with an inner portion having circumferentially arranged seed pockets and an outer portion having seed dispensing openings. Each seed pocket corresponds to a seed dispensing opening. Passages extend between the seed pockets and the seed dispensing openings. The seed pockets of the inner portion are located adjacent to and radially inward from the metering rim.