Skip to content

MindSphere Remote Services: Getting Connected

Within this chapter we define device-specific Protocol Applications needed for Remote Login. We also outline, how to assign predefined Protocol Applications for Remote Login to devices located in primary Device Networks and how to launch such Remote Login as outlined in below process sketch:

Onboard Device in Primary Device Network

Note: The setup and configuration of this documentation's reference tenant, its users, Sites and Devices can be found in chapter Sample setup used in documentation.

Note: The product structure and the protocol routing capabilities of the individual optional capability packages are described in chapter Product structure and procurement.


Example: Create Protocol Application for Remote Login via VNC

Administrators create Protocol Applications and add these templates to a tenant-wide catalogue . Other users may then pull pre-defined Protocol Applications from this catalogue and assign one or many of them to a target device located in a Device Network. In MRS V2 select the blue box icon in the top left corner to open the Protocol Application menu with the Protocol Hub.

Admin creates Protocol App for VNC

The MRS Protocol Hub allows for creation and assignment of Protocol Applications. All Protocol Applications are tagged according to the functional MRS upgrade they might belong to. Select the VNC template.

Admin creates Protocol App for VNC

We assign the new Protocol Application with the name VNC login Europe and use a default port, which is meant for connecting to European devices via VNC-based remote login. Press "Save".

Admin creates Protocol App for VNC

Afterwards, the new Protocol Application is listed in the catalogue of pre-defined Protocol Applications. It may be assigned to Devices in a subsequent step.

Admin creates Protocol App for VNC


Example: Download Service Endpoint onto PC in Service Network

MRS provides a Service Endpoint for download. It must be installed on the "Access Device" (e.g. a PC) located in a Service Network. That enables encrypted protocol routing between the "Access Device" and MRS hosted on MindSphere, so that MRS can forward such encrypted traffic to Device Networks. For instance, if a technician named User Europe wants to perform remote service or maintenance on a Device located in another network, then he or she has to install such a Service Endpoint on their PC.

Download of Service Endpoint (formerly known as Operator Client) is done via the rightmost tile in MRS UI V1.

User downloads Service Endpoint

In a next step please specify the target Operating System on which the Endpoint shall be deployed.

User downloads Service Endpoint

Download of Service Endpoints is subject to export control and regulation (ECC). Please read and accept the related terms & conditions before the download of the related ZIP archive will proceed.

User downloads Service Endpoint

After download please expand the ZIP containing the Service Endpoint. Then the related files become visible in the underlying system's Operating System. The Service Endpoint's executable is called "mrs-client".

User downloads Service Endpoint


Example: Download Device Endpoint onto Device in Device Network

MRS provides a Device Endpoint for download. It must be installed by administrative users on a device in the primary network of a remote Device Network. That enables encrypted protocol routing between that device and MRS hosted on MindSphere, so that MRS can forward such encrypted traffic further to Service Networks.

Note: configuration of Device Endpoints as gateways into secondary Device Networks is outlined in section Advanced connections.

This download functionality is available both in MRS UI V1 and V2. This example uses V2 and starts with selecting the Operating System of the target device.

Admin downloads Device Endpoint

Download of will only proceed, if the export control (ECC) related terms & conditions are accepted.

Admin downloads Device Endpoint

Afterwards, the download can be executed. Please un-ZIP the archive so that the Device Endpoint becomes visible in the device's Operating System.

Admin downloads Device Endpoint


Example: Assign Protocol Application for VNC to a device

Connecting to a Device in a Service Network demands specification of the IP-based protocol that shall be used for doing so. In this example we assume that a user with site admin rights and named Owner Munich pulls a VNC Protocol Application from the catalogue of administrator-defined Protocol Applications and then assigns it to an already registered target Device named IPC m01.

In the beginning, the Device does not have any Protocol Application associated with it. Please use the button "Assign Protocol Application" for doing so.

Owner assigns VNC to IPC

Next the catalogue of available Protocol Applications will be displayed. Use the blue button next to VNC login Europe to assign this protocol to the device.

Owner assigns VNC to IPC

Now the Device was assigned with the VNC protocol.

Owner assigns VNC to IPC

The VNC login Europe is now listed in the Device properties. It may be connected via the blue "chain" button next to it.

Owner assigns VNC to IPC


Example: Launch Service Endpoint and establish VNC to a device

Now a remote maintenance expert named User Europe and thus having the MRS role of Remote User wants to connect from his/her PC (which must already run a Service Endpoint) to device IPC m01 using the previously assigned Protocol Application registered as VNC login Europe.

In the beginning, the connection is available and marked in orange. Select the blue "chain" button to trigger launching an end-2-end connection between the MRS endpoints in the Service Network and a Device Network respectively.

User launches VNC connection to IPC

Please provide the connection details regarding the remote host.

User launches VNC connection to IPC

The VNC server on the target device will prompt you for credentials.

User launches VNC connection to IPC

Once these are provided the VNC remote screen pops up.

User launches VNC connection to IPC



Any questions left?

Ask the community


Except where otherwise noted, content on this site is licensed under the MindSphere Development License Agreement.


Last update: July 29, 2022