Add files using upload-large-folder tool

marked/Y/T-REC-F.747.6-201410-I_PDF-E/raw.md

@@ -0,0 +1,553 @@
+
+
+# ITU-T
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+## F.747.6
+
+(10/2014)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Audiovisual services
+
+# --- **Requirements for water quality assessment services using ubiquitous sensor networks (USNs)**
+
+Recommendation ITU-T F.747.6
+
+## ITU-T F-SERIES RECOMMENDATIONS **NON-TELEPHONE TELECOMMUNICATION SERVICES**
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| <b>TELEGRAPH SERVICE</b>                                        |                    |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemessage service                           | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| <b>MOBILE SERVICE</b>                                           |                    |
+| Mobile services and multideestination satellite services        | F.110–F.159        |
+| <b>TELEMATIC SERVICES</b>                                       |                    |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| <b>MESSAGE HANDLING SERVICES</b>                                | F.400–F.499        |
+| <b>DIRECTORY SERVICES</b>                                       | F.500–F.549        |
+| <b>DOCUMENT COMMUNICATION</b>                                   |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| <b>DATA TRANSMISSION SERVICES</b>                               | F.600–F.699        |
+| <b>AUDIOVISUAL SERVICES</b>                                     | <b>F.700–F.799</b> |
+| <b>ISDN SERVICES</b>                                            | F.800–F.849        |
+| <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b>                     | F.850–F.899        |
+| <b>HUMAN FACTORS</b>                                            | F.900–F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## Recommendation ITU-T F.747.6
+
+## Requirements for water quality assessment services using ubiquitous sensor networks (USN)
+
+## Summary
+
+To make a safe and ecologically healthy water environment, assessment of changes in water quality and water quality monitoring are required in rivers, lakes and other bodies of water. Recommendation ITU-T F.747.6 describes scenarios for the applications of water quality assessment and the sensor network technology that is the most suitable method to fulfil it.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T F.747.6  | 2014-10-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12226">11.1002/1000/12226</a> |
+
+## Keywords
+
+Ubiquitous sensor network (USN), water quality assessment (WQA).
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication 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 Standardization 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 technology which fall within ITU-T's 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 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 obligatory 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 of 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 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 consult the TSB patent database at <http://www.itu.int/ITU-T/ipr/>.
+
+© ITU 2015
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+|                                                                         | <b>Page</b> |
+|-------------------------------------------------------------------------|-------------|
+| 1 Scope.....                                                            | 1           |
+| 2 References.....                                                       | 1           |
+| 3 Definitions .....                                                     | 1           |
+| 3.1 Terms defined elsewhere.....                                        | 1           |
+| 3.2 Terms defined in this Recommendation.....                           | 2           |
+| 4 Abbreviations and acronyms .....                                      | 2           |
+| 5 Conventions .....                                                     | 3           |
+| 6 Overview of water quality assessment .....                            | 3           |
+| 7 Scenarios for WQA services.....                                       | 3           |
+| 7.1 Scenario I: Real-time water quality data aggregation .....          | 3           |
+| 7.2 Scenario II: Automatic WQA node control.....                        | 4           |
+| 7.3 Scenario III: WQA node surveillance and logging .....               | 5           |
+| 7.4 Scenario IV: Water quality prediction through software sensors..... | 6           |
+| 8 Requirements of WQA services .....                                    | 7           |
+| 8.1 Reliable data transfer .....                                        | 7           |
+| 8.2 Real-time water quality information transfer .....                  | 7           |
+| 8.3 Bidirectional communication .....                                   | 7           |
+| 8.4 Security.....                                                       | 7           |
+| 8.5 Water assessment modelling .....                                    | 7           |
+| 9 USN based WQA services.....                                           | 8           |
+| 9.1 Water quality distribution service .....                            | 8           |
+| 9.2 Water quality prediction service.....                               | 8           |
+| 9.3 Service for total amount of polluted water .....                    | 8           |
+| 10 USN capabilities for WQA services.....                               | 8           |
+| 10.1 Reliable communication link in sensor networks.....                | 8           |
+| 10.2 Transmission delay guarantee to the WQA server .....               | 8           |
+| 10.3 Low power consumption in sensor networks .....                     | 8           |
+| 10.4 Bidirectional communication between WQA nodes and servers .....    | 9           |
+| 10.5 Multi-hop data transfer in sensor networks .....                   | 9           |
+| 10.6 IP infrastructure compatibility.....                               | 9           |
+| 10.7 Long distance transmission support in sensor networks .....        | 9           |
+| 10.8 Security services .....                                            | 9           |
+| 10.9 Data logging .....                                                 | 9           |
+| 10.10 Maintainability of sensor networks .....                          | 9           |
+| 10.11 Naming and addressing in sensor networks .....                    | 9           |
+
+
+
+## Recommendation ITU-T F.747.6
+
+# Requirements for water quality assessment services using ubiquitous sensor networks (USNs)
+
+## 1 Scope
+
+This Recommendation identifies requirements and scenarios for water quality assessment (WQA) services using ubiquitous sensor networks (USNs). The scope of this Recommendation covers the following:
+
+- Overview of WQA;
+- WQA scenarios;
+- Requirements for WQA services;
+- USN capabilities for supporting the requirements of WQA services.
+
+## 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through 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 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.744] Recommendation ITU-T F.744 (2009), *Service description and requirements for ubiquitous sensor network middleware*.
+
+[ITU-T Y.2221] Recommendation ITU-T Y.2221 (2010), *Requirements for support of ubiquitous sensor network (USN) applications and services in the NGN environment*.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 processed data** [ITU-T F.744]: Data that are processed from raw sensed data by the sensor network or USN middleware.
+
+**3.1.2 sensed data** [ITU-T F.744]: Data sensed by a sensor that is attached to a specific sensor node.
+
+**3.1.3 sensor** [ITU-T Y.2221]: An electronic device that senses a physical condition or chemical compound and delivers an electronic signal proportional to the observed characteristic.
+
+**3.1.4 sensor network** [ITU-T Y.2221]: A network comprised of inter-connected sensor nodes exchanging sensed data by wired or wireless communication.
+
+**3.1.5 sensor node** [ITU-T Y.2221]: A device consisting of sensor(s) and optional actuator(s) with capabilities of sensed data processing and networking.
+
+NOTE– In WQA environment, these sensor nodes have sensing and networking capabilities except sensed data processing.
+
+**3.1.6 ubiquitous sensor network (USN)** [ITU-T Y.2221]: A conceptual network built over existing physical networks which makes use of sensed data and provides knowledge services to anyone, anywhere and at any time, and where the information is generated by using context awareness.
+
+**3.1.7 USN end-user** [ITU-T Y.2221]: An entity that uses the sensed data provided by USN applications and services. This end-user may be a system or a human.
+
+NOTE – In WQA environment, a WQA user is a kind of USN end-user. This may be a WQA application or a human.
+
+**3.1.8 USN gateway** [ITU-T Y.2221]: A node which interconnects sensor networks with other networks.
+
+NOTE – In WQA environment, the USN gateway has the sensed data processing capabilities.
+
+**3.1.9 USN middleware** [ITU-T Y.2221]: A set of logical functions to support USN applications and services.
+
+NOTE – In WQA environment, a WQA server is a kind of USN middleware. The main functionalities of it are sensor network management and sensor data mining and processing.
+
+### **3.2 Terms defined in this Recommendation**
+
+This Recommendation defines the following terms:
+
+**3.2.1 measured data:** The sensing data by a sensor that is attached to a specific sensor node.
+
+**3.2.2 software sensor:** Software that gets the processed and predicted data from measured real-time sensed data.
+
+NOTE – WQA server has the software estimating the processed data (e.g., total nitrogen (TN) and total phosphorus (TP) values) using the water quality parameters (e.g., potential of hydrogen (pH), dissolved oxygen (DO), electrical conductivity (EC)) aggregated from sensors in sensor networks in real-time.
+
+**3.2.3 water quality assessment (WQA) node:** A device measuring water quality and capable of sensing, processing, networking and optionally actuating.
+
+**3.2.4 WQA system:** The devices consisting of sensor nodes with sensors, a USN gateway and a WQA server in order to support the water quality assessment.
+
+## **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                                |
+|------|--------------------------------|
+| DO   | Dissolved Oxygen               |
+| EC   | Electrical Conductivity        |
+| IP   | Internet Protocol              |
+| IPv4 | Internet Protocol version four |
+| IPv6 | Internet Protocol version six  |
+| ORP  | Oxidation-Reduction Potential  |
+| pH   | Potential of Hydrogen          |
+| TN   | Total Nitrogen                 |
+| TP   | Total Phosphorus               |
+| USN  | Ubiquitous Sensor Network      |
+| WQA  | Water Quality Assessment       |
+
+## 5 Conventions
+
+None.
+
+## 6 Overview of water quality assessment
+
+The water quality assessment (WQA) monitors dispersion of water pollution, tracking of a water pollutant source and predicts water quality change using the values measured from the measurement devices covering a specified area. It plays an important role to improve water quality through its real-time management.
+
+WQA is divided into water quality management for wide areas and for middle and small-sized areas such as rivers or lakes. In the former case, it is easy to monitor a large water pollutant accident, while the latter is used to prevent the spread of water pollution and to monitor water pollution before the water pollutant, actually generated at middle and small-sized rivers, is diluted.
+
+Applications for the WQA include the smart farm (for example, the horticultural and livestock industries) and smart leisure (for example, fishing where the angler is interested in information related to water quality, or the different opinions about a water pollutant source among local communities). These applications use sensor network technologies to assess water quality. The WQA nodes with water quality sensors deliver sensing data in real-time to a WQA server via wireless or mobile networks. The sensed data are used to monitor the water quality and track the water pollutant source in real-time. Furthermore, the large-scale deployment of a sensor network enhances the density of the WQA node thus realizing reliable water quality assessment. Besides, unmanned long-term operation of the WQA system is possible through network management technologies together with low power consumption and automated control of sensors.
+
+Figure 1 shows the overall conceptual diagram for the WQA. The device with the water quality sensor, flow sensor, water level sensor, etc., by the rivers and lakes periodically measures the value of the water quality parameters (e.g., potential of hydrogen (pH), dissolved oxygen (DO)), the flow velocity, the water level, etc. The sensed data are delivered to the WQA server located in infrastructure network. WQA server estimates the WQA information based on the sensed data. WQA server provides the information to WQA users in real-time.
+
+![Overall conceptual diagram for WQA showing the flow from rivers/lakes with WQA nodes and gateway, through the Internet, to a WQA server, and finally to a WQA user.](b28af4985cdef1e519e3aaf26561dcb3_img.jpg)
+
+The diagram illustrates the overall conceptual architecture for Water Quality Assessment (WQA). It shows a sequence of components connected by lines: 
+ 1. **Rivers or lakes with WQA nodes and gateway**: Represented by an icon of a river/lake with industrial buildings and trees.
+ 2. **Internet**: Represented by a cloud icon.
+ 3. **WQA server**: Represented by an icon of a server rack and a monitor displaying data.
+ 4. **WQA user**: Represented by an icon of a person sitting at a desk with a monitor displaying data.
+ The flow is from left to right: Rivers or lakes with WQA nodes and gateway → Internet → WQA server → WQA user.
+
+Overall conceptual diagram for WQA showing the flow from rivers/lakes with WQA nodes and gateway, through the Internet, to a WQA server, and finally to a WQA user.
+
+F.747.6(14)\_F01
+
+**Figure 1 – Overall conceptual diagram for WQA**
+
+## 7 Scenarios for WQA services
+
+The scenarios for the WQA include the following entities: the WQA nodes, server and users and are done through the interaction among them.
+
+### 7.1 Scenario I: Real-time water quality data aggregation
+
+Scenario I describes procedures where the measured data for the WQA are delivered periodically to the WQA server and, subsequently, the water quality information is provided to users in real-time.
+
+- 1) The WQA server initially sets the data-sensing period of the WQA node.
+- 2) The WQA nodes obtain the measured data periodically from the rivers, lakes, etc.
+- 3) The data measured by the WQA nodes and gateway are delivered to the WQA server.
+- 4) Steps 2 and 3 above are repeated after waiting for the data-sensing period. The WQA server estimates the water quality to provide the distribution of each water parameter from the delivered measured data.
+
+NOTE – The procedures from step 1 to step 3 are obtaining periodic measured data. In the scenario II and III, below, the same procedures are used.
+
+- 5) The WQA server derives the water quality distribution map of each water quality item by applying the WQA model.
+- 6) The WQA server provides the information on the water quality distribution to the WQA users.
+
+![Sequence diagram illustrating real-time water quality data aggregation. The diagram shows five lifelines: Rivers or lakes, WQA node 1, WQA node 2, WQA server, and WQA user. A red dashed box encloses the initial data sensing period. Within this box, WQA node 1 and WQA node 2 repeatedly measure values from the rivers or lakes and send the measured data to the WQA server. The WQA server receives the data and performs a water quality assessment model and driving the water quality distribution map. The WQA server then provides the water quality distribution information to the WQA user. The diagram also shows the WQA server getting the periodic measured data from the WQA nodes.](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Rivers as Rivers or lakes
+    participant WQA1 as WQA node 1
+    participant WQA2 as WQA node 2
+    participant WQAserver as WQA server
+    participant WQAuser as WQA user
+
+    Note over WQA1, WQA2: The data sensing period
+    WQA1->>Rivers: Measuring a value
+    WQA2->>Rivers: Measuring a value
+    WQA1->>WQAserver: The measured data
+    WQA2->>WQAserver: The measured data
+    WQAserver->>WQA1: Waiting for the data sensing period
+    WQAserver->>WQA2: Waiting for the data sensing period
+    WQA1->>Rivers: Measuring a value
+    WQA2->>Rivers: Measuring a value
+    WQA1->>WQAserver: The measured data
+    WQA2->>WQAserver: The measured data
+    WQAserver->>WQA1: Waiting for the data sensing period
+    WQAserver->>WQA2: Waiting for the data sensing period
+    WQA1->>Rivers: Measuring a value
+    WQA2->>Rivers: Measuring a value
+    WQA1->>WQAserver: The measured data
+    WQA2->>WQAserver: The measured data
+    WQAserver->>WQA1: Waiting for the data sensing period
+    WQAserver->>WQA2: Waiting for the data sensing period
+    WQAserver->>WQAuser: Water quality distribution information
+    
+```
+
+F.747.6(14)\_F02
+
+Sequence diagram illustrating real-time water quality data aggregation. The diagram shows five lifelines: Rivers or lakes, WQA node 1, WQA node 2, WQA server, and WQA user. A red dashed box encloses the initial data sensing period. Within this box, WQA node 1 and WQA node 2 repeatedly measure values from the rivers or lakes and send the measured data to the WQA server. The WQA server receives the data and performs a water quality assessment model and driving the water quality distribution map. The WQA server then provides the water quality distribution information to the WQA user. The diagram also shows the WQA server getting the periodic measured data from the WQA nodes.
+
+**Figure 2 – Real-time water quality data aggregation**
+
+### 7.2 Scenario II: Automatic WQA node control
+
+The WQA server monitors the water quality parameters measured from the WQA nodes and then filters any faults to improve the accuracy of the WQA. It also distinguishes sensing faults from the aggregated sensed data. For example, the WQA server can operate the sensor wiper of WQA node to prevent bio-fouling.
+
+Scenario II describes procedures for long-term unmanned operation of the WQA where the WQA server recognizes the changes, or faults, of sensor values and automatically controls the data sensing period and the operation of the sensor wiper.
+
+- 1) When the WQA server analyses the measured data, and if a change to the data sensing period is required, it requests the WQA nodes to change the period.
+
+- 2) The WQA nodes obtain sensing data with the new data sensing period from the rivers, lakes, etc. The sensed data by the WQA node are delivered to the WQA server.  
+NOTE – The same procedure for obtaining the periodic measured data is used as in Figure 2.
+- 3) The WQA server examines the changes or faults of sensor values.
+- 4) When the WQA server recognizes changes, or faults, of sensor values, it automatically controls the data sensing period and the operation of the sensor wiper.
+
+![Sequence diagram titled 'Automatic WQA node control' showing interactions between 'Rivers or lakes', 'WQA node 1', 'WQA node 2', and 'WQA server'. The diagram illustrates a feedback loop where the server recognizes changes, adjusts the sensing period, and triggers a sensor wiper operation based on periodic data received from the nodes.](5b4e774d63e0e0ed73801a9247755e5f_img.jpg)
+
+```
+
+sequenceDiagram
+    participant RL as Rivers or lakes
+    participant WN1 as WQA node 1
+    participant WN2 as WQA node 2
+    participant WS as WQA server
+
+    WS->>WS: Recognizing the changes or faults of sensor values
+    WS->>WS: Changing a data sensing period
+    WS->>WN1: Getting the periodic measured data
+    WS->>WN2: Getting the periodic measured data
+    WS->>WS: Recognizing the changes or faults of sensor values
+    WS->>WN1: The information of the sensor wiper
+    WN1->>WN1: Operation of the sensor wiper
+  
+```
+
+F.747.6(14)\_F03
+
+Sequence diagram titled 'Automatic WQA node control' showing interactions between 'Rivers or lakes', 'WQA node 1', 'WQA node 2', and 'WQA server'. The diagram illustrates a feedback loop where the server recognizes changes, adjusts the sensing period, and triggers a sensor wiper operation based on periodic data received from the nodes.
+
+**Figure 3 – Automatic WQA node control**
+
+### 7.3 Scenario III: WQA node surveillance and logging
+
+Scenario III describes the procedure where the WQA server observes the WQA nodes and then detects, separates and diagnoses faults of the devices. If the communication between the WQA server and the WQA nodes is interrupted, the WQA node must log the measured data until it returns to a normal communication state. Thus, fault monitoring among the WQA nodes is important.
+
+- 1) The WQA nodes obtain the measured data in every period from the rivers, lakes, etc. The measured data are delivered to the WQA server.  
+NOTE – The same as the procedure for obtaining the periodic measured data is used as in Figure 2.
+- 2) The WQA server periodically performs surveillance of the WQA nodes.
+- 3) The device receiving a surveillance request delivers the result to the WQA server. On the other hand, when a node detects a fault, it is delivered to the server.
+- 4) When the communication between the WQA server and the WQA nodes is interrupted, the WQA node logs the measured data.
+
+![Sequence diagram illustrating WQA node surveillance and logging. The diagram shows four lifelines: Rivers or lakes, WQA node 1, WQA node 2, and WQA server. The process begins with 'Getting the periodic measured data' from Rivers or lakes to WQA node 1. WQA node 1 then performs 'Device fault surveillance' and sends the 'Result of device fault surveillance' to WQA node 2. WQA node 2 also performs 'Device fault surveillance' and sends the 'Result of device fault surveillance' to WQA node 1. A 'Waiting for the fault surveillance period' is indicated between the first and second surveillance results. WQA node 1 then sends 'Fault automatic detection' to WQA node 2. A 'Communication interruption' occurs between WQA node 1 and WQA node 2. Finally, WQA node 1 performs 'The measured data logging'.](d4af765160d04ecef538e5066006dc77_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Rivers as Rivers or lakes
+    participant WQA1 as WQA node 1
+    participant WQA2 as WQA node 2
+    participant WQAS as WQA server
+
+    Rivers->>WQA1: Getting the periodic measured data
+    WQA1->>WQA2: Device fault surveillance
+    WQA2-->>WQA1: Result of device fault surveillance
+    WQA1->>WQA2: Device fault surveillance
+    WQA2-->>WQA1: Result of device fault surveillance
+    Note over WQA1, WQA2: Waiting for the fault surveillance period
+    WQA1->>WQA2: Fault automatic detection
+    WQA1-->>WQA1: Communication interruption
+    WQA1->>WQA1: The measured data logging
+  
+```
+
+F.747.6(14)\_F04
+
+Sequence diagram illustrating WQA node surveillance and logging. The diagram shows four lifelines: Rivers or lakes, WQA node 1, WQA node 2, and WQA server. The process begins with 'Getting the periodic measured data' from Rivers or lakes to WQA node 1. WQA node 1 then performs 'Device fault surveillance' and sends the 'Result of device fault surveillance' to WQA node 2. WQA node 2 also performs 'Device fault surveillance' and sends the 'Result of device fault surveillance' to WQA node 1. A 'Waiting for the fault surveillance period' is indicated between the first and second surveillance results. WQA node 1 then sends 'Fault automatic detection' to WQA node 2. A 'Communication interruption' occurs between WQA node 1 and WQA node 2. Finally, WQA node 1 performs 'The measured data logging'.
+
+**Figure 4 – WQA node surveillance and logging**
+
+### 7.4 Scenario IV: Water quality prediction through software sensors
+
+Scenario IV describes procedures that predict values of water quality parameters through software sensors. In general, WQA nodes measure the values of water quality parameters (e.g., pH, DO, electrical conductivity (EC)) in real-time using water quality sensors. However, total nitrogen (TN) and total phosphorus (TP) values, which are important criterion parameters for judgment of water pollution, are not measured via the WQA nodes in real-time due to its measurement method. Hence, the values of these parameters are predicted through the software sensor in real-time. TN and TP values obtained from the software sensor are offered as the input values for the analysis of water quality distribution, tracking of a water pollutant source and the prediction of the water quality change.
+
+- 1) The WQA nodes obtain the measured data in every period from the rivers, lakes, etc.
+- 2) The measured data are delivered to the WQA server.
+- 3) The WQA server updates the estimation function of the software sensor with the measured data. Here, initial TN and TP values are time series data measured in advance (measured by getting the water samples and testing its quality at the laboratory or by underwater pumps at the monitoring stations that are built beside rivers). The rest of the values (e.g., pH, DO, EC) are time series data measured in real-time from WQA nodes.
+- 4) The WQA server performs the estimation function of the software sensor. The software sensor, based on the values measured from WQA nodes, estimates TN and TP values in real-time.
+- 5) The WQA server delivers the values from the software sensor module to the WQA module in order to analyse the water quality distribution, the water quality prediction and the total amount of water pollution.
+
+![Sequence diagram showing the process of water quality prediction through software sensors. The diagram involves four lifelines: Rivers or lakes, WQA node 1, WQA node 2, and WQA server. The process starts with 'Getting the periodic measured data' from Rivers or lakes to WQA node 1 and WQA node 2. Then, WQA node 2 sends data to WQA server. WQA server performs 'Performing the model update function of software sensor'. Then, WQA server sends data to WQA node 1 and WQA node 2. WQA node 1 sends data to WQA server. WQA server performs 'Performing the estimation function of software sensor: estimating the TN and TP values'. Then, WQA server sends 'Estimated TN and TP values' to WQA node 1 and WQA node 2. Finally, WQA node 1 and WQA node 2 are 'Ready for water quality assessment services'.](af7916c89a458fdab6c3f443217388ae_img.jpg)
+
+```
+
+sequenceDiagram
+    participant Rivers as Rivers or lakes
+    participant WQA1 as WQA node 1
+    participant WQA2 as WQA node 2
+    participant WQAserver as WQA server
+
+    Rivers->>WQA1: Getting the periodic measured data
+    Rivers->>WQA2: Getting the periodic measured data
+    WQA2->>WQAserver: 
+    WQAserver->>WQAserver: Performing the model update function of software sensor
+    WQAserver->>WQA1: Getting the periodic measured data
+    WQAserver->>WQA2: Getting the periodic measured data
+    WQA1->>WQAserver: 
+    WQAserver->>WQAserver: Performing the estimation function of software sensor: estimating the TN and TP values
+    WQAserver->>WQA1: Estimated TN and TP values
+    WQAserver->>WQA2: Estimated TN and TP values
+    WQA1->>WQAserver: Ready for water quality assessment services
+    WQA2->>WQAserver: Ready for water quality assessment services
+  
+```
+
+F.747.6(14)\_F05
+
+Sequence diagram showing the process of water quality prediction through software sensors. The diagram involves four lifelines: Rivers or lakes, WQA node 1, WQA node 2, and WQA server. The process starts with 'Getting the periodic measured data' from Rivers or lakes to WQA node 1 and WQA node 2. Then, WQA node 2 sends data to WQA server. WQA server performs 'Performing the model update function of software sensor'. Then, WQA server sends data to WQA node 1 and WQA node 2. WQA node 1 sends data to WQA server. WQA server performs 'Performing the estimation function of software sensor: estimating the TN and TP values'. Then, WQA server sends 'Estimated TN and TP values' to WQA node 1 and WQA node 2. Finally, WQA node 1 and WQA node 2 are 'Ready for water quality assessment services'.
+
+**Figure 5 – Water quality prediction through software sensors**
+
+## **8 Requirements of WQA services**
+
+### **8.1 Reliable data transfer**
+
+Because the WQA services such as dispersion of the water pollution, tracking of the water pollutant source and the prediction of the water quality change are using the values measured from the WQA nodes, reliable data transfer without any data loss from WQA node to WQA server is required.
+
+### **8.2 Real-time water quality information transfer**
+
+The WQA information including sensing data, aggregated data, control data, the results of water quality analysis, etc., is required to deliver to the WQA server in real-time. It allows the public authorities to monitor the information and to handle the water pollutant accident in real-time. It also satisfies the user's desires to receive the information in prompt.
+
+### **8.3 Bidirectional communication**
+
+While the WQA node offers information to the WQA server periodically, the WQA server delivers control information to the WQA node. Thus, the bidirectional communication is recommended to support the smooth operation of the WQA system.
+
+### **8.4 Security**
+
+Security services are required, for example, to protect the integrity, delivery and confidentiality of water quality data, in order to provide accurate WQA.
+
+### **8.5 Water assessment modelling**
+
+Precise water pollution dispersion, prediction and water pollutant source tracking by using the measured data are required. To achieve this and to provide WQA services accurate modelling of WQA is essential.
+
+## **9 USN-based WQA services**
+
+Ubiquitous sensor network (USN)-based WQA services are provided by the analysis of the data measured from sensors within the sensor network. A WQA server, using sensing data, assesses changes in water quality and performs water quality monitoring through the aggregated sensing data in real-time.
+
+The sensor network consists of WQA nodes with sensors and a gateway. Sensors measure the value of the water quality parameters (e.g., pH, DO, EC, oxidation-reduction potential (ORP)), the flow velocity, the water level, etc. The WQA nodes aggregate the sensing data from various sensors and send it to the USN gateway. The USN gateway also sends the aggregated data to the WQA server where the WQA is performed. Therefore, the WQA system provides following WQA services.
+
+### **9.1 Water quality distribution service**
+
+The water quality distribution service provides water quality distribution map of rivers, lakes, ponds, etc. in real-time where WQA nodes are installed. For the service, the WQA server calculates estimated values of TN and TP in real-time using a software sensor. The WQA server offers water quality distribution in real-time for water temperature, turbidity, pH, TN or TP of middle and small-sized rivers.
+
+### **9.2 Water quality prediction service**
+
+The water quality prediction service provides water quality prediction values of rivers, lakes, ponds, etc. in real-time where WQA nodes are installed. For the service, the WQA server calculates estimated values of TN and TP in real-time using a software sensor. The WQA server offers prediction of water quality change in real-time for TN or TP of medium and small-sized rivers.
+
+### **9.3 Service for total amount of polluted water**
+
+The total amount of polluted water service provides the total amount of the polluted water of rivers, lakes, ponds, etc. in real-time where WQA nodes are installed. For the service, the WQA server calculates estimated values of TN and TP in real-time using software sensor. The WQA server offers the total amount of water pollution in real-time for flow velocity, water level, TN or TP of medium and small-sized rivers.
+
+## **10 USN capabilities for WQA services**
+
+### **10.1 Reliable communication link in sensor networks**
+
+The sensor networks are deployed in a large area in an outdoor water environment. Even if they have poor radio environment, reliable delivery of sensing data is required. That is, the WQA system offers an optimal communication link considering its operation and the characteristics of the sensing information. It also has to guarantee high end-to-end success rate of the data transmission.
+
+### **10.2 Transmission delay guarantee to the WQA server**
+
+The measured data from sensors is delivered in real-time to the WQA server. For that, the transmission delay (for example, data processing time and transmission time in the sensor networks) is guaranteed. The transmission delay over the Internet is also guaranteed.
+
+### **10.3 Low power consumption in sensor networks**
+
+The sensor network needs to provide uninterruptible power for long-term unmanned operation in a broad area. It must have sensors or sensor nodes that consume low electric power. It also has to use low power mechanisms or its own power supply.
+
+### **10.4 Bidirectional communication between WQA nodes and servers**
+
+In general, the data in sensor networks are transferred in an upward direction. However, the control data, which are transferred in a downward direction, are needed to control the sensors and USN gateways for the unmanned long-term operation in WQA system. For example, Internet protocol (IP) infrastructure is a good candidate to support the bidirectional communication.
+
+### **10.5 Multi-hop data transfer in sensor networks**
+
+The sensor network is constructed with an almost linear topology and so the proper multi-hop networking protocol must be considered. WQA nodes must be able to deliver the measured data to the USN gateway through multi-hop paths.
+
+### **10.6 IP infrastructure compatibility**
+
+For the interworking between WQA nodes and WQA servers or between WQA servers and users, IP based networking is considered with the support of Internet protocol version four/Internet protocol version six (IPv4/IPv6) translation.
+
+Along with IP networking, the network management protocol is considered to monitor and operate the WQA nodes in real-time.
+
+### **10.7 Long distance transmission support in sensor networks**
+
+A sensor network may require long distance data transmission (for example, several kilometres) between WQA nodes and USN gateways. Proper communication distance in large area (for example, dozens of kilometres) outside must be guaranteed.
+
+### **10.8 Security services**
+
+The security services are required to protect the delivery of water quality information; to protect data confidentiality and integrity among WQA nodes; to provide authentication between WQA nodes and USN gateways; to provide data confidentiality between the USN gateway and WQA server; and to preform authorization, verification, etc.
+
+### **10.9 Data logging**
+
+The gateway keeps a record of the measured data to prevent data loss due to communication interruptions between the USN gateway and WQA server, server faults, the flooding of WQA nodes, etc.
+
+### **10.10 Maintainability of sensor networks**
+
+The network components in sensor network must be observed and faults must be detected automatically during unmanned long-term operation. Furthermore, the current network status can be optionally reported to the WQA server through the USN gateway. For the prevention of bio-fouling, the sensor control, including changing the data sensing period and operation of the sensor wiper, may be optionally controlled automatically.
+
+### **10.11 Naming and addressing in sensor networks**
+
+The WQA system has two key features: real-time support and direct control of sensors. To support these features, each WQA node with sensors is required to be uniquely distinguished by the naming and addressing method. Here, the naming is recommended to have the relation to river name, zone improvement plan (ZIP) code and others.
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+|                 |                                                                                             |
+|-----------------|---------------------------------------------------------------------------------------------|
+| Series A        | Organization of the work of ITU-T                                                           |
+| Series D        | General tariff principles                                                                   |
+| Series E        | Overall network operation, telephone service, service operation and human factors           |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                             |
+| Series G        | Transmission systems and media, digital systems and networks                                |
+| Series H        | Audiovisual and multimedia systems                                                          |
+| Series I        | Integrated services digital network                                                         |
+| Series J        | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K        | Protection against interference                                                             |
+| Series L        | Construction, installation and protection of cables and other elements of outside plant     |
+| Series M        | Telecommunication management, including TMN and network maintenance                         |
+| Series N        | Maintenance: international sound programme and television transmission circuits             |
+| Series O        | Specifications of measuring equipment                                                       |
+| Series P        | Terminals and subjective and objective assessment methods                                   |
+| Series Q        | Switching and signalling                                                                    |
+| Series R        | Telegraph transmission                                                                      |
+| Series S        | Telegraph services terminal equipment                                                       |
+| Series T        | Terminals for telematic services                                                            |
+| Series U        | Telegraph switching                                                                         |
+| Series V        | Data communication over the telephone network                                               |
+| Series X        | Data networks, open system communications and security                                      |
+| Series Y        | Global information infrastructure, Internet protocol aspects and next-generation networks   |
+| Series Z        | Languages and general software aspects for telecommunication systems                        |

