M2M Service Architecture: Delivering M2M Services Over Heterogeneous Networks

Transcription

1 Service Architecture: Delivering Services Over Heterogeneous Networks IEEE Communications Quality & Reliability 202 International Workshop May 7, 202 Chonggang Wang InterDigtial Communications

2 Agenda Overview Protocol Stack Service Architecture CoAP Protocol Evolution to IoT 2

3 Overview - Definition Machine-to-Machine () is about communication among devices (such as a sensor or meter) without (or only limited) human intervention to capture/retrieve an event or status (such as temperature, inventory level, etc.), which is relayed through a network (wireless, wired or hybrid) to an application (software program), that translates the captured event into meaningful information (for example, items need to be restocked). a huge amount of resource-constrained or powerful devices autonomous device operation and management seamless domain inter-operability energy efficiency self-organization Source: Wikipedia 3

4 Overview General Network Architecture Devices Area Networks Gateway Access Networks Core Networks Server Network s Devices Access Networks Core Networks Server Network s Area Networks IEEE , etc Consists of resource-constrained devices (sensors and actuators) Gateway Converged GW Connects area networks to core networks via access networks Access Networks xdsl/cable, 3G/LTE, PLC Connects GW to core Core Networks IPv4/v6 Connects to Sever Server Connects to applications and/or backend database 4

5 Overview - Enabling Technologies Services and s Sensing Data Analytics Embedded Devices RESTful Web Communications IPv6/6LoWPAN 5

6 Overview Some Deployments Proprietary Logic Set A Proprietary Logic Set B Proprietary Logic Set C Proprietary Logic Set D Logic Proprietary Service Function Set A Proprietary Service Function Set B Proprietary Service Function Set C Proprietary Service Function Set D Proprietary Service Functions RFID RFID GPS, Cellular WiFI, BT, WSN Smart City in Oulu Communications Infrastructure Vertical and Proprietary Solution 6

7 Overview Characteristics and Challenges Huge Number of Devices device management, system optimization Diverse s and Use Cases Different traffic model: event-based, query-based, continuous streaming Different performance requirements: delay, lifetime, security, energy-efficiency Heterogeneous Communications Technologies Wireless: Capillary vs Cellular; Short-range vs Long-range Wired: PLC, Ethernet, xdsl, Fiber Different Actors device manufacturers, network providers, service providers, application providers, & system integrators Horizontal solutions are required to be standardized. 7

8 Overview Horizontal Solutions A B C D Logic Common Service Functions Open Middleware Platform Common Service Functions Wireless, Wireline, and/or Hybrid Networks Communications Infrastructure Horizontal solution means network & application-agnostic, but aware. This is the first step and a key enabler towards the Internet-of-Things (IoT) 8

9 Protocol Stack Service Layer Service Layer (ETSI Service Architecture) Control and Management Plane Transport Layer Network MAC/PHY 3GPP MTC (Device triggering, small data transmissions, etc) Cellular (2G/3G/LTE) Transport Protocols (CoAP/UDP; HTTP/TCP) IPv4/IPv6 (IETF ROLL/6LoWPAN) IEEE 802. IEEE Wireline (PLC, etc) (device management, service discovery, context information management, etc ) (SNMP, OMA DM, BBF TR069,etc) 9

10 Device Domain ETSI Service Architecture Network Domain 0

11 ETSI Service Architecture Service Capabilities s mia Device Domain s dia Service Capabilities Communication modules mid Service Capabilities SC SC2 SC3 SC7 SC8 SC4 SC6 SC5 Core Network Connection Core Network A Core Network B The list of Service Capabilities (SC) are: Enablement (xae) Generic Communication (xgc) Reachability, Addressing and Repository (xrar) Communication Selection (xcs) Remote Entity Management (xrem) SECurity (xsec) History and Data Retention (xhdr) Transaction Management (xtm) Compensation Broker (xcb) Telco Operator Exposure (xtoe) Interworking Proxy (xip) where x is: N for Network, consists of the complete ETSI core network infrastructure communication with gateways and devices. G for Gateway, is an ETSI device specialized to directly manage area networks of ETSI devices; the gateway directly communicates with an ETSI core network. D for Device, is an ETSI device than can directly communicate to an ETSI core network or to an ETSI gateway.

12 ETSI Service Architecture Resource Tree Area Network Area Network 2 Area Network N ehealth / mhealth (Bluetooth / ZigBee ) s Smart Energy (WiFi / ZigBee / ) s Home Automation (ZigBee / Bluetooth / ) s Gateway s <sclbase> n Server <sclbase> scls n applications containers scls groups accessrights applications containers discovery groups Device s <sclbase> n scls applications containers groups accessrights discovery Service Provider s accessrights discovery <sclbase-of-d/g/n> scls applications groups containers accessrights discovery <scl> <applicationannc> <groupannc> <application> accessrights <group> applications accessrights containers containers groups groups <containerannc> members memberscontent <container> notificationchannels notificationchannels m2mpocs attacheddevices mgmtobjs containerinstances latest <containerinstance> oldest 2

