Microsoft Technology Licensing, LLC

Microsoft Corportion

Max L Benson

Darren Arthur Shakib

Kim Cameron

Scott Norin

James H Booth

Matthias Adam Leibmann

Edward H Wayt

Felix W Wong

Stewart P MacLeod

Hilal Al-Hilali

Jonathan Fischer

Jing Wu

Jie Jerry Liu

Brian Thomas Berkowitz

Dinarte R Morais

Milind Madhukar Joshi

Thomas F Fakes

William H Rockenbeck

Derek Christopher Murman

Mark Robbin Brown

John Hal Howard

John Hillary Zybura

Peter E Durham

Jeffrey A Bisset

Michael S Jerger

Herman John Man

Ramesh Babu Pabbati

Miu Fung Apacible

Patrick Y Ng

Robert Dan Thompson, Iv

Robert Dan Thompson

Kenneth Mark

Robert Dan Thompson Iv

Kevin Ralph Miller

William P Champion

Various exemplary metadirectories, systems and/or methods include delta information, error information and/or state information to facilitate metadirectory administration and/or operation. An exemplary metadirectory relies on a hologram and a plurality of deltas to represent information related to an object of a directory. Such an exemplary metadirectory may represent the object in association with one or more processing states based on the hologram and one or more of the plurality of deltas. Various other exemplary metadirectories, systems and/or methods are also disclosed.

Associating and using information in a metadirectory

Exemplary methods, devices, systems, and/or storage media for organizational data management, including staging, synchronizing, and exporting of organizational data. Exemplary data aggregation rules specify methods for aggregating data from a remote repository. Schemas are exemplary rules configuration data structures having elements for associating processing data objects in a buffer space objects in a core space. The elements may also specify importing attributes into and exporting attributes from the core space.

Declarative rules for metadirectory

Exemplary techniques are described for configuring a metadirectory system used to interact with a collection of connected directory sources via a respective collection of management agents. The techniques can involve importing new management agents to the metadirectory system, updating existing management agents, or configuring the entire metadirectory system (which can involve adding or updating plural management agents). Techniques are provided for ensuring that the configuration of the metadirectory system provides partitions which conform to expected partitions associated with existing management agents and/or connected directory sources.

Configuration of a directory system

Described are mechanisms and techniques for enabling incremental non-chronological synchronization of namespaces. In an environment, entities must have unique names within a namespace and entities may only refer to entities that actually exist within the namespace. Synchronizing two such namespaces involves providing a mechanism for indicating that an entity has been created because a reference to that entity has been made even though that entity does not yet exist. At such time as the entity is formally created, the indication is removed. Synchronizing two such namespaces also involves providing a mechanism for indicating that an entity's unique name in the namespace has been compromised through the synchronization process.

Incremental non-chronological synchronization of namespaces

Exemplary methods and systems provide a relational directory of organizational information. Organizational data objects and their associated attributes are maintained in a relational directory. An organizational hierarchy is converted to a relational directory using projection, joining, and import attribute flow rules. Attributes in a relational directory may be exported out of the relational directory to a hierarchical directory.

Relational directory

Systems and methods for extending a directory schema independent of schema modification are described. In one aspect, a directory schema data structure includes a flexible attribute data field. The flexible attribute data field identifies a complex data type. The complex data type is used to express one or more operational or data providing properties of a flexible attribute. The one or more operational or data providing properties are independent of the complex data type and independent of directory schema modification. The directory schema data structure also includes a flexible structural object content class to encapsulate the flexible attribute.

Extending a directory schema independent of schema modification

Systems and methods for populating attribute value fields in an entity object employ in a ranked list of transfer options to determine which of a plurality of transfer options will be used to populate the attribute value fields in the entity object.

Attribute value selection for entity objects

