28 May ~ 2 June, 2006 Hyoungjun KIM TTA/ETRI

GSC: GSC: Standardization Standardization Advancing Global Advancing Global CommunicationsCommunications

Standardization topics on network based RFID services and Cooperation for

harmonized standards development

28 May ~ 2 June, 2006

Hyoungjun KIM

TTA/ETRI

SOURCE: TTA

TITLE: Standardization topics on network based RFID services and Cooperation for harmonized standards development

AGENDA ITEM: Joint 4.7

CONTACT: Hyoungjun KIM, ETRI, [email protected]

GSC11_JOINT_26

GSC: GSC: Standardization Advancing Global Standardization Advancing Global CommunicationsCommunications

Proposal

• Some added and revised texts are proposed to be included in the RFID HIS resolution of the GSC-11 meeting.

– GSC-11 recognized:

• There are many new standardization topics on networked B2B, B2C and B2B2C RFID applications; and

• A focus group is taken into account at ITU-T to create a common work place for all RFID matters.

– GSC-11 considered:

• Close cooperation with SDOs is required due to different and limited work scopes.


Proposal

– GSC-11 resolved:

• To encourage harmonized standards development; and

• To make a formal procedure of ITU-T with PSOs and SDOs to set up close cooperation for and develop harmonized and globally compatible RFID-related standards.


RFID developed in B2B


RFID evolved in B2C


New challenges in B2C RFID

• Existing RFID-related standards cover only B2B RFID.

• Characteristics of B2B and B2C

B2C B2B

Goal • Content distribution • Work flow automation

Service user • Human • Business logic

Service terminal • Cell phones • PDA, PC, POS, etc.

Contents

• information, voice, music, game, video, etc.

• Contents for the five senses of human

• Business-related Information

Network• Expensive wireless

network based• Low cost wire network

based

User property • Dynamic • Static


Standardization topics (1/6)

• Rationale: new service requirements require more standards and some extensions.

• Service requirements analysis– Existing ARP (Application Requirements Profile) is for B2B

applications.

– B2C and B2B2C have different requirements.

• Reader, tag and smartcard integration– B2C terminal needs reader, tag and smartcard features all

together.

• Application data protocol extension– ISO/IEC 15961 might need some extensions to support tag-

based B2C RFID applications.



• ID code identification

– A variety of code schemes and even private codes exist.

– How to distinguish them and how to process a code need to be defined.

• ID code representation

– A processed ID code is just a bit string.

– How to denote ID needs to be defined.

• Ex.: 1.2.3, 1:2:3, 123, etc.

• Ex.: 0xCF.0x8E.0x83.0xEB, 0317.0216.0203.0353, 3482223595, etc.



• ID code naming– “1.2.3.4” is IPv4 address or ID?

– Name is much better than numeric code.

– A unique name is needed. (ex. urn:ip:v4:1.2.3.4)

• Application data encoding– ISO/IEC 15961 & 15962 provides a framework of tag data

encoding.

– EPCglobal provides its tag data format.

– But, application user data encoding is not specified yet.

• One-code, multi-uses requirement– A single code must be associated with a single physical object

and multiple logical objects.



• Code resolution protocol– A resolution infrastructure needs to be established.

– Candidate protocols: DNS, IRIS, X.500, LDAP, etc.

• ENUM extension, in case of using DNS, – “e.164.arpa” is a special domain for E.164 resolution into a URI.

– Another special domain will be helpful for a code resolution into a URI.

• Directory interoperability– There may be many different directory infra. (ex. EPC directory

via ONS, Japan’s UID directory, IRIS directory, Korea’s ODS directory, etc.)

– Directory interoperability needs to be considered.



• Reader management protocol

– JTC 1/SC 31 and EPCglobal are working on this, but focusing on B2B-purposes readers.

– B2C models have different requirements for B2C-purposes reader systems.

• Service gateway architecture

– Service broker may be exploited for B2C to give subscribers value-added services.

– Architecture and relevant protocols need to be considered.



• Password acquisition protocol– kill and lock features require a proper password.

• Privacy control architecture and protocols– Private information may be leaked easily.

– A privacy control architecture may be exploited to manage access privileges to private information.

– Relevant protocols may be followed.

• Adult verification– Even boys and girls below 10 are using cell phones. ID

applications can make they access to adult contents very easily.


Relevant SDOs (1/3)

• ITU-T

– Covers application and network aspects of identification including RFID.

• ISO/IEC JTC 1/SC 31/WG 4

– Covers the scope between tags and an RFID application system via multiple RFID readers except for application and network aspects.

– WG 4/SG 1 deals with application interface protocol and data encoding.

– WG 4/SG 3 deals with air interface protocols.


Relevant SDOs (2/3)

• EPCglobal

– Has more extended work scopes including application and network aspects than ISO/IEC JTC 1/SC 31/WG 4. But it focuses on B2B applications.

• ISO/IEC JTC 1/SC 17

– Deals with smartcard issues, for examples, air interface protocols, data encoding, etc.

• ISO/IEC JTC 1/SC 27

– Deals with security techniques.

• IETF

– Deals with directory-related issues such as LDAP, DNS, etc.


Relevant SDOs (3/3)

• OMA

– Deals with content negotiation for cell phone environment


Conclusion and Proposal (1/3)

• Relevant SDOs have different work scopes.

• There are many prospective additions and extensions to existing RFID-related standards. Due to limited work scopes,

– Some of them correspond to ITU-T’s prospective work items;

– Some of them correspond to cooperation work items with other SDOs; and

– Some of them are likely to be other SDOs’ work items.

• Therefore, close cooperation is required to develop harmonized and globally compatible RFID-related standards.



• A leading formal action of ITU-T is required to set up close cooperation with PSOs and SDOs and develop harmonized and globally compatible RFID-related standards.

• So this contribution proposes following added and revised texts:– GSC-11 recognized:

• There are many new standardization topics on networked B2B, B2C and B2B2C RFID applications; and

• A focus group is taken into account at ITU-T to create a common work place for all RFID matters.

– GSC-11 considered:

• Close cooperation with SDOs is required due to different and limited work scopes.



– GSC-11 resolved:

• To encourage harmonized standards development; and

• To make a leading formal procedure of ITU-T to set up close cooperation with PSOs and SDOs and develop harmonized and globally compatible RFID-related standards.

Documents

28 May ~ 2 June, 2006 Hyoungjun KIM TTA/ETRI