LS to SG2 on definitions of NID


Published on

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

LS to SG2 on definitions of NID

  1. 1. INTERNATIONAL TELECOMMUNICATION UNION JCA-NID TELECOMMUNICATION Document O-17 STANDARDIZATION SECTOR English only STUDY PERIOD 2005-2008 Joint Coordination Activity on Network Aspects Submitted, 26 October 2007 of Identification Systems (including RFID) Source: Convener of JCA-NID Title: LS to SG2 on definitions of networks aspects of Identification systems (including RFID) To: SG2 CC: - Purpose: Action Deadline December 2007 JCA-NID is at present working on a list of definitions relevant to networks aspects of ID systems (including RFID). A first draft has been submitted to the last JCA-NID meeting on 18 September 2007 (see Doc I-86 in the annex). This document is intended to harmonize the definitions in ITU-T and in ISO. It includes around 60 terms and definitions. During the discussion of the document, it has been found important to indicate the origin of the individual definition. In addition, now that the FG IdM has produced its deliverables and that the work on NID and USN has progressed in various SGs (SG13, 16, 17), the proposed definitions should be compared to those used in these entities. In particular, it is important for JCA-NID to identify possible contradictions and differences, bearing in mind that each entity will feel responsible for definition in its specific domain. This document will be further developed by correspondence until the next JCA-NID meeting in January 2008 (correspondence group under the leadership of Mr.Y.W.Kim/ETRI). The meeting also found important to involve SG2 in this activity and agreed to send the present LS. SG2 is kindly requested to look at the proposals and to forward any comments and suggestions to JCA-NID before next meeting, which will take place in Seoul, Korea, on the 23 January 2008. Attachment: 1 Doc I-86 Contact: Mr Pierre-André Probst Tel.: +41 22 950 0507 OFCOM Fax: +41 22 950 0506 Switzerland Email:
  2. 2. 1 Attachment 1 to JCANID LS Doc O-17 INTERNATIONAL TELECOMMUNICATION UNION JCA-NID TELECOMMUNICATION Document I-086 STANDARDIZATION SECTOR English only STUDY PERIOD 2005-2008 Joint Coordination Activity on Network Aspects Submitted: 14 September 2007 of Identification Systems (including RFID) Source: Convener of the correspondence group on definitions Title: Tentative list of terms and definitions relevant to the ITU-T JCA-NID scope Agenda item: 8 Purpose: Discussion This contribution is a seed material to make the correspondence group deliverable on terms and definitions relevant to the ITU-T JCA-NID scope. This document collects terms and definitions found in ITU-T documents (existing ITU-T Recommendations, working drafts of new Recommendations, JCA-NID documents, etc.) and relevant ISO/IEC documents. It is intended that relevant terms and definitions be harmonized within ITU-T. The references are given in square brackets. The deliverable could be used to give reference terms defined by existing ITU-T Recommendations and ISO/IEC International Standards and to give harmonized definitions on new terms being defined. 1. NID [JCA-NID I-078 Rev 1] NID (Network aspects of Identification system (including RFID)) is used to designate network aspects of applications or services which involves at least the elements: identifier, reader/writer (interrogator), tag (transponder) and network(s). An Identifier is stored on a tag and a reader/writer reads the identifier from the tag via optical scanner, camera, IrDA, RF technique or other methods. So NID application or service provides identifier-based communication with information systems distributed over global open networks. Note: This definition will be reviewed in order to ensure that USN be covered. 2. Identifier [Y.2091] An identifier is a series of digits, characters and symbols or any other form of data used to identify subscriber(s), user(s), network element(s), function(s), network entity(ies) providing services/applications, or other entities (e.g., physical or logical objects). Identifiers can be used for registration or authorization. They can be either public to all networks, shared between a limited number of networks or private to a specific network (private IDs are normally not disclosed to third parties.)
  3. 3. [Y.idMsec] Anything that embodies the information required to distinguish what is being identified from all other things within its scope of identification. In the context of NGN, an identifier can be any form of data used to distinguish entities. Multiple identifiers can be associated with an entity. 3. Identification (ID) [JCA-NID I-006] Identification is the process of specifically identifying an object from a large class of objects through reading identifiers. ID is the abbreviation of identification. [F.851] A process to identify the UPT user or the UPT service provider 4. Code [JCA-NID I-006] Code is the same term to “identifier.” 5. ID code [JCA-NID I-006] An ID code is an identification code and the same to “identifier.” 6. Code resolution [JCA-NID I-006] A code resolution is a process of translating or resolving an identifier into an address. [Y.idserv-reqts] It is the process of translating or resolving an identifier into an address. It is provided via directory service operations based on X.500, LDAP, DNS, etc. 7. Code resolver [JCA-NID I-006] A code resolver is a code resolving agent to perform iterative code resolution procedures starting from the root of a code delegation hierarchy. 8. Stub code resolver [JCA-NID I-006] A stub code resolver is a local code resolver to ask the code resolver to look up an address from a code reversely. 9. Address [JCA-NID I-006] An address is the identifier for, in addition to identifying a resource, providing a means of acting upon or obtaining a representation of the resource by describing its primary access mechanism or network “location.” That is, the address may be given in a URL form. 10. Directory [JCA-NID I-006] A directory is a repository or database of information to provide the code resolution. 11. Directory service [JCA-NID I-006]
  4. 4. A directory service is highly optimized for reads and provides advanced search on the many different attributes that can be associated with objects in a directory. The data that is stored in the directory is defined by an extendable and modifiable schema. Directory services use a distributed model for storing their information and that information is usually replicated between directory servers. X.500, IRIS and DNS are typical examples. 12. RFID [JCA-NID I-006] RFID is a generic term for technologies that use radio waves to remotely store and retrieve data. In other words, it is a combined term with RF and ID where RF means a wireless communication technology and ID means identification information of a tag. So it is said that RFID is theoretically a wireless networking technology to transmit identification information stored at an electronic memory space. 13. Radio frequency identification system [ISO/IEC FDIS 19762] Automatic identification system and data capture system comprising one or more reader/interrogators and one or more transponders in which data transfer is achieved by means of suitably modulated inductive or radiating electromagnetic carriers 14. RFID system [JCA-NID I-060] [Note] this term is defined in [X.rfpg]. RFID system is any system which attaches an RFID tag to an article, etc. and, by using radio frequencies, perceives its identification information and the information about the surrounding environment so as to collect, store, process and utilize the said information. 15. RFID tag [JCA-NID I-060] [Note] this term is defined in [X.rfpg]. RFID tag is any tag, built in or attached to an article, etc., which can record its information or other information, and use radio frequencies to read or store this information. 16. Networked RFID [JCA-NID I-006] It means an expanded RFID network and communication scope to communicate with a series of networks, inter-networks and globally distributed application systems. So it makes global communication relationships triggered by RFID, for such applications as B2B, B2C, B2B2C, G2C, etc. where the term has to deal with all layer issues of L1 to L7. 17. Networked ID [JCA-NID I-006] It is the same to the networked RFID except for identifier transmission from tag to reader. The connectivity for transmission of identifiers is out of scope and an implementation issue at terminals. Identifiers can be transmitted via RF, camera, IrDA, scanner, manual key-in, etc. [JCA-NID I-015] Networked ID (N-ID) can be defined as an ID, which is stored in a system that is accessible via network by users who have the access permission in advance, and by
  5. 5. accessing the networked ID, users become aware of its associated data/information within the limits of their permissions. 18. Mobile terminal [X.1121] [Note] this term is referred to in [X.rfidsec-1]. An entity that has wireless network access function and connects a mobile network for data communication with application servers or other mobile terminals. 19. Mobile network [X.1121] [Note] this term is referred to in [X.rfidsec-1]. A network that provides wireless network access points to mobile terminals. 20. Mobile user [X.1121] [Note] this term is referred to in [X.rfidsec-1]. An entity (person) that uses and operates the mobile terminal for receiving various services from application service providers. 21. Application server [X.1121] [Note] this term is referred to in [X.rfidsec-1]. An entity that connects to an open network for data communication with mobile terminals. 22. Mobile security gateway [X.1121] [Note] this term is referred to in [X.rfidsec-1]. An entity which relays data communication between a mobile terminal and an application server, changes security parameters or communication protocol from a mobile network to an open network, or vice versa, and can perform security policy management functions for mobile end-to-end data communication. 23. Tag owner (or Owner) [JCA-NID I-027] [Note] this term is defined in [X.rfidsec-1]. A person who has the ownership for RFID tag. 24. The owner-defined privacy profile [JCA-NID I-027] [Note] this term is defined in [X.rfidsec-1]. A formatted set of the privacy protection rules and policies that are defined by the owner. 25. Personally Identifiable Information (PII) [JCA-NID I-060] [Note] this term is defined in [X.rfpg].
  6. 6. Personal Identifiable Information is the information pertaining to any living person, which makes it possible to identify such individual (including the information capable of identifying a person when combined with other information even if the information does not clearly identify the person). For example, some information contains a unique personal identity, including a name, fingerprints, a picture, and an ID number provided by a government organization (ex, social security number). PII also includes any data that can be used to identify someone, by referring to elements that uniquely show the person’s physical, spiritual, cultural, and social identity. Accordingly, personal information, which is collected and processed in a form that cannot identify the person, is not protected. For example, statistical data that cannot disclose a person’s identity do not belong to PII. However, if the information, which cannot identify a person by itself, can be easily contrasted, connected, or combined with other information to identify the person, it is classified into PII for protection. Therefore, if you can get information related to a person, form a unique ID number assigned to the RFID tag, it is PII although it does not provide personal information directly. 26. RFID service provider [JCA-NID I-060] [Note] this term is defined in [X.rfpg]. RFID service provider is any person who manufactures and sells RFID chips or tags, who manufactures (including processing or packaging) or sells article with RFID tags attached or built in, who links article information recorded in the RFID tag to PII, or who records PII in the RFID tag or collects PII recorded in the RFID tag. 27. User [JCA-NID I-060] [Note] this term is defined in [X.rfpg]. Any person who purchases an article with RFID tags built in or attached, or makes use of the services based on the article with RFID tags built in or attached. 28. Multimedia information [JCA-NID I-081] [Note] this term is defined in [F.mid]. Usually, multimedia information may include pictures, audio and video in a narrow sense. This Recommendation adopts much broader definition of “multimedia”. Multimedia information involves not only the audio-visual information, but also various digital information such as text, interactive 3D panorama pictures, digital maps, and so on. 29. Identity [Y.2091] The attributes by which an entity or person is described, recognized or known. [Y.idMsec] The attributes by which an entity is described, recognized or known. 30. Authenticated identity [X.811] [Note] this term is referred to in [Y.idMsec]. A distinguishing identifier of a principal that has been assured through authentication.
  7. 7. 31. Federated identity [Y.idMsec] A single user identity that can be used to access a group of services or applications that are bounded by the ties and conditions of a federation. 32. Federation [Y.idMsec] An established relationship among a domain of a single service provider or among NGN providers. 33. Identity pattern [Y.idMsec] A structured expression derived from behavior that is associated with and describes an entity allowing it to be recognized or known. Identity patterns may be uniquely associated with an entity, or a class with which the entity is associated. 34. Name [Y.2091] A name is the identifier of an entity (e.g. subscriber, network element) that may be resolved/translated into an address. 35. Identification [TD421 (WP3/13)] It is the process of specifically identifying an object from a large class of objects through reading identifiers. 36. Entity [Y.idMsec] Anything that has separate and distinct existence that can be uniquely identified. In the context of IdM, examples of entities include subscribers, users, network elements, networks, software applications, services and devices. An entity may have multiple identifiers. 37. Identity provider [Y.idMsec] IDP [Source: DOD] A type of service provider that creates, maintains, and manages identity information for users/devices and provides user/device authentication. Identity Provider [Source: VeriSign] An entity that creates, maintains, and manages trusted identity information for entities. An Identity Provider may include a Trusted Third Party. In the context of this NGN IdM, an Identity Provider makes available Identity Management capabilities pursuant to this recommendation to Relying Parties. Identity Provider (IdP) [Source: NTT] A service provider that authenticates a user and that creates, maintains, and manages identity information for users and asserts user authentication and other identity related information to other trusted service providers.
  8. 8. 38. Identity management [Y.idMsec] Management by NGN providers of trusted attributes of an entity such as: a subscriber, a device or a provider. This is not intended to indicate positive validation of a person. 39. Private (subscriber) identity [Y.idMsec] An identity derived from the IMSI (3GPP definition. see TS 123 003 clause 13.3). [EdNote: 3GPP has different definitions on Identity and Identifiers. This definition is for an identifier in our contest.] 40. Public (subscriber) identity [Y.idMsec] Either a SIP URI or a tel URI (3GPP definition. see TS 123 003 clause 13.4). [EdNote: 3GPP has different definitions on Identity and Identifiers. This definition is for an identifier in our contest.] 41. Public service identifier [Y.idMsec] Either a SIP URI or a tel URI (3GPP definition. see TS 123 003 clause 13.5). 42. Business-to-Business (B2B) [TD421 (WP3/13)] It is a business relationship which involves exchanges of identification information between business partners. 43. Business-to-Consumer (B2C) [TD421 (WP3/13)] It is a business relationship which involves exchanges of identification information between businesses and consumers where the service providers provide valuable and useful services to the consumers and the consumers use them. 44. Business-to-Business-to-Consumer (B2B2C) [TD421 (WP3/13)] It is an integrated business relationship between B2B and B2C where identification information is traversed across business partners and consumers. 45. Consumer-to-Consumer (C2C) [TD421 (WP3/13)] It is a business relationship which involves exchanges of identification information between consumers. The information exchanges may be enabled through a third party or a direct peer- to-peer communication. The online auction business model is the former case. 46. Object identifier [X.680] [Note] this term is referred to in [X.RA-nid]. A globally unique value associated with an object to unambiguously identify it. 47. Object [X.680]
  9. 9. It is a well-defined piece of information, definition, or specification which requires a name in order to identify its use in an instance of communication. NOTE – Such an object may be an information object as defined in ITU-T Rec. X.681 | ISO/IEC 8824-2. 48. Object identifier tree [X.660] [Note] this term is referred to in [X.RA-nid]. A specific form of an RH-name-tree whose root corresponds to this Recommendation | International Standard and whose nodes correspond to registration authorities responsible for allocating arcs from a parent node. 49. Registration [X.660] [Note] this term is referred to in [X.RA-nid]. The assignment of an unambiguous name to an object in a way which makes the assignment available to interested parties. 50. Registration authority [X.660] [Note] this term is referred to in [X.RA-nid]. An entity such as an organization, a standard or an automated facility that performs registration of one or more types of objects (see also International Registration Authority). NOTE – For this Recommendation | International Standard, the above definition of registration authority extends the term to cover registration by organizations acting at international, regional and national levels and by other means. For clarity, the term International Registration Authority is used in this Recommendation | International Standard to refer to an organization performing registration at the international level. 51. Registration-hierarchical-name [X.660] A name which is unambiguous within the registration-hierarchical-name-tree and which is assigned by registration. The semantic form of this name is structured according to the rules in clause 6. 52. Registration-hierarchical-name-tree [X.660] [Note] this term is referred to in [X.RA-nid]. A tree whose nodes correspond to objects that are registered and whose non-leaf nodes may be registration authorities. 53. Registration procedures [X.660] [Note] this term is referred to in [X.RA-nid]. The specified procedures for performing registration and amending (or deleting) existing registrations. 54. Air interface [ISO/IEC FDIS 19762]
  10. 10. Conductor-free medium, usually air, between a transmitter and the receiver through which data communication is achieved by means of a modulated inductive or propagated electromagnetic field 55. AFI [ISO/IEC FDIS 19762] Mechanism used in the data protocol and the air interface protocol to select a class of RFID tags relevant to an application, or aspect of an application, and to ignore further communications with other classes of RFID tags with different identifiers 56. AFI tag [ISO/IEC FDIS 19762] ISO/IEC 18000-6 Type C tag with Protocol Control bit 17 set at “1’ indicating that what follows is an Application Family Identifier (AFI) 57. EPC tag [ISO/IEC FDIS 19762] ISO/IEC 18000-6 Type C tag with Protocol Control bit 17 set at “0’ indicating that what follows is an EPC header 58. Arc [ISO/IEC FDIS 19762] Specific branch of an object identifier tree, with new arcs added as required to define a particular object 59. Bar [ISO/IEC FDIS 19762] Dark element corresponding to a region of a scan reflectance profile below the global threshold 60. Bar code [ISO/IEC FDIS 19762] Code representing data in machine-readable form by sets of parallel rectangular bars and spaces of varying thickness and separation which are read optically by scanning 61. Bar code reader [ISO/IEC FDIS 19762] Device used to capture the data encoded in a bar code symbol, consisting of two parts: 1) the scanner an input device which sends signals proportional to the reflectivity of each successive element of the symbol to the decoder, and 2) the decoder, which examines the signals from the scanner and translates them into recognizable or computer-compatible data. The decoder itself is sometimes erroneously called a reader 62. Bar code symbol [ISO/IEC FDIS 19762] Combination of symbol characters and features required by a particular symbology, including quiet zones, start and stop characters, data characters, check characters and other auxiliary patterns, which together form a complete scannable entity
  11. 11. 63. Interrogation [ISO/IEC FDIS 19762] Process of communicating with, and reading a transponder 64. Interrogation zone [ISO/IEC FDIS 19762] Region directivity is independent of antenna losses and equal to the absolute gain in which a transponder or group of transponders can be effectively read by an associated radio frequency identification reader/interrogator the same direction if the antenna is lossless. 65. Interrogator [ISO/IEC FDIS 19762] Fixed or mobile data capture and identification device using a radio frequency electromagnetic field to stimulate and effect a modulated data response from a transponder or group of transponders present in the interrogation zone 66. ORM (optically readable medium) [ISO/IEC FDIS 19762] Member of the set of automatic identification techniques such as a linear bar code, two- dimensional, mark sense, or optical character recognition (OCR) symbols, that are illuminated by a light source and examined by an optical detector that converts the received reflectance into an electrical signal that are grouped in a predetermined method, recognized by the reader and converted into the corresponding computer code 67. Reader, Interrogator, or Reader/Writer [ISO/IEC FDIS 19762] Electronic device for performing the process of retrieving data from and potentially transmitting data to a transponder and, as appropriate, the contention and error control management, and channel and source decoding required to recover and communicate the data entered at source 68. Transponder [ISO/IEC FDIS 19762] Combination of radio transmitter and radio receiver, which transmits a signal automatically in response to an appropriate triggering signal 69. Roaming [ISO/IEC FDIS 19762] Ability of a tag to move from one interrogator’s cell to another 70. Scanner [ISO/IEC FDIS 19762] Optical scanner that converts optical information (e.g., a printed bar code or two dimensional symbols) into electrical signals for subsequent decoding and transmission to a computer 71. Sensor [ISO/IEC FDIS 19762] Electronic device that senses a physical condition or chemical compound and delivers an electronic signal proportional to the observed characteristic
  12. 12. 72. Tag ID [ISO/IEC FDIS 19762] Generic reference to either a manufacturer tag ID or user tag ID 73. Manufacturer tag ID [ISO/IEC FDIS 19762] Reference number, which uniquely identifies the tag 74. User tag ID [ISO/IEC FDIS 19762] User-defined tag identifier. NOTE – The User Tag ID may not be a unique identifier. 75. Two-dimensional symbol [ISO/IEC FDIS 19762] Code representing data in machine-readable form by a collection of polygonal or circular cells in a regular pattern which are read optically by scanning 76. WORM (Write Once/Read Many) [ISO/IEC FDIS 19762] Distinguishing a transponder that can be part or totally programmed once by the user, and thereafter only read
  13. 13. References: [JCA-NID I-078 Rev 1] Draft NID High Level Requirements (HLR) Deliverable [X.rfidsec-1] Privacy Protection Framework for Networked RFID Services [JCA-NID I-027] LS on Privacy Protection framework for Networked RFID Services [JCA-NID I-006] TSAG-TD-GEN-0315: Final draft for "Review report of standardization issues on network aspects of identification including RFID" [JCA-NID I-015] A Proposed NID Service Reference Architecture and Some Terminologies [JCA-NID I-060] Liaison statement on draft Recommendation X.rfpg [JCA-NID I-081] LS on NID related services [X.1121] Framework of security technologies for mobile en-to-end data communications [Y.2091] Terms and Definitions for NGN [X.rfpg] Privacy guideline for RFID [F.mid] Service description and requirements for networked ID triggered multimedia information delivery services triggered by tag-based identification [TD421 (WP3/13)] Living list for Y.idserv-reqts (Geneva, 16-27 April 2007) [Y.idserv-reqts] NGN service requirements and capabilities for network aspects of identification-based applications and services [X.811] Security Frameworks for Open Systems: Authentication Framework - Data Networks and Open System Communications [Y.idMsec] NGN IDENTITY MANAGEMENT SECURITY [X.680] Abstract Syntax Notation One (ASN.1): Specification of basic notation [X.660] Procedures for the operation of OSI Registration Authorities: General procedures and top arcs of the ASN.1 Object Identifier tree [X.RA-nid] Procedures for the operation of OSI registration authorities: registration of object identifier arcs for ID-based applications [ISO/IEC FDIS19762] Information Technology AIDC Techniques - Harmonized Vocabulary __________