Patents by Inventor Andrew J. Layman
Andrew J. Layman 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: 9191394Abstract: Protecting user credentials from a computing device includes establishing a secure session between a computing device and an identity provider (e.g., a Web service). Parameters of the secure session are communicated to a credential service, which renegotiates or resumes the secure session to establish a new secure session between the credential service and the identity provider. User credentials are passed from the credential service to the identity provider via the new secure session, but the computing device does not have the parameters of the new secure session and thus does not have access to the passed user credentials. The credential service then renegotiates or resumes the secure session again to establish an additional secure session between the credential service and the identity provider. Parameters of the additional secure session are communicated to the computing device to allow the computing device to continue communicating securely with the identity provider.Type: GrantFiled: February 8, 2012Date of Patent: November 17, 2015Assignee: Microsoft Technology Licensing, LLCInventors: Mark F. Novak, Andrew J. Layman
-
Publication number: 20130205360Abstract: Protecting user credentials from a computing device includes establishing a secure session between a computing device and an identity provider (e.g., a Web service). Parameters of the secure session are communicated to a credential service, which renegotiates or resumes the secure session to establish a new secure session between the credential service and the identity provider. User credentials are passed from the credential service to the identity provider via the new secure session, but the computing device does not have the parameters of the new secure session and thus does not have access to the passed user credentials. The credential service then renegotiates or resumes the secure session again to establish an additional secure session between the credential service and the identity provider. Parameters of the additional secure session are communicated to the computing device to allow the computing device to continue communicating securely with the identity provider.Type: ApplicationFiled: February 8, 2012Publication date: August 8, 2013Applicant: MICROSOFT CORPORATIONInventors: Mark F. Novak, Andrew J. Layman
-
Patent number: 8001189Abstract: A routing protocol is provided for exchanging messages between an initial sender and an ultimate receiver, potentially via a set of intermediaries. The routing protocol provides an optional reverse message path that enables two-way message exchange patterns. The routing protocol can be expressed as a header entry within a message envelope, is independent of the underlying protocol, and can be generated at the application layer of a protocol stack. The routing protocol may allow each intermediary to process the message and dynamically alter the message path en route to the intended recipient.Type: GrantFiled: October 15, 2002Date of Patent: August 16, 2011Assignee: Microsoft CorporationInventors: Henrik F. Nielsen, John P. Shewchuk, Erik B. Christensen, Alfred M. Lee, Christian Huitema, James M. Lyon, Mark H. Lukovsky, Andrew J. Layman, Satish R. Thatte, Christopher Kaler
-
Patent number: 7653747Abstract: An apparatus and method is provided for resolving virtual network names using one or more name routers. A conventional Uniform Resource Locator (URL) naming scheme is extended by allowing any component to be mapped to an address. The resolution process occurs recursively through a plurality of name routers. Resolution can be contextual, such that the same virtual network name may be resolved differently depending on the identity of the client or other parameters.Type: GrantFiled: June 5, 2006Date of Patent: January 26, 2010Assignee: Microsoft CorporationInventors: Steven E. Lucco, Erik B. Christensen, Andrew J. Layman, David E. Levin, Bradford H. Lovering, Henrik Frystyk Nielsen, John P. Shewchuk
-
Patent number: 7543226Abstract: A programming object can comprise an executable method for loading a state of the object and an executable method for saving the object's state. The programming object can be an instance of a programmer-defined class. The executable method of the object for loading the state of the object can load the object's state as markup language text, and the executable method of the object for saving the object's state can save the object's state as markup language text.Type: GrantFiled: September 27, 2004Date of Patent: June 2, 2009Assignee: Microsoft CorporationInventors: James Lee Francis, Frank Mantek, Andrew J. Layman, Robert A. Little, Darren A. Apfel
-
Publication number: 20090132910Abstract: A technique for incorporating binary formatting into a tag-based description language, such as XML, is provided. The binary formatting is achieved by tokenizing the tag and attribute names into variable sized numeric tokens, thereby obviating the need for repetitive or redundant storage of lengthy unicode words, etc. The binary formatting minimizes parsing time and the generation of overhead incident to the formatting and parsing of data. Parsing time is thereby substantially decreased and generally, the size of the resulting file decreases too.Type: ApplicationFiled: January 23, 2009Publication date: May 21, 2009Applicant: Microsoft CorporationInventors: Istvan Cseri, Oliver Nicholas Seeliger, Andrew J. Layman
-
Patent number: 7500017Abstract: A technique for incorporating binary formatting into a tag-based description language, such as XML, is provided. The binary formatting is achieved by tokenizing the tag and attribute names into variable sized numeric tokens, thereby obviating the need for repetitive or redundant storage of lengthy unicode words, etc. The binary formatting minimizes parsing time and the generation of overhead incident to the formatting and parsing of data. Parsing time is thereby substantially decreased and generally, the size of the resulting file decreases too.Type: GrantFiled: April 19, 2001Date of Patent: March 3, 2009Assignee: Microsoft CorporationInventors: Istvan Cseri, Oliver Nicolas Seeliger, Andrew J. Layman
-
Patent number: 7496682Abstract: Using a message exchanger (“message exchanger”), data messages are exchanged between entities in a decentralized, distributed, potentially heterogeneous, network environment. The message exchanger employs XML (extensible Markup Language). To accomplish this, the entities on both ends of the message exchange understand, identify, and parse the message format. The message exchanger defines such a mechanism. Data messages are broken down into two portions—one portion (the body) is intended from an ultimate destination and the other portion (the header) is intended for intermediate destination and/or the ultimate destination. The body may be defined so that it must be understood by the ultimate destination. The header may be defined so that it must be understood or changed. Regardless, the data in the body is delivered intact to the ultimate destination. The message exchanger defines a message envelope exchange format in XML over a transport protocol, such as HTTP (HyperText Transport Protocol).Type: GrantFiled: June 26, 2006Date of Patent: February 24, 2009Assignee: Microsoft CorporationInventors: Andrew J. Layman, Gopal Krishna R. Kakivaya, Satish R. Thatte, Henrik F. Nielsen, Robert George Atkinson
-
Patent number: 7281207Abstract: Herein is described an implementation of an object persister, which serializes an object to preserve the object's data structure and its current data. The serialized object is encoded using XML and inserted within a message. That message is transmitted to an entity over a network. Such a transmission is performed using standard Internet protocols, such as HTML. Upon receiving the serialized object, the receiving entity deserializes the object to use it. Rather than include copies of referenced objects within the serialized object, the object persister includes references to those objects. This avoids redundant inclusion of the same object and potentially infinite inclusion of the object itself that is being serialized.Type: GrantFiled: July 16, 2004Date of Patent: October 9, 2007Assignee: Microsoft CorporationInventors: Andrew J. Layman, Gopal Krishna R. Kakivaya, Satish R. Thatte
-
Patent number: 7278095Abstract: Here is described an implementation of an object persister, which serializes an object to preserve the object's data structure and its current data. The serialized object is encoded using XML and inserted within a message. That message is transmitted to an entity over a network. Such a transmission is performed using standard Internet protocols, such as HTML. Upon receiving the serialed object, the receiving entity deserializes the object to use it. Rather than include copies of referenced objects within the serialized object, the object persister includes references to those objects. This avoids redundant inclusion of the same object and potentially infinite inclusion of the object itself that is being serialized.Type: GrantFiled: July 16, 2004Date of Patent: October 2, 2007Assignee: Microsoft CorporationInventors: Andrew J. Layman, Gopal Krishna R. Kakivaya, Satish R. Thatte
-
Patent number: 7260775Abstract: Described is a system and mechanism by which a client computer may issue a conventional request for a resource on the Web. A response to that request is annotated with information indicating that metadata is available for the resource. Specifically, a special tag or instruction may be included in the response document that indicates the existence and location of a discovery document containing metadata about the resource. The client computer may then retrieve the metadata from the location identified in the response.Type: GrantFiled: February 11, 2002Date of Patent: August 21, 2007Assignee: Microsoft CorporationInventors: Erik B. Christensen, Henrik Frystyk Nielsen, Andrew J. Layman, Gopal Krishna R. Kakivaya
-
Patent number: 7194553Abstract: An apparatus and method is provided for resolving virtual network names using one or more name routers. A conventional Uniform Resource Locator (URL) naming scheme is extended by allowing any component to be mapped to an address. The resolution process occurs recursively through a plurality of name routers. Resolution can be contextual, such that the same virtual network name may be resolved differently depending on the identity of the client or other parameters.Type: GrantFiled: October 24, 2001Date of Patent: March 20, 2007Assignee: Microsoft CorporationInventors: Steven E. Lucco, Erik B. Christensen, Andrew J. Layman, David E. Levin, Bradford H. Lovering, Henrik Frystyk Nielsen, John P. Shewchuk
-
Patent number: 7149965Abstract: The object persister serializes an object to preserve the object's data structure and its current data. The serialized object is encoded using XML and inserted within a message. That message is transmitted to an entity over a network. Such a transmission is performed using standard Internet protocols, such as HTML. Upon receiving the serialized object, the receiving entity deserializes the object to use it. Rather than include copies of referenced objects within the serialized object, the object persister includes references to those objects. This avoids redundant inclusion of the same object and potentially infinite inclusion of the object itself that is being serialized.Type: GrantFiled: August 9, 2000Date of Patent: December 12, 2006Assignee: Microsoft CorporationInventors: Andrew J. Layman, Gopal Krishna R. Kakivaya, Satish R. Thatte
-
Patent number: 7085814Abstract: A general programmatic interface-to-network messaging adapter exposes a suitable object integration interface or application programming interface to applications on a controller device and sends network data messages to invoke services or query status of a controlled device. The adapter maps application calls to the interface into network data messages according to service protocols of the controlled device. The general adapter provides the interface suitable to any specific service of a controlled device based on a data description of the interface, and converts the application calls to network data messages based on a data description of a protocol and format for network data messages to interact with the specific service. Once the interface/messaging description is obtained, applications on the controller device can programmatically interact with the adapter, and the adapter then handles appropriate message exchanges with the service of the controlled device.Type: GrantFiled: November 2, 2000Date of Patent: August 1, 2006Assignee: Microsoft CorporationInventors: Amar S. Gandhi, Andrew J. Layman, Daniel R. Weisman, Shyamalan Pather, William Michael Zintel
-
Patent number: 7069335Abstract: Using a message exchanger (“message exchanger”), data messages are exchanged between entities in a decentralized, distributed, potentially heterogeneous, network environment. The message exchanger employs XML (extensible Markup Language). To accomplish this, the entities on both ends of the message exchange understand, identify, and parse the message format. The message exchanger defines such a mechanism. Data messages are broken down into two portions—one portion (the body) is intended from an ultimate destination and the other portion (the header) is intended for intermediate destination and/or the ultimate destination. The body may be defined so that it must be understood by the ultimate destination. The header may be defined so that it must be understood or changed. Regardless, the data in the body is delivered intact to the ultimate destination. The message exchanger defines a message envelope exchange format in XML over a transport protocol, such as HTTP (HyperText Transport Protocol).Type: GrantFiled: August 9, 2000Date of Patent: June 27, 2006Assignee: Microsoft CorporationInventors: Andrew J. Layman, Gopal Krishna R. Kakivaya, Satish R. Thatte, Henrik F. Neilsen, Robert George Atkinson
-
Publication number: 20040268242Abstract: Herein is described an implementation of an object persister, which serializes an object to preserve the object's data structure and its current data. The serialized object is encoded using XML and inserted within a message. That message is transmitted to an entity over a network. Such a transmission is performed using standard Internet protocols, such as HTML. Upon receiving the serialized object, the receiving entity deserializes the object to use it. Rather than include copies of referenced objects within the serialized object, the object persister includes references to those objects. This avoids redundant inclusion of the same object and potentially infinite inclusion of the object itself that is being serialized.Type: ApplicationFiled: July 16, 2004Publication date: December 30, 2004Applicant: Microsoft CorporationInventors: Andrew J. Layman, Gopal Krishna R. Kakivaya, Satish R. Thatte
-
Publication number: 20040268241Abstract: Here is described an implementation of an object persister, which serializes an object to preserve the object's data structure and its current data. The serialized object is encoded using XML and inserted within a message. That message is transmitted to an entity over a network. Such a transmission is performed using standard Internet protocols, such as HTML. Upon receiving the serialed object, the receiving entity deserializes the object to use it. Rather than include copies of referenced objects within the serialized object, the object persister includes references to those objects. This avoids redundant inclusion of the same object and potentially infinite inclusion of the object itself that is being serialized.Type: ApplicationFiled: July 16, 2004Publication date: December 30, 2004Applicant: Microsoft CorporationInventors: Andrew J. Layman, Gopal Krishna R. Kakivaya, Satish R. Thatte
-
Publication number: 20040261020Abstract: Herein is described an implementation of an object persister, which serializes an object to preserve the object's data structure and its current data. The serialized object is encoded using XML and inserted within a message. That message is transmitted to an entity over a network. Such a transmission is performed using standard Internet protocols, such as HTML. Upon receiving the serialized object, the receiving entity deserializes the object to use it. Rather than include copies of referenced objects within the serialized object, the object persister includes references to those objects. This avoids redundant inclusion of the same object and potentially infinite inclusion of the object itself that is being serialized.Type: ApplicationFiled: July 16, 2004Publication date: December 23, 2004Applicant: Microsoft CorporationInventors: Andrew J. Layman, Gopal Krishna R. Kakivaya, Satish R. Thatte
-
Publication number: 20030074472Abstract: An apparatus and method is provided for resolving virtual network names using one or more name routers. A conventional Uniform Resource Locator (URL) naming scheme is extended by allowing any component to be mapped to an address. The resolution process occurs recursively through a plurality of name routers. Resolution can be contextual, such that the same virtual network name may be resolved differently depending on the identity of the client or other parameters.Type: ApplicationFiled: October 24, 2001Publication date: April 17, 2003Inventors: Steven E. Lucco, Erik B. Christensen, Andrew J. Layman, David E. Levin, Bradford H. Lovering, Henrik Frystyk Nielsen, John P. Shewchuk
-
Publication number: 20030074413Abstract: A routing protocol is provided for exchanging messages between an initial sender and an ultimate receiver, potentially via a set of intermediaries. The routing protocol provides an optional reverse message path that enables two-way message exchange patterns. The routing protocol can be expressed as a header entry within a message envelope, is independent of the underlying protocol, and can be generated at the application layer of a protocol stack. The routing protocol may allow each intermediary to process the message and dynamically alter the message path en route to the intended recipient.Type: ApplicationFiled: October 15, 2002Publication date: April 17, 2003Applicant: Microsoft CorporationInventors: Henrik F. Nielsen, John P. Shewchuk, Erik B. Christensen, Alfred M. Lee, Christian Huitema, James M. Lyon, Mark H. Lukovsky, Andrew J. Layman, Satish R. Thatte, Christopher Kaler