Play your Steam games on your phone, tablet, TV, or other PC. With touch control schemes newly-optimized for hundreds of top titles, you can now access and play games from your PC while on the couch, or on the go. Many Steam games are already optimized for your devices. A handheld steam cleaner is a great option for small tasks both inside and outside of the home. The Bissell Steam Shot Deluxe Hard Surface Cleaner weighs about 3 pounds but has a generous 20-foot power cord, giving you plenty of reach to tackle messes in the bathroom or kitchen, or to banish wrinkles from clothing. Steam is the ultimate destination for playing, discussing, and creating games. Steam is the ultimate destination for playing, discussing, and creating games. Meet Steamboy: the portable Steam Machine. A teaser video posted to YouTube has shown off a few glimpses of a portable gaming device designed to play your Steam library on the go.
-->Azure IoT Hub device streams facilitate the creation of secure bi-directional TCP tunnels for a variety of cloud-to-device communication scenarios. A device stream is mediated by an IoT Hub streaming endpoint which acts as a proxy between your device and service endpoints. This setup, depicted in the diagram below, is especially useful when devices are behind a network firewall or reside inside of a private network. As such, IoT Hub device streams help address customers' need to reach IoT devices in a firewall-friendly manner and without the need to broadly opening up incoming or outgoing network firewall ports.
Using IoT Hub device streams, devices remain secure and will only need to open up outbound TCP connections to IoT hub's streaming endpoint over port 443. Once a stream is established, the service-side and device-side applications will each have programmatic access to a WebSocket client object to send and receive raw bytes to one another. The reliability and ordering guarantees provided by this tunnel is on par with TCP.
Benefits
IoT Hub device streams provide the following benefits:
Firewall-friendly secure connectivity: IoT devices can be reached from service endpoints without opening of inbound firewall port at the device or network perimeters (only outbound connectivity to IoT Hub is needed over port 443).
Authentication: Both device and service sides of the tunnel need to authenticate with IoT Hub using their corresponding credentials.
Encryption: By default, IoT Hub device streams use TLS-enabled connections. This ensures that the traffic is always encrypted regardless of whether the application uses encryption or not.
Simplicity of connectivity: In many cases, the use of device streams eliminates the need for complex setup of Virtual Private Networks to enable connectivity to IoT devices.
Compatibility with TCP/IP stack: IoT Hub device streams can accommodate TCP/IP application traffic. This means that a wide range of proprietary as well as standards-based protocols can leverage this feature.
Ease of use in private network setups: Service can communicate with a device by referencing its device ID, rather than device's IP address. This is useful in situations where a device is located inside a private network and has a private IP address, or its IP address is assigned dynamically and is unknown to the service side.
Device stream workflows
A device stream is initiated when the service requests to connect to a device by providing its device ID. This workflow particularly fits into a client/server communication model, including SSH and RDP, where a user intends to remotely connect to the SSH or RDP server running on the device using an SSH or RDP client program.
The device stream creation process involves a negotiation between the device, service, IoT hub's main and streaming endpoints. While IoT hub's main endpoint orchestrates the creation of a device stream, the streaming endpoint handles the traffic that flows between the service and device.
Device stream creation flow
Programmatic creation of a device stream using the SDK involves the following steps, which are also depicted in the figure below:
The device application registers a callback in advance to be notified of when a new device stream is initiated to the device. This step typically takes place when the device boots up and connects to IoT Hub.
The service-side program initiates a device stream when needed by providing the device ID (not the IP address).
IoT hub notifies the device-side program by invoking the callback registered in step 1. The device may accept or reject the stream initiation request. This logic can be specific to your application scenario. If the stream request is rejected by the device, IoT Hub informs the service accordingly; otherwise, the steps below follow.
The device creates a secure outbound TCP connection to the streaming endpoint over port 443 and upgrades the connection to a WebSocket. The URL of the streaming endpoint as well as the credentials to use to authenticate are both provided to the device by IoT Hub as part of the request sent in step 3.
The service is notified of the result of device accepting the stream and proceeds to create its own WebSocket client to the streaming endpoint. Similarly, it receives the streaming endpoint URL and authentication information from IoT Hub.
In the handshake process above:
The handshake process must complete within 60 seconds (step 2 through 5), otherwise the handshake would fail with a timeout and the service will be notified accordingly.
After the stream creation flow above completes, the streaming endpoint will act as a proxy and will transfer traffic between the service and the device over their respective WebSockets.
Device and service both need outbound connectivity to IoT Hub's main endpoint as well as the streaming endpoint over port 443. The URL of these endpoints is available on Overview tab on the IoT Hub's portal.
The reliability and ordering guarantees of an established stream is on par with TCP.
All connections to IoT Hub and streaming endpoint use TLS and are encrypted.
Termination flow
An established stream terminates when either of the TCP connections to the gateway are disconnected (by the service or device). This can take place voluntarily by closing the WebSocket on either the device or service programs, or involuntarily in case of a network connectivity timeout or process failure. Upon termination of either device or service's connection to the streaming endpoint, the other TCP connection will also be (forcefully) terminated and the service and device are responsible to re-create the stream, if needed.
Connectivity requirements
Both the device and the service sides of a device stream must be capable of establishing TLS-enabled connections to IoT Hub and its streaming endpoint. This requires outbound connectivity over port 443 to these endpoints. The hostname associated with these endpoints can be found on the Overview tab of IoT Hub, as shown in the figure below:
Alternatively, the endpoints information can be retrieved using Azure CLI under the hub's properties section, specifically, property.hostname and property.deviceStreams keys.
The output is a JSON object of all endpoints that your hub's device and service may need to connect to in order to establish a device stream.
Note
Ensure you have installed Azure CLI version 2.0.57 or newer. You can download the latest version from the Install Azure CLI page.
Allow outbound connectivity to the device streaming endpoints
As mentioned at the beginning of this article, your device creates an outbound connection to IoT Hub streaming endpoint during device streams initiation process. Your firewalls on the device or its network must allow outbound connectivity to the streaming gateway over port 443 (note that communication takes place over a WebSocket connection that is encrypted using TLS).
The hostname of device streaming endpoint can be found on the Azure IoT Hub portal under the Overview tab.
Alternatively, you can find this information using Azure CLI:
Note
Ensure you have installed Azure CLI version 2.0.57 or newer. You can download the latest version from the Install Azure CLI page.
Troubleshoot via Device Streams resource logs
You can set up Azure Monitor to collect the resource logs for device streams emitted by your IoT Hub. This can be very helpful in troubleshooting scenarios.
Follow the steps below to create a diagnostics setting to send device streams logs for your IoT Hub to Azure Monitor Logs:
In Azure portal, navigate to your IoT hub. On the left pane, under Monitoring, select Diagnostic settings. Then select Add diagnostic setting.
Provide a name for your diagnostics setting and select DeviceStreams from the list of logs. Then select Send to Log Analytics. You'll be guided to choose an existing Log Analytics workspace or create a new one.
After you create a diagnostic setting to send your device streams logs to a Log Analytics workspace, you can access the logs by selecting Logs under Monitoring on the left pane of your IoT hub in Azure portal. Device streams logs will appear in the
AzureDiagnosticstable and haveCategory=DeviceStreams. Be aware that it may take several minutes following an operation for logs to appear in the table.As shown below, the identity of the target device and the result of the operation is also available in the logs.
To learn more about using Azure Monitor with IoT Hub, see Monitor IoT Hub. For information about all of the resource logs, metrics, and tables available for IoT Hub, see Monitoring Azure IoT Hub data reference.
Regional availability
During public preview, IoT Hub device streams are available in the Central US, Central US EUAP, North Europe, and Southeast Asia regions. Please make sure you create your hub in one of these regions.
SDK availability
Two sides of each stream (on the device and service side) use the IoT Hub SDK to establish the tunnel. During public preview, customers can choose from the following SDK languages:
The C and C# SDK's support device streams on the device side.
The NodeJS and C# SDK support device streams on the service side.
IoT Hub device stream samples
There are two quickstart samples available on the IoT Hub page. These demonstrate the use of device streams by applications.
The echo sample demonstrates programmatic use of device streams (by calling the SDK API's directly).
The local proxy sample demonstrates the tunneling of off-the-shelf client/server application traffic (such as SSH, RDP, or web) through device streams.
These samples are covered in greater detail below.
Echo sample
The echo sample demonstrates programmatic use of device streams to send and receive bytes between service and device applications. Note that you can use service and device programs in different languages. For example, you can use the C device program with the C# service program.
Here are the echo samples:
Local proxy sample (for SSH or RDP)
The local proxy sample demonstrates a way to enable tunneling of an existing application's traffic that involves communication between a client and a server program. This set up works for client/server protocols like SSH and RDP, where the service-side acts as a client (running SSH or RDP client programs), and the device-side acts as the server (running SSH daemon or RDP server programs).
This section describes the use of device streams to enable the user to SSH to a device over device streams (the case for RDP or other client/server application are similar by using the protocol's corresponding port).
The setup leverages two local proxy programs shown in the figure below, namely device-local proxy and service-local proxy. The local proxy programs are responsible for performing the device stream initiation handshake with IoT Hub, and interacting with SSH client and SSH daemon using regular client/server sockets.
The user runs service-local proxy to initiate a device stream to the device.
The device-local proxy accepts the stream initiation request and the tunnel is established to IoT Hub's streaming endpoint (as discussed above).
The device-local proxy connects to the SSH daemon endpoint listening on port 22 on the device.
The service-local proxy listens on a designated port awaiting new SSH connections from the user (port 2222 used in the sample, but this can be configured to any other available port). The user points the SSH client to the service-local proxy port on localhost.
Notes
The above steps complete an end-to-end tunnel between the SSH client (on the right) to the SSH daemon (on the left). Part of this end-to-end connectivity involves sending traffic over a device stream to IoT Hub.
The arrows in the figure indicate the direction in which connections are established between endpoints. Specifically, note that there is no inbound connections going to the device (this is often blocked by a firewall).
The choice of using port 2222 on the service-local proxy is an arbitrary choice. The proxy can be configured to use any other available port.
The choice of port 22 is protocol-dependent and specific to SSH in this case. For the case of RDP, the port 3389 must be used. This can be configured in the provided sample programs.
Use the links below for instructions on how to run the local proxy programs in your language of choice. Similar to the echo sample, you can run device- and service-local proxy programs in different languages as they are fully interoperable.
Next steps
Use the links below to learn more about device streams.
Safety device of steam turbineInfo
- Publication number
- JPH02267303A JPH02267303AJP8675789AJP8675789AJPH02267303AJP H02267303 AJPH02267303 AJP H02267303AJP 8675789 AJP8675789 AJP 8675789AJP 8675789 AJP8675789 AJP 8675789AJP H02267303 AJPH02267303 AJP H02267303A
- Authority
- JP
- Japan
- Prior art keywords
- trip
- emergency
- Japanese (ja)
- Inventor
- Toshiba Corp
- Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
- Filing date
- Publication date
- CriticalToshiba Corp
- Criticalpatent/JPH02267303A/en
- Criticalpatent/JPH02267303A/en
- Critical
JP8675789AJPH02267303A (en) 1989-04-07 1989-04-07 Safety device of steam turbine Applications Claiming Priority (1)
New Device Steam Trade
Application Number Priority Date Filing Date Title JPH02267303AtrueJPH02267303A (en) 1990-11-01 ID=13895625
Family Applications (1)
Application Number Title Priority Date Filing Date JP (1) JPH02267303A (en) Cited By (3)
* Cited by examiner, † Cited by third party Publication number Priority date Publication date Assignee Title EP1522681A3 (en) * 2003-09-22 2006-10-04 Kabushiki Kaisha Toshiba Protection system for turbo machine and power generating equipment 1989 EP1522681A3 (en) * 2003-09-22 2006-10-04 Kabushiki Kaisha Toshiba Protection system for turbo machine and power generating equipment
US7322788B2 (en) 2003-09-22 2008-01-29 Kabushiki Kaisha Toshiba Protection system for turbo machine and power generating equipment JP4693360B2 (en) * 2004-04-22 2011-06-01 株式会社東芝 Turbomachine safety equipment and power generation equipment JPH0245615A (en) Control device for turbo charger JPS63140832A (en) Throttle valve controlling device of internal combustion engine JPH04302791A (en) Thermostat actuated by expanding wax capsule provided with safety device JPS6182055A (en) Backup device of electronic speed change control device JPH04303102A (en) Selector valve, and hydraulic oil safety and power system JPH0374671A (en) Control device for continuously variable transmission JPH0388917A (en) Exhaustion control device for engine with turbo-supercharger JPH0316861A (en) Brake oil pressure control device JPH03175509A (en) Valve system JPH02120166A (en) Stoppage retainer using hydraulic servo unit KR970033482A (en) Fault elimination device and method for strapping machine JPH01216124A (en) Clutch actuator system for automatic/semi-automatic mechanical transmission system JPS59119036A (en) Throttle valve control device for engine
