X.500/LDAP as OID and URN resolver Erik Andersen Andersens L-Service [email protected].

X.500/LDAPas OID and URN

resolver

Erik AndersenAndersen’s L-Service

[email protected]

Hierarchical idenditiesHierarchical idendities

Object Identifiers (OIDs) uniquely identifies object by recognising the hierarchical structure of objects

Uniform Resource Names (RDNs) uniquely identifies object by recognising the hierarchical structure of objects

Directory Distinguished Names uniquely identifies object by recognising the hierarchical structure of objects

According, these identifiers can be mapped into each other

However - - -

Mapping to the DITMapping to the DIT

The Directory Distinguished Name is not only a hierarchical identity scheme

The Directory Information Tree information model is tightly related to Directory Distinguished Names

Information may be associated with each component of a Distinguished Name by being stored in the corresponding

entry of the Directory Information Tree

Information typesInformation types

Q: What kind information can you store?

A: Any type!

Text;photos;speech; certificates; andwhat ever may be represented in a digital form

Possible DIT subtree representing object identifier Possible DIT subtree representing object identifier componentscomponents

”oidC2obj”oidC2-attr=27

”oidCobj”oidC-attr=

10891


15459


15961

”Object class (type of entry)” Attribute with value (entry content)

Root of Directory Information Tree

(DIT)




”oidCobj”oidC-attr=8






”oidCobj”oidC-attr=n1




(iso)(itu-t) (joint-iso-itu-t)

DIT subtree of OIDs defined as URNs DIT subtree of OIDs defined as URNs


(DIT)

”urnC1obj”urnC1="oid"

”urnCobj”urnC="0"












”Object class (type of entry)” Attribute with value (entry content)

Representing URNs in LDAP/X.500 Representing URNs in LDAP/X.500


(DIT)

”urnC1obj”urnC1="iso"

”urnC1obj”urnC1="epc"

”urnC2obj”urnC2="id"

”urnC2obj”urnC2="std"

”urnCobj”urnC="iso-iec"

”urnCobj”urnC="iec"

”urnCobj”urnC="iso"

”urnCobj”urnC="sgtin"

”urnCobj”urnC="grai"

”urnCobj”urnC="gsrn"

”urnCobj”urnC="sscc"

”urnCobj”urnC="giai"

”urnCobj”urnC="gdti"”urnCobj”

urnC="9594"”urnCobj”

urnC="8824"”urnCobj”

urnC="15459"

”urnCobj”urnC="-1"






X.500/LDAP directory support for

Tag-based applications

Erik AndersenAndersen’s L-Service

[email protected]

RFID Information AcquisitionRFID Information Acquisition

1. Some kind of object has an Radio Frequency Identification (RFID) tag attached

2. The RFID ID-tag is read by tag reader (ID terminal)

3. Information associated with the object is retrieved from some information provider using the RFID tag information as key

X.500/LDAP as the information provider

Use of Directory technologyUse of Directory technology

AIDC media ID terminal

Directory infrastructure

DUA orLDAP client

AIDC client system

LDAP/X.500 advantagesLDAP/X.500 advantages

By use of off-the-shelf software.

Use of well known technology.

In some cases:a single access allows retrieval of the information associated with an RFID tag or it allows retrieving a URL for the associated information.

it is not necessary to convert the UII to URN format.

Relevant pieces of information may be represented by directory attributes

Has extensive search and filter capabilities.

Possibility for return of diverse and complex data structures.

Extensive security functions (important in many situations, e.g. For military applications).

Players and documentationPlayers and documentation

