Cross-platform touch feedback method, system and device

Abstract

The invention relates to a cross-platform touch feedback method, system and device. The method comprises the following steps: receiving a touch event triggering request, and determining a triggering parameter corresponding to a touch event; determining a target operation platform of the equipment, and creating a corresponding target platform controller according to the target operation platform; a touch event to be executed is determined based on a preset vibration configuration file, the trigger parameter is sent to a target platform controller, and the target platform controller is used for converting the trigger parameter into an instruction matched with a native interface format of a target operation platform; based on the converted instruction, a native interface of the target operation platform is called, the converted instruction is transmitted into the native interface, and the native interface is used for triggering equipment to execute touch feedback.

Description

Technical Field

[0001] This application relates to the field of computer software technology, and in particular to a cross-platform haptic feedback method, system, and apparatus. Background Technology

[0002] In the field of mobile game and application development, user experience and immersion have become key indicators of product core competitiveness. Haptic feedback, as a technology that transmits tactile interaction responses to users through device vibration, can significantly enhance the realism of operation feedback and the fun of interaction.

[0003] Currently, the industry standard for implementing haptic feedback is to directly call the native application programming interfaces (APIs) provided by the operating systems of various mobile platforms within the game engine (such as Unity) to trigger the device's vibration function. However, the vibration APIs of different platforms differ fundamentally in their interface formats and the granularity of supported functions. Developers need to write different code for each platform and perform a lot of adaptation work. Furthermore, when multiple vibration events are triggered simultaneously or consecutively within a short period of time in a game, it can easily lead to a confusing haptic experience. Summary of the Invention

[0004] Therefore, it is necessary to provide a cross-platform haptic feedback method, system, or device to address the aforementioned technical problems.

[0005] In a first aspect, this application provides a cross-platform haptic feedback method, the method comprising:

[0006] Receive haptic event trigger requests and determine the trigger parameters corresponding to the haptic event;

[0007] Determine the target operating platform of the terminal device, and create a corresponding target platform controller based on the target operating platform;

[0008] Based on a preset vibration profile, the tactile event to be executed is determined, and the trigger parameters are sent to the target platform controller. The target platform controller converts the trigger parameters into instructions that are compatible with the native interface format of the target operating platform.

[0009] Based on the instruction, the native interface of the target operating platform is invoked, and the instruction is passed into the native interface. The native interface is used to trigger the terminal device to perform haptic feedback.

[0010] In one embodiment, determining the tactile event to be executed based on a preset vibration profile includes:

[0011] Retrieve the first-level strategy from the preset vibration configuration file;

[0012] Based on the first-level strategy, one or more haptic events to be executed are determined from among the multiple received haptic events.

[0013] In one embodiment, after determining the tactile event to be executed based on a preset vibration profile, the method further includes:

[0014] Determine the priority of the haptic events to be executed;

[0015] Haptic feedback is executed in order of priority based on the haptic events to be executed.

[0016] In one embodiment, after executing the haptic feedback in order of priority based on the haptic events to be executed, the method further includes:

[0017] If at least two haptic events with the same priority are detected, retrieve the secondary strategy from the preset vibration profile.

[0018] The execution order of haptic events with the same priority is determined based on the secondary strategy.

[0019] In one embodiment, the triggering parameters are stored in a preset vibration configuration file, and the target platform controller converts the triggering parameters into instructions adapted to the native interface format of the target operating platform, including:

[0020] Retrieve the standardized trigger parameters corresponding to the haptic events in the configuration file;

[0021] According to the preset mapping rules, the standardized trigger parameters are converted into the target format trigger parameters of the target running platform, so as to obtain the instructions adapted to the native interface format of the target running platform.

[0022] In one embodiment, receiving a haptic event trigger request and determining the trigger parameters corresponding to the haptic event includes:

[0023] Based on the type event identifier in the haptic event trigger request, the trigger parameters corresponding to the type event identifier are obtained, and the type event identifier corresponds to the haptic event in the preset vibration configuration file.

[0024] Secondly, this application also provides a cross-platform haptic feedback system, the system comprising:

[0025] The application layer provides a unified application interface and responds to user touch event triggering operations by initiating touch event triggering requests to the core scheduling layer through the unified application interface. The triggering request includes triggering parameters.