13 ETSI Service Architecture Service and Registration Device (DA) dia Gateway (GSCL) mid Network (NSCL) Secure service bootstrap and connection GSCL initiated; created GSCL resource tree root and its child resources <myhomegscl>/ NSCL initiated; created NSCL resource tree root and its child resources <examplenscl>/ mia Network (NA) Responses not shown for simplicity GSCL Registers to NSCL (CREATE) DA Registers to GSCL (CREATE) Created counterpart resource for NSCL <myhomegscl>/scls/<exa mplenscl> Created resource for GSCL < examplenscl> /scls/<myhomegscl> NA Registers to NSCL (CREATE) Created resource for DA registration <myhomegscl>/ap plications/heating- App-ID Created resource for NA registration <examplenscl>/appli cations/smarthome-id 3

14 ETSI Service Architecture Resource Announcement/Discovery 4

15 ETSI Service Architecture Resource Subscription/Notification Device (DA) dia Gateway (GSCL) mid Network (NSCL) mia Network (NA) NA subscribes to DA data stored on GSCL (CREATE) Created subscription resource <myhomegscl>/applications/he ating-app- ID/containers/temperature/conten tinstances//tempsub DA writes new data to GSCL container (UPDATE) Updated resource for DA <myhomegscl>/applications /Heating-App- ID/containers/temperature/con tentinstances/myhometemp2 Notification to NA (NOTIFY) Obtained new temp 5

16 ETSI Service Architecture HTTP and CoAP Binding 6

17 ETSI Service Architecture Leveraging Verticals 7

18 CoAP Constrained IP Networks A constrained IP network is a network which consists of devices. Both the network and devices have the following unique features, in contrast to general IP networks. Limited packet sizes High degree of packet loss A number of low-duty cycling devices with severe limits on throughput, available device power, device RAM, and affordable complexity. An example: low-power wireless personal area networks (LoWPANs) -related resources in a constrained IP network include: Sensors (e.g. temperature sensors, light switches, power meters, etc) Actuators (e.g. light switches, heating controllers, door locks) Combinations of values or other information Common operations to/within constrained IP networks: Monitor sensors Control actuators Manage devices 8

19 CoAP Representative State Transfer (REST) REST is a style of software architecture for distributed hypermedia systems such as WWW. Six Constrains of REST Client-Server : a uniform interface to connect clients and servers Stateless: servers keep no state for previous client requests Cacheable: clients are able to cache responses from servers Layered System: clients do not recognize intermediate servers or end servers Code on Demand: servers can alter/customize the client s functionality, for example, by executing some compiled components (Java Applets, JavaScript) at the clients Uniform Interface: Identification (Representations) of Resources: such as URI in web-based REST systems (HTTP) Manipulation of Resources thru These Representations (by clients under permission approved) Self-Descriptive Messages: enough info is contained in each message Hypermedia as the Engine of State: the client accesses related sources Key Goals: Scalability of component interactions Generality of interfaces Independent deployment of components Intermediary components to reduce latency, enforce security and encapsulates legacy systems 9

20 CoAP Client / Server Model CoAP Server Request/Response CoAP Client CoAP Server Request/Response CoAP Intermediary Request/Response CoAP Client HTTP Server Request/Response Intermediary (CoAP-HTTP Mapping) Request/Response CoAP Client CoAP Server Request/Response Intermediary (HTTP-CoAP Mapping) Request/Response HTTP Client 20

21 CoAP Protocol Stack & Message Model CoAP Requests/Responses Messages UDP (Port# 5683 for Resource Discovery and Access Port# : 6LoWPAN) Request: confirmable and non-confirmable (GET/PUT/POST/DELETE) Response: piggybacked, separate, non-confirmable 4 Types: Confirmable (CON), Non-Confirmable (NON), Acknowledgement (ACK), Reset (RST) Each message has a Message ID ; Each request message has an addition Token for response-request matching purpose Reliable Msg Delivery (Timer-based Re-transmission) Unreliable Msg Delivery Piggybacked Response Response for NON-type Request Separate Response 2

22 Current Focuses on communications (i.e. how information is transmitted from one machine to another) InterDigital s Evolution into IoT Evolution Future IoT Cube A global network infrastructure, linking physical and virtual objects through the exploitation of data processing and communication capabilities Connectivity Content Effectively integrate connectivity and content with context, collaboration, cloud, and cognition Context Collabaration Cloud Cognition Cloud Cognition Content Context Collaboration A world-wide network of interconnected objects that enables object identification, semantic data processing, and service discovery via C 6 Connectivity Connectivity: provide connection for mobile and constrained objects Content: massive data produced from things Cloud: cloud service and cloud content storage Context: context-aware design to improve performance Collaboration: cooperative comm., inter-things, service sharing Cognition: mine knowledge from massive data and provide autonomous system adjustment for improvements 22

23 Evolution to IoT Architecture 23

24 Thank You! With an eye on the future, InterDigital invites fellow global market participants in the ecosystem to collaborate on integrating our advanced technologies into products and services for field testing and commercial deployment. 24