DOCSLIB.ORG

Longitude: a Privacy-Preserving Location Sharing Protocol for Mobile Applications⋆

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Longitude: a Privacy-Preserving Location Sharing Protocol for Mobile Applications⋆ Longitude: a Privacy-preserving Location Sharing Protocol for Mobile Applications⋆ Changyu Dong, Naranker Dulay Department of Computing Imperial College London {changyu.dong,n.dulay}@imperial.ac.uk Abstract. Location sharing services are becoming increasingly popular. Although many location sharing services allow users to set up privacy policies to control who can access their location, the use made by service providers remains a source of concern. Ideally, location sharing providers and middleware should not be able to access users’ location data without their consent. In this paper, we propose a new location sharing protocol called Longitude that eases privacy concerns by making it possible to share a user’s location data blindly and allowing the user to control who can access her location, when and to what degree of precision. The underlying cryptographic algorithms are designed for GPS-enabled mobile phones. We describe and evaluate our implementation for the Nexus One Android mobile phone. 1 Introduction Location sharing is an increasingly popular function of social-networking services, al- lowing users to share their location with family and friends. Examples include Google Latitude [1], Yahoo Fire Eagle [2], and Loopt [3]. Perhaps the biggest user concern about location sharing services is privacy. Many services allow the users to control who will have access to their location data, over what period of time, and to what degree of precision. However, for many users, the service providers are also a source of concern. Will not the location sharing service use location data to the detriment of the user? Users’ location data is normally saved by the service provider. Unfortunately, this allows providers to track, profile and target users [4,5] as well as aggregrate the data and sell it to others. The typical approach to informing users is to provide a lengthy webpage that states what the service provider may do with the data. The webpage is usually written in a sufficiently obfuscated way to ensure that few users will bother reading it, and often to hide the fact that providerswant to give themselves a high degree of access to the data. A related, but important concern, is that the service provider may be the target of network intrusions and untrustworthy insiders, as well as requests from law-enforcement agencies [6]. This paper describes a protocol called Longitude for location sharing that uses cryp- tography to limit service provider access to location data. It is aimed at providerson the ⋆ This work was supported by UK EPSRC research grant EP/F023294/1 - PRiMMA: Privacy Rights Management for Mobile Applications. Internet or middleware to provide location sharing blindly without the hassle of com- pliance to data protection and location data requests. It ensures that users are able to share their location but are not tracked. Note that the protocol is not a replacement for traditional location-services like Google maps that translate locations into maps. Naively, a user (Alice) could encrypt her location before sending it to the location sharing provider (Luke), effectively protecting it from Luke or other adversaries. Alice would have to securely disseminate the key to her friends (Bob and Carol) and revoke it if she wanted to prevent access to any friend or if the key was disclosed. Rather than a common shared key, Alice could establish pair-wise secret keys with each of her friends or use asymmetric keys, both requiring a great deal more additional storage, computa- tion and communication overheads. A more flexible approach is needed, particularly for resource-constrained mobile devices. Longitude has the following characteristics: 1. Privacy preserving. Longitude enables location-sharing providers or middleware to disseminate user location data blindly. The data is specially encrypted. Alice can control which of her friends can see her location, at what times and to what degree of precision. 2. Simple key management: Alice only needs to keep her own key on her mobile de- vice. She can remove any of her friends at any time without affecting other friends. The revocation process can be done by Alice without requiring any interactions with her friends. 3. Lightweight cryptography.Most of the computationallyintensive cryptographicop- erations in Longitude are done by the service provider, not on the mobile device. Computation and battery life for mobile devices can be optimised further by pre- computing cryptographic material when the mobile device is connected to a power source. 4. Constant communication overhead. Longitude’s communication costs do not in- crease with the number of friends (receivers). No matter how many friends a user has, each piece of location data is encrypted and sent only once. Therefore, the overhead of data communication is minimised. The paper is organised as follows: in Section 2, we summarise the related work; in Section 3, we discuss the system and security model as well as the initial assumptions; in Section 4, we present Longitude, how to fine control user privacy and issues related to user revocation; in Section 5, we explain the underlying cryptographic techniques; in Section 6, we describe and evaluate a prototype implementation of Longitude for Android phones; in Section 7, we conclude the paper and discuss our future plans. 2 Related Work Location sharing services have attracted a lot of attention from industry [1–3], and the development of GPS-enabled mobile phones makes it easy to sense and share user location. According to [7], these services can be categorised into two types: (1) purpose- driven,in which the requesterhas a specific need for the users location, e.g. coordinating meetings, arranging transportation, sending reminders, and (2) social, in which location information is shared simply because it is interesting or fun to do so. However, users are concerned about their privacy and according to [8], existing industry guidelines and implementations do not adequately address these concerns . Previous research on location privacy has focused on anonymisation. For example, in [9], the authors describe a middleware system which delays and reorders messages from users within a mix zone to confuse an observer.In [10],a mechanism called cloak- ing is proposed that conceals a user within a group of k people. To achieve this, the accuracy of the disclosed location is reduced so that a user is indistinguishable from at least k − 1 other users. In [11], k-anonymity is achieved by an ad-hoc network formed by the user and surrounding neighbours, while [12] shows how to achieve k-anonymity in a distributed environment where there are multiple non-colluding servers. Anonymi- sation has a fundamental difference with location sharing. The goal of anonymisation is to prevent others from relating a location to a user; on the other hand, the goal of loca- tion sharing is to let authorised users know where a user is. Therefore, anonymisation is not directly applicable here. Most existing location sharing services do offer the users some form of controls over their privacy. In [8], the authors examine 89 location sharing services and the most widely adopted privacy controls are white list, being invisible, blacklist, group-based permission and providing less detailed location. Several research projects in this area have tried to provide more expressive and effective policy-based privacy controls. For example, Locaccino [13] allows users to specify more fine grained policies based on temporal and spatial restrictions. The pawS system [14] allows a user to use P3P policies to define their location privacy settings and negotiate with the location service provider. The main drawback in all such approaches is that the users must trust the provider, its privileged employees and the security of the infrastructure. The user’s privacy will also be compromised if the service provider is required to disclose the data to a law- enforcement agency. In a location sharing services, the providerusually acts as a broker to disseminate the location information to the authorised receivers. In most of the cases the provider does not need to know the data content in order to provide this service. In [15] a system for sharing user location is described which provides protection from the provider. Users use pairwise symmetric key encryption or asymmetric key encryption to prevent the provider from learning their location. However, the user needs to store multiple keys. Moreover the user has to send multiple copies of the same data, each encrypted under a different key in order to let all her friends be able to get her location. The overheads of key management, computation and communication increase linearly with the number of friends. Some work [16–19] has been done dealing with the problem of preserving privacy in proximity services. Proximity service is a sub-type of location sharing service which notifies and displays a friend’s location if the friend is nearby. While in Longitude we consider the more general location sharing where a user can see a friend’s location no matter the friend is near or far away from the user. 3 Models and Assumptions 3.1 Systems model The Longitude protocol has the following parties: the location-sharing service provider and the set of users registered with the provider. We assume that each user has a GPS- enabled mobile phone that can sense the user’s current location and send it to the provider. The provider stores the location and along with some user configuration data. Users define which other users are authorised to receive their location. Authorised re- ceivers can be removed at any time by the user. Users can also define the precision of the location that will be seen by a particular receiver, e.g. accurate to 1km, 5km, 10km, 100km. 3.2 Security Model We consider the service-provider to be honest-but-curious.
Load more

