Add files using upload-large-folder tool

marked/Y/T-REC-F.747.3-201303-I_PDF-E/raw.md

@@ -0,0 +1,608 @@
+
+
+# ITU-T
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+## F.747.3
+
+(03/2013)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Audiovisual services
+
+---
+
+**Requirements and functional model for a  
+ubiquitous network robot platform that supports  
+ubiquitous sensor network applications and  
+services**
+
+Recommendation ITU-T F.747.3
+
+# 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>                                | <b>F.400–F.499</b> |
+| <b>DIRECTORY SERVICES</b>                                       | <b>F.500–F.549</b> |
+| <b>DOCUMENT COMMUNICATION</b>                                   |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| <b>DATA TRANSMISSION SERVICES</b>                               | <b>F.600–F.699</b> |
+| <b>AUDIOVISUAL SERVICES</b>                                     | <b>F.700–F.799</b> |
+| <b>ISDN SERVICES</b>                                            | <b>F.800–F.849</b> |
+| <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b>                     | <b>F.850–F.899</b> |
+| <b>HUMAN FACTORS</b>                                            | <b>F.900–F.999</b> |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# **Recommendation ITU-T F.747.3**
+
+# **Requirements and functional model for a ubiquitous network robot platform that supports ubiquitous sensor network applications and services**
+
+## **Summary**
+
+Recommendation ITU-T F.747.3 describes the concept, use cases, requirements and functional model of a ubiquitous network robot platform that supports ubiquitous sensor network (USN) applications and services.
+
+## **History**
+
+| Edition | Recommendation | Approval   | Study Group |
+|---------|----------------|------------|-------------|
+| 1.0     | ITU-T F.747.3  | 2013-03-16 | 16          |
+
+## **Keywords**
+
+Middleware, network robot system, ubiquitous network robot platform, USN.
+
+## 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 2014
+
+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 .....                                                 | 2           |
+| 6 | Overview of UNR-PF in terms of USN applications and services..... | 3           |
+|   | 6.1 General overview of UNR-PF .....                              | 3           |
+|   | 6.2 Relationships between USN and UNR-PF .....                    | 4           |
+| 7 | Use cases of ubiquitous network robot platform .....              | 5           |
+|   | 7.1 Health support service .....                                  | 5           |
+|   | 7.2 Shopping support service .....                                | 6           |
+| 8 | Requirements for UNR-PF .....                                     | 8           |
+|   | 8.1 Abstraction of functionality.....                             | 8           |
+|   | 8.2 Inter-service collaboration.....                              | 9           |
+|   | 8.3 Service among multiple areas.....                             | 10          |
+|   | 8.4 Service execution based on customer attributes.....           | 13          |
+| 9 | Functional model for UNR-PF .....                                 | 13          |
+|   | 9.1 Robot registry function.....                                  | 15          |
+|   | 9.2 Operator registry function .....                              | 15          |
+|   | 9.3 User registry function.....                                   | 15          |
+|   | 9.4 Map registry function .....                                   | 15          |
+|   | 9.5 Service queue function .....                                  | 15          |
+|   | 9.6 State manager function.....                                   | 15          |
+|   | 9.7 Resource manager function .....                               | 15          |
+|   | 9.8 Message manager function.....                                 | 15          |
+|   | Bibliography.....                                                 | 17          |
+
+
+
+# Recommendation ITU-T F.747.3
+
+## Requirements and functional model for a ubiquitous network robot platform that supports ubiquitous sensor network applications and services
+
+# 1 Scope
+
+The objective of this Recommendation is to define a ubiquitous network robot platform, and to identify its requirements and functional model. The use of standard interfaces for the ubiquitous network robot platform will ensure network robot service reusability, portability across several network robot services, and network accessibility and interoperability by the ubiquitous sensor network (USN).
+
+The scope of this Recommendation includes:
+
+- the concept of ubiquitous network robot platform;
+- requirements of the ubiquitous network robot platform;
+- functional model of the ubiquitous network robot platform.
+
+# 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 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.2 sensor network** [ITU-T Y.2221]: A network comprised of inter-connected sensor nodes exchanging sensed data by wired or wireless communication.
+
+**3.1.3 sensor node** [ITU-T Y.2221]: A device consisting of sensor(s) and optional actuator(s) with capabilities of sensed data processing and networking.
+
+**3.1.4 service** [ITU-T Y.2221]: A set of functions and facilities offered to a user by a provider.
+
+**3.1.5 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.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 robot:** A device with a processing unit often accompanied by sensors and actuators that can work with real-world phenomena and entities. Robots can be roughly classified into the following three types: visible-type robot, virtual-type robot and unconscious-type robot.
+
+**3.2.2 ubiquitous network robot platform:** Middleware that enables applications to perform services continuously by combining multiple robotic devices effectively across multiple areas.
+
+**3.2.3 unconscious-type robot:** A type of robot that mainly senses real-world phenomena and processes measurement results into high-level abstractions. An example of this type of robot is a camera equipped with a processing unit used for detecting people. Unconscious-type robots are often embedded in environments such as roads, towns or rooms, or are hidden in clothes or accessories.
+
+**3.2.4 virtual-type robot:** A type of robot that mainly processes and utilizes information via a network. Smartphones are examples of this type of robot. Virtual-type robots typically interact with people through audio and visual modalities.
+
+**3.2.5 visible-type robot:** A type of robot that can be seen and which can take one of several forms such as a humanoid, a pet or a stuffed animal. Visible-type robots interact with people in a combination of verbal and nonverbal modalities such as through a conversation augmented by gestures.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|        |                                   |
+|--------|-----------------------------------|
+| FDML   | Field Data Mark-up Language       |
+| FE     | Functional Entity                 |
+| GPF    | Global Platform                   |
+| ID     | Identifier                        |
+| LOD    | Linked Open Data                  |
+| LPF    | Local Platform                    |
+| NGN    | Next Generation Network           |
+| NRS    | Network Robot System              |
+| PF     | Platform                          |
+| SOA    | Service-Oriented Architecture     |
+| UNR    | Ubiquitous Network Robot          |
+| UNR-PF | Ubiquitous Network Robot Platform |
+| USN    | Ubiquitous Sensor Network         |
+
+## 5 Conventions
+
+None.
+
+# **6 Overview of UNR-PF in terms of USN applications and services**
+
+### **6.1 General overview of UNR-PF**
+
+Demands for assistance robots are quickly emerging with the increase in elderly population. In recent decades, researchers have been focusing on constructing robots that can interactively support daily human activities. As the structure and functionality of robots grow large and complicated, constructing robots now requires more time, cost and effort. As with traditional software engineering, developers have started to seek modularity and reusability of basic functional components, which has led to research and development of common libraries and middleware. Reusable and modular components allow developers to utilize existing functional modules in combination with their own software and to rapidly develop working robots. This modularized development process has accelerated the development of stand-alone robots as well as individual functional components. At the same time, however, variations in both hardware and software have decreased the reusability of robotic applications.
+
+Another approach to enhance capabilities of robots is the concept called network robot system (NRS) or networked robots [b-Sanfeliu2008]. The main goal of NRS was to integrate various types of devices such as robots, sensor networks and smartphones, so that the whole system could act as an integrated system with enhanced capabilities that cannot be attained by a single robot or multiple uniform robots. Since its introduction in 2002, many research projects have been carried out accompanied with real-world field experiments. These have successfully shown that the concept is effective ([b-Jung2007], [b-Nakamura2008], [b-Tezuka2006], [b-Sanfeliu2010], [b-Shiomi2011] and [b-Salvini2011]).
+
+However, customers need robots to support them in a much wider range of daily activities. Robots for individual household tasks such as cleaning floors or folding laundry are not sufficient. Support for the elderly and disabled in a variety of daily activities is in great demand. Such support requires robots to accompany people to many different places (e.g., homes, shopping malls, hospitals) and to assist people for various activities (e.g., checking health, showing routes, carrying luggage) in ways that differ depending on place and the physical demands of an individual (e.g., wheelchair user). At the same time, these sequences of activities shall be well integrated to provide comfortable and seamless support throughout our daily lives.
+
+Existing robotic systems cannot yet provide such continuous support in various aspects of our daily lives. Although they have had success in enriching capabilities of individual robotic applications, a general framework is missing for adapting behaviours of robots and composing them to form an integrated sequence of applications. Similar concepts can be seen in computer systems, such as service oriented architecture (SOA). SOA provides design principles for constructing large-scale information systems and has been adopted in various middleware stacks, especially in web service systems. In combination with the concepts of grid or cloud computing systems, many commercial services with high dependability are available today. However, these concepts are not sufficient for robotic systems.
+
+The major difference between information systems and robotic systems is where the applications reside. Information system applications reside in cyberspace using information terminals such as personal computers or mobile phones. This is especially clear for web-based systems where applications run through web browsers. Based on the information shown on the screen, users perform actions such as business procedures, travel and cooking. Thus, the actual work in the physical world is left to the customers. This is where the robotic systems with sensor networks start. Robotic systems need to consider various factors in real-world environments, including physical abilities and limitations of both customers and devices. Moreover, as stated previously, a variety of different devices need to be integrated to realize continuous robotic support in our daily lives.
+
+As such, one needs to focus on different kinds of "ubiquity", not just for location but also for various applications and ways of providing each service on the basis of customer attributes, as well as inter-application and inter-location continuity. As the complexity of robotic devices is much higher than that of traditional information systems, abstract, common access methods need to be provided for application programmers and service providers to make the development process easy and highly reusable. A new framework is now required that can bridge the gap between systems that realize the above ubiquity and those that improve and extend traditional robot systems which satisfy such demands. Based on such considerations, an extended infrastructure based on NRS is defined in this Recommendation, the ubiquitous network robot platform (UNR-PF) [b-Sato2011b] and [b-Kamei2012]. UNR-PF combines multiple robots in multiple areas for the support of NGN, USN and their middleware that provide access to sensor networks and portable devices. This concept offers the possibility of providing innovative services promptly and at low cost.
+
+### **6.2 Relationships between USN and UNR-PF**
+
+UNR-PF utilizes USN and USN middleware in two ways: a) as an infrastructure with advanced functionalities such as intelligent routing of messages, and b) as a representative of various sensor networks/nodes. USN may provide connectivity not only to sensors, or unconscious-type robots, but also to robots of the visible and virtual types. UNR-PF can be seen as a middleware for USN applications that provides detailed information and control over USN, such as detailed device profiles, common representation of measurements and an abstract command interface. UNR-PF can also be considered as a higher layer router over USN. UNR-PF selects and allocates appropriate devices to applications. This allocation may change dynamically over time, while the applications do not care or notice the actual changes.
+
+Figure 1 shows the relationship between the open USN service platform and UNR-PF defined in this Recommendation.
+
+![Figure 1: Relation between open USN service platform and UNR-PF. The diagram shows a hierarchical architecture. At the top is the 'Application' layer. Below it is the 'Open USN service platform' which contains several functional elements: 'Application support FE', 'Semantic query FE', 'LOD linking FE', 'Semantic inference FE', 'Semantic USN repository FE' (which includes 'Semantic data repository' and 'Sensed data repository'), 'Resource management FE', and the 'Ubiquitous network robot platform' (shaded grey). These elements are interconnected with bidirectional arrows. Below the Open USN service platform is the 'Adaptation FE' layer, which includes 'Adaptation FE1', 'Adaptation FE2', and 'Adaptation FE_n'. These are connected to 'USN middleware' layers (USN middleware_2, ..., USN middleware_n), which in turn connect to a 'Robot' and 'Sensor or sensor network' (represented by circles in dashed boxes). The label 'F.747.3(13)_F01' is at the bottom right of the diagram.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg)
+
+Figure 1: Relation between open USN service platform and UNR-PF. The diagram shows a hierarchical architecture. At the top is the 'Application' layer. Below it is the 'Open USN service platform' which contains several functional elements: 'Application support FE', 'Semantic query FE', 'LOD linking FE', 'Semantic inference FE', 'Semantic USN repository FE' (which includes 'Semantic data repository' and 'Sensed data repository'), 'Resource management FE', and the 'Ubiquitous network robot platform' (shaded grey). These elements are interconnected with bidirectional arrows. Below the Open USN service platform is the 'Adaptation FE' layer, which includes 'Adaptation FE1', 'Adaptation FE2', and 'Adaptation FE\_n'. These are connected to 'USN middleware' layers (USN middleware\_2, ..., USN middleware\_n), which in turn connect to a 'Robot' and 'Sensor or sensor network' (represented by circles in dashed boxes). The label 'F.747.3(13)\_F01' is at the bottom right of the diagram.
+
+**Figure 1 – Relation between open USN service platform and UNR-PF**
+
+## 7 Use cases of ubiquitous network robot platform
+
+### 7.1 Health support service
+
+A health support service using two different platforms is shown in Figure 2.
+
+In the figure, '1' is an electronic tag attestation platform. A user is registered in an entrance area as the first step. At the same time, disclosure level of user information is set here. The attestation platform discloses customer information to the user according to the user's demand. Next, the user sets up the alarm clock of get-up time in an alarm clock support area. The user can then exercise in the physical exercise area where the user's health condition is checked. A teacher robot gives instructions for the exercise and the assistance robot instructs the user according to the actions performed. The user's health condition is checked by the action recognition unit embedded in the robots. Finally, the user gets the health condition results in the health check area.
+
+This example shows an implementation of two or more cooperative services and one independent service (alarm clock support area) on the network robot platform.
+
+![Figure 2 – Health support service diagram showing four areas: [1] Entrance area, [2] Alarm clock support area, [3] Physical exercise area, and [4] Health check area. The diagram includes a central FDML unit, an Electronic tag attestation-PF box, and a Network robot platform box. A table lists the number of robots in each area: Visible (5), Virtual (2), and Unconscious (6).](d4af765160d04ecef538e5066006dc77_img.jpg)
+
+**[2] Alarm clock support area**
+
+**[3] Physical exercise area**
+
+**[1] Entrance area**
+
+**[4] Health check area**
+
+**Electronic tag attestation-PF**
+
+- Protection of personal information
+- Disclosure of user information according to user demand
+
+**Network robot platform**
+
+- Robotic control based on disclosed user information and recognized action data
+
+**The number of the robot**
+
+|             |   |
+|-------------|---|
+| Visible     | 5 |
+| Virtual     | 2 |
+| Unconscious | 6 |
+
+**FDML**
+
+**Action recognition unit**
+
+**Assistant robot**
+
+**Teacher robot**
+
+**You are cool!**
+
+**Good morning!**
+
+**Let's begin the next exercise**
+
+**Please set disclosure level.**
+
+**Your health condition is ...**
+
+F.747.3(13)\_F02
+
+Figure 2 – Health support service diagram showing four areas: [1] Entrance area, [2] Alarm clock support area, [3] Physical exercise area, and [4] Health check area. The diagram includes a central FDML unit, an Electronic tag attestation-PF box, and a Network robot platform box. A table lists the number of robots in each area: Visible (5), Virtual (2), and Unconscious (6).
+
+**Figure 2 – Health support service**
+
+### 7.2 Shopping support service
+
+The second use case of UNR-PF is shopping support ([b-Nishio2010], [b-OMG2012] and [b-Kamei2012]). Figure 3 shows the overview of the scenario. A typical service scenario is performed across three areas: customer's home (Area 1 in Figure 3), shopping mall (Area 2) and support centre (Area 3).
+
+When a customer feels like going for shopping, he/she first makes reservation of the service using a smartphone. Here, with help from a remote operator, the customer makes a rough plan on what to buy. The operator or the smartphone application may provide the customer with recommendations on things to buy ("fish on sale today") or on where to go shopping ("many customers gave store X a high ranking"). After arriving at the mall, the customer finds that a robot is already waiting for him/her at the entrance. In this example, as the customer has a walking disability, a wheelchair robot is prepared. The customer sits on the wheelchair robot and is guided in the mall so that he/she can purchase the planned items.
+
+![Figure 3: Overview of the shopping support service. The diagram illustrates a service flow across different areas. At the top left, 'Area 1: Home' shows a user booking a wheelchair robot using a smartphone. This connects to 'The ubiquitous network robot platform (UNR-PF)', which is linked to a 'Teleoperator' at the top right. The UNR-PF is also connected to a 'Networking' hub. Below, 'Area 2(a): West mall' shows the wheelchair robot welcoming and navigating the user. This area is connected to 'Area 2(b): East mall', where navigation continues. The entire system is supported by a central networking hub.](af7916c89a458fdab6c3f443217388ae_img.jpg)
+
+Area 1: Home
+
+Book a wheelchair robot using smartphone in advance
+
+The ubiquitous network robot platform (UNR-PF)
+
+Teleoperator
+
+Networking
+
+Area 2(a): West mall
+
+The wheelchair robot welcomes and navigates the user
+
+Area 2(b): East mall
+
+Navigation continues
+
+F.747.3(13)\_F03
+
+Figure 3: Overview of the shopping support service. The diagram illustrates a service flow across different areas. At the top left, 'Area 1: Home' shows a user booking a wheelchair robot using a smartphone. This connects to 'The ubiquitous network robot platform (UNR-PF)', which is linked to a 'Teleoperator' at the top right. The UNR-PF is also connected to a 'Networking' hub. Below, 'Area 2(a): West mall' shows the wheelchair robot welcoming and navigating the user. This area is connected to 'Area 2(b): East mall', where navigation continues. The entire system is supported by a central networking hub.
+
+**Figure 3 – Overview of the shopping support service**
+
+Figure 4 shows the structure and interaction sequence of the service. The customer first makes a reservation via the virtual-type robot on the mobile device at home. The virtual-type robot is connected to the local platform (LPF) installed in the user's home. LPF notifies the global platform (GPF) of the reservation information. The shopping support service application is connected to the GPF and receives the reservation request. After receiving the reservation request, the service application registers its service ID and a trigger condition (the user's arrival at the shopping mall, in the example) to the service queue on the GPF. The GPF refers to its map registry to confirm the LPF of the shopping mall and then registers the service and its starting condition to the LPF's service queue. When the user approaches the shopping mall, the virtual-type robot on the user's mobile device connects to the LPF of the shopping mall and notifies it of the user arrival. Then, the LPF of the shopping mall determines that the state meets the starting condition for the service and notifies the service application of the start via the GPF. Next, the service application requests the resource manager to reserve the robot in the shopping mall and the operator in the support centre via the GPF. To reserve the robot, the resource manager refers to the user registry and selects a suitable robot for the user. In the shopping support service, the resource manager selects a wheelchair robot if the user has difficulty in walking. Otherwise, it selects another type of mobile robot. After the allocation of the resources, the service is executed in accordance with the service flow defined in the service application. The service application refers to the map registry in the LPF and instructs the robot to navigate around the shopping mall.
+
+In the case of a large shopping mall, the shopping support service is provided across several areas managed by different LPFs. When the robot comes close to the boundary between the two areas, the robot notifies GPF's state manager via the state manager of the LPF of the current area. Then, GPF's state manager refers to its map registry to find the LPF of the next area and then registers the service and its trigger condition, i.e., the customer's arrival at the next area or the service queue of the LPF. When the user arrives at the next area, the robot disconnects from the LPF of the first area and connects to the next LPF, if the robot is able to continue working in the next area. Otherwise, another robot in the next area comes to pick up the customer. Thus, the service is executed continuously. In this way, the customer can receive the service seamlessly in a wide area regardless
+
+of the area segmentation for the robotic system. When an operator is required, the service application requests the assignment of an operator to the LPF through GPF. The assigned operator will assist the user by remotely taking the user's detailed request and adapting it for the platform.
+
+![Figure 4: Overview of the shopping support service sequence. The diagram illustrates a multi-layered system architecture and a sequence of 17 steps. The layers are: Touring support service application (top), Global platform (middle), and three Local platforms (Home, Shopping mall, Operation center) at the bottom. The sequence of steps is: 1. Request service (Home to Global), 2. Announce request (Global to Home), 3. Announce request (Home to Touring), 4. Register on service queue (Touring to Home), 5. Register on service queue (Home to Global), 6. Announce arrival (Global to Home), 7. Announce arrival (Home to Shopping mall), 8. Announce start (Shopping mall to Touring), 9. Request robot (Touring to Shopping mall), 10. Request robot (Shopping mall to Global), 11. Bind robot suitable for user (Global to Shopping mall), 12. Request operator (Global to Operation center), 13. Request operator (Operation center to Global), 14. Bind operator for the service (Global to Operation center), 15. Execute service flow (Operation center to Touring), 16. Execute service flow (Touring to Global), 17. Execute service flow (Global to Shopping mall). The diagram also shows a 'Virtual-type robot' moving from 'Home' to 'Shopping mall' and an 'Operator' at the 'Support center'.](b9ecbc3baefab13719e000faa6e0c7eb_img.jpg)
+
+F.747.3(13)\_F04
+
+Figure 4: Overview of the shopping support service sequence. The diagram illustrates a multi-layered system architecture and a sequence of 17 steps. The layers are: Touring support service application (top), Global platform (middle), and three Local platforms (Home, Shopping mall, Operation center) at the bottom. The sequence of steps is: 1. Request service (Home to Global), 2. Announce request (Global to Home), 3. Announce request (Home to Touring), 4. Register on service queue (Touring to Home), 5. Register on service queue (Home to Global), 6. Announce arrival (Global to Home), 7. Announce arrival (Home to Shopping mall), 8. Announce start (Shopping mall to Touring), 9. Request robot (Touring to Shopping mall), 10. Request robot (Shopping mall to Global), 11. Bind robot suitable for user (Global to Shopping mall), 12. Request operator (Global to Operation center), 13. Request operator (Operation center to Global), 14. Bind operator for the service (Global to Operation center), 15. Execute service flow (Operation center to Touring), 16. Execute service flow (Touring to Global), 17. Execute service flow (Global to Shopping mall). The diagram also shows a 'Virtual-type robot' moving from 'Home' to 'Shopping mall' and an 'Operator' at the 'Support center'.
+
+**Figure 4 – Overview of the shopping support service sequence**
+
+## 8 Requirements for UNR-PF
+
+### 8.1 Abstraction of functionality
+
+It is required that UNR-PF provides a standardized and abstracted interface for controlling as well as receiving results from USN nodes. That is, from application point of view, UNR-PF provides access to a set of abstracted functionalities instead of raw USN nodes.
+
+One of the most simple use cases of UNR-PF is collaboration among sensor networks and robots. A sensor network measures phenomena in the real world, notifies them to one or more applications, and then the application commands actuator devices, such as robots and smartphones, to interact with people. Such collaboration may be performed by USN, without UNR-PF, when treating robots as one of the "sensor nodes" with actuator facility. However, by the abstraction of functionality provided by UNR-PF, this can be realized in a much simpler way.
+
+Consider the example shown in Figure 5. Here, based on the sensing result, a person is approaching a dangerous construction area, a robot warns the person. In order to warn the person, a) a mobile robot can approach the person and give a warning, or b) a nearby loudspeaker can warn the person. From the viewpoint of the effect, i.e., to let the person know that he/she is approaching a dangerous area, these two devices perform equivalent services. Dangerous spots change every day. If the application is coded to use a navigation robot and if there are no robots available nearby, the customer would not receive a warning. However, if the application is programmed to utilize the "alert" functionality, then the system would search for a device that can provide such functionality and choose it based on resource availability. This is also useful from the point that applications are not bound to a certain device at the time when it was coded. The application can then continue to provide service without change even though the devices have changed, if they provide the same kind of functionality.
+
+![Diagram illustrating service execution by abstracted functionalities. A 'Speaking robot' (a sphere on a pole) sends a 'Speech' message to a woman, Ms. Smith, saying 'Ms. Smith! it is dangerous here!'. A 'Possible robot candidates' box points to both the 'Speaking robot' and a 'Communication robot' (a humanoid robot). The 'Communication robot' sends a message to Ms. Smith saying 'Ms. Smith, it is dangerous here!'. A dashed arrow labeled 'Movement, speech and gesture' points from the 'Communication robot' to Ms. Smith. A red shopping cart is visible in the background.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg)
+
+Diagram illustrating service execution by abstracted functionalities. A 'Speaking robot' (a sphere on a pole) sends a 'Speech' message to a woman, Ms. Smith, saying 'Ms. Smith! it is dangerous here!'. A 'Possible robot candidates' box points to both the 'Speaking robot' and a 'Communication robot' (a humanoid robot). The 'Communication robot' sends a message to Ms. Smith saying 'Ms. Smith, it is dangerous here!'. A dashed arrow labeled 'Movement, speech and gesture' points from the 'Communication robot' to Ms. Smith. A red shopping cart is visible in the background.
+
+**Figure 5 – Service execution by abstracted functionalities**
+
+Although the above case focuses on the actuation part, the same concept can be applied for the sensing part. When the sensing functionality is also abstracted, applications can request abstracted sensing functionalities, such as detection of dangerous areas, to the infrastructure, while the actual sensing equipment or sensor network in use may change.
+
+### 8.2 Inter-service collaboration
+
+It is required that UNR-PF provides functionalities to allow collaboration between different USN applications for realizing compositional applications.
+
+Consider the photo printing service shown in Figure 6(a). This service has two tasks: taking a picture and then printing it out. This represents a simple functional dependency. Robot A possesses the photo taking function while Robot B possesses the photo printing function; they are spatially separated, but linked via a network. To realize this service, the photo printing task can be performed only after the photo taking task. Therefore, the robots need to interact with the customer based on the customer's history.
+
+Another example is a service that guides exhibits in a museum, exhibition hall, etc., as shown in Figure 6(b). The tasks are to explain the exhibit and to guide the visitor to the next exhibit. Given that the visitor is free to visit the exhibits in any order, each robot needs to modify its responses according to the visitor's service history.
+
+![Figure 6: Inter-service collaboration. The diagram is divided into two parts: (a) Photo printing service and (b) Guiding service in museum. Part (a) shows Robot A performing a 'Photo-taking task' by saying 'Ms. Smith, say cheese!' to a woman, and then Robot B performing a 'Photo-printing task' by saying 'Mr Brown, go first to the photograph-taking area!' to a man. Part (b) shows Robot A performing an 'Explanation (Picture A) and guide task' by saying 'This picture was drawn by Mr Smith.' to a woman and child, and then Robot B performing an 'Explanation (Picture B) and guide task' by saying 'You have not looked at picture A. I recommend that you look at picture A!' to a man. Both parts show robots interacting with customers and displaying pictures on screens.](fa859e4e468bfb2710a94527f2c504af_img.jpg)
+
+Robot A: Ms. Smith, say cheese!
+
+Photo-taking task
+
+Robot B: Mr Brown, go first to the photograph-taking area!
+
+Photo-printing task
+
+a) Photo printing service
+
+Picture A: This picture was drawn by Mr Smith.
+
+Picture B: You have not looked at picture A. I recommend that you look at picture A!
+
+Explanation (Picture A) and guide task
+
+Explanation (Picture B) and guide task
+
+b) Guiding service in museum
+
+F.747.3(13)\_F06
+
+Figure 6: Inter-service collaboration. The diagram is divided into two parts: (a) Photo printing service and (b) Guiding service in museum. Part (a) shows Robot A performing a 'Photo-taking task' by saying 'Ms. Smith, say cheese!' to a woman, and then Robot B performing a 'Photo-printing task' by saying 'Mr Brown, go first to the photograph-taking area!' to a man. Part (b) shows Robot A performing an 'Explanation (Picture A) and guide task' by saying 'This picture was drawn by Mr Smith.' to a woman and child, and then Robot B performing an 'Explanation (Picture B) and guide task' by saying 'You have not looked at picture A. I recommend that you look at picture A!' to a man. Both parts show robots interacting with customers and displaying pictures on screens.
+
+**Figure 6 – Inter-service collaboration**
+
+As can be seen from these examples, there are many cases where multiple tasks or applications need to collaborate with each other to provide a consistent service to customers. In some cases, applications from different service providers need to collaborate. In the photo printing service example, photo taking and printing may be performed by different companies. In both situations of Figure 6, the important thing is that the applications share certain aspects of customer history. In the photo printing service case, only photograph data may be exchanged. However, in the museum guidance service, robots may share more detailed information, such as in which point the customer was interested, what kind of questions did the customer ask, or how long the customer spent in front of a Van Gogh painting. In some cases, such information sharing can be performed within frameworks of traditional information system. However, a common infrastructure is needed for sharing information required for affecting human-robot interaction and reflecting it on the behaviour of the robot.
+
+### 8.3 Service among multiple areas
+
+It is required that UNR-PF provides functionalities to allow applications to seamlessly utilize USN nodes in multiple areas.
+
+One of the key aspects in multiple-device collaboration is resource allocation in the spatiotemporal domain. Robots, as well as sensor networks, can only be effective in limited areas due to their physical nature. Sensors can only sense phenomena happening in a limited area, and robots can only serve within a certain area. For example, robots nowadays have a limited navigation capability and suffer interference from obstacles, floor materials and bumps. Battery life is another concern; after a while, robots need to be recharged. Due to these limits, in order to serve people that have much wider area of activity, multiple robots and sensor networks need to collaborate with each other while applications run continuously. For example, consider a navigation service where a robot guides a customer around a shopping mall. Depending on its ability, the robot may not be able to navigate in certain areas such as outdoor corridor between different mall buildings. In such cases,
+
+however, the service must continue. Therefore, UNR-PF will perform handover of the navigation act that is necessary for the guidance service (Figure 7). Such handover may occur in different patterns based on the ability of the robot and the resource availability. A similar situation is likely to happen for sensing equipment, such as for localizing or identifying people throughout the mall. When a customer reaches the end of sensing area of one device, UNR-PF searches for other devices that can continue to sense the customer so that the application can continue to receive and utilize sensing results.
+
+In order to realize a smooth handover between various devices, UNR-PF shall provide rich support so that applications do not need to be concerned about the actual resource availability or the device ability. UNR-PF shall manage various devices not only spatially but also in temporal space in order to effectively allocate them according to application requirements. At the same time, in order to perform effective handovers among devices of various natures and in varieties of areas, UNR-PF needs to manage spatial information as well as specifications of devices. As shown in Figure 8 ([b-Kolbe2011] and [b-OGC2011]), the navigation service is one typical example that clearly shows necessity for such information. In many indoor and outdoor areas, there are places not suitable for robots to move around. This limitation depends on the specifications of robots and of the kind of service the robot needs to perform. Moreover, the spatial nature may change with time. For example, think of a case where a robot guides the user around a station. In mornings and evenings of weekdays there are huge numbers of people passing through during the rush-hour, and thus the corridors become not suitable for robots to move around. But at other hours, the station is less crowded and the robot can easily perform its service. As there are many cases where such dynamic changes occur, the spatiotemporal nature of areas shall be managed and considered by UNR-PF.
+
+![Figure 7: Example of service handover between robots. The diagram is divided into three horizontal panels labeled a, b, and c. Panel a) shows a robot guiding a woman and child from Mall 1 through a corridor to Mall 2; a red arrow indicates the path, and a speech bubble from the robot says 'I will guide you'. Panel b) shows a robot at Mall 1 handing over to a second robot; the first robot's bubble says 'From here on, that robot will guide you', and a red arrow shows the second robot's path to Mall 2. Panel c) shows a robot at Mall 1 and another robot waiting at Mall 2; the first robot's bubble says 'Another robot is waiting for you across the entrance', with blue arrows indicating communication/handover across the corridor.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg)
+
+a) If the robot is able to navigate all the way, the same robot continues the service
+
+b) If the first robot cannot navigate all the way but there is another robot that can, the service is handled by the other robot
+
+c) If there are no robots that can navigate through the corridor, the service is passed over to another robot at a distant location
+
+F.747.3(13)\_F07
+
+Figure 7: Example of service handover between robots. The diagram is divided into three horizontal panels labeled a, b, and c. Panel a) shows a robot guiding a woman and child from Mall 1 through a corridor to Mall 2; a red arrow indicates the path, and a speech bubble from the robot says 'I will guide you'. Panel b) shows a robot at Mall 1 handing over to a second robot; the first robot's bubble says 'From here on, that robot will guide you', and a red arrow shows the second robot's path to Mall 2. Panel c) shows a robot at Mall 1 and another robot waiting at Mall 2; the first robot's bubble says 'Another robot is waiting for you across the entrance', with blue arrows indicating communication/handover across the corridor.
+
+**Figure 7 – Example of service handover between robots**
+
+![Figure 8: Spatial information for robot and customer activities. A central 3D architectural scene shows various elements: blue blocks (obstacles), a narrow passage, an automatic door with a knob, a carpeted area, a slope, and tactile paving. Callouts from these elements point to a 'Spatial info' block which feeds into a 'Map registry'. Above this is a 'UNR-PF' bar. To the right, a 'Robot registry' and 'User registry' are shown. A robot and a person in a wheelchair are depicted with speech bubbles. The robot asks about pathway suitability. A yellow bubble notes: 'The user can move across this slope, but not the robot...'. An inset shows an 'Elevator' with a red dot indicating a button.](dfe556fea00682b09a59427aaf72051c_img.jpg)
+
+UNR-PF
+
+Map registry
+Robot registry
+User registry
+
+Spatial info
+
+There are lots of obstacles here!
+
+Width is 1metre here. Can I pass through?
+
+Here's an automatic door. Can I pass through?
+
+There's a nob on this door. Can I open it?
+
+There's a bump here. Can I go over it?
+
+This area is covered by a carpet.
+
+There's a slope at the entrance. Can I pass through?
+
+Studded paving block here. Can I pass through?
+
+Is this pathway suitable for robots? And for the user?
+
+The user can move across this slope, but not the robot...
+
+Elevator
+
+F.747.3(13)\_F08
+
+Figure 8: Spatial information for robot and customer activities. A central 3D architectural scene shows various elements: blue blocks (obstacles), a narrow passage, an automatic door with a knob, a carpeted area, a slope, and tactile paving. Callouts from these elements point to a 'Spatial info' block which feeds into a 'Map registry'. Above this is a 'UNR-PF' bar. To the right, a 'Robot registry' and 'User registry' are shown. A robot and a person in a wheelchair are depicted with speech bubbles. The robot asks about pathway suitability. A yellow bubble notes: 'The user can move across this slope, but not the robot...'. An inset shows an 'Elevator' with a red dot indicating a button.
+
+**Figure 8 – Spatial information for robot and customer activities**
+
+### 8.4 Service execution based on customer attributes
+
+It is required that UNR-PF provides functionalities for selecting appropriate USN nodes based on customer attributes.
+
+An important requirement for UNR-PF is the selection of devices based on customer attributes. Similar to selecting combination of robots based on spatiotemporal availability and robot ability, UNR-PF also needs to consider customer attributes for its robot allocation planning. As for utilizing general customer tendencies, many data mining algorithms and applications have been built and are now actively in use, such as online stores. In such sites, the application servers "remember" what a certain customer chose in the past and would recommend products that are likely to suit the customers. However, for real-world applications using robots, this is a more serious issue. One case that the UNR-PF handles relates to physical disabilities as shown in Figure 8. If a customer can only walk slowly, the robots also need to slow down. If a customer is troubled by steep inclines, the chosen route should consist of flat paths. When a customer requires a wheelchair to move around, a wheelchair robot or a robot that can push wheelchairs shall be used for application execution. As such, walking ability is one clear example to show why customer attributes are important in planning device allocation for service execution. There are, however, a number of such factors, including visual disabilities or impairment in audition. Based on descriptions for each customer, UNR-PF needs to carefully select appropriate devices to make the customer experience as good as possible.
+
+![Diagram illustrating service execution based on customer ability. A database of customer attributes is used to select appropriate robots for different customers.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg)
+
+The diagram illustrates the process of selecting robots based on customer attributes. On the left, a database contains customer information:
+
+- Customer ID: 13
+- Customer ID: 14
+- Customer ID: 15  
+Name: Mr Smith  
+Mobile ability:
+  - Max speed: 1.2 m/sec
+  - Wheelchair use: Yes
+  - Crane use: No
+- Visual ability:
+  - Sight: 0.5
+  - Angle: 10° -- 190° (Left)
+- Hearing ability
+- ...
+
+An orange box labeled "Service style is changed based on customer attributes" receives input from the database and directs the selection of robots. On the right, two scenarios are shown:
+
+- A standing woman (Customer ID 13) is served by a small, upright robot.
+- A man in a wheelchair (Customer ID 15) is served by a larger robot designed to push wheelchairs.
+
+The diagram is labeled F.747.3(13)\_F09 in the bottom right corner.
+
+Diagram illustrating service execution based on customer ability. A database of customer attributes is used to select appropriate robots for different customers.
+
+Figure 9 – Service execution based on customer ability
+
+## 9 Functional model for UNR-PF
+
+A general network robot system consists of three parts as shown in Figure 10:
+
+- 1) Robot service applications
+- 2) UNR-PF
+- 3) Robotic functions
+
+The first robotic function consists of robot service applications that define flow of the service contents, and are typically held and maintained by service providers, using the common interface that UNR-PF provides. The third robotic function consists of various robots that are dedicated to specific capabilities and registered to UNR-PF through the common interface.
+
+The second robotic function is UNR-PF, which is the subject of this Recommendation, which establishes the interaction between the service applications and the robots. The functional model of UNR-PF is shown in the dotted part of Figure 10. This UNR-PF has two layers: the lower layer consists of reusable functional modules that belong to individual robots, and the higher layer manages logic for service contents.
+
+The UNR-PF should be independent of and serve common functions to the other two parts. Once such a common platform is developed and is stable, it will separate robotic functions and services so that the whole robotic system can be developed at lower cost and become more dependable in terms of reusability, scalability and availability.
+
+![Figure 10 – Functional model of UNR-PF. The diagram illustrates the functional model of the UNR-PF (Unified Network Robot Platform Function). It is divided into two main layers: Global PF (Global Platform Function) and Local PF (Local Platform Function). The Global PF layer contains five database functions: Map registry function, User registry function, Operator registry function, Message manager function, and State manager function. The Local PF layer contains five database functions: Map registry function, Robot registry function, Resource manager function, Message manager function, and State manager function. The Global PF layer also includes a Service queue function. The diagram shows the flow of data and control between these functions and the external components. Service applications interact with the Global PF layer through a Common interface. The Global PF layer interacts with the Local PF layer through a Common interface. The Local PF layer interacts with various robotic devices and networks, including ROS (robot operating system), RTM (robotics technologies middleware), Sensor network, and Smart phone. The diagram also shows a Local-PF (Single area platform) and a dotted line indicating further expansion.](5445597cceefaca1ac89e710fe339325_img.jpg)
+
+Figure 10 – Functional model of UNR-PF. The diagram illustrates the functional model of the UNR-PF (Unified Network Robot Platform Function). It is divided into two main layers: Global PF (Global Platform Function) and Local PF (Local Platform Function). The Global PF layer contains five database functions: Map registry function, User registry function, Operator registry function, Message manager function, and State manager function. The Local PF layer contains five database functions: Map registry function, Robot registry function, Resource manager function, Message manager function, and State manager function. The Global PF layer also includes a Service queue function. The diagram shows the flow of data and control between these functions and the external components. Service applications interact with the Global PF layer through a Common interface. The Global PF layer interacts with the Local PF layer through a Common interface. The Local PF layer interacts with various robotic devices and networks, including ROS (robot operating system), RTM (robotics technologies middleware), Sensor network, and Smart phone. The diagram also shows a Local-PF (Single area platform) and a dotted line indicating further expansion.
+
+**Figure 10 – Functional model of UNR-PF**
+
+As such, UNR-PF serves as middleware between services and robotic devices and is composed of two layers of network robot platforms: a local platform (LPF) and a global platform (GPF). LPF is a platform for configuring the robotic system in a single area. GPF is a platform for configuring the robotic system in a wider range of areas that includes a number of LPFs. These platforms serve as a middle-layer between robot service applications and robotic functions. The platform has five database functions and three management functions. The database functions consist of robot registry, operator registry, user registry, map registry and service queue. The management functions consist of a state manager, resource manager and message manager. Each function is detailed below. Refer to Figure 4 in clause 7.2 about concrete message flows among three parts.
+
+UNR-PF contains several registries (database) for managing attributes for robots, operators and robotic service users. These are used for selecting appropriate robots and/or operators on the basis of each user's demands.
+
+### **9.1 Robot registry function**
+
+The robot registry contains information about the robots available in each area, such as their shapes and capabilities as well as their statuses. In addition, functionalities that each robot provides, such as navigation, people detection or face recognition, are stored in the registry as functional profiles. These pieces of information show what kind of service a certain robot can perform, what kind of route the robot can navigate, and whether the robot is available now or in the near future. From this information, UNR-PF can decide what device to allocate for a certain application.
+
+### **9.2 Operator registry function**
+
+Operators for tele-operation of robots are managed in the operator registry. Such operators are often necessary to compensate for the artificial intelligence limitations in the robot. In UNR-PF, operators are treated as one kind of robot. The same selection mechanism works for the operators on respective service application demands based on the information stored in the operator registry.
+
+### **9.3 User registry function**
+
+The user registry holds attributes on each customer who wishes to receive robotic support, as well as a history of services that the customer has used. From these pieces of information, UNR-PF can allocate the robots and operators necessary to provide certain services.
+
+### **9.4 Map registry function**
+
+The map registries in both LPF and GPF are used to improve the linkage between different areas. The map registry of the LPF contains spatial information of the service execution environment, such as the properties of the floor and information about movable zones and keep-out zones. The map registry of the GPF contains the positional relationship among single areas.
+
+### **9.5 Service queue function**
+
+The service queue is a function implemented in both LPF and GPF. This function is used to manage the start of the service. This database contains IDs of the services and their initiation conditions. At first, the service application registers its ID and initiation condition to the service queue in the GPF and the state manager in the GPF registers the ID and condition to the service queue in the appropriate LPF in accordance with the state notification from the LPFs.
+
+### **9.6 State manager function**
+
+The state manager is implemented in both LPF and GPF. This function subscribes to the message manager for the state notifications that are registered in the service queue. When receiving the state notification, the manager determines if the state complies with the start conditions in the service queue. If the state complies with the start condition, the manager sends a message to the service application to start the service.
+
+### **9.7 Resource manager function**
+
+The resource manager is implemented in LPF. When receiving the command message for executing a service application, the resource manager refers to the robot registry, the user registry and the operator registry and reserves the robot suitable for the customer and the operator who can operate the service depending on the situation.
+
+### **9.8 Message manager function**
+
+The message manager is implemented in both LPF and GPF. This function manages the messages exchanged between the service applications and the robotic functions through the common interface. The robotic functions provide the profile of available messages to the message manager.
+
+When receiving the message from the service applications, the message manager refers to the profiles and selects the robotic functions that fit the service application requirements. In LPF, the message manager requires the resource manager to reserve the necessary resources. When receiving the message, i.e., the state notification from the robotic function, the message manager checks the delivery addresses, which are given at the time of the state notification subscription, and forwards the message to the appropriate state manager and/or the service applications.
+
+## Bibliography
+
+- [b-Jung2007] Jung, H.-S. et al., *Unified Ubiquitous Middleware for U-City*, in Proc. ICCIT2007, pp. 2374-2379, 2007.
+- [b-Kamei2012] Kamei, K. et al., *Cloud Network Robotics*, IEEE Network, Vol. 26, No. 3, pp. 28-34, 2012.
+- [b-Kolbe2011] Kolbe, T.H., *Indoor Localization and Tracking supported by 3D Models*, OGC Standards for the Internet of Things – a Workshop, 2011.
+- [b-Nakamura2008] Nakamura, Y. et al., *Framework and service allocation for network robot platform and execution of interdependent services*, Robotics and Autonomous Systems, Vol. 56, pp.831-843, 2008.
+- [b-Nishio2010] Nishio, S. et al., *Robotic Localization Service Standard for Ubiquitous Network Robots*, in Abdellatif, H. ed., Robotics 2010 Current and Future Challenges, pp. 381-400, In-Tech: Vukovar, Croatia, 2010.
+- [b-OGC2011] Open Geospatial Consortium, *OpenGIS City Geography Markup Language (CityGML) Encoding Standard*, version 1.1.0, 2011.
+- [b-OMG2012] Object Management Group, *Robotic Localization Service*, version 1.1, formal/2012-08-01, <http://www.omg.org/spec/RLS/>, 2012.
+- [b-Shiomi2011] Shiomi, M. et al., *Field Trial of a Networked Robot at a Train Station*, Int. J. Social Robotics, Vol. 3, No. 1, pp. 27-40, 2011.
+- [b-Salvini2011] Salvini, P. et al., *Do Service Robots Need a Driving License?*, IEEE Robotics and Automation Magazine, Vol. 18, No. 2, pp. 12-13, 2011.
+- [b-Sanfeliu2008] Sanfeliu, A. et al., *Network Robot Systems*, Robotics and Autonomous Systems, Vol. 56, pp. 793-797, 2008.
+- [b-Sanfeliu2010] Sanfeliu, A. et al., *Decentralized Sensor Fusion for Ubiquitous Networking Robotics in Urban Areas*, Proc. Sensors, pp. 2274-2314, 2010.
+- [b-Sato2011a] Sato, M. et al., *Standardizing Framework for Robotic Services and Functions*, Proc. ICRA Workshop on Robotics Modular Architecture Design and Standardization, 2011.
+- [b-Sato2011b] Sato, M. et al., *The Ubiquitous Network Robot Platform: Common Platform for Continuous Daily Robotic Services*, in Proc. 2011 IEEE/SICE International Symposium on System Integration, pp. 318-323, 2011.
+- [b-Tezuka2006] Tezuka, H. et al., *Robot platform architecture for information sharing and collaboration among multiple networked robots*, Journal of Robotics and Mechatronics, Vol. 18, No. 3, pp. 325-332, 2006.
+
+
+
+
+
+## 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.747.4-201312-I_PDF-E/raw.md

@@ -0,0 +1,616 @@
+
+
+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.747.4**
+
+(12/2013)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Audiovisual services
+
+# --- **Requirements and functional architecture for the open ubiquitous sensor network service platform**
+
+Recommendation ITU-T F.747.4
+
+## 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>                                | <b>F.400–F.499</b> |
+| <b>DIRECTORY SERVICES</b>                                       | <b>F.500–F.549</b> |
+| <b>DOCUMENT COMMUNICATION</b>                                   |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| <b>DATA TRANSMISSION SERVICES</b>                               | <b>F.600–F.699</b> |
+| <b>AUDIOVISUAL SERVICES</b>                                     | <b>F.700–F.799</b> |
+| <b>ISDN SERVICES</b>                                            | <b>F.800–F.849</b> |
+| <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b>                     | <b>F.850–F.899</b> |
+| <b>HUMAN FACTORS</b>                                            | <b>F.900–F.999</b> |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.747.4
+
+# Requirements and functional architecture for the open ubiquitous sensor network service platform
+
+## Summary
+
+Recommendation ITU-T F.747.4 defines the requirements and functional architecture for the open ubiquitous sensor network (USN) service platform.
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                      |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------------|
+| 1.0     | ITU-T F.747.4  | 2013-12-14 | 16          | <a href="http://handle.itu.int/11.1002/1000/12051-en">11.1002/1000/12051-en</a> |
+
+## Keywords
+
+Open USN service, semantic data, USN middleware, USN resource.
+
+---
+
+\* 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 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 2014
+
+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 .....                                                          | 2           |
+| 6 | Open USN service description and characteristics.....                      | 2           |
+| 7 | Requirements for the open USN service platform.....                        | 4           |
+|   | 7.1 Requirements to communicate with heterogeneous USN middleware .....    | 4           |
+|   | 7.2 Requirements of the open USN service platform.....                     | 4           |
+|   | 7.3 Requirements for linking the LOD.....                                  | 4           |
+|   | 7.4 Requirements for applications .....                                    | 4           |
+|   | 7.5 Requirements for USN resources and sensed data/semantic data.....      | 4           |
+| 8 | Functional architecture of the open USN service framework .....            | 5           |
+|   | 8.1 Functional architecture .....                                          | 5           |
+|   | 8.2 Functional entities .....                                              | 6           |
+|   | Appendix I – Information flow in the open USN service framework .....      | 9           |
+|   | I.1 USN resource registration .....                                        | 9           |
+|   | I.2 Sensed data/semantic data access from Semantic USN repository FE ..... | 10          |
+|   | I.3 Sensed data access from USN resources .....                            | 11          |
+|   | Appendix II – Use cases of the open USN service platform .....             | 14          |
+|   | II.1 Traffic information service using the open USN service platform ..... | 14          |
+|   | Bibliography.....                                                          | 17          |
+
+# Introduction
+
+There is a large number of middleware available for sensor networks and different kinds of ubiquitous sensor network (USN) middleware that may be deployed. Furthermore, USN services may utilize widely distributed sensors or sensor networks through different USN middleware. In a widely distributed environment, USN applications need to know of the various USN middleware, sensors and sensor networks used. For example, if an application wants to get the current temperature in Geneva, the application should have information specifying which USN middleware and which sensors or sensor networks can provide the data requested and how they can provide the data.
+
+The open USN service platform aims to provide unified access to USN resources and sensed data/semantic data through heterogeneous USN middleware, thereby enabling USN applications to take full advantage of the USN capabilities. It allows providers, users and application developers to provide USN resources, use USN services, or develop USN applications without needing to have specific knowledge about the USN middleware and sensors, or how to access specific sensor networks. The main purpose of the open USN service platform defined in this Recommendation is to provide:
+
+- easy access to and use of the global USN resources and sensed data/semantic data;
+- easy connection of USN resources; and
+- easy development and distribution of various applications.
+
+# Recommendation ITU-T F.747.4
+
+# Requirements and functional architecture for the open ubiquitous sensor network service platform
+
+# 1 Scope
+
+The objective of this Recommendation is to define the open ubiquitous sensor network (USN) service platform and provide requirements and functional architecture for the open USN service platform.
+
+The scope of this Recommendation includes:
+
+- concept of the open USN service platform;
+- requirements for the open USN service platform;
+- functional architecture of the open USN service platform;
+- functional entities of the open USN service platform.
+
+# 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), <i>Service description and requirements for ubiquitous sensor network middleware</i> .                                 |
+| [ITU-T Y.2201] | Recommendation ITU-T Y.2201 (2009), <i>Requirements and capabilities for ITU-T NGN</i> .                                                                  |
+| [ITU-T Y.2221] | Recommendation ITU-T Y.2221 (2010), <i>Requirements for support of ubiquitous sensor network (USN) applications and services in the NGN environment</i> . |
+
+# 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+- 3.1.1 context awareness** [ITU-T Y.2201]: A capability to determine or influence a next action in telecommunication or process by referring to the status of relevant entities, which form a coherent environment as a context.
+- 3.1.2 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.3 sensor network** [ITU-T Y.2221]: A network comprised of interconnected sensor nodes exchanging sensed data by wired or wireless communication.
+- 3.1.4 sensor node** [ITU-T Y.2221]: A device consisting of sensor(s) and optional actuator(s) with capabilities of sensed data processing and networking.
+
+**3.1.5 sensed data** [ITU-T F.744]: Data sensed by a sensor that is attached to a specific sensor node.
+
+NOTE – The sensed data are collected from USN resources via USN middleware and stored in a sensed data repository.
+
+**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 anytime, and where the information is generated by using context awareness.
+
+**3.1.7 USN middleware** [ITU-T Y.2221]: A set of logical functions to support USN applications and services.
+
+### **3.2 Terms defined in this Recommendation**
+
+This Recommendation defines the following terms:
+
+**3.2.1 metadata:** Description of USN resources which include types of operations supported, attributes for those operations, etc.
+
+**3.2.2 open USN service:** USN service which provides unified access to USN resources and sensed data/semantic data through heterogeneous USN middleware.
+
+**3.2.3 semantic data:** Data translated into resource description framework (RDF) [b-RDF] form from metadata of USN resources and sensed data, and data processed by the Semantic inference functional entity (FE) from data represented in RDF form. These data are stored in a Semantic data repository.
+
+**3.2.4 USN resource:** An entity that provides a USN service including sensor, actuator, sensor node, sensor network and gateway.
+
+# **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|        |                                        |
+|--------|----------------------------------------|
+| API    | Application Programming Interface      |
+| FE     | Functional Entity                      |
+| LOD    | Linked Open Data                       |
+| RDF    | Resource Description Framework         |
+| REST   | Representational State Transfer        |
+| SPARQL | SPARQL Protocol and RDF Query Language |
+| URI    | Uniform Resource Identifier            |
+| USN    | Ubiquitous Sensor Network              |
+
+# **5 Conventions**
+
+None.
+
+# **6 Open USN service description and characteristics**
+
+USN services require USN applications to have knowledge of USN middleware and sensors or sensor networks in order to access USN resources. For example, heterogeneous USN middleware is not easily accessed by applications since each USN middleware may have proprietary application programming interfaces (APIs) which may hinder access to various USN resources attached to the USN middleware.
+
+Even when applications have access to multiple USN middleware entities, the applications must search, collect, analyse and process the sensed data themselves.
+
+These limitations can be overcome by providing a unified access method for USN resources and sensed data/semantic data via heterogeneous USN middleware.
+
+Figure 6-1 shows the traditional USN service framework and the open USN service framework.
+
+![Figure 6-1: Comparison of Traditional and Open USN service frameworks.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+The diagram illustrates two architectural models for USN services. On the left, the 'Traditional USN service framework' shows a direct, many-to-many connection where multiple 'Sensor resource' nodes (circles) are linked to multiple 'USN middleware' nodes (squares), which in turn are linked to multiple 'Application' nodes (circles). On the right, the 'Open USN service framework' introduces an 'Open USN service platform' (a central square). In this model, all 'Sensor resource' nodes connect to their respective 'USN middleware' nodes, and all 'USN middleware' nodes connect to a single 'Open USN service platform'. This platform then acts as a central hub, connecting to all 'Application' nodes. This centralization simplifies the access for applications.
+
+Figure 6-1: Comparison of Traditional and Open USN service frameworks.
+
+**Figure 6-1 – Traditional USN service framework and open USN service framework**
+
+In the traditional USN service framework, each application needs to know how to access heterogeneous USN middleware and which USN resources should be accessed. In the open USN service framework, each application does not need to know how to access heterogeneous USN middleware nor which USN resources should be accessed.
+
+Figure 6-2 shows heterogeneous USN middleware access provided by the open USN service platform.
+
+![Figure 6-2: Heterogeneous USN middleware access through the open USN service platform.](0b87abe67b21a93777287649c33e755d_img.jpg)
+
+This diagram details the data flow between 'Sensor resource', 'USN middleware', 'Open USN service platform', and 'Application' components. 
+ 1. A 'Sensor resource' (circle) sends '3 Sensed data collection' to a 'USN middleware' (square).
+ 2. The 'USN middleware' sends '2 Sensed data request' to the 'Open USN service platform' (square).
+ 3. The 'Open USN service platform' sends '1 Service request' to an 'Application' (circle).
+ 4. The 'Application' sends '5 Service response' back to the 'Open USN service platform'.
+ 5. The 'Open USN service platform' sends '4 Sensed data reply' back to the 'USN middleware'.
+ 6. The 'USN middleware' then sends '3' (representing the sensed data) to the 'Sensor resource'.
+ This sequence shows how the platform mediates between the application and the heterogeneous middleware, abstracting the underlying sensor details.
+
+Figure 6-2: Heterogeneous USN middleware access through the open USN service platform.
+
+**Figure 6-2 – Heterogeneous USN middleware access through the open USN service platform**
+
+In the open USN service framework, a USN application only needs to send requests to the open USN service platform; the remaining processing is done by the platform itself. The open USN service platform converts a request from each USN application into a specific request for different USN middleware.
+
+The ultimate goal of the open USN service platform is to provide the application with the following services:
+
+- easy access to and use of global USN resources and sensed data/semantic data;
+- easy connection of USN resources;
+- easy development and distribution of various applications.
+
+# **7 Requirements for the open USN service platform**
+
+The following are the requirements for the open USN service platform.
+
+## **7.1 Requirements to communicate with heterogeneous USN middleware**
+
+- It is required to provide an open interface for heterogeneous USN middleware to provide the sensed data and metadata received from USN resources.
+- USN resources and semantic data are required to be identified by a universal resource identifier (URI).
+- URIs for USN resources are required to be dynamically assigned when the USN resources are registered to the open USN service platform.
+- It is required to provide open interface for accessing heterogeneous USN middleware.
+
+### **7.2 Requirements of the open USN service platform**
+
+- USN resource management is required according to proper management policies on authentication, authorization and access rights.
+- The characteristics and status of USN resources are required to be managed.
+- It is required to provide functionality of inheritance and binding of USN middleware management policy.
+- It is recommended to manage a logical group of USN resources according to application service requests.
+- It is recommended to provide inference functions to derive the context data by user rules.
+
+### **7.3 Requirements for linking the LOD**
+
+- It is required to be accessed by external linked open data (LOD) [b-LOD] by assigning a unique URI to each USN resource and semantic data.
+- It is required to access the external LOD via the web.
+
+### **7.4 Requirements for applications**
+
+- It is required to provide an open protocol, such as representational state transfer (REST), for applications.
+- It is required to provide an open interface to services and applications for the combination of existing applications.
+
+### **7.5 Requirements for USN resources and sensed data/semantic data**
+
+- Metadata of USN resources and semantic data are required to be represented in RDF [b-RDF] format.
+
+- It is required to provide functions to store, query, modify and delete data in RDF form in the repository.
+- It is required to provide functions to search USN resources and sensed data/semantic data by analysing the intention of service requests from an application.
+- It is required to support a standard query language such as SPARQL Protocol and RDF Query Language (SPARQL) [b-SPARQL].
+- It is recommended to manage access for USN resources and sensed data/semantic data according to proper access rights.
+
+# 8 Functional architecture of the open USN service framework
+
+### 8.1 Functional architecture
+
+Figure 8-1 shows the functional architecture of the open USN service framework.
+
+![Functional architecture of the open USN service framework diagram](d26959f4514c26ca19c3d6f00da85956_img.jpg)
+
+The diagram illustrates the functional architecture of the open USN service framework. It is structured as follows:
+
+- Application:** The top-level component that interacts with the service platform.
+- Open USN service platform:** A large container box enclosing the core services.
+  - Application support FE:** The first layer within the platform, connected to the Application.
+  - Semantic query FE:** The second layer, connected to the Application support FE.
+  - Internal Components:**
+    - LOD linking FE:** Connected to the Semantic query FE and a **LOD** (Linked Open Data) cloud icon.
+    - Semantic inference FE:** Connected to the Semantic data repository.
+    - Semantic USN repository FE:** Contains the **Semantic data repository** and the **Sensed data repository**.
+    - Resource management FE:** Connected to the Semantic data repository and the Adaptation FE.
+  - Adaptation FE:** A layer at the bottom of the platform containing multiple **Adaptation FE<sub>1</sub>**, **Adaptation FE<sub>2</sub>**, ..., **Adaptation FE<sub>n</sub>** components.
+- USN middleware:** A row of **USN middleware<sub>1</sub>**, **USN middleware<sub>2</sub>**, ..., **USN middleware<sub>n</sub>** components, each connected to an Adaptation FE.
+- Sensor or sensor network:** The bottom layer, represented by a dotted line containing multiple sensor icons, connected to the USN middleware.
+
+Arrows indicate the flow of data and control between these components.
+
+Functional architecture of the open USN service framework diagram
+
+**Figure 8-1 – Functional architecture of the open USN service framework**
+
+The functional architecture of the open USN service framework consists of the open USN service platform and heterogeneous USN middleware. The open USN service platform consists of seven functional entities (FEs): Application support FE, LOD linking FE, Semantic inference FE, Resource management FE, Semantic USN repository FE, Semantic query FE and Adaptation FE.
+
+The heterogeneous USN middleware entities are integrated into the open USN service platform through the Adaptation FEs; furthermore, the metadata of USN resources and semantic data are shared with the other services through LOD linking FE.
+
+### **8.2 Functional entities**
+
+#### **8.2.1 Application support FE**
+
+The Application support FE provides the functions which enable USN applications to obtain open USN services and/or the sensed data/semantic data from the open USN service platform.
+
+The Application support FE also supports the functions that allow the establishment or maintenance of connections or disconnections according to the type of data request, and access control to handle access rights for user authentication and the use of services.
+
+#### **8.2.2 LOD linking FE**
+
+The LOD linking FE provides the functions that enable users to access the metadata of USN resources and semantic data in the open USN service platform via the web. It allows linking external LOD with the metadata of USN resources and semantic data in the open USN service platform.
+
+The LOD linking FE also supports the interface for querying the metadata of USN resources and semantic data from the LOD, and the functions which allow the application and management of policies that include criteria about selection and publication of data for the LOD.
+
+#### **8.2.3 Semantic inference FE (optional)**
+
+The Semantic inference FE provides the inference functions based on the information described in the ontology schema and user rules by using the data stored in the Semantic USN repository FE.
+
+Through the inference functions, the original sensed data in the sensed data repository are processed into semantic data, such as context data, and stored in the semantic data repository. The semantic data repository is updated with the inferred data either periodically or on-demand. Furthermore, it provides the functions to compose different kinds of patterns and levels for inference.
+
+#### **8.2.4 Resource management FE**
+
+The Resource management FE provides the functions that issue and manage the URIs of USN resources and semantic data. It also provides the functions that manage the mapping relations with the address of the USN resource. Further, the Resource management FE supports the functions that enable USN resources to be automatically registered in the open USN service platform when a USN resource is connected to a network such as the Internet, and enables applications to obtain and utilize information about USN resources.
+
+The Resource management FE provides the functions that enable USN resources to actively register their status and connection information. By using this information, the open USN service platform will support network connection and mobility of USN resources.
+
+Therefore, the Resource management FE can support plug and play functions which enable the open USN service platform to dynamically use USN resources which can automatically connect to the open USN service platform and register their own status and property information.
+
+The Resource management FE provides the functions needed to search URIs of USN resources for performing queries that can provide necessary information for requests from applications.
+
+In some cases, the Resource management FE can provide the functions necessary to configure and manage a logical group on USN resources for satisfying application service requests.
+
+The Resource management FE may perform the functions to create a resource group according to application service requests and to manage lists of USN resources that belong to the resource group. Also, it supports the functions needed to create, maintain and manage information such as the resource group purpose, makers, control with rights, etc. It provides the functions necessary to manage the lifecycle of each resource group according to the duration of service.
+
+#### **8.2.5 Semantic USN repository FE**
+
+The Semantic USN repository FE includes the functions for converting metadata of USN resources and sensed data into RDF form. The Semantic USN repository FE includes two different repositories: Semantic data repository and Sensed data repository.
+
+The Semantic USN repository FE stores the metadata of USN resources and semantic data in the Semantic data repository in RDF form. Also, the Semantic USN repository FE stores sensed data collected from USN middleware in the Sensed data repository.
+
+It also provides query functions for searching, modifying and deleting stored data, as well as for inserting new data.
+
+#### **8.2.6 Semantic query FE**
+
+The Semantic query FE performs the functions that handle queries to USN middleware, Semantic USN repository FE and Resource management FE for providing responses to application information requests. It consists of a query analyser function, middleware query function, SPARQL query function and URI request query function.
+
+The query analyser function creates queries by analysing the intentions of requests made by the applications, translates the results of each query process according to application message specifications, and delivers the translated data to the applications through the Application support FE. It classifies the requests from the applications into a query to the USN middleware, a query to the Semantic USN repository FE and a query to the Resource management FE. The query to the USN middleware, which requests the sensed data to the USN resources through the USN middleware, is created from metadata of USN resources according to types and attributes of operations supported. The query to the Semantic USN repository FE, which requests the metadata of USN resources and semantic data to the Semantic USN repository FE, is created by translating the queries that the applications request into SPARQL. The query to the Resource management FE, which requests the URIs of corresponding USN resources to the Resource management FE, is created for performing queries to the USN middleware or the Semantic USN repository FE that can provide the necessary information for satisfying requests from applications.
+
+The middleware query function performs the functions to send queries to the USN middleware, and to collect the resulting data from the USN middleware through the Adaptation FE: it also manages the query status of each query to the USN middleware created from the query analyser function. The data, received temporarily or periodically from the USN middleware, are stored in the Semantic USN repository FE by the Adaptation FE. However, in some cases, such as for a real-time sensed data request, the sensed data can be directly sent to the query analyser function.
+
+The SPARQL query function performs the functions to simultaneously handle many SPARQL queries created by the query analyser function, to produce the outcome of each query from the Semantic USN repository FE and to deliver these to the query analyser function.
+
+The URI request query function performs the functions to send URI request queries to the Resource management FE, receive the URIs of corresponding USN resources from the Resource management FE and deliver them to the query analyser function.
+
+#### **8.2.7 Adaptation FE**
+
+Adaptation FE provides the functions to handle the protocols and messages for setting up connections with USN middleware and delivering queries and commands. It works as an interface between the open USN service platform and heterogeneous USN middleware for processing the corresponding protocols and messages for the respective USN middleware.
+
+It supports the message translation function to translate the data from/to heterogeneous USN middleware according to proper message specifications to deal with in the open USN service platform and the respective USN middleware. It also provides the message routing function to deliver the translated data to corresponding FEs (Semantic USN repository FE, Resource management FE and Semantic query FE) of the open USN service platform in order to process requests.
+
+# Appendix I
+
+## Information flow in the open USN service framework
+
+(This appendix does not form an integral part of this Recommendation.)
+
+This appendix describes the information flow related to the operation of the open USN service framework that includes USN resource registration, sensed data/semantic data access from Semantic USN repository FE and USN resources.
+
+## I.1 USN resource registration
+
+Figure I.1 shows the information flow describing how to register a USN resource into the open USN service platform.
+
+![Diagram of information flow for USN resource registration.](9ae17964ddd9b814c7d905b1af2fddf2_img.jpg)
+
+The diagram illustrates the information flow for USN resource registration within the Open USN service platform. The components and their interactions are as follows:
+
+- Application**: Interacts with the **Application support FE** via a bidirectional arrow.
+- Open USN service platform**: Contains the following components:
+  - Application support FE**: Interacts with the **Semantic query FE** via a bidirectional arrow.
+  - Semantic query FE**: Interacts with the **Semantic USN repository FE** and the **Resource management FE** via bidirectional arrows.
+  - Semantic USN repository FE**: Contains a **Semantic data repository** and a **Sensed data repository**. It interacts with the **LOD linking FE** and **Semantic inference FE** via bidirectional arrows.
+  - Resource management FE**: Interacts with the **Semantic USN repository FE** and the **Adaptation FE** via bidirectional arrows.
+  - Adaptation FE**: Contains multiple **Adaptation FE<sub>1</sub>**, **Adaptation FE<sub>2</sub>**, ..., **Adaptation FE<sub>n</sub>**. It interacts with the **USN middleware<sub>1</sub>**, **USN middleware<sub>2</sub>**, ..., **USN middleware<sub>n</sub>** via bidirectional arrows.
+- USN middleware<sub>1</sub>**, **USN middleware<sub>2</sub>**, ..., **USN middleware<sub>n</sub>**: Interact with the **Sensor or sensor network** via bidirectional arrows.
+- Sensor or sensor network**: Represented by a circle at the bottom.
+
+Numbered red arrows indicate specific steps in the registration process:
+
+- 1: From **Sensor or sensor network** to **USN middleware<sub>2</sub>**.
+- 2: From **USN middleware<sub>2</sub>** to **Adaptation FE<sub>2</sub>**.
+- 3: From **Adaptation FE<sub>2</sub>** to **Resource management FE**.
+- 4: From **Resource management FE** to **Semantic USN repository FE**.
+- 5: From **Resource management FE** to **Semantic query FE**.
+- 6: From **Adaptation FE<sub>2</sub>** to **Semantic USN repository FE**.
+
+Diagram of information flow for USN resource registration.
+
+Figure I.1 – Information flow of USN resource registration
+
+- (1) The USN resource requests the USN middleware to register its information to the open USN service platform.
+- (2) The USN middleware sends a request to the open USN service platform through the Adaptation FE.
+- (3) The Adaptation FE sends the request message to the Resource management FE.
+- (4) The Resource management FE issues the URI of the USN resource and requests the Semantic USN repository FE to store the URI and metadata of the USN resource.
+- (5) The Resource management FE returns the result of the registration to the Adaptation FE.
+- (6) The Adaptation FE returns the result to the USN middleware.
+
+## I.2 Sensed data/semantic data access from Semantic USN repository FE
+
+Figure I.2 shows the information flows describing how to access sensed data/semantic data stored in the Semantic USN repository FE.
+
+![Figure I.2: Information flow of accessing sensed data/semantic data from Semantic USN repository FE. The diagram illustrates the architecture and data flow between various components. At the top is the 'Application'. Below it is the 'Open USN service platform' containing 'Application support FE', 'Semantic query FE', 'LOD linking FE', 'Semantic inference FE', 'Semantic USN repository FE' (which includes 'Semantic data repository' and 'Sensed data repository'), and 'Resource management FE'. At the bottom is the 'Adaptation FE' (containing 'Adaptation FE1', 'Adaptation FE2', ..., 'Adaptation FE_n') and 'USN middleware' (containing 'USN middleware1', 'USN middleware2', ..., 'USN middleware_n'). A 'Sensor or sensor network' is at the very bottom. Numbered red arrows indicate specific information flows: 1 (Sensor to Sensed data repository), 2 (USN middleware to Application support FE), 3 (Application support FE to Semantic query FE), 4 (Semantic query FE to Resource management FE), 5 (Resource management FE to Semantic data repository), 6 (Semantic data repository to Resource management FE), 7 (Resource management FE to Semantic query FE), 8 (Semantic query FE to Semantic USN repository FE), 9 (Semantic USN repository FE to Semantic query FE), 10 (Application support FE to Semantic query FE), and 11 (Application support FE to Application). Black arrows show other system interactions.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg)
+
+Figure I.2: Information flow of accessing sensed data/semantic data from Semantic USN repository FE. The diagram illustrates the architecture and data flow between various components. At the top is the 'Application'. Below it is the 'Open USN service platform' containing 'Application support FE', 'Semantic query FE', 'LOD linking FE', 'Semantic inference FE', 'Semantic USN repository FE' (which includes 'Semantic data repository' and 'Sensed data repository'), and 'Resource management FE'. At the bottom is the 'Adaptation FE' (containing 'Adaptation FE1', 'Adaptation FE2', ..., 'Adaptation FE\_n') and 'USN middleware' (containing 'USN middleware1', 'USN middleware2', ..., 'USN middleware\_n'). A 'Sensor or sensor network' is at the very bottom. Numbered red arrows indicate specific information flows: 1 (Sensor to Sensed data repository), 2 (USN middleware to Application support FE), 3 (Application support FE to Semantic query FE), 4 (Semantic query FE to Resource management FE), 5 (Resource management FE to Semantic data repository), 6 (Semantic data repository to Resource management FE), 7 (Resource management FE to Semantic query FE), 8 (Semantic query FE to Semantic USN repository FE), 9 (Semantic USN repository FE to Semantic query FE), 10 (Application support FE to Semantic query FE), and 11 (Application support FE to Application). Black arrows show other system interactions.
+
+**Figure I.2 – Information flow of accessing sensed data/semantic data from Semantic USN repository FE**
+
+- (1) The sensed data via the USN middleware from USN resources are periodically or continuously stored in the Semantic USN repository FE. The Semantic inference FE converts sensed data into semantic data periodically or on-demand.
+- (2) The Application requests the sensed data/semantic data from the open USN service platform through the Application support FE.
+- (3) The Application support FE sends a request message to the Semantic query FE.
+- (4) The Semantic query FE requests from the Resource management FE the URIs of USN resources that can be used for performing queries that will provide the necessary information to satisfy the Application request.
+- (5) The Resource management FE sends this request message to the Semantic USN repository FE.
+- (6) The Resource management FE receives the URIs of corresponding USN resources from the Semantic USN repository FE.
+- (7) The Resource management FE returns the URIs of corresponding USN resources to the Semantic query FE.
+- (8) The Semantic query FE queries the Semantic USN repository FE for the sensed data/semantic data related to the returned URIs.
+- (9) The Semantic query FE receives the sensed data/semantic data related to the returned URIs in the Semantic USN repository FE.
+- (10) The Semantic query FE sends the sensed data/semantic data to the Application support FE.
+- (11) The Application support FE sends the sensed data/semantic data to the Application.
+
+## **I.3 Sensed data access from USN resources**
+
+Figure I.3 shows the information flows describing how to access sensed data directly from USN resources in real-time.
+
+![Figure I.3 – Information flow of accessing sensed data from USN resources. The diagram illustrates the architecture and data flow for accessing sensed data from USN resources. At the top is the 'Application' box. Below it is the 'Open USN service platform' container, which includes 'Application support FE', 'Semantic query FE', 'Semantic USN repository FE' (containing 'Semantic data repository' and 'Sensed data repository'), 'Resource management FE', 'Adaptation FE' (containing 'Adaptation FE1', 'Adaptation FE2', ..., 'Adaptation FE_n'), 'LOD linking FE', and 'Semantic inference FE'. Below the platform are 'USN middleware1', 'USN middleware2', ..., 'USN middleware_n', and at the bottom is the 'Sensor or sensor network'. Numbered arrows indicate the flow: (1) Application to Application support FE; (2) Application support FE to Semantic query FE; (3) Semantic query FE to Resource management FE; (4) Resource management FE to Semantic USN repository FE; (5) Semantic USN repository FE to Resource management FE; (6) Resource management FE to Semantic query FE; (7) Semantic query FE to USN middleware_n; (8) USN middleware_n to Sensor or sensor network; (9) Semantic query FE to Application support FE; (10) Application support FE to Application. Black arrows show internal platform connections, and red arrows show the numbered external flows.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg)
+
+Figure I.3 – Information flow of accessing sensed data from USN resources. The diagram illustrates the architecture and data flow for accessing sensed data from USN resources. At the top is the 'Application' box. Below it is the 'Open USN service platform' container, which includes 'Application support FE', 'Semantic query FE', 'Semantic USN repository FE' (containing 'Semantic data repository' and 'Sensed data repository'), 'Resource management FE', 'Adaptation FE' (containing 'Adaptation FE1', 'Adaptation FE2', ..., 'Adaptation FE\_n'), 'LOD linking FE', and 'Semantic inference FE'. Below the platform are 'USN middleware1', 'USN middleware2', ..., 'USN middleware\_n', and at the bottom is the 'Sensor or sensor network'. Numbered arrows indicate the flow: (1) Application to Application support FE; (2) Application support FE to Semantic query FE; (3) Semantic query FE to Resource management FE; (4) Resource management FE to Semantic USN repository FE; (5) Semantic USN repository FE to Resource management FE; (6) Resource management FE to Semantic query FE; (7) Semantic query FE to USN middleware\_n; (8) USN middleware\_n to Sensor or sensor network; (9) Semantic query FE to Application support FE; (10) Application support FE to Application. Black arrows show internal platform connections, and red arrows show the numbered external flows.
+
+**Figure I.3 – Information flow of accessing sensed data from USN resources**
+
+- (1) The Application requests the sensed data from the open USN service platform through the Application support FE.
+- (2) The Application support FE sends a request message to the Semantic query FE.
+- (3) The Semantic query FE requests from the Resource management FE the URIs of USN resources that can be used for performing queries that will provide the necessary information to satisfy the request from the Application.
+- (4) The Resource management FE sends this request message to the Semantic USN repository FE.
+- (5) The Resource management FE receives the URIs of corresponding USN resources from the Semantic USN repository FE.
+- (6) The Resource management FE returns the URIs of corresponding USN resources to the Semantic query FE.
+- (7) The Semantic query FE queries via the USN middleware the sensed data of the corresponding USN resources using the returned URIs.
+
+- (8) The Semantic query FE receives the sensed data from corresponding USN resources via the USN middleware.
+- (9) The Semantic query FE sends the sensed data to the Application support FE.
+- (10) The Application support FE sends the sensed data to the Application.
+
+# Appendix II
+
+## Use cases of the open USN service platform
+
+(This appendix does not form an integral part of this Recommendation.)
+
+This appendix describes a use case for providing traffic information service using the open USN service platform.
+
+## II.1 Traffic information service using the open USN service platform
+
+Most traffic information services provide information related to the driving of vehicles, such as traffic reports, road conditions and route guides (navigation) based on distance data. If various data related to the driving of vehicles are obtained in real-time, more valuable traffic information services could be provided. For example, recommended routes could be served more usefully by utilizing various data in real-time such as vehicle speed and condition data, weather data, traffic light data, personal schedule, and so on. Figure II.1 shows a use case that illustrates providing recommended routes in the traffic information service.
+
+For this service, the open USN service platform could collect the following data:
+
+- vehicle speed and condition (e.g., parts, tires, fuel) data from several sensors installed within the vehicle,
+- weather data from weather sensors installed nationwide,
+- traffic light data from sensor nodes that collect the state of traffic lights,
+- personal scheduling data stored in a smart phone that can be used as a sensor node or gateway which delivers data in a smart phone to destination.
+
+These data can be collected by the methods used to handle the respective messages and protocols through heterogeneous USN middleware, such as the open geospatial consortium (OGC) sensor web enablement (SWE) [b-SWE] or USN middleware described in [ITU-T F.744]. In the open USN service platform, the data collected from heterogeneous USN middleware are translated into proper message specifications by the message translation function of the Adaptation FE. The translated data are delivered to the corresponding FEs (Semantic USN repository FE, Resource management FE and Semantic query FE) of the open USN service platform in order to process requests by the message routing function of the Adaptation FE. The above data are stored in the Semantic USN repository FE in RDF form.
+
+Using the Semantic inference FE, data with semantics such as the following context data are created and provided to users:
+
+- recommended routes with good weather conditions and without traffic congestion, based on weather and speed data collected from vehicles on route to the destination;
+- recommended routes to reach a meeting place in time for appointments according to personal schedule and vehicle fuel-level data based on traffic light and speed data collected from vehicles on route to the destination
+
+![Architecture diagram of a Traffic information service using the open USN service platform. The diagram shows a multi-layered system. At the top is the 'Traffic information service' represented by a mobile app interface. Below it is the 'Open USN service platform' which contains several functional layers: 'Application support FE' at the top, followed by 'Semantic query FE'. Below these are the 'Semantic USN repository FE' and 'Resource management FE'. The 'Semantic USN repository FE' contains a 'Semantic data repository' which is linked to a 'Sensed data repository' and interacts with 'LOD linking FE' and 'Semantic inference FE'. At the bottom of the platform is the 'Adaptation FE' layer, which includes 'SWE Adaptation FE' and 'F.744 Adaptation FE'. External sensors interact with these layers: 'Sensors installed within vehicles' and 'Weather sensors' send 'InsertObservation' data to the 'SWE' block, which then feeds into the 'SWE Adaptation FE'. 'Sensor nodes' (like traffic lights) send 'SensorQuery' to the 'F.744' block, which feeds into the 'F.744 Adaptation FE'. The 'F.744' block also sends 'SensingValueReport' back to the 'F.744 Adaptation FE'. The 'SWE' block also sends 'GetObservation' data to the 'Semantic query FE'. The 'F.744' block sends 'SensingValueReport' data to the 'Resource management FE'. The 'Semantic query FE' sends data to the 'Application support FE', which finally provides the 'Traffic information service'.](5b8a756d9a71c35f17db8bcb90b438a3_img.jpg)
+
+Traffic information service
+
+Open USN service platform
+
+Application support FE
+
+Semantic query FE
+
+Semantic USN repository FE
+
+Resource management FE
+
+Semantic data repository
+
+Sensed data repository
+
+LOD linking FE
+
+Semantic inference FE
+
+Adaptation FE
+
+SWE Adaptation FE
+
+...
+
+F.744 Adaptation FE
+
+GetObservation
+
+InsertObservation
+
+SensorQuery
+
+SensingValueReport
+
+SWE
+
+F.744
+
+InsertObservation
+
+SensorQuery
+
+SensingValueReport
+
+Sensors installed within vehicles to collect vehicle speed and condition data
+
+Weather sensors
+
+Sensor node to collect the state of traffic light
+
+Sensor node or gateway which delivers data in smart phone to destination
+
+Architecture diagram of a Traffic information service using the open USN service platform. The diagram shows a multi-layered system. At the top is the 'Traffic information service' represented by a mobile app interface. Below it is the 'Open USN service platform' which contains several functional layers: 'Application support FE' at the top, followed by 'Semantic query FE'. Below these are the 'Semantic USN repository FE' and 'Resource management FE'. The 'Semantic USN repository FE' contains a 'Semantic data repository' which is linked to a 'Sensed data repository' and interacts with 'LOD linking FE' and 'Semantic inference FE'. At the bottom of the platform is the 'Adaptation FE' layer, which includes 'SWE Adaptation FE' and 'F.744 Adaptation FE'. External sensors interact with these layers: 'Sensors installed within vehicles' and 'Weather sensors' send 'InsertObservation' data to the 'SWE' block, which then feeds into the 'SWE Adaptation FE'. 'Sensor nodes' (like traffic lights) send 'SensorQuery' to the 'F.744' block, which feeds into the 'F.744 Adaptation FE'. The 'F.744' block also sends 'SensingValueReport' back to the 'F.744 Adaptation FE'. The 'SWE' block also sends 'GetObservation' data to the 'Semantic query FE'. The 'F.744' block sends 'SensingValueReport' data to the 'Resource management FE'. The 'Semantic query FE' sends data to the 'Application support FE', which finally provides the 'Traffic information service'.
+
+**Figure II.1 – Traffic information service using the open USN service platform**
+
+Based on these data, the following scenario can be considered:
+
+- The application requests information from the open USN service platform for finding the optimal route – with good weather conditions without traffic jams – to a destination.
+- The open USN service platform collects relevant data from various sensors through various USN middleware including weather sensors and sensors installed within vehicles.
+
+- The open USN service platform provides the information which is needed by the application to determine the optimal route to the destination.
+- The application generates the recommended route to the destination based on the information provided from the open USN service platform.
+
+# Bibliography
+
+- [b-LOD] W3C Working Group Note 27 June 2013, Linked Data Glossary, *Linked Open Data (LOD)*, <<http://www.w3.org/TR/ld-glossary/#linked-open-data>>
+- [b-RDF] W3C RDF Working Group (2004-02-10), *Resource Description Framework (RDF)*, <<http://www.w3.org/2001/sw/wiki/RDF>>
+- [b-SPARQL] W3C Recommendation 15 January 2008, *SPARQL Query Language for RDF*, <<http://www.w3.org/TR/rdf-sparql-query>>
+- [b-SWE] Open Geospatial Consortium (OGC), Sensor Web Enablement Domain Working Group (DWG), *Sensor Web Enablement*, <<http://www.opengeospatial.org/projects/groups/sensorwebdwg>>
+
+
+
+
+
+## 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.747.5-201401-I_PDF-E/raw.md

@@ -0,0 +1,578 @@
+
+
+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.747.5
+
+(01/2014)
+
+SERIES F: NON-TELEPHONE TELECOMMUNICATION  
+SERVICES
+
+Audiovisual services
+
+---
+
+**Requirements and functional architecture of an  
+automatic location identification system for  
+ubiquitous sensor network (USN) applications  
+and services**
+
+Recommendation ITU-T F.747.5
+
+![ITU logo](84a1d09fb489061482111515543b60dc_img.jpg)
+
+The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with a red lightning bolt striking it, and the text "ITU" in blue, with "International Telecommunication Union" in smaller blue text below it.
+
+ITU logo
+
+# 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>                                | <b>F.400–F.499</b> |
+| <b>DIRECTORY SERVICES</b>                                       | <b>F.500–F.549</b> |
+| <b>DOCUMENT COMMUNICATION</b>                                   |                    |
+| Document communication                                          | F.550–F.579        |
+| Programming communication interfaces                            | F.580–F.599        |
+| <b>DATA TRANSMISSION SERVICES</b>                               | <b>F.600–F.699</b> |
+| <b>AUDIOVISUAL SERVICES</b>                                     | <b>F.700–F.799</b> |
+| <b>ISDN SERVICES</b>                                            | <b>F.800–F.849</b> |
+| <b>UNIVERSAL PERSONAL TELECOMMUNICATION</b>                     | <b>F.850–F.899</b> |
+| <b>HUMAN FACTORS</b>                                            | <b>F.900–F.999</b> |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+# Recommendation ITU-T F.747.5
+
+# Requirements and functional architecture of an automatic location identification system for ubiquitous sensor network (USN) applications and services
+
+## Summary
+
+Recommendation ITU-T F.747.5 defines the functional requirements, architecture and entities of automatic location identification in ubiquitous sensor networks (USNs).
+
+## History
+
+| Edition | Recommendation | Approval   | Study Group | Unique ID*                                                                      |
+|---------|----------------|------------|-------------|---------------------------------------------------------------------------------|
+| 1.0     | ITU-T F.747.5  | 2014-01-13 | 16          | <a href="http://handle.itu.int/11.1002/1000/12052-en">11.1002/1000/12052-en</a> |
+
+## Keywords
+
+Automatic positioning capability, location-based services, sensor location information.
+
+---
+
+\* 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 2014
+
+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 .....                                                                                 | 2           |
+| 6 | Requirements for ALI systems .....                                                                | 2           |
+|   | 6.1 General requirements.....                                                                     | 2           |
+|   | 6.2 High-level requirements .....                                                                 | 3           |
+| 7 | Functional architecture of the ALI system for USN applications and services.....                  | 4           |
+|   | 7.1 Functional architecture .....                                                                 | 4           |
+|   | 7.2 Functional entities .....                                                                     | 4           |
+|   | Appendix I – Relationship between open USN service platform and ALI capabilities .....            | 6           |
+|   | Appendix II – Information flow of ALI services.....                                               | 7           |
+|   | II.1 Resource registration .....                                                                  | 7           |
+|   | II.2 Positioning process.....                                                                     | 8           |
+|   | II.3 Configuration process.....                                                                   | 8           |
+|   | Appendix III – ALI scenarios for USN applications and services.....                               | 10          |
+|   | III.1 Location identification for sensor nodes working in complex environments .....              | 10          |
+|   | III.2 Continuing location identification for sensor nodes in a changing physical environment..... | 11          |
+|   | III.3 Location identification for sensor nodes using sensing and actuating techniques.....        | 12          |
+|   | III.4 Configuration for sensor nodes with limited processing capabilities.....                    | 13          |
+|   | III.5 Location identification for sensor nodes in a resource-limited USN environment.....         | 13          |
+|   | Bibliography.....                                                                                 | 15          |
+
+## **Introduction**
+
+With the help of numerous sensors, radio frequency identification (RFID) tags and other end-node devices, the ubiquitous sensor network (USN) can provide information exchange without any human intervention, for example, it is possible to monitor the weather in one particular area of China from the ITU office in Geneva by means of humidity and temperature sensors, and it is also possible to display traffic flow information for London via the velocity sensors on mobile phones. These trillions of new USN applications and services are built using three basic elements – data, time and location.
+
+With the increase in USN applications and services, new positioning methods are being created and automatic location identification (ALI) capabilities need to be added to the open USN service platform which provide unified accessibility to USN resources and which allows the data of USN applications to take full advantage of the USN capabilities.
+
+# Recommendation ITU-T F.747.5
+
+## Requirements and functional architecture of an automatic location identification system for ubiquitous sensor network (USN) applications and services
+
+## 1 Scope
+
+The automatic location identification (ALI) capability enables a device to discover its own location. The ALI system can be deployed along with network equipment or independently integrated with end-node devices. It can be used in various networks such as a mobile network, the Internet, or a low power wireless network.
+
+The scope of this Recommendation includes:
+
+- requirements of the ALI system
+- the functional architecture of the ALI system within an open USN service platform
+- Specific scenarios of the ALI system.
+
+## 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 F.747.4] Recommendation ITU-T F.747.4 (2014), *Requirements and functional architecture for the open ubiquitous sensor network service platform*.
+- [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 open USN service** [ITU-T F.747.4]: USN service which provides unified access to USN resources and sensed data/semantic data through heterogeneous USN middleware.
+
+**3.1.2 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.3 sensor network** [ITU-T Y.2221]: A network comprised of interconnected sensor nodes exchanging sensed data by wired or wireless communication.
+
+**3.1.4 sensor node** [ITU-T Y.2221]: A device consisting of sensor(s) and optional actuator(s) with capabilities of sensed data processing and networking.
+
+**3.1.5 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.6 USN middleware** [ITU-T Y.2221]: A set of logical functions to support USN applications and services.
+
+**3.1.7 USN resource** [ITU-T F.747.4]: An entity that provides a USN service including sensor, actuator, sensor node, sensor network and gateway.
+
+### **3.2 Terms defined in this Recommendation**
+
+This Recommendation defines the following terms:
+
+**3.2.1 ALI service:** A service which provides the best accessible positioning results to USN applications through heterogeneous USN middleware and open USN service platform provisioning based on the use of standard interfaces.
+
+**3.2.2 ALI system:** An ALI system is a set of interacting or interdependent components forming an integrated whole or a set of elements to offer an ALI service.
+
+## **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|      |                                   |
+|------|-----------------------------------|
+| ALI  | Automatic Location Identification |
+| API  | Application Programming Interface |
+| CDMA | Code Division Multiple Access     |
+| FE   | Functional Entity                 |
+| GPS  | Global Positioning System         |
+| GSM  | Global System for Mobile          |
+| RFID | Radio Frequency Identification    |
+| USN  | Ubiquitous Sensor Network         |
+| UWB  | Ultra-Wideband                    |
+
+## **5 Conventions**
+
+No specific conventions have been used in this Recommendation.
+
+## **6 Requirements for ALI systems**
+
+### **6.1 General requirements**
+
+The following are the general requirements of the ALI system which address the minimum requirements of the location identification system for USN applications and services:
+
+- ALI systems should coexist with existing location-related standards defined by other SDOs such as 3GPP2 [b-3GPP2 IP-BLS] and [b-3GPP2 b-MAPLS], 3GPP [b-3GPP LCS], and OMA [b-OMA SUPL and b-OMA MLS]. It is recommended that the introduction of an ALI system does not have any negative impact on the operation and performance of existing standards.
+
+- The functions introduced by the ALI system are recommended to be either hosted in existing function elements of the USN or in completely new physical entities. The ALI system is required to not impose any modifications on the architecture or functionality of underlying network technology.
+- It is recommended that all ALI location data be time-stamped, and the USN application and service are required to use the most recent data available.
+- The ALI system is required to provide mechanisms to prevent denial of service attacks.
+- The ALI system is required to ensure that data is protected in all transactions, in accordance with the user's privacy preferences, except for when this information is required for emergency or lawful purposes depending on local/regional regulations.
+- The architecture is recommended to support the storage of location information for a sensor node so that it may be available later, if required.
+- ALI capability is required in order to allow support for location requests, regardless of a user's privacy preferences, when associated with emergency services and applicable by local regulations. The ALI system is required to support sensor node-initiated and network-initiated positioning for emergency location requests. It is required that emergency services location information requests are given a higher priority over other location information requests, based on local regulatory requirements.
+
+### 6.2 High-level requirements
+
+The following are the high-level requirements of the ALI system, which specify the user's needs for automatic location identification for the ubiquitous sensor network.
+
+- Supporting seamless positioning techniques:  
+The ALI system is recommended to support seamless positioning techniques. This could be accomplished by automatically changing to other suitable techniques when the currently operating positioning technique cannot determine the location, or the positioning result is not acceptable.
+- Supporting hybrid positioning techniques:  
+The ALI system is recommended to support location identification by combining more than one positioning technique when a single positioning technique cannot specify the exact location of the device. It is also recommended to support the process of choosing the best-fit positioning technique from the many available techniques.
+- Supporting USN location identification techniques:  
+The device utilizes USN techniques to determine its location, such as an image processing technique, RFID or a gyroscope technique. The ALI system is recommended to support these techniques.
+- Positioning data compression and conflict control management:  
+When portable devices periodically update their location, network performance could be affected if a large number of USN devices are working in an inadequate network environment. It is recommended that ALI systems support conflict control and compression of the positioning data to reduce this problem.
+- Conversion of coordinates:  
+Location information is shared to support many USN applications which use different coordinates; as a result, the ALI system is recommended to support the uniformity of coordinates and the possible conversion of coordinates.
+
+## 7 Functional architecture of the ALI system for USN applications and services
+
+### 7.1 Functional architecture
+
+The functional architecture of the ALI system for USN applications and services may be varied according to diverse USN architectures. Figure 1 shows the functional architecture of the ALI system within the open USN service platform, as a typical example. The functional entities defined in clause 7.2 and the information flow defined in Appendix II, have been applied to this architecture.
+
+![Functional architecture of the ALI system diagram](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+The diagram illustrates the functional architecture of the ALI system. It is organized into several layers and components:
+
+- Top Layer (Applications and Application support FE):** A dashed orange box encloses two stacked rectangles: "Applications" on top and "Application support FE" below it.
+- Second Layer:** Below the dashed box, there is a "Coordinate adaption FE" rectangle on the left and a larger "Configuration FE" rectangle on the right.
+- Third Layer (Positioning FE):** A large rectangle labeled "Positioning FE" contains three sub-components: "Positioning switching FE", "Positioning hybrid FE", and "USN positioning FE".
+- Fourth Layer (Adaption FE and USN middleware):** A dashed orange box encloses two stacked rectangles: "Adaption FE" on top and "USN middleware" below it.
+- Bottom Layer:** Below the "USN middleware" rectangle, there are six small circles representing network interfaces. Arrows point upwards from each circle to the "USN middleware" rectangle.
+
+Legend: A dashed orange box is labeled "Defined in ITU-T F.747.4".
+
+Reference: F.747.5(14)\_F01
+
+Functional architecture of the ALI system diagram
+
+**Figure 1 – Functional architecture of the ALI system**
+
+### 7.2 Functional entities
+
+#### 7.2.1 Application support FE
+
+The application support FE provides the functions which enable open USN services to obtain ALI services and/or the positioning data from the ALI system.
+
+Also, it supports the functions which allow the establishment or maintenance of the connection or disconnection according to the type of a request, and the access control to handle the access privileges for users and services.
+
+#### 7.2.2 Coordinate adaptation FE
+
+The coordinates adaptation FE provides the functions which translate the positioning results into the standard and required coordinate, and this is provided for related open USN services.
+
+#### 7.2.3 Remote configuration FE
+
+The remote configuration FE provides the function which enables applications to modify the configurations of the positioning services through an ALI system.
+
+#### **7.2.4 Adaptation FE**
+
+The adaption FE provides the functions which handle the protocol and message for setting the connection with USN middleware, and which deliver queries and commands as an interface for processing several types of positioning data that come from USN middleware.
+
+Also, it supports the function to translate generated data from USN middleware to proper message specifications that are dealt with in the ALI system.
+
+The adaptation FE provides a similar function to that of the adaptation FE which is defined in [ITU-T F.747.4]. However, the adaptation FE defined here also directly provides services to sensor nodes which require positioning results and it does not share this with other open application programming interfaces (APIs).
+
+#### **7.2.5 Positioning FE**
+
+##### **7.2.5.1 Positioning switching FE**
+
+The positioning switching FE provides the functions which support the smooth transition to a valid positioning technique, and which estimate the best available positioning result when the operating positioning technique cannot determine the location or the positioning result is not acceptable.
+
+##### **7.2.5.2 Positioning hybrid FE**
+
+The positioning hybrid FE provides the functions which support position calculation by combining various positioning techniques when a single technique cannot specify the exact location of the device. It also supports positioning result optimization by choosing the best-fit positioning technique from the many available techniques, according to the requirements of the applications, such as accuracy first or time first.
+
+##### **7.2.5.3 USN positioning FE**
+
+The USN positioning FE provides the functions which support USN techniques for the determination of a sensor node location.
+
+## Appendix I
+
+### Relationship between open USN service platform and ALI capabilities
+
+(This appendix does not form an integral part of this Recommendation.)
+
+Figure I.1 shows the relationship between an open USN service platform and ALI capabilities. ALI capabilities are important capabilities of an open USN service platform, which are to be provided to various USN applications and services.
+
+![Architecture diagram showing the relationship between an open USN service platform and ALI capabilities.](1439cb942d9e363bbb3161b5540dd8c6_img.jpg)
+
+The diagram illustrates the architecture of an open USN service platform and its relationship with various components and sensor networks.
+
+- Application:** The top-level component, which interacts with the platform via an **Application support FE**.
+- Open USN service platform:** A large container box containing several functional elements:
+  - Application support FE:** Connects the Application to the platform.
+  - Semantic query FE:** Interacts with the Semantic USN repository FE and the Automatic location identification support FE.
+  - Semantic USN repository FE:** Contains a **Semantic data repository** and a **Sensed data repository**. It interacts with the **LOD linking FE**, **Semantic inference FE**, and the **Resource management FE**.
+  - Resource management FE:** Interacts with the Semantic USN repository FE and the **Adaptation FE**.
+  - Automatic location identification support FE:** A shaded box representing ALI capabilities, which interacts with the Semantic query FE and the **Adaptation FE**.
+  - Adaptation FE:** A container for multiple **Adaptation FE<sub>1</sub>**, **Adaptation FE<sub>2</sub>**, ..., **Adaptation FE<sub>n</sub>** components.
+- USN middleware:** Multiple middleware components (**USN middleware<sub>1</sub>**, **USN middleware<sub>2</sub>**, ..., **USN middleware<sub>n</sub>**) that interface between the platform's adaptation layer and the sensor networks.
+- Sensor or sensor network:** Represented by groups of circles at the bottom, each connected to a corresponding USN middleware component.
+
+Arrows indicate the direction of data flow and interactions between these components.
+
+F.747.5(14)\_Fl.1
+
+Architecture diagram showing the relationship between an open USN service platform and ALI capabilities.
+
+**Figure I.1 – Relationship between open USN service platform and ALI capabilities**
+
+## Appendix II
+
+### Information flow of ALI services
+
+(This appendix does not form an integral part of this Recommendation.)
+
+This appendix shows the information flow of ALI systems.
+
+### II.1 Resource registration
+
+Figure II.1 shows the information flow of sensor node registration for the use of ALI services.
+
+![Figure II.1: Information flow of sensor node registration for the use of ALI services. The diagram shows a layered architecture. At the top, 'Applications' and 'Application support FE' are enclosed in a dashed box. Below them are 'Coordinate adaption FE' and 'Configuration FE'. A 'Positioning FE' block contains 'Positioning switching FE', 'Positioning hybrid FE', and 'USN positioning FE'. Below the positioning FE is the 'Adaption FE' and 'USN middleware' block, also enclosed in a dashed box. To the right is the 'Resource management FE' block. Arrows indicate the flow: 1. From a circle at the bottom to 'USN middleware'. 2. From 'USN middleware' to 'Adaption FE'. 3. From 'Adaption FE' to 'Resource management FE'. 4. From 'Resource management FE' to 'Adaption FE'. 5. From 'Adaption FE' to 'Positioning FE'. A legend indicates that dashed boxes are defined in ITU-T F.747.4. The reference F.747.5(14)_FII.1 is noted at the bottom right.](ddc7460821484f1ae2835c67955c554c_img.jpg)
+
+Defined in ITU-T F.747.4
+
+F.747.5(14)\_FII.1
+
+Figure II.1: Information flow of sensor node registration for the use of ALI services. The diagram shows a layered architecture. At the top, 'Applications' and 'Application support FE' are enclosed in a dashed box. Below them are 'Coordinate adaption FE' and 'Configuration FE'. A 'Positioning FE' block contains 'Positioning switching FE', 'Positioning hybrid FE', and 'USN positioning FE'. Below the positioning FE is the 'Adaption FE' and 'USN middleware' block, also enclosed in a dashed box. To the right is the 'Resource management FE' block. Arrows indicate the flow: 1. From a circle at the bottom to 'USN middleware'. 2. From 'USN middleware' to 'Adaption FE'. 3. From 'Adaption FE' to 'Resource management FE'. 4. From 'Resource management FE' to 'Adaption FE'. 5. From 'Adaption FE' to 'Positioning FE'. A legend indicates that dashed boxes are defined in ITU-T F.747.4. The reference F.747.5(14)\_FII.1 is noted at the bottom right.
+
+**Figure II.1 – Information flow of sensor node registration for the use of ALI services**
+
+- (1) After receiving an application request, the sensors send the registration requests to the ALI system with the location-related data via USN middleware.
+- (2) USN middleware sends a request to an open USN service platform through the adaptation FE to ensure that the sensor/application is registered.
+- (3) The adaptation FE sends the message to the resource management FE.
+- (4) The resource management FE returns the result of the registration to the adaptation FE and ensures that the sensor supports the ALI function.
+- (5) The adaptation FE returns the result to the ALI service; the valid requests are sent to the ALI service platform.
+
+### II.2 Positioning process
+
+Figure II.2 shows the information flow of the positioning process of an ALI system.
+
+![Diagram of the information flow of the positioning process of an ALI system.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg)
+
+The diagram illustrates the information flow of the positioning process of an ALI system. It shows a hierarchical structure of functional entities (FEs) and their interactions:
+
+- Applications** and **Application support FE** are grouped within a dashed orange box at the top.
+- Coordinate adaption FE** is positioned below the dashed box.
+- Positioning FE** is a container box below the coordinate adaption FE, containing three sub-FEs: **Positioning switching FE**, **Positioning hybrid FE**, and **USN positioning FE**.
+- Configuration FE** is a separate box to the right of the positioning FE.
+- Adaption FE** and **USN middleware** are grouped within a dashed orange box at the bottom.
+- An external input (represented by a circle) connects to the **USN middleware**.
+
+Numbered arrows indicate the flow of information:
+
+- Arrow 1: From **USN middleware** to **Positioning FE**.
+- Arrow 2: From **Positioning FE** to **Coordinate adaption FE**.
+- Arrow 3: From **Coordinate adaption FE** to **Application support FE**.
+- Arrow 4: From **Application support FE** to **Applications**.
+
+A legend at the bottom left shows a dashed orange box labeled "Defined in ITU-T F.747.4". The reference "F.747.5(14)\_FII.2" is located at the bottom right of the diagram.
+
+Diagram of the information flow of the positioning process of an ALI system.
+
+**Figure II.2 – Information flow of the positioning process of an ALI system**
+
+- (1) The valid requests are sent to the ALI service platform.
+- (2) The positioning FE will then decide, according to the positioning request and any requirements, on the best positioning method, such as positioning switching, positioning hybrid and USN positioning. Positioning switching, positioning hybrid and the USN positioning functions in the positioning FE calculate the position of the sensor.
+- (3) According to the positioning request, the positioning results are translated into the requested data via the coordinates adaption FE. The coordinates adaption FE sends the data to the application support FE.
+- (4) The application support FE sends the data to the application.
+
+### II.3 Configuration process
+
+Figure II.3 shows the information flow of the configuration process of the ALI system.
+
+![Figure II.3 – The information flow of the configuration process of the ALI system. The diagram shows a layered architecture with components: Applications, Application support FE, Coordinate adaption FE, Positioning FE (containing Positioning switching FE, Positioning hybrid FE, and USN positioning FE), Configuration FE, Adaption FE, and USN middleware. A sensor is connected to the USN middleware. Numbered arrows (1-16) indicate the flow of information. A dashed orange box encloses the top three layers (Applications, Application support FE, and Configuration FE). A legend indicates that dashed orange boxes are defined in ITU-T F.747.4.](33ed1f9b27c7c21c797aa928b0f06851_img.jpg)
+
+Defined in ITU-T F.747.4
+
+Figure II.3 – The information flow of the configuration process of the ALI system. The diagram shows a layered architecture with components: Applications, Application support FE, Coordinate adaption FE, Positioning FE (containing Positioning switching FE, Positioning hybrid FE, and USN positioning FE), Configuration FE, Adaption FE, and USN middleware. A sensor is connected to the USN middleware. Numbered arrows (1-16) indicate the flow of information. A dashed orange box encloses the top three layers (Applications, Application support FE, and Configuration FE). A legend indicates that dashed orange boxes are defined in ITU-T F.747.4.
+
+**Figure II.3 – The information flow of the configuration process of the ALI system**
+
+- (1) The application sends a configuration change request to the application support FE.
+- (2) The application support FE sends the request to the configuration FE. The configuration FE checks the request, sees if it is a valid process and accepts the rules according to the privacy policy and other rules which exist in the configuration FE.
+- (3) If it is acceptable, the configuration FE sends the configuration change request message to the adaption FE. Otherwise, it will return the unsuccessful information back to the application.
+- (4) The adaption FE sends the information to the USN middleware.
+- (5) The USN middleware sends the request to the sensor.
+- (6) The sensor receives the configuration change message, and decides whether or not to download the new configuration. When the sensor accepts the request, it sends a request for downloading the new configuration to the USN middleware; otherwise it returns the error code and goes to step 12.
+- (7) The USN middleware sends the request to the adaption FE.
+- (8) The adaption FE sends the request to the configuration FE.
+- (9) The configuration FE sends the configuration parameters to the sensor via the adaption FE.
+- (10) The adaption FE sends the new parameters to the USN middleware.
+- (11) The USN middleware sends the new parameters to the sensor.
+- (12-14) After successfully receiving the new configuration, the sensor sends the success feedback message to the configuration FE via the USN middleware, and the adaption FE; otherwise, the sensor sends the error code to the configuration FE via the USN middleware, and the adaption FE.
+- (15-16) The configuration FE sends the information back to the application via the application support FE.
+
+## Appendix III
+
+### ALI scenarios for USN applications and services
+
+(This appendix does not form an integral part of this Recommendation.)
+
+Possible use cases in the ALI system are described in this appendix.
+
+### III.1 Location identification for sensor nodes working in complex environments
+
+Compared with regular mobile positioning capabilities, sensor nodes sometimes work in complex environments. One example is that the capability of one single technique, such as a GSM/CDMA cell tower, Wi-Fi real-time locating systems or a global positioning system (GPS), is restricted and the location of a mobile unit cannot be determined, or sometimes it receives multiple location results. Therefore, in complex environments, the sensing node either supports the capability to combine multiple positioning techniques to provide a suitable positioning result or it supports the capability of choosing the best positioning method from more than one approach. The following use cases demonstrate this scenario.
+
+#### III.1.1 Not receiving an acceptable result from a single positioning technique
+
+This scenario covers an example that requires hybrid positioning techniques. The positioning for indoor sensors during a fire emergency is a typical case which requires the use of various positioning techniques.
+
+The fire zone includes indoor and outdoor sites and many sensors are shot into the burning area. These sensors sense the temperature or capture the motion around them to detect survivors. All the sensors are communicating with wireless / near-field communication techniques, such as Wi-Fi, ZigBee, UWB, etc. With the help of one or more sink nodes, the sensor network connects to transmission networks to report the specific situation of the alerting zone. Some of the sensors contain GPS modules. These sensors are regarded as the reference points, or marks. The position of other sensors could not be determined without the help of these GPS references. By calculating the distance using the power attenuation from the reference points to the sensors, the positions of these sensors could be determined by hybrid positioning techniques, i.e., GPS and received signal strength indication. Figure III.1 illustrates this use case.
+
+![Diagram illustrating the Fire emergency use case for sensor node positioning. It shows two GPS satellites at the top, with dashed lines representing signals being received by a network of sensor nodes below. The sensor nodes are represented by various colored shapes: red squares, green squares, and yellow circles. Some nodes are connected by solid lines, forming a network. A text box on the left explains that nodes without GPS modules use signal strength and distance from GPS nodes to determine their location. The diagram is labeled F.747.5(14)_FIII.1 in the bottom right corner.](6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg)
+
+Nodes which do not have a GPS module use both the signal received from the GPS node and the distance calculated according to signal attrition to calculate its own location.
+
+F.747.5(14)\_FIII.1
+
+Diagram illustrating the Fire emergency use case for sensor node positioning. It shows two GPS satellites at the top, with dashed lines representing signals being received by a network of sensor nodes below. The sensor nodes are represented by various colored shapes: red squares, green squares, and yellow circles. Some nodes are connected by solid lines, forming a network. A text box on the left explains that nodes without GPS modules use signal strength and distance from GPS nodes to determine their location. The diagram is labeled F.747.5(14)\_FIII.1 in the bottom right corner.
+
+Figure III.1 – Fire emergency use case
+
+#### **III.1.2 Receiving more than one location identification result**
+
+With the development of positioning techniques, devices sometimes support more than one methodology of obtaining location information. Several positioning results may be attained; these are estimated via multiple procedures. It is necessary to choose the most appropriate procedure according to the requirements of the application (time-first or accurate-first) to present the most applicable outcome.
+
+A medical emergency can be used to illustrate this. The service is highly sensitive to the amount of time used. When an emergency service requests location information, several modules (IP, cell-tower, GPS, and others) start the positioning processes. The system first informs the nearby ambulances according to the IP address, and requests that they head to the location area consistent with the result from the cell-tower. Yet, the result is not precise enough. While on the road, GPS sends the accurate position of the patient to the ambulance. The optimization of the multiple positioning methods helps the ambulance reach the site of the incident as soon as possible.
+
+### **III.2 Continuing location identification for sensor nodes in a changing physical environment**
+
+Some USN applications ask for an integrated positioning solution that can provide seamless location identification in a variety of environments. This entails a positioning solution which is required to switch automatically from one positioning method to another, as soon as the node realizes the current positioning result is not acceptable to provide the required services with guaranteed quality, or the current positioning procedure cannot be supported. This scenario provides an example where nodes require seamless location identification. The following use cases describe this scenario.
+
+#### **III.2.1 Continuing location identification within the same system of coordinates**
+
+Traditionally, positioning results are obtained through geographical coordinates, i.e., latitude and longitude. When switching between traditional techniques, positioning results are expected to be in a uniform format and updated to applications seamlessly.
+
+The tracking of a heart disease patient is a typical use case for the switching between traditional techniques use case. The sensors attached to a patient's body, monitors the patient's heart rate and other vital signs. They also report latitude and longitude to a health manager centre which is tracking the patient's location. When the patient walks along the street, the patient's location is obtained by the GPS module; if the patient drives into a tunnel and the GPS signal is lost, the location can be attained through GSM/CDMA cell-towers; as soon as the patient walks into a house, the device switches automatically to the Wi-Fi positioning mode to address the patient's precise location; and the hospital also provides RFID indicators to specify a more accurate position. Figure III.2 illustrates the heart disease patient use case for a multiple-location identification scenario.
+
+![Diagram illustrating the use case of heart disease patient tracking. A central figure of a person is connected to four cloud-shaped nodes labeled GPS, GSM, Wi-Fi, and RFID. Each node is linked to a corresponding image: GPS to an outdoor road scene, GSM to a tunnel with cars, Wi-Fi to an indoor room with a bed, and RFID to a hospital room with a patient in bed.](76b0cd79baaedd942af4dc42f2e764b8_img.jpg)
+
+Diagram illustrating the use case of heart disease patient tracking. A central figure of a person is connected to four cloud-shaped nodes labeled GPS, GSM, Wi-Fi, and RFID. Each node is linked to a corresponding image: GPS to an outdoor road scene, GSM to a tunnel with cars, Wi-Fi to an indoor room with a bed, and RFID to a hospital room with a patient in bed.
+
+**Figure III.2 – Use case of heart disease patient tracking**
+
+#### **III.2.2 Continuing location identification across different systems of coordinates**
+
+Instead of traditional geographical coordinates, the location information obtained by most new techniques is presented in other formats. When switching between a traditional positioning technique and these new positioning techniques, applications should either get the result in the same format or be informed of the change in format of the coordinates.
+
+Shopping centre navigation is an illustration of this use case. Applications direct customers to target places. Outdoor navigation uses GPS (resulting in geographical coordinates) to help customers drive to the shopping centre; after entering the shopping centre, the indoor guiding system directs customers to their preferred shops, using Wi-Fi (resulting in indoor coordinates) or RFID (represented by a special identification string ID). The indoor coordinate system uses offset  $x, y, z$  to indicate the customer's location, while identification string ID uses strings to represent a particular spot. The change in the format of the coordinates should be notified, so that applications understand the meaning of the positioning results and give users the correct directions.
+
+### **III.3 Location identification for sensor nodes using sensing and actuating techniques**
+
+Various sensing and actuating techniques are introduced in the USN. Other than the traditional cell-tower or GPS, these USN sensing and actuating techniques could also be used to determine the location. It opens the door to numerous innovative positioning ways, which also brings challenges for ALI systems to be compatible with these techniques. There are several ways of delivering these state-of-the-art techniques for location identification; these include but are not limited to the following use cases.
+
+#### **III.3.1 Location identification using images**
+
+With the new image processing ability, the devices with cameras or other sensors can recognize landmarks or particular patterns, thus determining the location.
+
+The example below of robot positioning shows the image processing technique used in location identification. The robots, which are equipped with cameras/mark-readers, follow particular patterns on the floor. Each mark indicates a certain spot. The robot reads the mark and identifies the position. A supervisor thus tracks the footpaths that the robots have reported, and also gives them appropriate commands. Figure III.3 illustrates the example that the robots identify the locations with the help of an image processing technique.
+
+![Figure III.3: Use case of robot positioning with image processing capabilities. The diagram shows a floor plan of a facility with various rooms: SHIPPING and RECEIVING, TOOLS, MATERIALS PROCESSING, RESEARCH and DEVELOPMENT, STORAGE ROOM, CAFE, EMPLOYEE LOUNGE, and MANAGER OFFICE. A small robot is positioned near the MAIN ENTRANCE. Numerous QR codes are placed throughout the environment as landmarks. A text box states: 'With the help of image sensors, the robot recognises landmarks which make it aware of its location.' The diagram is labeled F.747.5(13)_FIII.3.](9c6461e1e94afae4dec455e69a2ce152_img.jpg)
+
+Figure III.3: Use case of robot positioning with image processing capabilities. The diagram shows a floor plan of a facility with various rooms: SHIPPING and RECEIVING, TOOLS, MATERIALS PROCESSING, RESEARCH and DEVELOPMENT, STORAGE ROOM, CAFE, EMPLOYEE LOUNGE, and MANAGER OFFICE. A small robot is positioned near the MAIN ENTRANCE. Numerous QR codes are placed throughout the environment as landmarks. A text box states: 'With the help of image sensors, the robot recognises landmarks which make it aware of its location.' The diagram is labeled F.747.5(13)\_FIII.3.
+
+**Figure III.3 – Use case of robot positioning with image processing capabilities**
+
+#### **III.3.2 Location identification using an RFID tag**
+
+When a radio signal from a specific RFID tag is collected by devices at a certain point, the identification string of the tag can be decoded, and the corresponding location can be determined.
+
+#### **III.3.3 Location identification using a gyroscope**
+
+A device with a gyroscope can quantify movement in the x, y, z directions, and thus it can calculate its position from the original point.
+
+### **III.4 Configuration for sensor nodes with limited processing capabilities**
+
+Sometimes, the configuration parameters of the sensor need to be modified during the positioning process according to its environment or the requirements from applications. However, the processing capabilities of the USN end nodes are limited. The ALI end node cannot adjust itself spontaneously and it needs the help of the platform. The configuration parameters may include but are not limited to the time of positioning periods, the alarming condition, etc. When sensors are not able to complete these actions dynamically, they connect to the management platform and download the configurations and process as required.
+
+The sensor placed in a briefcase can be a typical example. It checks its position periodically. The positioning period and the sound of the alarm can be altered remotely by the management platform, according to the distance between the briefcase and the owner. If the distance between the briefcase and its owner exceeds the distance limit, the platform can send a notification to the owner.
+
+### **III.5 Location identification for sensor nodes in a resource-limited USN environment**
+
+Resource-limited places are common in daily life and USN systems may be deployed in such places. Moreover, a USN may utilize resource-limited devices or terminals to facilitate its deployment. The limitation may be the power of the battery or the bandwidth of the link. This scenario demonstrates that location identification works in resource-limited environments, and it describes use cases which optimize the ALI system in such situations.
+
+#### **III.5.1 Power-limited environment**
+
+A power-limited environment refers to cases where, when the ALI system is used, the power of the device can be exhausted after a period of time. A typical power-limited environment is when devices adopt batteries as their power supply. Decreasing the power consumption can prolong the usage time. For instance, the ZigBee [b-ZigBee] terminal providing location identification can switch to power saving mode to extend its usage time (when batteries are used).
+
+#### **III.5.2 Network-limited environment**
+
+The network-limited environment includes two cases, low bandwidth and unstable connections. For example, ZigBee or some UWB technologies have very low bandwidths. The connection of GSM/CDMA is sometimes not stable, due to strong interference. In this case, the ALI system needs to increase its transmission efficiency, for instance, by compressing the payload of location information in packets.
+
+## Bibliography
+
+- [b-3GPP LCS] 3GPP (2013), *Functional stage 2 description of Location Services (LCS)*  
+<<http://www.3gpp.org/ftp/Specs/html-info/23271.htm>> (accessed 2013-05-20)
+- [b-3GPP2 IP-BLS] 3GPP2 (2005), *IP-Based Location Services Revision: 0 – 3GPP2*.  
+<[http://www.3gpp2.org/public\\_html/specs/X.S0024-0\\_v1.0\\_051102.pdf](http://www.3gpp2.org/public_html/specs/X.S0024-0_v1.0_051102.pdf)> (accessed 2013-05-20)
+- [b-3GPP2 MAP-LS] 3GPP2 (2006), *MAP Location Services Enhancements*.  
+<[http://www.3gpp2.org/public\\_html/specs/X.S0002-0\\_v2.0\\_060531.pdf](http://www.3gpp2.org/public_html/specs/X.S0002-0_v2.0_060531.pdf)> (accessed 2013-05-20)
+- [b-OMA] OMA (2011), *Mobile Location Service V1.2*.  
+<[http://technical.openmobilealliance.org/Technical/release\\_program/mls\\_v1\\_2.aspx](http://technical.openmobilealliance.org/Technical/release_program/mls_v1_2.aspx)>  
+(accessed 2013-05-20)
+- [b-OMA SUPL] OMA (2013), *OMA Secure User Plane Location V2.0*.  
+<[http://technical.openmobilealliance.org/technical/release\\_program/supl\\_v2\\_0.aspx](http://technical.openmobilealliance.org/technical/release_program/supl_v2_0.aspx)>  
+(accessed 2013-05-20)
+- [b-ZigBee] ZigBee Alliance (2007), *ZigBee Specification*.  
+<<http://www.zigbee.org/Specifications/ZigBee/download.aspx>>  
+(accessed 2013-12-12)
+
+
+
+
+
+## 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-H.623-201511-I_PDF-E/raw.md

@@ -0,0 +1,732 @@
+
+
+**ITU-T**
+
+**Y.4414/H.623**
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+(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 –  
+Frameworks, architectures and protocols
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS  
+Broadband, triple-play and advanced multimedia  
+services – Advanced multimedia services and applications
+
+---
+
+# **Web of things service architecture**
+
+Recommendation ITU-T Y.4414/H.623
+
+# 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                |                      |
+| 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.4414/H.623
+
+# Web of things service architecture
+
+## Summary
+
+Recommendation ITU-T Y.4414/H.623 defines a web of things (WoT) service architecture that can encompass service discovery, accessibility, sharing and mash-up for IoT devices and services with web technologies. It includes an overview of WoT services, the functional architecture of WoT services and WoT service/resource functions.
+
+The WoT service architecture supports accessibility and reusability across IoT resources, and supports portability across heterogeneous network environments. Therefore, this Recommendation is applicable to seamless and interoperable IoT services with information interaction and exchange over physical IoT devices.
+
+## History
+
+| Edition | Recommendation     | Approval   | Study Group | Unique ID*                                                                |
+|---------|--------------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T Y.4414/H.623 | 2015-11-29 | 16          | <a href="http://handle.itu.int/11.1002/1000/12647">11.1002/1000/12647</a> |
+
+## Keywords
+
+Web of things, WoT, WoT service architecture.
+
+---
+
+\* 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 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.....                                    | 3    |
+| 4 | Abbreviations and acronyms .....                                                 | 3    |
+| 5 | Conventions .....                                                                | 4    |
+| 6 | Overview of the WoT service.....                                                 | 4    |
+| 7 | Functional architecture of the WoT service.....                                  | 5    |
+|   | 7.1 WoT service functions.....                                                   | 6    |
+|   | 7.2 Web resource functions .....                                                 | 7    |
+|   | 7.3 Web client.....                                                              | 7    |
+|   | 7.4 Things.....                                                                  | 7    |
+| 8 | WoT service functions.....                                                       | 8    |
+|   | 8.1 Functional entities of the WoT service support functions (WoT-S SF).....     | 8    |
+|   | 8.2 Functional entities of the WoT service control functions (WoT-S CF) .....    | 9    |
+|   | 8.3 Functional entities of the WoT resource management functions (WoT RMF) ..... | 11   |
+| 9 | Web resource functions .....                                                     | 13   |
+|   | 9.1 WoT broker functions.....                                                    | 13   |
+|   | 9.2 RESTful web services .....                                                   | 14   |
+|   | Appendix I – WoT description model.....                                          | 15   |
+|   | I.1 Physical characteristics in WoT description.....                             | 15   |
+|   | I.2 Service characteristics in WoT description .....                             | 15   |
+|   | Appendix II – An example of information flows.....                               | 16   |
+|   | II.1 Information flow between web client and things .....                        | 16   |
+|   | Bibliography.....                                                                | 18   |
+
+
+
+# Recommendation ITU-T Y.4414/H.623
+
+# Web of things service architecture
+
+# 1 Scope
+
+The objective of this Recommendation is to define a WoT service architecture. The scope of this Recommendation covers the following:
+
+- overview of the WoT applications
+- a functional architecture for the WoT service
+- functional entities for the WoT service
+
+# 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 M.3030] Recommendation ITU-T M.3030 (2002), *Telecommunications Markup Language (tML) framework*.
+- [ITU-T Y.2002] Recommendation ITU-T Y.2002 (2009), *Overview of ubiquitous networking and of its support in NGN*.
+- [ITU-T Y.2232] Recommendation ITU-T Y.2232 (2008), *NGN convergence service model and scenario using web services*.
+- [ITU-T Y.4000] Recommendation ITU-T Y.4000/Y.2060 (2012), *Overview of the Internet of things*.
+- [ITU-T Y.4400] Recommendation ITU-T Y.4400/Y.2063 (2012), *Framework of the web of things*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 client** [b-W3C WACterms]: The role adopted by an application when it is retrieving and/or rendering resources. A program establishes connections for the purpose of sending requests.
+
+**3.1.2 device** [b-W3C digloss]: An apparatus through which a user can perceive and interact with the Web.
+
+**3.1.3 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 – In a broad perspective, the IoT can be perceived as a vision with technological and societal implications.
+
+**3.1.4 metadata** [ITU-T M.3030]: Data that describes other data.
+
+**3.1.5 resource** [b-IETF RFC 3986]: This specification does not limit the scope of what might be a resource; rather, the term "resource" is used in a general sense for whatever might be identified by a URI. Familiar examples include an electronic document, an image, a source of information with a consistent purpose (e.g., "today's weather report for Los Angeles"), a service (e.g., an HTTP-to-SMS gateway), and a collection of other resources. A resource is not necessarily accessible via the Internet; e.g., human beings, corporations, and bound books in a library can also be resources. Likewise, abstract concepts can be resources, such as the operators and operands of a mathematical equation, the types of a relationship (e.g., "parent" or "employee"), or numeric values (e.g., zero, one, and infinity).
+
+**3.1.6 server** [b-W3C WACterms]: The role adopted by an application when it is supplying resources.
+
+**3.1.7 service provider** [ITU-T Y.2232]: An entity that provides services.
+
+**3.1.8 SOAP** [b-W3C SOAP 1]: The formal set of conventions governing the format and processing rules of a SOAP message. These conventions include the interactions among SOAP nodes generating and accepting SOAP messages for the purpose of exchanging information along a SOAP message path.
+
+**3.1.9 SOAP intermediary** [b-W3C SOAP 1]: A SOAP intermediary is both a SOAP receiver and a SOAP sender and is targetable from within a SOAP message. It processes the SOAP header blocks targeted at it and acts to forward a SOAP message towards an ultimate SOAP receiver.
+
+**3.1.10 the World Wide Web (WWW, or simply web)** [b-W3C webarch]: An information space in which the items of interest, referred to as resources, are identified by global identifiers called Uniform Resource Identifiers (URI).
+
+**3.1.11 thing** [ITU-T Y.4000]: In the Internet of things, object of the physical world (physical things) or of the information world (virtual things), which is capable of being identified and integrated into the communication networks.
+
+**3.1.12 URI** [b-IETF RFC 3986]: A URI is an identifier consisting of a sequence of characters matching the syntax rule named <URI> in Section 3 of [b-IETF RFC 3986]. It enables uniform identification of resources via a separately defined extensible set of naming schemes (Section 3.1 of [b-IETF RFC 3986]). How that identification is accomplished, assigned, or enabled is delegated to each scheme specification.
+
+**3.1.13 web of things** [ITU-T Y.4400]: A way of realization of the IoT where (physical and virtual) things are connected and controlled through the World Wide Web.
+
+**3.1.14 web resource** [b-W3C WACterms]: A resource, identified by a URI.
+
+**3.1.15 web services** [ITU-T Y.2232]: Web services is a service provided using web services systems.
+
+**3.1.16 web services gateway (WSG)** [ITU-T Y.2232]: A gateway which handles the web services message between the WSP and WSR.
+
+**3.1.17 web services provider (WSP)** [ITU-T Y.2232]: A service provider that exposes a capability for use to create web services.
+
+**3.1.18 web services registry** [ITU-T Y.2232]: An entity that stores web services information (e.g., WSDL).
+
+**3.1.19 Web services requester (WSR)** [ITU-T Y.2232]: Client software that makes use of the services provided by a WSP.
+
+**3.1.20 web services system** [ITU-T Y.2232]: A web services system is a software system designed to support interoperable machine-to-machine interaction over a network using web services standards.
+
+NOTE – It has an interface described in a machine-processable format (specifically WSDL). Other systems interact with the web services in a manner prescribed by its description using SOAP-messages, typically conveyed using HTTP with an XML serialization in conjunction with other web-related standards.
+
+**3.1.21 WSDL** [b-W3C WSDL 1]: Web services description language Version 2.0 (WSDL 2.0) provides a model and an XML format for describing web services. WSDL 2.0 enables one to separate the description of the abstract functionality offered by a service from concrete details of a service description such as "how" and "where" that functionality is offered.
+
+## **3.2 Terms defined in this Recommendation**
+
+None.
+
+# **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|           |                                              |
+|-----------|----------------------------------------------|
+| API       | Application Programming Interface            |
+| CPU       | Central Processing Unit                      |
+| DPWS      | Device Profile for Web Services              |
+| GPU       | Graphics Processing Unit                     |
+| HTML      | Hypertext Markup Language                    |
+| HTTP      | Hypertext Transport Protocol                 |
+| ID        | Identification                               |
+| IoT       | Internet of Things                           |
+| IP        | Internet Protocol                            |
+| JSON      | JavaScript Object Notation                   |
+| NFC       | Near Field Communication                     |
+| QoS       | Quality of Service                           |
+| RDFa      | Resource Description Framework in attributes |
+| REST      | Representational State Transfer              |
+| SOAP      | Simple Object Access Protocol                |
+| TCP       | Transmission Control Protocol                |
+| UI        | User Interface                               |
+| URI       | Uniform Resource Identifiers                 |
+| Web-RM FE | Web Resource Management Functional Entity    |
+| WoT       | Web of Things                                |
+| WoT-BM FE | WoT Broker Management Functional Entity      |
+| WoT-DM FE | WoT Description Management Functional Entity |
+| WoT-EN FE | WoT Enrolment Functional Entity              |
+| WoT RMF   | WoT Resource Management Function             |
+
+|              |                                                  |
+|--------------|--------------------------------------------------|
+| WoT-S CF     | WoT Service Control Function                     |
+| WoT-S SF     | WoT Service Support Function                     |
+| WoT-S-CR FE  | WoT Service Creation Functional Entity           |
+| WoT-S-DIS FE | WoT Service Discovery Functional Entity          |
+| WoT-S-EX FE  | WoT Service Execution Functional Entity          |
+| WoT-S-MA FE  | WoT Service Management Functional Entity         |
+| WoT-S-MON FE | WoT Service Monitoring Functional Entity         |
+| WoT-S-PM FE  | WoT Service Policy Management Functional Entity  |
+| WoT-S-PRM FE | WoT Service Profile Management Functional Entity |
+| WoT-S-RE FE  | WoT Service Registration Functional Entity       |
+| WSDL         | Web Service Description Language                 |
+| XML          | extensible Markup Language                       |
+
+# 5 Conventions
+
+None.
+
+# 6 Overview of the WoT service
+
+The web is used as a global standard platform to deliver services to an end user and applications to intercommunicate with each other over a network. [ITU-T Y.4400] describes that the web has program language independent properties, uses message driven communications and easily bounds to different transport protocols. Web technology allows the exposure of physical devices as well as several kinds of content as web resources such as URI and HTTP. Therefore, users and service developers can interact with the devices using web interfaces. The WoT can provide capabilities such as device reusability, portability across several heterogeneous networks and accessibility based on web standards technologies.
+
+Figure 1 shows a general concept of the WoT service. The physical devices as well as content are integrated into the web and are viewed as the sort of services provided by the web environment. In addition, each service has a mash-up capability to create a new service by composition of the existing services in the web environments. According to [ITU-T Y.4400], the web technologies can support to create applications of networked devices and services.
+
+![Figure 1: General concept of a web of things service. The diagram shows a central cloud labeled 'Web' containing several 'Service' nodes. These services are connected to various physical devices (things) at the bottom, including a router, light bulb, camera, phone, printer, computer, mobile phone, CD, books, and film reel. The connections are color-coded: blue for general web connectivity and red for specific service connections to devices.](cfef993dcc8fb513de79eb1f93cf26ae_img.jpg)
+
+Y.4414-H.623(15)\_F01
+
+Figure 1: General concept of a web of things service. The diagram shows a central cloud labeled 'Web' containing several 'Service' nodes. These services are connected to various physical devices (things) at the bottom, including a router, light bulb, camera, phone, printer, computer, mobile phone, CD, books, and film reel. The connections are color-coded: blue for general web connectivity and red for specific service connections to devices.
+
+**Figure 1 – General concept of a web of things service**
+
+# 7 Functional architecture of the WoT service
+
+Figure 2 shows an overview of the functional architecture of a WoT service.
+
+![Figure 2: Functional architecture of WoT service. This is a complex block diagram showing the internal structure of a WoT service. On the left, a 'Web client' interacts with 'WoT service functions' (support, control, and resource management) and a 'WoT-S repository'. These functions interact with 'Web resource functions' (broker functions with T2R and adaptation components) and a 'Resource information repository'. The broker functions then interact with 'Things' on the right, categorized into 'Physical thing: constrained devices', 'Physical thing: Fully-fledged devices', and 'Virtual thing: Web resource'. Arrows indicate different types of interfaces: solid for web, dashed for proprietary, and dotted for other connections.](d26959f4514c26ca19c3d6f00da85956_img.jpg)
+
+Y.4414-H.623(15)\_F02
+
+\* T2R: Things to resource  
+ <---> Proprietary interface  
+ <==> Web interface
+
+Figure 2: Functional architecture of WoT service. This is a complex block diagram showing the internal structure of a WoT service. On the left, a 'Web client' interacts with 'WoT service functions' (support, control, and resource management) and a 'WoT-S repository'. These functions interact with 'Web resource functions' (broker functions with T2R and adaptation components) and a 'Resource information repository'. The broker functions then interact with 'Things' on the right, categorized into 'Physical thing: constrained devices', 'Physical thing: Fully-fledged devices', and 'Virtual thing: Web resource'. Arrows indicate different types of interfaces: solid for web, dashed for proprietary, and dotted for other connections.
+
+**Figure 2 – Functional architecture of WoT service**
+
+NOTE – Virtual things exist in the information world and are capable of being stored, processed and accessed. Examples of virtual things include multimedia content and application software [ITU-T Y.4000]. In the case of a WoT service architecture, virtual things exist as the web resources on the web environments.
+
+## 7.1 WoT service functions
+
+The WoT service functions provide WoT services to WoT clients. They manage overall behaviours related to the WoT service. If a WoT client requests a WoT service, the WoT service functions analyse the request then discover and provide the services for a WoT client. The WoT service functions have three sub-functions as follows:
+
+- **WoT service support functions (WoT-S SF):** The WoT-S SF manages overall behaviours of the WoT service. The WoT-S SF are responsible for providing service profile management, service discovery, service monitoring, QoS management, access control and policy management of WoT service. And it is also responsible for containing and updating the WoT service information.
+- **WoT service control functions (WoT-S CF):** They control the WoT service which are registered in the WoT service providers. It is responsible for executing and creating the WoT service and mash-up services.
+- **WoT resource management functions (WoT RMF):** They contain resource information (things information) which is used by and registered at the WoT service functions.
+
+## 7.2 Web resource functions
+
+The web resource functions have responsibility for accessing the things by enabling web technologies. If there are no relevant web technologies to access the things (devices) directly, the WoT broker function should be used which provides access to the devices on the web. Also it is responsible for integrating the web resources (e.g., fully-fledged device and constrained device) to the web [ITU-T Y.4400]. If it is a virtual thing, it can be accessed directly by the WoT resource management function. The T2R function has a role for integrating and exposing things to the web resources. In [ITU-T Y.4400], the service layer of the WoT broker is responsible for the T2R role. And, the things adaptation functions are responsible for adaptation.
+
+## 7.3 Web client
+
+With the web client, an end user can use WoT services provided by an accessed physical device or virtual thing. The web browser and web applications allow the web client to use WoT services. The web client can control devices by using a web browser and web technologies such as HTTP, RESTful API etc.
+
+## 7.4 Things
+
+In the WoT service, the things can be classified into two types; physical things and virtual things. The physical things can be classified into two types of devices, constrained devices and fully-fledged devices. The things can be accessed and exposed on the web as a WoT service.
+
+#### 7.4.1 Physical things
+
+##### 7.4.1.1 Constrained device
+
+The constrained device is a non-capable device to connect to the Internet or web alone. And it has no functionality of web. It has just its own proprietary interfaces and protocols such as ZigBee, Bluetooth, NFC, etc. These interfaces and protocols do not have interoperability with web technologies. In this case, the devices need the WoT broker. By exposing on web through the WoT broker, the devices can communication with the WoT broker using their proprietary interface. And the WoT broker has a role of agent for these devices in order to communicate with the web user.
+
+##### 7.4.1.2 Fully-fledged device
+
+The fully-fledged device is a device to support direct web connectivity functionalities, therefore there is no need to translate HTTP requests from the web clients into the appropriate protocol.
+
+However, to enable this capability, the web server is built in the devices itself.
+
+The fully-fledged device is necessary to satisfy the following two capabilities:
+
+- support of TCP/IP protocol suite
+- web server.
+
+These capabilities enable devices seamless integrating to the web and their functionality through the web interface.
+
+#### 7.4.2 Virtual things
+
+The virtual things are information world objects such as media, image, video and documents, etc. These objects are web resources exposing through the web service.
+
+# 8 WoT service functions
+
+## 8.1 Functional entities of the WoT service support functions (WoT-S SF)
+
+The WoT-S SF manages overall behaviours of the WoT service. The WoT-S SF are responsible for providing service profile management, service discovery, service monitoring, QoS management, access control and policy management of a WoT service. The WoT-S SF consists of four functional entities (FEs); the WoT service profile management FE (WoT-S-PRM FE), the WoT service discovery FE (WoT-S-DIS FE), the WoT service policy management FE (WoT-S-PM FE) and the WoT service monitoring FE (WoT-S MON FE). The WoT-S SF also interworks with the WoT-S repository to register and discover WoT services, etc.
+
+![Diagram of WoT service support functions (WoT-S-SF) functional entities and interfaces.](5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg)
+
+The diagram illustrates the functional entities and interfaces of the WoT service support functions (WoT-S-SF). A large rounded rectangle labeled "WoT service support functions (WoT-S-SF)" contains four functional entities (FEs): "WoT-S policy management FE (WoT-S-PM FE)" at the top, "WoT-S profile management FE (WoT-S-PRM FE)" on the bottom left, "WoT-S discovery FE (WoT-S-DIS FE)" on the bottom right, and "WoT-S monitoring FE (WoT-S-MON FE)" on the far right. Bidirectional arrows connect the PM FE to the PRM FE, and the PM FE to the DIS FE. A bidirectional arrow also connects the PRM FE and the DIS FE. A horizontal bidirectional arrow connects the DIS FE and the MON FE. Below the main container is a cylinder labeled "WoT-S repository". Bidirectional arrows connect the PRM FE and the DIS FE to the repository. The identifier "Y.4414-H.623(15)\_F03" is located at the bottom right of the diagram.
+
+Diagram of WoT service support functions (WoT-S-SF) functional entities and interfaces.
+
+**Figure 3 – Functional entities and interfaces of WoT-S SF**
+
+### 8.1.1 WoT service profile management functional entity (WoT-S-PRM FE)
+
+The WoT-S profile management FE (WoT-S-PRM FE) is responsible for managing the profile of the registered services. The service profile is a record that contains information related to the WoT service such as version of service, service life cycle, service classification etc. If a service version is changed, this information is reflected in the registered WoT-S repository. The WoT-S-PRM FE interworks with the WoT-S repository to maintain the latest information of the WoT service.
+
+A WoT user requests a service through the WoT-S-PRM FE and the WoT-S-PRM FE forwards the request to the WoT-S-DIS FE. The WoT-S-DIS FE analyses the request and searches the services in
+
+the WoT-S repository or on the web. The WoT-S-DIS FE returns the result to the WoT-S-PRM FE. And the WoT-S-PRM FE provides the service to the WoT user.
+
+### **8.1.2 WoT service discovery functional entity (WoT-S-DIS FE)**
+
+The WoT service discovery FE (WoT-S-DIS FE) provides a discovery capability in collaboration with web resource functions. The WoT-S-DIS FE interworks with the WoT broker functions to discover the WoT service composed of physical devices.
+
+In the WoT service environments, lots of the WoT services will be presented and provided on the web and many users and service developers want to search and find them on the web. In the context of the WoT, the simplest way of enabling search for the WoT service (things) is using the web search engines like the web documents. However, a search for things as the WoT service is more complicated than a search for documents on the web due to its contextual information such as their absolute location or their relative location.
+
+#### **8.1.3 WoT service monitoring functional entity (WoT-S-MON FE)**
+
+The WoT service monitoring FE (WoT-S-MON FE) is responsible for monitoring the registered WoT service. The web client or other FEs (WoT-S-DIS FE, WoT-S-PRM FE) utilize the WoT-S-MON FE to find out the status of the WoT service. The status of the WoT service is recommended to include service availability or predict response time, static/dynamic status information and resource information, e.g., CPU/GPU power.
+
+The WoT-S-MON FE is recommended to provide static and dynamic information in order to guarantee a stable quality of the WoT service. Static information consists of quality requirements, e.g., response time, min performance value, max performance value and normal performance value for the WoT service. Dynamic information consists of a real-time updated status for the WoT system and service. For example, system status includes application ID, network port, the amount of instant data and average data, network bandwidth, and so on. Service status includes execution time, fps, screen size, and so on.
+
+The WoT-S-MON FE is required to monitor system resource information of processor power consumption, e.g., CPU and GPU, in order to predict system power consumption of the WoT service. Therefore, the system resource is necessary to provide the QoS guaranteed WoT service such as a high performance with lower power consumption. A GPU resource is measured by using a power coefficient corresponding to each GPU frequency, GPU utilization and GPU static power.
+
+#### **8.1.4 WoT service policy management functional entity (WoT-S-PM FE)**
+
+The WoT service policy management FE (WoT-S-PM FE) provides three capabilities for the WoT service as follows:
+
+- QoS information management: The WoT-S-PM FE is responsible for managing QoS information about the registered WoT service. It checks accessibility, performance, reliability of the WoT service. The WoT-S-PM FE is also responsible for providing QoS information to the web client.
+- Service access control: The WoT-S-PM FE provides service access control capabilities to control the accessibility of a specific service by an application. It provides authentication and authorization actions required to ensure that the web client has appropriate access rights to the requested service.
+- Security and safety management: The WoT-S-PM FE provides control capabilities regarding security and safety in order to support a trustworthy WoT service. It provides methods to guarantee the safe execution of service in the WoT system, which are comprised of actions by detecting an execution request and controlling execution of the service command.
+
+### 8.2 Functional entities of the WoT service control functions (WoT-S CF)
+
+The WoT-S CF is responsible for controlling the WoT service creation, service execution, service registration and service management. The WoT-S-CF consists of four functional entities (FEs); the WoT-S management FE (WoT-S-MA FE), the WoT service execution FE (WoT-S-EX FE), the WoT-S creation FE (WoT-S-CR FE), the WoT service registration FE (WoT-S-RE FE) with WoT-S repository.
+
+![Diagram of WoT service control functions (WoT-S CF) showing internal components and their interactions with the WoT-S repository.](724c7777b608e53be38b12b6fb3c43bc_img.jpg)
+
+The diagram illustrates the functional entities and interfaces of the WoT-S CF. A large box labeled 'WoT service control functions (WoT-S CF)' contains four smaller boxes: 'WoT-S management FE (WoT-S MA FE)', 'WoT-S creation FE (WoT-S-CR FE)', 'WoT-S registration FE (WoT-S-RE FE)', and 'WoT-S execution FE (WoT-S-EX FE)'. The 'WoT-S management FE' is connected to the other three entities by double-headed arrows. The 'WoT-S creation FE' and 'WoT-S registration FE' are also connected by a double-headed arrow. The 'WoT-S registration FE' and 'WoT-S execution FE' are connected by a double-headed arrow. All four entities are connected to a cylinder labeled 'WoT-S repository' by double-headed arrows. A reference code 'Y.4414-H.623(15)\_F04' is located at the bottom right of the diagram.
+
+Diagram of WoT service control functions (WoT-S CF) showing internal components and their interactions with the WoT-S repository.
+
+Figure 4 – Functional entities and interfaces of WoT-S CF
+
+### 8.2.1 WoT service execution functional entity (WoT-S-EX FE)
+
+The WoT service execution FE (WoT-S-EX FE) is responsible for executing the WoT service. The WoT-S-EX FE enables the WoT service user to access and execute the WoT service. When an end user (web client) wants to use the WoT service, the WoT-S-EX FE interacts with the WoT-S-PM FE located in the WoT-S SF to check the authentication and the authorization of the requester. Additionally, the WoT-S-PRM FE also checks availability of the service at that time.
+
+The WoT-S-EX FE interworks with the WoT-S repository which includes logics to execute a service. The WoT execution logics have a method for how to operate services.
+
+The basic functionalities of the WoT-S-EX FE on managing logic are:
+
+- storing and management logics describing an event in the WoT-S repository, a condition to be satisfied by the event, and an action to be executed when the conditions are satisfied;  
+NOTE – When a service requester requests to register the logic, the logic is stored if and only if the logic does not generate a static conflict in which the logic describes different actions upon the same event and the same conditions for the action with other logics.
+- retrieving a logic describing the event storage when an event occurs;
+- inspecting the conditions whether or not the event satisfies a condition described in the retrieved logic;
+- executing an action described in the retrieved logic when the event satisfies the condition.
+
+#### 8.2.2 WoT service creation functional entity (WoT-S-CR FE)
+
+The WoT service creation FE (WoT-S-CR FE) allows the WoT service to be developed by simple composition of the existing WoT services on top of web-based things.
+
+The WoT-S-CR FE is responsible for managing and executing mash-up WoT services. The WoT-S-CR FE provides two functions: mash-up logic management and mash-up engine.
+
+A WoT user is able to search, create or update service execution logic through mash-up logic management via the web access. The service execution logic is stored and retrieved using the WoT-S repository. A WoT user can also request a mash-up engine to operate the service execution
+
+logic for the mash-up WoT service. Each unit of the WoT service for the mash-up service is executed by the WoT-S-EX FE.
+
+NOTE – The web mash-up is defined as "web applications generated by combining content, presentation or application functionality from the disparate web sources". The aim of mash-up is to create new useful applications or services by combining them in a value-adding manner. The WoT allows developers to access and search for the web-enabled things, and also allows owners of the web-enabled things to have a simple and scalable mechanism on sharing them.
+
+#### 8.2.3 WoT service management functional entity (WoT-S-MA FE)
+
+The WoT service management FE (WoT-S-MA FE) is responsible for managing the WoT service. It provides capabilities to manage service updating, service tracking, update management, auditing, version control, logging and service coordination.
+
+The WoT-S-MA FE supports the collection and storage of the WoT service logs. It also provides capabilities to replace or substitute the WoT service. If the WoT-S-MA FE finds better services, it recommends to change the old service to the new service. The WoT-S-MA has the ability to detect failures of services as well as recovery from failures.
+
+#### 8.2.4 WoT service registration functional entity (WoT-S-RE FE)
+
+The WoT service registration FE (WoT-S-RE FE) allows registration and deregistration of the WoT service in the WoT service repository. The WoT-S-RE FE has the ability to analyse services for registration in terms of their characteristics (e.g., service category, service provider and information about service charging).
+
+The WoT-S-RE FE interworks with the WoT service creation FE (WoT-S-CR FE). The WoT-S-RE FE registers the new service after creating a service by the WoT-S-CR FE. The WoT-S-RE FE investigates the service and extracts information of the service.
+
+#### 8.2.5 WoT service repository (WoT-S repository)
+
+The WoT service repository is responsible for storing WoT services and related information such as service characteristics, service type, service location, service version, service status, etc. The WoT service repository also contains the service execution logic, which comprises the service execution description of each WoT service. Mash-up services also have the service execution description which contains service information, service rule and service profiles like other WoT services:
+
+- service information is related to the linked information with the WoT-S repository or in case of mash-up services, it contains key features for WoT mash-up services such as classification, QoS, owner, etc.;
+- service rule is related to the method on how to operate services, or in case of mash-up services, it contains one or mixed rules of sequential execution, conditional execution and operational execution;
+- service profiles are related to the parameters to provide customised services according to location, preference or other clients' characteristics.
+
+![Diagram illustrating Service execution logic in a WoT-S repository. A large light blue rounded rectangle is labeled 'Service execution logic' at the top. Inside this rectangle, there are three white document-shaped boxes. The first box on the left is labeled '#1' and contains the text 'Service execution description'. The second box in the middle is labeled '#2' and also contains 'Service execution description'. To the right of the second box are three dots '...', followed by a third box on the right labeled '#n' which contains 'Service execution description'.](96b0240f56d14453b5da05ec30fd5c6e_img.jpg)
+
+Y.4414-H.623(15)\_F05
+
+Diagram illustrating Service execution logic in a WoT-S repository. A large light blue rounded rectangle is labeled 'Service execution logic' at the top. Inside this rectangle, there are three white document-shaped boxes. The first box on the left is labeled '#1' and contains the text 'Service execution description'. The second box in the middle is labeled '#2' and also contains 'Service execution description'. To the right of the second box are three dots '...', followed by a third box on the right labeled '#n' which contains 'Service execution description'.
+
+Figure 5 – Service execution logic in a WoT-S repository
+
+## 8.3 Functional entities of the WoT resource management functions (WoT RMF)
+
+The WoT RMF manage resources that are used for the WoT service. The WoT RMF can register resources into a resource information repository and can delete them. The resources are provided by the WoT broker functions and the web. The WoT RMF consists of four functional entities; the WoT enrolment FE (WoT-EN FE), the WoT broker management FE (WoT-BM FE), the web resource management FE (Web-RM FE) and the WoT description management FE (WoT-DM FE).
+
+![Diagram of WoT resource management functions (WoT RMF) showing four functional entities and a resource information repository.](2cde062fd82833415971a8bd1a2cafab_img.jpg)
+
+The diagram illustrates the functional entities and interfaces of the WoT RMF. It is enclosed in a box labeled "WoT resource management functions (WoT RMF)". Inside, there are four rectangular boxes representing functional entities: "WoT-S enrolment FE (WoT-EN FE)" at the top, "WoT broker management FE (WoT-BM FE)" in the middle, "WoT resource management FE (WoT-RM FE)" at the bottom, and "WoT resource description FE (WoT-DM FE)" on the left. A cylindrical database symbol labeled "Resource information repository" is on the right. Bidirectional arrows connect the WoT-EN FE, WoT-BM FE, and WoT-RM FE to the Resource information repository. A bidirectional arrow also connects the WoT-DM FE to the WoT-EN FE. A long arrow points from the bottom of the Resource information repository to the bottom of the WoT-DM FE. The label "H.623(15)\_F06" is at the bottom right of the diagram.
+
+Diagram of WoT resource management functions (WoT RMF) showing four functional entities and a resource information repository.
+
+Figure 6 – Functional entities and interfaces of WoT RMF
+
+### 8.3.1 WoT broker management functional entity (WoT-BM FE)
+
+The WoT-BM FE is responsible for registering information of each WoT broker function with related information such as location, owner, their services, etc.
+
+The WoT broker functions are responsible for providing physical devices as the web resources. The WoT broker functions reside in the WoT resource support functions area. However, there can be a large number of brokers and each WoT broker provides a number of different web resources. Therefore, in order to provide efficient WoT service management of the WoT a broker is necessary.
+
+### 8.3.2 Web resource management functional entity (Web-RM FE)
+
+The Web-RM FE is responsible for managing the web resource with the resource information repository.
+
+There are many types of content on the web such as image, video, music, documents, weather information, and text as a virtual things. These virtual things are ready to be exposed on the web and the WoT service provider uses them to create new WoT services. The Web-RM FE interworks with the resource information repository to manage these virtual things.
+
+### 8.3.3 WoT enrolment functional entity (WoT-EN FE)
+
+The WoT-EN FE provides a capability to support the WoT service enrolment, e.g., submission and registration. The web resource functions submit information of the web-enabled things to the WoT-EN FE. The WoT-EN FE checks and filters them using the enrolment policy.
+
+The WoT-EN FE also manages the enrolment policy. The WoT-EN FE updates and deletes the enrolment policy according to the changes on the information and context of the WoT service. The following are functions of the WoT-EN FE:
+
+- Submission handling: The WoT-EN FE receives the enrolment request from the WoT enabled things. For the request, these WoT services can submit their information such as IP, descriptions, name, URI, capability, related services, etc. Then the WoT-EN FE allows or blocks the request based on the enrolment policy.
+
+- Enrolment policy: The enrolment policy contains the rules of allowance for the web-enabled things. The WoT-EN FE manages the enrolment policy according to the changes of related entities such as the WoT service, service providers, users, etc.
+- Enrolment management: The WoT-EN FE has the capability for registration and management of the submitted web-enabled things to the resource information repository. The changes on the information and the context of the registered web-enabled things induce change of information of the resource information repository. The WoT-EN FE re-examines the changed web-enabled things with enrolment policy rules. It means that the WoT-EN FE can remove the registered web-enabled things beforehand from the resource information repository. The WoT-EN FE can allow the blocked WoT service to register in the repository if those are acceptable based on the changed enrolment policy.
+
+### **8.3.4 WoT description management functional entity (WoT-DM FE)**
+
+The WoT-DM FE provides a description method and it manages all description information related to things. Also, it provides capabilities for translating descriptions among the WoT services.
+
+There are many kinds of things that exist and all things need a mechanism to describe themselves and their services to be (automatically) discovered and used on the web. There are many description methods to utilize describing things such as web service description language (WSDL), resource description framework in attributes (RDFa), microformat, device profile for web services (DPWS) metadata, SensorML, JSON, etc. The WoT-DM FE provides the capability of description translation to cooperate among the many description methods and models supported by the different service providers.
+
+# **9 Web resource functions**
+
+## **9.1 WoT broker functions**
+
+The WoT broker functions have a role for integrating and exposing the devices to the web. To expose and use physical devices on the web, a web server supporting the HTTP is implemented on the devices. However, every device does not satisfy these conditions because of constraints.
+
+The WoT broker functions support communication between users of the WoT (e.g., the web clients, applications) and fully-fledged devices as well as constrained devices. The WoT broker functions enable the seamless integration of a device onto the web. The agent of the WoT broker has a role to control and communicate with physical devices.
+
+![Figure 7: Overview of WoT broker function architecture. The diagram shows a central 'WoT broker functions' block containing 'Things adaptation functions' and four 'Agent' icons. This block is connected via bidirectional arrows to 'Web resource providing functions/Web applications' at the top, 'Constrained devices' at the bottom left, and 'Fully-fledged devices' at the bottom right. A long arrow also points from the top to the bottom right. The bottom right is labeled 'Y.4414-H.623(15)_F07'.](9c6461e1e94afae4dec455e69a2ce152_img.jpg)
+
+Figure 7: Overview of WoT broker function architecture. The diagram shows a central 'WoT broker functions' block containing 'Things adaptation functions' and four 'Agent' icons. This block is connected via bidirectional arrows to 'Web resource providing functions/Web applications' at the top, 'Constrained devices' at the bottom left, and 'Fully-fledged devices' at the bottom right. A long arrow also points from the top to the bottom right. The bottom right is labeled 'Y.4414-H.623(15)\_F07'.
+
+**Figure 7 – Overview of WoT broker function architecture**
+
+NOTE – Detailed functions and architecture of the WoT broker function are given in [ITU-T Y.4400].
+
+There are several ways to interact between a WoT broker and devices such as http-based connection and web services:
+
+- Web services: enable business entities and applications to intercommunicate openly with each other over a network. Web service systems have program-language-independent properties, use message-driven communication, and are easily bound to different transport protocols [ITU-T Y.2232]. The basic web services for WoT define an interaction [b-W3C SOAP 0] [b-W3C SOAP 1] between WoT broker and constraint/fully-fledged device as an exchange of messages.
+- In the web services, a service and services descriptions are described [b-W3C WSDL 0]. A service is enabled by a software module deployed on network-accessible platforms provided by the service provider. The service description contains the details of the interface and implementation of the service including the data types, operations, binding information and network location. The service description is supported by a web services provider.
+- Also, in order for an application to take advantage of web services, three behaviours must take place: the publication of service descriptions, the finding and retrieval of service descriptions, and the binding or invoking of services based on the service description. These behaviours can occur singly or iteratively, with any cardinality between the roles. In detail, these operations are the execution (binding or invoking) of services based on the service description, finding and retrieval of service descriptions and publication of service descriptions.
+
+The WoT broker is a web services provider who provides a capability for use to create web services. The web client and web service application function are the web services requester who use the services provided by a WSP.
+
+## 9.2 RESTful web services
+
+The RESTful web services have some efficient properties such as high scalability achieved by the result of a loosely coupled design and facility for deployment since it builds up on the web infrastructure and standards.
+
+The REST includes the primacy of resources, identified using URIs, and a uniform interface generally implemented by the HTTP protocol. Resources are manipulated through representations portrayed according to a media type (e.g., HTML, Atom, etc.) and some metadata.
+
+The WoT uses HTTP as an application protocol rather than using it as a transport protocol. The WoT exposes its interface following the REST principle because these technical characteristics enable services and applications on the WoT to be built as loosely coupled systems which expose the application programming interface (API) in a uniform manner.
+
+# **Appendix I**
+
+## **WoT description model**
+
+(This appendix does not form an integral part of this Recommendation.)
+
+This appendix provides the following WoT description models.
+
+### **I.1 Physical characteristics in WoT description**
+
+#### **I.1.1 Device description**
+
+The device description provides information about things itself and its manufacturers. As a result, browsers, search engines and applications discovery by browsing the product description will be able to render its UI and visualization in an enhanced manner. Device description may have the following general components:
+
+- unique ID
+- name
+- brand
+- manufacturer
+- description
+- device picture
+- tags and
+- authoritative information URL.
+
+#### **I.1.2 Location description**
+
+The location description provides the physical location information of things. The user and application get the current latitude and longitude of the things. Also they get address, postal code, country name, street information etc.
+
+#### **I.1.3 Owner description**
+
+The owner description provides the current owner of things.
+
+### **I.2 Service characteristics in WoT description**
+
+#### **I.2.1 Quality of service description**
+
+The quality of service description covers parameters such as bandwidth, up-time, average response time it helps taking the right decision. In a WoT populated by billions of things quality of service information can be of great help to choose the right things for the right application. These data can be based on monitoring services or provided by the manufacturer of device and service provider.
+
+#### **I.2.2 Types of services description**
+
+The type of services description covers basic information required to describe things on the web. It contains a description of services that a thing offers (e.g., sensor information, multimedia service, etc.).
+
+# Appendix II
+
+## An example of information flows
+
+(This appendix does not form an integral part of this Recommendation.)
+
+This appendix describes information flows for providing WoT services. The information flow shows an example of a use case of how to provide a WoT service or how to access things.
+
+## II.1 Information flow between web client and things
+
+Figure II.1 shows one of the information flows relating to using WoT services. In this case, the web client wants to get a WoT service which consists of several kinds of things. At first, the web client sends a request for the WoT service to the WoT service functions using web technology (e.g., HTTP). And then the WoT service functions can access things through interworking with WoT broker functions. The detailed operation with information flow is followed as below.
+
+![Sequence diagram showing information flow between Web client, WoT service functions, Web resource functions, and Things.](5793a44ffdadd039928e2f9fe6daae06_img.jpg)
+
+The diagram illustrates the information flow between four main components: Web client, WoT service functions, Web resource functions, and Things. The WoT service functions are divided into two sub-sections: WoT service control functions (WoT-S CF) and WoT service support functions (WoT-S SF). The WoT-S CF section contains WoT-S-MA FE and WoT-S-EX FE. The WoT-S SF section contains WoT-S-PM FE, WoT-S-PRM FE, and WoT-S-DIS FE. The Web resource functions section contains the WoT broker function. The Things section contains three icons representing different types of things (white cube, white square, blue square).
+
+The sequence of operations is as follows:
+
+- ① Request a WoT service: Web client sends a request to WoT-S-MA FE.
+- ② User verification: WoT-S-MA FE sends a message to WoT-S-PM FE.
+- ③ Find the service: WoT-S-MA FE sends a message to WoT-S-PRM FE.
+- ④ Perform discovery procedure: WoT-S-PRM FE sends a message to WoT-S-DIS FE.
+- ⑤ Return information of the service: WoT-S-DIS FE sends a message to WoT-S-PRM FE.
+- ⑥ Command execution: WoT-S-MA FE sends a message to WoT-S-EX FE.
+- ⑦ Executing the service: WoT-S-EX FE sends a message to the WoT broker function.
+- ⑧ Finish the WoT service: Web client sends a message to WoT-S-MA FE.
+- ⑨ Stop execution: WoT-S-MA FE sends a message to WoT-S-EX FE.
+- ⑩ Release resources: WoT-S-EX FE sends a message to the WoT broker function.
+
+The diagram also shows a bidirectional arrow between the WoT broker function and the Things section, indicating communication between the broker and the things.
+
+Y.4414-H.623(15)\_FII.1
+
+Sequence diagram showing information flow between Web client, WoT service functions, Web resource functions, and Things.
+
+Figure II.1 – Information flow between end user and things
+
+- 1) Web client requests a WoT service to the WoT-S-MA FE.
+- 2) The WoT-S-MA FE (WoT service management FE) performs user verification with the WoT-S-PM FE (WoT service policy management FE). The WoT-S-MA FE sends a message to the WoT-S-PM FE to verify the user. The WoT-S-PM FE checks user validation and authentication to see whether the user is authorized to access the service. If the user does not have authorization, the WoT-S-PM FE returns a failure message.
+
+- 3) When the authentication procedure is finished successfully, the WoT-S-MA FE sends a message to the WoT-S-DIS FE to discover the service.
+- 4) The WoT-S-DIS FE performs a search procedure with the WoT-S-PRM FE (WoT service profile management FE). The WoT-S-PRM FE searches for the WoT service and retrieves information from the WoT-S repository.
+- 5) When the search procedure is finished successfully, the WoT-S-DIS FE returns information of the WoT service to the WoT-S-MA FE.
+- 6) The WoT-S-MA FE requests executing the WoT service to the WoT-S-EX FE (WoT service execution FE).
+- 7) The WoT-S-EX FE executes the service, interworking between the WoT-S-EX FE and the WoT broker function, to use/access things.
+- 8) The web client informs the WoT-S-MA FE to finish the WoT service.
+- 9) The WoT-S-MA FE commands the WoT-S-EX FE to stop executing the WoT service.
+- 10) The WoT-S-EX FE releases resources.
+
+# Bibliography
+
+- [b-IETF RFC 3986] IETF RFC 3986 (2005), *Uniform Resource Identifiers (URI): Generic Syntax*.  
+<https://tools.ietf.org/html/rfc3986>
+- [b-W3C digloss] Glossary of Terms for Device Independence (2005)  
+<http://www.w3.org/TR/di-gloss/>
+- [b-W3C SOAP 0] W3C Recommendation (2007), *SOAP Version 1.2 Part 0: Primer (Second Edition)*.  
+<http://www.w3.org/TR/soap12-part0/>
+- [b-W3C SOAP 1] W3C Recommendation (2007), *SOAP Version 1.2 Part 1: Messaging Framework (Second Edition)*.  
+<http://www.w3.org/TR/soap12-part1/>
+- [b-W3C WACterms] W3C et (1999) – *Web Characterization Terminology & Definitions Sheet*.  
+<http://www.w3.org/1999/05/WCA-terms/>
+- [b-W3C webarch] Jacobs, I & Walsh N (2004), *Architecture of the World Wide Web*, Volume One, 2004.  
+<http://www.w3.org/TR/webarch/>
+- [b-W3C WSDL 1] W3C Recommendation (2007), *Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language*.  
+<http://www.w3.org/TR/wsdl20/>
+
+# 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        |
+| Telepresence                                                                                | H.420–H.429        |
+| 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        |
+| <b>Advanced multimedia services and applications</b>                                        | <b>H.620–H.629</b> |
+| Ubiquitous sensor network applications and Internet of Things                               | H.640–H.649        |
+| 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        |
+| E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS                                               |                    |
+| Personal health systems                                                                     | H.810–H.819        |
+| Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) | H.820–H.859        |
+| Multimedia e-health data exchange services                                                  | H.860–H.869        |
+
+*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                                                                         |
+| 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        | 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.641-201202-I_PDF-E/raw.md

@@ -0,0 +1,535 @@
+
+
+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.641
+
+(02/2012)
+
+SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS
+
+Broadband, triple-play and advanced multimedia  
+services – Ubiquitous sensor network applications and  
+Internet of Things
+
+# --- **SNMP-based sensor network management framework**
+
+Recommendation ITU-T H.641
+
+![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        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## **Recommendation ITU-T H.641**
+
+# **SNMP-based sensor network management framework**
+
+## **Summary**
+
+Recommendation ITU-T H.641 describes a sensor network management framework intended to provide integrated management functionalities for heterogeneous sensor networks using the simple network management protocol (SNMP).
+
+## **History**
+
+| Edition | Recommendation | Approval   | Study Group |
+|---------|----------------|------------|-------------|
+| 1.0     | ITU-T H.641    | 2012-02-13 | 16          |
+
+## **Keywords**
+
+Sensor network management framework, SNMP.
+
+## 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 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 2012
+
+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 .....                                                                                                                    | 3    |
+| 6 | Architecture of an SNMP-based sensor network management framework.....                                                               | 3    |
+| 7 | Functional entities of SNMP-based sensor network management framework.....                                                           | 3    |
+|   | 7.1 SNMP manager .....                                                                                                               | 4    |
+|   | 7.2 SNMP agent.....                                                                                                                  | 4    |
+|   | 7.3 Sensor network management protocol manager.....                                                                                  | 4    |
+|   | 7.4 Sensor network management protocol agent.....                                                                                    | 4    |
+|   | 7.5 Application level gateway .....                                                                                                  | 5    |
+|   | 7.6 Managed object for sensor network .....                                                                                          | 5    |
+|   | 7.7 Managed object for sensor node.....                                                                                              | 5    |
+| 8 | Operation of an SNMP-based sensor network management framework.....                                                                  | 5    |
+|   | 8.1 Overview .....                                                                                                                   | 5    |
+|   | 8.2 Application level gateway database .....                                                                                         | 6    |
+|   | 8.3 Translation from an SNMP to a sensor network management protocol<br>message.....                                                 | 6    |
+|   | 8.4 Translation from a sensor network management protocol to an SNMP<br>message.....                                                 | 7    |
+|   | 8.5 Consideration of the sensor network gateway for supporting IP-based<br>sensor networks .....                                     | 8    |
+| 9 | Object identifier allocation for MIB and object identifier translation between<br>SNMP and sensor network management protocols ..... | 9    |
+|   | Annex A – Object identifier assignments .....                                                                                        | 10   |
+|   | Appendix I – Example of object identifier translation.....                                                                           | 11   |
+|   | Bibliography.....                                                                                                                    | 12   |
+
+# Introduction
+
+Ubiquitous sensor network (USN) is a conceptual network built over existing physical networks that 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 [ITU-T Y.2221]. One of the basic infrastructures of USN is wireless sensor networks that monitor physical or environmental conditions. These sensor networks may use different MAC/PHY protocols and different transport protocols, they may have different sensor node identification schemes and may use different management protocols.
+
+From the viewpoint of a sensor network management protocol, each sensor network may use different sensor network management protocols that are optimized for its MAC/PHY characteristics, transport layer characteristics and for each sensor network management information base (MIB). For example, an IEEE 802.15.4 based sensor network can deliver a 128 bytes frame at one time including 22 bytes of the IEEE 802.15.4 header. It means that a sensor network management protocol for an IEEE 802.15.4-based sensor network should be designed considering this frame size. The ZigBee sensor network based on IEEE 802.15.4 uses its own addressing scheme and defines its own MIB.
+
+Currently, many new sensor networking technologies are under development and it is inevitable that optimized sensor networking technologies for a particular purpose will be deployed. This means that there will be many heterogeneous sensor networks.
+
+From the viewpoint of network management, managing each heterogeneous sensor network with heterogeneous management protocols is impractical and an integrated management protocol for all heterogeneous sensor networks is needed.
+
+The common management information protocol (CMIP) [ITU-T X.711] is widely used in network management systems. However, most TCP/IP devices only support SNMP. SNMP is favoured and strongly supported by vendors, and it has been successfully adapted to manage wired and wireless networks.
+
+Due to the limited computing and communication power of sensor networks, the use of standard SNMP in sensor networks is either impractical or impossible.
+
+## Recommendation ITU-T H.641
+
+# SNMP-based sensor network management framework
+
+# 1 Scope
+
+This Recommendation provides an SNMP-based sensor network management framework. The primary purpose of this Recommendation is to describe the framework of integrated sensor network management which can be used to manage heterogeneous sensor networks. The scope of this Recommendation includes:
+
+- overall architecture of framework
+- functional entities of framework
+- object identifier allocation for MIB
+- object identifier translation between SNMP and sensor network management protocol.
+
+# 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.2221] Recommendation ITU-T Y.2221 (2010), *Requirements for support of Ubiquitous Sensor Network (USN) applications and services in the NGN environment.*
+- [ITU-T Y.2201] Recommendation ITU-T Y.2201 (2009), *Requirements and capabilities for ITU-T NGN.*
+- [IETF RFC 3411] IETF RFC 3411 (2002), *An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks.*
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 context awareness** [ITU-T Y.2201]: Context awareness is a capability to determine or influence a next action in telecommunication or process by referring to the status of relevant entities, which form a coherent environment as a context.
+
+**3.1.2 management information base** [IETF RFC 3411]: A collection of managed objects, residing in a virtual information store.
+
+**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 interconnected 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.
+
+**3.1.6 SNMP agent** [IETF RFC 3411]: An SNMP entity containing one or more command responder and/or notification originator applications (along with their associated SNMP engine).
+
+**3.1.7 SNMP manager** [IETF RFC 3411]: An SNMP entity containing one or more command generator and/or notification receiver applications (along with their associated SNMP engine).
+
+### **3.2 Terms defined in this Recommendation**
+
+This Recommendation defines the following terms:
+
+**3.2.1 sensor network management protocol agent:** A sensor network management protocol entity containing one or more command responder and/or notification originator applications (along with their associated sensor network management protocol engine).
+
+**3.2.2 sensor network management protocol manager:** A sensor network management protocol entity containing one or more command generator and/or notification receiver applications (along with their associated sensor network management protocol engine).
+
+# **4 Abbreviations and acronyms**
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|         |                                                     |
+|---------|-----------------------------------------------------|
+| 6LoWPAN | IPv6 over Low power Wireless Personal Area Networks |
+| AIB     | Application support Information Base                |
+| ALG     | Application Level Gateway                           |
+| CMIP    | Common Management Information Protocol              |
+| DST     | Destination                                         |
+| ID      | Identifier                                          |
+| IP      | Internet Protocol                                   |
+| IPv4    | Internet Protocol version 4                         |
+| IPv6    | Internet Protocol version 6                         |
+| MAC     | Media Access Control                                |
+| MIB     | Management Information Base                         |
+| NIB     | Network Information Base                            |
+| OID     | Object Identifier                                   |
+| PAN     | Personal Area Network                               |
+| PDU     | Protocol Data Unit                                  |
+| PHY     | Physical layer                                      |
+| PIB     | PAN Information Base                                |
+| SDO     | Standards Development Organization                  |
+| SNMP    | Simple Network Management Protocol                  |
+| SRC     | Source                                              |
+| TCP     | Transmission Control Protocol                       |
+| UDP     | User Datagram Protocol                              |
+| USN     | Ubiquitous Sensor Network                           |
+
+# 5 Conventions
+
+None.
+
+# 6 Architecture of an SNMP-based sensor network management framework
+
+Figure 1 illustrates the architecture of the SNMP-based sensor network management framework.
+
+The architecture comprises a sensor network manager, sensor network gateway and sensor node. The sensor network manager resides in the TCP/IP network and manages sensor nodes or sensor networks through sensor network gateways.
+
+![Figure 1: Architecture of an SNMP-based sensor network management framework. The diagram shows a sensor network (Sensor network X) containing several sensor nodes. This network is connected to a sensor network gateway. The gateway is connected to the Internet, which in turn connects to a sensor network manager. A double-headed arrow labeled 'Sensor network management protocol x' connects the sensor network to the gateway. A double-headed arrow labeled 'SNMP' connects the gateway to the sensor network manager.](367926125450c2bc3f4bdca9d59a62ba_img.jpg)
+
+The diagram illustrates the architecture of an SNMP-based sensor network management framework. On the left, a dashed circle represents 'Sensor network X', which contains several 'Sensor node' icons. A double-headed arrow labeled 'Sensor network management protocol x' connects this network to a central 'Sensor network gateway' (represented by a cube with a red circular arrow). The gateway is connected to an 'Internet' cloud, which then connects to a 'Sensor network manager' (represented by a computer icon). A double-headed arrow labeled 'SNMP' connects the gateway to the manager.
+
+H.641(12)\_F01
+
+Figure 1: Architecture of an SNMP-based sensor network management framework. The diagram shows a sensor network (Sensor network X) containing several sensor nodes. This network is connected to a sensor network gateway. The gateway is connected to the Internet, which in turn connects to a sensor network manager. A double-headed arrow labeled 'Sensor network management protocol x' connects the sensor network to the gateway. A double-headed arrow labeled 'SNMP' connects the gateway to the sensor network manager.
+
+**Figure 1 – Architecture of an SNMP-based sensor network management framework**
+
+A sensor network manager communicates with the sensor network gateway using standard SNMP over the IPv4 or IPv6.
+
+A sensor network gateway communicates with sensor nodes using a sensor network specific management protocol. Specific sensor network management protocols for specific sensor networks are out of the scope of this Recommendation.
+
+A sensor network gateway has dual network interfaces and performs MAC/PHY protocol translation, transport protocol translation, and management protocol translation between TCP/IP network and specific sensor networks if necessary. The translation of management protocol means translation between SNMP and sensor network specific management protocols. Protocol translations, other than management protocol translation, are out of the scope of this Recommendation.
+
+# 7 Functional entities of SNMP-based sensor network management framework
+
+Figure 2 illustrates the functional entities of an SNMP-based sensor network management framework.
+
+![Figure 2: Functional entities of an SNMP-based sensor network management framework. The diagram illustrates the architecture of a sensor network management system. On the left, 'Sensor network X' is a group of 'Sensor nodes' connected to a 'Sensor network management protocol agent'. This agent is linked to a 'Managed objects for sensor node' (represented by a key icon). In the center, a 'Sensor network gateway' connects to an 'ALG' (Application Level Gateway). The gateway is also connected to a 'Sensor network management protocol manager' and an 'SNMP agent'. The 'Sensor network management protocol manager' is linked to 'Managed objects for sensor network' (represented by a key icon). The 'SNMP agent' is linked to an 'SNMP manager'. The 'SNMP manager' is connected to the 'Internet' cloud, which in turn connects to a 'Sensor network manager' (represented by a computer icon). The diagram is divided into two main sections: 'Sensor network management protocol' on the left and 'SNMP' on the right, separated by a double-headed arrow. Dashed lines indicate connections between the sensor network, the gateway, and the management entities.](a5ee5c23b6dc52ec1d724b76d5a5f58f_img.jpg)
+
+Figure 2: Functional entities of an SNMP-based sensor network management framework. The diagram illustrates the architecture of a sensor network management system. On the left, 'Sensor network X' is a group of 'Sensor nodes' connected to a 'Sensor network management protocol agent'. This agent is linked to a 'Managed objects for sensor node' (represented by a key icon). In the center, a 'Sensor network gateway' connects to an 'ALG' (Application Level Gateway). The gateway is also connected to a 'Sensor network management protocol manager' and an 'SNMP agent'. The 'Sensor network management protocol manager' is linked to 'Managed objects for sensor network' (represented by a key icon). The 'SNMP agent' is linked to an 'SNMP manager'. The 'SNMP manager' is connected to the 'Internet' cloud, which in turn connects to a 'Sensor network manager' (represented by a computer icon). The diagram is divided into two main sections: 'Sensor network management protocol' on the left and 'SNMP' on the right, separated by a double-headed arrow. Dashed lines indicate connections between the sensor network, the gateway, and the management entities.
+
+H.641(12)\_F02
+
+**Figure 2 – Functional entities of an SNMP-based sensor network management framework**
+
+## 7.1 SNMP manager
+
+An SNMP manager is a set of management applications that monitor and control network elements such as the sensor network gateway and sensor network elements such as sensor nodes. An SNMP manager uses standard SNMP. Because the sensor network gateway is a normal TCP/IP device, an SNMP manager can manage the sensor network gateway using standard SNMP.
+
+## 7.2 SNMP agent
+
+An SNMP agent is a set of software modules that reside in network elements. It collects and stores management information such as the number of error packets received by a network element. In this framework, the SNMP agent has two roles, a role as the standard SNMP agent for managing the sensor network gateway and another role of delivering SNMP commands to the application level gateway (ALG) and SNMP responses to the SNMP manager.
+
+## 7.3 Sensor network management protocol manager
+
+A sensor network management protocol manager is a set of management applications that monitor and control sensor network elements. It receives commands from an ALG and delivers these commands to the sensor network management protocol agent and receives responses from the sensor network management protocol agent and delivers these responses to the ALG.
+
+## 7.4 Sensor network management protocol agent
+
+A sensor network management protocol agent is a set of software modules that reside in sensor network elements. It collects and stores management information such as the number of error packets received by a sensor network element.
+
+## 7.5 Application level gateway
+
+An application level gateway is a set of software modules that perform protocol translation between the SNMP and the sensor network management protocol. A sensor network management protocol manager, a sensor network management protocol agent and an ALG may be implemented in one software module, or in separate ones.
+
+## 7.6 Managed object for sensor network
+
+A managed object for a sensor network is a characteristic of a sensor network that can be managed. The characteristic of a sensor network is mainly related to the whole sensor network (not just for each sensor node) such as the number of sensor nodes in a sensor network. This information is managed by the SNMP agent in a sensor network gateway (see clause 6).
+
+## 7.7 Managed object for sensor node
+
+A managed object for a sensor node is a characteristic of a sensor node that can be managed. This information is managed by a sensor network management protocol agent in each sensor node. The managed object for a sensor node should be defined by other SDOs developing standards for specific sensor network technology. For example, if the sensor network is a ZigBee sensor network, the managed objects for the sensor nodes could be a ZigBee network information base (NIB) and a ZigBee application support information base (AIB), which are described in [b-ZigBee Specification].
+
+# 8 Operation of an SNMP-based sensor network management framework
+
+## 8.1 Overview
+
+Figure 3 illustrates the overall operation flow of an SNMP-based sensor network management framework.
+
+![Sequence diagram illustrating the operation flow of an SNMP-based sensor network management framework between a Sensor node, Sensor network gateway, and Sensor network manager.](7c6d9bfe9c31ce872722d60b73d20df1_img.jpg)
+
+```
+sequenceDiagram
+    participant SN as Sensor node
+    participant SNG as Sensor network gateway
+    participant SNM as Sensor network manager
+
+    SNM->>SNG: GetRequest{OID(ManagedObject_A), NULL}
+    SNG->>SNM: GetResponse {OID(ManagedObject_A), value}
+    Note over SNM: ~~~~~
+    SNG->>SNM: GetRequest{{OID(NodeID), NodeID_1}, {OID(ManagedObject_1), NULL}}
+    SNM->>SNG: GetResponse {{OID(NodeID), NodeID_1}, {OID(ManagedObject_1), value}}
+    Note over SNM: ~~~~~
+    SNG->>SN: GetRequest{OID(ManagedObject_1), NULL}
+    SN->>SNG: GetResponse {OID(ManagedObject_1), value}
+    Note over SNM: ~~~~~
+    SNM->>SNG: GetRequest{OID(ManagedObject_1), NULL}
+    Note over SNG: TCP/UDP header compression, SNMP optimization
+    SNG->>SNM: GetResponse {OID(ManagedObject_1), value}
+    Note over SNM: ~~~~~
+    SNM->>SNG: GetResponse {OID(ManagedObject_1), value}
+    Note over SNG: TCP/UDP header de-compression, SNMP re-storing
+    SNG->>SN: GetResponse {OID(ManagedObject_1), value}
+```
+
+The diagram illustrates the operation flow of an SNMP-based sensor network management framework. It shows three entities: Sensor node, Sensor network gateway, and Sensor network manager. The flow is as follows:
+
+- The Sensor network manager sends a `GetRequest{OID(ManagedObject_A), NULL}` to the Sensor network gateway.
+- The Sensor network gateway sends a `GetResponse {OID(ManagedObject_A), value}` to the Sensor network manager.
+- The Sensor network manager sends a `GetRequest{{OID(NodeID), NodeID_1}, {OID(ManagedObject_1), NULL}}` to the Sensor network gateway.
+- The Sensor network gateway sends a `GetResponse {{OID(NodeID), NodeID_1}, {OID(ManagedObject_1), value}}` to the Sensor network manager.
+- The Sensor network gateway sends a `GetRequest{OID(ManagedObject_1), NULL}` to the Sensor node.
+- The Sensor node sends a `GetResponse {OID(ManagedObject_1), value}` to the Sensor network gateway.
+- The Sensor network manager sends a `GetRequest{OID(ManagedObject_1), NULL}` to the Sensor network gateway.
+- The Sensor network gateway performs `TCP/UDP header compression, SNMP optimization` and sends a `GetResponse {OID(ManagedObject_1), value}` to the Sensor network manager.
+- The Sensor network manager sends a `GetResponse {OID(ManagedObject_1), value}` to the Sensor network gateway.
+- The Sensor network gateway performs `TCP/UDP header de-compression, SNMP re-storing` and sends a `GetResponse {OID(ManagedObject_1), value}` to the Sensor node.
+
+H.641(12)\_F03
+
+Sequence diagram illustrating the operation flow of an SNMP-based sensor network management framework between a Sensor node, Sensor network gateway, and Sensor network manager.
+
+**Figure 3 – Operation of an SNMP-based sensor network management framework**
+
+To manage a sensor node, a sensor network manager needs to send SNMP requests to a sensor network gateway.
+
+When the SNMP agent receives an SNMP message from the sensor network manager, it should check the OID values in the first *VarBind*. If this OID does not begin with {itu-t(0) recommendation(0) h(8) h641(641)} (see Annex A), then it just performs a normal SNMP agent role as specified in [IETF RFC 3411].
+
+If this OID begins with {itu-t(0) recommendation(0) h(8) h641(641)}, it passes the SNMP message to the ALG. In this message, the sensor node ID should be included as a *VarBind*. The ALG in the sensor network gateway converts this SNMP message to a sensor network management protocol message and sends it to a sensor node which is identified by a sensor node ID in *VarBind*. In this conversion process, the ALG removes the first *VarBind* from the *VarBindList*. The value of the first *VarBind* (sensor node ID) is used for the destination address in the sensor network protocol.
+
+A sensor node management protocol agent replies back to the sensor network gateway using the sensor network management protocol. When the ALG in the sensor network gateway receives this message, the ALG converts this sensor network management protocol message to an SNMP message. In this conversion process, the sensor network gateway adds *VarBind* to the *VarBindList*. The value of this *VarBind* can be acquired from the source address of the received sensor network management protocol message or from a mapping table managed by the ALG in the sensor network gateway.
+
+The ALG in the sensor network gateway also performs object identifiers (OIDs) conversion between the sensor network management protocol messages and SNMP messages (see clause 9 and Appendix I).
+
+## 8.2 Application level gateway database
+
+The sensor network gateway should maintain an ALG database. It is constructed with the information listed below for every SNMP message from the SNMP manager in order to perform protocol and OID translation between the SNMP and the sensor network management protocol.
+
+- Request ID sequence number (generated by ALG)
+- IP header (from SNMP message)
+- UDP header (from SNMP message)
+- Common SNMP header (from SNMP message)
+- Get/set header (from SNMP message)
+- Variable binding list (from SNMP message)
+
+The sequence number shall be used as a primary key in this ALG database.
+
+## 8.3 Translation from an SNMP to a sensor network management protocol message
+
+Figure 4 shows the operational procedure of the sensor network gateway when it receives an SNMP message from an SNMP manager.
+
+![Diagram illustrating the translation from an SNMP message to a sensor network management protocol message. The diagram shows the structure of an SNMP message (IP header, UDP header, SNMP common header, SNMP PDU) and an ALG database table. Arrows indicate the mapping of fields from the SNMP message to the sensor network management protocol message.](af7916c89a458fdab6c3f443217388ae_img.jpg)
+
+The diagram illustrates the translation process from an SNMP message to a sensor network management protocol message. It shows the structure of an SNMP message and an ALG database table.
+
+**SNMP Message Structure:**
+
+- IP header:** Contains Source IP address and Destination IP address.
+- UDP header:** (Empty in this diagram)
+- SNMP common header:** (Empty in this diagram)
+- SNMP PDU:** Contains Request ID, Name, and Value.
+- VarBindList:** A list of variable bindings, each containing Name and Value.
+- First VarBind:** The first variable binding in the VarBindList.
+
+**ALG Database Table:**
+
+| Keys            | Contents                |
+|-----------------|-------------------------|
+| Sequence number | [Sequence number field] |
+|                 |                         |
+|                 |                         |
+|                 |                         |
+
+**Sensor Network Management Protocol Message Structure:**
+
+- Header:** Contains Source sensor ID, Destination sensor ID, and Sequence number.
+- VarBindList:** Contains Name and Value.
+
+Arrows indicate the mapping of fields from the SNMP message to the sensor network management protocol message:
+
+- The Request ID from the SNMP PDU is mapped to the Sequence number field in the Header.
+- The Name and Value from the First VarBind are mapped to the Destination sensor ID and Sequence number fields in the Header.
+- The Name and Value from the other VarBinds are mapped to the Name and Value fields in the VarBindList.
+
+Diagram illustrating the translation from an SNMP message to a sensor network management protocol message. The diagram shows the structure of an SNMP message (IP header, UDP header, SNMP common header, SNMP PDU) and an ALG database table. Arrows indicate the mapping of fields from the SNMP message to the sensor network management protocol message.
+
+H.641(12)\_F04
+
+**Figure 4 – Translation from an SNMP message to a sensor network management protocol message**
+
+When the sensor network gateway receives an SNMP message from an SNMP manager, it generates a sequence number to be used as the request ID in the sensor network management protocol message and records this sequence number and the whole message into an ALG database. Then it creates a sensor network management protocol message. It copies the sequence number in the ALG database into the sequence number field of the sensor network management protocol message. It copies the value of the first *VarBind* into the destination sensor ID field of the sensor network management protocol message. Then it copies the *VarBindList* except for the first one into the sensor network management protocol message. When it copies object identifiers in the *VarBindList*, base OID should be removed (see clause 9 and Appendix I).
+
+The sensor network management protocol message should include a request ID field. If this field does not use the same format with an SNMP message, then the sensor network gateway also maintains mapping information between the request ID from the SNMP message and request ID from the sensor network management protocol message.
+
+## 8.4 Translation from a sensor network management protocol to an SNMP message
+
+Figure 5 shows the operational procedure of the sensor network gateway when it receives a sensor network management protocol message from a sensor network management protocol agent.
+
+![Diagram illustrating the translation from a sensor network management protocol message to an SNMP message. The diagram shows a 'Sensor network management protocol message' with fields: Source sensor ID, Destination sensor ID, ..., Sequence number, ..., Name, Value, .... A 'Lookup' arrow points from the 'Sequence number' field to an 'ALG database'. The 'ALG database' has a table with 'Keys' and 'Contents'. The 'Keys' column contains 'Sequence number'. The 'Contents' column contains a row of small squares. A dashed line connects the 'Sequence number' key to a row in the 'Contents' column. Below the 'ALG database' is a row of fields: Source IP address, Destination IP address, ..., Request ID, ..., Name, Value, Name, Value, .... Arrows point from the 'Source sensor ID', 'Destination sensor ID', 'Sequence number', 'Name', and 'Value' fields of the 'Sensor network management protocol message' to the 'Source IP address', 'Destination IP address', 'Request ID', 'Name', and 'Value' fields of the 'SNMP message' respectively. The 'SNMP message' is composed of an 'IP header' (containing Source IP address and Destination IP address), a 'UDP header', an 'SNMP common header', and an 'SNMP PDU'. The 'SNMP PDU' contains a 'First VarBind' and a 'VarBindList'. The 'VarBindList' contains 'Name' and 'Value' pairs. The 'Request ID' is also part of the 'SNMP PDU'. The diagram is labeled H.641(12)_F05.](4801720824e4b5e2361a5564f91cfb70_img.jpg)
+
+H.641(12)\_F05
+
+Diagram illustrating the translation from a sensor network management protocol message to an SNMP message. The diagram shows a 'Sensor network management protocol message' with fields: Source sensor ID, Destination sensor ID, ..., Sequence number, ..., Name, Value, .... A 'Lookup' arrow points from the 'Sequence number' field to an 'ALG database'. The 'ALG database' has a table with 'Keys' and 'Contents'. The 'Keys' column contains 'Sequence number'. The 'Contents' column contains a row of small squares. A dashed line connects the 'Sequence number' key to a row in the 'Contents' column. Below the 'ALG database' is a row of fields: Source IP address, Destination IP address, ..., Request ID, ..., Name, Value, Name, Value, .... Arrows point from the 'Source sensor ID', 'Destination sensor ID', 'Sequence number', 'Name', and 'Value' fields of the 'Sensor network management protocol message' to the 'Source IP address', 'Destination IP address', 'Request ID', 'Name', and 'Value' fields of the 'SNMP message' respectively. The 'SNMP message' is composed of an 'IP header' (containing Source IP address and Destination IP address), a 'UDP header', an 'SNMP common header', and an 'SNMP PDU'. The 'SNMP PDU' contains a 'First VarBind' and a 'VarBindList'. The 'VarBindList' contains 'Name' and 'Value' pairs. The 'Request ID' is also part of the 'SNMP PDU'. The diagram is labeled H.641(12)\_F05.
+
+**Figure 5 – Translation from a sensor network management protocol message to an SNMP message**
+
+When the sensor network gateway receives a sensor network management protocol message from a sensor node, it extracts the sequence number and looks up the original SNMP message from the ALG database. Then it creates a new SNMP message. It copies the destination IP address of the original SNMP message into the source IP address field. It then copies the source IP address of the original SNMP message into the destination IP address field. Then it copies the request ID and the first *VarBind*. It copies the *VarBindList* from the sensor network management protocol message into the *VarBindList* of the new SNMP message. When it copies the OID in the *VarBindList*, base OID should be added (see clause 9 and Appendix I).
+
+## 8.5 Consideration of the sensor network gateway for supporting IP-based sensor networks
+
+In case an IP-based sensor network is deployed (e.g. 6LoWPAN), the sensor network gateway (6LowPAN gateway) can be expected to inspect the data packets traversing the sensor network gateway. If the destination IP address of an IP header of an SNMP message is the IP address of the sensor node that resides under the sensor network gateway, the conversion of an SNMP message described in clause 8.3 is not needed. However, the sensor network gateway can perform TCP/UDP header compression and SNMP optimizations.
+
+When the sensor network gateway receives an SNMP message that is bound for the sensor network manager, the sensor network gateway may perform TCP/UDP header de-compression and SNMP message re-storing if TCP/UDP header compression and SNMP optimizations are performed on the received SNMP message.
+
+# **9 Object identifier allocation for MIB and object identifier translation between SNMP and sensor network management protocols**
+
+In SNMP, managed objects are identified by OIDs [b-ITU-T X.660] that are relatively long byte strings to be transferred on a sensor network. Considering the low data rate of sensor networks, relative OIDs are used in sensor network management protocols so as to identify managed objects relative to the base OID {itu-t(0) recommendation(0) h(8) h641(641) sensor-network-mgt(2) n} (see Annex A).
+
+When a sensor network gateway translates an SNMP message into a sensor network management protocol message, the sensor network gateway can remove the base OID from the OID for MIB in *VarBind*. When a sensor network gateway translates a sensor network management protocol message into an SNMP message, the sensor network gateway inserts the base OID in front of the OID of the MIB in *VarBind* (see Appendix I).
+
+# Annex A
+
+## Object identifier assignments
+
+(This annex forms an integral part of this Recommendation.)
+
+Table A.1 lists the assignment of OIDs defined for use by this Recommendation.
+
+**Table A.1 – Object identifier assignments**
+
+| Object Identifier Value                                                                  | Description                                                                                                                                                                                                                                                                                                                                   |
+|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| {itu-t(0) recommendation(0) h(8)<br>h641(641) sensor-network-mgt(2)<br>ieee-802-15-4(1)} | This OID is used to indicate that the sensor network conforms to [b-IEEE 802.15.4].<br>Subsequent arcs of this node are identical to the identifiers of PHY and MAC PIB attributes defined in [b-IEEE 802.15.4].                                                                                                                              |
+| {itu-t(0) recommendation(0) h(8)<br>h641(641) sensor-network-mgt(2)<br>zigbee(2)}        | This OID is used to indicate that the sensor network conforms to [b-ZigBee Specification].<br>Subsequent arcs of this node are identical to the identifiers of the network layer information base, application layer information base and security-related application layer information base attributes defined in [b-ZigBee Specification]. |
+
+# Appendix I
+
+## Example of object identifier translation
+
+(This annex forms an integral part of this Recommendation.)
+
+Figure I.1 shows the translation of an OID in a sensor network gateway.
+
+![Sequence diagram showing the translation of an OID in a sensor network gateway between a Sensor node, Sensor network gateway, and Sensor network manager.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg)
+
+```
+sequenceDiagram
+    participant SN as Sensor node
+    participant SNG as Sensor network gateway
+    participant SNM as Sensor network manager
+
+    SNM->>SNG: GetRequest{{0 0 8 641 2 2 150}, NodeID}, {{0 0 8 641 2 2 132}, NULL}}
+    SNG->>SN: GetRequest{{2 132}, NULL}
+    SN-->>SNG: GetResponse {{2 132}, value}
+    SNG-->>SNM: GetResponse{{0 0 8 641 2 2 150}, NodeID}, {{0 0 8 641 2 2 132}, value}}
+```
+
+The diagram illustrates the translation of an Object Identifier (OID) in a sensor network gateway. It shows three entities: a Sensor node, a Sensor network gateway, and a Sensor network manager. The sequence of messages is as follows: 1. The Sensor network manager sends a *GetRequest* message to the Sensor network gateway. The message contains a base OID `{{0 0 8 641 2 2 150}, NodeID}` and a relative OID `{{0 0 8 641 2 2 132}, NULL}`. 2. The Sensor network gateway sends a *GetRequest* message to the Sensor node. The message contains the relative OID `{{2 132}, NULL}`. 3. The Sensor node sends a *GetResponse* message to the Sensor network gateway. The message contains the relative OID `{{2 132}, value}`. 4. The Sensor network gateway sends a *GetResponse* message to the Sensor network manager. The message contains the base OID `{{0 0 8 641 2 2 150}, NodeID}` and the translated relative OID `{{0 0 8 641 2 2 132}, value}`. The diagram is labeled H.641(12)\_FB.1 in the bottom right corner.
+
+Sequence diagram showing the translation of an OID in a sensor network gateway between a Sensor node, Sensor network gateway, and Sensor network manager.
+
+**Figure I.1 – Example of object identifier translation**
+
+In Figure I.1, the sensor network is a ZigBee sensor network. When the sensor network manager wants to get the `nwkMaxChildren` of a ZigBee node, it sends a *GetRequest* message to the sensor network gateway with OID `{itu-t(0) recommendation(0) h(8) h641(641) sensor-network-mgt(2) zigbee(2) nwkMaxChildren(132)}` in a *VarBind*. When the sensor network gateway receives an SNMP message from the sensor network manager, it removes the base OID so as to create the relative OID `{zigbee(2) nwkMaxChildren(132)}` for the sensor network management protocol message.
+
+NOTE – The OID `{itu-t(0) recommendation(0) h(8) h641(641) sensor-network-mgt(2) zigbee(2) nwkNetworkAddress(150)}` is allocated for `nwkNetworkAddress` of the ZigBee node and this is a 16-bit address used in a ZigBee network.
+
+When the sensor network gateway receives a sensor network management protocol message from a sensor node, it inserts the base OID in front of the relative OID `{zigbee(2) nwkNetworkAddress(150)}` so as to create the full OID `{itu-t(0) recommendation(0) h(8) h641(641) sensor-network-mgt(2) zigbee(2) nwkMaxChildren(132)}` for the sensor network management protocol message.
+
+# Bibliography
+
+- [b-ITU-T X.660] Recommendation ITU-T X.660 (2011) | ISO/IEC 9834-1:2012, *Information technology – Procedures for the operation of object identifier registration authorities: General procedures and top arcs of the international object identifier tree.*
+- [b-ITU-T X.711] Recommendation ITU-T X.711 (1997) | ISO/IEC 9596-1:1997, *Information technology – Open Systems Interconnection – Common Management Information Protocol: Specification.*
+- [b-IEEE 802.15.4] IEEE 802.15.4 (2006), *IEEE Standard for Information technology – Telecommunications and information exchange between systems – Local and metropolitan area networks – Specific requirements, Part 15.4: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Low-Rate Wireless Personal Area Networks (WPANs).*
+- [b-ZigBee Specification] ZigBee Document 053474r17 (2008), *ZigBee Specification.*
+
+
+
+## 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-L.1602-201606-I_PDF-E/raw.md

@@ -0,0 +1,589 @@
+
+
+# ITU-T
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+## Y.4902/L.1602
+
+(06/2016)
+
+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 – Evaluation  
+and assessment
+
+SERIES L: ENVIRONMENT AND ICTS, CLIMATE CHANGE, E-  
+WASTE, ENERGY EFFICIENCY; CONSTRUCTION,  
+INSTALLATION AND PROTECTION OF CABLES AND OTHER  
+ELEMENTS OF OUTSIDE PLANT
+
+Internet of things and smart cities and communities – Evaluation  
+and assessment
+
+---
+
+**Key performance indicators related to the  
+sustainability impacts of information and  
+communication technology in smart sustainable  
+cities**
+
+Recommendation ITU-T Y.4902/L.1602
+
+# 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
+
+|                                                         |                      |
+|---------------------------------------------------------|----------------------|
+| 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        |
+| 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        |
+| <b>Evaluation and assessment</b>                        | <b>Y.4900–Y.4999</b> |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+# Recommendation ITU-T Y.4902/L.1602
+
+# Key performance indicators related to the sustainability impacts of information and communication technology in smart sustainable cities
+
+## Summary
+
+Recommendation ITU-T Y.4902/L.1602 gives a general guidance to cities and provide the definitions of key performance indicators (KPIs) related to the sustainability impact of information and communication technology (ICT) in the context of smart sustainable cities (SSCs).
+
+This Recommendation is one of series of the Recommendations and Supplements that define KPIs. The series of KPI definitions documents also include:
+
+- Recommendation ITU-T Y.4900/L.1600 on overview of key performance indicators (KPIs) in smart sustainable cities.
+- Recommendation ITU-T Y.4901/L.1601 on key performance indicators (KPIs) related to the use of information and communication technology (ICT) in smart sustainable cities. This Recommendation lists the KPIs used for ICT use in SSC.
+- Supplement ITU-T Y. Suppl. 39 on key performance indicators (KPIs) for smart sustainable cities. This document provides information regarding KPIs and evaluation index systems of smart cities, KPIs of sustainable cities, etc.
+
+## History
+
+| Edition | Recommendation      | Approval   | Study Group | Unique ID*                                                                |
+|---------|---------------------|------------|-------------|---------------------------------------------------------------------------|
+| 1.0     | ITU-T Y.4902/L.1602 | 2016-06-06 | 5           | <a href="http://handle.itu.int/11.1002/1000/12662">11.1002/1000/12662</a> |
+
+## Keywords
+
+Cities, information communication technologies (ICTs), key performance indicators (KPIs), metrics and evaluation, smart sustainable cities (SSCs), sustainability impacts.
+
+---
+
+\* 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.....                                                         | 2           |
+| 3 Definitions .....                                                       | 2           |
+| 3.1 Terms defined elsewhere .....                                         | 2           |
+| 3.2 Terms defined in this Recommendation .....                            | 3           |
+| 4 Abbreviations and acronyms .....                                        | 3           |
+| 5 General principles for selecting key performance indicators (KPIs)..... | 3           |
+| 6 Key performance indicators.....                                         | 3           |
+| 6.1 Sub-dimensions of KPIs .....                                          | 3           |
+| 6.2 Key performance indicators of SSC .....                               | 4           |
+| Appendix I – Additional indicators.....                                   | 10          |
+| Appendix II – UN-Habitat city prosperity index .....                      | 12          |
+| Bibliography.....                                                         | 14          |
+
+
+
+# **Recommendation ITU-T Y.4902/L.1602**
+
+## **Key performance indicators related to the sustainability impacts of information and communication technology in smart sustainable cities**
+
+## **1 Scope**
+
+This Recommendation forms part of a series of Recommendations and Supplements focusing on the key performance indicators (KPIs) for smart sustainable cities (SSCs). It specifically provides the KPIs related to information and communication technology (ICT) impacts on city sustainability in the context of SSCs. Evaluating these indicators can help cities as well as their stakeholders understand the extent to which they may be perceived as SSC. The Recommendation describes applicability of KPIs, principles and dimensions as well as the definitions of corresponding indicators. To fit into the overall framework of city indicators the present Recommendation re-uses the categorization of UN Habitat's City Prosperity Index.
+
+The sustainability of a smart city is based on four main aspects:
+
+- Economic: The ability to generate income and employment for the livelihood of the inhabitants.
+- Social: The ability to ensure that the welfare (safety, health, education) of the citizens can be equally delivered despite differences in class, race or gender.
+- Environmental: The ability to protect future quality and reproducibility of natural resources.
+- Governance: The ability to maintain social conditions of stability, democracy, participation, and justice.
+
+This Recommendation can be utilized by:
+
+- Cities and municipal administrations, including the SSC-relevant policy-making organizations, and government sectors, enabling them to develop strategies and understand the progress related to the use of ICT for making cities smarter and more sustainable.
+- City residents and their non-profit organizations, enabling them to understand the development and progress of SSCs with respect to the impact of ICT.
+- Development and operation organizations of SSC, including planning units, SSC-related producers and service providers, operation and maintenance organizations, helping them to fulfil the tasks of sharing information related to the use of ICT and its impact on the sustainability of cities.
+- Evaluation agencies and academia, supporting them in selection of relevant KPIs for assessing the contribution from ICT in the development of SSC.
+
+The intention of identifying the KPIs is to establish the criteria to evaluate ICT's contributions in making cities smarter and more sustainable, and to provide the cities with the means for self-assessments. It is desirable that cities can quantify their achievement according to their goals.
+
+The ICT solutions include ICT goods, networks and services as well as ICT projects. An ICT project is defined as a set of activities that uses mainly ICT goods, networks and services to implement a specific task. At a city level, ICT projects particularly target the deployment of ICT in different parts of society to improve the sustainability performance in SSC. The KPIs can be used to assess the city sustainability before and after the implementation of ICT solutions.
+
+This Recommendation lists the core indicators that are chosen to be applicable for all cities. The goals for moving towards increased smartness and sustainability differs between cities. Thus, based on their population growth, geographical locations, environmental conditions, demography etc., the cities can also select appropriate indicators among those listed in Appendix I and/or add new ones.
+
+This Recommendation is applicable for both cities and city regions, which could be organized in different ways:
+
+- A single city organized as one or more administrative units, or
+- A union of cities in the neighbouring area that can share some 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 Y.4900] Recommendation ITU-T Y.4900/L.1600 (2015), *Overview of key performance indicators in smart sustainable cities*.
+- [ITU-T Y.4901] Recommendation ITU-T Y.4901/L.1601 (2015), *Key performance indicators related to the use of information and communication technology in smart sustainable cities*.
+- [ITU-T Y-Sup.39] ITU-T Y-series Recommendations – Supplement 39 (2015), *ITU-T Y.4900 Series – Key performance indicators definitions for smart sustainable cities*.
+- [ISO 37120] ISO 37120:2014, *Sustainable development of communities – Indicators for city services and quality of life*.
+
+## 3 Definitions
+
+### 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 city** [ITU-T Y.4900]: A urban geographical area with one (or several) local government and planning authorities.
+
+**3.1.2 ICT companies** [ITU-T Y.4901]: Companies that provide products and/or services with respect to information and communication technologies.
+
+**3.1.3 knowledge economy** [b-OECD KE]: Economies which are directly based on the production, distribution and use of knowledge and information.
+
+**3.1.4 smart sustainable city** [ITU-T Y.4900]: A smart sustainable city is an innovative city that uses information and communication technologies (ICTs) and other means to improve quality of life, efficiency of urban operation and services and competitiveness, while ensuring that it meets the needs of present and future generations with respect to economic, social, environmental, as well as cultural aspects.
+
+NOTE – City competitiveness refers to policies, institutions, strategies and processes that determine the city's sustainable productivity.
+
+### 3.2 Terms defined in this Recommendation
+
+None.
+
+## 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+|            |                                                  |
+|------------|--------------------------------------------------|
+| AIDS       | Acquired Immune Deficiency Syndrome              |
+| HIV        | Human Immunodeficiency Virus infection           |
+| HLY        | Healthy Life Years                               |
+| ICT        | Information and Communication Technology         |
+| KPI        | Key Performance Indicator                        |
+| PM10       | Particulate Matter up to 10 micrometres in size  |
+| PM2.5      | Particulate Matter up to 2.5 micrometres in size |
+| QoL        | Quality of Life                                  |
+| SSC        | Smart Sustainable City                           |
+| UN-Habitat | United Nations Human Settlements Programme       |
+
+## 5 General principles for selecting key performance indicators (KPIs)
+
+The selection of KPIs is based on the following principles:
+
+- **Comprehensiveness:** The set of indicators should cover all the aspects of SSC. The indicators of evaluation should be aligned to the measured subject, i.e., ICT and its impact on the sustainability of cities. The index system should reflect the level of general development in a certain aspect.
+- **Comparability:** The KPIs should be defined in a way that data can be compared scientifically between different phases of urban development, which means the KPIs should be comparable over time and space for the same city. It should also be possible to extend and amend the set of KPIs according to the actual development.
+- **Availability:** The KPIs should be quantitative and the historic and current data should be either available or easy to collect.
+- **Independence:** The KPIs in the same dimension should be independent or almost-orthogonal i.e., overlap of the KPIs should be avoided as much as possible.
+- **Simplicity:** The concept of each indicator should be simple and easy to understand. Also the calculation of the associated data should be intuitive and simple.
+- **Timeliness:** The ability to produce KPIs with respect to emerging issues in SSC construction.
+
+## 6 Key performance indicators
+
+### 6.1 Sub-dimensions of KPIs
+
+The sub-dimensions for each dimension are recorded in Table 1. These have been tailored<sup>1</sup> from Table 1 of [ITU-T Y.4900].
+
+---
+
+<sup>1</sup> Note that this list only contains the sub-categories for which indicators are defined in this Recommendation. For a total set of sub-categories refer to [ITU-T Y.4900].
+
+In Table 1, each dimension is identified by the letter Dx. The sub-dimensions are then classified by the label Dx.y where x denotes the dimension and y maps to sub-dimension.
+
+**Table 1 – Sub-dimension of KPIs**
+
+| <b>Dimension label</b> | <b>Dimension</b>             | <b>Sub-dimension label</b> | <b>Sub-dimension</b>                                                |
+|------------------------|------------------------------|----------------------------|---------------------------------------------------------------------|
+| D2                     | Environmental sustainability | D2.1                       | Air quality                                                         |
+|                        |                              | D2.2                       | CO <sub>2</sub> emissions                                           |
+|                        |                              | D2.3                       | Energy                                                              |
+|                        |                              | D2.5                       | Water, soil and noise                                               |
+| D3                     | Productivity                 | D3.1                       | Capital investment                                                  |
+|                        |                              | D3.2                       | Employment                                                          |
+|                        |                              | D3.3                       | Inflation                                                           |
+|                        |                              | D3.5                       | Savings                                                             |
+|                        |                              | D3.6                       | Export/import                                                       |
+|                        |                              | D3.7                       | Household income/consumption                                        |
+|                        |                              | D3.8                       | Innovation                                                          |
+| D4                     | Quality of life              | D4.1                       | Education                                                           |
+|                        |                              | D4.2                       | Health                                                              |
+|                        |                              | D4.3                       | Safety/security public place                                        |
+| D5                     | Equity and social inclusion  | D5.1                       | Inequity of income/consumption (Gini coefficient)                   |
+|                        |                              | D5.2                       | Social and gender inequity of access to services and infrastructure |
+|                        |                              | D5.3                       | Openness and public participation                                   |
+| D6                     | Physical infrastructure      | D6.1                       | Infrastructure/connection to services – piped water                 |
+|                        |                              | D6.2                       | Infrastructure/connection to services – sewage                      |
+|                        |                              | D6.3                       | Infrastructure/connection to services – electricity                 |
+|                        |                              | D6.6                       | Infrastructure/connection to services – health infrastructure       |
+|                        |                              | D6.7                       | Infrastructure/connection to services – transport                   |
+
+### 6.2 Key performance indicators of SSC
+
+This clause defines the core indicators applicable for all cities.
+
+Each indicator is labelled (Ix.y.z), where (i) x denotes the dimension, (ii) y, the sub-dimension, and (iii) z, the indicator.
+
+NOTE – The numbering of indicator Ix.y.z of this Recommendation follows that of [ITU-T Y.4901].
+
+The indicators listed in Appendix I are provided as additional indicators for consideration. Cities can select appropriate ones among those, and/or add new indicators, in order to evaluate the sustainability impacts related to the use of ICT.
+
+NOTE 1 – This Recommendation identifies the KPIs related to ICT impacts on city sustainability in the context of SSC but does not provide any quantification method. Quantification methods will be provided separately.
+
+NOTE 2 – This Recommendation contains ICT specific indicators and general indicators<sup>2</sup> which describe the sustainability impacts in the context of smart sustainable cities. Due to the complexity of cities and the wide range of factors that impact citizens' behaviour, impacts from ICT could in many cases mainly be tracked for specific projects or initiatives. For this reason, the general city level KPIs are defined for areas where ICT could have an impact, though it is not the only change lever. Thus, to understand the ICT impact on the general KPIs, depth analysis is needed based on a broad understanding of the general city development.
+
+NOTE 3 – Although convenience and comfort is an important aspect of SSC, there are no KPIs defined for sub-dimension D4.4 Convenience and comfort [ITU-T Y.4900]. However, it is important that ICT projects are designed in a way that is convenient for the intended users. Therefore it is good to combine the use of KPIs with other assessment methods to understand the satisfaction level linked to the use of such projects and how these KPIs develop over time.
+
+NOTE 4 – In this Recommendation the e-service concept (e.g., e-health and e-governance, etc.) is used in an inclusive way and refers to both wired and wireless services that benefit cities and city inhabitants. The mobile wireless services could also be referred to as m-services (e.g., m-health, m-banking, etc.). These ICT services and goods can be also collectively termed as smart services (e.g., smart grid, smart lighting) and smart goods (e.g., smart meters). In some cases the smart service / smart goods concept may be used instead of e-service if this terminology is more widely adopted for the referred service or goods.
+
+NOTE 5 – In this Recommendation the term city inhabitant is used to refer to the people living in the city.
+
+#### 6.2.1 Environmental sustainability
+
+This clause lists the core indicators defined for environmental sustainability.
+
+There are ten indicators in this dimension, covering *air pollution, GHG emissions, renewable energy, energy saving in households, environment perception, quality of water resources, recycling of waste, noise and soil pollution, green areas, etc.*
+
+| Sub-dimension                       | Indicator                                      | Description                                                                                                                                                                                                                                                                                        |
+|-------------------------------------|------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| D2.1 Air quality                    | I2.1.2 Air pollution intensity                 | Intensity of particles and toxic substances. (*)<br>NOTE – This includes toxic substances and particles such as PM10 and PM2.5.                                                                                                                                                                    |
+| D2.2 CO <sub>2</sub> emissions (**) | I2.2.1 GHG emissions                           | Amount of GHG emissions per capita. (*)<br>NOTE – It is preferred to distinguish between emissions emerging from industrial (manufacturing, construction), commercial, household, transport, and waste disposal, etc.                                                                              |
+| D2.3 Energy                         | I2.3.1 Use of alternative and renewable energy | Proportion of renewable energy consumed in the city. (*)<br>NOTE – Renewable energy sources include geothermal, solar thermal, solar voltaic, hydro, wind, and combustible renewable sources and waste (composed of solid biomass, liquid biomass, bio-gas, industrial waste and municipal waste). |
+|                                     | I2.3.2 Energy saving in households             | Energy saving in households compared to a baseline. (*)                                                                                                                                                                                                                                            |
+
+<sup>2</sup> The general indicators are marked (\*).
+
+| Sub-dimension                                                                                                                                                                                                                                                                                                            | Indicator                                  | Description                                                                                                                                                                                                                   |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|                                                                                                                                                                                                                                                                                                                          |                                            | NOTE – The baseline may be either a previous measurement or a reference value.<br>NOTE – It would be preferred to distinguish between households with and without smart meters, and with and without home automation systems. |
+| D2.5 Water, soil and noise                                                                                                                                                                                                                                                                                               | I2.5.3 Quality of city water resources     | Quality of water resources (rivers, lakes, etc.). (*)<br>NOTE – Pollution of water resources includes (but is not limited to) acidity, organic, floatables, alga, chemical substances and bacteria, etc.                      |
+|                                                                                                                                                                                                                                                                                                                          | I2.5.4 Recycling of waste                  | Proportion of waste recycled compared to total collected waste. (*)                                                                                                                                                           |
+|                                                                                                                                                                                                                                                                                                                          | I2.5.5 Exposure to noise                   | Proportion of the city inhabitants with noise levels above international/national exposure limits at home. (*)<br>NOTE – Noise is measured as sound pressure in accordance with relevant international/national standards.    |
+|                                                                                                                                                                                                                                                                                                                          | I2.5.6 Soil pollution avoidance            | Proportion of soil pollution incidents with successful early warning and emergency detection of heavy metal, chemicals, acid, etc. through ICT.                                                                               |
+|                                                                                                                                                                                                                                                                                                                          | I2.5.7 Green areas surface                 | Proportion of municipal territory allocated to publicly accessible green areas. (*)                                                                                                                                           |
+|                                                                                                                                                                                                                                                                                                                          | I2.5.8 Perception on environmental quality | Proportion of city inhabitants satisfied with the urban environment. (*)                                                                                                                                                      |
+| NOTE 1 – Indicators marked by (*) are not ICT specific, but indicators focusing on general city sustainability.<br>NOTE 2 – This sub-dimension marked by (**) looks into the CO <sub>2</sub> -e/GHG emissions of the city where "-e" is "equivalent" and all other greenhouse gases are converted into CO <sub>2</sub> . |                                            |                                                                                                                                                                                                                               |
+
+#### 6.2.2 Productivity
+
+This clause lists the core indicators defined for productivity and economic sustainability.
+
+There are seven indicators in this dimension, covering *expenditure of ICT to improve industry productivity, service industry employment, saving, city export/import, household ICT expenditures, ICT investment, and ICT related patents, etc.*
+
+| Sub-dimension           | Indicator                                               | Description                                                                                                                                                                                                                                                               |
+|-------------------------|---------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| D3.1 Capital investment | I3.1.3 Improvement of industry productivity through ICT | Productivity enhancement in industry through ICT measured as the impact of ICT on value added per person employed.<br>NOTE 1 – This is the contribution from ICT investment.<br>NOTE 2 – Value added per person employed is generally referred to as labour productivity. |
+
+| Sub-dimension                                                                                                 | Indicator                                | Description                                                                                                                                                                                                                                                                                            |
+|---------------------------------------------------------------------------------------------------------------|------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| D3.2 Employment                                                                                               | I3.2.1 Service industry employment       | Proportion of employees working in service industry in the city compared with the total employed workforce. (*)                                                                                                                                                                                        |
+| D3.5 Savings                                                                                                  | I3.5.1 Saving rate                       | Proportion of total incomes for each household remaining after deducting consumption and expenditures. (*)                                                                                                                                                                                             |
+| D3.6 Export/import                                                                                            | I3.6.1 Knowledge-intensive export/import | Proportion of export/import of knowledge-intensive goods and services within a city compared to the total industrial export/import. (*)<br>NOTE 1 – Amount of export/import may be counted among cities, maybe in the same country.<br>NOTE 2 – In some cases data is only available at country level. |
+| D3.7 Household income/consumption                                                                             | I3.7.1 Household ICT expenditures        | Proportion of household expenditures related to ICT.                                                                                                                                                                                                                                                   |
+| D3.8 Innovation                                                                                               | I3.8.2 Investments in ICT innovation     | Proportion of private sector expenditures invested in ICT innovation.                                                                                                                                                                                                                                  |
+|                                                                                                               | I3.8.3 ICT related patents               | Number of ICT related patents granted per capita.                                                                                                                                                                                                                                                      |
+| NOTE – Indicators marked by (*) are not ICT specific, but indicators focusing on general city sustainability. |                                          |                                                                                                                                                                                                                                                                                                        |
+
+#### 6.2.3 Quality of life
+
+This clause lists the core indicators defined for Quality of Life (QoL).
+
+There are three indicators in this dimension, covering *student ICT availability, inhabitants' health status, and emergency process to improve safety and security*.
+
+| Sub-dimension                                                                                                 | Indicator                                      | Description                                                                                                                                                                                                                                |
+|---------------------------------------------------------------------------------------------------------------|------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| D4.1 Education                                                                                                | I4.1.2 Students ICT availability               | Proportion of students/pupils with access to ICT capabilities in school.<br>NOTE – ICT capabilities include Internet connectivity, computer labs, ICT modules, digital learning, etc.                                                      |
+| D4.2 Health                                                                                                   | I4.2.5 Healthy life years (HLY)                | Number of remaining years that a person of a certain age is expected to live without disability. (*)<br>NOTE – The emphasis is not exclusively on the length of life, as is the case for life expectancy, but also on the quality of life. |
+| D4.3 Safety/security public place                                                                             | I4.3.3 Disaster and emergencies alert accuracy | Proportion of disasters and emergencies with timely alerts. (*)<br>NOTE – Disasters may be natural or man-made. Emergencies concern incidents like kidnapping and missing people, etc.                                                     |
+| NOTE – Indicators marked by (*) are not ICT specific, but indicators focusing on general city sustainability. |                                                |                                                                                                                                                                                                                                            |
+
+#### 6.2.4 Equity and social inclusion<sup>3</sup>
+
+This clause lists the core indicators defined for equity and social inclusion.
+
+There are 4 indicators in this dimension, covering *income inequity, gender inequity, use of online services and perception on social inclusion, etc.*
+
+| Sub-dimension                                                                                                 | Indicator                             | Description                                                                                                                                                                                                         |
+|---------------------------------------------------------------------------------------------------------------|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| D5.1 Inequity of income/consumption (Gini coefficient)                                                        | I5.1.1 Income distribution            | Income distribution in accordance with Gini coefficient. (*)                                                                                                                                                        |
+| D5.2 Social and gender inequity of access to services and infrastructure                                      | I5.2.1 Gender income disparity        | Rate of income disparity between men and women. (*)<br>NOTE – Income has potential influence on equity of access to services and infrastructure.                                                                    |
+| D5.3 Openness and public participation                                                                        | I5.3.5 Use of online city services    | Proportion of city inhabitants using online public services and facilities (e.g., choice of schools, booking of public sports facilities, library services, etc.).<br>NOTE – This includes bookings, payments, etc. |
+|                                                                                                               | I5.3.6 Perception on social inclusion | Proportion of city inhabitants satisfied with the social inclusion. (*)<br>NOTE – Social inclusion usually refers to members of society feeling valued and important.                                               |
+| NOTE – Indicators marked by (*) are not ICT specific, but indicators focusing on general city sustainability. |                                       |                                                                                                                                                                                                                     |
+
+#### 6.2.5 Physical infrastructure<sup>4</sup>
+
+This clause lists the core indicators defined for the physical infrastructure.
+
+There are six indicators in this dimension, covering *piped water, sewage, electricity, health infrastructure, transport and road traffic.*
+
+| Sub-dimension                                             | Indicator                             | Description                                                  |
+|-----------------------------------------------------------|---------------------------------------|--------------------------------------------------------------|
+| D6.1 Infrastructure /connection to services – piped water | I6.1.4 Leakage in water supply system | Proportion of water leakage in the water supply system. (*)  |
+| D6.2 Infrastructure /connection to services – sewage      | I6.2.3 Sewage system coverage         | Proportion of households connected to the sewage system. (*) |
+
+<sup>3</sup> In general equity and inclusion in relation to ICT are hard to measure by defining specific indicators. Therefore, in addition to the indicators defined in dimension D5, cities are encouraged to disaggregate and analyse their data with respect to other aspects including gender, age, income and geographic location/area.
+
+<sup>4</sup> The number of various sensors (per capita) deployed in the city and accessibility to the public administration is very important.
+
+| <b>Sub-dimension</b>                                                                                          | <b>Indicator</b>                                | <b>Description</b>                                                                                                                                                                                                       |
+|---------------------------------------------------------------------------------------------------------------|-------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| D6.3 Infrastructure /connection to services – electricity                                                     | I6.3.2 Reliability of electricity supply system | Proportion of time during which electricity supply system works without outages. (*)                                                                                                                                     |
+| D6.6 Infrastructure /connection to services – health infrastructure                                           | I6.6.1 Availability of sporting facilities      | Number of sports training facilities per capita. (*)                                                                                                                                                                     |
+| D6.7 Infrastructure /connection to services – transport                                                       | I6.7.1 Use of public transport                  | Proportion of travellers utilizing public transportation compared to overall city population. (*)                                                                                                                        |
+|                                                                                                               | I6.7.2 Road traffic efficiency                  | Freedom from traffic congestion exposure. (*)<br>NOTE – Traffic congestion is measured in accordance with relevant international/national standards. For example, in terms of average speed of vehicle or average delay. |
+| NOTE – Indicators marked by (*) are not ICT specific, but indicators focusing on general city sustainability. |                                                 |                                                                                                                                                                                                                          |
+
+## Appendix I
+
+### Additional indicators
+
+(This appendix does not form an integral part of this Recommendation.)
+
+The indicators listed in the following table are provided as additional indicators for consideration. Cities can select appropriate ones among those, and/or add new indicators, to evaluate the contributions of ICT to their SSC goals. Each additional indicator is labelled (Ax.y.z), where (i) x denotes the dimension, (ii) y, the sub-dimension, and (iii) z, the indicator.
+
+| Sub-dimension                          | Indicator                                              | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|----------------------------------------|--------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| D2.2 CO <sub>2</sub> emissions (**)    | A2.2.1 GHG emissions per sector per capita             | GHG emissions per capita per sector including industrial (manufacturing, construction), commercial, household, transport, and waste disposal, etc. (*)                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| D2.3 Energy                            | A2.3.1 Electricity use for street lighting             | Electricity used for street lighting per capita. (*)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| D3.2 Employment                        | A3.2.1 Creative industry employment                    | Proportion of employees working in start-ups and creative industry in the city compared to the total employed workforce. (*)<br>NOTE – Creative industries refer to those ones that are based on individual creativity, skill and talent with the potential to create wealth and jobs through developing intellectual property. This includes thirteen sectors: advertising, architecture, the art and antiques market, crafts, design, designer fashion, film, interactive leisure software (i.e., video games), music, the performing arts, publishing, software, and television and radio. |
+| D3.3 Inflation                         | A3.3.1 Inflation rate                                  | A city's inflation rate is based on a projection of its Consumer Price Index, which measures the rise in prices of goods and services. (*)<br>NOTE – National inflation data may be used.<br>NOTE – A +2% inflation rate is regarded as a target or healthy inflation rate by major international banks.                                                                                                                                                                                                                                                                                      |
+| D4.2 Health                            | A4.2.1 Coverage of health insurance                    | Proportion of city inhabitants covered by health insurances. (*)<br>NOTE – Health insurances may be either private or provided by authorities.                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| D5.3 Openness and public participation | A5.3.2 Interest in online access to cultural resources | On-line visits to cultural resources per capita.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+| Sub-dimension                                                                                                                                                                                                                                                                                                            | Indicator                     | Description                                                                                                                     |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------|
+| D6.1 Infrastructure /connection to services – piped water                                                                                                                                                                                                                                                                | A6.1.2 Quality of piped water | Quality of water as supplied to end users. (*)<br>NOTE – Quality is impacted by both water treatments and distribution systems. |
+| NOTE 1 – Indicators marked by (*) are not ICT specific, but indicators focusing on general city sustainability.<br>NOTE 2 – This sub-dimension marked by (**) looks into the CO <sub>2</sub> -e/GHG emissions of the city where "-e" is "equivalent" and all other greenhouse gases are converted into CO <sub>2</sub> . |                               |                                                                                                                                 |
+
+## Appendix II
+
+### UN-Habitat city prosperity index
+
+(This appendix does not form an integral part of this Recommendation.)
+
+In the Wheel of Prosperity, as defined by UN-Habitat, the "spokes" are the five dimensions of prosperity: productivity, infrastructure development, quality of life, equity and social inclusion, and environmental sustainability.
+
+![Diagram of the UN-Habitat City Prosperity Index, known as the Wheel of Prosperity. It features a central blue circle labeled 'Government institutions laws and urban planning'. Five blue spokes radiate from this center, each labeled with a dimension of prosperity: 'Productivity' (top), 'Infrastructure' (top-right), 'Quality of life' (bottom-right), 'Equity and social inclusion' (bottom-left), and 'Environmental sustainability' (top-left). The outer rim of the wheel is a purple circle with the text 'URBAN PROSPERITY' repeated five times, once for each spoke. Double-headed orange arrows labeled 'Policy interactions' connect the central hub to each spoke. Double-headed purple arrows labeled 'Spoke interactions' connect the outer rim to each spoke. The entire diagram is set against a white background.](9b9d2abd741ed4bafe7f78f89961c663_img.jpg)
+
+URBAN PROSPERITY
+
+Spoke interactions
+
+Policy interactions
+
+Productivity
+
+URBAN PROSPERITY
+
+Spoke interactions
+
+Infrastructure
+
+Policy interactions
+
+Government institutions laws and urban planning
+
+Quality of life
+
+Policy interactions
+
+URBAN PROSPERITY
+
+Spoke interactions
+
+Equity and social inclusion
+
+Policy interactions
+
+URBAN PROSPERITY
+
+Spoke interactions
+
+Environmental sustainability
+
+Policy interactions
+
+URBAN PROSPERITY
+
+Spoke interactions
+
+L.1602(16)\_FII.1
+
+Diagram of the UN-Habitat City Prosperity Index, known as the Wheel of Prosperity. It features a central blue circle labeled 'Government institutions laws and urban planning'. Five blue spokes radiate from this center, each labeled with a dimension of prosperity: 'Productivity' (top), 'Infrastructure' (top-right), 'Quality of life' (bottom-right), 'Equity and social inclusion' (bottom-left), and 'Environmental sustainability' (top-left). The outer rim of the wheel is a purple circle with the text 'URBAN PROSPERITY' repeated five times, once for each spoke. Double-headed orange arrows labeled 'Policy interactions' connect the central hub to each spoke. Double-headed purple arrows labeled 'Spoke interactions' connect the outer rim to each spoke. The entire diagram is set against a white background.
+
+In the "City Prosperity Index" each dimension has its own index and it might be built up by a number of indices. The basic "City Prosperity Index" as reported in a publication consists of the following sub-indices and indicators:
+
+| Dimension                    | Definition/variables                                                                                                                                                                                                                                                                                                                                                                                  |
+|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Productivity                 | The productivity index is measured through the city product, which is composed of the variables capital investment, formal/informal employment, inflation, trade, savings, export/import, and household income/consumption. The city product represents the total output of goods and services (value added) produced by a city's population during a specific year.                                  |
+| Quality of life              | The quality of life index is a combination of four sub-indices: education, health, safety/security and public space. The sub-index education includes literacy, primary, secondary and tertiary enrolment. The sub-index health includes life expectancy, under-five mortality rates, HIV/AIDS, morbidity and nutrition variables.                                                                    |
+| Infrastructure development   | The infrastructure development index combines two sub-indices: one for infrastructure and another for housing.<br>The infrastructure sub-index includes: connection to services (piped water, sewage, electricity and ICT), waste management, knowledge infrastructure, health infrastructure, transport and road infrastructure. The housing sub-index includes building materials and living space. |
+| Environmental sustainability | The environmental sustainability index is made of four sub-indices: air quality (PM10), CO <sub>2</sub> emissions, energy and indoor pollution.                                                                                                                                                                                                                                                       |
+| Equity and social inclusion  | The equity and social inclusion index combines statistical measures of inequity of income/consumption (Gini coefficient) and social and gender inequity of access to services and infrastructure.                                                                                                                                                                                                     |
+
+## Reference
+
+UN Habitat report "State of the World's cities 2012/2013 Prosperity of Cities", Table 1.1.3, p. 18.
+
+There is also an extended "City Prosperity Index" with more indicators and a plan to include "Governance" as a sixth dimension. Furthermore, a specific work has been made on Streets as a driver for prosperity.
+
+UN Habitat (2013), *State of the World's Cities 2012/2013, Prosperity of Cities*: <http://www.unhabitat.org/pmss/listItemDetails.aspx?publicationID=3387>
+
+UN Habitat (2013), *Streets as Public Spaces and Drivers of Urban Prosperity*: <http://www.unhabitat.org/pmss/listItemDetails.aspx?publicationID=3513>
+
+## Bibliography
+
+- [b-FG-SSC KPIs metrics] FG-SSC deliverable, *Technical Report on metrics and evaluation of key performance indicators for smart sustainable cities.*
+- [b-FG-SSC overview] FG-SSC deliverable (2014), *Technical Report on an overview of smart sustainable cities and the role of information and communication technologies.*
+- [b-FG-SSC infrastructure] FG-SSC deliverable (2015), *Technical Report on overview of smart sustainable cities infrastructure.*
+- [b-FG-SSC security] FG-SSC deliverable (2015), *Technical Report on cyber-security, data protection and cyber-resilience in smart sustainable cities.*
+- [b-FG-SSC building] FG-SSC deliverable (2015), *Technical Report on smart sustainable buildings for smart sustainable cities.*
+- [b-FG-SSC water] FG-SSC deliverable (2014), *Technical Report on smart water management in cities.*
+- [b-FG-SSC management] FG-SSC deliverable (2015), *Technical Report on integrated management for smart sustainable cities.*
+- [b-FG-SSC stakeholders] FG-SSC deliverable (2015), *Technical Report on engaging stakeholders for smart sustainable cities.*
+- [b-ISO/TS 37151] ISO/TS 37151:2015, *Smart community infrastructures - Principles and requirements for performance metrics.*
+- [b-OECD KE] Organisation for Economic Co-operation and Development (1996), *The knowledge-based economy.*
+- [b-UN-Habitat report] UN-Habitat report (2013), *State of the World's cities 2012/2013 Prosperity of Cities.*
+
+## ITU-T L-SERIES RECOMMENDATIONS
+
+## **ENVIRONMENT AND ICTS, CLIMATE CHANGE, E-WASTE, ENERGY EFFICIENCY; CONSTRUCTION, INSTALLATION AND PROTECTION OF CABLES AND OTHER ELEMENTS OF OUTSIDE PLANT**
+
+|                                                       |             |
+|-------------------------------------------------------|-------------|
+| OPTICAL FIBRE CABLES                                  |             |
+| Cable structure and characteristics                   | L.100–L.124 |
+| Cable evaluation                                      | L.125–L.149 |
+| Guidance and installation technique                   | L.150–L.199 |
+| OPTICAL INFRASTRUCTURES                               |             |
+| Infrastructure including node element (except cables) | L.200–L.249 |
+| General aspects and network design                    | L.250–L.299 |
+| MAINTENANCE AND OPERATION                             |             |
+| Optical fibre cable maintenance                       | L.300–L.329 |
+| Infrastructure maintenance                            | L.330–L.349 |
+| Operation support and infrastructure management       | L.350–L.379 |
+| Disaster management                                   | L.380–L.399 |
+| PASSIVE OPTICAL DEVICES                               | L.400–L.429 |
+| MARINIZED TERRESTRIAL CABLES                          | L.430–L.449 |
+
+*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                                                                                |
+| 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        | Cable networks and transmission of television, sound programme and other multimedia signals                                                                      |
+| Series K        | Protection against interference                                                                                                                                  |
+| <b>Series L</b> | <b>Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant</b> |
+| 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, Internet of Things and smart cities</b>                            |
+| Series Z        | Languages and general software aspects for telecommunication systems                                                                                             |

marked/Y/T-REC-Y.101-200003-I_PDF-E/raw.md

@@ -0,0 +1,740 @@
+
+
+![ITU logo: a globe with the letters ITU inside, and a lightning bolt striking the globe.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+ITU logo: a globe with the letters ITU inside, and a lightning bolt striking the globe.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+# ITU-T
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+# Y.101
+
+(03/2000)
+
+SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE  
+AND INTERNET PROTOCOL ASPECTS
+
+Global information infrastructure – General
+
+# --- **Global Information Infrastructure terminology: Terms and definitions**
+
+ITU-T Recommendation Y.101
+
+(Formerly CCITT Recommendation)
+
+---
+
+## ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE AND INTERNET PROTOCOL ASPECTS
+
+|                                                                    |                    |
+|--------------------------------------------------------------------|--------------------|
+| GLOBAL INFORMATION INFRASTRUCTURE                                  |                    |
+| <b>General</b>                                                     | <b>Y.100–Y.199</b> |
+| 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      |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## **ITU-T Recommendation Y.101**
+
+## **Global Information Infrastructure terminology: Terms and definitions**
+
+### **Summary**
+
+This ITU-T Recommendation contains the Global Information Infrastructure terminology.
+
+### **Source**
+
+ITU-T Recommendation Y.101 was prepared by ITU-T Study Group 13 (1997-2000) and approved under the WTSC Resolution 1 procedure on 10 March 2000.
+
+### FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. 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 Conference (WTSC), 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 WTSC 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.
+
+### 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, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2001
+
+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 access network .....                             | 1           |
+| 2 Access Network Interface (ANI).....              | 1           |
+| 3 access node.....                                 | 1           |
+| 4 adaptation unit.....                             | 1           |
+| 5 affordability.....                               | 1           |
+| 6 agent.....                                       | 2           |
+| 7 appliance .....                                  | 2           |
+| 8 application.....                                 | 2           |
+| 9 application process.....                         | 2           |
+| 10 Application Service Element (ASE) .....         | 2           |
+| 11 Application Service Object (ASO) .....          | 2           |
+| 12 Asymmetric Digital Subscriber Line (ADSL) ..... | 3           |
+| 13 ATM Transfer Capability (ATC).....              | 3           |
+| 14 availability.....                               | 3           |
+| 15 bitway.....                                     | 3           |
+| 16 broadcast .....                                 | 3           |
+| 17 Cable Distribution Network (CDN).....           | 3           |
+| 18 cell conformance .....                          | 3           |
+| 19 Cell Delay Variation (CDV) .....                | 4           |
+| 20 cell entry event.....                           | 4           |
+| 21 cell exit event.....                            | 4           |
+| 22 continuity check .....                          | 4           |
+| 23 compression .....                               | 4           |
+| 24 core network.....                               | 4           |
+| 25 cultural elements .....                         | 5           |
+| 26 Customer Premises Equipment (CPE).....          | 5           |
+| 27 decryption .....                                | 5           |
+| 28 domain .....                                    | 5           |
+| 29 Drop Distribution Interface (DDI) .....         | 5           |
+
+|                                                      | <b>Page</b> |
+|------------------------------------------------------|-------------|
+| 30 element.....                                      | 5           |
+| 31 emulation .....                                   | 6           |
+| 32 encryption .....                                  | 6           |
+| 33 Global Information Infrastructure (GII).....      | 6           |
+| 34 head end .....                                    | 6           |
+| 35 interoperability.....                             | 6           |
+| 36 interface.....                                    | 6           |
+| 37 Internet .....                                    | 7           |
+| 38 Inter-Network Interface (INI).....                | 7           |
+| 39 Intrinsic Burst Tolerance (IBT).....              | 7           |
+| 40 manageability .....                               | 7           |
+| 41 management system .....                           | 7           |
+| 42 media.....                                        | 7           |
+| 43 medium .....                                      | 8           |
+| 44 middleware.....                                   | 8           |
+| 45 network .....                                     | 8           |
+| 46 nomadicity.....                                   | 8           |
+| 47 Network-to-Network Interface type A (NNI-A) ..... | 8           |
+| 48 Network-to-Network Interface type B (NNI-B).....  | 8           |
+| 49 Peak Cell Rate (PCR) .....                        | 9           |
+| 50 player.....                                       | 9           |
+| 51 portability.....                                  | 9           |
+| 52 quality of service.....                           | 9           |
+| 53 reference point .....                             | 9           |
+| 54 reliability .....                                 | 9           |
+| 55 role .....                                        | 10          |
+| 56 segment .....                                     | 10          |
+| 57 service .....                                     | 10          |
+| 58 service node .....                                | 10          |
+| 59 service primitive .....                           | 10          |
+
+|                                                        | <b>Page</b> |
+|--------------------------------------------------------|-------------|
+| 60 service primitive; primitive.....                   | 10          |
+| 61 Sustainable Cell Rate (SCR).....                    | 10          |
+| 62 User-Network Interface (UNI).....                   | 11          |
+| 63 Very high speed Digital Subscriber Line (VDSL)..... | 11          |
+| 64 video.....                                          | 11          |
+| 65 video server.....                                   | 11          |
+
+# **Introduction**
+
+This ITU-T Recommendation provides the terms and definitions used in the Global Information Infrastructure.
+
+## **Global Information Infrastructure terminology: Terms and definitions**
+
+### **1 access network**
+
+*F: réseau d'accès*
+
+*S: red de acceso*
+
+An implementation comprising those entities (such as cable plant, transmission facilities, etc.) which provide the required transport bearer capabilities for the provision of telecommunications services between a *Service Node Interface* (SNI) and each of the associated *User-Network Interfaces* (UNIs).
+
+### **2 Access Network Interface (ANI)**
+
+*F: interface du réseau d'accès*
+
+*S: interfaz de red de acceso*
+
+An interface between a local switch and an *access network* within a local network.
+
+### **3 access node**
+
+*F: nœud d'accès*
+
+*S: nodo de acceso*
+
+The element of the access network containing centralized functions responsible for processing information flows in preparation for transport through the selected distribution network.
+
+### **4 adaptation unit**
+
+*F: adaptateur*
+
+*S: unidad de adaptación*
+
+The unit which converts from the native *On-Premise Interface* (OPI) to another interface more suitable for the given appliance.
+
+### **5 affordability**
+
+*F: prix abordable (accessibilité pécuniaire)*
+
+*S: asequibilidad*
+
+The cost effectiveness of the resources utilized by an enterprise/organization or consumer over a specified period of time.
+
+### **6 agent**
+
+*F: agent*
+
+*S: agente*
+
+An agent is an element that performs some task on behalf of some party (i.e. a user, machine, application, or another agent) rather than having the party itself perform the task.
+
+### **7 appliance**
+
+*F: appareil*
+
+*S: aparato*
+
+Generic term used to describe the terminal device employed by the service application. Telephones, TV sets, computers, etc. are examples of appliances.
+
+### **8 application**
+
+*F: application*
+
+*S: aplicación*
+
+A structured set of capabilities, which provide value-added functionality supported by one or more services.
+
+### **9 application process**
+
+*F: processus d'application*
+
+*S: proceso de aplicación*
+
+A sequence of operations that performs the information processing for a particular application.
+
+### **10 Application Service Element (ASE)**
+
+*F: élément de service d'application*
+
+*S: elemento de servicio de aplicación*
+
+A set of application functions that provide a capability for the interworking of application-entity invocations for a specific purpose; application-service elements are components of application-service objects.
+
+### **11 Application Service Object (ASO)**
+
+*F: objet de service d'application*
+
+*S: objeto de servicio de aplicación*
+
+A configuration of various groups of application service elements.
+
+### **12 Asymmetric Digital Subscriber Line (ADSL)**
+
+*F: ligne d'abonné numérique asymétrique*
+
+*S: línea de abonado digital asimétrica*
+
+A modem technology that converts twisted-pair telephone lines into access paths for multimedia and high-speed data communications. The bit rates transmitted in both directions are different.
+
+### **13 ATM Transfer Capability (ATC)**
+
+*F: capacité de transfert ATM*
+
+*S: capacidad de transferencia ATM*
+
+A set of ATM traffic control procedures, tailored to support a service with given traffic characteristics.
+
+### **14 availability**
+
+*F: disponibilité*
+
+*S: disponibilidad*
+
+The measure of the degree of access to a particular resource or set of resources.
+
+### **15 bitway**
+
+*F: connexion physique; route physique*
+
+*S: conexión física*
+
+All the associated physical *media* between a sender and a receiver of data.
+
+### **16 broadcast**
+
+*F: diffusion*
+
+*S: difusión*
+
+A unidirectional distribution of data from one point to many points.
+
+### **17 Cable Distribution Network (CDN)**
+
+*F: réseau de distribution par câble*
+
+*S: red de distribución por cable*
+
+A tree-structured network to transport a signal to appliances.
+
+### **18 cell conformance**
+
+*F: conformité d'une cellule*
+
+*S: conformidad de una célula*
+
+An algorithm that identifies cells that conform to negotiated traffic parameters and traffic control procedures at a standardized interface.
+
+### **19 Cell Delay Variation (CDV)**
+
+*F: variation du temps de propagation des cellules*
+
+*S: variación del retardo de célula*
+
+The variation of cell transfer delay between two given points of an ATM layer connection.
+
+### **20 cell entry event**
+
+*F: instant d'arrivée d'une cellule*
+
+*S: evento de llegada de célula*
+
+An event which occurs when an ATM cell crosses a measurement point entering the Switching or Signalling Node (SSN) or customer equipment (CEQ) from the attached transmission system.
+
+### **21 cell exit event**
+
+*F: instant de sortie d'une cellule*
+
+*S: evento de salida de célula*
+
+An event which occurs when an ATM cell crosses a measurement point exiting the Switching or Signalling Node (SSN) or customer equipment (CEQ) into the attached transmission system.
+
+### **22 continuity check**
+
+*F: test de continuité*
+
+*S: prueba de continuidad*
+
+Mechanism to test that transfer is possible on a certain link or connection. This term is normally qualified to indicate the object being supervised (e.g. VP continuity check).
+
+### **23 compression**
+
+*F: compression*
+
+*S: compresión*
+
+A representation scheme to reduce the size of data maintaining acceptable quality.
+
+NOTE – Compression schemes are usually designed for a particular type of data or content and may give lower quality for other types.
+
+### **24 core network**
+
+*F: réseau central*
+
+*S: red medular; principal*
+
+A portion of the delivery system composed of networks, systems equipment and infrastructures, connecting the service providers to the access network.
+
+### **25 cultural elements**
+
+*F: éléments culturels*
+
+*S: elementos culturales*
+
+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 entities (such as country and currency codes), presentation of telephone numbers, and keyboard layouts.
+
+### **26 Customer Premises Equipment (CPE)**
+
+*F: équipement des locaux client*
+
+*S: equipo en las instalaciones del cliente*
+
+End-use system including private network elements connecting the customer applications to the access line.
+
+### **27 decryption**
+
+*F: déchiffrement*
+
+*S: descripción*
+
+The decoding of encrypted information.
+
+### **28 domain**
+
+*F: domaine*
+
+*S: dominio*
+
+A domain is a set of functions that are performed by one or more players and can include functions from more than one role.
+
+### **29 Drop Distribution Interface (DDI)**
+
+*F: interface entre distribution et raccordement*
+
+*S: interfaz distribución entrega*
+
+The interface between a local distribution network and the final drop network to the customer premises.
+
+### **30 element**
+
+*F: élément*
+
+*S: elemento*
+
+Generic term used to describe any GII component e.g. network, switch, application server, appliance, etc.
+
+### **31 emulation**
+
+*F: émulation*
+
+*S: emulación*
+
+Simulation in real time.
+
+### **32 encryption**
+
+*F: chiffrement*
+
+*S: criptación*
+
+An encoding scheme that produces meaningless information to all observers except those with the decoding key.
+
+### **33 Global Information Infrastructure (GII)**
+
+*F: infrastructure mondiale de l'information*
+
+*S: infraestructura mundial de la información*
+
+A collection of networks, end user equipment, information, and human resources which can be used to access valuable information, communicate with each other, work, learn, receive entertainment from it, at any time and from any place, with affordable cost on a global scale.
+
+### **34 head end**
+
+*F: tête de réseau*
+
+*S: cabecera de red*
+
+An element in a cable distribution system which receives information from a service provider and transmits it to end users.
+
+### **35 interoperability**
+
+*F: interopérabilité*
+
+*S: interoperabilidad*
+
+The ability of two or more systems or applications to exchange information and to mutually use the information that has been exchanged.
+
+### **36 interface**
+
+*F: interface*
+
+*S: interfaz*
+
+A shared boundary between two functional units.
+
+NOTE – An interface is defined by various characteristics pertaining to the functions, physical interconnections, signal exchanges and other characteristics as appropriate.
+
+### **37 Internet**
+
+*F: Internet*
+
+*S: Internet*
+
+A collection of interconnected networks using the Internet Protocol which allows them to function as a single, large virtual network.
+
+### **38 Inter-Network Interface (INI)**
+
+*F: interface interréseaux*
+
+*S: interfaz entre redes*
+
+The interface between two networks.
+
+### **39 Intrinsic Burst Tolerance (IBT)**
+
+*F: tolérance intrinsèque de rafales*
+
+*S: tolerancia intrínseca de ráfaga*
+
+A traffic parameter which characterises the maximum burst duration at a specified peak cell rate, for use together with a Sustainable Cell Rate (SCR) in addition to a Peak Cell Rate (PCR).
+
+### **40 manageability**
+
+*F: aptitude à être géré*
+
+*S: gestionabilidad*
+
+The characteristic of a set of resources, which allows an enterprise, organization, or consumer to control how these resources are deployed and/or utilized.
+
+### **41 management system**
+
+*F: système de gestion*
+
+*S: sistema de gestión*
+
+A functional system which supports the management of user and/or network information and resources for the proper operation of a service.
+
+### **42 media**
+
+*F: médias*
+
+*S: medios*
+
+Plural of medium.
+
+### **43 medium**
+
+*F: média*
+
+*S: medio*
+
+Specific physical support for transmission or storage of information.
+
+Type of presentation of information (i.e., video, audio, text, etc.).
+
+### **44 middleware**
+
+*F: entité médiatrice*
+
+*S: soporte intermedio*
+
+The mediating entity between two information elements. Such an element can be, for example, an application, infrastructure component, or another mediating entity.
+
+### **45 network**
+
+*F: réseau*
+
+*S: red*
+
+A set of nodes and links that provide connections between two or more defined points to facilitate telecommunication between them.
+
+### **46 nomadicity**
+
+*F: itinérance*
+
+*S: nomadicidad*
+
+Continuity of access between two information infrastructure components as they move in space.
+
+### **47 Network-to-Network Interface type A (NNI-A)**
+
+*F: interface réseau-réseau de type A*
+
+*S: interfaz red/red tipo A*
+
+The interface between a long-distance backbone network and a local network.
+
+### **48 Network-to-Network Interface type B (NNI-B)**
+
+*F: interface réseau-réseau de type B*
+
+*S: interfaz red/red tipo B*
+
+The interface between a long-distance backbone network and a peer long-distance backbone network.
+
+### **49 Peak Cell Rate (PCR)**
+
+*F: débit cellulaire crête*
+
+*S: velocidad de células de cresta*
+
+An upper limit on the rate at which cells can be submitted on an ATM connection.
+
+### **50 player**
+
+*F: acteur*
+
+*S: actor*
+
+A player is an organization, or individual, which undertakes one or more roles.
+
+### **51 portability**
+
+*F: portabilité*
+
+*S: portabilidad*
+
+The ability of an entity or element to be used in different systems or environments. Three examples of portability are as follows:
+
+- 1) Ability of software or data to be used in different systems;
+- 2) Ability of a system to be connected to several different systems and operate in different environments; and
+- 3) Ability of a user's telephone number or address to be allocated to different systems when the user moves from one location to another.
+
+### **52 quality of service**
+
+*F: qualité de service*
+
+*S: calidad de servicio*
+
+The collective effect of service performances which determine the degree of satisfaction of a user of the service.
+
+### **53 reference point**
+
+*F: point de référence*
+
+*S: punto de referencia*
+
+A conceptual point at the conjunction of two non-overlapping functional groups (see ITU-T Recommendations G.960, I.112, I.430 and Q.9).
+
+NOTE – Each reference point is assigned a prefix letter (for example: T reference point).
+
+### **54 reliability**
+
+*F: fiabilité*
+
+*S: fiabilidad*
+
+The probability that a product or system will perform as required for a specified period of time.
+
+### **55 role**
+
+*F: rôle*
+
+*S: cometido; rol*
+
+The role is a business activity that is intended to add value to certain goods/services.
+
+### **56 segment**
+
+*F: segment*
+
+*S: segmento*
+
+A segment is a well-defined set of functions, part of one role, owned and operated by one player, part of one (and only one) service provisioning platform, and part of one domain.
+
+### **57 service**
+
+*F: service*
+
+*S: servicio*
+
+A structure set of capabilities intended to support applications.
+
+### **58 service node**
+
+*F: nœud de service*
+
+*S: nodo de servicio*
+
+A network element that contains one or several of the service control functions, service data functions, specialized resource functions and service switching/control function to provide a service in the context of GII.
+
+### **59 service primitive**
+
+*F: primitive de service*
+
+*S: primitiva de servicio*
+
+The smallest defined interaction between the user and provider of a communication service.
+
+### **60 service primitive; primitive**
+
+*F: primitive de service; primitive*
+
+*S: primitiva de servicio; primitiva*
+
+An abstract, implementation-independent interaction between a service user and the service provider.
+
+### **61 Sustainable Cell Rate (SCR)**
+
+*F: débit cellulaire soutenu*
+
+*S: velocidad de células sostenible*
+
+An upper limit on the long-term average cell transfer rate of an ATM connection.
+
+### **62 User-Network Interface (UNI)**
+
+*F: interface utilisateur*
+
+*S: interfaz usuario/red*
+
+The interface between the terminal equipment and a network termination at which interface the access protocols apply.
+
+### **63 Very high speed Digital Subscriber Line (VDSL)**
+
+*F: ligne d'abonné à très haut débit*
+
+*S: línea digital de abonado de velocidad muy alta*
+
+A modem technology that enables converts twisted-pair telephone lines to be used as access paths for multimedia and high-speed data communications. VDSL uses higher bit rates than ADSL. These bit rates may or may not be different in both directions.
+
+### **64 video**
+
+*F: vidéo*
+
+*S: vídeo*
+
+Electronic image with the capability to reproduce movement.
+
+### **65 video server**
+
+*F: serveur vidéo*
+
+*S: servidor de vídeo*
+
+A physical entity that stores video contents for retrieval by users.
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+|                 |                                                                                                                                |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A        | Organization of the work of 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 and Internet protocol aspects</b>                                                         |
+| Series Z        | Languages and general software aspects for telecommunication systems                                                           |

marked/Y/T-REC-Y.1411-200302-I_PDF-E/raw.md

@@ -0,0 +1,866 @@
+
+
+![ITU logo: a globe with the letters ITU inside, and a lightning bolt striking the globe.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+ITU logo: a globe with the letters ITU inside, and a lightning bolt striking the globe.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+# ITU-T
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+# Y.1411
+
+(02/2003)
+
+SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE  
+AND INTERNET PROTOCOL ASPECTS
+
+Internet protocol aspects – Interworking
+
+# --- **ATM-MPLS network interworking – Cell mode user plane interworking**
+
+ITU-T Recommendation Y.1411
+
+---
+
+## ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE AND INTERNET PROTOCOL ASPECTS
+
+|                                                                    |                      |
+|--------------------------------------------------------------------|----------------------|
+| 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        |
+| <b>Interworking</b>                                                | <b>Y.1400–Y.1499</b> |
+| 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        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## **ITU-T Recommendation Y.1411**
+
+# **ATM-MPLS network interworking – Cell mode user plane interworking**
+
+## **Summary**
+
+This Recommendation addresses required functions of network interworking between ATM networks and MPLS networks specifically the user plane interworking mechanisms and procedures. One of the key aspects of network interworking is to provide network support for ATM services during the evolution of networks. Details of the interworking model and required interworking functions are described.
+
+## **Source**
+
+ITU-T Recommendation Y.1411 was prepared by ITU-T Study Group 13 (2001-2004) and approved under the WTSA Resolution 1 procedure on 22 February 2003.
+
+## **Keywords**
+
+ATM, MPLS, interworking, network, user plane.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. 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.
+
+## 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, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2003
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## CONTENTS
+
+|                                                                            | <b>Page</b> |
+|----------------------------------------------------------------------------|-------------|
+| 1 Scope .....                                                              | 1           |
+| 2 References.....                                                          | 1           |
+| 3 Definitions .....                                                        | 2           |
+| 4 Abbreviations.....                                                       | 2           |
+| 5 ATM-MPLS interworking .....                                              | 4           |
+| 6 General requirements.....                                                | 4           |
+| 6.1 User plane requirements .....                                          | 4           |
+| 6.2 Control plane aspects.....                                             | 5           |
+| 6.3 Management plane aspects .....                                         | 6           |
+| 6.4 Traffic Management aspects.....                                        | 7           |
+| 7 Methods of ATM transport over MPLS .....                                 | 8           |
+| 7.1 One-to-one mode .....                                                  | 8           |
+| 7.2 N-to-one mode.....                                                     | 8           |
+| 7.3 Functional group considerations for ATM-MPLS Network interworking..... | 10          |
+| 8 One-to-one mode encapsulation .....                                      | 12          |
+| 8.1 Transport label.....                                                   | 12          |
+| 8.2 Interworking label .....                                               | 12          |
+| 8.3 Common interworking indicators.....                                    | 13          |
+| 8.4 ATM-MPLS interworking specific header.....                             | 13          |
+| 8.5 ATM payload.....                                                       | 13          |
+| 8.6 Encapsulation .....                                                    | 13          |
+| 9 N-to-one mode encapsulation .....                                        | 15          |
+| 9.1 Transport label.....                                                   | 15          |
+| 9.2 Interworking label .....                                               | 15          |
+| 9.3 Common interworking indicators.....                                    | 16          |
+| 9.4 ATM-MPLS interworking specific header.....                             | 16          |
+| 9.5 ATM payload.....                                                       | 16          |
+| 9.6 Encapsulation .....                                                    | 16          |
+| 10 OAM and RM cell treatment .....                                         | 19          |
+| 10.1 ATM-to-MPLS direction.....                                            | 19          |
+| 10.2 MPLS-to-ATM direction.....                                            | 19          |
+
+# **Introduction**
+
+There is a need to focus on required functions of network interworking between ATM networks and MPLS networks specifically the user plane interworking mechanisms and procedures. One of the key aspects of network interworking is to provide network support for ATM services during the evolution of networks.
+
+## ITU-T Recommendation Y.1411
+
+# ATM-MPLS network interworking – Cell mode user plane interworking
+
+# 1 Scope
+
+This Recommendation focuses on required functions for network interworking between ATM and MPLS, specifically the user plane interworking mechanisms and procedures for cell mode transport. In particular it specifies a list of requirements, interworking scenarios and interworking encapsulation format and semantics for ATM-MPLS cell mode network interworking.
+
+This Recommendation enables transport of ATM Permanent Virtual Connections (PVC) or Switched Virtual Connections (SVC) over an MPLS network. The encapsulation allows ATM Virtual Channel Connections (VCCs) or Virtual Path Connections (VPCs) to be carried within MPLS Label Switched Paths (LSPs). The scope includes support of all AAL types as well as OAM and RM cells, and the ability to encapsulate one or multiple ATM cells in a single MPLS Frame.
+
+# 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.
+
+- [1] ITU-T Recommendation I.510 (1993), *Definitions and general principles for ISDN interworking*.
+- [2] IETF RFC 3031 (2001), *Multiprotocol label switching architecture*.
+- [3] ITU-T Recommendation I.610 (1999), *B-ISDN operation and maintenance principles and functions*.
+- [4] ITU-T Recommendation I.610 (1999)/Cor.1 (2000), *B-ISDN operation and maintenance principles and functions – Corrigendum 1*.
+- [5] ITU-T Recommendation I.610 (1999)/Amd.1 (2000), *B-ISDN operation and maintenance principles and functions – Amendment 1*.
+- [6] ITU-T Recommendation Y.1710 (2002), *Requirements for Operation & Maintenance functionality in MPLS networks*.
+- [7] ITU-T Recommendation Y.1711 (2002), *Operation & Maintenance mechanism for MPLS networks*.
+- [8] ITU-T Recommendation I.371 (2000), *Traffic control and congestion control in B-ISDN*.
+- [9] ITU-T Recommendation I.371.1 (2000), *Guaranteed frame rate ATM transfer capability*.
+- [10] ITU-T Recommendation I.356 (2000), *Muti-protocol Label Switching (MPLS) B-ISDN ATM layer cell transfer performance*.
+- [11] IETF RFC 3270 (2002), *Muti-protocol Label Switching (MPLS) Support of Differentiated Services*.
+- [12] IETF RFC 3032 (2001), *MPLS Label Stack Encoding*.
+- [13] ITU-T Recommendation I.732 (2000), *Functional characteristics of ATM equipment*.
+
+- [14] ATM Forum, af-sec-0100.002 (2001), *ATM Security Specification Version 1.1*.
+- [15] ITU-T Recommendation I.361 (1999), *B-ISDN ATM layer specification*.
+- [16] IETF RFC 2475 (1998), *An Architecture for Differentiated Services*.
+- [17] IETF RFC 3260 (2002), *New terminology and clarifications for DiffServ*.
+
+# 3 Definitions
+
+This Recommendation defines the following terms:
+
+**3.1 cell concatenation:** The process of bundling a group of cells belonging to VCCs or VPCs into a MPLS frame. Note that this is not AAL segmentation and reassembly.
+
+**3.2 interworking:** The term "interworking" is used to express interactions between networks, between end systems, or between parts thereof, with the aim of providing a functional entity capable of supporting an end-to-end communication. The interactions required to provide a functional entity rely on functions and on the means to select these functions [1].
+
+**3.3 interworking function (IWF):** These functions are referred to in the interworking definition, which include the conversion between protocols and the mapping of one protocol to another. The functionality required between networks can be separated from the functionality, if any, required in end systems. The IWFs needed as a result of a service requirement for interworking are categorized as connection-dependent IWFs (i.e., those functions needed in order to interconnect two networks) or communication-dependent IWFs (i.e., those functions in addition to connection-dependent IWFs needed in order to establish a specific end-to-end communication and which may differ from application to application) [1]. The IWF includes interworking between U-plane, C-plane and M-plane functions.
+
+**3.4 ingress IWF/network element:** The point where the ATM cells are encapsulated into an MPLS frame (ATM-to-MPLS direction.)
+
+**3.5 egress IWF/network element:** The point where the ATM cells are de-encapsulated from an MPLS frame (MPLS-to-ATM direction.)
+
+**3.6 one-to-one mode:** The one-to-one mode specifies an encapsulation method which maps one ATM VCC (or one ATM VPC) to one interworking LSP.
+
+**3.7 N-to-one mode:** The N-to-one mode specifies an encapsulation method which maps one or more ATM VCCs (or one or more ATM VPCs) to one interworking LSP.
+
+# 4 Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+|        |                                               |
+|--------|-----------------------------------------------|
+| AAL    | ATM Adaptation Layer                          |
+| AINI   | ATM Inter-Network Interface                   |
+| ATC    | ATM Transfer Capability                       |
+| ATM    | Asynchronous Transfer Mode                    |
+| ATM-F  | ATM Forum                                     |
+| B-ISDN | Broadband-Integrated Services Digital Network |
+| B-ISUP | Broadband ISDN User Part                      |
+| CES    | Circuit Emulation Service                     |
+| CLP    | Cell Loss Priority                            |
+
+|       |                                            |
+|-------|--------------------------------------------|
+| DSS2  | Digital Subscriber Signalling System No. 2 |
+| E-LSP | EXP-inferred-PSC LSP                       |
+| EXP   | Experimental Bits                          |
+| FIFO  | First In First Out                         |
+| GFC   | Generic Flow Control                       |
+| HEC   | Header Error Control                       |
+| ILMI  | Integrated Local Management Interface      |
+| ISDN  | Integrated Services Digital Network        |
+| ISH   | Interworking Specific Header               |
+| IWF   | Interworking Function                      |
+| L-LSP | Label-only-inferred-PSC LSP                |
+| LSP   | Label Switched Path                        |
+| LSR   | Label Switching Router                     |
+| MPLS  | Multi-Protocol Label Switching             |
+| MTU   | Maximum Transport Unit                     |
+| NNI   | Network-to-Network Interface               |
+| OAM   | Operation And Maintenance                  |
+| PHB   | Per Hop Behaviour                          |
+| PM    | Performance Monitoring                     |
+| PNNI  | Private Network-to-Network Interface       |
+| PSC   | PHB Scheduling Class                       |
+| PTI   | Payload Type Identifier                    |
+| PVC   | Permanent Virtual Connection               |
+| QoS   | Quality of Service                         |
+| RFC   | Request for Comments                       |
+| RM    | Resource Management                        |
+| S-bit | Stack bit                                  |
+| SPVC  | Soft PVC                                   |
+| SVC   | Switched Virtual Connection                |
+| TTL   | Time To Live                               |
+| UNI   | User-Network Interface                     |
+| VC    | Virtual Channel                            |
+| VCC   | Virtual Channel Connection                 |
+| VCI   | Virtual Channel Identifier                 |
+| VP    | Virtual Path                               |
+| VPC   | Virtual Path Connection                    |
+| VPI   | Virtual Path Identifier                    |
+
+# 5 ATM-MPLS interworking
+
+The multi-protocol label switching (MPLS) technology [2] allows services to be supported over a single networking infrastructure. Services in this context are traditional data services such as ATM, Frame Relay, IP and Circuit Emulation Services (CES). Figure 1 provides a general network architecture for ATM-MPLS network interworking where ATM network(s) are interconnected through an MPLS network. For the ATM-to-MPLS direction, the ATM cells are encapsulated into a MPLS frame by the interworking function (IWF). For the MPLS-to-ATM direction, reconstruction of the ATM cells is performed.
+
+![Figure 1/Y.1411 – Reference network architecture for ATM-MPLS network interworking. The diagram shows a horizontal flow from left to right. On the far left is a box labeled 'End System 1'. To its right is a cloud labeled 'ATM'. This is followed by a trapezoidal box labeled 'IWF' (Interworking Function) with 'ATM' on the left side and 'MPLS' on the right side. This connects to a central cloud labeled 'MPLS' containing a network of nodes and links. Some links are solid lines (LSPs) and some are dashed lines (LSRs). To the right of the MPLS cloud is another 'IWF' box, also labeled 'MPLS' on the left and 'ATM' on the right. This connects to another 'ATM' cloud, which then connects to a box labeled 'End System 2'. Below the main flow, three horizontal arrows indicate the network segments: 'ATM network' under the first ATM cloud, 'MPLS network' under the central MPLS cloud, and 'ATM network' under the second ATM cloud. A legend at the bottom left shows a circle for 'LSR' and a solid line for 'LSP'. The identifier 'Y.1411_F01' is at the bottom right.](cfda9df1319e04207eb28bcefd1dab7b_img.jpg)
+
+○ LSR      — LSP
+
+Y.1411\_F01
+
+Figure 1/Y.1411 – Reference network architecture for ATM-MPLS network interworking. The diagram shows a horizontal flow from left to right. On the far left is a box labeled 'End System 1'. To its right is a cloud labeled 'ATM'. This is followed by a trapezoidal box labeled 'IWF' (Interworking Function) with 'ATM' on the left side and 'MPLS' on the right side. This connects to a central cloud labeled 'MPLS' containing a network of nodes and links. Some links are solid lines (LSPs) and some are dashed lines (LSRs). To the right of the MPLS cloud is another 'IWF' box, also labeled 'MPLS' on the left and 'ATM' on the right. This connects to another 'ATM' cloud, which then connects to a box labeled 'End System 2'. Below the main flow, three horizontal arrows indicate the network segments: 'ATM network' under the first ATM cloud, 'MPLS network' under the central MPLS cloud, and 'ATM network' under the second ATM cloud. A legend at the bottom left shows a circle for 'LSR' and a solid line for 'LSP'. The identifier 'Y.1411\_F01' is at the bottom right.
+
+**Figure 1/Y.1411 – Reference network architecture for ATM-MPLS network interworking**
+
+This Recommendation defines two methods for encapsulation of ATM cells into an MPLS frame:
+
+- 1) one ATM connection to an interworking LSP, referred to as one-to-one mode;
+- 2) N ATM connections to an interworking LSP, referred to as N-to-one mode.
+
+The one-to-one mode specifies an encapsulation method that maps one ATM VCC or one ATM VPC to one interworking LSP. For VCCs, the VPI/VCI is not included. For VPCs, the VPI is not included. Cells from one VCC or one VPC may be concatenated.
+
+The N-to-one mode specifies an encapsulation method that maps one or more ATM VCCs (or one or more ATM VPCs) to one interworking LSP. For both VCCs and VPCs, the VPI/VCI is always included. Cells from one or more VCCs (or one or more VPCs) may be concatenated.
+
+This Recommendation defines only the encapsulation of ATM cells that use the NNI format [15]. The encapsulation of ATM cells that use the UNI format which includes the GFC field is for further study.
+
+# 6 General requirements
+
+## 6.1 User plane requirements
+
+For transparent transfer of ATM-related services in the transfer (user) plane, the following items are required:
+
+- a) the ability to multiplex multiple ATM connections (i.e., VPCs and/or VCCs) into interworking LSPs;
+- b) support for the traffic contracts and the QoS commitments made to the ATM connections;
+- c) the ability to transparently carry all AAL types;
+- d) the ability to transparently carry all OAM cells, including the support for proper operation of OAM PM cells;
+- e) transport of Resource Management (RM) cells;
+
+- f) transport of Cell Loss Priority (CLP) indication and Payload Type Indication (PTI) information from the ATM cell header;
+- g) the ability to encapsulate an ATM single cell or concatenated ATM cells into one MPLS frame;
+- h) maintaining sequence integrity for all VCCs and VPCs between the IWFs;
+- i) support of ATM point-to-point and ATM point-to-multipoint connection;
+- j) support of unidirectional ATM connection;
+- k) support of bidirectional point-to-point ATM connections with symmetric or asymmetric bandwidth.
+
+Figure 2 shows the network reference model and protocol layers for ATM-MPLS user plane interworking.
+
+![Figure 2: Network reference model and protocol layers for ATM-MPLS user plane interworking. The top part shows a high-level view of the network architecture: ATM cloud -> IWF -> MPLS cloud -> IWF -> ATM cloud. Below this, a horizontal line represents the MPLS LSP, with VC/VP segments at the ends. The bottom part shows a detailed protocol stack diagram. On the left, the ATM stack consists of Upper Layers, AAL, ATM, and Physical layers. This connects to an IWF, which is split into ATM and MPLS LSP Stacks. The MPLS LSP Stacks connect to another IWF, which is split into MPLS LSP Stacks and ATM. Finally, the ATM stack on the right consists of Upper Layers, AAL, ATM, and Physical layers. The Physical layers of all stacks are connected in a sequence.](e9314c83043183351ed74908e9bf2f90_img.jpg)
+
+Y.1411\_F02
+
+Figure 2: Network reference model and protocol layers for ATM-MPLS user plane interworking. The top part shows a high-level view of the network architecture: ATM cloud -> IWF -> MPLS cloud -> IWF -> ATM cloud. Below this, a horizontal line represents the MPLS LSP, with VC/VP segments at the ends. The bottom part shows a detailed protocol stack diagram. On the left, the ATM stack consists of Upper Layers, AAL, ATM, and Physical layers. This connects to an IWF, which is split into ATM and MPLS LSP Stacks. The MPLS LSP Stacks connect to another IWF, which is split into MPLS LSP Stacks and ATM. Finally, the ATM stack on the right consists of Upper Layers, AAL, ATM, and Physical layers. The Physical layers of all stacks are connected in a sequence.
+
+**Figure 2/Y.1411 – Network reference model and protocol layers for ATM-MPLS user plane interworking**
+
+## 6.2 Control plane aspects
+
+For transparent transfer of ATM-related services, the following items are to be signalled or provisioned:
+
+- a) exchange of interworking label(s) between IWFs;
+- b) correlation of interworking labels for one or more bidirectional connections per interworking LSP. Mechanisms are to be defined;
+- c) operation in one-to-one or N-to-one mode;
+- d) maximum number of concatenated cells for a given interworking LSP between IWFs;
+- e) indication of cell encapsulation modes as either single or concatenated;
+- f) presence of common interworking indicators field;
+- g) support of the connection types Switched Virtual Connection (SVC) and Soft Permanent Virtual Connection (SPVC);
+
+- h) support of ATM point-to-point and ATM point-to-multipoint connections;
+- i) support of bidirectional ATM point-to-point connections with symmetric or asymmetric bandwidth;
+- j) the transparent transport of ATM signalling protocols (e.g., DSS2, B-ISUP, ATM-F UNI, ATM-F PNNI, ATM-F AINI), ATM routing protocols (e.g., ATM-F PNNI) and ATM management protocols (e.g., ATM-F ILMI), which control the ATM connections across the MPLS network;
+- k) the ability to control the MPLS interworking LSPs via ATM control protocols by the IWFs for ATM SVCs and ATM Soft-PVCs;
+- l) the control of MPLS Transport LSPs or interworking LSPs via MPLS control protocols by the IWFs;
+- m) a mechanism to associate the two transport LSPs, one for each direction, to act as a logical ATM port to ATM signalling and routing, capable of carrying ATM connections between two IWFs.
+
+## 6.3 Management plane aspects
+
+ATM OAM cells carry performance, defect, and protection switching information for VCCs and VPCs on an end-to-end and per segment basis to support the ATM management plane [3], [4] and [5]. OAM functionality in MPLS networks and OAM mechanism for MPLS networks can be found in ITU-T Recs Y.1710 [6] and Y.1711 [7].
+
+For transparent transfer of ATM-related services in the management plane, the interworking function should support transparent transfer or mapping of performance, defect, and protection switching information between MPLS OAM flows and ATM OAM cells.
+
+As a minimum, the interworking function shall transfer ATM OAM information through the MPLS core network by encapsulating OAM cells in MPLS packets. The encapsulation mechanism supports the ordered delivery of OAM cells in respect to cell flow of that connection.
+
+Where end-to-end OAM is required, the interworking function may have to correlate the MPLS OAM information with the ATM OAM. This aspect of OAM interworking with MPLS is outside the scope of this Recommendation.
+
+Figure 3 shows functional representation of ATM-MPLS management plane.
+
+![Figure 3/Y.1411 – Functional representation of ATM-MPLS management plane interworking. The diagram shows a functional architecture where two ATM networks are connected via an MPLS network through Interworking Function (IWF) blocks. Management planes are shown as horizontal arrows: ATM management on the left and right, and MPLS management in the center. Below, two detailed IWF blocks show the mapping of management functions: the left IWF handles AIS, RDI, CC, LB, FPM (from ATM) and FDI, BDI, CV, LB, P (to MPLS); the right IWF handles FDI, BDI, CV, LB, P (from MPLS) and AIS, RDI, CC, LB, FPM (to ATM).](af7916c89a458fdab6c3f443217388ae_img.jpg)
+
+Y.1411\_F03
+
+|     |                           |     |                                |
+|-----|---------------------------|-----|--------------------------------|
+| AIS | Alarm Indication Signal   | RDI | Remote Defect Indication       |
+| CC  | Continuity Check          | FPM | Forward Performance Monitoring |
+| LB  | Loop Back                 | FDI | Forward Defect Indicator       |
+| CV  | Connectivity Verification | BDI | Backward Defect Indication     |
+| P   | P flows                   |     |                                |
+
+Figure 3/Y.1411 – Functional representation of ATM-MPLS management plane interworking. The diagram shows a functional architecture where two ATM networks are connected via an MPLS network through Interworking Function (IWF) blocks. Management planes are shown as horizontal arrows: ATM management on the left and right, and MPLS management in the center. Below, two detailed IWF blocks show the mapping of management functions: the left IWF handles AIS, RDI, CC, LB, FPM (from ATM) and FDI, BDI, CV, LB, P (to MPLS); the right IWF handles FDI, BDI, CV, LB, P (from MPLS) and AIS, RDI, CC, LB, FPM (to ATM).
+
+**Figure 3/Y.1411 – Functional representation of ATM-MPLS management plane interworking**
+
+## 6.4 Traffic Management aspects
+
+In ATM, a number of different ATM Transfer Capabilities (ATC) [8], [9] and Quality of Service (QoS) classes [10] are defined. A combination of an ATC and an associated QoS class is intended to support an ATM layer service model.
+
+When a transport LSP is used to carry multiple ATM connections with different combinations of ATC and QoS classes, the transport LSP shall be capable of providing the required QoS for all ATM connections. In a MPLS network that does not support QoS differentiation on a per packet basis, the LSP shall meet the most stringent QoS requirements of the ATM connections transported by the LSP.
+
+### 6.4.1 Use of Differentiated Services for ATM-MPLS interworking
+
+If the MPLS network supports Differentiated Services (DiffServ) Behaviour Aggregates defined in [16], MPLS packets can be treated with different priorities on a Per Hop Behaviour (PHB). In this case, two different types of LSPs are defined [11], which can both be used for the transport LSP:
+
+- Label-Only-Inferred-PSC LSPs (L-LSP);
+- EXP-Inferred-PSC LSPs (E-LSP).
+
+If a L-LSP is used as a transport LSP, the PHB scheduling class (PSC) [17] of each packet is inferred from the label without any other information (e.g., regardless of the EXP field value). In that case, the LSP shall meet the most stringent QoS requirements of the ATM connections transported by the LSP.
+
+If an E-LSP is used as a transport LSP, the EXP field of the transport label is used to determine the PHB to be applied to each packet, i.e., different packets in one LSP may receive a different QoS. The 3-bit EXP field of the transport label can represent eight different combinations of Per Hop Behaviour (PHB) and drop precedence levels. The mapping of the PHB to EXP fields is either explicitly signalled at label set-up or relies on a pre-configured mapping.
+
+The mapping between ATM QoS classes and MPLS PHB is for further study.
+
+### 6.4.2 Connection admission control for the IWF
+
+Virtual connections (VPCs, VCCs, LSPs) have to be managed on both ATM and MPLS sides of the IWF. The IWF binds an ATM connection with a MPLS connection. The MPLS connection consists of a combination of an interworking LSP and a transport LSP. The IWF connection admission control applies to the bandwidth allocation of the transport LSP.
+
+A connection request shall be accepted only when sufficient resources are available to establish the connection through the whole network (ATM network and MPLS network), to comply with the required QoS and to maintain the agreed QoS of the existing connections.
+
+In case there is not sufficient capacity to accept a new ATM connection, the network may consider to increase the bandwidth of the transport LSP.
+
+# 7 Methods of ATM transport over MPLS
+
+## 7.1 One-to-one mode
+
+In one-to-one cell mode network interworking, one ATM connection (VPC or VCC) is carried by one interworking LSP (Label Switched Path). Since the interworking LSP is unidirectional therefore for the case of bidirectional ATM connections, there will be two different interworking LSPs, one for each direction of the connection.
+
+Figure 4 shows an illustration of the one-to-one mode.
+
+![Diagram illustrating the one-to-one mode of ATM transport over MPLS. It shows four physical transmission paths on the left, each labeled 'VCC or VPC'. These paths enter an 'IWF' (Interworking Function) block. Inside the IWF, the paths cross, indicating bidirectional flow. On the right side of the IWF, there are four 'Interworking LSP' paths. These paths then connect to four 'Transport LSP' paths on the far right. The diagram uses solid lines for the physical paths and dashed lines for the LSP paths. Ellipses are used to group the VCC/VPC paths and the Transport LSP paths.](f6e8acf9f931452d01688d311b5c0364_img.jpg)
+
+Y.1411\_F04
+
+Diagram illustrating the one-to-one mode of ATM transport over MPLS. It shows four physical transmission paths on the left, each labeled 'VCC or VPC'. These paths enter an 'IWF' (Interworking Function) block. Inside the IWF, the paths cross, indicating bidirectional flow. On the right side of the IWF, there are four 'Interworking LSP' paths. These paths then connect to four 'Transport LSP' paths on the far right. The diagram uses solid lines for the physical paths and dashed lines for the LSP paths. Ellipses are used to group the VCC/VPC paths and the Transport LSP paths.
+
+Figure 4/Y.1411 – Illustration of one-to-one mode
+
+## 7.2 N-to-one mode
+
+The N-to-one mode specifies an encapsulation method that maps one or more ATM VCCs (or one or more ATM VPCs) to one Interworking LSP. For both VCCs and VPCs, the VPI/VCI is always included. Cells from one or more VCCs (or one or more VPCs) may be concatenated. The interworking LSP is unidirectional; thus, for the case of bidirectional ATM connections, there will be two different interworking LSPs, one for each direction of the connection.
+
+Figure 5 illustrates the N-to-one mode. The illustration where  $N = 1$  indicates encapsulation of one VCC or one VPC into one interworking LSP. This is similar to one-to-one mode. In the figure where  $N = 2$ , this indicates encapsulation of two VCCs or two VPCS into one interworking LSP.
+
+Figure 6 is an illustration of grouping of ATM connections with similar attributes using N-to-one mode to various IWFs.
+
+![Diagram illustrating N-to-one mode for ATM connections. It shows two physical transmission paths on the left, each containing multiple VCC or VPC lines. These connect to an IWF block. From the IWF, two Interworking LSP lines emerge. The top Interworking LSP connects to a Transport LSP block labeled 'N = 1'. The bottom Interworking LSP connects to a Transport LSP block labeled 'N = 2'. The Transport LSP blocks contain dashed lines representing individual connections. The diagram is labeled Y.1411_F05 in the bottom right corner.](bd0b93e7a46ede276d0a3b79ac487bd9_img.jpg)
+
+Diagram illustrating N-to-one mode for ATM connections. It shows two physical transmission paths on the left, each containing multiple VCC or VPC lines. These connect to an IWF block. From the IWF, two Interworking LSP lines emerge. The top Interworking LSP connects to a Transport LSP block labeled 'N = 1'. The bottom Interworking LSP connects to a Transport LSP block labeled 'N = 2'. The Transport LSP blocks contain dashed lines representing individual connections. The diagram is labeled Y.1411\_F05 in the bottom right corner.
+
+NOTE – When multiple VCCs or VPCs are transported in one interworking LSP, VPI/VCI values shall be unique. When the multiple VCCs or VPCs are from different physical transmission paths, it may be necessary to assign unique VPI/VCI values to the ATM connections. If they are from the same physical transmission path, the VPI/VCI values are unique.
+
+**Figure 5/Y.1411 – Illustration of N-to-one mode**
+
+![Diagram illustrating N-to-one mode for ATM connections. It shows two physical transmission paths on the left, each containing multiple VCC or VPC lines. These connect to an IWF X block. From IWF X, two sets of Interworking LSP lines emerge. The top set connects to a Transport LSP block labeled 'To IWF A'. The bottom set connects to a Transport LSP block labeled 'To IWF B'. The Transport LSP blocks contain dashed lines representing individual connections. The diagram is labeled Y.1411_F06 in the bottom right corner.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg)
+
+Diagram illustrating N-to-one mode for ATM connections. It shows two physical transmission paths on the left, each containing multiple VCC or VPC lines. These connect to an IWF X block. From IWF X, two sets of Interworking LSP lines emerge. The top set connects to a Transport LSP block labeled 'To IWF A'. The bottom set connects to a Transport LSP block labeled 'To IWF B'. The Transport LSP blocks contain dashed lines representing individual connections. The diagram is labeled Y.1411\_F06 in the bottom right corner.
+
+**Figure 6/Y.1411 – Illustration of grouping in N-to-one mode**
+
+## 7.3 Functional group considerations for ATM-MPLS Network interworking
+
+Figure 7 provides an illustration of functional grouping for ATM-MPLS network interworking.
+
+|                                       |  |
+|---------------------------------------|--|
+| MPLS transport label                  |  |
+| Interworking label                    |  |
+| Common interworking indicators        |  |
+| ATM-MPLS interworking specific header |  |
+| ATM Cell Payload (48 octets)          |  |
+| ...                                   |  |
+| ATM-MPLS interworking specific header |  |
+| ATM Cell Payload (48 octets)          |  |
+
+**Figure 7/Y.1411 – ATM-MPLS interworking functional groups**
+
+### 7.3.1 MPLS transport label
+
+The 4-octet MPLS transport label identifies a LSP used to transport traffic between two ATM-MPLS IWFs. The transport label is a standard MPLS shim header [12]. This label is processed at each LSR. Since MPLS LSPs are unidirectional, a pair of transport LSPs carrying traffic in opposite directions will be required to create a bidirectional transport. The setting of the EXP and TTL fields of the transport label is outside the scope of this Recommendation. The S bit is set to 0 for this label, indicating that this is not the bottom of the label stack. Between any two ATM-MPLS IWFs, there may exist more than one transport LSP in each direction at any time.
+
+### 7.3.2 Interworking label
+
+The 4-octet interworking label uniquely identifies one interworking LSP carried inside a MPLS transport LSP. The interworking label has the structure of a standard MPLS shim header [12]. More than one interworking LSP may be supported by one MPLS transport LSP.
+
+Since MPLS LSPs are unidirectional, for the case of bidirectional ATM VCCs or VPCs, there will be two different interworking LSPs, one for each direction of the connection. These may have different label values.
+
+The interworking function maintains context information that associates ATM connections with the interworking LSP.
+
+### 7.3.3 Common interworking indicators
+
+The functions in the common interworking indicators are related to the interworking LSP and are independent of any specific service or encapsulation. This does not imply identical encapsulation formats in the one-to-one and N-to-one mode.
+
+In general the common interworking indicators is comprised of a control field, a length field and a sequence number field.
+
+#### 7.3.3.1 Control field
+
+The control field does not exist for one-to-one mode. It only exists in N-to-one mode.
+
+If the common interworking indicators is present, in N-to-one mode, this field shall be present. However its use is optional (see 9.3.1).
+
+#### 7.3.3.2 Length field
+
+The length field indicates the length of the payload. When the LSP path includes an Ethernet link, a minimum packet size of 64 octets is required. This may require padding to be applied to the interworking packet payload in order to reach this minimum packet size. The padding size can be determined from the length field so that the padding can be extracted at the egress.
+
+If the common interworking indicators is present, this field shall be present. However, its use is optional (see 8.3.2 and 9.3.2).
+
+The two most significant bits of the length field are reserved for future use. They are set to zero in this Recommendation for both one-to-one and N-to-one modes. The remaining six bits are called length indicator.
+
+#### 7.3.3.3 Sequence number field
+
+The sequence number field is used to check on the sequence integrity of MPLS frames sent from the ingress IWF to the egress IWF. In general, ATM services require that the sequence integrity of cells on a VCC or VPC be maintained. When ATM services are transported over an underlying MPLS-based network, it is required that the MPLS network should attempt to maintain the sequence integrity of the ATM cells encapsulated in the MPLS frames.
+
+Even under the normal "first in first out" (FIFO) operation, it is possible that mis-ordering of the frames still could occur. As an option, the sequence number field is set by the IWF in the ATM-to-MPLS direction. The sequence number is a 2-octet field that may be used to monitor packet order delivery. The sequence number space is a 16-bit, unsigned circular space.
+
+If the common interworking indicators is present, this field shall be present. However, its use is optional (see 8.3.3 and 9.3.3).
+
+##### 7.3.3.3.1 Setting the sequence numbers
+
+If the sequence number field is used, then the following procedures apply in the ATM-to-MPLS direction:
+
+- The sequence number shall be set to 1 for the first MPLS frame transmitted on the interworking LSP.
+- For each subsequent MPLS frame, the sequence number shall be incremented by 1.
+- If the result of incrementing is a value of 65 535 for the current MPLS frame, the sequence number shall be reset to 1 for the next MPLS frame.
+
+If the ingress IWF does not use the sequence number, then the sequence number field shall be set to zero.
+
+##### 7.3.3.3.2 Processing the sequence numbers
+
+If the IWF is capable of monitoring sequence integrity, then the following procedures shall be used:
+
+- If the sequence number is 0, the sequence integrity of the packets cannot be determined by the IWF. In this case, the received packet is considered to be in order.
+- Otherwise, if the sequence number  $\geq$  the expected sequence number and the sequence number – the expected sequence number  $< 32\,768$ , then the received packet is considered to be in order.
+- Otherwise, if the sequence number  $<$  the expected sequence number and the expected sequence number – the sequence number  $\geq 32\,768$ , then the received packet is considered to be in order.
+- Otherwise, the received packet is out of order.
+
+- If the received packet is in order, then the expected sequence number = the sequence number +1 mod  $2^{16}$ .
+- If the expected sequence number = 0, then the expected sequence number = 1.
+
+NOTE – The initial expected sequence number is set to 1.
+
+### **7.3.4 ATM-MPLS interworking specific header**
+
+The interworking specific header contains the information, which is used to reconstruct the ATM cells from an MPLS frame in the MPLS-to-ATM direction at the IWF.
+
+# **8 One-to-one mode encapsulation**
+
+## **8.1 Transport label**
+
+The transport label is a four-octet MPLS shim header as specified in [12]. See 7.3.1 for more information.
+
+## **8.2 Interworking label**
+
+The interworking label is a four-octet MPLS shim header as specified in [12]. See 7.3.2 for more information.
+
+The interworking function maintains context information that associates ATM connections with the interworking LSP. This information is referenced by means of the 20-bit label field of the interworking label.
+
+The context of the interworking label field implies:
+
+- Connection type: VCC or VPC.
+- For VPC connection types, VPI value to be inserted in the ATM cells headers in the MPLS-to-ATM direction.
+- For VCC connection types, the VPI and VCI value to be inserted in the ATM cells headers in the MPLS-to-ATM direction.
+
+This does not preclude the inclusion of other context information.
+
+Procedures for the generation and parsing of the interworking label are as follows:
+
+#### **ATM-to-MPLS direction**
+
+In the case of a VPC, translation of the VPI to the 20-bit label field is performed. In the case of a VCC, the VPI and VCI are translated to the 20-bit label field. This association is signalled or provisioned between a pair of peer IWFs.
+
+The S bit is set to 1 to indicate the bottom of the label stack.
+
+As the interworking label is only significant to the ATM-MPLS interworking functions at either end of the interworking LSP, it appears to the IWFs as though they are directly connected by one hop.
+
+The TTL value in the Interworking label is set to 2.
+
+The settings of the EXP bits are for further study.
+
+### **MPLS-to-ATM direction**
+
+In the case of a VPC, translation of the 20-bit label field to the VPI is performed. In the case of a VCC, the 20-bit label field is translated to the VPI and VCI. This association is signalled or provisioned between a pair of peer IWFs. MPLS frames received with an invalid or unassigned interworking label are discarded.
+
+## **8.3 Common interworking indicators**
+
+Presence and use of the common interworking indicators is optional.
+
+If present, in one-to-one mode the Common interworking indicators field is comprised of a length field and a sequence number field.
+
+The IWF in the MPLS-to-ATM direction shall be aware of whether the common interworking indicators (i.e., all fields together) is used. See item f in 6.2.
+
+### **8.3.1 Control field**
+
+This field does not exist for one-to-one mode.
+
+### **8.3.2 Length field**
+
+If the common interworking indicators is present, this field shall be present. The use of the length indicator function is not required in the one-to-one mode. The two most significant bits of the length field are reserved and are set to zero. The remaining six bits are called length indicator.
+
+If the common interworking indicators is present and length indicator field is not used, this field is set to all zeros at the ATM-to-MPLS direction IWF and is not processed at the MPLS-to-ATM direction IWF.
+
+### **8.3.3 Sequence number field**
+
+If the common interworking indicators is present, this field shall be present. However, the use of sequence number field is optional. The sequence number is a 2-octet field that may be used to monitor the MPLS frame ordered delivery and is set by the IWF in the ATM-to-MPLS direction. The sequence number space is a 16-bit, unsigned circular space.
+
+If the common interworking indicators is present and sequence number function is not used, this field is set to all zeros at the ATM-to-MPLS direction IWF.
+
+#### **8.3.3.1 Procedures for setting the sequence number in the ATM-to-MPLS direction**
+
+See 7.3.3.3.1.
+
+#### **8.3.3.2 Processing the sequence number in the MPLS-to-ATM direction**
+
+See 7.3.3.3.2.
+
+The treatment of packets that are received out of order is for further study.
+
+## **8.4 ATM-MPLS interworking specific header**
+
+The ATM-MPLS interworking specific header (ISH) identifies whether encapsulation is to be performed for ATM cells or AAL 5 frames. In addition, other elements of the protocol control information constitute parts of this header.
+
+## **8.5 ATM payload**
+
+This consists of one ATM cell payload (i.e., 48 octets).
+
+## **8.6 Encapsulation**
+
+Two cell encapsulation methods are considered, the single cell encapsulation and the concatenated cell encapsulation. Both methods are allowed in one-to-one mode.
+
+For single cell encapsulation, one ATM cell is encapsulated into a single MPLS frame.
+
+For concatenated cell encapsulation, multiple ATM cells are encapsulated in a single MPLS frame. These cells shall belong to the same VCC or VPC. In the case of a VPC, the concatenated cells may belong to different VCCs.
+
+The maximum number of concatenated ATM cells is determined by considerations such as the MTU size of the transport medium and QoS requirements for the ATM connection.
+
+The IWF may be configured via provisioning or via signalling to transmit and receive MPLS frames which contain concatenated cells.
+
+In the case of mis-configuration, a receiver that is not configured to support cell concatenation shall discard a received MPLS frame that contains more than one ATM cell payload (i.e., 48 bytes). The event should be reported to the management plane.
+
+Figures 8 and 9 show the MPLS frame format of single and concatenated cell encapsulations respectively.
+
+|                                   |      |                         |   |     |   |     |   |  |  |  |  |  |  |
+|-----------------------------------|------|-------------------------|---|-----|---|-----|---|--|--|--|--|--|--|
+| 8                                 | 7    | 6                       | 5 | 4   | 3 | 2   | 1 |  |  |  |  |  |  |
+| Transport Label (4 octets)        |      |                         |   |     |   |     |   |  |  |  |  |  |  |
+| Interworking Label (4 octets)     |      |                         |   |     |   |     |   |  |  |  |  |  |  |
+| Reserved (Note)                   |      | Length indicator (Note) |   |     |   |     |   |  |  |  |  |  |  |
+| Sequence number (2 octets) (Note) |      |                         |   |     |   |     |   |  |  |  |  |  |  |
+| MODE                              | VCIP | RES                     |   | PTI |   | CLP |   |  |  |  |  |  |  |
+| VCI (2 octets)                    |      |                         |   |     |   |     |   |  |  |  |  |  |  |
+| ATM Payload (48 octets)           |      |                         |   |     |   |     |   |  |  |  |  |  |  |
+
+NOTE – Presence and use of the common interworking indicators is optional.
+
+**Figure 8/Y.1411 – Single cell encapsulation (One-to-one mode)**
+
+|                                   |      |                         |   |     |   |     |   |  |  |  |  |  |  |
+|-----------------------------------|------|-------------------------|---|-----|---|-----|---|--|--|--|--|--|--|
+| 8                                 | 7    | 6                       | 5 | 4   | 3 | 2   | 1 |  |  |  |  |  |  |
+| Transport Label (4 octets)        |      |                         |   |     |   |     |   |  |  |  |  |  |  |
+| Interworking Label (4 octets)     |      |                         |   |     |   |     |   |  |  |  |  |  |  |
+| Reserved (Note)                   |      | Length indicator (Note) |   |     |   |     |   |  |  |  |  |  |  |
+| Sequence number (2 octets) (Note) |      |                         |   |     |   |     |   |  |  |  |  |  |  |
+| MODE                              | VCIP | RES                     |   | PTI |   | CLP |   |  |  |  |  |  |  |
+| VCI (2 octets)                    |      |                         |   |     |   |     |   |  |  |  |  |  |  |
+| ATM Payload (48 octets)           |      |                         |   |     |   |     |   |  |  |  |  |  |  |
+| MODE                              | VCIP | RES                     |   | PTI |   | CLP |   |  |  |  |  |  |  |
+| VCI (2 octets)                    |      |                         |   |     |   |     |   |  |  |  |  |  |  |
+| ATM Payload (48 octets)           |      |                         |   |     |   |     |   |  |  |  |  |  |  |
+|                                   |      |                         |   |     |   |     |   |  |  |  |  |  |  |
+| MODE                              | VCIP | RES                     |   | PTI |   | CLP |   |  |  |  |  |  |  |
+| VCI (2 octets)                    |      |                         |   |     |   |     |   |  |  |  |  |  |  |
+| ATM Payload (48 octets)           |      |                         |   |     |   |     |   |  |  |  |  |  |  |
+
+NOTE – Presence and use of the common interworking indicators is optional.
+
+**Figure 9/Y.1411 – Concatenated cell encapsulation format (One-to-one mode)**
+
+Description of ATM-MPLS interworking specific header fields are given below:
+
+### ***MODE (bit 8)***
+
+Identifies payload as either cell (= 0), as set for this case, or frame (= 1). In this Recommendation, mode is always set to "0".
+
+### ***VCI Present (bit 7)***
+
+This bit is set to "1" when VCI field is present, set to "0" when no VCI field is present.
+
+For VPCs, the VCI field is present for every cell in the MPLS frame. In a particular case where all the VCI values are the same, VCIP optimization can be used for further bandwidth efficiency. When VCIP optimization is used, the VCI field shall be present in the following cases:
+
+- The cell is the first cell within the MPLS frame.
+- The previous cell within the MPLS frame belongs to a different VCC.
+
+However, the default mode is when there is no VCIP optimization.
+
+#### ***REServed (bits 6 & 5)***
+
+These bits are reserved and are set to "0".
+
+#### ***PTI (bits 4-2)***
+
+Payload Type Identifier incorporates the ATM layer PTI coding of each encapsulated cell. The PTI bits are carried from the ATM cell header without modification by the ATM-to-MPLS direction IWF. This does not preclude the ATM function of the network element in which the IWF resides from modifying the PTI bits, in accordance with ITU-T Rec. I.371 [8], before the interworking conversion.
+
+#### ***CLP (bit 1)***
+
+Cell Loss Priority indicates the CLP value of each encapsulated cell. The CLP bit is carried from the ATM cell header without modification by the ATM-MPLS direction IWF. This does not preclude the ATM function of the network element in which the IWF resides from modifying the CLP bit, in accordance with ITU-T Rec. I.371 [8], before the interworking conversion.
+
+#### ***VCI (2 bytes)***
+
+The VCI value, if present, is the same as that of the encapsulated ATM cell.
+
+# **9 N-to-one mode encapsulation**
+
+## **9.1 Transport label**
+
+The transport label is a four-octet MPLS shim header as specified in [12]. See 7.3.1 for more information.
+
+## **9.2 Interworking label**
+
+The interworking label is a four-octet MPLS shim header as specified in [12]. See 7.3.2 for more information.
+
+The S bit is set to 1 to indicate the bottom of the label stack.
+
+As the interworking label is only significant to the ATM-MPLS interworking functions at either end of the interworking LSP, it appears to the IWFs as though they are directly connected by one hop. The TTL value in the Interworking label should be set to 2.
+
+The setting of the EXP bits are for further study.
+
+## **9.3 Common interworking indicators**
+
+Presence and use of the common interworking indicators is optional.
+
+If present in N-to-one mode, the Common interworking indicators is comprised of a control field, a length field and a sequence number field.
+
+The IWF in the MPLS-to-ATM direction shall be aware of whether the Common interworking indicators (i.e., all fields together) is used. See 6.2 item (f).
+
+### **9.3.1 Control field**
+
+If the common interworking indicators is present, this field shall be present. If present, it is set to all zeros at the ATM-to-MPLS direction IWF and is not processed at the MPLS-to-ATM direction IWF.
+
+### **9.3.2 Length field**
+
+If the common interworking indicators is present, this field shall be present. The use of length indicator function is not required in the N-to-one mode. The two most significant bits of the length field are reserved and are set to zero. The remaining six bits are called length indicator.
+
+If the common interworking indicators is present and length indicator field is not used, this field is set to all zeros at the ATM-to-MPLS direction IWF and is not processed at the MPLS-to-ATM direction IWF.
+
+### **9.3.3 Sequence number field**
+
+If the common interworking indicators is present, this field shall be present. However, the use of sequence number field is optional. The sequence number is a 2-octet field that may be used to monitor the MPLS frame ordered delivery and is set by the IWF in the ATM-to-MPLS direction. The sequence number space is a 16-bit, unsigned circular space.
+
+If the common interworking indicators is present and sequence number function is not used, this field is set to all zeros at the ATM-to-MPLS direction IWF.
+
+#### **9.3.3.1 Procedures for setting the sequence number in the ATM-to-MPLS direction**
+
+See 7.3.3.3.1.
+
+#### **9.3.3.2 Processing the sequence number in the MPLS-to-ATM direction**
+
+See 7.3.3.3.2.
+
+The treatment of packets that are received out of order is for further study.
+
+## **9.4 ATM-MPLS interworking specific header**
+
+In the N-to-one mode, the ATM-MPLS interworking specific header is composed of the ATM cell header minus the HEC field [15].
+
+## **9.5 ATM payload**
+
+This consists of one ATM cell payload (i.e., 48 octets).
+
+## **9.6 Encapsulation**
+
+Two cell encapsulation methods are considered: the single cell encapsulation and the concatenated cell encapsulation. Both methods are allowed in N-to-one mode.
+
+For single cell encapsulation, one ATM cell is encapsulated into a single MPLS frame.
+
+For concatenated cell encapsulation, multiple ATM cells are encapsulated in a single MPLS frame. These cells consists of cells from one or more VCCs and/or VPCS. That is, cells may be concatenated from only one VCC (or VPC) or from multiple VCCs (or VPCs).
+
+The maximum number of concatenated ATM cells is determined by considerations such as the MTU size of the transport medium and QoS requirements for the ATM connection.
+
+The IWF may be configured via provisioning or via signalling to transmit and receive MPLS frames which contain concatenated cells.
+
+In the case of mis-configuration, a receiver that is not configured to support cell concatenation shall discard a received MPLS frame that contains more than one ATM cell payload. The event should be reported to the management plane.
+
+Figures 10 and 11 show the MPLS frame format for single and concatenated cell encapsulation respectively.
+
+![](d9c0a780cd22626253dab4aa41699e2f_img.jpg)
+
+|                                   |   |                         |   |     |   |     |   |
+|-----------------------------------|---|-------------------------|---|-----|---|-----|---|
+| 8                                 | 7 | 6                       | 5 | 4   | 3 | 2   | 1 |
+| Transport label (4 octets)        |   |                         |   |     |   |     |   |
+| Interworking label (4 octets)     |   |                         |   |     |   |     |   |
+| Control (Note)                    |   |                         |   |     |   |     |   |
+| Reserved (Note)                   |   | Length indicator (Note) |   |     |   |     |   |
+| Sequence number (2 octets) (Note) |   |                         |   |     |   |     |   |
+| VPI                               |   |                         |   |     |   |     |   |
+| VPI                               |   |                         |   | VCI |   |     |   |
+| VCI                               |   |                         |   |     |   |     |   |
+| VCI                               |   |                         |   | PTI |   | CLP |   |
+| ATM payload (48 octets)           |   |                         |   |     |   |     |   |
+
+NOTE – Presence and use of the common interworking indicators is optional.
+
+**Figure 10/Y.1411 – Single cell encapsulation (N-to-one mode)**
+
+![](c5452f95f3b28f1bfe29e84fbc2e1267_img.jpg)
+
+|                                   |   |                         |   |     |   |     |   |
+|-----------------------------------|---|-------------------------|---|-----|---|-----|---|
+| 8                                 | 7 | 6                       | 5 | 4   | 3 | 2   | 1 |
+| Transport label (4 octets)        |   |                         |   |     |   |     |   |
+| Interworking label (4 octets)     |   |                         |   |     |   |     |   |
+| Control (Note)                    |   |                         |   |     |   |     |   |
+| Reserved (Note)                   |   | Length indicator (Note) |   |     |   |     |   |
+| Sequence number (2 octets) (Note) |   |                         |   |     |   |     |   |
+| VPI                               |   |                         |   |     |   |     |   |
+| VPI                               |   |                         |   | VCI |   |     |   |
+| VCI                               |   |                         |   |     |   |     |   |
+| VCI                               |   |                         |   | PTI |   | CLP |   |
+| ATM payload (48 octets)           |   |                         |   |     |   |     |   |
+| ⋮                                 |   |                         |   |     |   |     |   |
+| VPI                               |   |                         |   |     |   |     |   |
+| VPI                               |   |                         |   | VCI |   |     |   |
+| VCI                               |   |                         |   |     |   |     |   |
+| VCI                               |   |                         |   | PTI |   | CLP |   |
+| ATM payload (48 octets)           |   |                         |   |     |   |     |   |
+
+NOTE – Presence and use of the common interworking indicators is optional.
+
+**Figure 11/Y.1411 – Concatenated cell encapsulation format (N-to-one mode)**
+
+Description of ATM-MPLS interworking specific header fields are given below:
+
+#### ***VPI***
+
+The ingress IWF shall copy the VPI field from the incoming cell into this field. See Note in Figure 5 for more detail. The egress IWF may generate a new VPI.
+
+### ***VCI***
+
+The ingress IWF shall copy the VCI field from the incoming ATM cell header into this field. See note in Figure 5 for more detail. The egress IWF may generate a new VCI.
+
+### ***PTI***
+
+Payload Type Identifier incorporates the ATM layer PTI coding of each encapsulated cell. The PTI bits are carried from the ATM cell header without modification by the ATM-MPLS ingress IWF. This does not preclude the ATM function of the network element in which the IWF resides from modifying the PTI bits, in accordance with ITU-T Rec. I.371 [8], before the interworking conversion.
+
+### ***CLP***
+
+Cell Loss Priority indicates the CLP value of each encapsulated cell. The CLP bit is carried from the ATM cell header without modification by the ATM-MPLS ingress IWF. This does not preclude the ATM function of the network element in which the IWF resides from modifying the CLP bits, in accordance with ITU-T Rec. I.371 [8], before the interworking conversion.
+
+# **10 OAM and RM cell treatment**
+
+## **10.1 ATM-to-MPLS direction**
+
+### **10.1.1 OAM cells**
+
+Several types of OAM cells are defined in [3]. Applications, such as those identified in [14], utilize these OAM cells. These cells are categorized as:
+
+- fault management cells;
+- performance monitoring and reporting, both in forward and backward directions;
+- user OAM cells (e.g. security OAM cells).
+
+At the ATM layer, two types of OAM cell flows are identified: F4 (OAM flow on virtual path level) and F5 (OAM flow on virtual channel level). F4 and F5 OAM cells are either segment flows for communicating OAM-related information within the boundary of the VPC or VCC, or end-to-end flows for information regarding end-to-end VPC or VCC operations. From an OAM perspective, the network element in which the IWF resides behaves as an ATM switch.
+
+For cell mode encapsulation of user data, OAM cells are encapsulated in the same manner as user data cells.
+
+The general functional architecture of an ATM network element is provided in Figure 4-2/I.732 of [13]. This functional model is used below to describe the treatment of F4 and F5 OAM cells at the network element in which the IWF resides.
+
+The network element in which the IWF resides performs switching at either the VP or the VC level.
+
+#### **VP switching**
+
+F4 OAM cells may be inserted or extracted by the network element in which the IWF resides. These cells are then sent across the LSP according to procedures specified in [13]. F5 OAM are not inserted or extracted here and are therefore simply encapsulated and sent across the LSP.
+
+#### **VC switching**
+
+F4 OAM cells may be inserted or extracted at the VP link termination; such OAM cells are not seen at the VC link termination and are therefore not sent across the LSP. F5 OAM cells are inserted or extracted at the VC link termination or VC termination. These cells are then sent across the LSP according to procedures specified in [13].
+
+### **10.1.2 RM cells**
+
+VC RM cells are identified by a PTI value of 110 and VP RM cells are identified by a VCI value of 6 [15]. VP/VC RM cells are treated the same way as F4/F5 OAM cells respectively in order to maintain cell ordering.
+
+## **10.2 MPLS-to-ATM direction**
+
+OAM and RM cells are received as single encapsulated cells. They are treated at the network element in which the IWF resides in accordance with procedures described in [3], [4], [5] and [8].
+
+
+
+
+
+# SERIES OF ITU-T RECOMMENDATIONS
+
+|                 |                                                                                                                                |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A        | Organization of the work of 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        | 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        | 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 and Internet protocol aspects</b>                                                         |
+| Series Z        | Languages and general software aspects for telecommunication systems                                                           |

marked/Y/T-REC-Y.1412-200311-I_PDF-E/raw.md

@@ -0,0 +1,837 @@
+
+
+![ITU logo: a globe with the letters ITU inside, and a lightning bolt striking the globe.](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg)
+
+ITU logo: a globe with the letters ITU inside, and a lightning bolt striking the globe.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+# ITU-T
+
+TELECOMMUNICATION  
+STANDARDIZATION SECTOR  
+OF ITU
+
+# Y.1412
+
+(11/2003)
+
+SERIES Y: GLOBAL INFORMATION  
+INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS  
+AND NEXT GENERATION NETWORKS
+
+Internet protocol aspects – Interworking
+
+---
+
+**ATM-MPLS network interworking – Frame mode  
+user plane interworking**
+
+ITU-T Recommendation Y.1412
+
+---
+
+# ITU-T Y-SERIES RECOMMENDATIONS **GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT GENERATION NETWORKS**
+
+|                                                                    |                      |
+|--------------------------------------------------------------------|----------------------|
+| 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        |
+| <b>Interworking</b>                                                | <b>Y.1400–Y.1499</b> |
+| 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        |
+| 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        |
+| Numbering, naming and addressing                                   | Y.2300–Y.2399        |
+| Network management                                                 | Y.2400–Y.2499        |
+| Network control architectures and protocols                        | Y.2500–Y.2599        |
+| Security                                                           | Y.2700–Y.2799        |
+| Generalized mobility                                               | Y.2800–Y.2899        |
+
+*For further details, please refer to the list of ITU-T Recommendations.*
+
+## **ITU-T Recommendation Y.1412**
+
+# **ATM-MPLS network interworking – Frame mode user plane interworking**
+
+## **Summary**
+
+This Recommendation addresses the required functions for network interworking between ATM networks and MPLS networks, specifically the user plane interworking mechanisms and procedures. One of the key aspects of network interworking is to provide network support for ATM services during the evolution of networks. Details of the interworking model and required interworking functions are described.
+
+## **Source**
+
+ITU-T Recommendation Y.1412 was approved by ITU-T Study Group 13 (2001-2004) under the ITU-T Recommendation A.8 procedure on 6 November 2003.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. 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, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 2004
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## CONTENTS
+
+|    |                                                                             | <b>Page</b> |
+|----|-----------------------------------------------------------------------------|-------------|
+| 1  | Scope .....                                                                 | 1           |
+| 2  | References.....                                                             | 1           |
+| 3  | Definitions .....                                                           | 2           |
+| 4  | Abbreviations.....                                                          | 2           |
+| 5  | ATM-MPLS interworking .....                                                 | 4           |
+| 6  | General requirements.....                                                   | 4           |
+|    | 6.1 User plane requirements .....                                           | 4           |
+|    | 6.2 Control plane aspects.....                                              | 5           |
+|    | 6.3 Management plane aspects .....                                          | 6           |
+|    | 6.4 Traffic management aspects .....                                        | 6           |
+| 7  | Methods for ATM transport over MPLS .....                                   | 7           |
+|    | 7.1 AAL type 5 PDU mode .....                                               | 7           |
+|    | 7.2 AAL type 5 SDU mode .....                                               | 7           |
+|    | 7.3 Functional group considerations for ATM-MPLS network interworking ..... | 8           |
+| 8  | AAL type 5 PDU mode encapsulation .....                                     | 10          |
+|    | 8.1 Transport label.....                                                    | 10          |
+|    | 8.2 Interworking label .....                                                | 10          |
+|    | 8.3 Common interworking indicators.....                                     | 10          |
+|    | 8.4 ATM-MPLS interworking specific header.....                              | 11          |
+|    | 8.5 Payload .....                                                           | 11          |
+|    | 8.6 Encapsulation .....                                                     | 11          |
+|    | 8.7 AAL type 5 PDU frame fragmentation .....                                | 12          |
+|    | 8.8 Procedure at the egress IWF .....                                       | 12          |
+| 9  | AAL type 5 SDU mode encapsulation .....                                     | 13          |
+|    | 9.1 Transport label.....                                                    | 13          |
+|    | 9.2 Interworking label .....                                                | 13          |
+|    | 9.3 Common interworking indicators.....                                     | 13          |
+|    | 9.4 ATM-MPLS interworking specific header.....                              | 14          |
+|    | 9.5 Payload .....                                                           | 14          |
+|    | 9.6 Encapsulation .....                                                     | 14          |
+|    | 9.7 Procedures at the egress IWF .....                                      | 15          |
+| 10 | OAM and RM cell treatment .....                                             | 16          |
+|    | 10.1 ATM-to-MPLS direction.....                                             | 16          |
+|    | 10.2 MPLS-to-ATM direction.....                                             | 17          |
+| 11 | Security considerations.....                                                | 17          |
+|    | Appendix I – Bibliography .....                                             | 17          |
+
+# **Introduction**
+
+There is a need to focus on the functions required for network interworking between ATM networks and MPLS networks, specifically the user plane interworking mechanisms and procedures. One of the key aspects of network interworking is to provide network support for ATM services during the evolution of networks.
+
+# ITU-T Recommendation Y.1412
+
+# ATM-MPLS network interworking – Frame mode user plane interworking
+
+# 1 Scope
+
+This Recommendation focuses on the functions required for network interworking between ATM and MPLS, specifically the user plane interworking mechanisms and procedures for the AAL type 5 protocol data unit (PDU) and service data unit (SDU) transport modes. In particular, it specifies a list of requirements, interworking scenarios and interworking encapsulation formats and semantics for ATM-MPLS AAL type 5 PDU and SDU mode network interworking.
+
+This Recommendation enables transport of ATM PVC or SVC connections over an MPLS network. The encapsulation allows one AAL type 5 CPCS PDU or SDU to be carried within a single MPLS label switched path (LSP).
+
+The scope includes support of AAL type 5, transport of OAM and RM cells.
+
+# 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.
+
+- [1] IETF RFC 3031 (2001), *Multiprotocol Label Switching Architecture*.
+- [2] ITU-T Recommendation I.610 (1999), *B-ISDN operation and maintenance principles and functions*.
+- [3] ITU-T Recommendation I.610 (1999)/Corrigendum 1 (2000), *B-ISDN operation and maintenance principles and functions*.
+- [4] ITU-T Recommendation I.610 (1999)/Amendment 1 (2000), *B-ISDN operation and maintenance principles and functions*.
+- [5] ITU-T Recommendation Y.1710 (2002), *Requirements for Operation and Maintenance functionality in MPLS networks*.
+- [6] ITU-T Recommendation Y.1711 (2002), *Operation and Maintenance mechanism for MPLS networks*.
+- [7] ITU-T Recommendation I.371 (2000), *Traffic control and congestion control in B-ISDN*.
+- [8] ITU-T Recommendation I.371.1 (2000), *Guaranteed frame rate ATM transfer capability*.
+- [9] ITU-T Recommendation I.356 (2000), *B-ISDN ATM layer cell transfer performance*.
+- [10] IETF RFC 3270 (2002), *Multi-Protocol Label Switching (MPLS) Support of Differentiated Services*.
+- [11] IETF RFC 3032 (2001), *MPLS Label Stack Encoding*.
+- [12] ITU-T Recommendation I.732 (2000), *Functional characteristics of ATM equipment*.
+- [13] ATM Forum af-sec-0100.002 (2001), *ATM Security Specification Version 1.1*.
+
+- [14] ITU-T Recommendation I.363.5 (1996), *B-ISDN ATM Adaptation Layer specification: Type 5 AAL*.
+- [15] ITU-T Recommendation Y.1411 (2003), *ATM-MPLS network interworking – Cell mode user plane interworking*.
+- [17] FR Forum Implementation Agreement FRF.8.1 (2000), *Frame Relay/ATM PVC service interworking implementation agreement*.
+- [18] ITU-T Recommendation I.361 (1999), *B-ISDN ATM layer specification*.
+- [19] ITU-T Recommendation I.510 (1993), *Definitions and general principles for ISDN interworking*.
+
+# 3 Definitions
+
+This Recommendation defines the following terms:
+
+**3.1 interworking:** The term interworking is used to express interactions between networks, between end systems, or between parts thereof, with the aim of providing a functional entity capable of supporting an end-to-end communication. The interactions required to provide a functional entity rely on functions and on the means to select these functions [19].
+
+**3.2 interworking function (IWF):** These functions are referred to in the interworking definition, which include the conversion between protocols and the mapping of one protocol to another. The functionality required between networks can be separated from the functionality, if any, required in end systems. The IWFs needed as a result of a service requirement for interworking are categorized as connection-dependent IWFs (i.e., those functions needed in order to interconnect two networks) or communication-dependent IWFs (i.e., those functions in addition to connection-dependent IWFs needed in order to establish a specific end-to-end communication and which may differ from application to application) [19]. The IWF includes interworking between U-plane, C-plane and M-plane functions.
+
+**3.3 ingress IWF/network element:** The point where the AAL type 5 PDUs or SDUs are encapsulated into an MPLS packet (ATM-to-MPLS direction).
+
+**3.4 egress IWF/network element:** The point where the AAL type 5 PDUs or SDUs are de-encapsulated from an MPLS packet (MPLS-to-ATM direction).
+
+**3.5 MPLS packet payload:** The MPLS packet payload is comprised of the common interworking indicators, the ATM-MPLS interworking specific header and the payload. The length of the MPLS packet payload is expressed in number of octets.
+
+# 4 Abbreviations
+
+This Recommendation uses the following abbreviations.
+
+|       |                             |
+|-------|-----------------------------|
+| AAL   | ATM Adaptation Layer        |
+| AINI  | ATM Inter-Network Interface |
+| ATC   | ATM Transfer Capability     |
+| ATM   | Asynchronous Transfer Mode  |
+| ATM-F | ATM Forum                   |
+| AUU   | ATM User-to-User indication |
+| CES   | Circuit Emulation Service   |
+| CLP   | Cell Loss Priority          |
+
+|         |                                            |
+|---------|--------------------------------------------|
+| CPCS    | Common Part Convergence Sub-layer          |
+| CPCS-UU | CPCS User-to-User indication               |
+| CPI     | Common Part Indicator                      |
+| CRC     | Cyclic Redundancy Check                    |
+| DSS2    | Digital Subscriber Signalling System No. 2 |
+| E-LSP   | EXP-inferred-PSC LSP                       |
+| EFCI    | Explicit Forward Congestion Indication     |
+| EXP     | Experimental Bit                           |
+| FIFO    | First-In First-Out                         |
+| ILMI    | Integrated Local Management Interface      |
+| IP      | Internet Protocol                          |
+| ISH     | Interworking Specific Header               |
+| IWF     | InterWorking Function                      |
+| L-LSP   | Label-only-inferred-PSC LSP                |
+| LSP     | Label Switched Path                        |
+| LSR     | Label Switching Router                     |
+| MPLS    | Multi-Protocol Label Switching             |
+| MTU     | Maximum Transport Unit                     |
+| OAM     | Operation and Maintenance                  |
+| PDU     | Protocol Data Unit                         |
+| PHB     | Per Hop Behaviour                          |
+| PM      | Performance Monitoring                     |
+| PNNI    | Private Network-to-Network Interface       |
+| PSC     | PHB Scheduling Class                       |
+| PTI     | Payload Type Identifier                    |
+| PVC     | Permanent Virtual Circuit                  |
+| QoS     | Quality of Service                         |
+| RFC     | Request For Comments                       |
+| RM      | Resource Management                        |
+| S-bit   | Stack bit                                  |
+| SAP     | Service Access Point                       |
+| SDU     | Service Data Unit                          |
+| SPVC    | Soft PVC                                   |
+| SVC     | Switched Virtual Circuit                   |
+| TTL     | Time To Live                               |
+| UNI     | User-Network Interface                     |
+| UU      | User-to-User                               |
+
+|     |                            |
+|-----|----------------------------|
+| VC  | Virtual Channel            |
+| VCC | Virtual Channel Connection |
+| VCI | Virtual Channel Identifier |
+| VP  | Virtual Path               |
+| VPC | Virtual Path Connection    |
+| VPI | Virtual Path Identifier    |
+
+# 5 ATM-MPLS interworking
+
+The multi-protocol label switching (MPLS) technology [1] allows services to be supported over a single networking infrastructure. Services in this context are traditional data services such as ATM, Frame Relay, IP and circuit emulation services (CES). Figure 5.1 provides the reference network architecture for ATM-MPLS network interworking where ATM network(s) are interconnected through an MPLS network. For the ATM-to-MPLS direction, an AAL type 5 PDU, AAL type 5 PDU fragment or an AAL type 5 SDU are encapsulated in an MPLS packet by the interworking function. For the MPLS-to-ATM direction, reconstruction of the ATM cells is performed.
+
+![Figure 5.1/Y.1412 – Reference network architecture for ATM-MPLS network interworking. The diagram shows a network architecture with three main sections: an ATM network on the left, an MPLS network in the center, and another ATM network on the right. End system 1 is connected to the left ATM network. End system 2 is connected to the right ATM network. Two Interworking Functions (IWF) are shown: one at the interface between the left ATM network and the MPLS network, and another at the interface between the MPLS network and the right ATM network. The IWFs are depicted as trapezoidal blocks with 'ATM' and 'MPLS' labels. The MPLS network is represented by a cloud containing several nodes (circles) connected by lines. A legend at the bottom left indicates that a circle represents an LSR (Label Switched Router) and a thick line represents an LSP (Label Switched Path). A horizontal double-headed arrow at the bottom spans the entire network, with labels 'ATM network', 'MPLS network', and 'ATM network' under the respective sections. The identifier 'Y.1412_F5.1' is located at the bottom right.](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+Figure 5.1/Y.1412 – Reference network architecture for ATM-MPLS network interworking. The diagram shows a network architecture with three main sections: an ATM network on the left, an MPLS network in the center, and another ATM network on the right. End system 1 is connected to the left ATM network. End system 2 is connected to the right ATM network. Two Interworking Functions (IWF) are shown: one at the interface between the left ATM network and the MPLS network, and another at the interface between the MPLS network and the right ATM network. The IWFs are depicted as trapezoidal blocks with 'ATM' and 'MPLS' labels. The MPLS network is represented by a cloud containing several nodes (circles) connected by lines. A legend at the bottom left indicates that a circle represents an LSR (Label Switched Router) and a thick line represents an LSP (Label Switched Path). A horizontal double-headed arrow at the bottom spans the entire network, with labels 'ATM network', 'MPLS network', and 'ATM network' under the respective sections. The identifier 'Y.1412\_F5.1' is located at the bottom right.
+
+**Figure 5.1/Y.1412 – Reference network architecture for ATM-MPLS network interworking**
+
+# 6 General requirements
+
+## 6.1 User plane requirements
+
+For transparent transfer of ATM-related information in the transfer (user) plane, the following are required:
+
+- The ability to multiplex multiple ATM VCCs into a transport LSP.
+- Support for the traffic contracts and the QoS commitments made to the ATM connections.
+- The ability to transparently carry all OAM cells, including the support for proper operation of OAM PM cells.
+- Transport of resource management (RM) cells.
+- Transport of cell loss priority (CLP) indication and explicit forward congestion indication (EFCI) information from AAL type 5 frame.
+- Maintaining frame sequence integrity for AAL type 5 PDU, AAL type 5 PDU fragment or AAL type 5 SDU.
+- Support of ATM point-to-point and ATM point-to-multipoint connections.
+- Support of bidirectional ATM point-to-point connections with symmetric or asymmetric bandwidth.
+
+- i) Support for transparent transport of ATM signalling protocols (e.g., DSS2, B-ISUP, ATM-F UNI, ATM-F PNNI, ATM-F AINI), ATM routing protocols (e.g., ATM-F PNNI) and ATM management protocols (e.g., ATM Forum ILMI), which control the ATM connections across the MPLS network.
+- j) Support of a mechanism to associate the two transport LSPs, one for each direction, to act as a logical ATM port to ATM signalling and routing, capable of carrying ATM connections between two IWFs.
+
+Figure 6.1 shows the network reference model and protocol layers for ATM-MPLS user plane interworking.
+
+![Figure 6.1: Network reference model and protocol layers for ATM-MPLS user plane interworking. The top part shows a high-level network diagram with two ATM clouds connected via IWFs to a central MPLS cloud. Below this, a detailed protocol layer diagram shows the stack for each component. The stacks for the two IWFs and the two MPLS LSPs are shown, with the Physical layer connected between them. The VCC (Virtual Connection) spans the two IWFs and the MPLS LSPs.](e9314c83043183351ed74908e9bf2f90_img.jpg)
+
+The diagram illustrates the network reference model and protocol layers for ATM-MPLS user plane interworking. The top part shows a high-level network diagram with two ATM clouds connected via IWFs to a central MPLS cloud. Below this, a detailed protocol layer diagram shows the stack for each component. The stacks for the two IWFs and the two MPLS LSPs are shown, with the Physical layer connected between them. The VCC (Virtual Connection) spans the two IWFs and the MPLS LSPs.
+
+| Left IWF     |          |                 |                 | MPLS LSP        |                 |          |              | Right IWF |  |  |  |
+|--------------|----------|-----------------|-----------------|-----------------|-----------------|----------|--------------|-----------|--|--|--|
+| Upper layers |          | MPLS LSP stacks | MPLS LSP stacks | MPLS LSP stacks | MPLS LSP stacks |          | Upper layers |           |  |  |  |
+| AAL          | AAL      | Link layer      | Link layer      | Link layer      | Link layer      | AAL      | AAL          |           |  |  |  |
+| ATM          | ATM      |                 |                 |                 |                 | ATM      | ATM          |           |  |  |  |
+| Physical     | Physical | Physical        | Physical        | Physical        | Physical        | Physical | Physical     |           |  |  |  |
+
+Y.1412\_F6.1
+
+Figure 6.1: Network reference model and protocol layers for ATM-MPLS user plane interworking. The top part shows a high-level network diagram with two ATM clouds connected via IWFs to a central MPLS cloud. Below this, a detailed protocol layer diagram shows the stack for each component. The stacks for the two IWFs and the two MPLS LSPs are shown, with the Physical layer connected between them. The VCC (Virtual Connection) spans the two IWFs and the MPLS LSPs.
+
+**Figure 6.1/Y.1412 – Network reference model and protocol layers for ATM-MPLS user plane interworking**
+
+## 6.2 Control plane aspects
+
+For transparent transfer of ATM-related services, the following items are required to be signalled or provisioned:
+
+- a) Exchange of interworking label(s) 20-bit label field between IWFs;
+- b) Correlation of interworking labels for a bidirectional connection for each interworking LSP. Mechanisms are to be defined;
+- c) Operation in PDU or SDU mode;
+- d) Support of the connection types switched virtual connection (SVC) and soft permanent virtual connection (SPVC);
+- e) The ability to control the MPLS interworking LSPs via ATM control protocols by the IWFs for ATM SVCs and ATM Soft PVCs;
+- f) The control of MPLS transport LSPs or interworking LSPs via MPLS control protocols by the IWFs;
+- g) The ability to exchange the MTU size which can be supported.
+
+## 6.3 Management plane aspects
+
+ATM OAM cells carry performance, defect, and protection switching information for VCCs and VPCs on an end-to-end and per segment basis to support the ATM management plane [2], [3] and [4]. OAM functionality in MPLS networks and OAM mechanisms for MPLS networks are specified in ITU-T Recs Y.1710 [5] and Y.1711 [6]. For transparent transfer of ATM-related information in the management plane, the interworking function should support transparent transfer or mapping of performance, defect, and protection switching information between MPLS OAM flows and ATM OAM cells.
+
+As a minimum, the interworking function must transfer ATM OAM information through the MPLS core network by encapsulating OAM cells in MPLS packets. Where end-to-end OAM is required, the interworking function may have to correlate the MPLS OAM information with the ATM OAM. This aspect of OAM interworking with MPLS is outside the scope of this Recommendation.
+
+Figure 6.2 shows functional representation of ATM-MPLS management plane interworking.
+
+![Figure 6.2/Y.1412 – Functional representation of ATM-MPLS management plane interworking. The diagram shows a functional representation of ATM-MPLS management plane interworking. At the top, a horizontal flow shows an ATM cloud connected to an IWF box, which is connected to an MPLS cloud, which is then connected to another IWF box, and finally to another ATM cloud. Below this, a horizontal line with arrows at both ends is divided into three sections: 'ATM management' on the left, 'MPLS management' in the center, and 'ATM management' on the right. Below the 'ATM management' sections, there are two trapezoidal boxes representing the IWF. The left IWF box is divided into two columns: the left column contains 'AIS, RDI, CC, LB, FPM' and the right column contains 'FDI, BDI, CV, LB, P'. The right IWF box is also divided into two columns: the left column contains 'FDI, BDI, CV, LB, P' and the right column contains 'AIS, RDI, CC, LB, FPM'. To the right of the diagram is the label 'Y.1412_F6.2'. Below the diagram is a legend for the OAM codes: AIS Alarm Indication Signal, BDI Backward Defect Indication, CC Continuity Check, CV Connectivity Verification, FDI Forward Defect Indicator, FPM Forward Performance Monitoring, LB Loop Back, P P flows, RDI Remote Defect Indication.](1439cb942d9e363bbb3161b5540dd8c6_img.jpg)
+
+Y.1412\_F6.2
+
+|     |                            |     |                                |
+|-----|----------------------------|-----|--------------------------------|
+| AIS | Alarm Indication Signal    | FPM | Forward Performance Monitoring |
+| BDI | Backward Defect Indication | LB  | Loop Back                      |
+| CC  | Continuity Check           | P   | P flows                        |
+| CV  | Connectivity Verification  | RDI | Remote Defect Indication       |
+| FDI | Forward Defect Indicator   |     |                                |
+
+Figure 6.2/Y.1412 – Functional representation of ATM-MPLS management plane interworking. The diagram shows a functional representation of ATM-MPLS management plane interworking. At the top, a horizontal flow shows an ATM cloud connected to an IWF box, which is connected to an MPLS cloud, which is then connected to another IWF box, and finally to another ATM cloud. Below this, a horizontal line with arrows at both ends is divided into three sections: 'ATM management' on the left, 'MPLS management' in the center, and 'ATM management' on the right. Below the 'ATM management' sections, there are two trapezoidal boxes representing the IWF. The left IWF box is divided into two columns: the left column contains 'AIS, RDI, CC, LB, FPM' and the right column contains 'FDI, BDI, CV, LB, P'. The right IWF box is also divided into two columns: the left column contains 'FDI, BDI, CV, LB, P' and the right column contains 'AIS, RDI, CC, LB, FPM'. To the right of the diagram is the label 'Y.1412\_F6.2'. Below the diagram is a legend for the OAM codes: AIS Alarm Indication Signal, BDI Backward Defect Indication, CC Continuity Check, CV Connectivity Verification, FDI Forward Defect Indicator, FPM Forward Performance Monitoring, LB Loop Back, P P flows, RDI Remote Defect Indication.
+
+**Figure 6.2/Y.1412 – Functional representation of ATM-MPLS management plane interworking**
+
+## 6.4 Traffic management aspects
+
+In ATM, a number of different ATM transfer capabilities (ATC) [7], [8] and quality of service (QoS) classes [9] are defined. A combination of an ATC and an associated QoS class is intended to support an ATM layer service model.
+
+When a transport LSP is used to carry multiple ATM connections with different combinations of ATC and QoS classes, the transport LSP shall be capable of providing the required QoS for all ATM connections. In an MPLS network that does not support QoS differentiation on a per packet basis, the LSP shall meet the most stringent QoS requirements of the ATM connections transported by the LSP.
+
+### 6.4.1 Use of differentiated services for ATM-MPLS interworking
+
+Informational RFC 2475 [I-1] and informational RFC 3260 [I-2] describe one way in which an MPLS network may support differentiated services (DiffServ) behaviour aggregates. MPLS packets
+
+can be treated with different priorities according to a per hop behaviour (PHB). In this case, two different types of LSPs are defined [10] which can both be used for the transport LSP:
+
+- a) Label-only-inferred-PSC LSP(s) (L-LSP);
+- b) EXP-inferred-PSC LSP(s) (E-LSP).
+
+If an L-LSP is used as a transport LSP, the PHB scheduling class (PSC) of each packet is inferred from the label without any other information (e.g., regardless of the EXP field value). In that case, the LSP shall meet the most stringent QoS requirements of the ATM connections transported by the LSP.
+
+If an E-LSP is used as a transport LSP, the EXP field of the transport label is used to determine the PHB to be applied to each packet, i.e., different packets in one LSP may receive a different QoS. The 3-bit EXP field of the transport label can represent eight different combinations of per hop behaviour (PHB) and drop precedence levels. The mapping of the PHB to EXP fields is either explicitly signalled at label set-up or relies on a preconfigured mapping.
+
+The mapping between ATM QoS classes and MPLS PHBs is for further study.
+
+### **6.4.2 Connection admission control for the IWF**
+
+Virtual connections (VCCs, LSPs) have to be managed on both ATM and MPLS sides of the IWF. The IWF binds an ATM connection with a MPLS connection. The MPLS connection consists of a combination of an interworking LSP and a transport LSP. The IWF connection admission control applies to the bandwidth allocation of the transport LSP.
+
+A connection request shall be accepted only when sufficient resources are available to establish the connection through the whole network (ATM network and MPLS network), to comply with the required QoS and to maintain the agreed QoS of the existing connections.
+
+If there is insufficient capacity to accept a new ATM connection, the network may consider to increase the bandwidth of the transport LSP.
+
+# **7 Methods for ATM transport over MPLS**
+
+For transport of AAL type 5 frames over MPLS interworking LSPs, two encapsulation formats are used, one for AAL type 5 PDU mode and the other for AAL type 5 SDU mode.
+
+## **7.1 AAL type 5 PDU mode**
+
+This mode is used for carrying a whole AAL type 5 PDU in the interworking LSP. The whole AAL type 5 PDU is comprised of its payload, padding, and whole trailer, which include CPCS user-to-user indication (CPCS-UU), common part indicator (CPI), length and cyclic redundancy check (CRC). ATM cells of an AAL type 5 PDU are reassembled and the resulting AAL type 5 PDU is encapsulated in one or more (if fragmentation is performed) MPLS packets. The AAL type 5 PDU encapsulation mechanism supports the ordered delivery of OAM cells in respect to cell flow of that connection.
+
+This mode is only applicable to VCCs.
+
+## **7.2 AAL type 5 SDU mode**
+
+This mode is used for carrying an AAL type 5 service data unit (SDU) in the interworking LSP. No trailer or padding bits are carried.
+
+Since the SDU size may vary between 1 and 65535 octets, it is necessary to make the provision for the application of padding. This is to avoid a problem when the transport path includes an Ethernet link, which requires a minimum packet size of 64 octets. Thus, using this mode requires the presence of a length indicator in the length field of the common interworking indicators.
+
+If the ingress IWF determines that an encapsulated AAL type 5 SDU exceeds the MTU size of the transport LSP, then the AAL type 5 SDU should be discarded.
+
+OAM cells that arrive during the reassembly of an AAL type 5 SDU are sent immediately on the LSP followed by the AAL type 5 SDU payload. In this case, cell sequence integrity is lost.
+
+OAM performance monitoring, as specified in ITU-T Rec I.610 [2], [3] and [4], should not be used in combination with SDU frame mode because the cell sequence integrity is not maintained.
+
+This mode is only applicable to VCCs.
+
+## 7.3 Functional group considerations for ATM-MPLS network interworking
+
+Figure 7.1 provides an illustration of functional grouping for ATM-MPLS network interworking.
+
+|                                       |
+|---------------------------------------|
+| MPLS transport label                  |
+| Interworking label                    |
+| Common interworking indicators        |
+| ATM-MPLS interworking specific header |
+| Payload                               |
+
+**Figure 7.1/Y.1412 – ATM-MPLS interworking functional groups**
+
+### 7.3.1 MPLS transport label
+
+The 4-octet MPLS transport label identifies a LSP used to transport traffic between two ATM-MPLS IWFs. The MPLS transport label is a standard MPLS shim header [11]. This label is processed at each LSR. Since MPLS LSPs are unidirectional, a pair of MPLS transport LSPs carrying traffic in opposite directions will be required to create a bidirectional transport. The setting of the EXP and TTL fields of the MPLS transport label is outside the scope of this Recommendation. The S bit is set to 0 for this label, indicating that this is not the bottom of the label stack. More than one transport LSP may exist in each direction at any given time between any two ATM-MPLS IWFs.
+
+### 7.3.2 Interworking label
+
+The 4-octet interworking label uniquely identifies one interworking LSP carried inside a MPLS transport LSP. The interworking label is a standard MPLS shim header [11]. More than one interworking LSP may be supported by one MPLS transport LSP.
+
+Since an MPLS LSP is unidirectional, for the case of bidirectional ATM VCCs, there will be two different interworking LSPs, one for each direction of the connection. These may have different label values.
+
+The interworking function maintains context information that associates ATM connections with the interworking LSP.
+
+In the MPLS-to-ATM direction, the 20-bit interworking label field value is translated to the VPI and VCI. This association is signalled or provisioned between a pair of peer IWFs. MPLS packets received with an invalid or unassigned interworking label are discarded.
+
+The S bit is set to 1 to indicate the bottom of the label stack.
+
+As the interworking label is only significant to the ATM-MPLS interworking functions at either end of the interworking LSP, it appears to the IWFs as though they are directly connected by a link of one hop. Therefore, the TTL value in the interworking label should be set to 2.
+
+The setting of the EXP bits are for further study.
+
+### **7.3.3 Common interworking indicators**
+
+The functions in the common interworking indicators are related to the interworking LSP.
+
+In general, the common interworking indicators functional group is comprised of a control field, a length field and a sequence number field.
+
+#### **7.3.3.1 Control field**
+
+The control field is not present when operating in AAL type 5 PDU mode. It only exists when operating in AAL type 5 SDU mode. See 9.3.1.
+
+#### **7.3.3.2 Length field**
+
+The length field indicates the length of the payload. When the LSP path includes an Ethernet link, a minimum packet size of 64 octets is required. This may require padding to be applied to the MPLS packet payload in order to reach this minimum MPLS packet size. The padding size can be determined from the length field so that the padding can be extracted at the egress.
+
+This field shall always be present. See 8.3.2 and 9.3.2.
+
+#### **7.3.3.3 Sequence number field**
+
+The sequence number field is used to check the sequence integrity of MPLS packets sent from the ingress IWF to the egress IWF. In general, ATM services require that the sequence integrity be maintained. When ATM services are transported over an underlying MPLS-based network, it is required that the MPLS network should attempt to maintain the sequence integrity of the ATM cells encapsulated in the MPLS packets.
+
+Even under the normal "first-in first-out" (FIFO) operation, it is possible that misordering of the packets could occur. As an option, the sequence number field can be set by the IWF in the ATM-to-MPLS direction. The sequence number is a 2-octet field using a 16-bit, unsigned circular space.
+
+This field shall be present, but its use is optional. If the sequence number function is not used, then it is set to all zeros at the ATM-to-MPLS direction IWF.
+
+###### **7.3.3.3.1 Setting the sequence number**
+
+If the sequence number field is used, then the following procedures apply in the ATM-to-MPLS direction:
+
+- a) The sequence number shall be set to 1 for the first MPLS packet transmitted on the interworking LSP.
+- b) For each subsequent MPLS packet, the sequence number shall be incremented by 1.
+- c) If the result of incrementing is a value of 65535 for the current MPLS packet, the sequence number shall be reset to 1 for the next MPLS packet.
+
+If the ingress IWF does not use the sequence number, then the sequence number field shall be set to zero.
+
+##### **7.3.3.3.2 Processing the sequence numbers**
+
+If the IWF is capable of monitoring sequence integrity, then the following procedures shall be used:
+
+- a) If the sequence number is 0, the sequence integrity of the packets cannot be determined by the IWF. In this case, the received packet is considered to be in order.
+- b) Otherwise, if the sequence number  $\geq$  the expected sequence number, and the sequence number – the expected sequence number  $< 32768$ , then the received packet is considered to be in order.
+
+- c) Otherwise, if the sequence number < the expected sequence number, and the expected sequence number – the sequence number  $\geq 32768$ , then the received packet is considered to be in order.
+- d) Otherwise, the received packet is out of order.
+- e) If the received packet is in order, then the expected sequence number = the sequence number +1 mod  $2^{16}$ .
+- f) If the expected sequence number = 0, then the expected sequence number = 1.
+
+NOTE – The initial expected sequence number is set to 1.
+
+### **7.3.4 ATM-MPLS interworking specific header**
+
+The ATM-MPLS interworking specific header (ISH) contains information that is used to reconstruct the ATM cells or AAL type 5 frames from a MPLS packet in the MPLS-to-ATM direction at the egress IWF.
+
+# **8 AAL type 5 PDU mode encapsulation**
+
+This clause provides procedures for the encapsulation of AAL type 5 PDU or an AAL type 5 PDU fragment into a MPLS packet at the ingress IWF. Procedures for fragmentation of AAL type 5 PDU are provided in this clause. This clause also provides procedures for reconstruction of ATM cells from the AAL type 5 PDU or an AAL type 5 PDU fragment at the egress IWF.
+
+## **8.1 Transport label**
+
+The transport label is a four-octet MPLS shim header as specified in [11]. See 7.3.1 for more detail.
+
+## **8.2 Interworking label**
+
+The interworking label is a four-octet MPLS shim header as specified in [11]. See 7.3.2 for more detail.
+
+## **8.3 Common interworking indicators**
+
+This field is always present.
+
+In AAL type 5 PDU mode the common interworking indicators field is comprised of a one-octet length field and a two-octet sequence number field.
+
+The IWF in the MPLS-to-ATM direction shall be aware of whether the common interworking indicators (i.e., all fields together) are used.
+
+### **8.3.1 Control field**
+
+This field is not present when operating in AAL type 5 PDU mode.
+
+### **8.3.2 Length field**
+
+The length indicator function is not used in AAL type 5 PDU mode. The two most significant bits of the length field are set to zero. The remaining six bits are called length indicator (even though not used in this mode). The first two significant bits of the length indicator are set to zero and the remaining four bits are reserved.
+
+### **8.3.3 Sequence number field**
+
+See 7.3.3.3.
+
+## 8.4 ATM-MPLS interworking specific header
+
+The ATM-MPLS interworking specific header identifies whether ATM cells or AAL type 5 frames are encapsulated. In addition, other elements of the protocol control information constitute parts of this header (see Figure 8.1).
+
+## 8.5 Payload
+
+The payload consists of the reassembled AAL type 5 CPCS-PDU, including the AAL type 5 padding and trailer or the AAL type 5 fragment.
+
+## 8.6 Encapsulation
+
+Figure 8.1 shows the MPLS packet format for the AAL type 5 PDU or AAL type 5 fragment.
+
+If the AAL type 5 PDU and other fields as identified in Figure 7.1 exceed the MPLS network MTU size or if OAM cells arrive during reassembly of AAL type 5 frames, the AAL type 5 PDU shall be fragmented (see 8.7).
+
+Mechanisms to detect misconfiguration of the ATM encapsulation mode and the consequent actions to be taken are for further study.
+
+![](43837b056625d3d6ce615e4c02f163bb_img.jpg)
+
+|                               |      |                  |   |   |     |      |     |
+|-------------------------------|------|------------------|---|---|-----|------|-----|
+| Bits                          |      |                  |   |   |     |      |     |
+| 8                             | 7    | 6                | 5 | 4 | 3   | 2    | 1   |
+| Transport label (4 octets)    |      |                  |   |   |     |      |     |
+| Interworking label (4 octets) |      |                  |   |   |     |      |     |
+| 0                             | 0    | Length indicator |   |   |     |      |     |
+| Sequence number (2 octets)    |      |                  |   |   |     |      |     |
+| MODE                          | VCIP | RES              |   |   | AUU | EFCI | CLP |
+| Payload                       |      |                  |   |   |     |      |     |
+
+NOTE – Bit 8 is the most significant bit
+
+**Figure 8.1/Y.1412 – AAL type 5 PDU encapsulation**
+
+Description of ATM-MPLS interworking specific header fields are given below:
+
+### MODE (bit 8)
+
+Bit (MODE) indicates whether the MPLS packet contains an ATM cell or an AAL type 5 PDU frame. In this Recommendation, MODE is always set to "1".
+
+MODE = 0, the MPLS packet contains an ATM cell, encapsulated according to the VCC cell one-to-one mode (see Figure 8/Y.1411 [15]).
+
+MODE = 1, the MPLS packet contains an AAL type 5 PDU frame.
+
+NOTE – The bit called MODE is functionally similar to the bit T in the SDU encapsulation format.
+
+### VCI Present (bit 7)
+
+This bit is always set to 0.
+
+#### REServed (bits 6-4)
+
+These bits are reserved and are set to "0".
+
+#### **AUU bit (bit 3)**
+
+This bit indicates whether the payload in the MPLS packet contains the last of the cells comprising the AAL type 5 PDU frame or fragment.
+
+AUU = 1 indicates the presence of the last cell. Otherwise it is set to 0.
+
+### **EFCI (bit 2)**
+
+The EFCI state of the reassembled AAL type 5 PDU is conveyed in the EFCI field of the ATM-MPLS interworking specific header. The EFCI state of an AAL type 5 PDU or AAL type 5 fragment is set to 1 if the last ATM cell of the AAL type 5 PDU or AAL type 5 fragment has its EFCI bit set to "1", otherwise it is set to "0". This field carries the EFCI state of the PTI field of the last ATM cell encapsulated within the MPLS packet. The EFCI is the middle bit of the PTI field.
+
+### **CLP (bit 1)**
+
+The CLP state of the reassembled AAL type 5 PDU is conveyed in the CLP field of the ATM-MPLS interworking specific header. The CLP state of the AAL type 5 PDU or the AAL type 5 fragment is set to 1 if any of their constituent ATM cells has its CLP bit set to 1. Otherwise it is set to "0".
+
+## **8.7 AAL type 5 PDU frame fragmentation**
+
+It may not always be possible to reassemble a full AAL type 5 frame at an ATM-MPLS IWF. This may be due to the AAL type 5 PDU and other fields as identified in Figure 7.1 exceed the MPLS network MTU size or if OAM or RM cells arrive during reassembly of an AAL type 5 PDU. In these cases, the AAL type 5 PDU shall be fragmented. Fragmentation is a function that is used to subdivide the payload into a series of fragments. In addition, fragmentation may be used to bound ATM cell delay.
+
+When fragmentation occurs, the procedures described in the following clause shall be followed. Note that fragmentation always occurs at the ingress IWF (i.e., ATM-to-MPLS direction).
+
+### **8.7.1 Fragmentation procedures**
+
+- a) Fragmentation shall always occur at cell boundaries within the AAL type 5 PDU.
+- b) The AUU bit in the ATM-MPLS ISH for the fragment shall be set to the value of the ATM user-to-user bit in the cell header of the last received ATM cell to be included in the MPLS packet (see 8.6).
+- c) The EFCI and CLP fields in the ATM specific header of the fragment shall be set as per 8.6.
+- d) If the arriving cell is an OAM or an RM cell, then the current MPLS packet shall be sent immediately followed by the OAM or the RM cell using one-to-one single cell mode defined in ITU-T Rec. Y.1411 [15].
+
+## **8.8 Procedure at the egress IWF**
+
+The following provides procedures at the egress IWF (MPLS-to-ATM direction) when an AAL type 5 frame or AAL type 5 fragment arrives as the payload part of the MPLS packet (see Figure 8.1).
+
+At the egress IWF, cells are constructed from whole AAL type 5 PDU or AAL type 5 PDU fragments. There is no reassembly of the fragments in order to construct the AAL type 5 PDU.
+
+The AAL type 5 PDU or AAL type 5 PDU fragment is an integral multiple of 48 octets.
+
+The information exchanged between the ATM layer and the IWF across the ATM-SAP includes the following primitive (see ITU-T Rec. I.361 [18]):
+
+ATM-DATA request (ATM cell payload (i.e., ATM-SDU), cell loss priority, congestion indication, ATM user-to-user indication (AUU)).
+
+The parameter values for the request for all constituent ATM cells of an AAL type 5 PDU or AAL type 5 fragment are as follows:
+
+- The congestion indication parameter is set to the EFCI value of the ATM-MPLS interworking specific header.
+- If the AUU bit of the ATM-MPLS interworking specific header equal to 1 then:
+  - The ATM user-to-user indication (AUU) of the last ATM cell in the MPLS packet is set to the value of the AUU bit of the ISH.
+  - For all other cells, the ATM user-to-user indication (AUU) is set to zero.
+- The cell loss priority parameter is copied from the CLP bit of the ATM-MPLS interworking specific header (ISH).
+
+# **9 AAL type 5 SDU mode encapsulation**
+
+This clause provides procedures for the encapsulation of AAL type 5 SDU into a MPLS packet at the ingress IWF and the reconstruction of AAL type 5 PDU at the egress IWF.
+
+## **9.1 Transport label**
+
+The transport label is a four-octet MPLS shim header as specified in [11]. See 7.3.1 for more information.
+
+## **9.2 Interworking label**
+
+The interworking label is a four-octet MPLS shim header as specified in [11]. See 7.3.2 for more information.
+
+## **9.3 Common interworking indicators**
+
+For AAL type 5 SDU mode, the common interworking indicators field is comprised of a one-octet control field, a one-octet length field and a two-octet sequence number field.
+
+This field is always present.
+
+### **9.3.1 Control field**
+
+The four most significant bits of the control field are reserved and are set to zero. The four least significant bits are the T bit, the E bit, the C bit and the U bit. These bits are explained in 9.6.
+
+### **9.3.2 Length field**
+
+The two most significant bits of the length field are reserved and are set to zero. The remaining six bits are called length indicator.
+
+The length indicator provides, in octets, the size of the MPLS packet payload without padding bits if performed (see 9.5). The length indicator value is comprised of:
+
+- a) size of the common interworking indicators; and
+- b) size of the payload.
+
+The length field is always used.
+
+#### 9.3.2.1 Setting the length indicator in the ATM-to-MPLS direction
+
+The IWF shall use the following procedures:
+
+- If the MPLS packet payload size is greater than or equal to 64 octets, the length indicator field shall be set to 0.
+- If the MPLS packet payload size is less than 64 octets, the length field shall be set to the packet length (see 9.5).
+
+### 9.3.3 Sequence number field
+
+See 7.3.3.3.
+
+## 9.4 ATM-MPLS interworking specific header
+
+There is no ATM-MPLS interworking specific header field present when operating in AAL type 5 SDU mode.
+
+## 9.5 Payload
+
+The payload consists of the reassembled AAL type 5 CPCS-SDU without the padding bits and the trailer. If the length of the MPLS packet payload is less than 64 octets then padding will be performed (see 7.3.3.2). The new MPLS packet payload is then comprised of the old MPLS packet payload plus additional padding.
+
+## 9.6 Encapsulation
+
+Figure 9.1 shows structure of the common interworking indicators and the ATM AAL type 5 SDU payload.
+
+Mechanisms to detect misconfiguration of the ATM encapsulation mode and the consequent actions to be taken are for further study.
+
+![](cd141897aa368dbbaa398ace230cdd85_img.jpg)
+
+|                            |   |                  |   |   |   |   |   |  |  |  |  |  |  |
+|----------------------------|---|------------------|---|---|---|---|---|--|--|--|--|--|--|
+| Bits                       |   |                  |   |   |   |   |   |  |  |  |  |  |  |
+| 8                          | 7 | 6                | 5 | 4 | 3 | 2 | 1 |  |  |  |  |  |  |
+| Reserved                   |   |                  |   | T | E | C | U |  |  |  |  |  |  |
+| Reserved                   |   | Length indicator |   |   |   |   |   |  |  |  |  |  |  |
+| Sequence number (2 octets) |   |                  |   |   |   |   |   |  |  |  |  |  |  |
+| Payload                    |   |                  |   |   |   |   |   |  |  |  |  |  |  |
+
+NOTE – Bit 8 is the most significant bit.
+
+**Figure 9.1/Y.1412 – AAL type 5 SDU encapsulation**
+
+Descriptions of the constituent parts of the control fields are given below.
+
+### Reserved (bits 8-5)
+
+The reserved bits in the control field shall be set to zero when transmitting and shall be ignored on receipt.
+
+### **T (transport type, bit 4)**
+
+Bit (T) indicates whether the MPLS packet contains an ATM cell or an ATM AAL type 5 SDU frame.
+
+T = 1, the MPLS packet contains an ATM cell, encapsulated according to the N-to-one cell mode (see Figure 10/Y.1411 [15]).
+
+T = 0, the MPLS packet contains an AAL5 SDU frame.
+
+NOTE – The bit T is functionally similar to the mode bit in the PDU encapsulation format.
+
+#### **E (EFCI, bit 3)**
+
+Bit E is set to 1 if the last constituent ATM cell of the AAL5 SDU has its EFCI bit set to “1”, otherwise it is set to “0”.
+
+#### **C (CLP, bit 2)**
+
+The CLP state of the reassembled AAL type 5 SDU is conveyed in as the C bit. The CLP bit of the AAL type 5 SDU is set to 1 if any of the AAL type 5 SDU constituent ATM cells has its CLP bit set to 1, otherwise it is set to 0.
+
+#### **U (Command/Response indicator, bit 1)**
+
+An AAL type 5 SDU is created by removing the padding and the trailer from AAL type 5 PDU. One of the constituent parts of an AAL type 5 trailer is the CPCS-UU (CPCS user-to-user indication). For AAL type 5 SDU mode, only the least significant bit of this octet, i.e., the U bit, is transported in the control field.
+
+If the AAL type 5 frame is the result of frame relay (FR) and ATM service interworking as per frame relay FRF.8.1 [17], then the least significant bit of the CPCS-UU is the same as the Command/Response bit of the frame relay frame.
+
+The least significant bit of the CPCS-UU of the AAL type 5 PDU trailer is set as the U bit.
+
+## **9.7 Procedures at the egress IWF**
+
+The following provides procedures at the egress IWF (MPLS-to-ATM direction) when an MPLS packet arrives.
+
+The AAL type 5 PDU is reconstructed from the payload part of the MPLS packet (see Figure 9.1) and the control field.
+
+### **9.7.1 Processing the length indicator**
+
+The IWF shall follow the following procedures:
+
+- a) If the length field is 0, or if the packet size is the same as that indicated by the length field, then no action shall be taken. The payload is the SDU.
+- b) If the MPLS packet payload size is larger than that indicated by the length field, the padding is removed.
+- c) If the MPLS packet payload size is smaller than that indicated by the length field, the packet is discarded.
+
+### 9.7.2 Reconstruction of AAL type 5 PDU
+
+The IWF provides the capabilities to transfer the AAL type 5 SDU from MPLS packet to the ATM network. ITU-T Rec. I.363.5 [14] is used for reassembly of the AAL5 PDU.
+
+The information exchanged between the AAL type 5 layer and the IWF across the AAL-SAP is identical to the CPCS primitives (see 7.2/I.363.5 [14]). The following primitive is used:
+
+CPCS-UNITDATA invoke (CPCS-SDU, CPCS-Loss Priority (CPCS-LP), CPCS Congestion Indication (CPCS-CI), CPCS User-to-User indication (CPCS-UU)).
+
+The parameter values of the "request" for an AAL type 5 SDU are as follows:
+
+- 1) The CPCS congestion indication parameter is set to the E (EFCI) value of the control field;
+- 2) The CPCS user-to-user indication is copied from U (Command/Response indicator) bit;
+- 3) The CPCS loss priority parameter is copied from the C (CLP) bit of the control field.
+
+# 10 OAM and RM cell treatment
+
+## 10.1 ATM-to-MPLS direction
+
+### 10.1.1 OAM cells
+
+Several types of OAM cells are defined in [2], [3] and [4]. Applications, such as those identified in [13], utilize these OAM cells. These cells are categorized as:
+
+- a) Fault management cells;
+- b) Performance monitoring and reporting, both in forward and backward directions;
+- c) User OAM cells (e.g., security OAM cells).
+
+At the ATM layer, two types of OAM cell flows are identified: F4 (OAM flow on virtual path level) and F5 (OAM flow on virtual channel level). F4 and F5 OAM cells are either segment flows for communicating OAM-related information within the boundary of the VPC or VCC, or end-to-end flows for information regarding end-to-end VPC or VCC operations. From an OAM perspective, the IWF behaves as an ATM switch.
+
+OAM cells are always encapsulated using cell mode encapsulation, regardless of the encapsulation format implemented for user data (see 8.6 and 9.6/Y.1411 [15]).
+
+In frame mode encapsulation of user data, OAM cells that arrive during the reassembly of an AAL type 5 frame the following procedures to be invoked:
+
+For AAL type 5 PDU mode the partially reassembled AAL type 5 PDU is sent as a fragment, immediately followed by the OAM cell. Reassembly of the AAL type 5 PDU is then resumed. If an OAM cell arrives between AAL type 5 PDUs, then it is sent using cell mode encapsulation (see 8.6/Y.1411 [15]). This procedure ensures cell sequence integrity for user cells and OAM cells.
+
+For AAL type 5 SDU mode, OAM cells that arrive during the reassembly of a single AAL type 5 CPCS-PDU are sent immediately using cell mode encapsulation (see Figure 10/Y.1411 [15]) on the LSP followed by the AAL type 5 SDU payload. This service does not attempt to maintain the relative order of these OAM cells with respect to the ATM cells that comprise the AAL type 5 frame.
+
+The general functional architecture of an ATM network element is provided in Figure 4-2/I.732 [12]. This functional model is used below to describe the treatment of F4 and F5 OAM cells at the IWF.
+
+#### *VP switching*
+
+This case is not supported by this Recommendation.
+
+#### *VC switching*
+
+F4 OAM cells may be inserted or extracted at the VP link termination; such OAM cells are not seen at the VC link termination and are, therefore, not sent across the LSP. F5 OAM cells are inserted or extracted at the VC link termination or VC termination. These cells are then sent across the LSP according to procedures specified in [12].
+
+### **10.1.2 RM cells**
+
+VC RM cells use a PTI value of 110 and VP RM cells are identified by a VCI of 6 [18]. VP/VC RM cells are treated the same way as F4/F5 OAM cells in order to maintain cell ordering.
+
+## **10.2 MPLS-to-ATM direction**
+
+OAM and RM cells are received as single encapsulated cells. They are treated at the IWF in accordance with procedures described in [2], [3], [4] and [7].
+
+# **11 Security considerations**
+
+There are no security related issues identified in this Recommendation.
+
+# **Appendix I**
+
+## **Bibliography**
+
+- [I-1] IETF RFC 2475 (1998), *An Architecture for Differentiated Services*.
+- [I-2] IETF RFC 3260 (2002), *New terminology and clarifications for Diffserv*.
+
+
+
+
+
+## SERIES OF ITU-T RECOMMENDATIONS
+
+|                 |                                                                                                                                |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Series A        | Organization of the work of 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        | 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        | 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, Internet protocol aspects and Next Generation Networks</b>                               |
+| Series Z        | Languages and general software aspects for telecommunication systems                                                           |