Patents by Inventor Sean C. Olson
Sean C. Olson has filed for patents to protect the following inventions. This listing includes patent applications that are pending as well as patents that have already been granted by the United States Patent and Trademark Office (USPTO).
-
Patent number: 9432239Abstract: A system and method for uniquely identifying an SIP device extends the SIP communications protocol with an end point identifier, carried for example in the header of an SIP transmission. The end point identifier is useful for routing, registration, subscription, and authentication. The end point (device) of a given user epid can be uniquely identified by creating a key from an epid and a user's address-of-record (URI). This in turn enables improved connection management and security association management when the connections/IP addresses are transient, such as when HTTPS tunneling is used.Type: GrantFiled: March 19, 2013Date of Patent: August 30, 2016Assignee: Microsoft Technology Licensing, LLCInventors: Sean C. Olson, Jeremy T. Buch, Ajay P. Chitturi, David J. Simons, Nikhil P. Bobde
-
Patent number: 8402146Abstract: A system and method for uniquely identifying an SIP device extends the SIP communications protocol with an end point identifier, carried for example in the header of an SIP transmission. The end point identifier is useful for routing, registration, subscription, and authentication. The end point (device) of a given user epid can be uniquely identified by creating a key from an epid and a user's address-of-record (URI). This in turn enables improved connection management and security association management when the connections/IP addresses are transient, such as when HTTPS tunneling is used.Type: GrantFiled: August 30, 2011Date of Patent: March 19, 2013Assignee: Microsoft CorporationInventors: Sean C. Olson, Jeremy T. Buch, Ajay P. Chitturi, David J. Simons, Nikhil P. Bobde
-
Publication number: 20120084447Abstract: A system and method for uniquely identifying an SIP device extends the SIP communications protocol with an end point identifier, carried for example in the header of an SIP transmission. The end point identifier is useful for routing, registration, subscription, and authentication. The end point (device) of a given user epid can be uniquely identified by creating a key from an epid and a user's address-of-record (URI). This in turn enables improved connection management and security association management when the connections/IP addresses are transient, such as when HTTPS tunneling is used.Type: ApplicationFiled: August 30, 2011Publication date: April 5, 2012Applicant: MICROSOFT CORPORATIONInventors: Sean C. Olson, Jeremy T. Buch, Ajay P. Chitturi, David J. Simons, Nikhil P. Bobde
-
Publication number: 20120079014Abstract: The present invention allows a server to delay allocating resources to a client's request. When the client requests a feature that requires server resources, the server accepts and acknowledges the client's request, but the client is prohibited from using the requested feature until further notice from the server. For example, during an authorization process, the server allocates only the minimum resources required to maintain the session and to authorize the client. Thereafter, the server allocates the resources necessary to support the client's request only when the resources become available. Until then, the server maintains the communications session without supporting the request. Thus, the server shepherds its resources rather than committing them at the whim of a client. Also, a client need not repeat its request if the server cannot immediately satisfy it; instead, the server accepts the request and then later begins to support it when adequate resources become available.Type: ApplicationFiled: December 1, 2011Publication date: March 29, 2012Applicant: Microsoft CorporationInventors: Mark Markaryan, Dmitry M. Kakurin, Sean C. Olson, Srikanth Shoroff, Radu Ionescu
-
Patent number: 8086741Abstract: The present invention allows a server to delay allocating resources to a client's request. When the client requests a feature that requires server resources, the server accepts and acknowledges the client's request, but the client is prohibited from using the requested feature until further notice from the server. For example, during an authorization process, the server allocates only the minimum resources required to maintain the session and to authorize the client. Thereafter, the server allocates the resources necessary to support the client's request only when the resources become available. Until then, the server maintains the communications session without supporting the request. Thus, the server shepherds its resources rather than committing them at the whim of a client. Also, a client need not repeat its request if the server cannot immediately satisfy it; instead, the server accepts the request and then later begins to support it when adequate resources become available.Type: GrantFiled: August 15, 2003Date of Patent: December 27, 2011Assignee: Microsoft CorporationInventors: Mark Markaryan, Dmitry M. Kakurin, Sean C. Olson, Srikanth Shoroff, Radu Ionescu
-
Patent number: 8024470Abstract: A system and method for uniquely identifying an SIP device extends the SIP communications protocol with an end point identifier, carried for example in the header of an SIP transmission. The end point identifier is useful for routing, registration, subscription, and authentication. The end point (device) of a given user epid can be uniquely identified by creating a key from an epid and a user's address-of-record (URI). This in turn enables improved connection management and security association management when the connections/IP addresses are transient, such as when HTTPS tunneling is used.Type: GrantFiled: July 8, 2008Date of Patent: September 20, 2011Assignee: Microsoft CorporationInventors: Sean C. Olson, Jeremy T. Buch, Ajay P. Chitturi, David J. Simons, Nikhil P. Bobde
-
Patent number: 7653812Abstract: A method and system for identifying whether an electronic communication is likely to be unwanted by the recipient is provided. A trust system relies on a trust provider, such as a sending domain, to indicate whether an electronic communication is likely to be unwanted. The sending domain may assign its trust level to the electronic communications based on various factors. Upon receiving the electronic communication and the trust level assigned by the sending domain, the receiving domain may determine whether to forward the electronic communication to the recipient based on the trust level. If a sending domain consistently provides trust levels that are accurate assessments of whether electronic communications are unwanted, then the receiving domain learns to trust the trust levels assigned by the sending domain.Type: GrantFiled: December 9, 2004Date of Patent: January 26, 2010Assignee: Microsoft CorporationInventors: Orit Levin, Sean C. Olson, Timothy Rang
-
Patent number: 7577984Abstract: A method and system for identifying whether an electronic communication is likely to be unwanted by the recipient is provided. A trust system relies on a trust provider, such as a sending domain, to indicate whether an electronic communication is likely to be unwanted. The sending domain may assign its trust level to the electronic communications based on various factors. Upon receiving the electronic communication and the trust level assigned by the sending domain, the receiving domain may determine whether to forward the electronic communication to the recipient based on the trust level. If a sending domain consistently provides trust levels that are accurate assessments of whether electronic communications are unwanted, then the receiving domain learns to trust the trust levels assigned by the sending domain.Type: GrantFiled: December 9, 2004Date of Patent: August 18, 2009Assignee: Microsoft CorporationInventors: Orit Levin, Sean C. Olson, Timothy Rang, Srikanth Shoroff, Vadim Eydelman
-
Publication number: 20090177784Abstract: A system and method for uniquely identifying an SIP device extends the SIP communications protocol with an end point identifier, carried for example in the header of an SIP transmission. The end point identifier is useful for routing, registration, subscription, and authentication. The end point (device) of a given user epid can be uniquely identified by creating a key from an epid and a user's address-of-record (URI). This in turn enables improved connection management and security association management when the connections/IP addresses are transient, such as when HTTPS tunneling is used.Type: ApplicationFiled: July 8, 2008Publication date: July 9, 2009Applicant: Microsoft CorporationInventors: Sean C. Olson, Jeremy T. Buch, Ajay P. Chitturi, David J. Simons, Nikhil P. Bobde
-
Patent number: 7519818Abstract: A method and system for identifying whether an electronic communication is likely to be unwanted by the recipient is provided. A trust system relies on a trust provider, such as a sending domain, to indicate whether an electronic communication is likely to be unwanted. The sending domain may assign its trust level to the electronic communications based on various factors. Upon receiving the electronic communication and the trust level assigned by the sending domain, the receiving domain may determine whether to forward the electronic communication to the recipient based on the trust level. If a sending domain consistently provides trust levels that are accurate assessments of whether electronic communications are unwanted, then the receiving domain learns to trust the trust levels assigned by the sending domain.Type: GrantFiled: December 9, 2004Date of Patent: April 14, 2009Assignee: Microsoft CorporationInventors: Orit Levin, Sean C. Olson, Timothy Rang
-
Patent number: 7412521Abstract: A system and method for uniquely identifying an SIP device extends the SIP communications protocol with an end point identifier, carried for example in the header of an SIP transmission. The end point identifier is useful for routing, registration, subscription, and authentication. The end point (device) of a given user epid can be uniquely identified by creating a key from an epid and a user's address-of-record (URI). This in turn enables improved connection management and security association management when the connections/IP addresses are transient, such as when HTTPS tunneling is used.Type: GrantFiled: March 12, 2003Date of Patent: August 12, 2008Assignee: Microsoft CorporationInventors: Sean C. Olson, Jeremy T. Buch, Ajay P. Chitturi, David J. Simons, Nikhil P. Bobde
-
Publication number: 20070276913Abstract: This document describes tools capable of enabling participants in a real-time, text-messaging conference to access text messages that they have missed, whether that be because they joined the conference late, were disconnected, or did not receive a message due to some sort of failure. Assume, for example, that a conference participant on a wireless laptop does not receive a text message because of a wireless connection failure. The tools, in one embodiment, enable the participant's laptop to notice that the text message was not received, ask for the missing text message, and receive the missing text message. The participant's laptop may then display the missing text message thereby allowing the participant to catch up with the conference and so not lose the context of the ongoing text-messaging conversation.Type: ApplicationFiled: May 23, 2006Publication date: November 29, 2007Applicant: Microsoft CorporationInventors: Sean C. Olson, Ajay P. Chitturi, Rajesh Ramanathan, Parag Samdadiya
-
Publication number: 20070271337Abstract: This document describes tools that notify participants of a real-time, collaborative electronic meeting when the meeting productively starts. To do so, the tools may build a quorum of events that need to occur before the meeting may productively start. These events may include a particular person joining the meeting, such as the meeting's lead presenter, a particular document being uploaded for the participants to see or use, such as a PowerPointâ„¢ presentation, an agenda for the meeting, and the meeting's start time, to name a few. When the tools determine that the events have occurred, the tools notify the participants. This permits participants of a meeting to focus on things other than the meeting until the meeting productively starts.Type: ApplicationFiled: May 22, 2006Publication date: November 22, 2007Applicant: Microsoft CorporationInventor: Sean C. Olson
-
Publication number: 20040205192Abstract: A system and method for uniquely identifying an SIP device extends the SIP communications protocol with an end point identifier, carried for example in the header of an SIP transmission. The end point identifier is useful for routing, registration, subscription, and authentication. The end point (device) of a given user epid can be uniquely identified by creating a key from an epid and a user's address-of-record (URI). This in turn enables improved connection management and security association management when the connections/IP addresses are transient, such as when HTTPS tunneling is used.Type: ApplicationFiled: March 12, 2003Publication date: October 14, 2004Applicant: Microsoft CorporationInventors: Sean C. Olson, Jeremy T. Buch, Ajay P. Chitturi, David J. Simons, Nikhil P. Bobde
-
Publication number: 20040172474Abstract: The present invention allows a server to delay allocating resources to a client's request. When the client requests a feature that requires server resources, the server accepts and acknowledges the client's request, but the client is prohibited from using the requested feature until further notice from the server. For example, during an authorization process, the server allocates only the minimum resources required to maintain the session and to authorize the client. Thereafter, the server allocates the resources necessary to support the client's request only when the resources become available. Until then, the server maintains the communications session without supporting the request. Thus, the server shepherds its resources rather than committing them at the whim of a client. Also, a client need not repeat its request if the server cannot immediately satisfy it; instead, the server accepts the request and then later begins to support it when adequate resources become available.Type: ApplicationFiled: August 15, 2003Publication date: September 2, 2004Applicant: Microsoft CorporationInventors: Mark Markaryan, Dmitry M. Kakurin, Sean C. Olson, Srikanth Shoroff, Radu Ionescu