Data processing system, computer-implemented method, computer program product, and storage medium for controlling multiple types of mobile platforms

Abstract

The invention relates to a data processing system (1) for controlling different types of mobile platforms. The data processing system comprises an abstraction component (3, 5), a standardization component (6) and a driver management unit (7). The abstraction component is designed to connect to one or more mobile platforms, to determine the type of the mobile platform, to indicate the type to the driver management unit and to use drivers provided by the driver management unit in order to convert messages between an interface to the standardization component and an interface to the mobile platform and / or to manipulate functions of the mobile platform and the standardization component. In this case, the interface of the abstraction component to the mobile platform has an interface to a software component of the mobile platform.

Description

Technical Field

[0001] The present invention relates to a data processing system for controlling multiple types of mobile platforms, wherein the data processing system has an abstraction component, a standardized component and a driver management unit. The present invention also relates to a computer-implemented method, a computer program product and a computer-readable storage medium. Background Art

[0002] Mobile platforms are used today in a variety of forms. They can be, for example, mobile robots or vehicles. The present invention particularly relates to semi-autonomous and / or fully autonomous mobile platforms. Unlike autonomous mobile platforms, semi-autonomous mobile platforms require more or less input from a user or a central control unit to perform their tasks.

[0003] Currently, in order to control a mobile platform, suitable software and / or control technology is required, which is usually delivered together with the mobile platform by the manufacturer of the mobile platform. This necessity arises from the fact that mobile platforms are not subject to any cross-manufacturer standardization. Summary of the Invention

[0004] Because the software and / or control technology used for mobile platforms is not standardized, there are many disadvantages. In particular, users must be trained in the software and / or control technology. Furthermore, the software and / or control technology must be maintained individually.

[0005] Furthermore, software and / or control technology must be installed and operated, which sometimes requires different operating systems and / or servers, leading to increased personnel and / or work expenditure.

[0006] Mobile platforms such as robots mostly use localization technology designed to identify their surroundings and, for safety reasons, humans. However, robots often face problems identifying other robots, which can have very different sizes, shapes, and structures. Errors in identifying other robots can lead to collisions or deadlocks.

[0007] Robots can be used in a variety of applications. For example, they can transport goods. Furthermore, they can be used to identify and report situations, such as the arrival of goods and / or people. Programming robots for these applications has traditionally required control software specific to the robot type. Consequently, applications where multiple robots coordinate tasks have been impossible or difficult to implement.

[0008] The task of the application includes achieving a simpler, in particular uniform, control of mobile platforms. The task of the application also includes remote control of mobile platforms, in particular of different types of mobile platforms, in a coordinated manner by means of a central control system. Thereby, the following applications can be implemented: in which different robots jointly act to complete a task. In particular, the mobile platforms should be supported in implementing their tasks by information about their place of residence (Aufenthaltsort), the properties of the working environment and the position of other mobile platforms.

[0009] A first aspect of the application relates to a data processing system for controlling a plurality of types of mobile platforms. The data processing system comprises an abstraction component, a standardization component and a driver management unit. The abstraction component is configured to connect to a first mobile platform, to determine a first type of the first mobile platform and to communicate with the driver management unit in order to indicate the first type of the first mobile platform to the driver management unit. The driver management unit is configured to provide a first driver to the abstraction component depending on the indicated first type. The abstraction component has a first interface to the first mobile platform and a second interface to the standardization component and is configured to translate messages between the first interface and the second interface using the first driver provided by the driver management unit, to manipulate functions of the first mobile platform via the first interface and / or to manipulate functions of the standardization component via the second interface. Here, the first interface of the abstraction component has an interface to a software component of the first mobile platform.

[0010] The data processing system can have a central data processing device and a first mobile data processing device. The first mobile data processing device can be permanently connected to the first mobile platform. In particular, the first interface can connect the first mobile platform to the first mobile data processing device and the first mobile data processing device can be connected to the central data processing device by means of a wireless message system.