marked/Y/T-REC-F.748.0-201410-I_PDF-E/raw.md

@@ -0,0 +1,516 @@
+
+
+I n t e r n a t i o n a l   T e l e c o m m u n i c a t i o n   U n i o n
+
+**ITU-T**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+**F.748.0**
+
+(10/2014)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Audiovisual services
+
+# --- **Common requirements for Internet of things (IoT) applications**
+
+Recommendation ITU-T F.748.0
+
+## ITU-T F-SERIES RECOMMENDATIONS NON-TELEPHONE TELECOMMUNICATION SERVICES
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               |                    |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemesssage service                          | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| MOBILE SERVICE                                                  |                    |
+| Mobile services and multideestination satellite services        | F.110–F.159        |
+| TELEMATIC SERVICES                                              |                    |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400–F.499        |
+| DIRECTORY SERVICES                                              | F.500–F.549        |
+| DOCUMENT COMMUNICATION                                          |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600–F.699        |
+| <b>AUDIOVISUAL SERVICES</b>                                     | <b>F.700–F.799</b> |
+| ISDN SERVICES                                                   | F.800–F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850–F.899        |
+| HUMAN FACTORS                                                   | F.900–F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.748.0
+
+# Common requirements for Internet of things (IoT) applications
+
+## Summary
+
+Recommendation ITU-T F.748.0 includes the common requirements for Internet of things (IoT) applications enabling advanced services by interconnecting (physical and virtual) things based on, existing and evolving, interoperable information and communication technologies.
+
+The requirements defined in this Recommendation are general requirements, and can therefore be applied to many kinds of IoT applications regardless of their types and characteristics.
+
+This Recommendation is based on the high-level requirements and the reference model defined in Recommendation ITU-T Y.2060.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T F.748.0  | 2014-10-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12228">11.1002/1000/12228</a> |
+
+## Keywords
+
+Internet of things, IoT, things, ubiquitous computing.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication 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 Standardization 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 technology which fall within ITU-T's 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 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 obligatory 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 of 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 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 consult the TSB patent database at <http://www.itu.int/ITU-T/ipr/>.
+
+© ITU 2015
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+|   |                                                                                           | Page |
+|---|-------------------------------------------------------------------------------------------|------|
+| 1 | Scope.....                                                                                | 1    |
+| 2 | References.....                                                                           | 1    |
+| 3 | Definitions .....                                                                         | 1    |
+|   | 3.1 Terms defined elsewhere.....                                                          | 1    |
+|   | 3.2 Terms defined in this Recommendation.....                                             | 2    |
+| 4 | Abbreviations and acronyms .....                                                          | 2    |
+| 5 | Conventions .....                                                                         | 2    |
+| 6 | Characteristics of things in the IoT.....                                                 | 2    |
+|   | 6.1 Fundamental characteristics .....                                                     | 2    |
+|   | 6.2 Common characteristics .....                                                          | 3    |
+|   | 6.3 Social characteristics .....                                                          | 3    |
+|   | 6.4 Autonomy of things.....                                                               | 3    |
+|   | 6.5 Capability of self-replication or control .....                                       | 3    |
+| 7 | Characteristics of IoT applications .....                                                 | 3    |
+|   | 7.1 Interconnectivity.....                                                                | 3    |
+|   | 7.2 Things-related services .....                                                         | 4    |
+|   | 7.3 Heterogeneity .....                                                                   | 4    |
+|   | 7.4 Dynamic changes.....                                                                  | 4    |
+|   | 7.5 Enormous scale.....                                                                   | 4    |
+|   | 7.6 Data gathering and processing by things.....                                          | 4    |
+|   | 7.7 Collaborative data processing.....                                                    | 4    |
+|   | 7.8 Maintenance-free operation.....                                                       | 4    |
+|   | 7.9 Self-adaptation.....                                                                  | 5    |
+|   | 7.10 Energy efficiency and operating lifetime .....                                       | 5    |
+|   | 7.11 Embedded intelligence .....                                                          | 5    |
+|   | 7.12 Location considerations.....                                                         | 5    |
+|   | 7.13 Auto-configuring reliable information transmission over ubiquitous<br>networks ..... | 5    |
+|   | 7.14 Security.....                                                                        | 6    |
+|   | 7.15 Privacy.....                                                                         | 6    |
+|   | 7.16 Infrastructure-less versus infrastructure-based application .....                    | 6    |
+|   | 7.17 Observation and/or actuation vs. data exchanges.....                                 | 6    |
+|   | 7.18 Application domains.....                                                             | 6    |
+| 8 | Common requirements for IoT applications.....                                             | 7    |
+|   | 8.1 Identification.....                                                                   | 7    |
+|   | 8.2 Identification-based connectivity .....                                               | 7    |
+|   | 8.3 Interoperability .....                                                                | 7    |
+|   | 8.4 Autonomic networking.....                                                             | 7    |
+
+|                                                                    | <b>Page</b> |
+|--------------------------------------------------------------------|-------------|
+| 8.5     Autonomic services provisioning .....                      | 8           |
+| 8.6     Location-based capabilities .....                          | 8           |
+| 8.7     Security .....                                             | 8           |
+| 8.8     Privacy protection .....                                   | 8           |
+| 8.9     Plug and play .....                                        | 8           |
+| 8.10    Manageability .....                                        | 8           |
+| 8.11    Compliance with laws and regulations .....                 | 8           |
+| 8.12    Awareness of service .....                                 | 8           |
+| 8.13    Mobility support .....                                     | 9           |
+| 8.14    Scalability support .....                                  | 9           |
+| 8.15    Robustness against dynamic changes .....                   | 9           |
+| 8.16    Self-organization (re-organization) and self-healing ..... | 9           |
+| 8.17    Energy efficient operation .....                           | 9           |
+| 8.18    Common data format for collaborative data processing ..... | 9           |
+| Bibliography .....                                                 | 10          |
+
+## Recommendation ITU-T F.748.0
+
+# Common requirements for Internet of things (IoT) applications
+
+## 1 Scope
+
+This Recommendation defines the common requirements for Internet of things (IoT) applications based on [ITU-T Y.2060].
+
+This Recommendation covers the following from the application point of view:
+
+- overview of the IoT applications;
+- characteristics of the IoT applications;
+- common requirements for the IoT applications.
+
+NOTE – This Recommendation mainly focuses on the viewpoint of the IoT applications. The network layer aspect of the IoT is out of scope of this Recommendation.
+
+## 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through 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 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 Y.2060] Recommendation ITU-T Y.2060 (2012), *Overview of the Internet of things*.
+
+[ISO/IEC 29182-1] ISO/IEC 29182-1 (2013), *Sensor networks: Sensor Network Reference Architecture (SNRA) – Part 1: General overview and requirements*.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 data fusion** [ISO/IEC 29182-1]: Deriving information by processing data from various sources.
+
+**3.1.2 Internet of things (IoT)** [ITU-T Y.2060]: A global infrastructure for the information society, enabling advanced services by interconnecting (physical and virtual) things based on existing and evolving interoperable information and communication technologies.
+
+NOTE 1 – Through the exploitation of identification, data capture, processing and communication capabilities, the IoT makes full use of things to offer services to all kinds of applications, whilst ensuring that security and privacy requirements are fulfilled.
+
+NOTE 2 – From a broad perspective, the IoT can be perceived as a vision with technological and societal implications.
+
+**3.1.3 thing** [ITU-T Y.2060]: With regard to the Internet of things, this is an object of the physical world (physical things) or of the information world (virtual things), which is capable of being identified and integrated into communication networks.
+
+### **3.2 Terms defined in this Recommendation**
+
+None.
+
+## **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                                |
+|------|--------------------------------|
+| IoT  | Internet of Things             |
+| M2M  | Machine-to-Machine             |
+| MOC  | Machine Oriented Communication |
+| MTC  | Machine-Type Communication     |
+| QoS  | Quality of Service             |
+| RFID | Radio Frequency Identification |
+| SOA  | Service Oriented Architecture  |
+| USN  | Ubiquitous Sensor Network      |
+
+## **5 Conventions**
+
+In this Recommendation:
+
+- The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this document is to be claimed.
+- The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus this requirement need not be present to claim conformance.
+- The keywords "can optionally" and "may" indicate an optional requirement which is permissible, without implying any sense of being recommended. These terms are not intended to imply that the vendor's implementation must provide the option and the feature can be optionally enabled by the network operator/service provider. Rather, it means the vendor may optionally provide the feature and still claim conformance with the specification.
+
+## **6 Characteristics of things in the IoT**
+
+[ITU-T Y.2060] explains the concept of the Internet of things (IoT) as a vision with technological and social implications. In addition, the IoT can be viewed as a global infrastructure for the information society, enabling advanced services by interconnecting (physical and virtual) things based on, existing and evolving, interoperable information and communication technologies.
+
+Things in the IoT can be characterized using five criteria: fundamental, common, social, autonomy and capability of self-replication or control [b-CERP-IoT].
+
+### **6.1 Fundamental characteristics**
+
+Fundamentally, things have characteristics as follows:
+
+- Things can be "real world entities" or "virtual entities";
+- Things have identity and there are means for identifying (automatically or manually) them, for example barcode and radio frequency identification (RFID);
+- Things and their associated information (their virtual representations) respect the privacy, security and safety of other things or people with which they interact;
+- Association (or relation) among things (both physical and virtual) and the related information is as important as the things and the information in IoT application; and
+
+- Things communicate with each other via the infrastructure or the infrastructure-less communications means.
+
+### **6.2 Common characteristics**
+
+There are common characteristics in things as follows:
+
+- Things can use services that act as interfaces to things;
+- Things could be competing with other things for resources, services and subject to selective pressures;
+- Things may have embedded or attached sensors (and/or actuators), thus they can interact with their environment;
+- Things use protocols to communicate with each other and the infrastructure; and
+- Things are environmentally safe, where things are devices for identification, sense or communication, etc.
+
+### **6.3 Social characteristics**
+
+Things have the following social characteristics towards other things or people:
+
+- Things can communicate with other things, computing devices and with people;
+- Things can collaborate to create groups or networks;
+- Things can initiate communication without human intervention;
+- Things can create, manage and destroy other things; and
+- Things can respect the privacy, security and safety of other things or people with which they interact.
+
+### **6.4 Autonomy of things**
+
+Autonomy is an important feature of the IoT. The followings are characteristics of autonomous things:
+
+- Things can do many tasks autonomously;
+- Things can negotiate, understand and adapt to their environment;
+- Things can extract patterns from the environment or to learn from other things;
+- Things can take decisions through their reasoning capabilities; and
+- Things can selectively transform or evolve and propagate information.
+
+### **6.5 Capability of self-replication or control**
+
+Autonomous things tend to have a capability of self-replication or control under specific conditions.
+
+- Things can create, manage and destroy other things.
+
+## **7 Characteristics of IoT applications**
+
+NOTE – Characteristics given in clauses 7.1 to 7.5 refer to [ITU-T Y.2060] and characteristics given in clauses 7.6 to 7.10 refer to [ISO/IEC 29182-1].
+
+### **7.1 Interconnectivity**
+
+In the IoT, anything will be inter-connected with the global information and communication infrastructure.
+
+### **7.2 Things-related services**
+
+The IoT is capable of providing thing-related services within the constraints of things, such as privacy protection and semantic consistency between physical things and their associated virtual things. In order to provide thing-related services within the constraints of things, both the technologies in the physical world and information world will change.
+
+### **7.3 Heterogeneity**
+
+The devices in the IoT are heterogeneous and based on different hardware platforms and networks. They can interact with other devices or service platforms through different networks.
+
+### **7.4 Dynamic changes**
+
+The state of devices change dynamically, e.g., sleeping and waking up, connected and/or disconnected as well as the context of devices including location and speed. Moreover, the number of devices involved can change dynamically.
+
+### **7.5 Enormous scale**
+
+The number of devices that need to be managed and that communicate with each other will be at least an order of magnitude larger than the devices connected to the current Internet. The ratio of communication triggered by devices as compared to communication triggered by humans will noticeably shift towards device-triggered communication. Even more critical will be the management of the data generated and their interpretation for application purposes. This relates to semantics of data, as well as efficient data handling.
+
+### **7.6 Data gathering and processing by things**
+
+IoT devices gather data from the real world and pre-process the data. Then IoT services are provided to the user, either directly from IoT devices or via a service provider.
+
+NOTE – As seen in the definition of the IoT, sensor network technology is one of the key enablers for IoT services. [ISO/IEC 29182-1] describes the characteristics and defines the requirements of sensor networks. This clause rephrases the characteristics described in [ISO/IEC 29182-1] for reflecting the characteristics of the IoT.
+
+### **7.7 Collaborative data processing**
+
+In IoT applications, IoT devices may collaborate to solve complex sensing problems such as the detection, classification and tracking of objects in the physical world. The data from an IoT device may be pre-processed and refined at the IoT device acquiring the data or at another IoT device.
+
+Depending on the application, intermediate data, such as features or estimated parameters, may be extracted from the captured data during pre-processing. The results from this pre-processing may be shared among IoT devices. Once shared, the intermediate data from the multiple IoT devices can be transformed into context data and situation information by data fusion.
+
+NOTE – As seen in the definition of the IoT, sensor network technology is one of the key enablers for IoT services. [ISO/IEC 29182-1] describes the characteristics and defines the requirements of sensor networks. This clause rephrases the characteristics described in [ISO/IEC 29182-1] for reflecting the characteristics of the IoT.
+
+### **7.8 Maintenance-free operation**
+
+IoT devices may have to operate for long periods of time without maintenance or technical support to resolve problems. Provision of remote diagnostics and resolution may be required.
+
+NOTE – As seen in the definition of the IoT, sensor network technology is one of the key enablers for IoT services. [ISO/IEC 29182-1] describes the characteristics and defines the requirements of sensor networks.
+
+This clause rephrases the characteristics described in [ISO/IEC 29182-1] for reflecting the characteristics of the IoT.
+
+### **7.9 Self-adaptation**
+
+IoT devices may self-adapt to accommodate changing operating conditions, to support robustness and reliability and to optimize resource management and functionality.
+
+NOTE – As seen in the definition of the IoT, sensor network technology is one of the key enablers for IoT services. [ISO/IEC 29182-1] describes the characteristics and defines the requirements of sensor networks. This clause rephrases the characteristics described in [ISO/IEC 29182-1] for reflecting the characteristics of the IoT.
+
+### **7.10 Energy efficiency and operating lifetime**
+
+Energy management is important in many IoT devices where the IoT device is battery-operated and it is desirable for the device to be operational for as long as possible. Energy harvesting technologies may help with energy management and extending the device lifetime.
+
+NOTE – As seen in the definition of the IoT, sensor network technology is one of the key enablers for IoT services. [ISO/IEC 29182-1] describes the characteristics and defines the requirements of sensor networks. This clause rephrases the characteristics described in [ISO/IEC 29182-1] for reflecting the characteristics of the IoT.
+
+### **7.11 Embedded intelligence**
+
+Embedded intelligence can be defined as the capability of things to collect information of the surroundings and analyse it to learn the state of the real world, possibly interacting with other widely deployed things. Smart things (or intelligent objects [b-SPRINGER-TRON]) are things with embedded intelligence that can interoperate with each other and can act independently if necessary.
+
+Embedded intelligence (sometimes called ambient intelligence) and autonomous control will be integrated into IoT devices. The IoT is a large non-deterministic and open network in which auto-organized or intelligent entities (web services, service oriented architecture (SOA) components), and virtual objects will interoperate with each other, and shall be able to act independently depending on the context, circumstances or environments.
+
+### **7.12 Location considerations**
+
+The precise geographic location of a thing and its precise geometrical dimensions will be critical (i.e., some things in the IoT will be sensor nodes in sensor networks. Sensor node location is important for many applications.)
+
+It is desirable to provide the location context to the things and, if appropriate, to IoT applications in order to take full of advantage of the IoT.
+
+### **7.13 Auto-configuring reliable information transmission over ubiquitous networks**
+
+According to the diversity of IoT services, the services information categories become much richer and differentiation of quality of service (QoS) in each category becomes more complicated than in existing networks. Information service, rather than connection service, will be a basic operation feature of the networks used in the IoT. As an infrastructure and support environment for a ubiquitous information society, ubiquitous networks will be an important feature in the IoT service environment. Reliable transmission technologies that are easy to set up or are auto-configuring are required in existing and/or evolving networks to provide ubiquitous and intelligent services and provide people with rich real-world information.
+
+### **7.14 Security**
+
+In the IoT, all things are connected which results in significant security threats, such as threats towards confidentiality, authenticity and integrity of both data and services. A critical example of security requirements is the need to integrate different security policies and techniques related to the variety of devices and user networks in the IoT.
+
+### **7.15 Privacy**
+
+Many things have their owners and users. Sensed data of things may contain private information concerning their owners or users. Unlike ordinary desktop and other legacy applications, in the IoT data may be collected by a ubiquitous sensor network (USN) without human users being aware of such collection.
+
+### **7.16 Infrastructure-less versus infrastructure-based application**
+
+Some IoT applications, such as machine-to-machine (M2M), machine-type communications (MTC), machine oriented communications (MOC) or USN-based applications, require network infrastructure (for example, Internet or mobile telecommunication networks as a delivery/backbone network). In contrast, some applications used in smart home or smart office may not require network infrastructure. These two types of application will have different requirements. Still, it is required that these two types of applications be able to talk to each other through proper gateways.
+
+### **7.17 Observation and/or actuation vs. data exchanges**
+
+Typically, things with embedded sensors observe physical environments and acquire information about surroundings. Based on this information, some devices are actuated (actuators) and physical surrounding can be controlled. Some applications, such as RFID applications for example, use data exchanges between things. In this type of application, data that the thing acquires from outside and/or holds inside are essential to provide the IoT services.
+
+### **7.18 Application domains**
+
+IoT applications can be deployed in many domains. Table 7-1 lists typical application domains. This list is not exhaustive.
+
+In the IoT, inter-domain applications will also be very common.
+
+For example, a pre-planning of an outdoor outing by a family or a group of friends can use the following services.
+
+- Information provided about transportation: train timetable and its operation status, expressway congestion, etc.
+- Weather services of regions to be visited.
+- Information about the environmental conditions of natural habitats such as mountains, rivers, lakes, marshes, etc. of the area to be visited.
+- If the outing is overnight, information related to reservations (for example, hotel, camping sites or restaurants).
+- If someone in the group is physically challenged, information on accessibility.
+
+**Table 7-1 – Example of IoT application domains**
+
+| <b>Domains</b> | <b>Description</b>                                                                                                                                                                     | <b>Examples</b>                                                                                                                                                  |
+|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Industry       | Activities involving financial or commercial transactions among companies, organizations and other entities: These include business to business (B2B) and business to customers (B2Cs) | Manufacturing, logistics, service sector, banking, financial governmental authorities, intermediaries, etc.                                                      |
+| Environment    | Activities regarding the protection, monitoring and development of all natural resources                                                                                               | Agriculture and breeding, recycling, environmental management services, energy management, etc.                                                                  |
+| Society        | Activities/initiatives regarding the development and inclusion of societies, cities and people                                                                                         | Governmental services towards citizens and other society structures (e-participation), e-inclusion (e.g., elderly, disabled people), public transportation, etc. |
+| Home           | Activities concerning individual and family members                                                                                                                                    | Health monitoring for oneself (weight, sleeping hours, etc.), nutrition care by monitoring of diet taken by family members using Cloud database.                 |
+
+## **8 Common requirements for IoT applications**
+
+NOTE – Requirements given in clauses 8.2 to 8.10 refer to [ITU-T Y.2060]. The requirements of the IoT as a whole and the requirement for a single IoT application need to be considered separately. The requirements for IoT applications are defined here.
+
+### **8.1 Identification**
+
+For communication between things, unique identification of the thing to communicate is required before communication. Many identification schemes may be used, depending on the application (e.g., RFID applications, sensor network applications and M2M applications).
+
+### **8.2 Identification-based connectivity**
+
+IoT applications are required to support the establishment of connectivity between a thing and the IoT based on the thing's identifier.
+
+A common approach is required for handling the possible assignment of heterogeneous identifiers to different types of things (see clause 7.16).
+
+### **8.3 Interoperability**
+
+Interoperability is required to be ensured among heterogeneous and distributed systems for provision and consumption of a variety of information and services (see clauses 7.1 and 7.3). Proper gateways are required to be provided if infrastructure-less and infrastructure-based applications are mixed.
+
+### **8.4 Autonomic networking**
+
+Autonomic networking (such as self-management, self-configuring, self-healing, self-optimizing, and self-protecting techniques and/or mechanisms; see clause 7.13) may be supported in networking control functions of the IoT in order to adapt to different application domains (see clause 7.18), different communication environments (see clauses 7.1, 7.3 and 7.16) and large numbers and types of devices (see clause 7.5).
+
+### **8.5 Autonomic services provisioning**
+
+The services may be provided by capturing, communicating and processing automatically the data of things based on the rules configured by operators or customized by subscribers. Autonomic services may depend on the techniques of automatic data fusion and data mining. Some things may be equipped with actuators to act on the surrounding environment.
+
+### **8.6 Location-based capabilities**
+
+The IoT as a whole supports location-based services. Location-based capabilities may be optionally supported by IoT applications. Certain types of communications and services will depend on the location information of things and/or users. It is required to sense and track the location information automatically, unless security and/or privacy concerns dictate otherwise, when location information is necessary for an IoT application.
+
+### **8.7 Security**
+
+Generally accepted measures for providing confidentiality, authenticity and integrity of data are required to be provided to the things and servers after a proper threat-analysis is performed. The proper threat-analysis is required to pay attention the characteristics of an IoT application in particular (see clause 7.14)
+
+### **8.8 Privacy protection**
+
+Privacy protection is required to be supported in the IoT. IoT applications are required to support privacy protection during data transmission, aggregation, storage, mining and processing. Privacy protection is recommended to strike a balance and not to impose an undue barrier to data source authentication provided by the authentication requirement.
+
+### **8.9 Plug and play**
+
+Plug and play capability is an important feature to be supported in the IoT in order to enable on-the-fly generation for seamless integration and cooperation of interconnected things with applications, and for improving responsiveness of things to application requirements. IoT applications are recommended to support plug and play features (see clauses 7.8 and 7.13).
+
+### **8.10 Manageability**
+
+Manageability is required to be supported in the IoT in order to ensure normal network operations. IoT applications usually work automatically without people's participation, but their whole operation process should be manageable by the relevant parties.
+
+### **8.11 Compliance with laws and regulations**
+
+Communications and services may be constrained by laws and regulations. Such constraints are often found in location-based services (see clause 8.6), and services related to human body.
+
+Often security and privacy requirements are imposed by laws and regulations (see clauses 8.7 and 8.8). These are required to be obeyed in a global manner and IoT applications must meet local requirements as well.
+
+### **8.12 Awareness of service**
+
+Even though IoT services are generally available without human intervention, humans (the users of IoT services) may need to be aware of IoT services surrounding them. When IoT services are provided to a user, it is recommended that the user be able to notice (discover) their presence. This has implication for security and privacy protection (for example surveillance, see clauses 8.7 and 8.8) [b-EC-PRIVACY].
+
+### **8.13 Mobility support**
+
+IoT devices can be either mobile or static. When an IoT device moves from place to place, it is necessary to support mobility at the application level (such as service mobility between different service providers) as well as the network level. Therefore, IoT applications are recommended to support mobility of IoT devices.
+
+### **8.14 Scalability support**
+
+As stated in clause 7.5, the scale of the network of IoT devices may be huge. IoT applications are recommended to support scalability, including the number of devices, the volume of data traffic that needs to be communicated, etc.
+
+### **8.15 Robustness against dynamic changes**
+
+Clause 7.4 describes dynamic change of status of an IoT device. Therefore, IoT applications are recommended to provide robustness, e.g., seamless continuity and sustainability, against dynamic transformation and change of IoT devices.
+
+### **8.16 Self-organization (re-organization) and self-healing**
+
+IoT devices may provide maintenance-free operation and may be self-adaptable as described in clauses 7.8 and 7.9. For coping with these characteristics, IoT applications are recommended to support self-organization (re-organization) and self-healing of the application and the network on the IoT device to recover from failure or mal-function. This requirement is related to robustness against dynamic transformation and changes in clause 8.15.
+
+### **8.17 Energy efficient operation**
+
+IoT applications are recommended to operate IoT thing devices in a way that minimizes the necessary energy for operation. This will ensure longer battery life, if the devices are battery-operated (see clause 7.10), and longer maintenance-free operation (see clause 7.8). This will also help reduction of carbon gas emissions.
+
+### **8.18 Common data format for collaborative data processing**
+
+IoT applications are recommended to adopt common data formats (see clause 7.7). This is to facilitate the mixing and mashing of data gathered by many IoT applications (which adds value to the collected data as a whole) as well as to facilitate data exchange.
+
+## Bibliography
+
+- [b-CERP-IoT] *Vision and Challenges for Realizing the Internet of Things*, CERP-IoT (Cluster of European Research Projects on the Internet of things), Publication Office of The European Union, March 2010, ISBN 978-92-79-15088-3. Also available online at <http://bookshop.europa.eu/en/vision-and-challenges-for-realising-the-internet-of-things-pbKK3110323/>
+- [b-EC-PRIVACY] *Privacy and Data Protection Impact Assessment Framework for RFID Applications*, 2011. Available online at <http://cordis.europa.eu/fp7/ict/enet/documents/rfid-pia-framework-final.pdf>
+- [b-SPRINGER-TRON] *TRON Project 1987 Open Architecture Computer Systems*, Proceedings of the Third TRON Project Symposium, Springer Verlag, 1987, ISBN 978-4431700272.
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+|                 |                                                                                             |
+|-----------------|---------------------------------------------------------------------------------------------|
+| Series A        | Organization of the work of ITU-T                                                           |
+| Series D        | General tariff principles                                                                   |
+| Series E        | Overall network operation, telephone service, service operation and human factors           |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                             |
+| Series G        | Transmission systems and media, digital systems and networks                                |
+| Series H        | Audiovisual and multimedia systems                                                          |
+| Series I        | Integrated services digital network                                                         |
+| Series J        | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K        | Protection against interference                                                             |
+| Series L        | Construction, installation and protection of cables and other elements of outside plant     |
+| Series M        | Telecommunication management, including TMN and network maintenance                         |
+| Series N        | Maintenance: international sound programme and television transmission circuits             |
+| Series O        | Specifications of measuring equipment                                                       |
+| Series P        | Terminals and subjective and objective assessment methods                                   |
+| Series Q        | Switching and signalling                                                                    |
+| Series R        | Telegraph transmission                                                                      |
+| Series S        | Telegraph services terminal equipment                                                       |
+| Series T        | Terminals for telematic services                                                            |
+| Series U        | Telegraph switching                                                                         |
+| Series V        | Data communication over the telephone network                                               |
+| Series X        | Data networks, open system communications and security                                      |
+| Series Y        | Global information infrastructure, Internet protocol aspects and next-generation networks   |
+| Series Z        | Languages and general software aspects for telecommunication systems                        |