Various exemplary metadirectories, systems and/or methods include or allow for executing a software module on an execution engine, emitting semantic information based on the executing, and analyzing the executing using the semantic information. An exemplary execution engine includes an input for receiving software modules, an output for emitting semantic information, and an output for outputting generated output information. Upon execution, an exemplary software module may cause processing of information in a metadirectory and emitting of semantic information pertaining to the processing. Various exemplary metadirectories, systems and/or methods emit and/or store semantic information in a self-defining language, an extensible language, and/or a markup language. Other exemplary metadirectories, systems, and/or methods are also disclosed.

Preview mode

Subject matter includes exemplary flexible rules for defining an information management process, for example a process that manages information being transferred between databases or with respect to an exemplary metadirectory. The flexible rules have inherent logic to define part of an information management action or a database structure and perform a call out for custom logic. The custom logic performs or defines another part of the information management action or database structure. Besides the exemplary flexible rules, the subject matter describes exemplary identity information management processes, engines, and related methods.

Rules customization and related methods

The described arrangements and procedures provide a directory schema with object classes that have flexible attributes. This means that attributes can be extended independent of modifications to the directory schema. Specifically, an object instance of a content class described in the directory schema is instantiated. The content class includes a flexible attribute having a data type. A property is assigned to the attribute. The property is any combination of an operational and data providing property. The property is independent of the attribute's data type. Thus, without modifying the directory schema, multiple instances of the same object class can have attributes that provide completely different data types and completely different data operations.

Calls to a server computer in a system that includes a client computer and a server computer connected to each other by a network are processed at the client computer by receiving information identifying first and second calls to the server computer. This information is combined to form a request that is then transmitted to the server computer over the network.

Multiple procedure calls in a single request

A system and method for incremental change synchronization among multiple copies of data is disclosed. To achieve the synchronization a genera synchronization model is used. The synchronization model establishes a one-way data flow path to allow incremental changes to be transferred from a copy of data that incorporates the incremental changes to a copy of data that does not yet incorporate the incremental changes. To achieve this one-way data flow path, the synchronization model uses an agent, a data collector, and a data synchronizer. The data collector collects incremental changes transferred to it and applies the incremental changes to a copy of data. A data synchronizer transfers incremental changes to a data collector. An agent controls the synchronization process by making a connection between a data collector and a data synchronizer and then directing the data synchronizer to transfer data to the data collector. If bidirectional data flow is necessary to achieve synchronization between two copies of data, a one-way data flow path is established first in one direction and after all incremental changes have been passed in that direction, a data flow path is established in the opposite direction to pass incremental changes in the opposite direction.

System and method for incremental change synchronization between multiple copies of data

In one aspect, the disclosed technique detects common leading byte patterns in the integers so that these patterns need only be stored once in the encoded byte stream. Those integers that share a common leading byte pattern are stored in truncated form, without their common leading bytes. These truncated integers may themselves be further examined to determine if any of them share additional common leading bytes beyond those already detected. Thus, the technique lends itself naturally to description using the language of trees. Integers with a common leading byte pattern are stored as child nodes, their parent being the node containing the common byte pattern. Child nodes consist only of those bytes remaining after the initial byte pattern has been extracted; the greater the number of children, the greater are the efficiency gains. All the children of a given tree or subtree are similarly examined for common leading byte patterns, ignoring those bytes that are already accounted for in their ancestor nodes. In a second aspect, the disclosed technique makes use of 'clustering', a second type of locality that is not reached by the interval concept. A cluster is a sequence of singleton integers that are very close together but do not form a contiguous interval. The technique recognizes that such a cluster can be compactly stored as a bitmap, in which each active bit ('1-bit') represents a member of the cluster. The choice of bitmap size (e.g., 1 byte, 2 bytes, etc.) can be calibrated to suit the clustering characteristics of the input data set.

Compressing sets of integers

A messaging system user's mailbox is moved using a method in which the mailbox is flagged as being moved and a message arriving for the user during the move is delivered to a holding area to await re-delivery to the mailbox after the move is completed. A combination of non-volatile memory and volatile memory is used to ensure the message's delivery in the event of a power loss or other system failure.

Growing community of inventors

Redmond, WA, United States of America

Max L Benson