[0011] The abstraction component, the standardization component and the driver management unit are preferably software components. However, it is also possible that the abstraction component, the standardization component and / or the driver management unit are implemented completely or partially by means of dedicated hardware components.

[0012] The first mobile data processing device can be a separate data processing device, or it can be integrated into the data processing device of the first mobile platform. The first mobile data processing device preferably includes a processor, such as a microprocessor, a microcontroller, or an application-specific processor. Furthermore, the first mobile data processing device preferably includes one or more memory units. In particular, the first mobile data processing device includes a non-volatile memory unit. The first mobile data processing device can have a number of other components, such as a communication unit, via which the first mobile data processing device can communicate with the central data processing device.

[0013] The central data processing device preferably also includes a processor, such as a microprocessor, a microcontroller, or an application-specific processor. Furthermore, the central data processing device preferably includes one or more memory units. In particular, the central data processing device includes a non-volatile memory unit. The central data processing device may have a number of other components, such as a communication unit, via which the central data processing device can communicate with the first mobile data processing device.

[0014] In particular, the abstraction component may include a central abstraction element and a first mobile abstraction element. The central data processing device may include the central abstraction element, a driver management unit, and a standardized component. Furthermore, the first mobile data processing device may include the first mobile abstraction element. In particular, the central abstraction element, the driver management unit, and the standardized component are software components implemented by the central data processing device. Furthermore, the first mobile abstraction element may be implemented as a software component by the first mobile data processing device.

[0015] Different data processing structures are possible. For example, the abstraction component, the standardization component and / or the driver management unit can be implemented completely or partially on the first mobile platform.

[0016] The first mobile platform can be, for example, a robot or a vehicle such as a car. The first mobile platform is in particular a semi-autonomous or fully autonomous mobile platform.

[0017] The abstraction component may also be implemented to communicate with a driver management unit in order to ensure compatibility of the mobile platform with the data processing system and to prevent unwanted connections to incompatible mobile platforms.

[0018] The driver management unit may be configured to store drivers for a plurality of mobile platforms. Preferably, the driver management unit is configured to store the drivers in a cryptographically signed form. Alternatively, the drivers may be stored on another data processing device, and the driver management unit may access the other data processing device to provide the first driver according to the indicated first type to the abstraction component.

[0019] Here, the driver implementation is used to: convert messages between the mobile platform and the standardized component, operate the functions of the mobile platform and / or operate the functions of the standardized component. Preferably, the first driver provided by the driver management unit is implemented by the first mobile data processing device as part of the first mobile abstraction element. Thirdly, it is also possible that the first driver provided by the driver management unit is implemented by the central data processing device as part of the central abstraction element. It is also possible that the first driver provided by the driver management unit has a first mobile driver component and a first central driver component, wherein the first mobile driver component is implemented by the first mobile data processing device as part of the first mobile abstraction element, and wherein the first central driver component is implemented by the central data processing device as part of the central abstraction element.

[0020] The driver for the mobile platform is preferably written in a stream-based programming language suitable for dynamic, state-based communication with the mobile robot. For example, the driver for the mobile platform can be written in a programming language oriented to the Robot Operating System (ROS) standard. However, the user of the present invention is largely free to choose the programming language and implement the interface for the driver.

[0021] The first driver can be based on software (aufsetzen), which is provided by the manufacturer for controlling the first mobile platform. Therefore, the driver managed by the driver management unit can be created without detailed knowledge of the hardware of different types of mobile platforms.

[0022] In particular, the data processing system can implement functions for controlling a steering system, a drive system and / or a braking system of the first mobile platform.

[0023] According to one embodiment, the abstraction component is configured to connect to another mobile platform, determine the type of the other mobile platform, and indicate the type of the other mobile platform to the driver management unit. Furthermore, the driver management unit is configured to provide the abstraction component with another driver based on the indicated type of the other mobile platform. The abstraction component has another interface to the other mobile platform and is configured to, using the other driver provided by the driver management unit, convert messages between the second interface and another interface to the other mobile platform, control functions of the other mobile platform via the other interface, and / or control functions of the standardized component via the second interface.