marked/Y/T-REC-F.748.2-201511-I_PDF-E/raw.md

@@ -0,0 +1,641 @@
+
+
+# ITU-T
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+# Y.4001/F.748.2
+
+(11/2015)
+
+SERIES Y: GLOBAL INFORMATION  
+INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS  
+AND NEXT-GENERATION NETWORKS, INTERNET OF  
+THINGS AND SMART CITIES
+
+Internet of things and smart cities and communities –  
+General
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+# --- **Machine socialization: Overview and reference model**
+
+Recommendation ITU-T Y.4001/F.748.2
+
+## ITU-T Y-SERIES RECOMMENDATIONS
+
+## GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES
+
+|                                                                    |                      |
+|--------------------------------------------------------------------|----------------------|
+| GLOBAL INFORMATION INFRASTRUCTURE                                  |                      |
+| General                                                            | Y.100–Y.199          |
+| Services, applications and middleware                              | Y.200–Y.299          |
+| Network aspects                                                    | Y.300–Y.399          |
+| Interfaces and protocols                                           | Y.400–Y.499          |
+| Numbering, addressing and naming                                   | Y.500–Y.599          |
+| Operation, administration and maintenance                          | Y.600–Y.699          |
+| Security                                                           | Y.700–Y.799          |
+| Performances                                                       | Y.800–Y.899          |
+| INTERNET PROTOCOL ASPECTS                                          |                      |
+| General                                                            | Y.1000–Y.1099        |
+| Services and applications                                          | Y.1100–Y.1199        |
+| Architecture, access, network capabilities and resource management | Y.1200–Y.1299        |
+| Transport                                                          | Y.1300–Y.1399        |
+| Interworking                                                       | Y.1400–Y.1499        |
+| Quality of service and network performance                         | Y.1500–Y.1599        |
+| Signalling                                                         | Y.1600–Y.1699        |
+| Operation, administration and maintenance                          | Y.1700–Y.1799        |
+| Charging                                                           | Y.1800–Y.1899        |
+| IPTV over NGN                                                      | Y.1900–Y.1999        |
+| NEXT GENERATION NETWORKS                                           |                      |
+| Frameworks and functional architecture models                      | Y.2000–Y.2099        |
+| Quality of Service and performance                                 | Y.2100–Y.2199        |
+| Service aspects: Service capabilities and service architecture     | Y.2200–Y.2249        |
+| Service aspects: Interoperability of services and networks in NGN  | Y.2250–Y.2299        |
+| Enhancements to NGN                                                | Y.2300–Y.2399        |
+| Network management                                                 | Y.2400–Y.2499        |
+| Network control architectures and protocols                        | Y.2500–Y.2599        |
+| Packet-based Networks                                              | Y.2600–Y.2699        |
+| Security                                                           | Y.2700–Y.2799        |
+| Generalized mobility                                               | Y.2800–Y.2899        |
+| Carrier grade open environment                                     | Y.2900–Y.2999        |
+| FUTURE NETWORKS                                                    | Y.3000–Y.3499        |
+| CLOUD COMPUTING                                                    | Y.3500–Y.3999        |
+| INTERNET OF THINGS AND SMART CITIES AND COMMUNITIES                |                      |
+| <b>General</b>                                                     | <b>Y.4000–Y.4049</b> |
+| Definitions and terminologies                                      | Y.4050–Y.4099        |
+| Requirements and use cases                                         | Y.4100–Y.4249        |
+| Infrastructure, connectivity and networks                          | Y.4250–Y.4399        |
+| Frameworks, architectures and protocols                            | Y.4400–Y.4549        |
+| Services, applications, computation and data processing            | Y.4550–Y.4699        |
+| Management, control and performance                                | Y.4700–Y.4799        |
+| Identification and security                                        | Y.4800–Y.4899        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## Recommendation ITU-T Y.4001/F.748.2
+
+# Machine socialization: Overview and reference model
+
+## Summary
+
+Recommendation ITU-T Y.4001/F.748.2 describes machine socialization, which enables machines to cooperate with one another via their relations with other machines. In machine socialization, machines can be identified, can communicate and can capture data using machine identifiers, features of machine capabilities and machine owners, etc. Machines can be socialized with the information of identified machines through the establishment of relations. This Recommendation provides an overview, requirements and a reference model for machine socialization.
+
+## History
+
+| Edition | Recommendation       | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T Y.4001/F.748.2 | 2015-11-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/12621">11.1002/1000/12621</a> |
+
+## Keywords
+
+Internet of things (IoT), machine socialization, social Internet of things, socialization, social web of things.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication 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 Standardization 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 technology which fall within ITU-T's 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 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 obligatory 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 of 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 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 consult the TSB patent database at <http://www.itu.int/ITU-T/ipr/>.
+
+© ITU 2016
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+|   |                                                               | <b>Page</b> |
+|---|---------------------------------------------------------------|-------------|
+| 1 | Scope.....                                                    | 1           |
+| 2 | References.....                                               | 1           |
+| 3 | Definitions .....                                             | 1           |
+|   | 3.1 Terms defined elsewhere.....                              | 1           |
+|   | 3.2 Terms defined in this Recommendation.....                 | 1           |
+| 4 | Abbreviations and acronyms .....                              | 2           |
+| 5 | Conventions .....                                             | 2           |
+| 6 | Overview of machine socialization .....                       | 2           |
+|   | 6.1 General overview of machine socialization .....           | 2           |
+|   | 6.2 Relations for socialization .....                         | 3           |
+|   | 6.3 Socialization under the same ownership of machines.....   | 5           |
+|   | 6.4 Socialization under different ownerships of machines..... | 5           |
+|   | 6.5 General procedures of machine socialization.....          | 5           |
+| 7 | Requirements for machine socialization.....                   | 6           |
+|   | 7.1 Standardized description of a machine.....                | 6           |
+|   | 7.2 Service discovery.....                                    | 6           |
+|   | 7.3 Standardized expression of relation.....                  | 6           |
+|   | 7.4 Dynamic update of relation .....                          | 7           |
+|   | 7.5 Multiple ways of establishing a relation.....             | 7           |
+|   | 7.6 Caching of relation information .....                     | 7           |
+|   | 7.7 Fault recovery for a relation .....                       | 7           |
+|   | 7.8 Resilience of relation.....                               | 7           |
+|   | 7.9 Negotiation of QoS.....                                   | 7           |
+|   | 7.10 Verification of ownership of a machine .....             | 7           |
+| 8 | Reference models of machine socialization .....               | 7           |
+|   | 8.1 Service model of machine socialization.....               | 7           |
+|   | 8.2 Functional model of machine socialization.....            | 8           |
+
+## Introduction
+
+Social relations existed between people before the appearance of social network services as known today. However, these social relations were constrained by time, location, space, etc.
+
+A social networking service is a platform that enables the building of social networks or social relations among people who share interests, activities, backgrounds or real-life connections. Unlike traditional social networks or social relations, social network services make it possible to connect people who share interests and activities across political, economic, and geographic borders, etc. In addition, social network services make it easy to create, maintain, strengthen and extend social networks or social relations.
+
+The most important factor in the use of social network services is the possibility of being able to cooperate with other people including crowd activities by sharing and exchanging information.
+
+According to the definition of the Internet of things (IoT), things or machines collect data (either environmental or non-environmental) and transfer this data to the information world through communication networks. Though things or machines are interconnected with one another, the important point of the IoT is in providing the capability for communication and data (either environmental or non-environmental) capture to things or machines. Without collaboration or cooperation between things or machines, they may remain isolated and constrained from a capability point of view.
+
+Because humans have an always-on networking capability, a social network service becomes a great way to share and exchange information. Using this capability, it is easy for humans to acquire information on the experience, knowledge and capability of other humans without the barriers associated with time, space, etc.
+
+Consequently, it can be easily understood that all networked things or machines will:
+
+- produce numerous items of meaningful information or more specifically, captured data, occasionally pre-processed by things or machines;
+- evolve intellectually and then converse with one another, in other words, they will be socialized.
+
+To enable things to communicate what they do or need, follow one another, discuss with one another, collaborate, create events and do things together demands the socialization of machines to a level corresponding to that of social relations among humans.
+
+## Recommendation ITU-T F.748.2
+
+# Machine socialization: Overview and reference model
+
+## 1 Scope
+
+This Recommendation specifies machine socialization which enables machines to cooperate with one another using their relations with other machines. This Recommendation covers the following:
+
+- overview of machine socialization;
+- requirements for machine socialization; and
+- reference models of machine socialization including a service model and functional model.
+
+## 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through 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 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 Y.4000] Recommendation ITU-T Y.4000/Y.2060 (2012), *Overview of the Internet of things*.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 Internet of things (IoT)** [ITU-T Y.4000]: A global infrastructure for the information society, enabling advanced services by interconnecting (physical and virtual) things based on existing and evolving interoperable information and communication technologies.
+
+NOTE 1 – Through the exploitation of identification, data capture, processing and communication capabilities, the IoT makes full use of things to offer services to all kinds of applications, whilst ensuring that security and privacy requirements are fulfilled.
+
+NOTE 2 – From a broader perspective, the IoT can be perceived as a vision with technological and societal implications.
+
+**3.1.2 thing** [ITU-T Y.4000]: In the Internet of things, this is an object of the physical world (physical things) or of the information world (virtual things), which is capable of being identified and integrated into communication networks.
+
+### 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 machine:** An object of the physical world which is capable of being identified and of communicating, computing and processing data.
+
+**3.2.2 machine socialization:** Enabling things or machines to communicate what they do or what they need, as well as to follow one another, discuss with one another and collaborate with one another.
+
+**3.2.3 relation:** An association between or among machines or things enabling machines or things to share or to provide the capability to achieve a task in collaboration. This includes scheduling of processes between or among machines or things to perform a task.
+
+**3.2.4 sociality:** The tendency of things or machines to be in the state of socialization.
+
+## **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                                |
+|------|--------------------------------|
+| E-R  | Entity Relationship            |
+| IoT  | Internet of Things             |
+| M2M  | Machine to Machine             |
+| QoS  | Quality of Service             |
+| RFID | Radio Frequency Identification |
+| XML  | Extensible Markup Language     |
+
+## **5 Conventions**
+
+The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted if conformance to this Recommendation is to be claimed.
+
+The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus this requirement need not be present to claim conformance.
+
+## **6 Overview of machine socialization**
+
+### **6.1 General overview of machine socialization**
+
+The Internet of things (IoT) is defined as a global infrastructure for the information society, enabling advanced services by interconnecting (physical and virtual) things based on existing and evolving interoperable information and communication technologies. Through the exploitation of identification, data capture, processing and communication capabilities, the IoT makes full use of things to offer services to all kinds of applications, while ensuring that security and privacy requirements are fulfilled. From a broader perspective, the IoT can be perceived as a vision with technological and societal implications [ITU-T Y.4000]. Other definitions on the IoT can be found, however they do not have any significant differences.
+
+According to the existing definitions of the IoT, things or machines collect data (either environmental or non-environmental) and transfer it to the information world through communication networks. In other words, current understating of the IoT is reduced to merely a collection of world-wide sensor networks and radio frequency identification (RFID) systems and global machine-to-machine (M2M) systems. Though things or machines are interconnected with one another, the point of interest of the IoT is in providing capability for communication and data capture to things or machines. However, expectations for the IoT go beyond sensor networks, RFID and M2M, etc., as these are just some of the enablers for the IoT.
+
+Like the human experience of using social network services to obtain information on the knowledge and capabilities of other people, unrestricted by barriers of time and place, etc., machines can communicate and say what they do or what they need, they can follow one another, discuss, collaborate, create events and do things together. This involves the socialization of machines to a level corresponding to that of the social relations of humans.
+
+Figure 1 depicts a conceptual model of machine socialization. In machine socialization, machines are capable of basic communication and computing. For machine socialization, machines should at least be able to discover other machines and obtain information about the properties of other machines such as capability (service that the machine can provide) and interface.
+
+In Figure 1, M3 locates in the home and office whereas M2 locates in public and the home. When M3 locates in the office, M3 has M4 and M5 as its neighbourhood. M4 and M5 have different properties from the properties of M1 and M2 which locate in M3's home. If M3 is socialized with M4 and M5, M3 is able to collaborate with M4 and M5.
+
+M3 can do different jobs when M3 is socialized with M4 and M5 compared to the socialization with M1 and M2 because M4 and M5 provide different services. M2 also has M1, M3 and M6 and M7 as its neighbourhood in home and public. From the socialization with both neighbourhoods in home and public, M2 can do different jobs when it locates in home and in public respectively.
+
+The capability of machines can be extended through socializations supporting collaboration, and machines can be socialized with many other types of machines. This means that machines can extend their capability in different ways using various socializations.
+
+![Figure 1: Conceptual model of machine socialization. The diagram shows a flow from 'Discovery of machine' to 'Socialization of machine'. 'Discovery of machine' branches into 'Presence' and 'Properties'. 'Socialization of machine' branches into three locations: 'Home', 'Public', and 'Office'. In 'Home', machines M1, M2, and M3 are shown. In 'Public', machines M2, M6, and M7 are shown. In 'Office', machines M3, M4, and M5 are shown. Arrows indicate socialization links: M1 and M2 connect to M3 in the Home location; M2 connects to M6 and M7 in the Public location; M3 connects to M4 and M5 in the Office location. A circular arrow icon is on the main process arrow.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg)
+
+Y.4001-F.748.2(15)\_F01
+
+Figure 1: Conceptual model of machine socialization. The diagram shows a flow from 'Discovery of machine' to 'Socialization of machine'. 'Discovery of machine' branches into 'Presence' and 'Properties'. 'Socialization of machine' branches into three locations: 'Home', 'Public', and 'Office'. In 'Home', machines M1, M2, and M3 are shown. In 'Public', machines M2, M6, and M7 are shown. In 'Office', machines M3, M4, and M5 are shown. Arrows indicate socialization links: M1 and M2 connect to M3 in the Home location; M2 connects to M6 and M7 in the Public location; M3 connects to M4 and M5 in the Office location. A circular arrow icon is on the main process arrow.
+
+**Figure 1 – Conceptual model of machine socialization**
+
+### 6.2 Relations for socialization
+
+As defined in clause 3, a relation is an association between or among machines to share or provide capability. A relation also specifies the schedule of processes between or among machines while performing the task in collaboration.
+
+Establishing a relation enables machines to collaborate with other machines in a form of capabilities sharing.
+
+Figure 2 depicts an entity relationship (E-R) diagram of socialization which associates two machines by a relation.
+
+![E-R diagram of socialization showing relationships between Task, Service, Relation, and Machine entities.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg)
+
+```
+
+    graph TD
+      Task[Task]
+      Service[Service]
+      Relation[Relation  
+Involved machines  
+Procedure (schedule of process)]
+      Machine1[Machine  
+ID  
+Properties  
+- Origin  
+- Capabilities  
+- Position  
+...]
+      Machine2[Machine  
+ID  
+Properties  
+- Origin  
+- Capabilities  
+- Position  
+...]
+
+      Task -- "is achieved by" --> Service
+      Service -- "is provided by" --> Relation
+      Relation -- "is an association of" --> Machine1
+      Relation -- "is an association of" --> Machine2
+  
+```
+
+The diagram illustrates the relationships between four entities: Task, Service, Relation, and Machine. Task and Service are connected by a relationship 'is achieved by'. Service and Relation are connected by a relationship 'is provided by'. Relation and two Machine entities are connected by a relationship 'is an association of'. The Relation entity includes attributes 'Involved machines' and 'Procedure (schedule of process)'. Each Machine entity includes attributes 'ID', 'Properties', 'Origin', 'Capabilities', 'Position', and an ellipsis '...'. The Machine entity on the right is also labeled 'Machine' at the top.
+
+E-R diagram of socialization showing relationships between Task, Service, Relation, and Machine entities.
+
+Y.4001-F.748.2(15)\_F02
+
+**Figure 2 – E-R diagram of socialization**
+
+As shown in Figure 2, socialization can be established by establishing a relation or relations. A relation is an association between or among machines to enable a machine to expose its capabilities to other machines for collaboration. Once a machine is associated with other machine(s) as a relation, their capabilities can be exchanged to achieve a given task.
+
+Figure 3 presents an E-R diagram of a relation as an example. In this example, three machines are associated as a relation. Each machine has different properties and capabilities. This relation includes machine information of machines that are involved in socialization and also includes procedures to be carried out in each machine to achieve a given task. This procedure defines sequential actions for each machine and the relationship between or among capabilities of the machines.
+
+In a relation, output from one machine can be transferred to another machine as an input. Display mirroring is an example of this property. Some vehicles can be associated with a smart phone for mirroring a smart phone's display. In this case, navigation information can be displayed in a vehicle with the aid of a smart phone, even if the vehicle does not have a navigation system.
+
+![E-R diagram of relation (example) showing Machine entities, a Relation entity, and a Relation_Info entity with their relationships.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg)
+
+The diagram illustrates an Entity-Relationship (E-R) model for relations. It features three main entities: **Machine**, **Relation**, and **Relation\_Info**.
+
+- Machine Entity (Left):**
+  - ID: A
+  - Properties:
+    - Origin: ...
+    - Capabilities: A
+    - Position: ...
+    - ...
+- Machine Entity (Middle):**
+  - ID: B
+  - Properties:
+    - Origin: ...
+    - Capabilities: B
+    - Position: ...
+    - ...
+- Machine Entity (Bottom):**
+  - ID: C
+  - Properties:
+    - Origin: ...
+    - Capabilities: C
+    - Position: ...
+    - ...
+- Relation Entity (Top):**
+  - Properties:
+    - Origin: ...
+    - Capabilities: ...
+    - Position: ...
+    - ...
+- Relation\_Info Entity (Right):**
+  - Involved machines: A, B, C
+  - Procedure (in order)
+    - In machine A: Perform capability A, and;
+    - In machines B and C: Parallely perform capability B and C, and;
+    - In machine C and A: Perform capability A with output from machine C
+    - ...
+
+**Relationships:**
+
+- A **Machine** entity (ID: A) is associated with a **Relation** entity via the relationship "is an association of".
+- A **Machine** entity (ID: B) is associated with a **Relation** entity via the relationship "is an association of".
+- A **Machine** entity (ID: C) is associated with a **Relation** entity via the relationship "is an association of".
+- A **Relation** entity is associated with a **Relation\_Info** entity via the relationship "is expressed as".
+
+E-R diagram of relation (example) showing Machine entities, a Relation entity, and a Relation\_Info entity with their relationships.
+
+Y.4001-F.748.2(15)\_F03
+
+**Figure 3 – E-R diagram of relation (example)**
+
+### 6.3 Socialization under the same ownership of machines
+
+Typically, machine socialization is established between or among machines which are under the same ownership. In the case of machine socialization under the same ownership, particular authentication and authorization of access to a machine is not necessary.
+
+### 6.4 Socialization under different ownerships of machines
+
+A user of a machine can configure his/her machine to expose its capability to other machines which are under different owners, or vice versa. When machine socialization is necessary between or among machines which are under different ownerships, particular authentications and authorizations are needed with respect to machine socialization under the same ownership.
+
+### 6.5 General procedures of machine socialization
+
+Figure 4 shows socialization procedures.
+
+![Sequence diagram illustrating socialization procedures between Machine 1, Machine 2, Machine N, and Human or machine.](d4af765160d04ecef538e5066006dc77_img.jpg)
+
+```
+
+sequenceDiagram
+    participant M1 as Machine 1
+    participant M2 as Machine 2
+    participant MN as Machine N
+    participant HM as Human or machine
+
+    HM->>M1: Assigning the task
+    M1->>M1: 1. Analysing the task
+    M1->>M2: 2. Retrieving machines around to achieve the task
+    M1->>MN: 3. Establishing relation between machines: Socialization
+    M1->>M2: 4. Achieving the task
+    M1->>M2: 5. Releasing the socialization
+  
+```
+
+The diagram shows a sequence of steps for socialization. It starts with 'Assigning the task' from 'Human or machine' to 'Machine 1'. 'Machine 1' then performs '1. Analysing the task'. Next, 'Machine 1' sends '2. Retrieving machines around to achieve the task' to 'Machine 2'. Then, 'Machine 1' sends '3. Establishing relation between machines: Socialization' to 'Machine N'. Finally, 'Machine 1' sends '4. Achieving the task' and '5. Releasing the socialization' to 'Machine 2'.
+
+Y.4001-F.748.2(15)\_F04
+
+Sequence diagram illustrating socialization procedures between Machine 1, Machine 2, Machine N, and Human or machine.
+
+**Figure 4 – Socialization procedures**
+
+A user can be a human or a machine. When a user assigns a task to a machine, the machine analyses the task. Through an analysis of the task, the machine obtains information about the capabilities needed to achieve the task. If capabilities that are needed are not supported by the machine, the machine starts to retrieve machines to provide those capabilities. Once the machine finds another machine to provide the capability, the machine tries to establish a relation with that machine and achieve the task through that relation. After achieving the task, the relation is released and socialization is also released.
+
+## **7 Requirements for machine socialization**
+
+This clause describes requirements for machine socialization from an application point of view; therefore, communication specific requirements are not covered.
+
+### **7.1 Standardized description of a machine**
+
+In a machine socialization, a machine has to find other machines from the perspective of their capability with which to be associated by a relation. To do this, the machine is required to present its machine capability(s) in a standardized way. Machine presentation is used to perform service discovery.
+
+### **7.2 Service discovery**
+
+For a machine to find other machines with the necessary capabilities, service discovery is required. Through service discovery, a machine can find other machines to be associated with.
+
+### **7.3 Standardized expression of relation**
+
+It is required to express relation information in a standardized form, for example as an extensible markup language (XML) schema. Relation information encompasses the machines involved, their association information with other machines and task information which is given to the machines, etc.
+
+### **7.4 Dynamic update of relation**
+
+Once a relation is established among machines under a given task, it is required to update a relation in runtime. This includes an update of the association status (leaving or joining the association of a machine) and an update of a given task.
+
+### **7.5 Multiple ways of establishing a relation**
+
+When a task is given to a particular machine, that machine is required to be capable of establishing relations with other machines in various ways. These may include that a separate object (server) analyses the task to determine machines with which it should be associated, or these procedures may be carried out by the machine itself.
+
+### **7.6 Caching of relation information**
+
+A device may have patterns to establish a relation in a specific area such as a home or an office where neighbouring devices are seldom changed. In this case, it is recommended to maintain or cache relation information in a device after accomplishing the task for rapid re-establishment of the relation.
+
+### **7.7 Fault recovery for a relation**
+
+When a fault occurs in a device performing a task in a form of machine socialization, it is recommended to recover the relation information after fault recovery in the machine.
+
+### **7.8 Resilience of relation**
+
+When a fault occurs in a relation, it is required to isolate the faulty device from a relation to keep a relation unaffected by the fault. The task performed by the faulty device can be taken over by another machine if available.
+
+### **7.9 Negotiation of QoS**
+
+In machine socialization, tasks are allocated to each machine in a relation according to capability. However, this does not mean that a machine can satisfy the full level of quality of service (QoS) for the given task. Therefore, it is required to be able to negotiate QoS when establishing a relation.
+
+### **7.10 Verification of ownership of a machine**
+
+A relation can be established under both the same ownership of machines and under different ownerships of machines. For this reason, it is required to verify the ownership of a machine.
+
+## **8 Reference models of machine socialization**
+
+The objective of machine socialization is to enable things to communicate what they do or what they need, follow one another, discuss with one another, collaborate, create events and do things together. This clause describes reference models of machine socialization including a service model and functional model.
+
+### **8.1 Service model of machine socialization**
+
+Feasible services by machine socialization may be varied and numerous from simple services such as display mirroring to complex services in which different functionalities are utilised by multiple socialized participants.
+
+However, a service model of machine socialization can be considered as one providing any services through relations between different machines.
+
+![Figure 5: Abstract service model diagram showing the relationships between Service, Relation, and Machine entities.](4801720824e4b5e2361a5564f91cfb70_img.jpg)
+
+```
+
+graph TD
+    Service[Service]
+    Relation[Relation  
+Involved machines  
+Procedure (schedule of process)]
+    Machine1[Machine  
+ID  
+Properties  
+- Origin  
+- Capabilities  
+- Position  
+...]
+    Machine2[Machine  
+ID  
+Properties  
+- Origin  
+- Capabilities  
+- Position  
+...]
+
+    Service <-->|is provided by| Relation
+    Machine1 -->|is an association of| Relation
+    Machine2 -->|is an association of| Relation
+  
+```
+
+The diagram illustrates the abstract service model. It features three main entities: **Service**, **Relation**, and **Machine**. The **Service** entity is connected to the **Relation** entity via a relationship labeled "is provided by". The **Relation** entity is defined by "Involved machines" and "Procedure (schedule of process)". The **Machine** entity is defined by "ID", "Properties" (including "Origin", "Capabilities", and "Position"), and "..." (indicating other properties). Two **Machine** entities are shown, both of which are associated with a **Relation** entity via a relationship labeled "is an association of".
+
+Figure 5: Abstract service model diagram showing the relationships between Service, Relation, and Machine entities.
+
+Y.4001-F.748.2(15)\_F05
+
+**Figure 5 – Abstract service model**
+
+Figure 5 depicts a service model of machine socialization. Machine socialization is a procedure of establishing relations among different machines to make machines communicate with one another what they do or what they need, follow one another, discuss with one another and collaborate with one another.
+
+Characteristics of a relation depend on the characteristics of services to be provided. For example, display mirroring in a vehicle between a smart phone and display unit of a vehicle is provided by a simple relation of display capability. In the case of a complex service, relations may be complex where various capabilities of different machines are associated.
+
+### 8.2 Functional model of machine socialization
+
+From a functional viewpoint, machine socialization is a process of establishing relations as explained above.
+
+![Figure 6: Functional model diagram showing the internal structure of Machine A and Machine B, including repositories, agents, and profiles.](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg)
+
+```
+
+graph TD
+    subgraph Machine_A [Machine A]
+        NR1[Neighborhood repository]
+        RR1[Relation repository]
+        RA1[Relation agent]
+        OR1[Ownership repository]
+        MP1[Machine profile]
+        NR1 --> RA1
+        RR1 --> RA1
+        RA1 --> OR1
+        RA1 --> MP1
+    end
+    subgraph Machine_B [Machine B]
+        NR2[Neighborhood repository]
+        RR2[Relation repository]
+        RA2[Relation agent]
+        MP2[Machine profile]
+        OR2[Ownership repository]
+        NR2 --> RA2
+        RR2 --> RA2
+        RA2 --> MP2
+        RA2 --> OR2
+    end
+    RA1 <--> RA2
+    UP1[User profile]
+    UP2[User profile]
+    OR1 --> UP1
+    OR2 --> UP2
+  
+```
+
+The diagram illustrates the functional model of machine socialization. It shows two machines, **Machine A** and **Machine B**, each containing a **Relation agent**. The **Relation agent** in Machine A is connected to a **Neighborhood repository** and a **Relation repository**. The **Relation agent** in Machine B is connected to a **Neighborhood repository** and a **Relation repository**. The **Relation agent** in Machine A is also connected to an **Ownership repository** and a **Machine profile**. The **Relation agent** in Machine B is also connected to a **Machine profile** and an **Ownership repository**. The **Relation agent** in Machine A is connected to the **Relation agent** in Machine B via an external interface. The **Ownership repository** in Machine A is connected to a **User profile**. The **Ownership repository** in Machine B is connected to a **User profile**. A legend at the bottom indicates that a line with an open circle represents an "External interface" and a line with a solid circle represents an "Internal interface".
+
+Figure 6: Functional model diagram showing the internal structure of Machine A and Machine B, including repositories, agents, and profiles.
+
+Y.4001-F.748.2(15)\_F06
+
+**Figure 6 – Functional model**
+
+Figure 6 depicts a functional model of machine socialization. Each machine has internal function blocks and internal interfaces as well as outgoing interfaces with external entities such as user profile or other machines.
+
+#### **8.2.1 Machine profile**
+
+Machine profile maintains capabilities with a standardized description of a machine as defined in clause 7.1. Machine profile is used to negotiate QoS as described in clause 7.9.
+
+#### **8.2.2 Neighbourhood repository**
+
+A neighbourhood repository stores information of machines with which associations are needed. Once a relation agent discovers the machines with the necessary capabilities which are needed for accomplishing the given task, as described in clause 7.2, the information of those machines is stored in a neighbourhood repository.
+
+#### **8.2.3 Relation repository**
+
+When a relation is established, the relation is represented as a standardized expression as described in clause 7.3. A relation repository maintains standardized expressions of established relations. Dynamic update of a relation as described in clause 7.4, caching of relation information as described in clause 7.6, fault recovery and resilience of relation as described in clauses 7.7 and 7.8, respectively are carried out on this relation repository.
+
+#### **8.2.4 Relation agent**
+
+A relation agent performs service discovery as described in clause 7.2, relation establishment and management are carried out as described in clauses 7.3, 7.4, 7.5, 7.6, 7.7, 7.8 and 7.9. A relation agent may perform limited functions in the case where preparation of a relation is carried out by a separate object (server) as described in clause 7.5.
+
+#### **8.2.5 Ownership repository**
+
+An ownership repository maintains the ownership information of a machine. When a relation is established, the ownership of a machine should be verified as described in clause 7.10. The ownership repository is involved in verification of ownership. The ownership repository may also interface with outside user profiles to check permissions for the establishment of a relation with the different ownerships of machines. In this case, a user profile outside the machine maintains the user's permission information for a relation.
+
+
+
+## ITU-T F-SERIES RECOMMENDATIONS NON-TELEPHONE TELECOMMUNICATION SERVICES
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               |                    |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemessage service                           | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| MOBILE SERVICE                                                  |                    |
+| Mobile services and multideestination satellite services        | F.110–F.159        |
+| TELEMATIC SERVICES                                              |                    |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400–F.499        |
+| DIRECTORY SERVICES                                              | F.500–F.549        |
+| DOCUMENT COMMUNICATION                                          |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600–F.699        |
+| <b>AUDIOVISUAL SERVICES</b>                                     | <b>F.700–F.799</b> |
+| ISDN SERVICES                                                   | F.800–F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850–F.899        |
+| HUMAN FACTORS                                                   | F.900–F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+|                 |                                                                                                                                                           |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A        | Organization of the work of ITU-T                                                                                                                         |
+| Series D        | General tariff principles                                                                                                                                 |
+| Series E        | Overall network operation, telephone service, service operation and human factors                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| Series G        | Transmission systems and media, digital systems and networks                                                                                              |
+| Series H        | Audiovisual and multimedia systems                                                                                                                        |
+| Series I        | Integrated services digital network                                                                                                                       |
+| Series J        | Cable networks and transmission of television, sound programme and other multimedia signals                                                               |
+| Series K        | Protection against interference                                                                                                                           |
+| Series L        | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M        | Telecommunication management, including TMN and network maintenance                                                                                       |
+| Series N        | Maintenance: international sound programme and television transmission circuits                                                                           |
+| Series O        | Specifications of measuring equipment                                                                                                                     |
+| Series P        | Terminals and subjective and objective assessment methods                                                                                                 |
+| Series Q        | Switching and signalling                                                                                                                                  |
+| Series R        | Telegraph transmission                                                                                                                                    |
+| Series S        | Telegraph services terminal equipment                                                                                                                     |
+| Series T        | Terminals for telematic services                                                                                                                          |
+| Series U        | Telegraph switching                                                                                                                                       |
+| Series V        | Data communication over the telephone network                                                                                                             |
+| Series X        | Data networks, open system communications and security                                                                                                    |
+| Series Y        | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities                               |
+| Series Z        | Languages and general software aspects for telecommunication systems                                                                                      |

