Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations


Presentation on theme: "X.500/LDAP as OID and URN resolver Erik Andersen Andersens L-Service"— Presentation transcript:

1 X.500/LDAP as OID and URN resolver Erik Andersen Andersens L-Service era@x500.eu

2 Hierarchical 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 - - -

3 Mapping 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

4 Information types Q: What kind information can you store? A: Any type! Text; photos; speech; certificates; and what ever may be represented in a digital form

5 Possible DIT subtree representing object identifier components oidC2obj oidC2-attr=27 oidCobj oidC-attr= 10891 oidCobj oidC-attr= 15459 oidCobj oidC-attr= 15961 Object class (type of entry) Attribute with value (entry content) Root of Directory Information Tree (DIT) oidC1obj oidC1-attr=2 oidC1obj oidC1-attr=1 oidC2obj oidC2-attr=0 oidCobj oidC-attr=8 oidCobj oidC-attr=9 oidCobj oidC-attr=12 oidCobj oidC-attr=5 oidCobj oidC-attr=4 oidCobj oidC-attr=1 oidCobj oidC-attr=n1 oidCobj oidC-attr=n2 oidCobj oidC-attr=n3 oidC1obj oidC1-attr=0 (iso)(itu-t) (joint-iso-itu-t)

6 DIT subtree of OIDs defined as URNs Root of Directory Information Tree (DIT) urnC1obj urnC1="oid" urnC2obj urnC2="1" urnC2obj urnC2="2" urnC2obj urnC2="0" urnCobj urnC="0" urnCobj urnC="15459" urnCobj urnC="4" urnCobj urnC="5" urnCobj urnC="4" urnCobj urnC="5" urnCobj urnC="6" urnCobj urnC="7" urnCobj urnC="3" urnCobj urnC="2" urnCobj urnC="1" Object class (type of entry) Attribute with value (entry content)

7 Representing URNs in LDAP/X.500 Root of Directory Information Tree (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" urnCobj urnC="-2" urnCobj urnC="-3" urnCobj urnC="-4" urnCobj urnC="-5" urnCobj urnC="-6"

8 X.500/LDAP directory support for Tag-based applications Erik Andersen Andersens L-Service era@x500.eu

9 RFID 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

10 Use of Directory technology AIDC media ID terminal Directory infrastructure DUA or LDAP client AIDC client system

11 LDAP/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).

12 Players 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

13 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

14 18000-6C & 3m3, Memory structure ¥ Data Objects formatted: Precursor, [OID], length, Object Sensors/Battery-assist See ISO/IEC 15961 and ISO/IEC 15962 MDID Part number Serial number Burned in or written and permalocked by IC manufacturer ¥ ¥ ¥ ¥ ¥ ¥ Reserved UII TID [User] Memory Banks DSFID RFU TID CRC-16 UII (may be EPC) Protocol Control Access Password Kill Password [Extended Protocol Control] 00 01 10 11 [ ] = Optional UII = Unique Item Identifier

15 Memory Bank 01B Cyclic Redundancy Check (16 bits) Length (5 bits) UII AFI (ISO) Toggle bit: 0=EPC/1=ISO Zero fill to Word boundary Protocol Control Length in words (of 16 bits) AFI= Application Family Identifier EPC= Electronic Product Code UII= Unique Item Identifier (8 bits) Reserved (EPC )$ (Confirms UII memory content)

16 Relevant tag information for directory 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

17 Uniqueness 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 format A numeric character or alpha numeric format

18 GS1 EPCglobal

19 EPC UII types Serialized Global Trade Item Number (SGTIN) SGTIN-96 and SGTIN-198 Serial Shipping Container Code (SSCC) SSCC-96 Serialized Global Location Number (SGLN) SGLN-96 and SGLN-195 Global Returnable Asset Identifier (GRAI) GRAI-96 and GRAI-170 Global Individual Asset Identifier (GIAI) GIAI-96 and GIAI-202 Global Service Relation Number (GSRN) GSRN-96 Global Document Type Identifier (GDTI) GDTI-96 and GDTI-113 DoD Tag Data Constructs DoD-96

20 EPC Search using the EPC UII in a limited environment epcUii uiiInUrn contentUrl or X.500/LDAP EPC UII Filter:epcUii | contentUrl (uiiInUrn, tagLocation) Data base ID terminal Attribute Value Assertions Entry tagLocation AIDC media

21 Search using the (AFI, UII) tuple tagOid isoUii uiiInUrn contentUrl or X.500/LDAP AFI + UII Filter: tagAfi & isoUii | contentUrl [uiiInUrn, tagOid, tagLocation] Data base ID terminal Attribute Value Assertions Entry tagAfi tagLocation AIDC media