[0024] The data processing system can therefore have other mobile data processing devices connected to other mobile platforms. In particular, other interfaces can connect other mobile platforms to other mobile data processing devices, and other mobile data processing devices can be connected to the central data processing device via a wireless messaging system.

[0025] The other mobile data processing device may be a separate data processing device, or may be integrated into a data processing device of another mobile platform. The other mobile data processing device includes, in particular, a processor, a storage unit, and a communication unit.

[0026] In particular, the abstraction component can have further mobile abstraction elements, wherein the further mobile data processing devices each include a further mobile abstraction element. The further mobile abstraction elements can in particular be implemented as software components by the further mobile data processing devices.

[0027] Different data processing structures are possible. For example, the abstraction component, the standardization component and / or the driver management unit can be implemented in a decentralized manner on multiple mobile platforms.

[0028] According to another embodiment, the standardized component is implemented to provide a control of the first mobile platform that is dependent on a position of the first mobile platform, positions of other mobile platforms connected to the abstraction component, and / or properties of the surroundings of the first mobile platform.

[0029] In particular, the standardized component can be implemented to: send a message to the first mobile platform via the abstraction component or control the functions of the first mobile platform via the abstraction component so as to control the first mobile platform based on the position of the first mobile platform, the positions of other mobile platforms and / or the characteristics of the surrounding environment of the first mobile platform.

[0030] It is also possible that the standardized component sends a message to the first mobile platform via the abstraction component in order to inform the first mobile platform of the position of the first mobile platform, the positions of other mobile platforms and / or properties of the surrounding environment, so that the first mobile platform can plan its actions and in particular movements based on this information.

[0031] According to another embodiment, the data processing system includes a central control component, wherein the standardized component is configured to provide the central control component with functions and / or messages for controlling the mobile platform via a third interface. In this case, several of the functions and / or messages provided by the standardized component for controlling the mobile platform are independent of the type of mobile platform being controlled.

[0032] The central control assembly can be part of a central data processing device. However, it is also possible that the central control assembly is part of a data processing device separate from the central data processing device.

[0033] For example, in the case of a battery charging station, the robot can transmit a first indicator for the current output voltage of the robot's battery. Optionally, the robot can also transmit a second indicator for the maximum output voltage of the battery. The standardized component can be implemented to calculate the percentage state of charge from the first indicator and (optionally) the second indicator.

[0034] In another example, the robot may be implemented to perform calculations using quaternions to determine the robot's rotation within the map. In this case, the normalization component may be implemented to convert these parameters into vectors.

[0035] In yet another example, the robot may be implemented to perform calculations in an English coordinate system using feet and / or yards, and the normalization component may be implemented to convert these parameters to metric units.

[0036] In yet another example, the standardization component may be implemented to transform complex, partially repetitive, and condition-dependent instructions into a sequence of simple instructions such as “go to” and / or “perform action”.

[0037] According to another embodiment, the standardization component is designed to receive messages from the abstraction component via the second interface, aggregate the received messages taking into account context information, and forward the aggregated messages to the central control component via the third interface.

[0038] For example, a robot may be implemented to send its current position as a single position parameter in the x, y, and z directions.

[0039] Thus, the standardized component can be configured to receive three messages with three time stamps. Furthermore, the standardized component can be configured to synchronize the three messages with respect to a fourth time stamp that is different and as close as possible to the three messages. Furthermore, the standardized component can be configured to subsequently send a message to the central control component, the message containing the position parameters for the three spatial directions and the fourth time stamp.

[0040] In another example involving position updates with task information, a robot may be implemented to support only simple "go to" commands. In this case, a standardized component may be implemented to determine the arrival of a "waypoint" or "intermediate task target" from position updates, robot speed, and / or other parameters and report this to the central control component.