[0026] The core scheduling layer is used to determine the target operating platform of the terminal device, create a corresponding target platform controller according to the target operating platform, determine the tactile event to be executed based on the preset vibration configuration file, and send the trigger parameters to the target platform controller when it is determined that the tactile event will be executed.

[0027] A platform abstraction layer, which includes multiple platform controllers corresponding to different operating platforms, is used to convert trigger parameters into instructions adapted to the native interface format of the target operating platform through the target platform controller;

[0028] The native implementation layer is used to receive the instruction, call the native interface of the target running platform, and pass the instruction to the native interface. The native interface is used to trigger the terminal device to perform haptic feedback.

[0029] Thirdly, this disclosure also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement steps of a cross-platform haptic feedback method.

[0030] Fourthly, this disclosure also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, implements the steps of a cross-platform haptic feedback method.

[0031] Fifthly, this disclosure also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the steps of a cross-platform haptic feedback method.

[0032] The aforementioned cross-platform haptic feedback methods include at least the following beneficial effects:

[0033] The embodiments provided in this disclosure only require writing a single set of general configuration files, eliminating the need to adapt underlying native interfaces separately for iOS / Android / Mini Programs. When adding a new platform, only the controller corresponding to the currently running platform is dynamically instantiated, thus completely decoupling business logic from platform implementation and greatly reducing the workload of repeated development, adaptation, and maintenance.

[0034] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0035] To more clearly illustrate the technical solutions in the embodiments or conventional technologies of this disclosure, the accompanying drawings used in the description of the embodiments or conventional technologies will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0036] Figure 1 This is a schematic diagram of a cross-platform haptic feedback system in one embodiment;

[0037] Figure 2 This is a schematic diagram illustrating an application scenario of a cross-platform haptic feedback system in one embodiment;

[0038] Figure 3 This is a flowchart illustrating a cross-platform haptic feedback method in one embodiment;

[0039] Figure 4 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0040] To enable those skilled in the art to better understand the technical solutions of this disclosure, the technical solutions in the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings.

[0041] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this disclosure described herein can be implemented in orders other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims. The terms "comprising," "including," or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, product, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, product, or apparatus. Without further limitation, the presence of other identical or equivalent elements in a process, method, product, or apparatus that includes said elements is not excluded. For example, the use of terms such as "first," "second," etc., is to denote names and does not indicate any specific order.

[0042] This disclosure provides a cross-platform haptic feedback method that can be applied to, for example... Figure 1 The application environment shown. Figure 1This is a schematic diagram of a cross-platform haptic feedback system in one embodiment.

[0043] The application layer provides a unified application programming interface (API) for game business logic to call. This interface is unaware of the target platform. When the game business logic triggers a vibration request, it calls the unified API, passing in common trigger parameters. After receiving the request, the API does not perform any platform-specific processing and directly forwards the common trigger parameters to the core scheduling layer.

[0044] The core scheduling layer (VibrationManager) is used to identify the current runtime environment, which can include iOS, Android, WeChat Mini Programs, etc. Based on the identified platform, it dynamically instantiates the corresponding platform-specific controller, such as iOSController and AndroidController.

[0045] The platform abstraction layer (Controller) contains multiple platform-specific controller modules, which are used to convert and adapt unified trigger parameters into an instruction format that the target platform can understand, thus achieving isolation between business logic and the specific implementation of the platform.

[0046] The native implementation layer (Proxy) contains multiple platform-specific proxy modules for calling the native APIs of various operating systems or platforms, such as iOS Core Haptics and Android Vibrator.

[0047] In one embodiment of this disclosure, Figure 2 This is a schematic diagram of an application scenario of a cross-platform haptic feedback system in one embodiment. The VibrationManager can be a core component of the core scheduling layer. When the game starts, the application layer calls the unified API to send the trigger request to the VibrationManager. The VibrationManager can be used to load a preset vibration configuration file and determine whether the current device is iOS, Android or a mini-program to obtain the target running platform.

