Microsoft Technology Licensing, LLC

Versata Development Group, Inc.

Elliot Lee Waingold

Erik B Christensen

Kenneth David Wolf

Giovanni Moises Della-Libera

Christopher G Kaler

Michael Steven Vernal

Stephen James Millet

Tomasz Janczuk

Douglas M Purdy

Yaniv Pessach

David Wortendyke

Jeffrey C Schlimmer

Michael James Coulson

Stefan Harrington Pharies

Craig Andrew Critchley

Vijay Gajjala

Uday Sooryakant Hegde

Stephen T Swartz

Martin James Gudgin

Shy Cohen

Aaron Stern

Siddhartha Puri

Mauro Ottaviani

Luis Felipe Cabrera

Donald F Box

James Ernest Johnson

Tirunelveli R Vishwanath

Lance Olson

David E Langworthy

Richard Douglas Hill

Umesh Madan

Stefan R Batres

John Raymond Justice

John David Doty

Alfred Lee

Michael Marucheck

Krishnan Srinivasan

Geary L Eppley

Matthew Thomas Tavis

David Edwin Levin

Max A Feingold

Richard Dievendorff

Eric Kenneth Zinda

Natasha Harish Jethanandani

David Owen Driver

Saurab Nog

Gopal Kakivaya

Jesus Ruiz-Scougall

Anastasios Kasiolas

Douglas A Walter

John Robert Lambert

Kapil Gupta

Ashok Malhotra

Vipul A Modi

Ryan Thomas Sturgell

Alexander Martin DeJarnatt

Sowmyanarayanan K Srinivasan

Scott Christopher Seely

Jonathan T Wheeler

Mohammad Makarechian

Evgeny Osovetsky

Chaitanya Dutt Upadhyay

Michael Thomas Dice

Erin Honeycutt

Alfred McClung Lee, Iv

Eugene Shvets

Alfred M Lee, Iv

Yasser Shohoud

Jeffery C Schlimmer

Anand Rjagopalan

Mohamed-Hany Essam Ramadan

Serge Sverdlov

Vaithialingam B Balayogan

Embodiments described herein provide for allowing processing code of a message to attach state thereto. More specifically, as a SOAP message is processed, various states known as properties (e.g., message security, message identifier, etc.) can be attached to the message for various purposes. In other words, embodiments provide for a properties object that represents a set of processing-level annotations to a message. These properties (representing the processing state of the headers or other portions of the message) can then be used by other component or modules for further processing purposes. Typically, these properties can then be removed (or sustained if desired) prior to transporting the SOAP message on the wire.

Annotating portions of a message with state properties

A mechanism for sending structured data using a corresponding byte stream. Upon accessing structured data such as a Simple Object Access Protocol (SOAP) envelope, a byte stream is generated. The byte stream includes bytes that represent the structured data, as well as a collection of bytes that represents properties about the byte stream such as, for example, a mode of communication. The byte stream may then be passed to a communication module (e.g., a TCP or Named Pipes module) capable of receiving and transmitting the byte stream.

Mechanism for binding a structured data protocol to a protocol offering up byte streams

A system and method for applying a people network representation to aid contact between a member of an organization and a target individual selects a contact path between the member and the target supported by analysis of the level of interaction between members of the organization based on network communications of the organization. Level of interaction is analyzed using network communications that take into account the recentness and frequency of interactions, such as email, ICQ, or phone interaction. To contact a targeted individual, for instance such as to obtain expertise in a desired area, the model of the people network allows determination of a contact path between the member and target which improves the likelihood of obtaining the target's expertise. A contact path from a member may include a suggestion to contact the target through one or more intervening organization members.

System and method for modeling and applying a people network representation

Methods, systems, and data structures for communicating object metadata are provided. A generic metadata container is presented that allows object metadata to be described in an extensible manner using protocol-neutral and platform-independent methodologies. A metadata scope refers to a dynamic universe of targets to which the included metadata statements correspond. Metadata properties provide a mechanism to describe the metadata itself, and metadata security can be used to ensure authentic metadata is sent and received. Mechanisms are also provided to allow refinement and replacement of metadata statements. The generic metadata container can be adapted to dynamically define access control rights to a range of objects by a range of users, including granted and denied access rights.

Scoped access control metadata element

The present invention provides for an automated, user friendly way of constructing and using a binding object. A developer is presented with and selects binding elements that will ultimately be used to create a runtime communication channel for transporting a message between a client and service endpoint. After receiving the user input, metadata, a channel factory and listener factory are created. The metadata describes binding elements and provides an abstract representation of a protocol stack that implements communication aspects at runtime. The channel factory is configured to use the collection of metadata at runtime to generate the runtime communication channel. Further, the listener factory is configured to accept the runtime communication channel for de-multiplexing the communication aspects in order to process the message at a service endpoint. The present invention also provides for groupings of binding elements and standardized binding objects organized based on industry need.

