Unit 3 First Half IoT Notes PDF
Document Details
Uploaded by ComplimentaryChalcedony4079
Tags
Summary
These notes cover the potential negative impacts of Global Value Chain (GVC) participation, focusing on workplace conditions, safety, and job security, and discuss recommendations. Then it details M2M to IoT architecture, highlighting four and five-layered architectures, functions of each layer, and building blocks like sensors, processors, gateways, and applications.
Full Transcript
# Potential Negative Impacts of GVC Participation - Poor workplace conditions - Occupational safety and health - Job security **Reason:** The relative ease with which Value Chain Governors can relocate their production to lower cost countries also creates additional risks. ## Promoting GVC Partic...
# Potential Negative Impacts of GVC Participation - Poor workplace conditions - Occupational safety and health - Job security **Reason:** The relative ease with which Value Chain Governors can relocate their production to lower cost countries also creates additional risks. ## Promoting GVC Participation **Recommendations:** 1. **Careful Assessment:** Countries need to carefully assess the pros and cons of GVC participation and the costs and benefits of proactive policies to promote GVCs or GVC-led development strategies. 2. **Targeting Specific GVC Segments:** Promoting GVC participation implies targeting specific GVC segments and GVC participation can only form one part of a country's overall development strategy. 3. **Evaluating Trade Profiles and Industrial Capabilities:** Before promoting GVC participation, policymakers should evaluate their countries' trade profiles and industrial capabilities in order to select strategic GVC development paths. 4. **Structured Approach:** Achieving upgrading opportunities through GVCs requires a structured approach that includes: - Embedding GVCs in industrial development policies (e.g. targeting GVC tasks and activities) - Enabling GVC growth by providing the right framework conditions for trade and FDI - Developing firm capabilities and training the local workforce ## M2M to IoT-An Architectural Overview ### IoT Architecture Overview IoT can be classified into a four or five-layered Architecture: #### Four-layered Architecture - Media/device layer - Network layer - Service and application support layer - Application layer #### Five-layered Architecture - Perception layer - Network layer - Middleware layer - Application layer - Business layer ### Functions of Each Layer - **Sensor/Perception layer:** This layer comprises of wireless devices, sensors, and radio frequency identification (RFID) tags that are used for collecting and transmitting raw data such as the temperature, moisture, etc., which is passed on to the next layer. - **Network layer:** This layer is largely responsible for routing data to the next layer in the hierarchy with the help of network protocols. It uses wired and wireless technologies for data transmission. - **Middleware layer:** This layer comprises of databases that store the information passed on by the lower layers where it performs information processing and uses the results to make further decisions. - **Service and application support layer:** This layer involves business process modeling and execution as well as IoT service monitoring and resolution. - **Application layer:** It consists of application user interface and deals with various applications such as home automation, electronic health monitoring, etc. - **Business layer:** This layer determines the future or further actions required based on the data provided by the lower layers. ### Building an IoT Architecture #### Building Blocks of IoT - **Sensors:** The front end of the IoT devices; they are the so-called “Things” of the system. Their main purpose is to collect data from its surroundings (sensors) or give out data to its surrounding (actuators). They have to be uniquely identifiable devices with a unique IP address so that they can be easily identifiable over a large network. They have to be active in nature which means that they should be able to collect real-time data. These can either work on their own (autonomous in nature) or can be made to work by the user depending on their needs (user-controlled). - **Processors:** The brain of the IoT system. Their main function is to process the data captured by the sensors and process them so as to extract the valuable data from the enormous amount of raw data collected. In a word, we can say that it gives intelligence to the data. - **Gateways:** Responsible for routing the processed data and send it to proper locations for its (data) proper utilization. In other words, we can say that gateway helps in to and fro communication of the data. It provides network connectivity to the data. Network connectivity is essential for any IoT system to communicate. - **Applications:** Another end of an IoT system. Applications are essential for proper utilization of all the data collected. These cloud-based applications which are responsible for rendering the effective meaning to the data collected. Applications are controlled by users and are a delivery point of particular services. ### Main Design Principles of IoT 1. **Do your research:** - When designing IoT-enabled products, designers might make the mistake of forgetting why customers value these products in the first place. - Think about the value an IoT offering should deliver at the initial phase of your design. - Instead of building products, consider building services and experiences that improve people's lives. - Assume the perspective of your customers to understand what they need and how your IoT implementation can solve their pain points. - Research your target audience deeply to see what their existing experiences are and what they wish was different about them. 2. **Concentrate on value:** - Early adopters are eager to try out new technologies. But the rest of your customer base might be reluctant to put a new solution to use. - If you want your IoT solution to become widely adopted, you need to focus on the actual tangible value it's going to deliver to your target audience. - What is the real end-user value of your solution? - What might be the barriers to adopting new technology? - How can your solution address them specifically? - Note that the features the early tech adopters might find valuable might turn out to be completely uninteresting for the majority of users. - Carefully plan which features to include and in what order, always concentrating on the actual value they provide. 3. **Don't forget about the bigger picture:** - One characteristic trait of IoT solutions is that they typically include multiple devices that come with different capabilities and consist of both digital and physical touchpoints. - Your solution might also be delivered to users in cooperation with service providers. - Take the bigger picture into account and treat your IoT system holistically. - Delineate the role of every device and service. - Develop a conceptual model of how users will perceive and understand the system. - All the parts of your system need to work seamlessly together. - Only then you'll be able to create a meaningful experience for your end-users. 4. **Remember about the security:** - IoT solutions aren't purely digital. They're located in the real-world context, and the consequences of their actions might be serious if something goes wrong. - Building trust in IoT solutions should be one of your main design drivers. - Make sure that every interaction with your product builds consumer trust rather than breaking it. - Understand all the possible error situations that may be related to the context of its use. - Design your product in a way to prevent them. - If error situations occur, make sure that the user is informed appropriately and provided with help. - Consider data security and privacy as a key aspect of your implementation. - Users need to feel that their data is safe, and objects located in their workspaces or home can't be hacked. - Quality assurance and testing the system in the real-world context are important. 5. **Build with the context in mind:** - IoT solutions are located at the intersection of the physical and digital world. - The commands you give through digital interfaces produce real-world effects. - Unlike digital commands, these actions may not be easily undone. - In a real-world context, many unexpected things may happen. - Make sure that the design of your solution enables users to feel safe and in control at all times. - The context itself is a crucial consideration during IoT design. - Depending on the physical context of your solution, you might have different goals in mind. - The social context is an important factor, as well. - Don't forget that the devices you design for workspaces or homes will be used by multiple users. 6. **Make good use of prototypes:** - IoT solutions are often difficult to upgrade. Once the user places the connected object somewhere, it might be hard to replace it with a new version, especially if the user would have to pay for the upgrade. - The software within the object might be hard to update because of security and privacy reasons. - Design practices should help to avoid costly hardware iterations. - Get your solution right from the start. - Prototyping and rapid iteration will become critical in the early stages of the project. ### Standards Consideration for IoT - Alliances have been formed by many domestic and multinational companies to agree on common standards and technology for the IoT. - However, no universal body has been formed yet. - Organizations such as IEEE, Internet Engineering Task Force (IETF), ITU-T, OneM2M, 3GPP, etc., are active at the international level. - Telecommunication Standards Development Society, India (TSDSI), Global ICT Standardization Forum for India (GISFI), Bureau of Indian Standards (BIS), Korean Agency for Technology and Standards (KATS), and so on, are active at the national level. - European Telecommunications Standards Institute (ETSI) is active at the regional level for standardization.