[0048] Upon receiving a vibration request, the vibration manager executes a scheduling algorithm. This algorithm may include checking the cooldown time of the haptic event, whether the current concurrent event count exceeds the limit, and the priority of the currently requested event. Based on priority rules, it decides whether to play or interrupt other haptic events. If execution is allowed, the vibration manager passes the corresponding haptic parameters from the preset vibration configuration file to the target operating platform controller, according to the set of multi-platform controllers corresponding to multiple operating platforms in the platform abstraction layer. The native implementation layer contains a set of multi-platform proxies dedicated to multiple operating platforms. The target platform controller converts the trigger parameters into an instruction format that can be recognized by the target operating platform's native interface. This allows the platform proxy to call the target operating platform's native interface based on the instructions, triggering device vibration on the terminal. For iOS, AHAP-formatted JSON data is executed directly through iOSProxy. For Android, the intensity / time series is converted into a vibration waveform array and the Vibrator API is called. For WeChat Mini Programs, the intensity level is mapped before calling the WeChat vibration interface.

[0049] In some embodiments of this disclosure, such as Figure 3 As shown, a cross-platform haptic feedback method is provided, applicable to cross-platform haptic feedback systems. In one specific embodiment, the method may include the following steps:

[0050] S302: Receive a haptic event trigger request and determine the trigger parameters corresponding to the haptic event.

[0051] Haptic events can include things like players clicking buttons or characters being hit in games. The core scheduling layer receives haptic event trigger requests through a unified interface provided by the application layer. The trigger request can include the type event identifier corresponding to the haptic event. The trigger parameters are standardized data that are universal across all platforms, including intensity, duration, etc., and are stored in a preset vibration configuration file. They do not contain any platform information, ensuring that iOS / Android / Mini Programs can all receive the same set of requests.

[0052] S304: Determine the target operating platform of the terminal device, and create a corresponding target platform controller based on the target operating platform.

[0053] The system can identify the running device by reading the system identifier of the device or environment, determining whether it is an iOS phone, Android phone, WeChat mini-program, or other platform. Each running platform corresponds to an independent platform controller, such as iOSController / AndroidController. The platform controller can include the parameter mapping rules for that platform, used to convert general trigger parameters into instructions that can be recognized by the native interface of the target running platform. After identifying the target running platform, the system dynamically creates a target platform controller for that platform, without needing to preload controllers for all platforms. After detecting the target running platform, the corresponding component is instantiated. For example, if iOS is detected, only iOSController is created; if Android is detected, only AndroidController is created. This avoids loading controllers for all platforms, saving memory. Furthermore, when adding a new platform, only a new controller needs to be added; the core logic does not need to be changed.

[0054] S306: Based on a preset vibration configuration file, determine the tactile event to be executed, and send the trigger parameters to the target platform controller. The target platform controller is used to convert the trigger parameters into instructions that are compatible with the native interface format of the target operating platform.

[0055] The preset vibration configuration file includes pre-configured standardized files that can contain event priorities, cooldown times, global concurrency thresholds, etc. The preset vibration configuration file is loaded and parsed, and received trigger requests are validated according to rules, such as checking if the current concurrency limit is exceeded, if the event is in a cooldown period, and if the priority is sufficient. If the validation passes, it is marked as a haptic event to be executed. The trigger parameters of the haptic event to be executed are passed to the instantiated target runtime platform controller. The target runtime platform controller converts the general haptic parameters into instructions recognizable by the platform's native interface according to the mapping rules. The conversion process is automatically completed by the target runtime platform controller; developers do not need to manually write parameter conversion code.

[0056] S308: Based on the converted instruction, call the native interface of the target operating platform and pass the converted instruction into the native interface. The native interface is used to trigger the terminal device to perform haptic feedback.

[0057] The converted instructions are generated by the target platform controller according to the mapping rules and are only compatible with the current platform's native interface. After receiving the instructions, the native interface drives the vibration component to vibrate according to the intensity and duration of the instructions.

[0058] The terminal device is a mobile device that includes a vibration component, such as a smartphone, tablet, or wearable smart device. It can also be a game console or game controller, with the game controller containing the vibration component.

[0059] The aforementioned cross-platform haptic feedback method only requires writing one set of general configuration files, without needing to adapt the underlying native interfaces separately for iOS / Android / Mini Programs. When adding a new platform, only the controller corresponding to the currently running platform is dynamically instantiated, which completely decouples the business logic from the platform implementation, greatly reducing the workload of repeated development, adaptation and maintenance.