GS1 EPCglobal (http://www.epcglobalinc.org)

GS1 General Specifications, Version 10

EPCglobal Tag Data Standards, Version 1.5

ISO/IEC JTC1/SC31

ISO/IEC 15418, ISO/IEC 15459 Series, ISO/IEC 15961 Series, ISO/IEC 15962 , ISO/IEC 15963, ISO/IEC 18000 Series, ISO/IEC 19762 Series

The list is certainly not complete

Players and documentation (cont.)Players and documentation (cont.)

ISO TC 122

ISO 17363 to ISO 17367

ISO TC 104

ISO/TS 10891, ISO 10374

ITU-T Q.12/17 | ISO/IEC JTC1/SC6 WG9

ITU-T X.668 | ISO/IEC 9834-9

ITU-T SG 13

ITU-T Y.2213

The list is certainly not complete

Common Working Group

18000-6C & 3m3, Memory structure18000-6C & 3m3, Memory structure

¥

Data Objects formatted:Precursor, [OID], length,ObjectSensors/Battery-assistSee ISO/IEC 15961and ISO/IEC 15962

MDIDPart numberSerial numberBurned in or writtenand permalocked byIC manufacturer

¥

¥¥

¥

¥

¥

Reserved

UII

TID

[User]

Memory Banks

CRC-16

UII(may be EPC)

Protocol Control

Access Password

Kill Password

[Extended Protocol Control]

00

01

10

11

[ ] = Optional

UII = Unique Item Identifier

Memory Bank 01’BMemory Bank 01’B

Cyclic Redundancy Check (16 bits)

Length(5 bits) UII

AFI (ISO)

Toggle bit: 0=EPC/1=ISO

Zero fillto Word

boundary

Protocol Control

Length in words (of 16 bits)

AFI = Application Family IdentifierEPC = Electronic Product CodeUII = Unique Item Identifier

(8 bits)

Reserved(EPC)$

(Confirms UII memory content)

Relevant tag information for Relevant tag information for directory supportdirectory support

In a RFID based application an ID-terminal reads data

from an ID-tag

From the point of this presentation, the data that is of

most interest is:

A toggle switch telling whether the tag content is defined by the GS1

EPC specifications or by ISO or ISO/IEC International Standards

The Unique Item Identifier (UII) – EPC UII or ISO UII

An Object Identifier (OID) and/or Application Family Identifier (AFI)

for ISO UIIs

Uniqueness of UIIUniqueness of UII

Header

A UII {EPC} is unique within the scope of EPC

EPC application is indicated by first octet (header) of UII

EPC:

UII

An Object Identifier + UII {ISO} is unique within the scope of ISO

ISO:

UII+OID

AFI

And/or

Toggle switch

A particular UII may have two formats:RFID binary formatA numeric character or alpha numeric format

GS1 EPCglobalGS1 EPCglobal

EPC Search using the EPC UII in a EPC Search using the EPC UII in a limited environmentlimited environment

epcUii

uiiInUrn

contentUrlor

<content>

X.500/LDAP

EPC UII Filter:epcUii

<content> | contentUrl

(uiiInUrn, tagLocation)

Data base

ID terminal

Attribute Value Assertions

Entry

tagLocation

AIDC media

Search using the (AFI, UII) tupleSearch using the (AFI, UII) tuple

tagOid

isoUii

uiiInUrn

contentUrlor

<content>

X.500/LDAP

AFI + UII Filter: tagAfi & isoUii

<content> | contentUrl

[uiiInUrn, tagOid, tagLocation]

Data base

ID terminal


Entry

tagAfi

tagLocation

AIDC media

SGTIN-96 PartitionsSGTIN-96 Partitions((Serialized Global Trade Item Number – 96 bits) Serialized Global Trade Item Number – 96 bits)

0 Company Prefix Serial NumberHeader

x’30’ F


x’30’ItemRef.F


x’30’ItemRef.F


x’30’Item

ReferenceF


x’30’Item

ReferenceF


x’30’Item ReferenceF


x’30’Item ReferenceF

Filter Partition44 bits 38 bits

Retrieving EPC UII format informationRetrieving EPC UII format information

X.500/LDAP

uiiFormat

Data base

ID terminal


EPC UII Filter: (epcHeader &epcPartition)

UII typeentry

epcHeader

epcPartition

uiiFormat

<Misc. Info>

AIDC media

Formatting informationFormatting information

The formatting information returned from the directory allows separation of UII into components

A printed character representation may be produced

A URN representaion of the UII may be generated

The URN DIT Subtree for EPC UIIsThe URN DIT Subtree for EPC UIIs

”urnC1obj”urnC1="epc"

”urnC2obj”urnC2="id"

”urnCobj”urnC="gsrn"

”urnCobj”urnC="grai"

”urnCobj”urnC="sgtin"

”urnCobj”urnC="sscc"

”urnCobj”urnC="giai"

”urnCobj”urnC="gdti"

”urnCobj”urnC="793591651

"


"


"





"


"


"

Company Prefix level

Item Reference level

Serial number level

”urnCobj”urnC="igln"

ISO/IEC 15459 Format retrievalISO/IEC 15459 Format retrieval

ISO/IEC 15459 Series specifies rules for identification of Transport Units

A Transport Unit is assigned a so-called license plate (UII)

A transport unit is handled by several parties, sender, receiver, carriers, customs authorities, etc.

Determination of length of UII components

General ISO/IEC 15459General ISO/IEC 15459Data Identifier formatData Identifier format

Company Identification

Number (CIN)Serial Number/Part Number

Data Identifier

Issuing Agency Code

IACDI

Data Identifier (DI):A specified character (or string of characters) that defines the

general category or intended use of the data that follows.Consists of one alphabetic character alone or prefixed by one to

three numeric characters Values registered by ANSI MH10.8.2Examples:

25S Id of a party identified by IAC and CIN followed by a Serial NumberJ Unique license plate number – unspecified – max 35 characters1 J to 6J Unique license plate number – different type of packeting / EDI data –

max 20 or 35 characters 25P Id of a party identified by IAC and CIN followed by a Part Number25B As for 25S for a returnable transport item

6 bits character encoding

Issuing Agency CodesIssuing Agency Codes

• A Issuing Agency is an entity for allocating identities to organisations (companies)

• An issuing Agency is given a unique Issuing Agency Code (IAC)

• The IAC together with the assigned organistion identity is globally unique identification of the organisation.

• IACs are allocated by Registration Authority, which currently is

NederlandsNormalisatie-instituut

List of assigned IACs may be found here: http://iso15459.nen.nl

http://iso15459.nen.nl/

Retrieving ISO UII format informationRetrieving ISO UII format information

X.500/LDAP

AFI and ISO UII Filter: (tagAfi & isoTagDi & isoTagIac)

uiiFormat

Data base

AIDCmedia ID terminal


tagOid

isoTagDi

uiiFormat

tagAfi

<Misc. Info>

UII typeentry

isoTagIac

URN generationURN generation

IANA registers URN name spaces, i.e. the first component after the lead urn: component.

Two registration of interest:epc - to generate a URN from an EPC UIIExample: urn:epc:id:sgtin:0614141.000024.400.

iso – to generate a URN from an ISO UII

Proposal for ISO/IEC 15459:urn:iso:std:iso-iec:15459.<DI>.<IAC>.<CIN>.<serial/part number>

Example:urn:iso:std:iso-iec:15459:25S.UN.043325711.MH803120000001

Company Identification Number (CIN)

Issuing Agency Code (IAC)Serial/part numberData Identifier (DI)

Representing URNs in LDAP/X.500 Representing URNs in LDAP/X.500



”urnCobj”urnC="iso-ieee"




”urnCobj”urnC="25B"

”urnCobj”urnC="25P"

”urnCobj”urnC="25S"

”urnCobj”urnC="J"

”urnCobj”urnC="1J"




”urnCobj”urnC="KDK"

”urnCobj”urnC="OD"

”urnCobj”urnC="SI"

”urnCobj”urnC="UN"

”urnCobj”urnC="VIB"




”urnCobj”urnC="MH803120000001"



Data Identity level

Issuing Agency Code level

Company Identifi-cation Number level

Serial/Part Number level

Use of digital signatureUse of digital signature

tagOid

isoUii

uiiInUrn

contentUrlor

<content>

X.500/LDAP

AFI + UIISigned Info

Filter: tagAfi & isoUii

<content> | contentUrlpkiPath

[uiiInUrn, tagOid, tagLocation]

Data base

ID terminal


Entry

tagAfi

tagLocation

AIDC media

pkiPath

Distribution of URN subtreeDistribution of URN subtree



”urnCobj”urnC="iso-ieee"




”urnCobj”urnC="25B"

”urnCobj”urnC="25P"

”urnCobj”urnC="25S"






”urnCobj”urnC="KDK"

”urnCobj”urnC="OD"

”urnCobj”urnC="SI"

”urnCobj”urnC="UN"

”urnCobj”urnC="VIB"




urnC=123456789

<Misc. Info>

Company site

Directory infrastructure for Directory infrastructure for specific applicationspecific application

Master directory

Data base

X.500/LDAP

Data base

Company

directoryX.500/LDAP

Data base

Company

directory

X.500/LDAP

Several independent infrastructuresSeveral independent infrastructures

Defence organisation

Aviationindustry

Autoindustry

Containershipping

ITU-T Y.2213 support requirementsITU-T Y.2213 support requirements

Not affected by a single of failure

Location-based service support

Forward identifier resolutionAs shown in examples above

Reverse identifier resolutionIdentification of tag/tag reader from associated information

One-to-many association between tag and usersDifferent information associated with tag for different users

We have all answer to all that

ENDEND

Date post:	27-Mar-2015
Category:	Documents
Upload:	kylie-curran
View:	216 times
Download:	1 times

X.500/LDAP as OID and URN resolver Erik Andersen Andersens L-Service [email protected].

Documents