marked/Y/T-REC-F.748.5-201511-I_PDF-E/raw.md

@@ -0,0 +1,721 @@
+
+
+**ITU-T**
+
+**Y.4413/F.748.5**
+
+(11/2015)
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+SERIES Y: GLOBAL INFORMATION  
+INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS  
+AND NEXT-GENERATION NETWORKS, INTERNET OF  
+THINGS AND SMART CITIES
+
+Internet of things and smart cities and communities –  
+Frameworks, architectures and protocols
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Audiovisual services
+
+# --- **Requirements and reference architecture of the machine-to-machine service layer**
+
+Recommendation ITU-T Y.4413/F.748.5
+
+## ITU-T Y-SERIES RECOMMENDATIONS
+
+## GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES
+
+## GLOBAL INFORMATION INFRASTRUCTURE
+
+|                                           |             |
+|-------------------------------------------|-------------|
+| General                                   | Y.100–Y.199 |
+| Services, applications and middleware     | Y.200–Y.299 |
+| Network aspects                           | Y.300–Y.399 |
+| Interfaces and protocols                  | Y.400–Y.499 |
+| Numbering, addressing and naming          | Y.500–Y.599 |
+| Operation, administration and maintenance | Y.600–Y.699 |
+| Security                                  | Y.700–Y.799 |
+| Performances                              | Y.800–Y.899 |
+
+## INTERNET PROTOCOL ASPECTS
+
+|                                                                    |               |
+|--------------------------------------------------------------------|---------------|
+| General                                                            | Y.1000–Y.1099 |
+| Services and applications                                          | Y.1100–Y.1199 |
+| Architecture, access, network capabilities and resource management | Y.1200–Y.1299 |
+| Transport                                                          | Y.1300–Y.1399 |
+| Interworking                                                       | Y.1400–Y.1499 |
+| Quality of service and network performance                         | Y.1500–Y.1599 |
+| Signalling                                                         | Y.1600–Y.1699 |
+| Operation, administration and maintenance                          | Y.1700–Y.1799 |
+| Charging                                                           | Y.1800–Y.1899 |
+| IPTV over NGN                                                      | Y.1900–Y.1999 |
+
+## NEXT GENERATION NETWORKS
+
+|                                                                   |               |
+|-------------------------------------------------------------------|---------------|
+| Frameworks and functional architecture models                     | Y.2000–Y.2099 |
+| Quality of Service and performance                                | Y.2100–Y.2199 |
+| Service aspects: Service capabilities and service architecture    | Y.2200–Y.2249 |
+| Service aspects: Interoperability of services and networks in NGN | Y.2250–Y.2299 |
+| Enhancements to NGN                                               | Y.2300–Y.2399 |
+| Network management                                                | Y.2400–Y.2499 |
+| Network control architectures and protocols                       | Y.2500–Y.2599 |
+| Packet-based Networks                                             | Y.2600–Y.2699 |
+| Security                                                          | Y.2700–Y.2799 |
+| Generalized mobility                                              | Y.2800–Y.2899 |
+| Carrier grade open environment                                    | Y.2900–Y.2999 |
+
+## FUTURE NETWORKS
+
+|                 |               |
+|-----------------|---------------|
+| CLOUD COMPUTING | Y.3000–Y.3499 |
+| Y.3500–Y.3999   |               |
+
+## INTERNET OF THINGS AND SMART CITIES AND COMMUNITIES
+
+|                                                         |                      |
+|---------------------------------------------------------|----------------------|
+| General                                                 | Y.4000–Y.4049        |
+| Definitions and terminologies                           | Y.4050–Y.4099        |
+| Requirements and use cases                              | Y.4100–Y.4249        |
+| Infrastructure, connectivity and networks               | Y.4250–Y.4399        |
+| <b>Frameworks, architectures and protocols</b>          | <b>Y.4400–Y.4549</b> |
+| Services, applications, computation and data processing | Y.4550–Y.4699        |
+| Management, control and performance                     | Y.4700–Y.4799        |
+| Identification and security                             | Y.4800–Y.4899        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T Y.4413/F.748.5
+
+# Requirements and reference architecture of the machine-to-machine service layer
+
+## Summary
+
+Recommendation ITU-T Y.4413/F.748.5 identifies requirements of the machine-to-machine (M2M) service layer, which are common to all M2M verticals or specific to e-health application support, and provides an architectural framework of the M2M service layer.
+
+## History
+
+| Edition | Recommendation       | Approval   | Study Group | Unique ID*                                                                |
+|---------|----------------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T Y.4413/F.748.5 | 2015-11-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/12623">11.1002/1000/12623</a> |
+
+## Keywords
+
+Internet of things, IoT, M2M, machine-to-machine, service layer.
+
+---
+
+\* To access the Recommendation, type the URL <http://handle.itu.int/> in the address field of your web browser, followed by the Recommendation's unique ID. For example, <http://handle.itu.int/11.1002/1000/11830-en>.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication 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 Standardization 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 technology which fall within ITU-T's 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 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 obligatory 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 of 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 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 consult the TSB patent database at <http://www.itu.int/ITU-T/ipr/>.
+
+© ITU 2016
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+|   |                                                                                                                                  | Page |
+|---|----------------------------------------------------------------------------------------------------------------------------------|------|
+| 1 | Scope.....                                                                                                                       | 1    |
+| 2 | References.....                                                                                                                  | 1    |
+| 3 | Definitions .....                                                                                                                | 1    |
+|   | 3.1 Terms defined elsewhere.....                                                                                                 | 1    |
+|   | 3.2 Terms defined in this Recommendation.....                                                                                    | 2    |
+| 4 | Abbreviations and acronyms .....                                                                                                 | 2    |
+| 5 | Conventions .....                                                                                                                | 2    |
+| 6 | Definition of the ITU-T M2M service layer.....                                                                                   | 3    |
+|   | 6.1 The ITU-T M2M service layer and its relationship with the IoT reference<br>model .....                                       | 3    |
+|   | 6.2 The ETSI M2M service capabilities layer and its relationship with the<br>ITU-T M2M service layer .....                       | 4    |
+|   | 6.3 The oneM2M common service entity and its relationship with the ITU-T<br>M2M service layer.....                               | 4    |
+| 7 | Requirements of the ITU-T M2M service layer .....                                                                                | 5    |
+|   | 7.1 Common requirements .....                                                                                                    | 5    |
+|   | 7.2 e-health specific requirements .....                                                                                         | 7    |
+| 8 | Architectural framework of the ITU-T M2M service layer.....                                                                      | 8    |
+|   | 8.1 Overview of the architectural framework of the ITU-T M2M service<br>layer .....                                              | 8    |
+|   | 8.2 The capabilities of the ITU-T M2M service layer.....                                                                         | 8    |
+| 9 | Reference points of the ITU-T M2M service layer .....                                                                            | 9    |
+|   | 9.1 Overview of the reference points .....                                                                                       | 9    |
+|   | 9.2 Details on the reference points .....                                                                                        | 10   |
+|   | Appendix I – Comparison between the capabilities of the ITU-T M2M service layer and<br>common services functions of oneM2M ..... | 12   |
+|   | Appendix II – Comparison of reference points between the ITU-T M2M service layer and<br>common services entity of oneM2M .....   | 14   |
+|   | Bibliography.....                                                                                                                | 15   |
+
+
+
+# Recommendation ITU-T Y.4413/F.748.5
+
+# Requirements and reference architecture of the machine-to-machine service layer
+
+# 1 Scope
+
+This Recommendation identifies requirements of the machine-to-machine (M2M) service layer, which are common to all M2M verticals or specific to e-health application support, and to provide an architectural framework of the M2M service layer.
+
+In particular, the scope of this Recommendation includes:
+
+- definition of the M2M service layer;
+- requirements of the M2M service layer;
+- architectural framework of the M2M service layer;
+- reference points of the M2M service layer.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through 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 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 Y.4000] Recommendation ITU-T Y.4000/Y.2060 (2012), *Overview of the Internet of things*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 application dedicated node** [b-oneM2M-TS-0011]: A node that contains at least one application entity and does not contain a common services entity. There may be zero or more application dedicated nodes (ADNs) in the field domain of the oneM2M system.
+
+**3.1.2 application entity** [b-oneM2M-TS-0011]: Represents an instantiation of application logic for end-to-end M2M solutions.
+
+**3.1.3 application service node** [b-oneM2M-TS-0011]: A node that contains one common services entity and contains at least one application entity. There may be zero or more ASNs in the field domain of the oneM2M system.
+
+**3.1.4 common service entity** [b-oneM2M-TS-0011]: Represents an instantiation of a set of common service functions of the M2M environments. Such service functions are exposed to other entities through reference points.
+
+**3.1.5 infrastructure node** [b-oneM2M-TS-0011]: A node that contains one common services entity and contains zero or more application entities. There is exactly one infrastructure node in the infrastructure domain per oneM2M service provider.
+
+**3.1.6 IoT** [ITU-T Y.4000]: A global infrastructure for the information society, enabling advanced services by interconnecting (physical and virtual) things based on, existing and evolving, interoperable information and communication technologies.
+
+NOTE 1 – Through the exploitation of identification, data capture, processing and communication capabilities, the IoT makes full use of things to offer services to all kinds of applications, whilst ensuring that security and privacy requirements are fulfilled.
+
+NOTE 2 – In a broad perspective, the IoT can be perceived as a vision with technological and societal implications.
+
+**3.1.7 middle node** [b-oneM2M-TS-0011]: A node that contains one common services entity and contains zero or more application entities. There may be zero or more middle nodes in the field domain of the oneM2M system.
+
+**3.1.8 node** [b-oneM2M-TS-0011]: Functional entity containing one of the following: one or more M2M applications; one CSE and zero or more M2M applications.
+
+### **3.2 Terms defined in this Recommendation**
+
+None.
+
+# **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|     |                            |
+|-----|----------------------------|
+| ADN | Application Dedicated Node |
+| AE  | Application Entity         |
+| ASN | Application Service Node   |
+| BAN | Body Area Network          |
+| CSE | Common Service Entity      |
+| CSF | Common Services Function   |
+| DA  | Device Application         |
+| GA  | Gateway Application        |
+| IN  | Infrastructure Node        |
+| IoT | Internet of Things         |
+| M2M | Machine-to-Machine         |
+| MN  | Middle Node                |
+| NA  | Network Application        |
+| NSE | Network Service Entity     |
+| SCL | Service Capabilities Layer |
+| SL  | Service Layer              |
+
+# **5 Conventions**
+
+None.
+
+# 6 Definition of the ITU-T M2M service layer
+
+## 6.1 The ITU-T M2M service layer and its relationship with the IoT reference model
+
+From the ITU-T perspective, the machine-to-machine (M2M) technologies are a key enabler of the Internet of things (IoT), [ITU-T Y.4000].
+
+The M2M service layer in the ITU-T scope, the "ITU-T M2M service layer", includes a set of generic and specific functions for the support of a variety of applications enabled by the M2M technologies. These include management functions and security functions, as well as service support and application support functions. The capabilities of the ITU-T M2M service layer are a subset of the entire set of capabilities of the IoT.
+
+Figure 1 shows the ITU-T M2M service layer and its position in the IoT reference model [ITU-T Y.4000].
+
+![Figure 1: The ITU-T M2M service layer in the IoT reference model. The diagram shows a layered architecture. At the top is the 'Application layer' containing 'IoT applications' (DA, GA, NA). Below this is the 'Service support and application support layer', which is highlighted by a red dashed box labeled 'ITU-T M2M service layer'. This layer contains 'Generic support capabilities' and 'Specific support capabilities' (e-health support, Telematics support, ...). Below this is the 'Network layer' containing 'Networking capabilities' and 'Transport capabilities'. At the bottom is the 'Device layer' containing 'Device capabilities' and 'Gateway capabilities'. On the left, 'Management capabilities' are shown, including 'Specific management capabilities' and 'General management capabilities'. On the right, 'Security capabilities' are shown, including 'Specific security capabilities' and 'General security capabilities'. The red dashed box encloses the 'Service support and application support layer' and the 'Management' and 'Security' capability blocks.](367926125450c2bc3f4bdca9d59a62ba_img.jpg)
+
+Y.4413-F.748.5(15)\_F01
+
+Figure 1: The ITU-T M2M service layer in the IoT reference model. The diagram shows a layered architecture. At the top is the 'Application layer' containing 'IoT applications' (DA, GA, NA). Below this is the 'Service support and application support layer', which is highlighted by a red dashed box labeled 'ITU-T M2M service layer'. This layer contains 'Generic support capabilities' and 'Specific support capabilities' (e-health support, Telematics support, ...). Below this is the 'Network layer' containing 'Networking capabilities' and 'Transport capabilities'. At the bottom is the 'Device layer' containing 'Device capabilities' and 'Gateway capabilities'. On the left, 'Management capabilities' are shown, including 'Specific management capabilities' and 'General management capabilities'. On the right, 'Security capabilities' are shown, including 'Specific security capabilities' and 'General security capabilities'. The red dashed box encloses the 'Service support and application support layer' and the 'Management' and 'Security' capability blocks.
+
+**Figure 1 – The ITU-T M2M service layer in the IoT reference model**
+
+The layered architectural approach, as illustrated in Figure 1, reduces the implementation complexity while providing interoperability between the various applications enabled by the M2M technologies.
+
+NOTE – Other architectural approaches are out of scope of this Recommendation. It is recognized that cross layer architectural approaches can show higher performances, but at the expense of higher implementation complexity.
+
+The specific support capabilities in the service support and application support layer include application specific support capabilities (e.g., e-health support, telematics support) as shown in Figure 1).
+
+Three types of applications are identified on top of the ITU-T M2M service layer (application layer): device application (DA), gateway application (GA) and network application (NA) servers. DA, GA and NA reside, respectively, in a device, gateway and network application server. All these applications can use capabilities provided by the ITU-T M2M service layer.
+
+## 6.2 The ETSI M2M service capabilities layer and its relationship with the ITU-T M2M service layer
+
+The ETSI M2M service capabilities layer (SCL) [b-ETSI 102 690] provides functions that are shared by different applications enabled by the M2M technologies, and can be positioned with respect to the IoT reference model described in [ITU-T Y.4000] as shown in Figure 2.
+
+![Figure 2: ETSI M2M SCL in the IoT reference model. The diagram shows the IoT reference model layers: Application layer (IoT applications: DA, GA, NA), Service support and application support layer (Generic support capabilities, Specific support capabilities), Network layer (Networking capabilities, Transport capabilities), and Device layer (Device capabilities, Gateway capabilities). The ETSI M2M SCLs are indicated by a red dashed box encompassing the Service support and application support layer, General management capabilities, and General security capabilities. Arrows labeled 'dla', 'dla', and 'mld' show interactions between the Application layer and the Service support and application support layer. A red arrow labeled 'mld' shows an interaction within the Service support and application support layer.](cfda9df1319e04207eb28bcefd1dab7b_img.jpg)
+
+Y.4413-F.748.5(15)\_F02
+
+Figure 2: ETSI M2M SCL in the IoT reference model. The diagram shows the IoT reference model layers: Application layer (IoT applications: DA, GA, NA), Service support and application support layer (Generic support capabilities, Specific support capabilities), Network layer (Networking capabilities, Transport capabilities), and Device layer (Device capabilities, Gateway capabilities). The ETSI M2M SCLs are indicated by a red dashed box encompassing the Service support and application support layer, General management capabilities, and General security capabilities. Arrows labeled 'dla', 'dla', and 'mld' show interactions between the Application layer and the Service support and application support layer. A red arrow labeled 'mld' shows an interaction within the Service support and application support layer.
+
+**Figure 2 – ETSI M2M SCL in the IoT reference model**
+
+In Figure 2, dla and mla from [b-ETSI 102 690] can be considered as reference points between IoT applications and the service support and application support layer with inclusion of the general management capabilities and general security capabilities. mld from [b-ETSI 102 690] can be considered as the reference point between the service support and application support layer of different devices.
+
+As shown in Figure 2, the ETSI M2M SCL includes only general functions of service support and application support layer, general management capabilities and general security capabilities.
+
+Compared to the ETSI M2M SCL, the ITU-T M2M service layer includes specific support capabilities in the service support and application support layer, specific management capabilities and specific security capabilities as shown in Figure 1.
+
+It is anticipated that dla, mla and mld from [b-ETSI 102 690] may need extension to include the support of the specific support capabilities in the service support and application support layer, the specific management capabilities and the specific security capabilities.
+
+## 6.3 The oneM2M common service entity and its relationship with the ITU-T M2M service layer
+
+The oneM2M common service entity (CSE) [b-oneM2M-TS-0001] means a group of the twelve common service functions (CSFs) that are shared by different applications enabled by the M2M application service provider and/or user, and can be positioned with respect to the IoT reference model described in [ITU-T Y.4000], as shown in Figure 3.
+
+![Figure 3: oneM2M functional architecture in the IoT reference model. The diagram shows a layered architecture. At the top is the 'Application layer' containing 'IoT applications' (DA, GA, NA) and 'oneM2M AE'. Below this is the 'oneM2M CSE' (Service support and application support layer), which is divided into 'Generic support capabilities' and 'Specific support capabilities'. Below the CSE is the 'oneM2M NSE' (Network layer), containing 'Networking capabilities' and 'Transport capabilities'. At the bottom is the 'Device layer' with 'Device capabilities' and 'Gateway capabilities'. On the left, 'Management capabilities' are split into 'Specific management capabilities' and 'General management capabilities'. On the right, 'Security capabilities' are split into 'General security capabilities' and 'Specific security capabilities'. A 'Charging server' is connected to the 'Specific management capabilities' via 'Mch'. 'Mca' points connect the 'IoT applications' to the 'Generic support capabilities'. 'Mcn' connects the 'Generic support capabilities' to the 'Networking capabilities'. 'Mcc' and 'Mcc'' connect the 'Specific support capabilities' to the 'Specific security capabilities'. A box on the right shows 'oneM2M CSE in other operator's network' connected via 'Mcc' and 'Mcc''.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg)
+
+Y.4413-F.748.5(15)\_F03
+
+Figure 3: oneM2M functional architecture in the IoT reference model. The diagram shows a layered architecture. At the top is the 'Application layer' containing 'IoT applications' (DA, GA, NA) and 'oneM2M AE'. Below this is the 'oneM2M CSE' (Service support and application support layer), which is divided into 'Generic support capabilities' and 'Specific support capabilities'. Below the CSE is the 'oneM2M NSE' (Network layer), containing 'Networking capabilities' and 'Transport capabilities'. At the bottom is the 'Device layer' with 'Device capabilities' and 'Gateway capabilities'. On the left, 'Management capabilities' are split into 'Specific management capabilities' and 'General management capabilities'. On the right, 'Security capabilities' are split into 'General security capabilities' and 'Specific security capabilities'. A 'Charging server' is connected to the 'Specific management capabilities' via 'Mch'. 'Mca' points connect the 'IoT applications' to the 'Generic support capabilities'. 'Mcn' connects the 'Generic support capabilities' to the 'Networking capabilities'. 'Mcc' and 'Mcc'' connect the 'Specific support capabilities' to the 'Specific security capabilities'. A box on the right shows 'oneM2M CSE in other operator's network' connected via 'Mcc' and 'Mcc''.
+
+**Figure 3 – oneM2M functional architecture in the IoT reference model**
+
+In Figure 3, Mca can be considered as reference points between IoT applications and the service support and application support layer with inclusion of the general management capabilities and general security capabilities. Mch can be considered as reference points between charging server and the service support and application support layer and with inclusion of the general management capabilities and general security capabilities. Mcc and Mcc' can be considered as the reference point between the service support and application support layer of different nodes. Here, Mcc' can be considered to connect to the CSE of other service providers.
+
+As shown in Figure 3, the oneM2M CSE, like the ETSI M2M SCL, includes only general functions of service support and application support layer, general management capabilities and general security capabilities.
+
+Compared to the oneM2M CSE, the ITU-T M2M service layer includes specific support capabilities in the service support and application support layer, specific management capabilities and specific security capabilities as shown in Figure 1.
+
+# 7 Requirements of the ITU-T M2M service layer
+
+## 7.1 Common requirements
+
+#### 7.1.1 Communication management
+
+- Message scheduling:  
+The ITU-T M2M service layer is required to support various priorities of messages.
+- Various types of communications:  
+The ITU-T M2M service layer is required to support various types of communication (e.g., on-demand, continuous) requested by applications. It should also support notification of communication failure.
+- Various underlying network technologies support:  
+The ITU-T M2M service layer is required to support underlying network technologies.
+
+#### **7.1.2 Application management**
+
+- Multiple applications support:  
+The ITU-T M2M service layer is required to support multiple applications concurrently.
+
+#### **7.1.3 Service and device discovery and registration**
+
+- Service and device discovery and registration:  
+The ITU-T M2M service layer is required to support service and device discovery and registration.
+
+#### **7.1.4 Service accounting and charging**
+
+- Service accounting and charging:  
+The ITU-T M2M service layer is required to support service accounting and charging.
+
+#### **7.1.5 Device management**
+
+- Auto configuration:  
+The ITU-T M2M service layer is required to support auto configuration and configuration management of devices and upgrading of software on the devices in a secure way.
+- Management of multiple devices and various types of devices:  
+The ITU-T M2M service layer is required to support management of multiple devices and various types of devices.
+
+#### **7.1.6 Data processing**
+
+- Data storage and notification:  
+The ITU-T M2M service layer is recommended to provide capability of data storage for applications. Once data are updated, the ITU-T M2M service layer should inform subscribed applications.
+- Data formatting and translation:  
+The ITU-T M2M service layer is recommended to provide capability of data formatting and translation to facilitate semantic interoperation between applications.
+- Data collection and reporting:  
+The ITU-T M2M service layer is required to support both on-demand and periodic reporting as requested by applications.
+
+#### **7.1.7 Diagnostics and fault recovery**
+
+- Diagnostics and fault recovery:  
+The ITU-T M2M service layer is required to support diagnostic mechanisms for applications and devices. In addition, it should support fault recovery and fault management to recognize, isolate, correct and log faults that occur.
+
+#### **7.1.8 Identification, naming and addressing**
+
+- Reachability of devices by identification:  
+The ITU-T M2M service layer is required to support reachability of devices based on device identification.
+
+#### **7.1.9 Security**
+
+- Authentication:  
+The ITU-T M2M service layer is required to provide authentication mechanisms for applications and devices and prevent unauthorized use of the devices.
+
+- Privacy:  
+The ITU-T M2M service layer is required to support privacy protection capabilities, such as anonymity of identity and location, according to regulation and laws.
+- Confidentiality:  
+The ITU-T M2M service layer is required to support data transfer confidentiality.
+- Integrity:  
+The ITU-T M2M service layer is required to support data integrity protection.
+- Support of security for service scenarios involving multiple actors:  
+The ITU-T M2M service layer is required to support security capabilities, such as supporting user access control of protected data, for M2M service scenarios involving multiple actors inside a single administrative domain and across different administrative domains (e.g., countries, operators).
+- Availability:  
+The ITU-T M2M service layer is required to support data availability. Typically, data, and their related-functions or services must be available whenever they are needed.
+
+#### **7.1.10 Location provisioning**
+
+- Location information:  
+The ITU-T M2M service layer is recommended to support collection, tracking and reporting of location information according to different collection, tracking and reporting strategies.
+
+#### **7.1.11 Group management**
+
+- Group management:  
+The ITU-T M2M service layer is required to support a mechanism to create and manage virtual group of devices.
+
+## **7.2 e-health specific requirements**
+
+- Security for personal health information:  
+The ITU-T M2M service layer is required to provide security capabilities in compliance with regulation and laws regarding personal health information (personal data and medical data).
+- Privacy protection:  
+The ITU-T M2M service layer is required to provide privacy protection capabilities for personal health information in compliance with regulation and laws (personal data and medical data when they are associated with a person's identification).
+- e-health device profile support:  
+The ITU-T M2M service layer is required to support e-health device profile according to international standards (e.g., medical body area network (BAN) [b-IEEE 802.15.6], Bluetooth [b-Bluetooth]).
+- Time synchronization and timestamping:  
+The ITU-T M2M service layer is required to support timestamping since health conditions vary over time. With timestamping, e-health applications can obtain useful information according to the health condition history. For support of timestamping, the ITU-T M2M service layer is also required to retrieve time parameters from authoritative time servers and publish time parameters according to the requests from e-health applications.
+- Audit trail support:  
+The ITU-T M2M service layer is required to support audit trails ensuring that any access or attempt to access personal health information is fully transparent, traceable and reproducible.
+
+# 8 Architectural framework of the ITU-T M2M service layer
+
+## 8.1 Overview of the architectural framework of the ITU-T M2M service layer
+
+As described in clause 6, the ITU-T M2M service layer is positioned between the application layer and the network layer, and provides various types of capabilities, including generic support capabilities, specific support capabilities, general and specific management capabilities, general and specific security capabilities.
+
+Figure 4 shows the architectural framework of the ITU-T M2M service layer.
+
+![Figure 4: The ITU-T M2M service layer architectural framework. The diagram shows a layered architecture. At the top is the 'Application layer' containing 'M2M applications' (DA, GA, NA) and 'Management capabilities' and 'Security capabilities'. Below this is the 'ITU-T M2M service layer' (indicated by a red dashed border), which contains a 3x4 grid of capabilities: Communication management capability, Application management capability, Service and device discovery and registration capability, Service accounting and charging capability, Device management capability, Data processing capability, Diagnostics and fault recovery capability, Identification, naming and addressing capability, Security capability, Location provisioning capability, Group management capability, and Specific support capabilities. Below the service layer is the 'Network layer' containing 'Networking capabilities' and 'Transport capabilities', and the 'Device layer' containing 'Device capabilities' and 'Gateway capabilities'. On the left and right sides, there are vertical bars representing 'Specific management capabilities' and 'General management capabilities' on the left, and 'Specific security capabilities' and 'General security capabilities' on the right. The reference 'Y.4413-F.748.5(15)_F04' is at the bottom right.](bd671b21db63e6fdb2196e9b18502aac_img.jpg)
+
+Y.4413-F.748.5(15)\_F04
+
+Figure 4: The ITU-T M2M service layer architectural framework. The diagram shows a layered architecture. At the top is the 'Application layer' containing 'M2M applications' (DA, GA, NA) and 'Management capabilities' and 'Security capabilities'. Below this is the 'ITU-T M2M service layer' (indicated by a red dashed border), which contains a 3x4 grid of capabilities: Communication management capability, Application management capability, Service and device discovery and registration capability, Service accounting and charging capability, Device management capability, Data processing capability, Diagnostics and fault recovery capability, Identification, naming and addressing capability, Security capability, Location provisioning capability, Group management capability, and Specific support capabilities. Below the service layer is the 'Network layer' containing 'Networking capabilities' and 'Transport capabilities', and the 'Device layer' containing 'Device capabilities' and 'Gateway capabilities'. On the left and right sides, there are vertical bars representing 'Specific management capabilities' and 'General management capabilities' on the left, and 'Specific security capabilities' and 'General security capabilities' on the right. The reference 'Y.4413-F.748.5(15)\_F04' is at the bottom right.
+
+**Figure 4 – The ITU-T M2M service layer architectural framework**
+
+## 8.2 The capabilities of the ITU-T M2M service layer
+
+NOTE – The capabilities in clause 8.2 (i.e., 8.2.1 through 8.2.11) correspond to the requirements in clause 7.1 (i.e., 7.1.1 through 7.1.11), respectively.
+
+#### 8.2.1 Communication management
+
+This capability supports message scheduling, various types of communications and various underlying network technologies.
+
+#### 8.2.2 Application management
+
+This capability supports multiple applications.
+
+#### 8.2.3 Service and device discovery and registration
+
+This capability supports service and device discovery and registration.
+
+#### **8.2.4 Service accounting and charging**
+
+This capability supports accounting and different charging models, including both online and offline charging.
+
+#### **8.2.5 Device management**
+
+This capability supports auto configuration, management of multiple devices and various types of devices.
+
+#### **8.2.6 Data processing**
+
+This capability supports data storage, notification, formatting, translation, collection and reporting.
+
+#### **8.2.7 Diagnostics and fault recovery**
+
+This capability supports recognition, isolation, correction and logging of the faults that occur in the application layer and the ITU-T M2M service layer.
+
+#### **8.2.8 Identification, naming and addressing**
+
+This capability supports reachability of devices based on device identification, naming and addressing.
+
+#### **8.2.9 Security**
+
+This capability supports authentication, privacy protection, confidentiality, integrity and support of security for service scenarios involving multiple actors.
+
+#### **8.2.10 Location provisioning**
+
+This capability supports the acquisition and management of location information based on the requests from applications.
+
+#### **8.2.11 Group management**
+
+This capability supports mechanisms to create and manage virtual group of devices.
+
+#### **8.2.12 Specific support**
+
+These capabilities are support capabilities that apply to specific applications. These capabilities are out of scope of this Recommendation.
+
+# **9 Reference points of the ITU-T M2M service layer**
+
+## **9.1 Overview of the reference points**
+
+Figure 5 shows the reference points of the ITU-T M2M service layer.
+
+![Figure 5: Reference points of the ITU-T M2M service layer. This diagram shows the layered architecture of the ITU-T M2M service layer. It is divided into four main layers: Application layer, Service support and application support layer, Network layer, and Device layer. The Application layer contains M2M applications (DA, GA, NA). The Service support and application support layer contains Generic support capabilities and Specific support capabilities (e-health support, Telematics support, ...). The Network layer contains Networking capabilities and Transport capabilities. The Device layer contains Device capabilities and Gateway capabilities. The diagram also shows Management capabilities (Specific management capabilities, General management capabilities) and Security capabilities (Specific security capabilities, General security capabilities) on the sides. Reference points D-SL, G-SL, A-SL, and SL-SL are indicated between the layers. A red dashed line highlights the ITU-T M2M service layer boundary.](fa859e4e468bfb2710a94527f2c504af_img.jpg)
+
+Y.4413-F.748.5(15)\_F05
+
+Figure 5: Reference points of the ITU-T M2M service layer. This diagram shows the layered architecture of the ITU-T M2M service layer. It is divided into four main layers: Application layer, Service support and application support layer, Network layer, and Device layer. The Application layer contains M2M applications (DA, GA, NA). The Service support and application support layer contains Generic support capabilities and Specific support capabilities (e-health support, Telematics support, ...). The Network layer contains Networking capabilities and Transport capabilities. The Device layer contains Device capabilities and Gateway capabilities. The diagram also shows Management capabilities (Specific management capabilities, General management capabilities) and Security capabilities (Specific security capabilities, General security capabilities) on the sides. Reference points D-SL, G-SL, A-SL, and SL-SL are indicated between the layers. A red dashed line highlights the ITU-T M2M service layer boundary.
+
+**Figure 5 – Reference points of the ITU-T M2M service layer**
+
+As described in clause 6.1, three types of applications are identified on top of the ITU-T M2M service layer (application layer): DA, GA and NA servers. DA, GA and NA reside, respectively, in a device, gateway and network application server. All these applications can use capabilities provided by the ITU-T M2M service layer.
+
+Four different reference points are identified for the ITU-T M2M service layer: D-SL, G-SL, A-SL and SL-SL. D-SL is the reference point between the DA and the ITU-T M2M service layer, G-SL is the reference point between the GA and the ITU-T M2M service layer, A-SL is the reference point between the NA and the ITU-T M2M service layer, and SL-SL is the reference point between the ITU-T M2M service layers residing, respectively, in device, gateway and network application servers.
+
+## 9.2 Details on the reference points
+
+Figure 6 provides a detailed illustration of the reference points described in Figure 5.
+
+![Figure 6: Reference points between device, gateway and network application server. This diagram illustrates the reference points between the DA, GA, and NA servers and the SL (Service Layer) components. It shows three main components: Legacy device (containing DA), Device (containing DA and SL), Gateway (containing GA and SL), and Network application server (containing NA and SL). Reference points D-SL, G-SL, A-SL, and SL-SL are indicated between the components. D-SL is between DA and SL in the Device. G-SL is between GA and SL in the Gateway. A-SL is between NA and SL in the Network application server. SL-SL is between the SL components in the Device, Gateway, and Network application server.](41a438d7e4adc17c3a4005e7c9500091_img.jpg)
+
+Y.4413-F.748.5(15)\_F06
+
+Figure 6: Reference points between device, gateway and network application server. This diagram illustrates the reference points between the DA, GA, and NA servers and the SL (Service Layer) components. It shows three main components: Legacy device (containing DA), Device (containing DA and SL), Gateway (containing GA and SL), and Network application server (containing NA and SL). Reference points D-SL, G-SL, A-SL, and SL-SL are indicated between the components. D-SL is between DA and SL in the Device. G-SL is between GA and SL in the Gateway. A-SL is between NA and SL in the Network application server. SL-SL is between the SL components in the Device, Gateway, and Network application server.
+
+**Figure 6 – Reference points between device, gateway and network application server**
+
+The D-SL reference point allows a device application in a device to access the ITU-T M2M service layer in the same device or in the gateway. The D-SL reference point between device application and service layer in a gateway is for legacy devices which do not have ITU-T M2M service layer capabilities.
+
+The G-SL reference point allows a gateway application in a gateway to access the ITU-T M2M service layer in the same gateway.
+
+The A-SL reference point allows a network application server to access the ITU-T M2M service layer in the same network application server.
+
+The SL-SL reference point allows the ITU-T M2M service layer in a device, gateway or network application server to access the ITU-T M2M service layer in a different device, gateway or network application server.
+
+## Appendix I
+
+### Comparison between the capabilities of the ITU-T M2M service layer and common services functions of oneM2M
+
+(This appendix does not form an integral part of this Recommendation.)
+
+This appendix provides comparison between the capabilities of the ITU-T M2M service layer and CSFs of oneM2M. oneM2M defines CSE as Figure I.1 in [b-oneM2M-TS-0001].
+
+![Figure I.1: oneM2M common services functions architecture diagram.](9b9d2abd741ed4bafe7f78f89961c663_img.jpg)
+
+The diagram illustrates the oneM2M common services functions (CSFs) architecture. It shows the following components and their interconnections:
+
+- Application entity (AE)**: A box at the top representing the application layer.
+- Common services entity (CSE)**: A large central box containing 12 functional blocks arranged in a 3x4 grid:
+  - Row 1: Application and service layer management, Communication management/delivery handling, Data management and repository, Device management.
+  - Row 2: Discovery, Group management, Location, Network service exposure/service execution and triggering.
+  - Row 3: Registration, Security, Service charging and accounting, Subscription and notification.
+- Underlying Network service entity (NSE)**: A box at the bottom representing the network layer.
+
+Interconnections are shown as follows:
+
+- A vertical line connects the **Application entity (AE)** to the **Common services entity (CSE)**, labeled **Mca reference point** on the right.
+- A vertical line connects the **Common services entity (CSE)** to the **Underlying Network service entity (NSE)**, labeled **Mcn reference point** on the right.
+- A horizontal line connects the **Common services entity (CSE)** to the right, labeled **Mcc reference point** on the right.
+
+Y.4413-F.748.5(15)\_F1.1
+
+Figure I.1: oneM2M common services functions architecture diagram.
+
+**Figure I.1 – oneM2M common services functions**
+
+Figure I.2 shows the summary of comparison between the capabilities of the ITU-T M2M service layer and the CSFs of oneM2M.
+
+For example, some functions of communication management/delivery handling and device management in CSFs of oneM2M is covered by communication management capability of the ITU-T M2M service layer.
+
+The main differences between them are that oneM2M CSF does not dealing with the application-specific support and ITU-T M2M service layer does not dealing with the subscription and notification.
+
+![Diagram comparing ITU-T M2M service layer capabilities with Common services functions of oneM2M. The diagram shows two columns of boxes. The left column, titled 'ITU-T M2M service layer capabilities', contains 11 boxes: 'Communication management capability', 'Application management capability', 'Service and device discovery and registration capability', 'Service accounting and charging capability', 'Device management capability', 'Data processing capability', 'Diagnostics and fault recovery capability', 'Identification, naming and addressing capability', 'Security capability', 'Location provisioning capability', and 'Group management capability'. The right column, titled 'Common services functions of oneM2M', contains 11 boxes: 'Application and service layer management', 'Communication management/delivery handling', 'Data management and repository', 'Device management', 'Discovery', 'Group management', 'Location', 'Network service exposure/service execution and triggering', 'Registration', 'Security', and 'Service charging and accounting'. A dashed box at the bottom of the left column is labeled 'Specific support capabilities'. Lines connect the boxes between the two columns, showing mappings between the capabilities and functions.](9c6461e1e94afae4dec455e69a2ce152_img.jpg)
+
+ITU-T M2M service layer capabilities
+
+Common services functions of oneM2M
+
+Communication management capability
+
+Application management capability
+
+Service and device discovery and registration capability
+
+Service accounting and charging capability
+
+Device management capability
+
+Data processing capability
+
+Diagnostics and fault recovery capability
+
+Identification, naming and addressing capability
+
+Security capability
+
+Location provisioning capability
+
+Group management capability
+
+Specific support capabilities
+
+Application and service layer management
+
+Communication management/delivery handling
+
+Data management and repository
+
+Device management
+
+Discovery
+
+Group management
+
+Location
+
+Network service exposure/service execution and triggering
+
+Registration
+
+Security
+
+Service charging and accounting
+
+Subscription and notification
+
+Y.4413-F.748.5(15)\_F1.2
+
+Diagram comparing ITU-T M2M service layer capabilities with Common services functions of oneM2M. The diagram shows two columns of boxes. The left column, titled 'ITU-T M2M service layer capabilities', contains 11 boxes: 'Communication management capability', 'Application management capability', 'Service and device discovery and registration capability', 'Service accounting and charging capability', 'Device management capability', 'Data processing capability', 'Diagnostics and fault recovery capability', 'Identification, naming and addressing capability', 'Security capability', 'Location provisioning capability', and 'Group management capability'. The right column, titled 'Common services functions of oneM2M', contains 11 boxes: 'Application and service layer management', 'Communication management/delivery handling', 'Data management and repository', 'Device management', 'Discovery', 'Group management', 'Location', 'Network service exposure/service execution and triggering', 'Registration', 'Security', and 'Service charging and accounting'. A dashed box at the bottom of the left column is labeled 'Specific support capabilities'. Lines connect the boxes between the two columns, showing mappings between the capabilities and functions.
+
+**Figure I.2 – Comparison between the capabilities of the ITU-T M2M service layer and the CSFs of oneM2M**
+
+## Appendix II
+
+### Comparison of reference points between the ITU-T M2M service layer and common services entity of oneM2M
+
+(This appendix does not form an integral part of this Recommendation.)
+
+Figure II.1 shows comparisons of reference points between the ITU-T M2M service layer and the CSE of oneM2M.
+
+![Figure II.1: Comparison of reference points between the ITU-T M2M service layer and the CSEs of oneM2M. The diagram illustrates the mapping of reference points (Mca and Mcc) between various entities in the ITU-T M2M service layer and the oneM2M CSE architecture.](523ab7b925beb555f88b2e1e1336974f_img.jpg)
+
+The diagram illustrates the comparison of reference points between the ITU-T M2M service layer and the CSEs of oneM2M. It shows the following components and their interactions:
+
+- Legacy device (ADN):** Contains an **ADN-AE** (Application Entity).
+- ASN (Access Service Network):** Contains an **ASN-AE** and an **ASN-CSE** (Common Services Entity).
+- Device:** A label for the legacy device.
+- MN (Mobile Network):** Contains an **MN-AE** and an **MN-CSE**.
+- Gateway:** A label for the MN-CSE.
+- Network application server (IN):** Contains an **IN-AE** and an **IN-CSE**.
+- IN (Information Network):** A label for the network application server.
+
+Reference points are indicated by arrows:
+
+- Mca (M2M Application Reference Point):** Connects ADN-AE to MN-AE, MN-AE to MN-CSE, MN-CSE to IN-CSE, and IN-CSE to IN-AE. It also connects ASN-AE to MN-CSE.
+- Mcc (M2M Common Reference Point):** Connects MN-CSE to ASN-CSE, MN-CSE to IN-CSE, and IN-CSE to IN-AE. It also connects ASN-CSE to MN-CSE.
+
+Y.4413-F.748.5(15)\_FII.1
+
+Figure II.1: Comparison of reference points between the ITU-T M2M service layer and the CSEs of oneM2M. The diagram illustrates the mapping of reference points (Mca and Mcc) between various entities in the ITU-T M2M service layer and the oneM2M CSE architecture.
+
+**Figure II.1 – Comparison of reference points between the ITU-T M2M service layer and the CSEs of oneM2M**
+
+Compared to the ITU-T M2M service layer, oneM2M CSE has additional reference points between ASN-AE and IN-CSE and between IN-CSE and IN-AE.
+
+## Bibliography
+
+- [b-Bluetooth] Bluetooth, *adopted specifications*.  
+<<https://www.bluetooth.org/en-us/specification/adopted-specifications>>
+- [b-ETSI 102 690] ETSI TS 102 690 v2.1.1 (2013), *Machine-to-Machine communications (M2M): Functional architecture*.
+- [b-IEEE 802.15.6] IEEE 802.15.6 (2012), *IEEE Standard for Local and metropolitan area networks - Part 15.6: Wireless Body Area Networks*.  
+<<http://standards.ieee.org/findstds/standard/802.15.6-2012.html>>,  
+accessed on 2014-06-10.
+- [b-oneM2M-TS-0001] oneM2M-TS-0001-V-2014-08 (2014), *oneM2M Functional Architecture Baseline Draft*.
+- [b-oneM2M-TS-0011] oneM2M-TS-0011-V-2014-08 (2014), *oneM2M Definitions and Acronyms*.
+
+
+
+## ITU-T F-SERIES RECOMMENDATIONS NON-TELEPHONE TELECOMMUNICATION SERVICES
+
+|                                                                 |                    |
+|-----------------------------------------------------------------|--------------------|
+| TELEGRAPH SERVICE                                               |                    |
+| Operating methods for the international public telegram service | F.1–F.19           |
+| The gentex network                                              | F.20–F.29          |
+| Message switching                                               | F.30–F.39          |
+| The international telemesssage service                          | F.40–F.58          |
+| The international telex service                                 | F.59–F.89          |
+| Statistics and publications on international telegraph services | F.90–F.99          |
+| Scheduled and leased communication services                     | F.100–F.104        |
+| Phototelegraph service                                          | F.105–F.109        |
+| MOBILE SERVICE                                                  |                    |
+| Mobile services and multideestination satellite services        | F.110–F.159        |
+| TELEMATIC SERVICES                                              |                    |
+| Public facsimile service                                        | F.160–F.199        |
+| Teletex service                                                 | F.200–F.299        |
+| Videotex service                                                | F.300–F.349        |
+| General provisions for telematic services                       | F.350–F.399        |
+| MESSAGE HANDLING SERVICES                                       | F.400–F.499        |
+| DIRECTORY SERVICES                                              | F.500–F.549        |
+| DOCUMENT COMMUNICATION                                          |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| DATA TRANSMISSION SERVICES                                      | F.600–F.699        |
+| <b>AUDIOVISUAL SERVICES</b>                                     | <b>F.700–F.799</b> |
+| ISDN SERVICES                                                   | F.800–F.849        |
+| UNIVERSAL PERSONAL TELECOMMUNICATION                            | F.850–F.899        |
+| HUMAN FACTORS                                                   | F.900–F.999        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+|                 |                                                                                                                                                           |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A        | Organization of the work of ITU-T                                                                                                                         |
+| Series D        | General tariff principles                                                                                                                                 |
+| Series E        | Overall network operation, telephone service, service operation and human factors                                                                         |
+| <b>Series F</b> | <b>Non-telephone telecommunication services</b>                                                                                                           |
+| Series G        | Transmission systems and media, digital systems and networks                                                                                              |
+| Series H        | Audiovisual and multimedia systems                                                                                                                        |
+| Series I        | Integrated services digital network                                                                                                                       |
+| Series J        | Cable networks and transmission of television, sound programme and other multimedia signals                                                               |
+| Series K        | Protection against interference                                                                                                                           |
+| Series L        | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M        | Telecommunication management, including TMN and network maintenance                                                                                       |
+| Series N        | Maintenance: international sound programme and television transmission circuits                                                                           |
+| Series O        | Specifications of measuring equipment                                                                                                                     |
+| Series P        | Terminals and subjective and objective assessment methods                                                                                                 |
+| Series Q        | Switching and signalling                                                                                                                                  |
+| Series R        | Telegraph transmission                                                                                                                                    |
+| Series S        | Telegraph services terminal equipment                                                                                                                     |
+| Series T        | Terminals for telematic services                                                                                                                          |
+| Series U        | Telegraph switching                                                                                                                                       |
+| Series V        | Data communication over the telephone network                                                                                                             |
+| Series X        | Data networks, open system communications and security                                                                                                    |
+| <b>Series Y</b> | <b>Global information infrastructure, Internet protocol aspects and next-generation networks</b>                                                          |
+| Series Z        | Languages and general software aspects for telecommunication systems                                                                                      |

marked/Y/T-REC-H.642.2-201206-I_PDF-E/raw.md

@@ -0,0 +1,370 @@
+
+
+I n t e r n a t i o n a l   T e l e c o m m u n i c a t i o n   U n i o n
+
+# ITU-T
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+# H.642.2
+
+(06/2012)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Broadband, triple-play and advanced multimedia  
+services – Ubiquitous sensor network applications and  
+Internet of Things
+
+---
+
+**Multimedia information access triggered by  
+tag-based identification – Registration  
+procedures for identifiers**
+
+Recommendation ITU-T H.642.2
+
+![ITU logo: A blue globe with red lightning bolts and the text 'ITU International Telecommunication Union'.](84a1d09fb489061482111515543b60dc_img.jpg)
+
+The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with two red lightning bolts striking it. To the right of the globe, the text 'ITU' is written in a large, bold, blue font, and below it, the words 'International Telecommunication Union' are written in a smaller, blue font.
+
+ITU logo: A blue globe with red lightning bolts and the text 'ITU International Telecommunication Union'.
+
+# ITU-T H-SERIES RECOMMENDATIONS AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+|                                                                               |                    |
+|-------------------------------------------------------------------------------|--------------------|
+| CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS                                   | H.100–H.199        |
+| INFRASTRUCTURE OF AUDIOVISUAL SERVICES                                        |                    |
+| General                                                                       | H.200–H.219        |
+| Transmission multiplexing and synchronization                                 | H.220–H.229        |
+| Systems aspects                                                               | H.230–H.239        |
+| Communication procedures                                                      | H.240–H.259        |
+| Coding of moving video                                                        | H.260–H.279        |
+| Related systems aspects                                                       | H.280–H.299        |
+| Systems and terminal equipment for audiovisual services                       | H.300–H.349        |
+| Directory services architecture for audiovisual and multimedia services       | H.350–H.359        |
+| Quality of service architecture for audiovisual and multimedia services       | H.360–H.369        |
+| Supplementary services for multimedia                                         | H.450–H.499        |
+| MOBILITY AND COLLABORATION PROCEDURES                                         |                    |
+| Overview of Mobility and Collaboration, definitions, protocols and procedures | H.500–H.509        |
+| Mobility for H-Series multimedia systems and services                         | H.510–H.519        |
+| Mobile multimedia collaboration applications and services                     | H.520–H.529        |
+| Security for mobile multimedia systems and services                           | H.530–H.539        |
+| Security for mobile multimedia collaboration applications and services        | H.540–H.549        |
+| Mobility interworking procedures                                              | H.550–H.559        |
+| Mobile multimedia collaboration inter-working procedures                      | H.560–H.569        |
+| BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES                       |                    |
+| Broadband multimedia services over VDSL                                       | H.610–H.619        |
+| Advanced multimedia services and applications                                 | H.620–H.629        |
+| <b>Ubiquitous sensor network applications and Internet of Things</b>          | <b>H.640–H.649</b> |
+| IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV                            |                    |
+| General aspects                                                               | H.700–H.719        |
+| IPTV terminal devices                                                         | H.720–H.729        |
+| IPTV middleware                                                               | H.730–H.739        |
+| IPTV application event handling                                               | H.740–H.749        |
+| IPTV metadata                                                                 | H.750–H.759        |
+| IPTV multimedia application frameworks                                        | H.760–H.769        |
+| IPTV service discovery up to consumption                                      | H.770–H.779        |
+| Digital Signage                                                               | H.780–H.789        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# **Recommendation ITU-T H.642.2**
+
+### **Multimedia information access triggered by tag-based identification – Registration procedures for identifiers**
+
+## **Summary**
+
+Recommendation 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-29 | 16          |
+
+## **Keywords**
+
+Identification scheme, identifier, registration authority.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication 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 Standardization 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 technology which fall within ITU-T's 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 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 obligatory 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 of 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 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 consult 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.
+
+## Table of Contents
+
+|   |                                                                       | Page |
+|---|-----------------------------------------------------------------------|------|
+| 1 | Scope .....                                                           | 1    |
+| 2 | References.....                                                       | 1    |
+| 3 | Definitions .....                                                     | 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 Responsibilities.....                                             | 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    |
+
+
+
+# Recommendation ITU-T H.642.2
+
+### Multimedia information access triggered by tag-based identification – 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 0001<sub>2</sub>. The identification scheme consists of a first level code (1LC), a second level code (2LC), class 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.
+
+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 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 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]   | Recommendation ITU-T F.771 (2008), <i>Service description and requirements for multimedia information access triggered by tag-based identification</i> .                                                                                            |
+| [ITU-T H.621]   | Recommendation ITU-T H.621 (2008), <i>Architecture of a system for multimedia information access triggered by tag-based identification</i> .                                                                                                        |
+| [ITU-T H.642.1] | Recommendation ITU-T H.642.1 (2012), <i>Multimedia information access triggered by tag-based identification – Identification scheme</i> .                                                                                                           |
+| [ITU-T H.642.3] | Recommendation ITU-T H.642.3   ISO/IEC 29177 (2012), <i>Information technology – Automatic identification and data capture technique – Identifier resolution protocol for multimedia information access triggered by tag-based identification</i> . |
+| [ISO 3166-1]    | ISO 3166-1:2006 <i>Codes for the representation of names of countries and their subdivisions – Part 1: Country codes</i> , plus its Cor.1 (2007).                                                                                                   |
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following 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).
+
+**3.1.2 country name** [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 individual 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.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 table 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:
+
+|     |                        |
+|-----|------------------------|
+| 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 countries 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**
+
+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.
+
+### **6.2 Announcement**
+
+When an organization is selected to run a second level RA at a pre-assigned 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 organization 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, 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 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 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 applications 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 publicly 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-recovery basis.
+
+### **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 time-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 allocation 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 following 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 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. The 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 by the second level RA when it contains incomplete or incomprehensible information, or if the conditions of criteria of acceptance are not satisfied.
+
+The second level RA shall send a notice of rejection to an applicant when the assignment of a 3LC has been rejected. The notice of rejection 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) full identification of the person submitting the application (including their role in the organization);
+- d) the reason for rejection, which *inter alia* may be:
+  - the absence of a proper fee;
+  - incomplete or incomprehensible information in application;
+  - the justification for inclusion in the register (as defined in this standard) is not adequate.
+
+#### **7.3.4 Content of the register**
+
+At a minimum, the register shall contain:
+
+- a) the assigned 3LC and the class under which the 3LC is used;
+- b) name of the initial applicant;
+- c) address of the initial applicant;
+- d) date of the original assignment;
+- e) date of the last transfer of assignment, if allowed (updatable);
+- f) name of the current owner (updatable);
+- g) address of the current owner (updatable);
+- h) if the owner is an organization, the name, title, postal/e-mail address (with the email address protected against robot harvesting), and telephone/facsimile number of a contact person within the organization (updatable);
+- i) date of last update (updatable).
+
+#### **7.3.5 Change of registration information**
+
+The registered organization identified by a 3LC shall not significantly change from the original application, but supporting information, such as the information provided in clause 7.3.1, may change from time to time. The second level RA shall be notified of all such changes, and shall update the register, maintaining an audit trail of earlier information.
+
+#### **7.3.6 Appeals process**
+
+In response to a notice of rejection of a 3LC application, the applicant can submit to a second level RA a supplement to its original application that responds to the reason(s) for rejection.
+
+### **7.4 Transfer of register entries held by the second level RA**
+
+The register entries held by the second level RA shall be made available to any subsequently appointed second level RA.
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+|                 |                                                                                             |
+|-----------------|---------------------------------------------------------------------------------------------|
+| Series A        | Organization of the work of ITU-T                                                           |
+| Series D        | General tariff principles                                                                   |
+| Series E        | Overall network operation, telephone service, service operation and human factors           |
+| Series F        | Non-telephone telecommunication services                                                    |
+| Series G        | Transmission systems and media, digital systems and networks                                |
+| <b>Series H</b> | <b>Audiovisual and multimedia systems</b>                                                   |
+| Series I        | Integrated services digital network                                                         |
+| Series J        | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K        | Protection against interference                                                             |
+| Series L        | Construction, installation and protection of cables and other elements of outside plant     |
+| Series M        | Telecommunication management, including TMN and network maintenance                         |
+| Series N        | Maintenance: international sound programme and television transmission circuits             |
+| Series O        | Specifications of measuring equipment                                                       |
+| Series P        | Terminals and subjective and objective assessment methods                                   |
+| Series Q        | Switching and signalling                                                                    |
+| Series R        | Telegraph transmission                                                                      |
+| Series S        | Telegraph services terminal equipment                                                       |
+| Series T        | Terminals for telematic services                                                            |
+| Series U        | Telegraph switching                                                                         |
+| Series V        | Data communication over the telephone network                                               |
+| Series X        | Data networks, open system communications and security                                      |
+| Series Y        | Global information infrastructure, Internet protocol aspects and next-generation networks   |
+| Series Z        | Languages and general software aspects for telecommunication systems                        |

