TC-IOT M2M CORE Services Protocol. User Manual. Version: 1.0 Date:
|
|
- Osborne Patterson
- 6 years ago
- Views:
Transcription
1 TC-IOT M2M CORE Services Protocol User Manual Version: 1.0 Date:
2 Document Name: TC-IOT M2M CORE Services Protocol - User Manual Version: 1.0 Date: Document ID: TC_IOT_M2M_CORE_Protocol_User_Manual_EN_v1.0 Content 1. Introduction What is the TC-IoT CORE? M2M CORE Services Protocol messages Methods Query - Searching for events Extra References of 14
3 1. Introduction This document provides an overview description of the M2M CORE Services Protocol, used in the Router component (TC-IoT CORE) of TC M2M Cloud Platform (TC-IoT) developed by Thought Creator. The objective of the document is to describe and illustrate the way to use the Protocol. For clarification, some terms used throughout the document are described in the following table. Term Description Client Router Gateway (Adapter) Terminal Subscription Feed User or Application receiving and sending information from/to the Terminal. Corresponds to the TC-IoT CORE component responsible for the queuing, distribution and archiving of events received from M2M Terminals. Software component responsible for the conversion of specific M2M communication protocols to the common and standard protocol used by the Router and by Clients. Electronic M2M Device able to interconnect with other equipments and/or sensors, and to communicate with the Gateway. Corresponds to the Registration of a Terminal in the system. Subscription made by a Client of the Terminal activates the automatic reception, in realtime, of all event issued by the said Terminal. Asynchronous Message originated from a Terminal sent to all Client who have Subscribed it. These messages correspond to state changes of Terminals or of their interconnected sensors. 3 of 14
4 2. What is the TC-IoT CORE? TC-IoT CORE is the main component of TC M2M Cloud Platform (TC-IoT), and is responsible for the distribution and storage of events from the M2M terminals. TC-IoT CORE is high-performance a message routing system, i.e., a Message Broker for all the traffic between Devices/Gateways and applications (Clients), controlling the authentication, authorization and access to Terminals, as well as replicating and storing messages of the subscribed Terminals. It can be considered a hybrid between a traditional router for distributing messages among resources, and a Resource Directory, a repository for registration and for querying information about those resources and their historical events. From a service perspective the TC-IoT CORE functions as a Web server, accessible from Web browsers and applications communicating via the HTTP protocol [1]. The TC-IoT CORE, i.e., the Router, interconnects the Clients (M2M applications), which consume information and request actions on Terminals, to the Gateways, which consist of applications (Adapters) that perform the translation of low-level device-specific M2M protocols, to the standard M2M CORE Services Protocol. Network Domain Gateway Domain Device Domain App App App App App M2M Application Services M2M CORE Services Protocol M2M Device Specific Messages GW Adapter M2M Device Access Networks GW Adapter M2M Device Resource Directory Application Layer API Layer IoT CORE Layer (Cloud) IP, 2G/GRPS, 3G/HSPA Agent Layer The M2M CORE Services Protocol is a resource-oriented and event-based communication protocol, over HTTP using a standard RESTful [2] design, or over WebSocket [3] transport, for real-time bi-directional communication of Terminal information. The protocol encodes requests and responses (messages exchanged between Gateway, Router and Client) using JSON [4,5], a textbased format of simple interpretation, widely supported by several programming languages and databases. This design makes it possible for the M2M CORE Services Protocol to be deployed at scale, by leveraging existing HTTP implementations and infrastructures. 3. M2M CORE Services Protocol messages The M2M CORE Services Protocol defines three distinct types of messages: information messages, terminal messages and control messages. The control messages are associated with quick response commands, such as subscriptions and registrations. The terminal messages are typically used for action commands or information requests between Client and Terminal and to query information about Terminals in the Resource Directory. 4 of 14
5 Control Messages A control message is used to inform the Client of the outcome of a particular operation, and consist of a JSON object with fields status and message. The message field indicates the result of the operation or the error that occurred, using an alphanumeric string format. The status field indicates if the operation was successful or not and typically takes one of the two values, 1 or -1. The status with a value of 1 indicates that the operation was successful. In case the value is -1, it means it was unable to execute the operation, as the following example: "message": "status": "NO_PERMISSION", - 1 Terminal Messages A terminal message can contain one or more JSON objects. There is no limitation on the content of these messages, only that they must contain the src, dst and timestamp fields. "src": " ", "dst": " ", "timestamp": The src field, for a message sent by a Client to a Terminal, must contain the username of the Client (the user with permissions to access the Terminal). For a message sent by a Terminal the src field must contain the identifier of the Terminal. The field dst defines the destination address of a message. In the case of a feed from a Terminal both fields src and dst have equal values corresponding to the identifier of the Terminal. The values of src and dst fileds are of alphanumeric string format. The timestamp field contains the creation date of the message represented in POSIX Epoch (Unix Timestamp), with an integer number format. Information Messages An information message is used to return Terminal identifiers known by the CORE. The responses have the format of JSON vector. 5 of 14
6 4. Methods Several methods (servlets) to interact with the TC-IoT CORE (Router component) are available. These methods allow the reception of messages, managing subscriptions, reading / changing states, etc. All requests should be made using the HTTP protocol. Optionally, for receiving and sending messages in real-time from / to the subscribed terminals, WebSockets [3] or HTTP Long Polling can be used. All requests require basic HTTP authentication using the credentials supplied by Thought Creator. The generality of the methods available in the Router function in a request-response perspective. The reception of messages related to information from subscribed Terminals, is sent to the Client whenever possible in real-time. If the Client is not online, those messages are temporarily stored in the TC-IoT platform and delivered a posteriori. Storage of messages for long periods are not guaranteed. It is advisable that Applications (Clients) are always connected to the TC-IoT Platform or to cancel subscriptions whenever these are no longer necessary. The next table describes the Methods and Resources supported by the Router, the format/syntax to be used and the entities can use them. Although available, it is not advisable to use the methods marked with (**) because they have lower performance and higher overhead in communications. Resource URI - Method - Message - request and/or Entity Description /index HTTP GET CONTROL MESSAGE All Returns the available information on the TC- IoT Platform. /subscribe_terminal/<id> HTTP GET CONTROL MESSAGE Client Subscribes the Terminal with the specified ID. Returns a control message with the result of the operation and, in case of error, the error code. /unsubscribe_terminal/ <ID> HTTP GET CONTROL MESSAGE Client Removes the subscription from Terminal with the specified ID. Returns a control message with the result of the operation and, in case of error, the error code. (**) /read_messages HTTP GET TERMINAL MESSAGE All Gets the oldest message stored in TC-IoT. If there are no saved messages, the HTTP session remains open for 30 seconds waiting for new messages. When the session expires a control message with timeout (Code 408) is received. 6 of 14
7 Resource URI - Method - Message - request and/or Entity Description (**) /message/<id> HTTP POST CONTROL MESSAGE request All Sends the message in the body of the POST request to the Client or Terminal with the specified ID. Returns a control message with the result of the operation. The ID parameter in the request is optional since the content of the message must contain the identifier of the recipient. /get_allowed HTTP GET INFORMATION MESSAGE [Vector of IDs] Client Returns the list of Terminals to which the Client can access, in a JSON vector format. /get_subscriptions HTTP GET INFORMATION MESSAGE [Vector of IDs] Client Returns the list of Terminals that the Client has subscribed, in a JSON vector format. /query HTTP POST TERMINAL MESSAGES request [Vector of messages] All Questions the TC-IoT through a query for information about a given set of terminals. (See example in Section 5) /messages WEBSOCKET Flow of TERMINAL MESSAGES All Bidirectional channel for sending messages between CORE and Client / Gateway. In direction Router -> Client, corresponds to messages from Terminals that Client has subscribed. In direction Client -> Terminal, corresponds to messages the Client wants to send to the Terminals. With this method, only terminal messages are allowed. (See section 3) /register_terminal/<id> HTTP POST CONTROL MESSAGE request Gateway This method allows to register a Terminal in the CORE. The POST body must contain the message for registering the Terminal. This method returns a control message. /unregister_terminal/<id> HTTP GET CONTROL MESSAGE Gateway This method allows removing the registration of a Terminal in the CORE. This method returns a control message. 7 of 14
8 Responses in Control Messages The following table describes the answers contained in the message field and the corresponding values of the status field for commands where the response is a control message: Message Status Description NO_PERMISSION -1 Message sent when there are no permissions to perform certain operations, such as subscribing to a Terminal not allowed. NOT_FOUND -1 Terminal not found. This message is received, for example, when a Terminal or a Client do not exist in the system. OK 1 When the operation was performed successfully and the message was sent. SUBSCRIBED, UNSUBSCRIBED, ALREADY SUBSCRIBED REGISTERED UNREGISTERED 1 When the operation was performed successfully for subscribing or unsubscribing Terminals. 1 When the operation was performed successfully for registration of Terminals. (Only for the account Gateway) BROADCAST_SENT 1 Feed message sent (Only for the account Gateway) MESSAGE_SENT 1 Message sent successfully to Client or Terminal. MESSAGE_ERROR -1 Error situation where it is not possible to send messages to a Terminal or to a Client. TIMEOUT_READING_MESSAGES 1 Message received on command /read_messages if there are no new messages at an interval of 30 seconds. Responses in Vector In the case of information messages, the responses return a JSON vector with the list of identifiers of Terminals, as shown in the following example: [123, 124, 1235] For terminal messages requests by HTTP POST, as is the case of /query command, the response returns a JSON vector with terminal messages. 8 of 14
9 HTTP Responses In parallel with the content of the control message it is possible from the HTTP response codes to get some information about the success of the operation, as shown in the following table. HTTP Responses Status Code and Reason Description 200 OK The action was successfully received, understood, and accepted. 403 Forbidden The request contains cannot be fulfilled. Typically, no permission to access the resource or no permission to access the Terminal. 404 Not Found Resource not available. 401 Authorization Required Authentication failure. 500 Internal Server Error This message may appear when the operation cannot be completed from the CORE side. 408 Request Timeout Timeout in /read_messages request. The response body is a control message where the field message has the value "TIMEOUT_READING_MESSAGES". 5. Query - Searching for events One of the features of the M2M Core Services Protocol is that all messages that are not control messages are stored persistently in the TC-IoT platform making possible at any time to query for them through the command /query. This section indicates the generic syntax used to query the fields and parameters contained in the messages stored in the TC-IoT platform, since the content of these messages differs depending on the type and model of the Terminal. The details of the fields and parameters of each Terminal model are described in relevant documents available on Thought Creator website. All searches are done using the servlet /query and are sent to the TC-IoT platform using an HTTP POST method, which content (request body) is a query in JSON format. In response, the TC-IoT platform returns a vector (array) of all messages matching the search performed. Response times differ depending on the complexity of the query and the amount of data involved. An example of a request /query is as follows: POST /query HTTP/1.1 Host: example.com Accept: application/json Content- Type: application/json Content- Length: 96 "src": "123456", "analog.value": $lt: 5 9 of 14
10 The example of the response to the request /query is as follows (returned an empty vector): HTTP/ OK Content- Type: application/json Content- Length: 2 [] Response in Vector The TC-IoT always returns the set of messages that match the criteria presented. An example of response, which returns the search criterion relating to two analog ports of a Terminal, is the following: [ ], "analog": "port": 3, "value": , "src": " ", "dst": " ", "timestamp": "analog": "port": 3, "value": , "src": " ", "dst": " ", "timestamp": Non-specific Query Search requests on TC-IoT should be valid JSON objects containing all the conditions that must be present in the responses. Search requests in which the query is an empty JSON object (nonspecific), will return in response all the messages in the database: 10 of 14
11 Query conditions and filters Responses to a query can be filtered by both the "identifier" of the Terminal as any other set of identifying data fields. To search for messages that contain one or more criteria, they should be indicated in the content of the query. An example with only one search criterion, in which all messages are returned from the Terminal , is as follows: "src": "123456" In another example, two fields are combined to limit the search. Such is the case of a search for messages containing analogue port 3 of Terminal , where only the messages with information on that port are filtered: "src": "123456", "analog.port": 3 If it were omitted the src field all messages containing analog port 3, regardless of the Terminal in question were obtained. Some general conditions for search of messages are the following: $lt e $gt The conditions $gt (greater than), $lt (less than), allow to filter messages that contain an filed whose value is greater than or less than a certain numerical value. In the following example it is intended to retrieve all messages from Terminal with analog port values less than 5: "src": "123456", "analog.value": $lt: 5 11 of 14
12 Similarly for values greater than 9.94: "src": "123456", "analog.value": $gt: 9.94 $or The condition $or allows to make a search on messages satisfying at least one of the conditions imposed. In the following example the query combines the two filters exemplified above: "src": " ", $or: [ "analog.value": $gt: 9.94, "analog.value": $lt: 5 ] $ne The condition $ne (not-equal) allows searching for fields that do not have a certain value. "timestamp": $ne: 0 $exists The condition $exists allows to search for messages containing a given field. As an example, to obtain all messages containing the GPIO field, the query would be the following: "gpio": $exists: true 12 of 14
13 6. Extra In this chapter some additional information and suggestions for implementation are presented. Subscriptions For applications that are not constantly online it is advisable to unsubscribe the Terminals before the applications are placed offline. This prevents the accumulation of messages in TC-IoT platform while the applications are not connected. Receiving messages in real-time The reception of messages in real-time can be done through WebSockets or HTTP Long Polling. It is recommended preferably the WebSocket mechanism, in which case the Client just needs to keep one HTTP WebSocket session with TC-IoT platform. In case of using HTTP Long Polling it is necessary to pay attention to timeout.s It is advisable to always send a new request for each message successfully received. WebSockets The communication via WebSockets should respect the recommendations of RFC 6455 [3]. WebSockets support bidirectional, full-duplex communications over persistent connections. A WebSocket connection is established over a standard HTTP connection which is then upgraded without impacting the original connection, working with existing networking infrastructures including firewalls and proxies. To establish a WebSocket connection, the client side sends a WebSocket handshake request, for which the server side returns a WebSocket handshake response, as in the following example: GET /websock/proto/msg HTTP/1.1 Connection: Upgrade Upgrade: websocket Sec- WebSocket- Protocol: chat, better- chat Sec- WebSocket- Key: 50cLrugr7h3yAbe5Kpc52Q== Sec- WebSocket- Version: 13 Origin: HTTP/ Switching Protocols Connection: Upgrade Upgrade: WebSocket Sec- WebSocket- Accept: 58ij/Yod1NTjzqcyjkZbZk6V6v0= Sec- WebSocket- Protocol: chat Once the connection is established, the client and server can send WebSocket text frames back and forth in full-duplex mode. To keep the communications channel alive, it is necessary to send regular messages to indicate the channel is still being used. The PING/PONG WebSockets messages are designed to send non-application level traffic that will prevent the channel from being prematurely closed. A PING message may be sent by either side and is replied with a PONG message. The messages implemented in TC-IoT are in text format. 13 of 14
14 7. References [1] R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, and T. Berners-Lee, Hypertext Transfer Protocol HTTP/1.1, RFC 2616, Internet Engineering Task Force, Jun Updated by RFC [2] R. T. Fielding, REST: Architectural Styles and the Design of Network-based Software Architectures. Doctoral dissertation, University of California, Irvine, [3] I. Fette and A. Melnikov, The WebSocket Protocol, RFC 6455, Internet Engineering Task Force, Dec [4] D. Crockford, The application/json Media Type for JavaScript Object Notation (JSON), RFC 4627, Internet Engineering Task Force, Jul Updated by RFC 7158, [5] T. Bray (Ed.), The JavaScript Object Notation (JSON) Data Interchange Format, RFC 7159, Internet Engineering Task Force, Mar of 14
MediaAUTH Draft Proposal
MediaAUTH Draft Proposal August 21, 2012 Contents 1 Introduction 2 2 Service & User Perspective 2 2.1 Login...................................... 2 2.2 Soft Login.................................... 3
More informationInternet Engineering Task Force (IETF) Request for Comments: ISSN: November 2013
Internet Engineering Task Force (IETF) N. Borenstein Request for Comments: 7072 Mimecast Category: Standards Track M. Kucherawy ISSN: 2070-1721 November 2013 Abstract A Reputation Query Protocol This document
More informationAdvanced Message Queuing Protocol (AMQP) WebSocket Binding (WSB) Version 1.0
Advanced Message Queuing Protocol (AMQP) WebSocket Binding (WSB) Version 1.0 Working Draft 05 2 April 2014 Technical Committee: OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings (AMQP-
More informationInformation About SIP Compliance with RFC 3261
APPENDIX A Information About SIP Compliance with RFC 3261 This appendix describes how the Cisco SIP IP phone complies with the IETF definition of SIP as described in RFC 3261. It has compliance information
More informationAdvanced Message Queuing Protocol (AMQP) WebSocket Binding (WSB) Version 1.0
Advanced Message Queuing Protocol (AMQP) WebSocket Binding (WSB) Version 1.0 Working Draft 08 7 March 2016 Technical Committee: OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings (AMQP-
More informationHow to Configure a Remote Management Tunnel for Barracuda NG Firewalls
How to Configure a Remote Management Tunnel for Barracuda NG Firewalls If the managed NG Firewall can not directly reach the NG Control Center it must connect via a remote management tunnel. The remote
More informationSIP Compliance APPENDIX
APPENDIX E This appendix describes Cisco SIP proxy server (Cisco SPS) compliance with the Internet Engineering Task Force (IETF) definition of Session Initiation Protocol (SIP) as described in the following
More informationAsyncOS 11.0 API - Getting Started Guide for Security Appliances
AsyncOS 11.0 API - Getting Started Guide for Email Security Appliances First Published: 2017-12-27 Last Modified: -- Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706
More informationJabber, Inc. August 20, 2004
Network Working Group Internet-Draft Expires: February 18, 2005 P. Saint-Andre Jabber Software Foundation J. Hildebrand Jabber, Inc. August 20, 2004 Transporting Atom Notifications over the Extensible
More informationCCNA Exploration Network Fundamentals. Chapter 03 Application Functionality and Protocols
CCNA Exploration Network Fundamentals Chapter 03 Application Functionality and Protocols Updated: 27/04/2008 1 3.1 Applications: The Interface Between Human and Networks Applications provide the means
More informationIntroduction to Cisco TV CDS Software APIs
CHAPTER 1 Cisco TV Content Delivery System (CDS) software provides two sets of application program interfaces (APIs): Monitoring Real Time Streaming Protocol (RTSP) Stream Diagnostics The Monitoring APIs
More informationLesson 1 Key-Terms Meanings: Web Connectivity of Devices and Devices Network
Lesson 1 Key-Terms Meanings: Web Connectivity of Devices and Devices Network 1 Application Application: A software (S/W) for an application, such as, creating and sending an SMS, measuring and sending
More informationEnabling Full-Duplex Communications in APEX
Enabling Full-Duplex Communications in APEX Me Curt Workman - workmancw@ldschurch.org Education University of Utah Work Micron Electronics Evans&Sutherland The Church of Jesus Christ of Latter-Day Saints
More informationReal-time video chat XPage application using websocket and WebRTC technologies AD-1077
Real-time video chat XPage application using websocket and WebRTC technologies AD-1077 Dr Csaba Kiss 02/03/2016 LA-UR-16-20047 Credentials Over 25 years experience in molecular biology Began Xpage application
More informationexpires in six months October 1997 Internet Public Key Infrastructure Operational Protocols: FTP and HTTP <draft-ietf-pkix-opp-ftp-http-01.
HTTP/1.1 200 OK Date: Tue, 09 Apr 2002 06:26:48 GMT Server: Apache/1.3.20 (Unix) Last-Modified: Tue, 21 Oct 1997 17:15:00 GMT ETag: "361b18-2953-344ce314" Accept-Ranges: bytes Content-Length: 10579 Connection:
More informationApplication Protocols and HTTP
Application Protocols and HTTP 14-740: Fundamentals of Computer Networks Bill Nace Material from Computer Networking: A Top Down Approach, 6 th edition. J.F. Kurose and K.W. Ross Administrivia Lab #0 due
More informationEverest: A Cloud Platform for Computational Web Services
Everest: A Cloud Platform for Computational Web Services Oleg Sukhoroslov 1, Alexander Afanasiev 1 1 Institute for Information Transmission Problems, Russian Academy of Sciences, Bolshoy Karetny per. 19,
More informationvrealize Log Insight Developer Resources
vrealize Log Insight Developer Resources vrealize Log Insight 4.3 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new
More informationInterdomain Federation Guide for IM and Presence Service on Cisco Unified Communications Manager, Release 11.5(1)SU2
Interdomain Federation Guide for IM and Presence Service on Cisco Unified Communications Manager, Release 11.5(1)SU2 First Published: 2017-11-29 Last Modified: 2017-12-01 Americas Headquarters Cisco Systems,
More informationObsoletes: 2070, 1980, 1942, 1867, 1866 Category: Informational June 2000
Network Working Group Request for Comments: 2854 Obsoletes: 2070, 1980, 1942, 1867, 1866 Category: Informational D. Connolly World Wide Web Consortium (W3C) L. Masinter AT&T June 2000 The text/html Media
More informationvrealize Log Insight Developer Resources Update 1 Modified on 03 SEP 2017 vrealize Log Insight 4.0
vrealize Log Insight Developer Resources Update 1 Modified on 03 SEP 2017 vrealize Log Insight 4.0 You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/
More informationReST 2000 Roy Fielding W3C
Outline What is ReST? Constraints in ReST REST Architecture Components Features of ReST applications Example of requests in REST & SOAP Complex REST request REST Server response Real REST examples REST
More informationInterdomain Federation for the IM and Presence Service, Release 10.x
First Published: 2014-01-29 Last Modified: 2018-11-05 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387)
More informationClient-Server Protocol Transport Bindings
Client-Server Protocol Transport Bindings V1.1 WV Internal Tracking Number: WV-024 Notice Copyright 2001-2002 Ericsson, Motorola and Nokia. All Rights Reserved. Implementation of all or part of any Specification
More informationLibelium Cloud Hive. Technical Guide
Libelium Cloud Hive Technical Guide Index Document version: v7.0-12/2018 Libelium Comunicaciones Distribuidas S.L. INDEX 1. General and information... 4 1.1. Introduction...4 1.1.1. Overview...4 1.2. Data
More informationRequest for Comments: 5437 Category: Standards Track Isode Limited January 2009
Network Working Group Request for Comments: 5437 Category: Standards Track P. Saint-Andre Cisco A. Melnikov Isode Limited January 2009 Status of This Memo Sieve Notification Mechanism: Extensible Messaging
More informationChapter 10 Web-based Information Systems
Prof. Dr.-Ing. Stefan Deßloch AG Heterogene Informationssysteme Geb. 36, Raum 329 Tel. 0631/205 3275 dessloch@informatik.uni-kl.de Chapter 10 Web-based Information Systems Role of the WWW for IS Initial
More informationHOW PERSISTENT CHAT SERVER WORKS
HOW PERSISTENT CHAT SERVER WORKS LYNC SERVER 2013 Lync Server 2013, Persistent Chat Server enables you to participate in multiparty, topic-based conversations that persist over time. Persistent Chat Server
More informationHypertext Transport Protocol
Hypertext Transport Protocol HTTP Hypertext Transport Protocol Language of the Web protocol used for communication between web browsers and web servers TCP port 80 HTTP - URLs URL Uniform Resource Locator
More informationHow to Configure a Remote Management Tunnel for an F-Series Firewall
How to Configure a Remote Management Tunnel for an F-Series Firewall If the managed NextGen Firewall F-Series cannot directly reach the NextGen Control Center, it must connect via a remote management tunnel.
More informationForeScout Extended Module for VMware AirWatch MDM
ForeScout Extended Module for VMware AirWatch MDM Version 1.7.2 Table of Contents About the AirWatch MDM Integration... 4 Additional AirWatch Documentation... 4 About this Module... 4 How it Works... 5
More informationSentinet for BizTalk Server SENTINET
Sentinet for BizTalk Server SENTINET Sentinet for BizTalk Server 1 Contents Introduction... 2 Sentinet Benefits... 3 SOA and API Repository... 4 Security... 4 Mediation and Virtualization... 5 Authentication
More informationHTTP 1.1 Web Server and Client
The feature provides a consistent interface for users and applications by implementing support for HTTP 1.1 in Cisco IOS XE software-based devices. When combined with the HTTPS feature, the feature provides
More informationConfiguring Virtual Servers
3 CHAPTER This section provides an overview of server load balancing and procedures for configuring virtual servers for load balancing on an ACE appliance. Note When you use the ACE CLI to configure named
More informationPassBy[ME] API Documentation
PassBy[ME] API Documentation Document id: PBM_01 Document Version: 1.1.12 Author: Microsec Ltd. Date: 2015.09.13. API Version 1 1 Table of contents 1 Introduction... 4 2 Terms... 5 3 PassBy[ME] message
More informationCompliance with RFC 3261
APPENDIX A Compliance with RFC 3261 This appendix describes how the Cisco Unified IP Phone 7960G and 7940G complies with the IETF definition of SIP as described in RFC 3261. It contains compliance information
More informationThe search being performed may take a significant time so a forking proxy must send a 100 Trying response.
SIP Response Codes Article Number: 178 Rating: Unrated Last Updated: Wed, Nov 15, 2017 at 2:31 PM SIP Response Codes 1xx Provisional Responses 100 Trying Extended The search being performed may take a
More informationStorageGRID Webscale NAS Bridge Management API Guide
StorageGRID Webscale NAS Bridge 2.0.3 Management API Guide January 2018 215-12414_B0 doccomments@netapp.com Table of Contents 3 Contents Understanding the NAS Bridge management API... 4 RESTful web services
More informationWorking with Cisco MediaSense APIs
MediaSense API Conventions, page 1 Job States, page 8 Precedence Rules for paramconnector and fieldconnector, page 9 Encoding, page 9 Special Characters in Text Strings, page 9 Request and Response Parameter
More informationPrivileged Identity App Launcher and Session Recording
Privileged Identity App Launcher and Session Recording 2018 Bomgar Corporation. All rights reserved worldwide. BOMGAR and the BOMGAR logo are trademarks of Bomgar Corporation; other trademarks shown are
More informationBarracuda Firewall Release Notes 6.5.x
Please Read Before Upgrading Before installing the new firmware version, back up your configuration and read all of the release notes that apply to the versions that are more current than the version that
More informationInterdomain Federation for IM and Presence Service on Cisco Unified Communications Manager, Release 10.5(1)
Interdomain Federation for IM and Presence Service on Cisco Unified Communications Manager, Release 10.5(1) First Published: 2014-01-29 Last Modified: 2017-12-01 Americas Headquarters Cisco Systems, Inc.
More informationSession 8. Reading and Reference. en.wikipedia.org/wiki/list_of_http_headers. en.wikipedia.org/wiki/http_status_codes
Session 8 Deployment Descriptor 1 Reading Reading and Reference en.wikipedia.org/wiki/http Reference http headers en.wikipedia.org/wiki/list_of_http_headers http status codes en.wikipedia.org/wiki/_status_codes
More informationIntended status: Informational. B. Wyman October 2, 2007
Network Working Group Internet-Draft Intended status: Informational Expires: April 4, 2008 P. Saint-Andre XMPP Standards Foundation J. Hildebrand Jabber, Inc. B. Wyman October 2, 2007 Transporting Atom
More informationsmap a Simple Measurement and Actuation Profile for Physical Information
smap a Simple Measurement and Actuation Profile for Physical Information S.Dawson-Haggerty, X.Jiang, G.Tolle, J.Ortiz, D.Culler Computer Science Division, University of California, Berkeley Presentation
More informationFeatures of a proxy server: - Nowadays, by using TCP/IP within local area networks, the relaying role that the proxy
Que: -Proxy server Introduction: Proxy simply means acting on someone other s behalf. A Proxy acts on behalf of the client or user to provide access to a network service, and it shields each side from
More informationcellip CELLIPS SMS INTERFACE DESCRIPTION HTTP GET INNEHÅLLSFÖRTECKNING
INNEHÅLLSFÖRTECKNING Innehållsförteckning... 1 1 Introduction... 2 1.1 Scope... 2 2 HTTP Get interface... 2 2.1 Mobile Terminated Messages... 2 2.1.1 Usage... 2 2.1.2 Parameters... 2 2.1.3 Codes... 4 2.1.4
More informationREST Web Services Objektumorientált szoftvertervezés Object-oriented software design
REST Web Services Objektumorientált szoftvertervezés Object-oriented software design Dr. Balázs Simon BME, IIT Outline HTTP REST REST principles Criticism of REST CRUD operations with REST RPC operations
More informationCopyright 2013, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 13
1 To Building WebSocket Apps in Java using JSR 356 Arun Gupta blogs.oracle.com/arungupta, @arungupta 2 The preceding is intended to outline our general product direction. It is intended for information
More informationAnalysis of the effects of removing redundant header information in persistent HTTP connections
Analysis of the effects of removing redundant header information in persistent HTTP connections Timothy Bower, Daniel Andresen, David Bacon Department of Computing and Information Sciences 234 Nichols
More informationIdentity Firewall. About the Identity Firewall
This chapter describes how to configure the ASA for the. About the, on page 1 Guidelines for the, on page 7 Prerequisites for the, on page 9 Configure the, on page 10 Monitoring the, on page 16 History
More informationSentinet for Microsoft Azure SENTINET
Sentinet for Microsoft Azure SENTINET Sentinet for Microsoft Azure 1 Contents Introduction... 2 Customer Benefits... 2 Deployment Topologies... 3 Cloud Deployment Model... 3 Hybrid Deployment Model...
More informationThe SAP Internet Programming Model, Part 1
The SAP Internet Programming Model, Part 1 Since the first SAP ITS-enabled R/3 release (R/3 3.1G), the number of standard Internet Applications Components (IACs) provided by SAP has constantly increased.
More information13. Internet Applications 최양희서울대학교컴퓨터공학부
13. Internet Applications 최양희서울대학교컴퓨터공학부 Internet Applications Telnet File Transfer (FTP) E-mail (SMTP) Web (HTTP) Internet Telephony (SIP/SDP) Presence Multimedia (Audio/Video Broadcasting, AoD/VoD) Network
More informationDell EMC Unisphere for PowerMax
Dell EMC Unisphere for PowerMax Version 9.0.0 REST API Concepts and Programmer's Guide REV 01 Copyright 2014-2018 Dell Inc. or its subsidiaries. All rights reserved. Published May, 2018 Dell believes the
More informationSession Initiation Protocol (SIP)
Session Initiation Protocol (SIP) Introduction A powerful alternative to H.323 More flexible, simpler Easier to implement Advanced features Better suited to the support of intelligent user devices A part
More informationRESTful Network API for Notification Channel
RESTful Network API for Notification Channel Candidate Version 1.0 17 Jan 2012 Open Mobile Alliance OMA-TS-REST_NetAPI_NotificationChannel-V1_0-20120117-C OMA-TS-REST_NetAPI_NotificationChannel-V1_0-20120117-C
More informationCache Operation. Version 31-Jul Wireless Application Protocol WAP-175-CacheOp a
Cache Operation Version 31-Jul-2001 Wireless Application Protocol WAP-175-CacheOp-20010731-a A list of errata and updates to this document is available from the WAP Forum Web site, http://www.wapforum.org/,
More informationHow to Route Internet Traffic between A Mobile Application and IoT Device?
Whitepaper How to Route Internet Traffic between A Mobile Application and IoT Device? Website: www.mobodexter.com www.paasmer.co 1 Table of Contents 1. Introduction 3 2. Approach: 1 Uses AWS IoT Setup
More informationConfiguration Manager
CHAPTER 7 This chapter describes how to perform routine Cisco VXC Manager configuration management tasks using the Administrator Console. It provides information on managing the configuration settings
More informationHands-On with IoT Standards & Protocols
DEVNET-3623 Hands-On with IoT Standards & Protocols Casey Bleeker, Developer Evangelist @geekbleek Cisco Spark How Questions? Use Cisco Spark to communicate with the speaker after the session 1. Find this
More informationSentinet for BizTalk Server VERSION 2.2
for BizTalk Server VERSION 2.2 for BizTalk Server 1 Contents Introduction... 2 SOA Repository... 2 Security... 3 Mediation and Virtualization... 3 Authentication and Authorization... 4 Monitoring, Recording
More informationIntroduction to RESTful Web Services. Presented by Steve Ives
1 Introduction to RESTful Web Services Presented by Steve Ives Introduction to RESTful Web Services What are web services? How are web services implemented? Why are web services used? Categories of web
More informationDepartment of Computer Science. Burapha University 6 SIP (I)
Burapha University ก Department of Computer Science 6 SIP (I) Functionalities of SIP Network elements that might be used in the SIP network Structure of Request and Response SIP messages Other important
More informationForeScout Extended Module for MaaS360
Version 1.8 Table of Contents About MaaS360 Integration... 4 Additional ForeScout MDM Documentation... 4 About this Module... 4 How it Works... 5 Continuous Query Refresh... 5 Offsite Device Management...
More informationMonitoring Agent for SAP Applications Fix pack 11. Reference IBM
Monitoring Agent for SAP Applications 7.1.1 Fix pack 11 Reference IBM Monitoring Agent for SAP Applications 7.1.1 Fix pack 11 Reference IBM Note Before using this information and the product it supports,
More informationRead the following information carefully, before you begin an upgrade.
Read the following information carefully, before you begin an upgrade. Review Supported Upgrade Paths, page 1 Review Time Taken for Upgrade, page 1 Review Available Cisco APIC-EM Ports, page 2 Securing
More informationHTTP 1.1 Web Server and Client
HTTP 1.1 Web Server and Client Finding Feature Information HTTP 1.1 Web Server and Client Last Updated: June 01, 2011 The HTTP 1.1 Web Server and Client feature provides a consistent interface for users
More informationCCNA Exploration1 Chapter 3: Application Layer Functionality and Protocols
CCNA Exploration1 Chapter 3: Application Layer Functionality and Protocols LOCAL CISCO ACADEMY ELSYS TU INSTRUCTOR: STELA STEFANOVA 1 Objectives Functions of the three upper OSI model layers, network services
More informationUsing ANM With Virtual Data Centers
APPENDIXB Date: 3/8/10 This appendix describes how to integrate ANM with VMware vcenter Server, which is a third-party product for creating and managing virtual data centers. Using VMware vsphere Client,
More informationForeScout Extended Module for ServiceNow
ForeScout Extended Module for ServiceNow Version 1.2 Table of Contents About ServiceNow Integration... 4 Use Cases... 4 Asset Identification... 4 Asset Inventory True-up... 5 Additional ServiceNow Documentation...
More informationForeScout Extended Module for ServiceNow
ForeScout Extended Module for ServiceNow Version 1.1.0 Table of Contents About this Integration... 4 Use Cases... 4 Asset Identification... 4 Asset Inventory True-up... 5 Additional ServiceNow Documentation...
More informationInternet Engineering Task Force (IETF) Request for Comments: 6572 Category: Standards Track
Internet Engineering Task Force (IETF) Request for Comments: 6572 Category: Standards Track ISSN: 2070-1721 F. Xia B. Sarikaya Huawei USA J. Korhonen, Ed. Nokia Siemens Networks S. Gundavelli Cisco D.
More informationSecurity Guide Zoom Video Communications Inc.
Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a softwaredefined conference room solution into one easy-to-use platform. Zoom offers the best video, audio, and wireless
More informationZero Latency HTTP The comet Technique
Zero Latency HTTP The comet Technique Filip Hanik SpringSource Inc Keystone, Colorado, 2008 Slide 1 Who am I bla bla fhanik@apache.org Tomcat Committer / ASF member Co-designed the Comet implementation
More informationThreatScape App for QRadar: Overview, Installation and Configuration
ThreatScape App for QRadar: Overview, Installation and Configuration December 16, 2015 App Description... 3 System Requirements... 3 ThreatScape App for QRadar Installation and Configuration... 3 Configuration...
More informationAlteryx Technical Overview
Alteryx Technical Overview v 1.5, March 2017 2017 Alteryx, Inc. v1.5, March 2017 Page 1 Contents System Overview... 3 Alteryx Designer... 3 Alteryx Engine... 3 Alteryx Service... 5 Alteryx Scheduler...
More informationOPC XML-DA Client Driver PTC Inc. All Rights Reserved.
2018 PTC Inc. All Rights Reserved. 2 Table of Contents 1 Table of Contents 2 4 Overview 4 Project Architecture 5 Setup 6 Channel Properties General 6 Channel Properties Write Optimizations 7 Channel Properties
More information[MS-ADFSOAL]: Active Directory Federation Services OAuth Authorization Code Lookup Protocol
[MS-ADFSOAL]: Active Directory Federation Services OAuth Authorization Code Lookup Protocol Intellectual Property Rights Notice for Open Specifications Documentation Technical Documentation. Microsoft
More informationStorageGRID Webscale 11.0 Tenant Administrator Guide
StorageGRID Webscale 11.0 Tenant Administrator Guide January 2018 215-12403_B0 doccomments@netapp.com Table of Contents 3 Contents Administering a StorageGRID Webscale tenant account... 5 Understanding
More informationKaazing Gateway: An Open Source
Kaazing Gateway: An Open Source HTML 5 Websocket Server Speaker Jonas Jacobi Co-Founder: Kaazing Co-Author: Pro JSF and Ajax, Apress Agenda Real-Time Web? Why Do I Care? Scalability and Performance Concerns
More informationSecurity Manager Policy Table Lookup from a MARS Event
CHAPTER 17 Security Manager Policy Table Lookup from a MARS Event This chapter describes how to configure and use Security Manager and MARS so as to enable bi-directional lookup between events recieved
More informationWeb, HTTP and Web Caching
Web, HTTP and Web Caching 1 HTTP overview HTTP: hypertext transfer protocol Web s application layer protocol client/ model client: browser that requests, receives, displays Web objects : Web sends objects
More informationEMC Isilon. Cisco UCS Director Support for EMC Isilon
Cisco UCS Director Support for, page 1 Adding an Account, page 2 Storage Pool Tiers, page 3 Storage Node Pools, page 4 SMB Shares, page 5 Creating an NFS Export, page 7 Quotas, page 9 Configuring a space
More informationOpen Cloud Computing Interface - HTTP Protocol
GFD-R-P.223 OCCI-WG Ralf Nyrén, Independent Andy Edmonds, ICCLab, ZHAW Thijs Metsch, Intel Boris Parák, CESNET Updated: September 19, 2016 Open Cloud Computing Interface - HTTP Protocol Status of this
More informationCOMPUTER NETWORKS AND COMMUNICATION PROTOCOLS. Web Access: HTTP Mehmet KORKMAZ
COMPUTER NETWORKS AND COMMUNICATION PROTOCOLS Web Access: HTTP 16501018 Mehmet KORKMAZ World Wide Web What is WWW? WWW = World Wide Web = Web!= Internet Internet is a global system of interconnected computer
More informationWatchGuard Cloud Release Notes
WatchGuard Cloud Release Notes Latest WatchGuard Cloud Update: 15 November 2018 Release Notes Revision Date 15 November 2018 Introduction WatchGuard Cloud allows you to see and manage all your products
More informationWorkspace ONE UEM Notification Service 2. VMware Workspace ONE UEM 1811
Workspace ONE UEM Email Notification Service 2 VMware Workspace ONE UEM 1811 You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ If you have comments
More informationOracle - Developing Applications for the Java EE 7 Platform Ed 1 (Training On Demand)
Oracle - Developing Applications for the Java EE 7 Platform Ed 1 (Training On Demand) Code: URL: D101074GC10 View Online The Developing Applications for the Java EE 7 Platform training teaches you how
More informationBuilding next-gen Web Apps with WebSocket. Copyright Kaazing Corporation. All rights reserved.
Building next-gen Web Apps with WebSocket Copyright 2011 - Kaazing Corporation. All rights reserved. Who am I? Graham Gear Solution Architect, with Kaazing, purveyors of HTML5 enabling tech Based in London,
More informationClient/Server Computing & Socket Programming
CPSC 852 Intering Client/Server Computing & Socket Programming Michele Weigle Department of Computer Science Clemson University mweigle@cs.clemson.edu http://www.cs.clemson.edu/~mweigle/courses/cpsc852
More informationFrequently Asked Questions About Performance Monitor
APPENDIXA Frequently Asked Questions About Performance Monitor The following topics answer common questions about Performance monitor and contain troubleshooting tips: Installation, page A-1 Importing,
More informationReal-Time SignalR. Overview
Real-Time SignalR Overview Real-time Web applications feature the ability to push server-side content to the connected clients as it happens, in real-time. For ASP.NET developers, ASP.NET SignalR is a
More informationAvaya Port Matrix: Avaya Proprietary Use pursuant to the terms of your signed agreement or Avaya policy.
Avaya Matrix: Release 3.0 Issue 2 April 2016 April 2016 Avaya Matrix: 3.0 1 ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED "AS IS". AVAYA INC. DISCLAIMS ALL WARRANTIES,
More informationInstalling and Configuring vcloud Connector
Installing and Configuring vcloud Connector vcloud Connector 2.6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new
More informationIoT Platform API Reference (Version 4_2.0)
IoT Platform API Reference (Version 4_2.0) Version No. Description Date Version 1.0 First version 2016/10/07 Version 1.1 Updates based on K5 launch on UK site 2016/11/01 Version 1.2
More informationComputer Networks. Wenzhong Li. Nanjing University
Computer Networks Wenzhong Li Nanjing University 1 Chapter 8. Internet Applications Internet Applications Overview Domain Name Service (DNS) Electronic Mail File Transfer Protocol (FTP) WWW and HTTP Content
More informationLINK Mobility SMS REST API MT and Delivery Reports Version 1.3; Last updated September 21, 2017
LINK Mobility SMS REST API MT and Delivery Reports Version 1.3; Last updated September 21, 2017 For help, contact support@linkmobility.com The most up-to-date version of this document is available at http://www.linkmobility.com/developers/
More informationWeb Engineering (CC 552)
Web Engineering (CC 552) Introduction Dr. Mohamed Magdy mohamedmagdy@gmail.com Room 405 (CCIT) Course Goals n A general understanding of the fundamentals of the Internet programming n Knowledge and experience
More informationAll Rights Reserved, Copyright FUJITSU LIMITED IoT Platform Service Portal Operating Manual (Version 5_0.0)
1 IoT Platform Service Portal Operating Manual (Version 5_0.0) Version No. Description Date Version 1.0 First version 2016/10/07 Version 1.1 Error corrections and supporting launch of
More information