[0041] According to another embodiment, the standardized component and the central control component are designed to exchange messages via a first network protocol, wherein the first network protocol is a message-oriented network protocol that enables targeted and open communication according to the queue principle.

[0042] Unlike user-oriented network protocols, in message-oriented network protocols, messages are not necessarily identified by the addresses of the participating mobile platforms. In message-oriented protocols, the destination or reason for sending a message is not necessarily determined. Instead, the mobile platform can decide for itself whether and how to react to the message.

[0043] Message-oriented network protocols enable not only targeted communication with one or more mobile platforms, but also the sending of broadcast messages (open communication).

[0044] The wait queue principle implies, inter alia, buffering of messages and processing of messages in the order in which they were inserted into the wait queue.

[0045] For example, standardized components and central control components can be implemented to exchange messages via Advanced Message Queuing Protocol (AMQP), ZeroMQ Message Transport Protocol (ZMTP), Extensible Messaging and Presence Protocol (XMPP), Java Message Service (JMS), WebSockets, Streaming Text Oriented Messaging Protocol (STOMP), or OpenWire.

[0046] According to another embodiment, the central abstraction element and the first mobility abstraction element are designed to exchange messages using a second network protocol, wherein the second network protocol is a message-oriented network protocol that enables targeted and open communication according to the queue principle.

[0047] Therefore, the first mobility abstraction element can be configured to provide a standardized interface to the central abstraction element based on the second network protocol. In particular, the first mobility abstraction element can be configured to send messages regarding the first mobile platform to the central abstraction element and / or receive these messages from the central abstraction element. Furthermore, the first mobility abstraction element can be configured to send and receive information for establishing, disconnecting, and securing a connection with the central abstraction element.

[0048] Similarly, the central abstraction element can be implemented to provide a standardized interface to the first mobility abstraction element based on the second network protocol. In addition, the central abstraction element can be implemented to send and receive information for establishing, disconnecting and ensuring a connection with the first mobility abstraction element.

[0049] The second network protocol may be, for example, Message Queuing Telemetry Transport (MQTT) protocol, ZMTP, XMPP, JMS, WebSockets, STOMP, OpenWire, or AMQP.

[0050] A second aspect of the present invention relates to a computer-implemented method. In this regard, the method comprises: establishing a connection to a first mobile platform via an abstraction component, wherein the abstraction component has a first interface to the first mobile platform and a second interface to a standardized component. The abstraction component determines a first type of the first mobile platform and sends a first indicator of the first type of the first mobile platform to a driver management unit. The driver management unit provides a first driver for the abstraction component based on the first indicator. The abstraction component uses the first driver provided by the driver management unit to convert messages between the first interface and the second interface, manipulate functions of the first mobile platform via the first interface, and / or manipulate functions of the standardized component via the second interface. In this regard, the first interface of the abstraction component has an interface to a software component of the first mobile platform.

[0051] According to another embodiment, the method according to the present invention further comprises: establishing a connection with other mobile platforms via an abstraction component, wherein the abstraction component has other interfaces to the other mobile platforms. The abstraction component determines the type of the other mobile platform and transmits other indicators of the type of the other mobile platform to the driver management unit. The driver management unit provides other drivers to the abstraction component based on the other indicators. The abstraction component uses other drivers provided by the driver management unit to convert messages between the second interface and other interfaces to the other mobile platforms, to manipulate functions of the other mobile platforms via the other interfaces and / or to manipulate functions of the standardized components via the second interface. Here, the other interfaces of the abstraction component to the other mobile platforms may have interfaces to software components of the other mobile platforms.

[0052] Furthermore, a third aspect of the present invention relates to a computer program product, wherein the computer program product comprises an abstraction component, a standardization component and a driver management unit.

[0053] A fourth aspect of the present invention relates to a computer-readable storage medium having stored thereon a computer program product according to the present invention.