Recommended publications
  • Efficient Implementation of Elliptic Curve Cryptography in Reconfigurable Hardware
    EFFICIENT IMPLEMENTATION OF ELLIPTIC CURVE CRYPTOGRAPHY IN RECONFIGURABLE HARDWARE by E-JEN LIEN Submitted in partial fulfillment of the requirements for the degree of Master of Science Thesis Advisor: Dr. Swarup Bhunia Department of Electrical Engineering and Computer Science CASE WESTERN RESERVE UNIVERSITY May, 2012 CASE WESTERN RESERVE UNIVERSITY SCHOOL OF GRADUATE STUDIES We hereby approve the thesis/dissertation of _____________________________________________________E-Jen Lien candidate for the ______________________degreeMaster of Science *. Swarup Bhunia (signed)_______________________________________________ (chair of the committee) Christos Papachristou ________________________________________________ Frank Merat ________________________________________________ ________________________________________________ ________________________________________________ ________________________________________________ (date) _______________________03/19/2012 *We also certify that written approval has been obtained for any proprietary material contained therein. To my family ⋯ Contents List of Tables iii List of Figures v Acknowledgements vi List of Abbreviations vii Abstract viii 1 Introduction 1 1.1 Research objectives . .1 1.2 Thesis Outline . .3 1.3 Contributions . .4 2 Background and Motivation 6 2.1 MBC Architecture . .6 2.2 Application Mapping to MBC . .7 2.3 FPGA . .9 2.4 Mathematical Preliminary . 10 2.5 Elliptic Curve Cryptography . 10 2.6 Motivation . 16 i 3 Design Principles and Methodology 18 3.1 Curves over Prime Field . 18 3.2 Curves over Binary Field . 25 3.3 Software Code for ECC . 31 3.4 RTL code for FPGA design . 31 3.5 Input Data Flow Graph (DFG) for MBC . 31 4 Implementation of ECC 32 4.1 Software Implementation . 32 4.1.1 Prime Field . 33 4.1.2 Binary Field . 34 4.2 Implementation in FPGA . 35 4.2.1 Prime Field . 36 4.2.2 Binary Field .
    [Show full text]
  • A High-Speed Constant-Time Hardware Implementation of Ntruencrypt SVES
    A High-Speed Constant-Time Hardware Implementation of NTRUEncrypt SVES Farnoud Farahmand, Malik Umar Sharif, Kevin Briggs, Kris Gaj Department of Electrical and Computer Engineering, George Mason University, Fairfax, VA, U.S.A. fffarahma, msharif2, kbriggs2, [email protected] process a year later. Among the candidates, there are new, Abstract—In this paper, we present a high-speed constant- substantially modified versions of NTRUEncrypt. However, in time hardware implementation of NTRUEncrypt Short Vector an attempt to characterize an already standardized algorithm, Encryption Scheme (SVES), fully compliant with the IEEE 1363.1 Standard Specification for Public Key Cryptographic Techniques in this paper, we focus on the still unbroken version of the Based on Hard Problems over Lattices. Our implementation algorithm published in 2008. We are not aware of any previous follows an earlier proposed Post-Quantum Cryptography (PQC) high-speed hardware implementation of the entire NTRUEn- Hardware Application Programming Interface (API), which crypt SVES scheme reported in the scientific literature or facilitates its fair comparison with implementations of other available commercially. Our implementation is also unique in PQC schemes. The paper contains the detailed flow and block diagrams, timing analysis, as well as results in terms of latency (in that it is the first implementation of any PQC scheme following clock cycles), maximum clock frequency, and resource utilization our newly proposed PQC Hardware API [3]. As such, it in modern high-performance Field Programmable Gate Arrays provides a valuable reference for any future implementers of (FPGAs). Our design takes full advantage of the ability to paral- PQC schemes, which is very important in the context of the lelize the major operation of NTRU, polynomial multiplication, in ongoing NIST standard candidate evaluation process.
    [Show full text]
  • FIDO Technical Glossary
    Client to Authenticator Protocol (CTAP) Implementation Draft, February 27, 2018 This version: https://fidoalliance.org/specs/fido-v2.0-id-20180227/fido-client-to-authenticator-protocol-v2.0-id- 20180227.html Previous Versions: https://fidoalliance.org/specs/fido-v2.0-ps-20170927/ Issue Tracking: GitHub Editors: Christiaan Brand (Google) Alexei Czeskis (Google) Jakob Ehrensvärd (Yubico) Michael B. Jones (Microsoft) Akshay Kumar (Microsoft) Rolf Lindemann (Nok Nok Labs) Adam Powers (FIDO Alliance) Johan Verrept (VASCO Data Security) Former Editors: Matthieu Antoine (Gemalto) Vijay Bharadwaj (Microsoft) Mirko J. Ploch (SurePassID) Contributors: Jeff Hodges (PayPal) Copyright © 2018 FIDO Alliance. All Rights Reserved. Abstract This specification describes an application layer protocol for communication between a roaming authenticator and another client/platform, as well as bindings of this application protocol to a variety of transport protocols using different physical media. The application layer protocol defines requirements for such transport protocols. Each transport binding defines the details of how such transport layer connections should be set up, in a manner that meets the requirements of the application layer protocol. Table of Contents 1 Introduction 1.1 Relationship to Other Specifications 2 Conformance 3 Protocol Structure 4 Protocol Overview 5 Authenticator API 5.1 authenticatorMakeCredential (0x01) 5.2 authenticatorGetAssertion (0x02) 5.3 authenticatorGetNextAssertion (0x08) 5.3.1 Client Logic 5.4 authenticatorGetInfo (0x04)
    [Show full text]
  • White-Box Implementation of the Identity-Based Signature Scheme in the IEEE P1363 Standard for Public Key Cryptography
    IEICE TRANS. INF. & SYST., VOL.E103–D, NO.2 FEBRUARY 2020 188 INVITED PAPER Special Section on Security, Privacy, Anonymity and Trust in Cyberspace Computing and Communications White-Box Implementation of the Identity-Based Signature Scheme in the IEEE P1363 Standard for Public Key Cryptography Yudi ZHANG†,††, Debiao HE†,††a), Xinyi HUANG†††,††††, Ding WANG††,†††††, Kim-Kwang Raymond CHOO††††††, Nonmembers, and Jing WANG†,††, Student Member SUMMARY Unlike black-box cryptography, an adversary in a white- box security model has full access to the implementation of the crypto- graphic algorithm. Thus, white-box implementation of cryptographic algo- rithms is more practical. Nevertheless, in recent years, there is no white- box implementation for public key cryptography. In this paper, we propose Fig. 1 A typical DRM architecture the first white-box implementation of the identity-based signature scheme in the IEEE P1363 standard. Our main idea is to hide the private key to multiple lookup tables, so that the private key cannot be leaked during the algorithm executed in the untrusted environment. We prove its security in both black-box and white-box models. We also evaluate the performance gram. However, the adversary does not have the permis- of our white-box implementations, in order to demonstrate utility for real- sion to access the internal process of the program’s execu- world applications. tion. In practice, an adversary can also observe and mod- key words: white-box implementation, white-box security, IEEE P1363, ify the algorithm’s implementation to obtain the internal de- identity-based signature, key extraction tails, such as the secret key.
    [Show full text]
  • IEEE P1363.3 Standard Specifications for Public Key Cryptography
    IEEE P1363.3 D1 IBKAS January 29, 2008 IEEE P1363.3 Standard Specifications for Public Key Cryptography: Identity Based Key Agreement Scheme (IBKAS) Abstract. This document specifies pairing based, identity based, and authenticated key agreement techniques. One of the advantages of Identity Based key agreement techniques is that there is no public key transmission and verification needed. Contents 1. DEFINITIONS ......................................................................................................................................... 2 2. TYPES OF CRYPTOGRAPHIC TECHNIQUES ................................................................................ 2 2.1 GENERAL MODEL .................................................................................................................................. 2 2.2 PRIMITIVES............................................................................................................................................ 2 2.3 SCHEMES ............................................................................................................................................... 3 2.4 ADDITIONAL METHODS ......................................................................................................................... 3 2.5 TABLE SUMMARY.................................................................................................................................. 3 3. PRIMITIVES FOR IDENTITY BASED KEY AGREEMENT PROBLEM...................................... 4 3.1 PRIMITIVES BORROWED FROM
    [Show full text]
  • IEEE P1363.2: Password-Based Cryptography
    IEEE P1363.2: Password-based Cryptography David Jablon CTO, Phoenix Technologies NIST PKI TWG - July 30, 2003 What is IEEE P1363.2? • “Standard Specification for Password-Based Public-Key Cryptographic Techniques” • Proposed standard • Companion to IEEE Std 1363-2000 • Product of P1363 Working Group • Open standards process PKI TWG July 2003 IEEE P1363.2: Password-based Cryptography 2 One of several IEEE 1363 standards • Std 1363-2000 • Sign, Encrypt, Key agreem’t, using IF, DL, & EC families • P1363a • Same goals & families as 1363-2000 • P1363.1: Lattice family • Same goals as 1363-2000, Different family • P1363.2: Password-based • Same families • More ambitious goals PKI TWG July 2003 IEEE P1363.2: Password-based Cryptography 3 Scope of P1363.2 • Modern “zero knowledge” password methods • Uses public key techniques • Uses two or more parties • Needs no other infrastructure • Authenticated key establishment • Resists attack on low-grade secrets • passwords, password-derived keys, PINs, ... PKI TWG July 2003 IEEE P1363.2: Password-based Cryptography 4 Rationale (1) • Why low-grade secrets? • People have trouble with high-grade keys • storage -- memorizing • input -- attention to detail • output -- typing • Passwords are ubiquitous • Easy for people to memorize, recognize, and type. • Reduce security/convenience tradeoffs. PKI TWG July 2003 IEEE P1363.2: Password-based Cryptography 5 Rationale (2) • Why use public-key techniques? • Symmetric methods can’t do it. • Why new methods? • Different than symmetric, hash, or other PK crypto. • AES, SHA-1, DH, and RSA can’t do it alone. PKI TWG July 2003 IEEE P1363.2: Password-based Cryptography 6 Chosen Password Quality Summarized from Distribution Morris & Thompson ‘79, Klein ‘90, Spafford ‘92 0 30 or so 60 or so Password Entropy (bits) History of protocols that fail to dictionary attack (or worse) • Clear text password π • Password as a key Eπ (verifiable text) • (e.g.
    [Show full text]
  • The Martini Synch
    The Martini Synch Darko Kirovski, Michael Sinclair, and David Wilson Microsoft Research Contact: {darkok,sinclair,dbwilson}@microsoft.com Technical Report MSR-TR-2007-123 September 2007 Microsoft Research One Microsoft Way Redmond, WA 98052, USA http://research.microsoft.com The Martini Synch Darko Kirovski, Michael Sinclair, and David Wilson Microsoft Research Abstract. Device pairing is a significant problem for a large class of increasingly popular resource-constrained wireless protocols such as BlueTooth. The objective of pairing is to establish a secure wireless communication channel between two specific devices without a public-key infrastructure, a secure near-field communi- cation channel, or electrical contact. We use a surprising user-device interaction as a solution to this problem. By adding an accelerometer, a device can sense its motion in a Cartesian space relative to the inertial space. The idea is to have two devices in a fixed, relative position to each other. Then, the joint object is moved randomly in 3D for several seconds. The unique motion generates approximately the same distinct signal at the accelerometers. The difference between the signals in the two inertially conjoined sensors should be relatively small under normal motion induced manually. The objective is to derive a deterministic key at both sides with maximized entropy that will be used as a private key for symmetric encryption. Currently, our prototype produces between 10–15 bits of entropy per second of usual manual motion using off-the-shelf components. Keywords: device pairing, key exchange, fuzzy hashing, error correction. 1 INTRODUCTION Establishing a secure session is one of the least efficiently resolved problems with mod- ern low-cost wireless protocols such as BlueTooth [1].
    [Show full text]
  • A Low-Power Design for an Elliptic Curve Digital Signature Chip
    A Low-Power Design for an Elliptic Curve Digital Signature Chip Richard Schroeppel, Cheryl Beaver, Rita Gonzales, Russell Miller, and Timothy Draelos Sandia National Laboratories Albuquerque, NM 87185-0785 {rschroe, cbeaver, ragonza, rdmille, tjdrael}@sandia.gov Abstract. We present a VHDL design that incorporates optimizations intended to provide digital signature generation with as little power, space, and time as possible. These three primary objectives of power, size, and speed must be balanced along with other important goals, including flexibility of the hardware and ease of use. The highest-level function offered by our hardware design is Elliptic Curve Optimal El Gamal digital signature generation. Our parameters are defined over the finite field GF (2178), which gives security that is roughly equivalent to that provided by 1500-bit RSA signatures. Our optimizations include using the point-halving algorithm for elliptic curves, field towers to speed up the finite field arithmetic in general, and further enhancements of basic finite field arithmetic operations. The result is a synthesized VHDL digital signature design (using a CMOS 0.5µm,5V ,25◦C library) of 191,000 gates that generates a signature in 4.4 ms at 20 MHz. Keywords: Digital Signature, Elliptic Curve, ECDSA, Optimal El Gamal, Characteristic 2, Field Towers, Trinomial Basis, Quadratic Equa- tion, Qsolve, Almost-Inverse Algorithm, Point Halving, Signed Sliding Window, GF(289), GF(2178), Hardware, VHDL, Low Power 1 Introduction While the value of elliptic curve arithmetic in enabling public-key cryptography to serve in resource-constrained environments is well accepted, efforts in cre- ative implementations continue to bear fruit.
    [Show full text]
  • FPGA Implementation of Post-Quantum Cryptography Recommended by NIST
    University of Windsor Scholarship at UWindsor Electronic Theses and Dissertations Theses, Dissertations, and Major Papers 3-10-2021 FPGA Implementation of Post-Quantum Cryptography Recommended by NIST Xi Gao University of Windsor Follow this and additional works at: https://scholar.uwindsor.ca/etd Recommended Citation Gao, Xi, "FPGA Implementation of Post-Quantum Cryptography Recommended by NIST" (2021). Electronic Theses and Dissertations. 8556. https://scholar.uwindsor.ca/etd/8556 This online database contains the full-text of PhD dissertations and Masters’ theses of University of Windsor students from 1954 forward. These documents are made available for personal study and research purposes only, in accordance with the Canadian Copyright Act and the Creative Commons license—CC BY-NC-ND (Attribution, Non-Commercial, No Derivative Works). Under this license, works must always be attributed to the copyright holder (original author), cannot be used for any commercial purposes, and may not be altered. Any other use would require the permission of the copyright holder. Students may inquire about withdrawing their dissertation and/or thesis from this database. For additional inquiries, please contact the repository administrator via email ([email protected]) or by telephone at 519-253-3000ext. 3208. FPGA Implementation of Post-Quantum Cryptography Recommended by NIST by Xi Gao A Thesis Submitted to the Faculty of Graduate Studies through Electrical and Computer Engineering in Partial Fulfilment of the Requirements for the Degree of Master of Applied Science at the University of Windsor Windsor, Ontario, Canada 2021 © 2021, Xi Gao FPGA Implementation of Post-Quantum Cryptography Recommended by NIST by Xi Gao APPROVED BY: X.
    [Show full text]
  • Hardware Architectures of Elliptic Curve Based Cryptosystems Over Binary Fields
    Hardware Architectures of Elliptic Curve Based Cryptosystems over Binary Fields Chang Shu Doctoral Dissertation Defense Feb. 8, 2007 Advisor: Dr. Kris Gaj Dept. of Electrical & Computer Engineering George Mason University 1 Acknowledgements Dr. Kris Gaj (Dissertation Director) Dr. Soonhak Kwon (Dept. of Mathematics, Sungkyunkwan University, Korea) Dr. Shih-Chun Chang (Committee Member) Dr. Brian L. Mark (Committee Member) Dr. Ravi Sandu (Committer Member) Dr. Andre Manitius (Chair of ECE) Dr. Yariv Ephraim (Ph.D. Coordinator) Dr. Tarek El-Ghazawi (Dept. of ECE at The George Washington University) 2 Overview • Introduction – Elliptic Curve Cryptography – Tate Pairing Based Cryptography • Architectures for Finite Field Arithmetic – Polynomial basis multiplier – Normal basis multiplier – Composite field arithmetic • Architectures for Elliptic Curve Cryptosystems – Optimizations for a single FPGA device – Reconfigurable computing approach • Architectures for Tate Pairing Based Cryptosystems – Optimizations for a single FPGA device – Reconfigurable computing approach • Summary 3 Elliptic Curve Cryptosystems • Family of public key cryptosystems • Invented in 1985 by Miller and Koblitz independently • Used primarily for digital signatures & key exchange • Included in multiple industry, government, and banking standards, such as IEEE p1363, ANSI 9.62, and FIPS 186-2 • Part of standard security protocols, such as IPSec and SSL (proposed extension) 4 Why Elliptic Curve Cryptography ? – ECC vs. RSA Key size comparison: Security Level (bits) 80 112
    [Show full text]
  • Competency Models
    SCIENCE, TECHNOLOGY, ENGINEERING & MATHEMATICS Architectural and Engineering Managers ACCCP Engineering and Technology Alabama Competency Model Architectural and Engineering Managers Code 1 Tier 1: Personal Effectiveness Competencies 1.1 Interpersonal Skills: Displaying the skills to work effectively with others from diverse backgrounds. 1.1.1 Demonstrating sensitivity/empathy 1.1.1.1 Show sincere interest in others and their concerns. 1.1.1.2 Demonstrate sensitivity to the needs and feelings of others. 1.1.1.3 Look for ways to help people and deliver assistance. 1.1.2 Demonstrating insight into behavior Recognize and accurately interpret the communications of others as expressed through various 1.1.2.1 formats (e.g., writing, speech, American Sign Language, computers, etc.). 1.1.2.2 Recognize when relationships with others are strained. 1.1.2.3 Show understanding of others’ behaviors and motives by demonstrating appropriate responses. 1.1.2.4 Demonstrate flexibility for change based on the ideas and actions of others. 1.1.3 Maintaining open relationships 1.1.3.1 Maintain open lines of communication with others. 1.1.3.2 Encourage others to share problems and successes. 1.1.3.3 Establish a high degree of trust and credibility with others. 1.1.4 Respecting diversity 1.1.4.1 Demonstrate respect for coworkers, colleagues, and customers. Interact respectfully and cooperatively with others who are of a different race, culture, or age, or 1.1.4.2 have different abilities, gender, or sexual orientation. Demonstrate sensitivity, flexibility, and open-mindedness when dealing with different values, 1.1.4.3 beliefs, perspectives, customs, or opinions.
    [Show full text]
  • White Blue and Lightnings
    Sirius Microtech LLC Innovative People Connectivity and Interoperability Of Embedded Systems Raja D. Singh http://www.siriusmicrotech.com [email protected] Sirius Microtech LLC Innovative People Little bit about me ● Curious about how things work ● Electronics and Communications Engineer ● Hardware Engineer ● Software, Firmware Architect ● Automation, Machine builder ● Senior Member of IEEE ● Vice Chair of IEEE Computer society, Foothills Section ● Chair of IEEE Consultants Network, Los Angeles ● Founder of Sirius Microtech LLC ● Attitude “Work is for fun” ● Currently working on IoT and LED Lighting applications Sirius Microtech LLC Innovative People Connectivity ● Ability to meaningful Communication ● Information exchange ● Possibility to correct errors ● Repeat reliably Sirius Microtech LLC Innovative People Why network? ● Connected computers serve content ● Contents consumed by other computers ● Consumption by users ● Place to buy my ‘Things’ ● Place of learn about ‘Things’ ● Place to socialize and do fun ‘Things’ ● Place to download ‘Things’ ● Market for personal computers – approximately 5! Sirius Microtech LLC Innovative People A networked device ● What is this ‘Thing’? ● A computing device ● Monitor and Control ● Collect ‘Information’ ● Work with other ‘Things’ ● Embedded system Sirius Microtech LLC Innovative People Embedded system ● Constrained ● Resource strapped ● Headless ● OS, Bare metal ● Battery or Mains powered ● Mostly low power ● Wearable or implantable ● Network connectible Sirius Microtech LLC Innovative
    [Show full text]