[0060] In some embodiments of this disclosure, determining the tactile event to be executed based on a preset vibration profile includes:

[0061] Retrieve the first-level strategy from the preset vibration configuration file;

[0062] Based on the first-level strategy, one or more haptic events to be executed are determined from among the multiple received haptic events.

[0063] Multiple haptic events may be acquired within a given time period. For example, during a team battle in a game, a player may simultaneously trigger vibrations from being hit, skill activation, interface swiping, and button clicks. If multiple events request execution simultaneously within a short period, the system cannot satisfy them all, and this overlap can lead to chaotic haptic effects. The solution is to first determine the appropriate strategy based on the primary policy in the preset vibration configuration file. This primary policy can include global concurrency limits (Limits), where the system sets a maximum number of concurrent vibration events. When the number of triggered haptic events exceeds this limit, existing events will be rejected or replaced according to preset rules. Alternatively, a cooldown period can be configured for specific events, preventing them from being triggered again during this time and thus preventing excessively frequent event calls.

[0064] In some embodiments of this disclosure, after determining the tactile event to be executed based on a preset vibration profile, the method further includes:

[0065] Determine the priority of the haptic events to be executed;

[0066] Haptic feedback is executed in order of priority based on the haptic events to be executed.

[0067] After selecting the haptic events to be executed, there may be multiple haptic events that need to be executed. If they are executed simultaneously, the vibration effects will overlap, resulting in a blurred haptic sensation. If they are executed randomly, the correlation between the operation and the feedback will be disrupted. Haptic feedback can be executed according to the priority of the haptic events. Each haptic event can be pre-configured with a priority value, with higher values ​​indicating higher priority. Haptic events with higher priority will be executed first.

[0068] In some embodiments of this disclosure, after executing the haptic feedback sequentially based on the priority of the haptic events to be executed, the method further includes:

[0069] If at least two haptic events with the same priority are detected, retrieve the secondary strategy from the preset vibration profile.

[0070] The execution order of haptic events with the same priority is determined based on the secondary strategy.

[0071] When there are at least two haptic events with the same priority pending execution in a game, the execution order of these events is determined according to the secondary strategy in the preset vibration configuration file. For example, if a player quickly and repeatedly clicks the confirmation button in a short period of time, triggering multiple button click vibration events of the same priority, these events will be ordered exactly after entering the pending execution list, creating a conflict. If all events are executed directly, the device will vibrate continuously and repeatedly, resulting in a blurred perception for the player.

[0072] According to the same priority processing rule (When Priority Is Equal), when multiple haptic events to be executed have the same priority, the system follows a two-level strategy, such as ignoring the new event or replacing the old event for processing.

[0073] The secondary strategy in the aforementioned preset vibration configuration file can effectively manage multiple haptic events that are triggered simultaneously, eliminating experience conflicts, performance losses, and effect chaos caused by the lack of global management when multiple vibration effects are triggered at the same time. By introducing primary strategies, priorities, and other mechanisms, it achieves orderly and efficient management of limited vibration resources, ensuring the orderliness, accuracy, and smoothness of the game's haptic feedback.

[0074] In some embodiments of this disclosure, the triggering parameters are stored in a preset vibration configuration file, and the target platform controller converts the triggering parameters into instructions adapted to the native interface format of the target operating platform, including:

[0075] Obtain the standardized trigger parameters corresponding to the haptic events in the preset vibration configuration file;

[0076] According to the preset mapping rules, the standardized trigger parameters are converted into the target format trigger parameters of the target running platform, so as to obtain the instructions adapted to the native interface format of the target running platform.

[0077] The preset vibration configuration file uses a serializable data structure to store standardized trigger parameters for all events. The parameter format is consistent across all platforms and is independent of the native format of any platform. The target platform controller first finds the haptic parameters corresponding to the haptic event to be executed in the unified configuration file. According to the preset mapping rules, it converts the standardized trigger parameters into the target format trigger parameters to obtain instructions that can be directly executed by the native interface.

[0078] In one embodiment of this disclosure, receiving a haptic event trigger request and determining the trigger parameters corresponding to the haptic event includes:

[0079] Based on the type event identifier in the haptic event trigger request, the trigger parameters corresponding to the type event identifier are obtained, and the type event identifier corresponds to the haptic event in the preset vibration configuration file.