22 SGTIN-96 Partitions ( Serialized Global Trade Item Number – 96 bits) 0 Company PrefixSerial Number Header x30 F 1 Company PrefixSerial Number Header x30 Item Ref. F 2 Company PrefixSerial Number Header x30 Item Ref. F 3 Company PrefixSerial Number Header x30 Item Reference F 4 Company PrefixSerial Number Header x30 Item Reference F 5 Company PrefixSerial Number Header x30 Item Reference F 6 Company PrefixSerial Number Header x30 Item Reference F Filter Partition 44 bits 38 bits

23 Retrieving EPC UII format information X.500/LDAP uiiFormat Data base ID terminal Attribute Value Assertions EPC UII Filter: (epcHeader & epcPartition) UII type entry epcHeader epcPartition uiiFormat AIDC media

24 Formatting 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

25 The 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" urnCobj urnC="9180" urnCobj urnC="9181" urnCobj urnC="9179" urnCobj urnC="793591651" urnCobj urnC="793591652" urnCobj urnC="793591653" Company Prefix level Item Reference level Serial number level urnCobj urnC="igln"

26 ISO/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

27 General ISO/IEC 15459 Data Identifier format General ISO/IEC 15459 Data Identifier format Company Identification Number (CIN) Serial Number/ Part Number Data Identifier Issuing Agency Code IAC DI 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.2 Examples: 25SId of a party identified by IAC and CIN followed by a Serial Number JUnique license plate number – unspecified – max 35 characters 1 J to 6JUnique 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 Number 25BAs for 25S for a returnable transport item 6 bits character encoding

28 Issuing 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 Nederlands Normalisatie-instituut List of assigned IACs may be found here: http://iso15459.nen.nlhttp://iso15459.nen.nl

29 Retrieving ISO UII format information X.500/LDAP AFI and ISO UII Filter: (tagAfi & isoTagDi & isoTagIac) uiiFormat Data base AIDC media ID terminal Attribute Value Assertions tagOid isoTagDi uiiFormat tagAfi UII type entry isoTagIac

30 URN 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 UII Example: 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.... Example: urn:iso:std:iso-iec:15459:25S.UN.043325711.MH803120000001 Company Identification Number (CIN) Issuing Agency Code (IAC) Serial/part number Data Identifier (DI)

31 Representing URNs in LDAP/X.500 urnC1obj urnC1="iso" urnC2obj urnC2="std" urnCobj urnC="iso-ieee" urnCobj urnC="iso-iec" urnCobj urnC="iso" urnCobj urnC="15459" urnCobj urnC="25B" urnCobj urnC="25P" urnCobj urnC="25S" urnCobj urnC="J" urnCobj urnC="1J" urnCobj urnC="2J" urnCobj urnC="3J" urnCobj urnC="J" urnCobj urnC="KDK" urnCobj urnC="OD" urnCobj urnC="SI" urnCobj urnC="UN" urnCobj urnC="VIB" urnCobj urnC="123456789" urnCobj urnC="234567890" urnCobj urnC="345678901" urnCobj urnC="MH803120000001" urnCobj urnC="MH803120000002" urnCobj urnC="MH803120000003" Data Identity level Issuing Agency Code level Company Identifi- cation Number level Serial/Part Number level

32 Use of digital signature tagOid isoUii uiiInUrn contentUrl or X.500/LDAP AFI + UII Signed Info Filter: tagAfi & isoUii | contentUrl pkiPath [uiiInUrn, tagOid, tagLocation] Data base ID terminal Attribute Value Assertions Entry tagAfi tagLocation AIDC media pkiPath

33 Distribution of URN subtree urnC1obj urnC1="iso" urnC2obj urnC2="std" urnCobj urnC="iso-ieee" urnCobj urnC="iso-iec" urnCobj urnC="iso" urnCobj urnC="15459" urnCobj urnC="25B" urnCobj urnC="25P" urnCobj urnC="25S" urnCobj urnC="J" urnCobj urnC="1J" urnCobj urnC="2J" urnCobj urnC="3J" urnCobj urnC="J" urnCobj urnC="KDK" urnCobj urnC="OD" urnCobj urnC="SI" urnCobj urnC="UN" urnCobj urnC="VIB" urnCobj urnC="123456789" urnCobj urnC="234567890" urnCobj urnC="345678901" urnC=123456789 Company site

34 Directory infrastructure for specific application Master directory Data base X.500/ LDAP Data base Company directory X.500/ LDAP Data base Company directory X.500/ LDAP

35 Several independent infrastructures Defence organisation Aviation industry Auto industry Container shipping

36 ITU-T Y.2213 support requirements Not affected by a single of failure Location-based service support Forward identifier resolution As shown in examples above Reverse identifier resolution Identification of tag/tag reader from associated information One-to-many association between tag and users Different information associated with tag for different users We have all answer to all that

37 END


Download ppt "X.500/LDAP as OID and URN resolver Erik Andersen Andersens L-Service"

Similar presentations


Ads by Google