[0054] A further explanation is presented in more detail below together with a description of preferred exemplary embodiments of the invention based on the drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] The accompanying drawings show:

[0056] Figure 1 An exemplary data processing system for controlling different types of mobile platforms is shown;

[0057] Figure 2 Exemplary methods for controlling different types of mobile platforms are shown. DETAILED DESCRIPTION

[0058] Figure 1 FIG. 1 shows a data processing system 1 for controlling a plurality of types of mobile platforms. Figure 1 In the embodiment of the present invention, a robot is shown as an example as a mobile platform. However, the present invention can also be applied to other mobile platforms, in particular vehicles, such as cars or trucks.

[0059] The data processing system 1 includes abstraction components 3 and 5, a standardization component 6, and a driver management unit 7. The abstraction components 3 and 5 are configured to connect to the first mobile platform 2, determine the first type of the first mobile platform 2, and communicate with the driver management unit 7 to indicate the first type of the first mobile platform to the driver management unit. The driver management unit 7 is configured to provide a first driver to the abstraction components 3 and 5 based on the indicated first type. The abstraction components 3 and 5 have a first interface to the first mobile platform 2 and a second interface to the standardization component 6, and are configured to convert messages between the first interface and the second interface, control functions of the first mobile platform via the first interface, and / or control functions of the standardization component via the second interface, using the first driver provided by the driver management unit 7. The first interface of the abstraction components 3 and 5 has an interface to a software component of the first mobile platform. For example, the software component can be software provided by the manufacturer of the first mobile platform.

[0060] The abstraction component includes a first mobile abstraction element 3 and a central abstraction element 5. Furthermore, the data processing system 1 may include a central data processing device and a first mobile data processing device. Here, the central data processing device includes the central abstraction element 5, a driver management unit 7, and a standardized component 6. Furthermore, the first mobile data processing device includes the first mobile abstraction element 3. The central abstraction element 5, the driver management unit 7, and the standardized component 6 may be software components implemented by the central data processing device. Furthermore, the first mobile abstraction element 3 may be a software component implemented by the first mobile data processing device.

[0061] The first mobile data processing device can be fixedly connected to the first mobile platform 2. In particular, the first interface can connect the first mobile platform 2 to the first mobile data processing device, and the first mobile data processing device can be connected to the central data processing device via a messaging system 4, in particular a wireless messaging system.

[0062] Therefore, the first mobile abstraction element 3 and the central abstraction element 5 are designed to communicate with each other via a message system 4. For this purpose, a message-oriented network protocol is preferably used, which enables targeted and open communication based on the queue principle. For example, the first mobile abstraction element 3 and the central abstraction element 5 can be designed to exchange messages using the MQTT protocol.

[0063] The abstraction components 3 , 5 can also be designed to communicate with the driver management unit 7 in order to ensure the compatibility of the mobile platform with the data processing system 1 and to prevent unwanted connections to incompatible mobile platforms.

[0064] The abstraction components 3 and 5 can be implemented to connect to other mobile platforms to determine the type of the other mobile platforms and indicate the type of the other mobile platforms to the driver management unit 7. In addition, the driver management unit 7 can be implemented to provide other drivers for the abstraction components 3 and 5 according to the indicated type of the other mobile platforms, so that the abstraction components can convert messages between the second interface and other interfaces to the other mobile platforms and can manipulate the functions of the other mobile platforms and the functions of the standardized components when using other drivers provided by the driver management unit. Here, the communication between the abstraction component and the driver management unit can be carried out through the standardized component. In particular, the abstraction component can be implemented to indicate the type of the other mobile platform to the standardized component, and the standardized component can be implemented to send indicators of the other mobile platforms to the driver management unit. In addition, the driver management unit can be implemented to send other drivers to the abstraction component through the standardized component.

[0065] Standardization component 6 is preferably designed to provide central control component 9 with control of first mobile platform 2 that is dependent on the position of the first mobile platform, the positions of other mobile platforms connected to abstraction components 3 , 5 and / or properties of the surroundings of the first mobile platform.

