WO2008042914A1 - Hierarchical federation metadata - Google Patents

Hierarchical federation metadata Download PDF

Info

Publication number
WO2008042914A1
WO2008042914A1 PCT/US2007/080223 US2007080223W WO2008042914A1 WO 2008042914 A1 WO2008042914 A1 WO 2008042914A1 US 2007080223 W US2007080223 W US 2007080223W WO 2008042914 A1 WO2008042914 A1 WO 2008042914A1
Authority
WO
WIPO (PCT)
Prior art keywords
federation
metadata
data structure
organization
inherited
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2007/080223
Other languages
English (en)
French (fr)
Inventor
Christopher G. Kaler
Arun K. Nanda
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Microsoft Corp
Original Assignee
Microsoft Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Microsoft Corp filed Critical Microsoft Corp
Priority to EP07843693.8A priority Critical patent/EP2080106B1/en
Priority to JP2009531565A priority patent/JP5028489B2/ja
Publication of WO2008042914A1 publication Critical patent/WO2008042914A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
    • G06F15/163—Interprocessor communication
    • G06F15/173—Interprocessor communication using an interconnection network, e.g. matrix, shuffle, pyramid, star, snowflake

Definitions

  • Computers and computing systems have affected nearly every aspect of modern living. Computers are generally involved in work, recreation, healthcare, transportation, entertainment, household management, etc. The functionality of computers has also been enhanced by their ability to be interconnected through various network connections.
  • Modern computers often include functionality for connecting to other computers.
  • a modern home computer may include a modem for dial- up connection to internet service provider servers, email servers, directly to other computers, etc.
  • nearly all home computers come equipped with a network interface port such as an RJ-45 Ethernet port complying with IEE 802.3 standards. This network port, as well as other connections such as various wireless and hardwired connections can be used to interconnect computers.
  • policies may be well known policies that are included in the software code of communication modules within a computing system.
  • the general policies may be readily ascertainable by reference to a known source.
  • a federation generally includes two or more organizations connected in a fashion such that authentication and authorization statements span the organizations in accordance with a pre-defined policy.
  • federation members generally need to understand additional information, such as structure or organization information.
  • the data structures may be implemented in a networked computing environment including federation.
  • a federation includes two or more organizations coupled in a fashion such that authentication and authorization statements span the organizations in accordance with a pre-defined policy.
  • a computer readable medium may include a data structure.
  • the data structure includes fields including at least one or more grouping of metadata about a first federation or about an organization within the first federation. At least one of the one or more groupings of metadata about the first federation or about an organization within the first federation are included in the data structure by a reference to a block of federation metadata, the block of federation metadata is used for at least one other federation or organization.
  • a computer readable medium includes a data structure.
  • the data structure includes fields including at least one or more grouping of metadata about a first federation or about an organization within the first federation.
  • At least one of the one or more groupings of metadata about the first federation or about an organization within the first federation is inherited federation metadata included by inheritance from metadata for a second federation hierarchically above the first federation. As such the inherited federation metadata is inherited from the second federation by the first federation.
  • Figure IA illustrates a common block of federation metadata used for two federations
  • Figure IB illustrates federation metadata obtained from an existing federation
  • Figure 1C illustrates federation metadata inherited hierarchically.
  • Embodiments herein may comprise a special purpose or general-purpose computer including various computer hardware, as discussed in greater detail below.
  • a data structure can be used.
  • the data structure includes fields including at least one or more grouping of metadata about a first federation or about an organization within the first federation. At least one of the one or more groupings of metadata about the first federation or about an organization within the first federation is included in the data structure by a reference to a block of federation metadata.
  • the block of federation metadata may be used for at least one other federation or organization.
  • federation metadata is inheritable.
  • Figure IA illustrates an example where a common metadata block 102 includes explicit metadata that is included by reference in the federation metadata of different federations.
  • Figure IA illustrates an organization 104 and an organization 106.
  • Organization 1 104 and organization 2 106 are organized into a federation named federation 1.
  • Information about the organization and structure of federation 1 is a block of federation 1 metadata 108.
  • the federation 1 metadata 108 includes a reference to the common metadata block 102.
  • the metadata in the common metadata block 102 is included in the federation 1 metadata 108 by reference to the common metadata block 102.
  • the federation 1 metadata 108 may include a pointer to explicitly defined metadata in the common metadata block 102.
  • Figure IA further illustrates a second federation, federation 2.
  • Federation 2 includes organization 3 110 and organization 4 112.
  • a block of federation metadata, federation 2 metadata 114 includes metadata, such as structure and organization metadata, for federation 2.
  • Federation 2 metadata 114 includes the metadata in the common metadata block 102 by reference.
  • Figure IA illustrates one example where metadata is explicitly set forth in one location, the common metadata block 102, but is included in metadata for a number of different federations.
  • federation metadata included by reference is included by virtue of a reference to a federation identifier identifying a second federation.
  • Figure IB illustrates an example where federation metadata may be included by reference to an existing federation.
  • Figure IB illustrates a federation 1 that includes organization 1 104 and organization 2 106.
  • Federation 1 metadata 108 is used to describe information about federation 1.
  • Figure IB illustrates a second federation, federation 2.
  • Federation 2 includes organization 3 110 and organization 4 112.
  • Federation 2 metadata 114 is used to describe information about federation 2.
  • the federation 1 metadata 108 is included, by reference, in the federation 2 metadata 114 as illustrated by the broken arrow directed from federation 1 metadata 108 to federation 2 metadata 114.
  • federation metadata may include other federation metadata by reference to the other federation.
  • reference may be made to a federation identifier.
  • federation 2 metadata 114 may include federation 1 metadata 108 by reference to the federation identifier for federation 1.
  • federation metadata for multiple federations can be used, by reference to the federations, as federation metadata for another federation.
  • federation metadata is included by reference to a name structure.
  • reference can be made to the structure of other federations.
  • reference to a name structure for federation 1 can be expressed as Organization 1 -Organization2.
  • Reference to a name structure for federation 2 can be expressed as
  • Reference to a name structure for federation 3 can be expressed as Organization 1/Team2/Group2- Organization2/Team3/Group3.
  • Reference to a name structure for federation 4 may be expressed as Organizationl/Team2/Group2/Individual2-Organization2/Team3/ Group3/Individual3.
  • federation metadata included by reference is included by virtue of a reference to a physical location.
  • a reference may be made to a geographic physical location, such as for example Seattle, WA.
  • a specific block of metadata specific to that location may be included by a reference to Seattle, WA. This reference will cause a common metadata block to be included by reference in the federation metadata.
  • the federation metadata included by reference is obtained from a service endpoint reference.
  • Explicit federation metadata included in the federation metadata by reference is embedded within the service endpoint.
  • federation metadata may be obtained from the service endpoint by reference to the service endpoint.
  • federation metadata included by reference may be fetched from a well known address given a target service address.
  • Explicit federation metadata included in the federation metadata included by reference may be obtained by reference to attributes in a directory.
  • directory services such as UDDI, DNS, or LDAP may include attributes which include the federation metadata that is included by reference.
  • FIG 1C an example is illustrated where federation metadata is inherited hierarchically.
  • Figure 1C illustrates a federation 1 which includes organization 1 104 and organization 2 106.
  • Federation 1 metadata 108 includes information about federation 1.
  • Organization 1 104 can be subdivided, in this example, into at least two teams, team 1 116 and team 2 118.
  • organization 2 106 can be subdivided into at least two teams, team 3 120 and team 4 122.
  • teams 1 and 2 116 and 118 are hierarchically below organization 1 104.
  • team 3 120 and team 4 122 are hierarchically below organization 2 106.
  • Figure 1C illustrates another federation, federation 2, which includes team 2 and team 3.
  • Information about federation 2 is contained in federation 2 metadata 124.
  • Federation 2 metadata 124 is included in a data structure.
  • the data structure includes fields including at least one or more grouping of metadata about federation 2 or about an organization within federation 2. At least one of the groupings of metadata about the first federation or about an organization within the first federation is inherited federation metadata included by inheritance. In this example, from federation 1 metadata for a federation 1 hierarchically above federation 2. As such the inherited federation metadata is inherited from the federation 2 by federation 1.
  • FIG. 1C Further examples of inherited metadata are illustrated in Figure 1C.
  • a federation 3 including group 2 126, which is hierarchically below team 2, and group 3 128, which is hierarchically below team 3 120 is shown.
  • federation 3 is hierarchically below federation 2.
  • federation 3 metadata 130 includes federation 2 metadata 124.
  • federation 4 which includes individual 2 132 and individual 3 134 is hierarchically below federation 3.
  • federation 4 metadata 136 includes federation 3 metadata 130, federation 2 metadata 124, and federation 1 metadata 108.
  • Embodiments may also include computer-readable media for carrying or having computer-executable instructions or data structures stored thereon.
  • Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer.
  • Such computer-readable media can comprise physical computer readable media such as RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer.
  • Computer-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • General Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Economics (AREA)
  • Human Resources & Organizations (AREA)
  • Tourism & Hospitality (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Business, Economics & Management (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • General Engineering & Computer Science (AREA)
  • Marketing (AREA)
  • Software Systems (AREA)
  • Mathematical Physics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Medical Treatment And Welfare Office Work (AREA)
PCT/US2007/080223 2006-10-05 2007-10-02 Hierarchical federation metadata Ceased WO2008042914A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP07843693.8A EP2080106B1 (en) 2006-10-05 2007-10-02 Hierarchical federation metadata
JP2009531565A JP5028489B2 (ja) 2006-10-05 2007-10-02 階層的フェデレーションメタデータ

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US11/538,916 2006-10-05
US11/538,916 US7676586B2 (en) 2006-10-05 2006-10-05 Hierarchical federation metadata

Publications (1)

Publication Number Publication Date
WO2008042914A1 true WO2008042914A1 (en) 2008-04-10

Family

ID=39268809

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2007/080223 Ceased WO2008042914A1 (en) 2006-10-05 2007-10-02 Hierarchical federation metadata

Country Status (6)

Country Link
US (1) US7676586B2 (https=)
EP (1) EP2080106B1 (https=)
JP (1) JP5028489B2 (https=)
KR (1) KR20090074023A (https=)
CN (1) CN101523375A (https=)
WO (1) WO2008042914A1 (https=)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2011527482A (ja) * 2008-07-07 2011-10-27 マイクロソフト コーポレーション クレームを使用したセキュリティアイデンティティの表示

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9389922B2 (en) 2011-03-11 2016-07-12 International Business Machines Corporation Declarative service domain federation
US8510807B1 (en) * 2011-08-16 2013-08-13 Edgecast Networks, Inc. Real-time granular statistical reporting for distributed platforms
US9410712B2 (en) * 2014-10-08 2016-08-09 Google Inc. Data management profile for a fabric network
CN105225060A (zh) * 2015-10-19 2016-01-06 福建星网锐捷通讯股份有限公司 有继承性的统一管理配置方法和装置
US11138184B2 (en) 2017-04-26 2021-10-05 Bank Of America Corporation Maintaining data integrity and referential data integrity within an enterprise data registry
KR20190092901A (ko) 2018-01-31 2019-08-08 주식회사 데이터스트림즈 SparkSQL 기반의 데이터 페더레이션장치
US12530366B2 (en) * 2023-11-10 2026-01-20 Oracle International Corporation Federation of disparate datasets hosted across separate servers

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6151624A (en) * 1998-02-03 2000-11-21 Realnames Corporation Navigating network resources based on metadata

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5535322A (en) 1992-10-27 1996-07-09 International Business Machines Corporation Data processing system with improved work flow system and method
US6792605B1 (en) 1999-06-10 2004-09-14 Bow Street Software, Inc. Method and apparatus for providing web based services using an XML Runtime model to store state session data
US6917944B1 (en) * 2001-08-30 2005-07-12 Cisco Technology, Inc. Method and apparatus for configuring access to a plurality of data repositories
US7221935B2 (en) * 2002-02-28 2007-05-22 Telefonaktiebolaget Lm Ericsson (Publ) System, method and apparatus for federated single sign-on services
US7065527B2 (en) 2002-06-26 2006-06-20 Microsoft Corporation Systems and methods of optimizing metadata publishing system updates by alternating databases
US7051038B1 (en) 2002-06-28 2006-05-23 Microsoft Corporation Method and system for a reporting information services architecture
US7730182B2 (en) 2003-08-25 2010-06-01 Microsoft Corporation System and method for integrating management of components of a resource
US20050050057A1 (en) 2003-08-25 2005-03-03 Microsoft Corporation System and method for integrating management of resources between application services and applications
US7539686B2 (en) 2004-03-12 2009-05-26 Microsoft Corporation Tag-based schema for distributing update metadata in an update distribution system
US20060021017A1 (en) * 2004-07-21 2006-01-26 International Business Machines Corporation Method and system for establishing federation relationships through imported configuration files
US7613703B2 (en) * 2004-09-30 2009-11-03 Microsoft Corporation Organizing resources into collections to facilitate more efficient and reliable resource access
US7653694B2 (en) 2004-12-15 2010-01-26 Microsoft Corporation E-mail containing a web-based form
US7950023B2 (en) 2005-02-04 2011-05-24 Microsoft Corporation Utilizing abstract descriptions to generate, exchange, and configure service and client runtimes
US8499028B2 (en) 2005-02-23 2013-07-30 International Business Machines Corporation Dynamic extensible lightweight access to web services for pervasive devices

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6151624A (en) * 1998-02-03 2000-11-21 Realnames Corporation Navigating network resources based on metadata

Non-Patent Citations (9)

* Cited by examiner, † Cited by third party
Title
"PROCEEDINGS OF THE WORKSHOP ON PARALLEL AND DISTRIBUTED SIMULATION", 15 May 2001, IEEE COMP. SOC, pages: 67 - 74
CAI W. ET AL.: "Hierarchical Federations: an Architecture for Information Hiding", PROCEEDINGS OF 15TH WORKSHOP ON PARALLEL AND DISTRIBUTED SIMULATION, 2001, pages 67 - 74, XP010543391 *
LOS ALAMITOS, CA, USA,IEEE COMPUT. SOC, US, vol. 1, 7 January 1997 (1997-01-07), pages 44 - 53
PROCEEDINGS OF 6TH INTERNATIONAL WORKSHOP ON DISTRIBUTED SIMULATION AND REAL-TIME APPLICATIONS, 2002, XP010624268 *
PROCEEDINGS OF THE THIRTIETH HWAII INTERNATIONA L CONFERENCE ON WAILEA, HI, USA, 7 January 1997 (1997-01-07)
ROANTREE M ET AL.: "A three-layer model for schema management in federated databases", SYSTEM SCIENCES, 1997
ROANTREE M. ET AL.: "A Three-Layer Model for Schema Management in Federated Database", PROCEEDINGS OF THE 30TH HAWAII INTERNATIONAL CONFERENCE ON SYSTEM SCIENCES, vol. 1, 7 January 1997 (1997-01-07) - 10 January 1997 (1997-01-10), pages 44 - 53, XP010272030 *
See also references of EP2080106A4
WENTONG CAI ET AL.: "Hierarchical federations: an architecture for information hiding", PROCEEDINGS 15TH. WORKSHOP ON PARALLEL AND DISTRIBUTED SIMULATION. PADS 2001. LAKE ARROWHEAD, CA, 15 May 2001 (2001-05-15)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2011527482A (ja) * 2008-07-07 2011-10-27 マイクロソフト コーポレーション クレームを使用したセキュリティアイデンティティの表示
US8910257B2 (en) 2008-07-07 2014-12-09 Microsoft Corporation Representing security identities using claims

Also Published As

Publication number Publication date
EP2080106B1 (en) 2021-09-08
EP2080106A4 (en) 2012-07-11
EP2080106A1 (en) 2009-07-22
JP5028489B2 (ja) 2012-09-19
US20080086486A1 (en) 2008-04-10
KR20090074023A (ko) 2009-07-03
JP2010506305A (ja) 2010-02-25
US7676586B2 (en) 2010-03-09
CN101523375A (zh) 2009-09-02

Similar Documents

Publication Publication Date Title
EP2080106A1 (en) Hierarchical federation metadata
CN101102257B (zh) 传输数据对象的方法和装置
CN101127606B (zh) 传输数据对象的方法和装置
US9015493B2 (en) Multitenant-aware protection service
US20080083009A1 (en) Policy fault
US20140289829A1 (en) Computer account management system and realizing method thereof
US8683545B2 (en) Federating policies from multiple policy providers
EP1829316B1 (en) Means and method for control of personal data
RU2010116037A (ru) Платформа составных приложений на базе модели
WO2008045759A1 (en) Client-based pseudonyms
CN104754009A (zh) 一种服务获取调用方法、装置以及客户端和服务器
WO2009108450A2 (en) Centralized publishing of network resources
Moldovan et al. An IoT middleware for enhanced security and privacy: the RERUM approach
US7860983B1 (en) Enterprise identity orchestration server
Gummadi et al. Modeling group trust for peer-to-peer access control
US20120159571A1 (en) Methods, systems, and computer program products for authenticating an entity through use of a global identity of the entity that serves as a proxy for one or more local identities of the entity
US20100332604A1 (en) Message selector-chaining
WO2008042916A1 (en) Issuance privacy
Habiba et al. Assessment criteria for cloud identity management systems
WO2014160993A1 (en) Coupling application data with network connectivity
US20120079088A1 (en) Proving domain name ownership
Ouardi et al. Technical and semantic interoperability in the cloud broker
JP2009518883A (ja) 分散サービスサイトの登録方法および登録システム
Zhao et al. An efficient privacy preserving location based service system
Distefano et al. Guest editors' introduction: Special section on cloud computing assessment: Metrics, algorithms, policies, models, and evaluation techniques

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200780037493.4

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07843693

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 1020097006430

Country of ref document: KR

WWE Wipo information: entry into national phase

Ref document number: 1766/CHENP/2009

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 2009531565

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2007843693

Country of ref document: EP