[0080] The type event identifier is a preset unique index. There is no need to parse the ambiguous event name. The corresponding haptic event in the preset vibration configuration file can be quickly located directly by the identifier. In multi-event concurrent scenarios such as game team battles, the time spent matching trigger parameters is reduced, and the vibration feedback and operation are not synchronized due to matching delay.

[0081] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0082] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 4 As shown, the computer device includes a processor, memory, communication interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a cross-platform haptic feedback method. The display screen can be an LCD screen or an e-ink screen. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad on the computer device's casing, or an external keyboard, touchpad, or mouse.

[0083] Those skilled in the art will understand thatFigure 4 The structure shown is merely a block diagram of a portion of the structure related to the present disclosure and does not constitute a limitation on the computer device to which the present disclosure is applied. A specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0084] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the methods described in any embodiment of this disclosure.

[0085] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the methods described in any embodiment of this disclosure.

[0086] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this disclosure can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this disclosure may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this disclosure may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0087] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0088] The embodiments described above are merely illustrative of several implementations of this disclosure, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent disclosure. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this disclosure, and these all fall within the protection scope of this disclosure. Therefore, the protection scope of this disclosure should be determined by the appended claims.

Claims

1. A cross-platform haptic feedback method, characterized in that, The method includes: Receive haptic event trigger requests and determine the trigger parameters corresponding to the haptic event; Determine the target operating platform of the terminal device, and create a corresponding target platform controller based on the target operating platform; Based on a preset vibration profile, the tactile event to be executed is determined, and the trigger parameters are sent to the target platform controller. The target platform controller converts the trigger parameters into instructions that are compatible with the native interface format of the target operating platform. Based on the instruction, the native interface of the target operating platform is invoked, and the instruction is passed to the native interface, which is used to trigger the terminal device to perform haptic feedback.

2. The method according to claim 1, characterized in that, The determination of the tactile event to be executed based on the preset vibration profile includes: Retrieve the first-level strategy from the preset vibration configuration file; Based on the first-level strategy, one or more haptic events to be executed are determined from among the multiple received haptic events.

3. The method according to claim 1 or 2, characterized in that, After determining the tactile event to be executed based on the preset vibration profile, the process also includes: Determine the priority of the haptic events to be executed; Haptic feedback is executed in order of priority based on the haptic events to be executed.

4. The method according to claim 3, characterized in that, After executing the haptic feedback sequentially based on the priority of the haptic events to be executed, the method further includes: If at least two haptic events with the same priority are detected, retrieve the secondary strategy from the preset vibration profile. The execution order of haptic events with the same priority is determined based on the secondary strategy.

5. The method according to claim 1, characterized in that, The triggering parameters are stored in the preset vibration configuration file. The target platform controller converts the triggering parameters into instructions adapted to the native interface format of the target operating platform, including: Obtain the standardized trigger parameters corresponding to the haptic events in the preset vibration configuration file; According to the preset mapping rules, the standardized trigger parameters are converted into the target format trigger parameters of the target running platform, so as to obtain the instructions adapted to the native interface format of the target running platform.

6. The method according to claim 1, characterized in that, Receive a haptic event trigger request and determine the trigger parameters corresponding to the haptic event, including: Based on the type event identifier in the haptic event trigger request, the trigger parameters corresponding to the type event identifier are obtained, and the type event identifier corresponds to the haptic event in the preset vibration configuration file.

7. A cross-platform haptic feedback system, characterized in that, The system includes: The application layer provides a unified application interface and responds to user touch event triggering operations. It initiates touch event triggering requests to the core scheduling layer through the unified application interface, and the triggering request includes triggering parameters. The core scheduling layer is used to determine the target operating platform of the terminal device, create a corresponding target platform controller according to the target operating platform, determine the tactile event to be executed based on the preset vibration configuration file, and send the trigger parameters to the target platform controller when it is determined that the tactile event will be executed. The platform abstraction layer includes multiple platform controllers corresponding to different operating platforms, which are used to convert trigger parameters into instructions adapted to the native interface format of the target operating platform through the target platform controller; The native implementation layer is used to receive the instruction, call the native interface of the target running platform, and pass the instruction to the native interface. The native interface is used to trigger the terminal device to perform haptic feedback.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images