[0066] The data processing system 1 further comprises a central control component 9, wherein the standardized component 6 is configured to provide the central control component with functions and / or messages for controlling the mobile platforms via a third interface 8. In this case, some or all of the functions and / or messages provided by the standardized component for controlling the mobile platforms are independent of the type of mobile platform being controlled.

[0067] The standardization component 6 can also be designed to receive messages from the abstraction component via the second interface, aggregate the received messages taking into account context information, and forward the aggregated messages to the central control component 9 via the third interface 8 .

[0068] Here, the standardized component 6 and the central control component 9 can be implemented to exchange messages via a message-oriented network protocol that enables targeted and open communication based on the queue principle. For example, AMQP can be used for communication between the standardized component 6 and the central control component 9.

[0069] The signal flow is shown by 10 .

[0070] The data processing system 1 can implement, in particular, a steering system, a drive system and / or a braking system for controlling the first mobile platform 2 .

[0071] The central control component, for example, enables applications in which multiple robots of different types work together in a coordinated manner. This allows for more efficient and reliable use of the robots. To implement such applications, employees only need to learn how to program the central control component. This makes it possible, or at least significantly simplifies, to implement applications involving multiple robots of different types. Furthermore, in applications involving multiple subtasks, the central control component can select and use the most suitable robot for each subtask.

[0072] Figure 2 A computer-implemented method 100 for controlling multiple types of mobile platforms is illustrated.

[0073] In step S1 , the abstraction component establishes a connection to the first mobile platform, so that the abstraction component has a first interface to the first mobile platform in addition to a second interface to the standardized component.

[0074] In step S2 , the abstraction component determines a first type of the first mobile platform.

[0075] In step S3 , the abstraction component sends a first indicator of a first type of the first mobile platform to the driver management unit.

[0076] In step S4 , the driver management unit provides a first driver for the abstraction component according to the first indicator.

[0077] In step S5, the abstraction component uses a first driver provided by the driver management unit to convert messages between the first interface and the second interface, to control functions of the first mobile platform via the first interface, and / or to control functions of the standardized component via the second interface. The first interface of the abstraction component may include an interface to a software component of the first mobile platform, i.e., the abstraction component is based on software of the first mobile platform, which is provided, for example, by the manufacturer of the first mobile platform.

[0078] Method 100 may further include: establishing a connection to another mobile platform via the abstraction component. Furthermore, the abstraction component may determine the type of the other mobile platform and transmit an indicator of the type of the other mobile platform to the driver management unit. The driver management unit may provide another driver for the abstraction component based on the other indicator. The abstraction component may use the other driver provided by the driver management unit to convert messages between the second interface and another interface to the other mobile platform, to control functions of the other mobile platform via the other interface, and / or to control functions of the standardized component via the second interface.

Claims

1. A data processing system (1) for controlling multiple types of mobile platforms, the data processing system comprising an abstraction component (3, 5), a standardization component (6) and a driver management unit (7), in, The abstraction component is implemented to: connect with a first mobile platform (2), determine a first type of the first mobile platform, and communicate with the driver management unit to indicate the first type of the first mobile platform to the driver management unit; The driver management unit is implemented to: provide a first driver to the abstract component according to the indicated first type; The abstraction component has a first interface to the first mobile platform and a second interface to the standardized component; wherein the abstraction component is implemented to: convert messages between the first interface and the second interface, control functions of the first mobile platform via the first interface, and / or control functions of the standardized component via the second interface, using a first driver provided by the driver management unit; The first interface of the abstraction component has an interface to the software component of the first mobile platform.

2. The data processing system (1) according to claim 1, in, The abstraction component (3, 5) is implemented to: connect with other mobile platforms, determine the type of the other mobile platforms, and indicate the type of the other mobile platforms to the driver management unit (7); The driver management unit is implemented to: provide other drivers for the abstract component according to the indicated type of the other mobile platform; Wherein, the abstract component has other interfaces to the other mobile platforms; The abstraction component is implemented to: convert messages between the second interface and other interfaces to the other mobile platforms using other drivers provided by the driver management unit, control functions of the other mobile platforms via the other interfaces and / or control functions of the standardized component (6) via the second interface.

