Resource tracking

US9413588B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9413588-B2
Application numberUS-201213709873-A
CountryUS
Kind codeB2
Filing dateDec 10, 2012
Priority dateOct 6, 2008
Publication dateAug 9, 2016
Grant dateAug 9, 2016

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Clients may subscribe to resources for the purpose of receiving notifications of changes in the resource (e.g., a file is added to a shared folder). Storing subscriptions within persistent storage provides data security in the event of a service failure, at the cost of high latency in accessing subscription data. An efficient method for tracking a resource is provided herein. A subscription service creates subscriptions and monitors resources for a client. Upon a subscribed resource change, a notification service stores a notification of the change into a queue associated with the client. Efficient resource tracking is achieved because notification and subscription data is stored in low latency soft memory. The notification service is configured to detect a failure in the notification service and/or subscription service. In the event a service fails, the client provides a recovery mechanism by resubscribing to resources with which the client has an interest.

First claim

Opening claim text (preview).

What is claimed is: 1. A computer system for determining and recovering from a notification service failure, the computing system comprising: one or more processors; and one or more computer readable hardware storage devices, wherein the one or more computer readable hardware storage devices comprise computer executable instructions that are executable by at least one of the one or more processors to cause the computer system to perform the following: provide a client with read access to a first queue of one or more queues of a notification service, the first queue having a first queue identifier and being created at a time during which the notification service has a first notification service identifier, the notification service identifier and the first queue identifier being provided to the client, the first queue being maintained in a soft memory; receive a client request at the notification service, the client request including at least the notification service identifier; compare the notification service identifier received from the client request to a current notification service identifier maintained by the notification service; upon determining the notification service identifier received from the client request fails to match the current notification service identifier, determine a failure of the notification service has occurred and that the first queue is lost from the soft memory; and create a new queue with a new queue identifier. 2. The computer system of claim 1 , also including computer-executable instructions that are executable by the one or more processors to configure the computer system to store a notification within the first queue, the notification comprising at least one of: a message that the first queue was created; a message identifying the first queue identifier; or a message identifying the first notification service identifier. 3. The computer system of claim 1 , also including computer-executable instructions that are executable by the one or more processors to configure the computer system to provide the client with the current notification service identifier. 4. The computer system of claim 1 , also including computer-executable instructions that are executable by the one or more processors to configure the computer system to provide the client with the new queue identifier. 5. The computer system of claim 1 , wherein the new queue identifier is distinguished from the first queue identifier. 6. The computer system of claim 1 , also including computer-executable instructions that are executable by the one or more processors to configure the computer system to store a notification within the new queue, the notification comprising at least one of: a message that the first queue was lost; a message that the new queue was created; a message identifying the current notification service identifier; or a message identifying the new queue identifier. 7. The computer system of claim 1 , wherein the soft memory comprises volatile memory. 8. A method, implemented at a computer system that includes one or more processors, for determining and recovering from a notification service failure, the method comprising the computer system performing the following: providing a client with read access to a first queue of one or more queues of a notification service, the first queue having a first queue identifier and being created at a time during which the notification service has a first notification service identifier, the notification service identifier and the first queue identifier being provided to the client, the first queue being maintained in a soft memory; receiving a client request at the notification service, the client request including at least the notification service identifier; comparing the notification service identifier received from the client request to a current notification service identifier maintained by the notification service; upon determining the notification service identifier received from the client request fails to match the current notification service identifier, determining a failure of the notification service has occurred and that the first queue is lost from the soft memory; and creating a new queue with a new queue identifier. 9. The method of claim 8 , the method further comprising storing a notification within the first queue, the notification comprising at least one of: a message that the first queue was created; a message identifying the first queue identifier; or a message identifying the first notification service identifier. 10. The method of claim 8 , the method further comprising providing the client with the current notification service identifier. 11. The method of claim 8 , the method further comprising providing the client with the new queue identifier. 12. The method of claim 8 , wherein the new queue identifier is distinguished from the first queue identifier. 13. The method of claim 8 , the method further comprising storing a notification within the new queue, the notification comprising at least one of: a message that the first queue was lost; a message that the new queue was created; a message identifying the current notification service identifier; or a message identifying the new queue identifier. 14. The method of claim 8 , wherein the soft memory comprises volatile memory. 15. A computer program product comprising one or more hardware storage devices having stored thereon computer-executable instructions that are executable by one or more processors of a computer system and that configure the computer system to determine and recover from a notification service failure, including computer-executable instructions that configure the computer system to perform at least the following: provide a client with read access to a first queue of one or more queues of a notification service, the first queue having a first queue identifier and being created at a time during which the notification service has a first notification service identifier, the notification service identifier and the first queue identifier being provided to the client, the first queue being maintained in a soft memory; receive a client request at the notification service, the client request including at least the notification service identifier; compare the notification service identifier received from the client request to a current notification service identifier maintained by the notification service; upon determining the notification service identifier received from the client request fails to match the current notification service identifier, determine a failure of the notification service has occurred and that the first queue is lost from the soft memory; and create a new queue with a new queue identifier. 16. The computer program product of claim 15 , the computer-executable instructions being further executable by the one or more processors to configure the computer system to store a notification within the first queue, the notification comprising at least one of: a message that the first queue was created; a message identifying the first queue identifier; or a message identifying the first notification service identifier. 17. The computer program product of claim 15 , the computer-executable instructions being further executable by the one or more processors to configure the computer system to provide the client with the current notification service identifier. 18. The computer program product of claim 15 , the computer-executable instructions being further executable by

Assignees

Inventors

Classifications

  • Physics · mapped topic

  • Electricity · mapped topic

  • Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes · CPC title

  • Data stream processing; Continuous queries · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9413588B2 cover?
Clients may subscribe to resources for the purpose of receiving notifications of changes in the resource (e.g., a file is added to a shared folder). Storing subscriptions within persistent storage provides data security in the event of a service failure, at the cost of high latency in accessing subscription data. An efficient method for tracking a resource is provided herein. A subscription ser…
Who is the assignee on this patent?
Microsoft Technology Licensing Llc
What technology area does this patent fall under?
Primary CPC classification H04L29/0854. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Aug 09 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).