marked/Y/T-REC-Y.100-199806-I_PDF-E/raw.md

@@ -0,0 +1,506 @@
+
+
+![ITU logo: a globe with the letters ITU inside, crossed by a lightning bolt.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+ITU logo: a globe with the letters ITU inside, crossed by a lightning bolt.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+# ITU-T
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+# Y.100
+
+(06/98)
+
+SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE  
+General
+
+---
+
+# **General overview of the Global Information Infrastructure standards development**
+
+ITU-T Recommendation Y.100
+
+(Previously CCITT Recommendation)
+
+---
+
+## ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE
+
+| General                                   | Y.100–Y.199 |
+|-------------------------------------------|-------------|
+| Services, applications and middleware     | Y.200–Y.299 |
+| Network aspects                           | Y.300–Y.399 |
+| Interfaces and protocols                  | Y.400–Y.499 |
+| Numbering, addressing and naming          | Y.500–Y.599 |
+| Operation, administration and maintenance | Y.600–Y.699 |
+| Security                                  | Y.700–Y.799 |
+
+*For further details, please refer to ITU-T List of Recommendations.*
+
+## **ITU-T RECOMMENDATION Y.100**
+
+# **GENERAL OVERVIEW OF THE GLOBAL INFORMATION INFRASTRUCTURE STANDARDS DEVELOPMENT**
+
+## **Summary**
+
+This Recommendation provides an overview of the nature of the Global Information Infrastructure (GII). It outlines the environment and the related factors which need to be taken into account in progressing the GII standardization work.
+
+## **Source**
+
+ITU-T Recommendation Y.100 was prepared by ITU-T Study Group 13 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 1st of June 1998.
+
+## **Keywords**
+
+Global Information Infrastructure, GII, standards, standardization, overview.
+
+## FOREWORD
+
+ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The 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 Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics.
+
+The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1.
+
+In some areas of information technology which fall within ITU-T's 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.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The 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 date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 1998
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
+
+## CONTENTS
+
+|                                                                    | <b>Page</b> |
+|--------------------------------------------------------------------|-------------|
+| 1 Introduction .....                                               | 1           |
+| 1.1 Purpose .....                                                  | 1           |
+| 1.2 Global collaboration .....                                     | 1           |
+| 1.3 The goals of the Global Information Infrastructure (GII) ..... | 1           |
+| 2 Abbreviations .....                                              | 2           |
+| 3 Driving forces .....                                             | 2           |
+| 3.1 The new environment .....                                      | 2           |
+| 3.2 Digitalization .....                                           | 3           |
+| 3.3 Value chain models and business opportunities .....            | 3           |
+| 4 General considerations .....                                     | 4           |
+| 4.1 Integration and convergence .....                              | 4           |
+| 4.2 Accommodation of existing and future technologies .....        | 4           |
+| 4.3 Accommodation of applications .....                            | 4           |
+| 5 GII trends and directions .....                                  | 5           |
+| 5.1 Networking considerations .....                                | 5           |
+| 5.2 Information technology considerations .....                    | 6           |
+| 5.3 Common generic capabilities .....                              | 7           |
+| 5.4 General considerations .....                                   | 8           |
+| 6 Standards objectives .....                                       | 9           |
+| 6.1 Business coupling .....                                        | 10          |
+| 6.2 Seamless operation .....                                       | 10          |
+| 6.3 Partnerships .....                                             | 10          |
+| 6.4 Joint work .....                                               | 10          |
+| 6.5 Cross-industry interfaces .....                                | 10          |
+| 6.6 Common GII models .....                                        | 10          |
+| 7 Role of ITU-T .....                                              | 10          |
+| 8 Framework of Recommendations .....                               | 11          |
+
+
+
+###### **Recommendation Y.100**
+
+# **GENERAL OVERVIEW OF THE GLOBAL INFORMATION INFRASTRUCTURE STANDARDS DEVELOPMENT**
+
+*(Geneva, 1998)*
+
+## **1 Introduction**
+
+This Recommendation provides an overview of the Global Information Infrastructure standards developments. It is intended to be a practical, educational and insightful guide for leaders and participants in GII-related standardization.
+
+### **1.1 Purpose**
+
+This Recommendation is intended to be used as a planning tool by everyone considering the development or adoption of standards for use in the GII. Its use is not restricted solely to the ITU organizations.
+
+### **1.2 Global collaboration**
+
+The word "global" is of critical importance. It is not desirable, or logical, to speak of more than one global infrastructure since, by definition, everything lies within a singular global infrastructure.
+
+It follows that the respective roles of the various participants in the GII have to be described in common documents that all participating parties understand. Collaboration between the various participants can best be achieved on the basis of consistent programme documents, common positioning documents, and agreed or non-conflicting basic GII terms and definitions.
+
+### **1.3 The goals of the Global Information Infrastructure (GII)**
+
+The ITU-T is seeking to ensure that the GII will be an infrastructure which facilitates the development, implementation and interoperability of existing and future information services and applications within and across the telecommunications, information technology, consumer electronics and content provision industries. This infrastructure will consist of interactive, broadcast and other multimedia delivery mechanisms coupled with capabilities for individuals to securely share, use and manage information, anytime and anywhere, with security and privacy protection, and with levels of acceptable cost and quality.
+
+The GII will provide for interoperability between a multiplicity of applications and different platforms through a seamless federation of interconnected computers and communications capabilities incorporating line-fed (e.g. copper pair, fibre, coax) and wireless (e.g. satellite and fixed/mobile terrestrial radio) connectionless or connection-oriented technologies. The areas of application must remain unrestricted and are practically unlimited. Current areas of application are expected to include electronic commerce, telemedicine, city information services, intelligent transportation systems, distance learning, electronic libraries and museums, nomadicity (continuity of access in space and time) etc.
+
+The GII must be designed to:
+
+- enable information providers and users (e.g. individuals, information users, information providers, and information service providers) to communicate securely with each other any time and anywhere at acceptable cost and with acceptable quality;
+- provide a set of communication services;
+- support a multitude of open applications;
+
+- embrace all forms of information (audio, text, data, image, video, etc.), and of information generation, use and transportation;
+- operate in a transparent, user-friendly and straightforward way;
+- provide seamless, interconnected and interoperable communication networks, information processing equipment, databases and terminals (including TV sets);
+- enable competition between the players in the information and telecommunications (including broadcasting) sectors.
+
+## **2 Abbreviations**
+
+This Recommendation uses the following abbreviations:
+
+|       |                                                                                  |
+|-------|----------------------------------------------------------------------------------|
+| ATM   | Asynchronous Transfer Mode                                                       |
+| CL    | Connectionless                                                                   |
+| CLNP  | Connectionless Network Protocol                                                  |
+| CO    | Connection Oriented                                                              |
+| CORBA | Common Object Request Broker Architecture                                        |
+| DCE   | Distributed Computing Environment                                                |
+| DVD   | Digital Video Disk, Digital Versatile Disk                                       |
+| GII   | Global Information Infrastructure                                                |
+| IP    | Internet Protocol                                                                |
+| ISDN  | Integrated Services Digital Network                                              |
+| ITU-T | International Telecommunication Union – Telecommunication Standardization Sector |
+| ODP   | Open Distributed Processing                                                      |
+| OSI   | Open Systems Interconnection                                                     |
+| PSTN  | Public Switched Telephone Network                                                |
+| QOS   | Quality of Service                                                               |
+| SDH   | Synchronous Digital Hierarchy                                                    |
+| SDO   | Standards Development Organization                                               |
+| SG    | Study Group                                                                      |
+| WP    | Working Party                                                                    |
+
+## **3 Driving forces**
+
+This clause outlines some of the key forces driving the evolution of the GII.
+
+### **3.1 The new environment**
+
+Two predominant factors distinguish a situation for the GII which is likely to be radically different from previous information infrastructures. These two factors are:
+
+- a) the convergence of technologies in use within telecommunications, computers, consumer electronics and the move of content provision industries towards digital technology; and
+
+- b) the new business opportunities, created by the unbundling of services made possible or necessary by deregulation, and other commercial and/or open market pressures.
+
+### 3.2 Digitalization
+
+Traditionally, networks have been designed with specific payloads in mind, e.g. voice, video or data. It is expected that digital networks will become general purpose carriers of streams of bits. In theory, this will enable any type of digital network to carry any and all types of information in digital format, such as voice, video or computer data. Moreover, the interconnection of different networks will be simplified. This will sweep away the restriction of video being carried on special purpose cable-TV networks, and the tradition of only carrying telephone service over traditional telecommunication networks. All forms of information, including voice, data or video/image, are simply reduced to streams of digital bits for transfer over a bit-way (or digital network). This represents a possible decoupling between networks and their payloads.
+
+Thus, any network that is capable of carrying digital data is also capable of carrying any kind of digitized information. Conversely, any information that is captured in digital form is capable of being carried over any digital network. From this, one can envisage a good deal of role reversal amongst the traditional carriers and suppliers of voice, data and video/image based services.
+
+This role reversal represents an industry-wide paradigm shift and thus requires new ways of doing business, including the business of Standards Development Organizations (SDOs). The convergence and new mix of players potentially created by this situation has enormous implications for the operation of, and relationships between, the standards development organizations representing the traditional players.
+
+### 3.3 Value chain models and business opportunities
+
+The technological unbundling, created by the new environment briefly outlined in 3.1 above, establishes many opportunities for new business(es) and standards-related developments.
+
+De-regulation in the telecommunications and broadcasting areas also plays a part in this scenario. De-regulation in many cases permits, or even forces, an unbundling of components and services.
+
+The main point to be illustrated is that any link in a value chain model represents both a business opportunity and a requirement for standards-based interface. It follows, therefore, that the ITU-T in conjunction with other Standards Development Organizations (SDOs) must become closely involved in business developments, to better understand their roles in the market place and its relationship to the other market players.
+
+Figure 1 shows a simple added-value chain model. In this model, a given product or service is progressively enhanced as it progresses from the initial supplier, through intermediate suppliers, to the end user.
+
+The following properties of an added-value chain are relevant to ITU-T standardization work:
+
+- a) Every link and item in an added-value chain, from content to user or user to user, potentially represents a possible business opportunity.
+- b) Every link in the chain establishes sufficient demarcation points to facilitate potential separate ownership and operation to be realized within the context of the entire chain.
+- c) a) and b) are sources of requirements for the definition of standards-based functions and/or interfaces.
+
+This model can be used to represent a competitive telecommunications and information provision environment, involving the interconnection of networks in parallel or in series, as well as systems which enhance or modify information content.
+
+NOTE – More substantial, formal and detailed material on the subject of value chains and Enterprise Models subject can be found in Recommendation Y.110, GII principles and framework architecture.
+
+![Figure 1/Y.100 – Added-value chain model. The diagram shows a horizontal flow from left to right. It starts with a rectangular box labeled 'Initial product or service'. An arrow points from this box to a circle labeled '1' containing the text 'Added value'. From circle 1, an arrow points to a second circle labeled '2' containing 'Added value'. From circle 2, a dashed arrow points to a third circle labeled 'n' containing 'Added value'. From circle n, an arrow points to a final rectangular box labeled 'Final product or service'. Below the circles, there are three arrows pointing upwards towards the gaps between them. The first arrow points to the gap between circle 1 and circle 2. The second arrow points to the gap between circle 2 and circle n. The third arrow points to the gap between circle n and the final box. These three arrows are collectively labeled 'Intermediate product or service'.](f4fdd410cdb84df81274da55721e56fb_img.jpg)
+
+Figure 1/Y.100 – Added-value chain model. The diagram shows a horizontal flow from left to right. It starts with a rectangular box labeled 'Initial product or service'. An arrow points from this box to a circle labeled '1' containing the text 'Added value'. From circle 1, an arrow points to a second circle labeled '2' containing 'Added value'. From circle 2, a dashed arrow points to a third circle labeled 'n' containing 'Added value'. From circle n, an arrow points to a final rectangular box labeled 'Final product or service'. Below the circles, there are three arrows pointing upwards towards the gaps between them. The first arrow points to the gap between circle 1 and circle 2. The second arrow points to the gap between circle 2 and circle n. The third arrow points to the gap between circle n and the final box. These three arrows are collectively labeled 'Intermediate product or service'.
+
+**Figure 1/Y.100 – Added-value chain model**
+
+## **4 General considerations**
+
+The following general aspects need to be considered.
+
+### **4.1 Integration and convergence**
+
+The GII must provide an evolutionary approach which allows the integration of current networks and technologies into an overall infrastructure as well as providing a direction for future network evolution.
+
+### **4.2 Accommodation of existing and future technologies**
+
+The GII standards must support existing and future telecommunications, information technologies and entertainment services and applications including interactive, broadcast and multimedia capabilities, and will incorporate wire-based and radio-based technologies such as copper pair, fibre, coax, satellite and terrestrial (fixed and mobile) radio.
+
+### **4.3 Accommodation of applications**
+
+The GII standards must provide for interoperability and interconnection (both connectionless and connection oriented), between a multiplicity of applications and different platforms (both software and hardware). The degree of interoperability and interconnection required is dependent on the individual business application areas.
+
+Typical areas include, for example:
+
+- distance learning/electronic libraries;
+- telemedicine;
+- teleworking (e.g. home office and "on-the-road" applications);
+- electronic commerce;
+- electronic Publishing;
+- gaming.
+
+Different types of application may have significantly different Quality of Service requirements. To illustrate this point the following rough guide to QOS categories is provided. The descriptions are not intended to be definitions and are only provided to show the need to consider various QOS
+
+aspects. Some applications may require a mixture or combination of these categories, or some other category entirely not yet described herein.
+
+#### **Block Transfer**
+
+As a response to a "click" on a home page at a terminal computer, a data block that contains information data and a program file, such as a JAVA applet for full-motion video, may need to be sent all at once. An Application Data Unit (ADU) is sent by several packets. Block delay is the main concern from the QOS viewpoint.
+
+#### **Stream**
+
+Audio and video communications require end-to-end bandwidths in the network (these bandwidths are related to the communications quality). This type of traffic is characterized as a continuous data-transmission stream. In multicasting, stream data traffic may be sent simultaneously from one site to many destinations. An ADU is generated constantly or at a certain time interval. End-to-end bandwidth and constancy of propagation time are the main concerns.
+
+#### **Transaction**
+
+A transaction type of communication, such as that used for electronic commerce, electronic banking, electronic ordering, etc., generates bi-directional data transmission with small-sized data packets (a few kilobits), and requires low data-transmission latency in the network. An ADU is sent in a single packet. Packet latency is the main concern.
+
+#### **Best-effort**
+
+As with the Internet, an ADU is sent without any guarantee of QOS. For example, E-mail is a non-interactive application and mail may reach the destination in a few seconds or even in a few minutes.
+
+Network control is not a user application, but it warrants mention. This information, which is accumulated in a single packet, may be categorized as a Transaction type.
+
+Thus, each type of traffic needs a different level of network performance and QOS. It follows that appropriate performance parameters need to be defined to reflect the characteristics of each category of QOS. For example, the parameter Block Throughput/Delay might be appropriate for the Block category, Latency for the Transaction category and so on.
+
+## **5 GII trends and directions**
+
+This clause identifies a number of trends and directions which need to be taken into account by both the ITU-T and other SDOs when establishing their respective programs, program priorities, and liaison or partnership arrangements.
+
+### **5.1 Networking considerations**
+
+The GII will not, initially, require or employ new network capabilities, but will define how a multiplicity of existing capabilities will interwork in the context of a "federation of networks". However, standardization activities related to the GII must permit new network capabilities and technologies to be introduced.
+
+Telecommunications networks are currently providing voice and data services worldwide with a high level of reliability and defined QOS and are based on different network technologies (PSTN, ISDN, Mobile, ATM, SDH, etc.) with interworking between them. Extension of the networks to include broadband capabilities is based on the ATM technology. ATM is also being enhanced to provide not
+
+only for connection-oriented network services but also to meet the requirements of connectionless network capabilities and services supported by these capabilities.
+
+IP-based networks provide a platform that allows users connected to different network infrastructures to have a common set of applications and to exchange data with an undefined QOS. The IP protocol suite is evolving to include voice, data and video applications with defined QOS.
+
+These convergence trends in networking technology are illustrated in Figure 2.
+
+Additionally, terrestrial radio, cable and satellite networks are providing local broadcast entertainment services and are also evolving to provide interactive voice, data and video services.
+
+![Figure 2/Y.100 – Networking directions. A diagram showing the convergence of IP-based connectionless (CL) and connection-oriented (CO) networks across three QoS levels: Unguaranteed, Guaranteed, and High QoS. IP is in the CL row, while PSTN/ISDN and ATM are in the CO row. Arrows indicate data flow directions between these components.](1439cb942d9e363bbb3161b5540dd8c6_img.jpg)
+
+The diagram illustrates networking directions across two operational modes (CL and CO) and three QoS levels (Unguaranteed, Guaranteed, and High QoS).
+
+- CL (Connectionless) Row:** Contains the IP component. It has a rightward arrow from the Unguaranteed QoS column to the Guaranteed QoS column. A downward arrow labeled "CO emulation" points from the IP component to the CO row.
+- CO (Connection-oriented) Row:** Contains a dashed box labeled "Telecommunications" which includes PSTN/ISDN and ATM.
+  - An arrow points left from the Guaranteed QoS column to the Unguaranteed QoS column.
+  - An arrow points up from the ATM component to the High QoS column.
+
+Legend:
+
+- CO Connection-oriented operation
+- CL Connectionless operation
+- ➡ Directions
+
+T1311560-97
+
+Figure 2/Y.100 – Networking directions. A diagram showing the convergence of IP-based connectionless (CL) and connection-oriented (CO) networks across three QoS levels: Unguaranteed, Guaranteed, and High QoS. IP is in the CL row, while PSTN/ISDN and ATM are in the CO row. Arrows indicate data flow directions between these components.
+
+**Figure 2/Y.100 – Networking directions**
+
+### 5.2 Information technology considerations
+
+The availability of core technology (IP communications networks, web user interfaces and information representation, compression and retrieval technologies etc.) together with extensive information user and provider uptake and interest has led to rapid successes and growth in the application of internet/intranets (i.e. IP-based) and World Wide Web browsers/communicators for business and entertainment use. The future information and telecommunications technology landscape will provide user capabilities and network/management systems and services which are likely to involve the co-existence of many of these web technologies together with associated distributed technologies and architectures (e.g. OSI/ODP, DCE, JAVA, DCOM, ActiveX, CORBA). No one technology is expected to dominate in the immediate term. Examples of current identified key driver technologies are multicast push technology, security/electronic commerce, internet telephony/audio/video, "internet" management, network computers, intelligent agents, High Definition Television, nomadicity/mobility, and distributed databases.
+
+The convergence of computing and networking requires tight cooperation and integration between computer systems and networking technologies. The scope of the required levels of cooperation will extend across the entire OSI stack but will be especially important in the mid-to-higher layers. Examples of specific areas of interest include data link protocol for satellite links, closer collaboration between physical layer and cabling standards, reliable multicast QOS negotiation, co-existence between OSI/CLNP and the IP protocols (IPv4 and IPv6) and migration to IPv6 in the longer term if IPv6 is commercially successful.
+
+Key areas of interest to information and communications technologies are expected to include Data Capture and Identification systems, Data Management Services, Distributed Application Services, Information Interchange Media, Terminology, Multimedia and Representation, Networking and Interconnects, Office Equipment, Programming Languages and Software Interfaces, Security, Software Engineering, User Interfaces, Document Description languages, and coded Character sets.
+
+### **5.3 Common generic capabilities**
+
+A number of fundamental common capabilities have been identified. These must be inherent in the GII to meet the needs of the user. The idea of common and reusable services/components is identified in order that the user will receive adequate value from the total of the parts, in a consistent manner.
+
+The following list is provided as a starting point. Standards developers and others are encouraged to supplement or improve this list as they see appropriate.
+
+- Access Methods – for requesting and reserving system resources/services;
+- Addressing – for identifying entities to receive or provide information, including group directories, directory navigation and dynamic routing;
+- Compression – for specifying the level and method of compression to be applied to data being transmitted between heterogeneous networks and applications;
+- Cost Quotation – for informing users of the costs associated with services requested, and methods by which payment can be made;
+- Data Navigation – for moving from one source of information to other, related, sources of information;
+- Data Portability through conversion – for requesting translation of data from the format it is currently in to a form that can be accepted by the requester;
+- Data Portability without conversion – for moving data from platform to platform in a neutral format;
+- Identification – for identifying objects and data entities to be transmitted via GII as belonging to a specific type, set or sequence of information;
+- Internationalization – for customizing applications for the generation of text in specific languages, for identifying the language of data and the sources of alternative versions of the same information for users who cannot understand the proffered language;
+- Interoperability Testing – for testing service interoperability;
+- Latency Control – for controlling the maximum length of time it may take a message to travel from source to destination<sup>1</sup>;
+
+---
+
+<sup>1</sup> Users must have a common way to specify the maximum acceptable delay in transmission, the "immediate" versus "as available" request for retrieval/supply of information, and how deterministic the delivery mechanism must be.
+
+- Nomadicity/Mobility – for retaining access to services that are not available in the local environment due to user mobility in time or space;
+- Priority Management – for prioritizing a request with respect to all other requests;
+- Privacy/Ownership – for ensuring that data transmitted via GII cannot be read or copied by those not intended to receive the data, including facilities for encryption, watermarking, copyright and IPR protection;
+- Quality of Service – for the identification of levels of functionality acceptable to the user;
+- Route Selection – for user control of networks/routes used to reach the destination;
+- Search – for requesting and defining ways of looking for information via the GII;
+- Security – for defining, in a graded fashion, the levels of security to be used, across all networks, applications and content, during transmission via the GIP<sup>2</sup>;
+- Integrity – For ensuring that information content is not altered without authorization.
+
+### 5.4 General considerations
+
+A number of other factors need to be borne in mind when designing standards for GII services and components.
+
+The following list is provided as a starting point. Standards developers and others are encouraged to supplement or improve this list as they see appropriate.
+
+- affordability – the cost effectiveness of the resources utilized by an enterprise/organization or user over a specified period of time;
+- availability – the measure of the degree of access to a particular resource or set of resources;
+- cultural elements – the special characteristics of languages and the commonly accepted rules for their use (especially in written form) which are particular to a society or geographic area. Examples are: national characters and associated elements (such as hyphens, dashes, and punctuation marks), correct transformation of characters, dates and measures, sorting and searching rules, coding of national items (such as country and currency codes), and keyboard layouts;
+- interoperability – the ability of two or more systems or applications to exchange information and to mutually use the information that has been exchanged;
+- manageability – the ability for any enterprise/organization or user to control how its resources are deployed and utilized;
+- minimalism – a methodology or approach which emphasizes the need to enable a resource to function with a minimum set of options;
+- performance – the measure of a system or subsystem to execute its functions, e.g. response time, throughput, number of transactions per second, or speed of video playback;
+- portability – the ease with which software and data can be transferred from one system to another;
+- quality – the provision of a level of service consistent with the expectations of the receiver of that service;
+
+---
+
+<sup>2</sup> Basic security services (authentication, non-repudiation, etc.) will be provided at each level in a graded fashion. The actual implementation of security levels is transparent to the user, and may differ across networks.
+
+- reliability – the probability that a product or system will perform as required for a specified period of time;
+- scalability – the ability to provide functionality up and down a graduated series of application platforms/environments that differ in speed, capacity, and cost.
+
+## **6 Standards objectives**
+
+The GII is seen as a means to economic growth, competitiveness and socio-cultural development. Jobs, prosperity and cultural developments traditionally follow advances in support infrastructures such as transportation facilities, communications, and higher levels of general and professional education. In the same way, the development of the GII is expected to lead to increased and improved person-to-person communications and to future, and as yet unknown, businesses and interpersonal applications. This move to an Information Society in which individuals have secure global access to all kinds of information and services and which recognizes and meets cultural diversities and sensitivities is expected to be as far reaching in its social and economic impact as the move from the agrarian society to the industrial age.
+
+While the convergence of telecommunications and computing is a prerequisite for the global information infrastructure to emerge, the essence of the information future is considered by some to be the mixing of previously separate types of information (e.g. text, video, audio) into a totally new paradigm. In fact, real and very significant standardization challenges are posed by each of the three component terms encompassed in the GII.
+
+- Global – Global standards are required for the information and infrastructure components of the GII. The globalization of business, the ease of information access and the ease of personal mobility require removal of restrictive national or regional ways of doing business.
+- Information – The purpose of the global infrastructure is to enable users to globally manage the creation, storage, delivery and use of information. Adequate global standards for the representation and secure context specific access to or exchange of information independently of the location of the information provider and information user are needed to realize the benefits of the GII.
+- Infrastructure – The technological convergence and interconnection of telecommunications equipment, computers and much of consumer electronics has lead to new demands on the communications infrastructure by information providers and information users.
+
+The precise requirements for all global information and infrastructure standards are not known. Nonetheless, it is generally accepted that the essential global standards must address market needs, must not impair or restrict the creativity of equipment manufacturers, information providers or service providers, and must provide a realistic and stable base for the envisioned information infrastructure. Global specifications are universally seen as necessary for a timely and successful GII. Such standards can achieve application-application, application-user and user-user interoperability and meet the market requirements for cost effectiveness, quality of service and support for cultural diversity. They must also address the needs generated by new technologies (such as DVD) and the impact of new operating paradigms (such as increased nomadicity and teleworking).
+
+In addition to the global developments underway in some consortia and industry forums relating to the GII, various national and regional organizations are concentrating on developing their own particular national and regional information infrastructures. While these efforts may be localized in particular geographic areas, it is very evident that all regions and consortia need and want global standards. The challenge for the international standards bodies is the development of the essential standards in a timely manner, while recognizing and building on existing efforts.
+
+It is proposed that GII work programmes be based on the sub-objectives outlined below.
+
+### **6.1 Business coupling**
+
+It will be necessary to ensure that ITU-T, in conjunction with other SDOs, will develop the standards necessary to meet or match a value chain model consistent with business requirements. Approaches to ensuring this match include the use of scenario analysis and business value chain modelling.
+
+NOTE – Business coupling is another way of expressing "meets market requirements" and represents strong added-value and market relevancy aspects to standardization programmes. It complements the growing solutions to the convergence objective. The value for users, developers and service providers would be measurable in real terms supportive of GII interoperability, portability, and connectivity needs.
+
+### **6.2 Seamless operation**
+
+It will be necessary to facilitate a seamless linkage between telecommunications, information technology and entertainment (consumer electronics) through joint agreements on use of appropriate standards (or their development as necessary).
+
+NOTE – The ITU-T and SDOs, by acting as project/programme managers, could offer their skills, procedures, collaborative agreements and liaison to manage and forward standards development and or importation of existing standards and/or specifications from outside bodies/groups.
+
+### **6.3 Partnerships**
+
+It will be necessary to ensure that ITU-T has sufficient working links to other SDOs which will be partners in the value chain.
+
+### **6.4 Joint work**
+
+Procedures to enable joint meetings, joint text, deferred ownership, etc., will need to be resolved amongst a set of collaborating SDOs for areas of joint interest.
+
+### **6.5 Cross-industry interfaces**
+
+The identification of critical cross-industry interfaces is a vital aspect of the convergence process.
+
+NOTE – Focused attention to cross-industry interfaces in light of GII and convergence is required at all levels.
+
+### **6.6 Common GII models**
+
+It will be necessary to establish, jointly with appropriate partners, a common set of models to be used as a framework for progression of GII related activities.
+
+## **7 Role of ITU-T**
+
+The strength of the ITU-T (and other SDOs) lies in their processes, their international membership, collaborative agreements and facilitation of global trade and commerce. The ITU-T can jointly create, implement and manage to a model based on GII standardization needs with its partner SDOs. The ITU is a strong vital organization equipped and organized to manage convergence and broker supportive Standards Development to benefit all parties. It can use its experts and processes to benefit from collaboration with experts from other groups via both formal and informal methods. The ITU can manage the puzzle, bring the players together, seek out agreement on work flow complete with mapping to each others, groups and cross-referenced standards and specifications, all geared towards solving the bigger/macro goal of standards for the GII.
+
+ITU-T SG 13 has been identified by WTSC-96 as the Lead Study Group within the ITU-T for the Global Information Infrastructure. The responsibilities of a Lead Study Group are defined in the following extract from Resolution 1:
+
+"A Study Group may be designated by the WTSC or TSAG as the "Lead Study Group" for ITU-T studies forming a defined programme of work involving a number of Study Groups. This Lead Study Group should be responsible for the study of the appropriate core questions. In addition, in consultation with the relevant Study Groups and in collaboration, where appropriate, with other standards bodies, the Lead Study Group has the responsibility to define and to maintain the overall framework and to coordinate, to assign (recognizing the mandates of the Study Groups) and to prioritize the studies to be done by the Study Groups and to ensure the preparation of consistent, complete and timely Recommendations."
+
+The work of SG 13 as the Lead Study Group for the GII in the ITU-T will include:
+
+- developing an overall view, in broad terms, of GII standardization needs within the ITU-T;
+- providing the primary point of contact on GII to other standards development organizations and industry groups (while the other Study Groups will interact with external organizations, as required, in their own areas of interest);
+- ensuring development of Recommendations if an activity is deemed to be important and if there was no existing work programme in any SG;
+- ensuring development of Recommendations if an activity was deemed to be important and if the work programme for that activity in the ITU does not meet the needs of the GII (e.g. in terms of features or scheduling);
+- taking the initiative for establishing an appropriate meeting schedule to progress its work expeditiously and take advantage of known meetings of relevant SGs by, for example, scheduling appropriate meetings to take place simultaneously with other SGs or WPs meetings;
+- encouraging electronic means of working such as audio teleconferencing and electronic mail;
+- being proactive in collaborating with other standards organizations and other industry organizations.
+
+To perform its work SG 13 will create a work programme, including:
+
+- a work plan, which will constitute an internal management tool covering project descriptions, detailed work items and schedules;
+- a project plan, which will provide information about milestones of the projects including dates, deliverables and required inputs
+- assign project coordinators for each individual projects.
+
+## **8 Framework of Recommendations**
+
+One of the major activities to be undertaken in the early stages of the ITU-T GII activities clearly has to be work on the three key elements mentioned above:
+
+- a) a common programme document, outlining areas of collaboration;
+- b) a common positioning document, describing the principles, frameworks and architectures with, and within which, the appropriate organizations are operating;
+- c) common terms and definitions.
+
+This overview Recommendation acts both as an overview and umbrella document for a family of subtending Recommendations.
+
+Currently, the framework for the Y series of Recommendations is shown below.
+
+|       |                                           |
+|-------|-------------------------------------------|
+| Y.100 | General                                   |
+| Y.200 | Services, applications and middleware     |
+| Y.300 | Network aspects                           |
+| Y.400 | Interfaces and protocols                  |
+| Y.500 | Numbering, addressing and naming          |
+| Y.600 | Operation, administration and maintenance |
+| Y.700 | Security                                  |
+
+The following Recommendations have been approved:
+
+|       |                                                                                 |
+|-------|---------------------------------------------------------------------------------|
+| Y.100 | General overview of the Global Information Infrastructure standards development |
+| Y.110 | Global Information Infrastructure principles and framework architecture         |
+| Y.120 | Global Information Infrastructure scenario methodology                          |
+
+## ITU-T RECOMMENDATIONS SERIES
+
+|                 |                                                                                                                                |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A        | Organization of the work of the ITU-T                                                                                          |
+| Series B        | Means of expression: definitions, symbols, classification                                                                      |
+| Series C        | General telecommunication statistics                                                                                           |
+| Series D        | General tariff principles                                                                                                      |
+| Series E        | Overall network operation, telephone service, service operation and human factors                                              |
+| Series F        | Non-telephone telecommunication services                                                                                       |
+| Series G        | Transmission systems and media, digital systems and networks                                                                   |
+| Series H        | Audiovisual and multimedia systems                                                                                             |
+| Series I        | Integrated services digital network                                                                                            |
+| Series J        | Transmission of television, sound programme and other multimedia signals                                                       |
+| Series K        | Protection against interference                                                                                                |
+| Series L        | Construction, installation and protection of cables and other elements of outside plant                                        |
+| Series M        | TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits |
+| Series N        | Maintenance: international sound programme and television transmission circuits                                                |
+| Series O        | Specifications of measuring equipment                                                                                          |
+| Series P        | Telephone transmission quality, telephone installations, local line networks                                                   |
+| Series Q        | Switching and signalling                                                                                                       |
+| Series R        | Telegraph transmission                                                                                                         |
+| Series S        | Telegraph services terminal equipment                                                                                          |
+| Series T        | Terminals for telematic services                                                                                               |
+| Series U        | Telegraph switching                                                                                                            |
+| Series V        | Data communication over the telephone network                                                                                  |
+| Series X        | Data networks and open system communications                                                                                   |
+| <b>Series Y</b> | <b>Global information infrastructure</b>                                                                                       |
+| Series Z        | Programming languages                                                                                                          |