1、 International Telecommunication Union ITU-T H.642.2TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (06/2012) SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMSBroadband, triple-play and advanced multimedia services Ubiquitous sensor network applications and Internet of Things Multimedia information acces
2、s triggered by tag-based identification Registration procedures for identifiers Recommendation ITU-T H.642.2 ITU-T H-SERIES RECOMMENDATIONS AUDIOVISUAL AND MULTIMEDIA SYSTEMS CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS H.100H.199 INFRASTRUCTURE OF AUDIOVISUAL SERVICES General H.200H.219 Transmission
3、 multiplexing and synchronization H.220H.229 Systems aspects H.230H.239 Communication procedures H.240H.259 Coding of moving video H.260H.279 Related systems aspects H.280H.299 Systems and terminal equipment for audiovisual services H.300H.349 Directory services architecture for audiovisual and mult
4、imedia services H.350H.359 Quality of service architecture for audiovisual and multimedia services H.360H.369 Supplementary services for multimedia H.450H.499 MOBILITY AND COLLABORATION PROCEDURES Overview of Mobility and Collaboration, definitions, protocols and procedures H.500H.509 Mobility for H
5、-Series multimedia systems and services H.510H.519 Mobile multimedia collaboration applications and services H.520H.529 Security for mobile multimedia systems and services H.530H.539 Security for mobile multimedia collaboration applications and services H.540H.549 Mobility interworking procedures H.
6、550H.559 Mobile multimedia collaboration inter-working procedures H.560H.569 BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES Broadband multimedia services over VDSL H.610H.619 Advanced multimedia services and applications H.620H.629 Ubiquitous sensor network applications and Internet of Thin
7、gs H.640H.649IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV General aspects H.700H.719 IPTV terminal devices H.720H.729 IPTV middleware H.730H.739 IPTV application event handling H.740H.749 IPTV metadata H.750H.759 IPTV multimedia application frameworks H.760H.769 IPTV service discovery up to co
8、nsumption H.770H.779 Digital Signage H.780H.789 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T H.642.2 (06/2012) i Recommendation ITU-T H.642.2 Multimedia information access triggered by tag-based identification Registration procedures for identifiers Summary Reco
9、mmendation ITU-T H.642.2 describes registration procedures for the identifier scheme defined in Recommendation ITU-T H.642.1. It also designates the Registration Authority (RA) in charge of implementing these procedures. History Edition Recommendation Approval Study Group 1.0 ITU-T H.642.2 2012-06-2
10、9 16 Keywords Identification scheme, identifier, registration authority. ii Rec. ITU-T H.642.2 (06/2012) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Te
11、lecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardizatio
12、n Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technolo
13、gy which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance
14、with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligato
15、ry language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation o
16、f this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the
17、 date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to con
18、sult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2013 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T H.642.2 (06/2012) iii Table of Contents Page 1 Scope 1 2 References. 1 3 Definit
19、ions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 2 5 Conventions 2 6 Registration authority for a second level code . 2 6.1 Selection . 2 6.2 Announcement 3 6.3 Change of information 3 6.4 Publication 3 7 Second level RA . 3 7.1 Responsib
20、ilities . 3 7.2 Criteria for acceptance 4 7.3 Detailed procedures for the operation of the second level RA . 4 7.4 Transfer of register entries held by the second level RA . 5 Rec. ITU-T H.642.2 (06/2012) 1 Recommendation ITU-T H.642.2 Multimedia information access triggered by tag-based identificat
21、ion Registration procedures for identifiers 1 Scope This Recommendation defines registration procedures of the identification scheme defined by ITU-T H.642.1 for the first level code (1LC) value of 00012. The identification scheme consists of a first level code (1LC), a second level code (2LC), clas
22、s and elements such as a third level code (3LC), and a fourth level code (4LC). A 2LC is pre-assigned to ITU Member States, and then a 3LC is allocated by the registrant of the 2LC, which is called the second level registration authority (RA). The mechanism is meant for the distributed RA hierarchy.
23、 Therefore, this Recommendation specifies as follows: registration procedures for the 2LC and 3LC; responsibilities of the second level RA; and procedures for the operation of the second level RA. 2 References The following ITU-T Recommendations and other references contain provisions which, through
24、 reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the
25、 most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T F.771 R
26、ecommendation ITU-T F.771 (2008), Service description and requirements for multimedia information access triggered by tag-based identification. ITU-T H.621 Recommendation ITU-T H.621 (2008), Architecture of a system for multimedia information access triggered by tag-based identification. ITU-T H.642
27、.1 Recommendation ITU-T H.642.1 (2012), Multimedia information access triggered by tag-based identification Identification scheme. ITU-T H.642.3 Recommendation ITU-T H.642.3 | ISO/IEC 29177 (2012), Information technology Automatic identification and data capture technique Identifier resolution proto
28、col for multimedia information access triggered by tag-based identification. ISO 3166-1 ISO 3166-1:2006 Codes for the representation of names of countries and their subdivisions Part 1: Country codes, plus its Cor.1 (2007). 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the follo
29、wing terms defined elsewhere: 3.1.1 class ITU-T H.642.1: Part of an identifier that defines the layout and interpretation of the following bit string inside the identifier, especially the length of the third level code (3LC) and fourth level code (4LC). 2 Rec. ITU-T H.642.2 (06/2012) 3.1.2 country n
30、ame ISO 3166-1: Name of a country, dependency, or other area of particular geopolitical interest. 3.1.3 first level code (1LC) ITU-T H.642.1: Part of the identifier that represents the identifier sub-blocks. 3.1.4 fourth level code (4LC) ITU-T H.642.1: Part of the identifier that serializes individu
31、al multimedia information and services. 3.1.5 ITU-T H.642 identification scheme ITU-T H.642.1: Name given to the identification scheme defined in ITU-T H.642.1. 3.1.6 second level code (2LC) ITU-T H.642.1: Part of the identifier assigned to ITU Member States. 3.1.7 third level code (3LC) ITU-T H.642
32、.1: Part of the identifier assigned to a registration authority (RA) that handles the allocation of the subspace to other organizations. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 numeric-3 code element: The numeric code found in column 6 of the t
33、able in clause 9 of ISO 3166-1. 3.2.2 second level RA: The organization to which a second level code (2LC) is assigned and that manages the allocation of third level codes (3LCs) under class from 1 to 14. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms:
34、 1LC First Level Code 2LC Second Level Code 3LC Third Level Code 4LC Fourth Level Code RA Registration Authority 5 Conventions None. 6 Registration authority for a second level code The second level code (2LC) is assigned to ITU Member States and its value is taken from the values assigned to countr
35、ies in ISO 3166-1. Each ITU Member State receives four 2LCs using the formula: C*4, C*4+1, C*4+2, C*4+3, where C is the numeric-3 code (without leading zeroes) element defined in ISO 3166-1 for the specific country name. Therefore, a registration authority (RA) is not needed for a 2LC. 6.1 Selection
36、 The selection of the party to run the second level RA at a given 2LC shall be managed by the administration of each Member State, or a delegated organization from the administration. Rec. ITU-T H.642.2 (06/2012) 3 6.2 Announcement When an organization is selected to run a second level RA at a pre-a
37、ssigned 2LC (see clause 6.1), the following information shall be sent to the Director of TSB (Telecommunication Standardization Bureau), so that interoperability between different second level RAs can be maintained: a) the assigned 2LC value from the pre-assigned 2LCs; b) name of the initial organiz
38、ation to operate the second level RA; c) address of the initial organization; d) date of the initial assignment; e) date of the last transfer of assignment, if allowed (updatable); f) name of the current organization (updatable); g) address of the current organization (updatable); h) the name, title
39、, postal/e-mail address, telephone/facsimile number of a contact person within the organization (updatable); i) date of the last update (updatable). 6.3 Change of information The information provided in clause 6.2 for organization identified by a 2LC may change from time to time. The Director of TSB
40、 shall be notified of all such changes in a timely manner (within 30 days of such change). 6.4 Publication The Director of TSB shall post the information concerning the selection of second level RAs at a pre-assigned 2LC (clause 6.2) on the ITU website and publish regular updates in the Operational
41、Bulletin of the International Telecommunication Union. 7 Second level RA 7.1 Responsibilities The responsibilities of the second level RA are as follows: a) to receive applications for third level code (3LC) (the required content of the application is specified in clause 7.3.1); b) to process applic
42、ations within 30 days of receipt of the application form; c) if the application is accepted according to the criteria of clause 7.2, to allocate the 3LC and to send a registration announcement to the applicant; d) if the application is not accepted, to send a notice of rejection; e) to maintain a pu
43、blicly available register of allocated 3LCs (see clause 7.3.4); f) to provide the necessary resources to operate a resolution server, based on Recommendation ITU-T H.642.3 and future protocols that are derived from it, and new protocols that may emerge. The permitted fee structure shall be on a cost
44、-recovery basis. 4 Rec. ITU-T H.642.2 (06/2012) 7.2 Criteria for acceptance 7.2.1 Time-scale The application for 3LC shall identify the time-scale within which the 3LC is to be used for multimedia information access, triggered by tag-based identification. The application shall be rejected if the tim
45、e-scale exceeds 12 months, and can be voided if it is not in use within that time-scale. 7.2.2 Size Based on the request and estimated usage of codes, the second level RA can suggest that the applicant apply for a subspace under a particular class. 7.2.3 Nature of service The service for which the a
46、llocation of a 3LC is requested shall be services which require interchange between multiple applications in an open environment in the long run. 7.3 Detailed procedures for the operation of the second level RA 7.3.1 Registration application for a 3LC The application shall include at least the follo
47、wing information: a) name of the organization submitting the application; b) name, postal mail address, and e-mail address; optionally, telephone and fax numbers for the contact point within the requesting organization; c) full identification of the person submitting the application (including their
48、 role in the organization); d) time-scale for application of the allocated 3LC; e) estimated usage (number of codes) in code subspace under 3LC. 7.3.2 Registration announcement The second-level RA shall send a registration announcement to an applicant when the assignment of a 3LC has been agreed. Th
49、e registration announcement shall include at least the following information: a) the name of the organization submitting the application; b) the name, postal/electronic mail address and telephone/facsimile number for the contact point within the requesting organization; c) the full identification of the person submitting the application (including their role in the organization); d) the 3LC value and the class value assigned. 7.3.3 Notice for rejection Any applications for a 3LC shall be rejected b