System and method for building and using communication binding objects

Embodiments described herein provide a user with the ability to vary the encoding of a message object rather than being bound to a specific one, e.g., the text encoding for SOAP messaging. Accordingly, a message encoding factory is provided that is responsible for mapping a message object (e.g., SOAP Infoset) into raw octets suitable for wire transmission. By encapsulating the notion of a message encoder factory abstractly, embodiments allow users to vary the encoding of an Infoset without varying the programming model (or any other aspect of the system that uses message). In other words, embodiments herein separate the transport (e.g., TCP, HTTP, etc.) from the encoding, which allows users to use any number of encoding mechanisms&#x2014;even their own proprietary ones.

Varying of message encoding

A listener operating in user-mode can dispatch control of a client connection to a listener without exposing system memory or other sensitive services or components. For example, a client component requests access to a network component through connection with a user-mode listener. Based on information contained in the client request, the listener passes a call to an application program interface, which returns a first set of data that includes user-mode contextual information. The listener passes this first set of data to the requested network component. Another call is made to an application program interface, which includes the first set of data, and a request for socket duplication. The application program interface returns control of the requested socket to the network component, such that the network component and the client component communicate directly through the requested socket in user-mode.

Dispatching network connections in user-mode

A system for processing multiple types of security schemes includes a server having a claims engine that extracts claim(s) from security token(s) and maps extracted claims to other claims. The term claim as used in this context is a statement about a token's subject. The claims engine can extract claim(s) from one or more different types of security tokens corresponding to the multiple security schemes. These extracted claim(s) can then be selectively mapped to other claims using mapping information that is accessible to the server. The security decision can then be based on the extracted and/or derived claim(s) rather than tokens. This system can thereby support multiple security schemes and simplify the security process for the user.

Generic security claim processing model

The present invention provide for an algebraic mapping of a policy expression from a compact to a normalized form, both in Boolean and set formulations. The policy algebra is defined in such a way that policy alternatives within the normalized expression will be the same across equivalent compact expressions&#x2014;regardless of how the assertions are arbitrarily constrained or what operators are used to constrain such equivalent expressions. Moreover, the present invention also provides a model for identifying alternatives that are equivalent by comparing only the root element names or QName of each assertion within an alternative. In addition, embodiments as described herein can utilize the identification of equivalent alternatives in order to create an intersection policy expression to limit alternatives of admissible behavior to those in common across both endpoints.

Policy algebra and compatibility model

A system and method for applying a people network representation to aid contact between a member of an organization and a target individual selects a contact path between the member and the target supported by analysis of the level of interaction between members of the organization based on network communications of the organization. The people network of the organization is modeled. Level of interaction is analyzed using network communications that take into account the recentness and frequency of interactions, such as email, ICQ, or phone interaction. To contact a targeted individual, for instance such as to obtain expertise in a desired area, the model of the people network allows determination of a contact path between the member and target which improves the likelihood of obtaining the target's expertise. A contact path from a member may include a suggestion to contact the target through one or more intervening organization members.

A web services namespace pertains to an infrastructure for enabling creation of a wide variety of applications. The infrastructure provides a foundation for building message-based applications of various scale and complexity. The infrastructure or framework provides APIs for basic messaging, secure messaging, reliable messaging and transacted messaging. In some embodiments, the associated APIs are factored into a hierarchy of namespaces in a manner that balances utility, usability, extensibility and versionability.

Interface infrastructure for creating and interacting with web services

A sending computer system can identify one or more available network resources at one or more network computers by sending a request for services using Simple Object Access Protocol (SOAP) over User Datagram Protocol (UDP). In particular, the sending computer system prepares a SOAP message that includes a request for available resources. The sending computer system then encapsulates the SOAP message into a user datagram, and sends the user datagram to one or more identifiable computer systems on the network. In one implementation, the sending computer system sends the user datagram to a multi-cast Uniform Resource Identifier (URI). The receiving computer system receives the message through UDP, unpacks the message, and responds to the SOAP message request. Accordingly, the sending computer system can query multiple computer systems in an efficient manner without necessarily incurring the overhead otherwise associated with connection-oriented communication.

Querying for services using soap over UDP

A plurality of message processors exchange public and secret information. Based on the exchanged information, each message processor computes a key sequence such that any one of a plurality of keys may be derived from the key sequence depending on key derivation data. A first message processor generates key derivation data that can be used to derive a particular key from among the plurality of keys. The first message processor sends a security token that includes the generated key derivation data to express to at least one other message processor how to derive the particular key from the computed key sequence. At least a second message processor receives the security token expressing how to derive the particular key from the computed key sequence. The first and/or second message processors apply the key derivation data to the computed key sequence to derive the particular key.

Deriving keys used to securely process electronic messages

Growing community of inventors

Seattle, WA, United States of America

Elliot Lee Waingold