3. The data processing system (1) according to claim 1 or 2, in, The standardized component (6) is implemented to provide control of the first mobile platform (2), the control being dependent on the position of the first mobile platform, the positions of other mobile platforms connected to the abstraction component (3, 5) and / or characteristics of the surrounding environment of the first mobile platform.

4. The data processing system (1) according to claim 1 or 2, further comprising a central control component (9), in, The standardized component (6) is implemented to: provide the central control component with functions and / or messages for controlling the mobile platform via a third interface; Therein, a plurality of functions and / or messages provided by the standardized component for controlling a mobile platform are independent of the type of the controlled mobile platform.

5. The data processing system (1) according to claim 4, in, The standardization component (6) is designed to receive messages from the abstraction component (3, 5) via the second interface, aggregate the received messages while taking into account context information, and forward the aggregated messages to the central control component (9) via the third interface.

6. The data processing system (1) according to claim 4, in, The standardization component (6) and the central control component (9) are designed to: exchange messages via a first network protocol, The first network protocol is a message-oriented network protocol, which can realize targeted communication and open communication based on the waiting queue principle.

7. The data processing system (1) according to claim 1 or 2, in, The data processing system has a central data processing device and a first mobile data processing device; wherein the first interface connects the first mobile platform to the first mobile data processing device; The first mobile data processing device is connected to the central data processing device via a wireless communication system (4).

8. The data processing system (1) according to claim 7, in, The abstraction component has a central abstraction element (5) and a first mobile abstraction element (3); wherein the central data processing device comprises the central abstraction element (5), the driver management unit (7) and the standardized component (6); The first mobile data processing device includes the first mobile abstraction element (3).

9. The data processing system (1) according to claim 8, in, The central abstraction element (5) and the first mobile abstraction element (3) are designed to exchange messages using a second network protocol. The second network protocol is a message-oriented network protocol, which can realize targeted communication and open communication based on the waiting queue principle.

10. A computer-implemented method (100), comprising: Establishing (S1) a connection to a first mobile platform (2) via an abstraction component (3, 5), wherein the abstraction component has a first interface to the first mobile platform and a second interface to a standardized component (6); determining (S2) a first type of the first mobile platform by the abstraction component; sending (S3) a first indicator of a first type of the first mobile platform from the abstraction component to a driver management unit (7); providing (S4) a first driver for the abstraction component through the driver management unit according to the first indicator; Using (S5) a first driver provided by the driver management unit via the abstraction component in order to convert messages between the first interface and the second interface, to control functions of the first mobile platform via the first interface, and / or to control functions of the standardized component via the second interface; The first interface of the abstraction component has an interface to the software component of the first mobile platform.

11. The computer-implemented method (100) of claim 10, further comprising: Establishing a connection with other mobile platforms through the abstraction component (3, 5), wherein the abstraction component has other interfaces to the other mobile platforms; Determining the type of the other mobile platform through the abstraction component; transmitting a further indicator of the type of the further mobile platform from the abstraction component to the driver management unit (7); According to the other indicators, providing other drivers for the abstract component through the driver management unit; Other drivers provided by the driver management unit are used by the abstraction component to convert messages between the second interface and other interfaces to the other mobile platforms, to control functions of the other mobile platforms via the other interfaces and / or to control functions of the standardized component (6) via the second interface.

12. A computer program product comprising an abstraction component (3, 5), a standardization component (6) and a driver management unit (7), wherein: The abstraction component, the standardization component and the driver management unit are implemented according to the data processing system (1) according to any one of claims 1 to 9.

13. A computer-readable storage medium having stored thereon the computer program product according to claim 12.

Images