Interaction method, device and storage medium

Abstract

The present application provides an interaction method, device and storage medium. The method receives a trigger request sent by an input device through an execution component. The execution component corresponds to the input device. The state of the execution component is active, and the states of other execution components are inactive, so that only one input device is active (can trigger an event) at the same time, so that the UI only responds to one trigger at the same time, and then, according to the above trigger request, trigger signal collision detection and event processing are performed, and the processing result is displayed on the UI, which solves the problem of how the UI responds correctly to the interaction between multiple input devices and the UI in the XR scenario, and ensures that the UI interaction in the XR scenario is correct, fast and complete.

Description

Technical Field

[0001] The present application relates to virtual reality technology, and in particular to an interaction method, device and storage medium. Background Art

[0002] Virtual Reality (VR) technology is a virtual environment created using modern computer technology. Users can use specific human-computer interaction devices and equipment to interact with the virtual environment and experience an immersive experience. Extended Reality (XR) is a further development of VR technology. Extended Reality refers to the use of computer technology and wearable devices to create a real-virtual, human-computer interactive environment.

[0003] Interaction with virtual objects is an essential part of the XR world. It is divided into two interaction modes according to the distance: one is near-field interaction, in which users touch objects with their fingers or handles; the other is far-field interaction, in which users generally use rays to perform collision detection on virtual objects to further complete the entire trigger cycle.

[0004] For far-field interaction, more than one input device may exist at the same time in an XR scene, but the user interface (UI) in the scene can only respond to one trigger at a time. Therefore, how to manage the interaction between multiple input devices and UI in an XR scene has become an urgent problem to be solved. Summary of the invention

[0005] The present application provides an interaction method, apparatus, and storage medium to manage the interaction between multiple input devices and a UI in an XR scenario.

[0006] In a first aspect, an embodiment of the present application provides an interaction method, which is applied to a target execution component, wherein the target execution component is one of multiple execution components, and one execution component corresponds to one input device, and the method includes:

[0007] receiving a trigger request, wherein the trigger request is sent by a target input device, the target execution component corresponds to the target input device, the state of the target execution component is an active state, and the states of the remaining execution components among the multiple execution components except the target execution component are in an inactive state;

[0008] Cache the trigger request in a preset action queue, and perform a trigger signal collision detection based on the UI after receiving an update instruction;

[0009] After the trigger signal collision detection, a trigger request is obtained from the preset action queue according to a preset order as a trigger request to be executed;

[0010] According to the trigger request to be executed, the corresponding action execution interface is called to process the trigger event, and the processing result of the action execution interface is displayed on the UI.

[0011] In a possible implementation, before calling a corresponding action execution interface to process a trigger event according to the trigger request to be executed, the method further includes:

[0012] Determine whether the action triggered by the currently executed trigger request is within the action cycle;

[0013] The calling of a corresponding action execution interface to process a trigger event according to the trigger request to be executed includes:

[0014] If the action triggered by the currently executed trigger request is not within the action cycle, then according to the to-be-executed trigger request, the corresponding action execution interface is called to process the trigger event.

[0015] In a possible implementation, after determining whether the action triggered by the trigger request currently being executed is within the action cycle, the method further includes:

[0016] If the action triggered by the trigger request currently being executed is within the action cycle, determining whether the action triggered by the trigger request to be executed is mutually exclusive with the action triggered by the trigger request currently being executed;

[0017] The calling of a corresponding action execution interface to process a trigger event according to the trigger request to be executed includes:

[0018] If the action triggered by the trigger request to be executed is not mutually exclusive with the action triggered by the trigger request currently being executed, then according to the trigger request to be executed, calling the corresponding action execution interface to process the trigger event;

[0019] If the action triggered by the to-be-executed trigger request is mutually exclusive with the action triggered by the currently-executed trigger request, then after the currently-executed trigger request is executed, the corresponding action execution interface is called according to the to-be-executed trigger request to process the trigger event.

[0020] In a possible implementation, the trigger request carries an activation flag, and the activation flag is used to indicate whether the action triggered by the trigger request is an activation action;

[0021] The determining whether the action triggered by the trigger request currently being executed is within the action cycle includes:

[0022] Determining, according to the activation identifier carried by the trigger request currently being executed, whether the action triggered by the trigger request currently being executed is an activation action;

[0023] If the action triggered by the currently executed trigger request is an activation action, it is determined that the action triggered by the currently executed trigger request is within an action cycle.

[0024] In a possible implementation, the determining whether the action triggered by the to-be-executed trigger request and the action triggered by the currently-executed trigger request are mutually exclusive includes:

[0025] Obtaining the type of the action triggered by the to-be-executed trigger request and the type of the action triggered by the currently-executed trigger request;

[0026] Determine whether the type of the action triggered by the trigger request to be executed is consistent with the type of the action triggered by the trigger request currently being executed;

[0027] If the type of the action triggered by the to-be-executed trigger request is consistent with the type of the action triggered by the currently-executed trigger request, it is determined that the action triggered by the to-be-executed trigger request is not mutually exclusive with the action triggered by the currently-executed trigger request.

[0028] In a possible implementation, after the trigger signal collision detection, before obtaining a trigger request from the preset action queue in a preset order as a trigger request to be executed, the method further includes:

[0029] According to the nodes detected by the trigger signal collision with the UI in the previous frame and the nodes detected by the trigger signal collision with the UI in the current frame, the corresponding hover processing interface is called to process the hover event, and the processing result of the hover processing interface is displayed on the UI.

[0030] In a possible implementation, the hover processing interface includes a hover entry interface, a hover stay interface, and a hover end interface;

[0031] The node detected according to the collision of the trigger signal and the UI in the previous frame and the node detected according to the collision of the trigger signal and the UI in the current frame, calling the corresponding hover processing interface to process the hover event, including:

[0032] Compare the node where the trigger signal collides with the UI in the previous frame with the node where the trigger signal collides with the UI in the current frame;

[0033] According to the comparison result, for a node that is not among the nodes where the trigger signal collides with the user interface in the previous frame but is among the nodes where the trigger signal collides with the user interface in the current frame, calling the hover entry interface to process the hover event;

[0034] According to the comparison result, among the nodes where the trigger signal collides with the user interface in the previous frame and among the nodes where the trigger signal collides with the user interface in the current frame, calling the hovering interface to process the hovering event;

[0035] According to the comparison result, among the nodes where the trigger signal collides with the user interface in the previous frame, but not among the nodes where the trigger signal collides with the user interface in the current frame, the hover end interface is called to process the hover event.

[0036] In a possible implementation, calling a corresponding action execution interface to process a trigger event according to the trigger request to be executed includes:

[0037] Obtain the type of action triggered by the trigger request to be executed;

[0038] Determining a corresponding action execution interface to be called according to the type of action triggered by the trigger request to be executed;

[0039] The corresponding action execution interface is called to process the triggering event.

[0040] In a possible implementation, the target execution component interacts with a management system;

[0041] The receiving a trigger request comprises:

[0042] Receive the trigger request sent by the management system, wherein the trigger request is received by the management system from the target input device, and the trigger request is used to instruct the management system to set the state of the target execution component to an active state, and to set the state of each execution component remaining among the multiple execution components except the target execution component to an inactive state.

[0043] In a possible implementation manner, the trigger signal is a ray.

[0044] In a second aspect, an embodiment of the present application provides an interactive device, which is applied to a target execution component, wherein the target execution component is one of a plurality of execution components, and one execution component corresponds to one input device, and the device comprises:

[0045] a receiving module, configured to receive a trigger request, wherein the trigger request is sent by a target input device, the target execution component corresponds to the target input device, the state of the target execution component is an active state, and the states of the remaining execution components among the multiple execution components except the target execution component are in an inactive state;

[0046] A processing module, used for caching the trigger request in a preset action queue, and performing a trigger signal collision detection based on the UI after receiving an update instruction;

[0047] An acquisition module, used for acquiring a trigger request from the preset action queue as a trigger request to be executed according to a preset order after the trigger signal collision detection;

[0048] The calling module is used to call the corresponding action execution interface to process the trigger event according to the trigger request to be executed, and display the processing result of the action execution interface on the UI.

[0049] In a possible implementation, the calling module is specifically used to:

[0050] Determine whether the action triggered by the currently executed trigger request is within the action cycle;

[0051] If the action triggered by the currently executed trigger request is not within the action cycle, then according to the to-be-executed trigger request, the corresponding action execution interface is called to process the trigger event.

[0052] In a possible implementation, the calling module is specifically used to:

[0053] If the action triggered by the trigger request currently being executed is within the action cycle, determining whether the action triggered by the trigger request to be executed is mutually exclusive with the action triggered by the trigger request currently being executed;

[0054] If the action triggered by the trigger request to be executed is not mutually exclusive with the action triggered by the trigger request currently being executed, then according to the trigger request to be executed, calling the corresponding action execution interface to process the trigger event;

[0055] If the action triggered by the to-be-executed trigger request is mutually exclusive with the action triggered by the currently-executed trigger request, then after the currently-executed trigger request is executed, the corresponding action execution interface is called according to the to-be-executed trigger request to process the trigger event.

[0056] In a possible implementation, the trigger request carries an activation flag, and the activation flag is used to indicate whether the action triggered by the trigger request is an activation action;

[0057] The calling module is specifically used for:

[0058] Determining, according to the activation identifier carried by the trigger request currently being executed, whether the action triggered by the trigger request currently being executed is an activation action;

[0059] If the action triggered by the currently executed trigger request is an activation action, it is determined that the action triggered by the currently executed trigger request is within an action cycle.

[0060] In a possible implementation, the calling module is specifically used to:

[0061] Obtaining the type of the action triggered by the trigger request to be executed and the type of the action triggered by the trigger request currently being executed;

[0062] Determine whether the type of the action triggered by the trigger request to be executed is consistent with the type of the action triggered by the trigger request currently being executed;

[0063] If the type of the action triggered by the to-be-executed trigger request is consistent with the type of the action triggered by the currently-executed trigger request, it is determined that the action triggered by the to-be-executed trigger request is not mutually exclusive with the action triggered by the currently-executed trigger request.

[0064] In a possible implementation, after the trigger signal collision detection, the acquisition module acquires a trigger request from the preset action queue in a preset order as a trigger request to be executed, and is further used to:

[0065] According to the nodes detected by the trigger signal collision with the UI in the previous frame and the nodes detected by the trigger signal collision with the UI in the current frame, the corresponding hover processing interface is called to process the hover event, and the processing result of the hover processing interface is displayed on the UI.

[0066] In a possible implementation, the hover processing interface includes a hover entry interface, a hover stay interface, and a hover end interface;

[0067] The acquisition module is specifically used for:

[0068] Compare the node where the trigger signal collides with the UI in the previous frame with the node where the trigger signal collides with the UI in the current frame;

[0069] According to the comparison result, for a node that is not among the nodes where the trigger signal collides with the user interface in the previous frame but is among the nodes where the trigger signal collides with the user interface in the current frame, calling the hover entry interface to process the hover event;

[0070] According to the comparison result, among the nodes where the trigger signal collides with the user interface in the previous frame and among the nodes where the trigger signal collides with the user interface in the current frame, calling the hovering interface to process the hovering event;

[0071] According to the comparison result, among the nodes where the trigger signal collides with the user interface in the previous frame, but not among the nodes where the trigger signal collides with the user interface in the current frame, the hover end interface is called to process the hover event.

[0072] In a possible implementation, the calling module is specifically used to:

[0073] Obtain the type of action triggered by the trigger request to be executed;

[0074] Determining a corresponding action execution interface to be called according to the type of action triggered by the trigger request to be executed;

[0075] The corresponding action execution interface is called to process the triggering event.

[0076] In a possible implementation manner, the target execution component interacts with a management system.

[0077] The receiving module is specifically used for:

[0078] Receive the trigger request sent by the management system, wherein the trigger request is received by the management system from the target input device, and the trigger request is used to instruct the management system to set the state of the target execution component to an active state, and to set the state of each execution component remaining among the multiple execution components except the target execution component to an inactive state.

[0079] In a possible implementation manner, the trigger signal is a ray.

[0080] In a third aspect, an embodiment of the present application provides a target execution component, including:

[0081] processor;

[0082] Memory; and

[0083] Computer programs;

[0084] The computer program is stored in the memory and is configured to be executed by the processor, wherein the computer program includes instructions for executing the method as described in the first aspect.

[0085] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program enables a server to execute the method described in the first aspect.

[0086] In a fifth aspect, an embodiment of the present application provides a computer program product, comprising computer instructions, wherein the computer instructions are executed by a processor according to the method described in the first aspect.

[0087] The interactive method, device and storage medium provided by the embodiment of the present application receive the trigger request sent by the input device through the execution component, the execution component corresponds to the input device, the state of the execution component is active, and the state of other execution components is inactive, so that only one input device is active (can trigger an event) at the same time, so that the UI only responds to one trigger at the same time, and then, according to the above trigger request, trigger signal collision detection and event processing are performed, and the processing result is displayed in the UI, which solves the problem of how the UI responds correctly to the interaction between multiple input devices and the UI in the XR scene, and ensures that the UI interaction in the XR scene is correct, fast and complete. Moreover, after receiving the trigger request sent by the management system, the execution component in the embodiment of the present application caches the trigger request in the preset action queue, so that on the one hand, the trigger requests with mutually exclusive relationships can be managed to ensure that the action cycles of the two do not overlap, and on the other hand, within the action cycle, even if the trigger request is not sent every frame, it can also ensure that the execution component generates a trigger event every frame, so that the UI can completely process the corresponding event. BRIEF DESCRIPTION OF THE DRAWINGS

[0088] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0089] Figure 1 A schematic diagram of the interactive system architecture provided in an embodiment of the present application;

[0090] Figure 2 A flowchart of an interactive method provided in an embodiment of the present application;

[0091] Figure 3 A schematic diagram of a hover event processing provided in an embodiment of the present application;

[0092] Figure 4 A schematic diagram of trigger event processing provided in an embodiment of the present application;

[0093] Figure 5 A flowchart of another interactive method provided in an embodiment of the present application;

[0094] Figure 6 A flowchart of another interaction method provided in an embodiment of the present application;

[0095] Figure 7 A schematic diagram of the structure of an interactive device provided in an embodiment of the present application;

[0096] Figure 8 A schematic diagram of the basic hardware architecture of a target execution component provided in an embodiment of the present application. DETAILED DESCRIPTION

[0097] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0098] The terms "first", "second", "third", and "fourth", etc. (if any) in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products, or devices.

[0099] XR technology includes augmented reality (AR), VR, and mixed reality (MR), which uses hardware devices combined with a variety of technical means to merge virtual content and real scenes. In the XR scenario, there are two interaction modes based on distance: one is near-field interaction, where users use finger clicks or handles to touch objects; the other is far-field interaction, where users generally use rays to perform collision detection on virtual objects to further complete the entire trigger cycle. Among them, for the latter, there may be more than one input device in the XR scenario at the same time, and the UI in the scene can only respond to one trigger at the same time. Therefore, a mechanism is needed to manage the interaction of multiple input devices with the UI.

[0100] Therefore, an embodiment of the present application proposes an interaction method, in which a trigger request sent by an input device is received through an execution component, the execution component corresponds to the input device, the state of the execution component is an active state, and the states of other execution components are inactive states, so that only one input device is active (can trigger events) at the same time, so that the UI only responds to one trigger at the same time, and then, according to the above trigger request, trigger signal collision detection and event processing are performed, and the processing results are displayed on the UI, to ensure that the interaction between multiple input devices and the UI in the XR scene is correct, fast and complete.

[0101] Optionally, the interaction method provided in the embodiment of the present application can be applied to Figure 1 In the interactive system shown. Figure 1 In the interactive system architecture, the interactive system architecture may include an execution component 101. The execution component 101 is one of multiple execution components, and one execution component corresponds to one input device. Here, the corresponding can be understood as one execution component is bound to one input device, and the execution component only processes the relevant information sent by the input device bound to it. If there are execution components 1, 2 and 3, and input devices A, B and C, execution component 1 corresponds to input device A, and execution component 1 receives the trigger request sent by input device A, and can perform trigger signal collision detection and event processing based on the trigger request.

[0102] In the specific implementation process, the execution component 101 receives the trigger request sent by the corresponding input device, performs trigger signal collision detection and event processing based on the above trigger request, and displays the processing result on the UI, solving the problem of how the UI responds correctly to the interaction between multiple input devices and the UI in the XR scene. Among them, the state of the execution component 101 is active, and the states of other execution components are inactive, so that only one input device is active (can trigger an event) at the same time, so that the UI only responds to one trigger at the same time.

[0103] In addition, the above interactive system architecture may include a management system 102, and the execution component 101 may interact with the management system 102 to manage the interaction between multiple input devices and the UI.

[0104] Among them, the management system 102 can receive each trigger request of each input device. If the user sends a trigger request through a certain input device, the management system 102 receives the trigger request, and manages multiple execution components according to the trigger request, such as setting the state of the execution component corresponding to the above input device to an active state, and setting the state of other execution components to an inactive state, etc., so that only one input device is active at the same time, so that the UI only responds to one trigger at the same time. Then, the management system 102 can also send the above trigger request to the execution component corresponding to the above input device, if the execution component is the above execution component 101, and the execution component 101 performs trigger signal collision detection and event processing based on the above trigger request, so as to ensure the correct, fast and complete interaction between multiple input devices and UI in the XR scene.

[0105] It should be noted that the system architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0106] The technical solution of the present application is described below by taking several embodiments as examples, and the same or similar concepts or processes may not be repeated in some embodiments.

[0107] Figure 2 A flowchart of an interactive method provided in an embodiment of the present application. The execution subject of this embodiment is as follows Figure 1 For example, the specific execution subject can be determined according to the actual application scenario, and the present application embodiment does not impose any special restrictions on this. Figure 2 The above-mentioned execution component can be understood as a target execution component, which is one of multiple execution components, and one execution component corresponds to one input device. Figure 2 As shown, the interaction method provided in the embodiment of the present application may include the following steps:

[0108] S201: receiving a trigger request, where the trigger request is sent by a target input device, the target execution component corresponds to the target input device, the state of the target execution component is an active state, and the states of the remaining execution components among the multiple execution components except the target execution component are set to an inactive state.

[0109] Here, the user can send a trigger request through a target input device. The target input device can be any input device. The input device corresponds to an execution component, that is, is bound to an execution component, and the execution component processes the relevant information sent by the target input device.

[0110] Among them, the above-mentioned trigger request can be a trigger request sent by the management system received by the above-mentioned target execution component, that is, the management system receives the trigger request sent by the target input device, and then forwards the trigger request to the above-mentioned target execution component, so that the target execution component can accurately process the relevant information sent by the corresponding input device. Here, the above-mentioned management system can manage multiple execution components including the above-mentioned target execution component, such as the above-mentioned control forwarding corresponding information to each execution component, and controlling the state of the execution component, setting the state of the above-mentioned target execution component to an active state, and setting the state of each execution component except the above-mentioned target execution component to an inactive state, so that only one input device is active (can trigger an event) at the same time, so that the UI only responds to one trigger at the same time.

[0111] Here, the trigger request may carry the identity of the target input device. Taking two input devices as an example, if the two input devices are a left handle and a right handle, respectively, and the target input device is the right handle, the trigger request may carry the identity of the right handle. The management system receives each trigger request of each input device. After receiving the trigger request of the target input device, the management system may determine the target execution component corresponding to the target input device according to the identity of the target input device carried in the trigger request, and then set the state of the target execution component to an active state, and set the states of the remaining execution components except the target execution component among the multiple execution components managed to an inactive state, so that only one input device is active (can trigger an event) at the same time, so that the UI only responds to one trigger at the same time, meeting the needs of actual applications.

[0112] In the embodiment of the present application, the management system can pre-store the correspondence between the identity of the input device and the execution component, so that after receiving the trigger request of the target input device, the target execution component corresponding to the target input device can be determined based on the correspondence and the identity of the target input device carried in the trigger request, which is simple and convenient. The identity can be the name, number, etc. of the input device that can uniquely identify the device identity.

[0113] In addition, the input device corresponding to the inactive execution component is triggered, such as the execution component corresponding to the left handle is in the inactive state, and the execution component corresponding to the right handle is in the active state. When the left handle is triggered, the management system will first cancel and clear all trigger events of the currently active handle (right handle), and set the execution component corresponding to the left handle to the active state to respond to the corresponding trigger, meet the actual application needs, and the user is unaware of whether the handle is active, thereby improving the user experience.

[0114] S202: Cache the trigger request in a preset action queue, and perform a trigger signal collision detection based on the UI after receiving an update instruction.

[0115] Here, the above-mentioned target execution component caches the above-mentioned trigger request in the preset action queue. On the one hand, it can manage the trigger requests with mutually exclusive relationships to ensure that the action cycles of the two do not overlap. On the other hand, within the action cycle, even if the trigger request is not sent every frame, it can also ensure that the execution component generates a trigger event every frame, so that the UI can fully handle the corresponding event.

[0116] In an embodiment of the present application, the trigger signal may be a collision trigger signal, such as a ray. After receiving the update instruction, the target execution component may track the position and posture of the target input device, thereby determining the starting point and direction of the ray, updating the position and direction of the ray, etc., and performing ray collision detection in each frame to determine the node where the ray collides with the UI, and displaying the collided node in the UI so that the user can understand the status of the input device.

[0117] In addition, after determining the node where the trigger signal collides with the UI, the target execution component may also store the node where the trigger signal collides with the UI, so as to facilitate subsequent processing of related events based on the stored colliding nodes.

[0118] S203: After the trigger signal collision detection, a trigger request is obtained from the preset action queue in a preset order as a trigger request to be executed.

[0119] Here, the above-mentioned preset order can be set according to actual conditions, for example, first-in-first-out, that is, after the trigger signal collision detection, the above-mentioned target execution component obtains a trigger request from the above-mentioned preset action queue in a first-in-first-out order as a trigger request to be executed to meet various application needs.

[0120] For example, taking the trigger signal as a ray, Figure 3 As shown, after the ray collision detection, before obtaining a trigger request as a trigger request to be executed from the preset action queue in a preset order, the above-mentioned target execution component can also update the length of the ray rendering, and update the visibility and position of the ray and UI intersection cursor. When the state of the target execution component is active, according to the ray collision detected in the previous frame and the ray and UI intersection cursor, and the ray and UI intersection cursor in the current frame, the corresponding hover processing interface is called to process the hover event, and the processing result of the hover processing interface is displayed on the UI, which solves the hover event processing of multiple input devices interacting with the UI in the XR scenario.

[0121] Among them, the above-mentioned hover processing interface includes a hover entry interface, a hover stay interface and a hover end interface. The above-mentioned target execution component can compare the nodes where the trigger signal collides with the UI in the above-mentioned previous frame with the nodes where the trigger signal collides with the UI in the current frame. According to the comparison result, the nodes in the nodes where the trigger signal collides with the UI in the previous frame but in the nodes where the trigger signal collides with the UI in the current frame call the hover entry interface to process the hover event; according to the above-mentioned comparison result, the nodes in the nodes where the trigger signal collides with the UI in the previous frame and in the nodes where the trigger signal collides with the UI in the current frame call the hover stay interface to process the hover event; according to the above-mentioned comparison result, the nodes in the nodes where the trigger signal collides with the UI in the previous frame but in the nodes where the trigger signal collides with the UI in the current frame call the hover end interface to process the hover event, that is, different events call different interface processing to successfully process the corresponding event through the called interface. For example, the nodes that the trigger signal collides with the UI in the previous frame are: A, B, C, and the nodes that the trigger signal collides with the UI in the current frame are: A, C, D. Then the hover stay interface is called in A and C to handle the hover event, the hover end interface is called in B to handle the hover event, and the hover entry interface is called in D to handle the hover event.

[0122] S204: According to the trigger request to be executed, the corresponding action execution interface is called to process the trigger event, and the processing result of the action execution interface is displayed on the UI.

[0123] For example, Figure 4 As shown, before the target execution component calls the corresponding action execution interface to process the trigger event according to the trigger request to be executed, it can also determine whether the action triggered by the currently executed trigger request is within the action cycle. If the action triggered by the currently executed trigger request is not within the action cycle, it means that the action triggered by the currently executed trigger request may be completed or the user has sent an end request, and there will be no mutual exclusion with the action triggered by the trigger request to be executed. At this time, the target execution component can call the corresponding action execution interface to process the trigger event according to the trigger request to be executed.

[0124] Here, if the action triggered by the currently executed trigger request is within the action cycle, the above-mentioned target execution component can further determine whether the action triggered by the above-mentioned trigger request to be executed is mutually exclusive with the action triggered by the currently executed trigger request. If they are not mutually exclusive, then according to the above-mentioned trigger request to be executed, call the corresponding action execution interface to handle the trigger event; if they are mutually exclusive, then after the currently executed trigger request is executed, call the corresponding action execution interface to handle the trigger event according to the above-mentioned trigger request to be executed.

[0125] For non-mutually exclusive trigger requests, the target execution components can process them in parallel to meet application requirements. For mutually exclusive trigger requests, the target execution components process the first trigger request before processing the other trigger request to ensure the integrity of the action cycle.

[0126] In an embodiment of the present application, when the target execution component determines whether the action triggered by the trigger request to be executed is mutually exclusive with the action triggered by the trigger request currently being executed, it can obtain the type of the action triggered by the trigger request to be executed and the type of the action triggered by the trigger request currently being executed, and then determine whether the type of the action triggered by the trigger request to be executed is consistent with the type of the action triggered by the trigger request currently being executed. If they are consistent, it is determined that the action triggered by the trigger request to be executed is not mutually exclusive with the action triggered by the trigger request currently being executed. If they are inconsistent, it is determined that the action triggered by the trigger request to be executed is mutually exclusive with the action triggered by the trigger request currently being executed, and then subsequent steps are executed based on the above judgment result to ensure that subsequent processing proceeds normally. Among them, the trigger request can carry the type of triggered action, and the target execution component obtains the type of action triggered by the trigger request to be executed and the type of action triggered by the trigger request currently being executed according to the type of triggered action carried by the trigger request to be executed and the type of triggered action carried by the trigger request currently being executed.

[0127] In addition, the trigger request may carry an activation identifier, which is used to indicate whether the action triggered by the trigger request is an activation action. When judging whether the action triggered by the currently executed trigger request is within the action cycle, the target execution component may determine whether the action triggered by the currently executed trigger request is an activation action according to the activation identifier carried by the currently executed trigger request. If the action triggered by the currently executed trigger request is an activation action, it is determined that the action triggered by the currently executed trigger request is within the action cycle. For example, taking the button on the handle as an example, the user sends a trigger request by pressing the button, and the trigger request carries an activation identifier, which is used to indicate that the action triggered by the trigger request is an activation action (i.e., when the button is pressed, the activation identifier carried by the trigger request indicates that the action triggered by the trigger request is an activation action, and when the button is lifted, the activation identifier carried by the trigger request indicates that the action triggered by the trigger request is not an activation action). The management system receives the trigger request and sends the trigger request to the corresponding execution component, which determines whether the action triggered by the trigger request is an activation action according to the activation identifier, thereby accurately determining whether the action triggered by the trigger request is within the action cycle.

[0128] In an embodiment of the present application, the above-mentioned target execution component caches the received trigger requests in a queue, and then takes out a trigger request from the queue as a trigger request to be executed. While ensuring the integrity of the action cycle, the corresponding action execution interface is called to process the trigger event, and the processing results of the action execution interface are displayed on the UI.

[0129] Among them, when calling the corresponding action execution interface to process the trigger event, the target execution component can obtain the type of action triggered by the trigger request to be executed, and then determine the corresponding action execution interface to be called according to the type, and then call the corresponding action execution interface to process the trigger event to ensure that subsequent processing is carried out accurately. Here, the above types may include single click, joystick, etc. The target execution component determines the action execution interface such as single click, joystick, etc. according to the type, and thus calls the action execution interface such as single click, joystick, etc. to process events such as single click, joystick, etc.

[0130] Here, the above-mentioned action execution interface may include interactive components, such as ordinary buttons (Button), progress bars (Slider), single check buttons (Tab), scroll views (ScrollView) and other UI components that carry specific functions, so as to implement their respective functional logic in the above-mentioned interface, respond to the triggering of input devices, and open up a complete UI interaction link.

[0131] In the embodiment of the present application, the trigger request sent by the input device is received by the execution component, and the execution component corresponds to the input device. The state of the execution component is active, and the state of other execution components is inactive, so that only one input device is active (can trigger an event) at the same time, so that the UI only responds to one trigger at the same time, and then, according to the above trigger request, the trigger signal collision detection and event processing are performed, and the processing result is displayed in the UI, which solves the interaction between multiple input devices and the UI in the XR scene, and how the UI responds correctly, ensuring that the UI interaction in the XR scene is correct, fast and complete. Moreover, in the embodiment of the present application, after receiving the trigger request sent by the management system, the execution component caches the trigger request in the preset action queue, so that on the one hand, the trigger requests with mutually exclusive relationships can be managed to ensure that the action cycles of the two do not overlap, and on the other hand, within the action cycle, even if the trigger request is not sent every frame, it can also ensure that the execution component generates a trigger event every frame, so that the UI can completely process the corresponding event.

[0132] In addition, taking the example of the target execution component interacting with the management system, the management system receiving the trigger request sent by the target input device and forwarding the trigger request to the target execution component, Figure 5 A flow chart of another interaction method is given, namely the flow chart of the interaction method corresponding to the management system. For related description, see Figure 2 , I will not repeat it here, such as Figure 5 As shown, the method may include:

[0133] S501: Receive a trigger request from a target input device.

[0134] S502: According to the above trigger request, the state of the target execution component is set to an active state, and the state of each execution component remaining among the multiple execution components managed except the above target execution component is set to an inactive state, wherein one execution component corresponds to one input device, and the above target execution component corresponds to the above target input device.

[0135] Here, one input device corresponds to one execution component, that is, it is bound to one execution component. In this way, the above-mentioned management system can set the state of the target execution component corresponding to the target input device to an active state, and set the states of other execution components to an inactive state, so that only one input device is active at the same time (can trigger an event), so that the UI only responds to one trigger at the same time, meeting the needs of actual applications.

[0136] S503: Send the trigger request to the target execution component. The trigger request is used to instruct the target execution component to cache the trigger request in a preset action queue, and after receiving an update instruction, perform a trigger signal collision detection based on the UI. After the trigger signal collision detection, obtain a trigger request from the preset action queue as a trigger request to be executed in a preset order. According to the trigger request to be executed, call the corresponding action execution interface to process the trigger event, and display the processing result of the action execution interface on the UI.

[0137] Among them, after setting the active state of the execution component, the above-mentioned management system sends the above-mentioned trigger request to the above-mentioned target execution component, so that the above-mentioned target execution component caches the received trigger request in a queue, and then takes out a trigger request from the queue as a trigger request to be executed. While ensuring the integrity of the action cycle, the corresponding action execution interface is called to process the trigger event, and the processing result of the action execution interface is displayed on the UI.

[0138] The embodiment of the present application manages the interaction between multiple input devices and the UI by interacting with the management system and multiple execution components. Among them, one execution component corresponds to one input device. After receiving the trigger request of the input device, the management system sets the state of the execution component corresponding to the input device to the active state, and the state of other execution components to the inactive state, so that only one input device is active (can trigger an event) at the same time, and then sends the trigger request to the corresponding execution component, which performs trigger signal collision detection and event processing, and displays the processing results in the UI, ensuring the correct, fast and complete interaction between multiple input devices and the UI in the XR scene.

[0139] in addition, Figure 6 A flow chart of another interaction method is provided for the embodiment of the present application. This embodiment illustrates the flow of the interaction method from the perspective of interaction between the management system and the execution component. Figure 6 As shown, the method may include:

[0140] S601: The management system receives a trigger request from a target input device.

[0141] S602: The management system sets the state of the target execution component to an active state based on the trigger request, and sets the state of each of the multiple execution components managed except the target execution component to an inactive state, wherein one execution component corresponds to one input device, and the target execution component corresponds to the target input device.

[0142] S603: Send the trigger request to the target execution component.

[0143] S604: The target execution component receives the trigger request, caches the trigger request in a preset action queue, and performs a trigger signal collision detection based on the UI after receiving an update instruction.

[0144] Among them, the above-mentioned target execution component caches the above-mentioned trigger request in a preset action queue. On the one hand, it can manage the trigger requests with mutually exclusive relationships to ensure that the action cycles of the two do not overlap. On the other hand, within the action cycle, even if the trigger request is not sent every frame, it can also ensure that the execution component generates a trigger event every frame.

[0145] S605: After the trigger signal collision detection, the target execution component obtains a trigger request from the preset action queue as a trigger request to be executed according to a preset order.

[0146] Here, after the trigger signal collision detection, before obtaining a trigger request as a trigger request to be executed from the preset action queue in a preset order, the above-mentioned target execution component can also call the corresponding hover processing interface to handle the hover event based on the node where the trigger signal and the UI collided in the previous frame detected by the trigger signal collision, and the node where the trigger signal and the UI collided in the current frame, and display the processing result of the hover processing interface in the UI.

[0147] Among them, the above-mentioned hover processing interface includes a hover entry interface, a hover stay interface and a hover end interface. The above-mentioned target execution component can compare the nodes where the trigger signal collides with the UI in the previous frame with the nodes where the trigger signal collides with the UI in the current frame; according to the comparison result, the nodes in the nodes where the trigger signal collides with the UI in the previous frame but in the nodes where the trigger signal collides with the UI in the current frame call the hover entry interface to process the hover event; according to the above-mentioned comparison result, the nodes in the nodes where the trigger signal collides with the UI in the previous frame and in the nodes where the trigger signal collides with the UI in the current frame call the hover stay interface to process the hover event; according to the above-mentioned comparison result, the nodes in the nodes where the trigger signal collides with the UI in the previous frame but in the nodes where the trigger signal collides with the UI in the current frame call the hover end interface to process the hover event.

[0148] S606: The target execution component calls the corresponding action execution interface to process the trigger event according to the trigger request to be executed, and displays the processing result of the action execution interface on the UI.

[0149] Among them, the above-mentioned target execution component can first determine whether the action triggered by the currently executed trigger request is within the action cycle. If the action triggered by the currently executed trigger request is not within the action cycle, then according to the above-mentioned trigger request to be executed, call the corresponding action execution interface to handle the trigger event.

[0150] Here, if the action triggered by the currently executed trigger request is within the action cycle, the above-mentioned target execution component can further determine whether the action triggered by the above-mentioned trigger request to be executed is mutually exclusive with the action triggered by the currently executed trigger request. If they are not mutually exclusive, then according to the above-mentioned trigger request to be executed, call the corresponding action execution interface to handle the trigger event; if they are mutually exclusive, then after the currently executed trigger request is executed, call the corresponding action execution interface to handle the trigger event according to the above-mentioned trigger request to be executed.

[0151] In an embodiment of the present application, the target execution component can obtain the type of action triggered by the trigger request to be executed and the type of action triggered by the trigger request currently being executed, and determine whether the action triggered by the trigger request to be executed is mutually exclusive with the action triggered by the trigger request currently being executed by judging whether the types of the two are consistent. If the type of action triggered by the trigger request to be executed is consistent with the type of action triggered by the trigger request currently being executed, the target execution component judges that the action triggered by the trigger request to be executed is not mutually exclusive with the action triggered by the trigger request currently being executed; otherwise, the target execution component judges that the action triggered by the trigger request to be executed is mutually exclusive with the action triggered by the trigger request currently being executed.

[0152] In addition, the trigger request carries an activation flag, which is used to indicate whether the action triggered by the trigger request is an activation action.

[0153] When the above-mentioned target execution component determines whether the action triggered by the currently executing trigger request is within the action cycle, it can determine whether the action triggered by the currently executing trigger request is an activation action based on the activation identifier carried by the currently executing trigger request. If the action triggered by the currently executing trigger request is an activation action, it is determined that the action triggered by the currently executing trigger request is within the action cycle.

[0154] When the target execution component calls the corresponding action execution interface to process the trigger event, it can obtain the type of action triggered by the trigger request to be executed, and then determine the corresponding action execution interface to be called based on the type, and then call the corresponding action execution interface to process the trigger event.

[0155] In summary, the embodiment of the present application manages the interaction between multiple input devices and the UI by interacting with a plurality of execution components through a management system. Among them, one execution component corresponds to one input device. After receiving the trigger request of the input device, the management system sets the state of the execution component corresponding to the input device to an active state, and sets the state of other execution components to an inactive state, so that only one input device is active (can trigger an event) at the same time, so that the UI only responds to one trigger at the same time. Then, the management system sends the above-mentioned trigger request to the execution component corresponding to the input device. After receiving the trigger request sent by the management system, the execution component caches the trigger request in a preset action queue. In this way, on the one hand, trigger requests with mutually exclusive relationships can be managed to ensure that the action cycles of the two do not overlap. On the other hand, within the action cycle, even if the trigger request is not sent every frame, it can also ensure that the execution component generates a trigger event every frame. In addition, the execution component performs trigger signal collision detection and event processing, and displays the processing results in the UI to ensure that the UI interaction in the XR scene is correct, fast and complete.

[0156] Corresponding to the interaction method of the above embodiment, Figure 7 This is a schematic diagram of the structure of the interactive device provided in the embodiment of the present application. For the convenience of explanation, only the parts related to the embodiment of the present application are shown. Figure 7 A schematic diagram of the structure of an interactive device provided in an embodiment of the present application, the interactive device 70 includes: a receiving module 701, a processing module 702, an acquisition module 703 and a calling module 704. The interactive device here can be the above-mentioned target execution component itself, or a chip or integrated circuit that implements the function of the target execution component. It should be noted here that the division of the receiving module, the processing module, the acquisition module and the calling module is only a division of logical functions, and the two can be physically integrated or independent.

[0157] Among them, the receiving module 701 is used to receive a trigger request, the trigger request is sent by the target input device, the target execution component corresponds to the target input device, the state of the target execution component is an active state, and the state of each execution component remaining among the multiple execution components except the target execution component is an inactive state.

[0158] The processing module 702 is used to cache the trigger request in a preset action queue, and perform a trigger signal collision detection based on the UI after receiving an update instruction.

[0159] The acquisition module 703 is used to acquire a trigger request from the preset action queue as a trigger request to be executed according to a preset order after the trigger signal collision detection.

[0160] The calling module 704 is used to call the corresponding action execution interface to process the trigger event according to the trigger request to be executed, and display the processing result of the action execution interface on the UI.

[0161] In a possible implementation, the calling module 704 is specifically configured to:

[0162] Determine whether the action triggered by the currently executed trigger request is within the action cycle;

[0163] If the action triggered by the currently executed trigger request is not within the action cycle, then according to the to-be-executed trigger request, the corresponding action execution interface is called to process the trigger event.

[0164] In a possible implementation, the calling module 704 is specifically configured to:

[0165] If the action triggered by the trigger request currently being executed is within the action cycle, determining whether the action triggered by the trigger request to be executed is mutually exclusive with the action triggered by the trigger request currently being executed;

[0166] If the action triggered by the trigger request to be executed is not mutually exclusive with the action triggered by the trigger request currently being executed, then according to the trigger request to be executed, calling the corresponding action execution interface to process the trigger event;

[0167] If the action triggered by the to-be-executed trigger request is mutually exclusive with the action triggered by the currently-executed trigger request, then after the currently-executed trigger request is executed, the corresponding action execution interface is called according to the to-be-executed trigger request to process the trigger event.

[0168] In a possible implementation, the trigger request carries an activation flag, where the activation flag is used to indicate whether the action triggered by the trigger request is an activation action.

[0169] The calling module 704 is specifically used for:

[0170] Determining, according to the activation identifier carried by the trigger request currently being executed, whether the action triggered by the trigger request currently being executed is an activation action;

[0171] If the action triggered by the currently executed trigger request is an activation action, it is determined that the action triggered by the currently executed trigger request is within an action cycle.

[0172] In a possible implementation, the calling module 704 is specifically configured to:

[0173] Obtaining the type of the action triggered by the trigger request to be executed and the type of the action triggered by the trigger request currently being executed;

[0174] Determine whether the type of the action triggered by the trigger request to be executed is consistent with the type of the action triggered by the trigger request currently being executed;

[0175] If the type of the action triggered by the to-be-executed trigger request is consistent with the type of the action triggered by the currently-executed trigger request, it is determined that the action triggered by the to-be-executed trigger request is not mutually exclusive with the action triggered by the currently-executed trigger request.

[0176] In a possible implementation, after the trigger signal collision detection, the acquisition module 703 acquires a trigger request from the preset action queue in a preset order as a trigger request to be executed, and is further used to:

[0177] According to the nodes detected by the trigger signal collision with the UI in the previous frame and the nodes detected by the trigger signal collision with the UI in the current frame, the corresponding hover processing interface is called to process the hover event, and the processing result of the hover processing interface is displayed on the UI.

[0178] In a possible implementation, the hover processing interface includes a hover entry interface, a hover stay interface, and a hover end interface;

[0179] The acquisition module 703 is specifically used for:

[0180] Compare the node where the trigger signal collides with the UI in the previous frame with the node where the trigger signal collides with the UI in the current frame;

[0181] According to the comparison result, for a node that is not among the nodes where the trigger signal collides with the user interface in the previous frame but is among the nodes where the trigger signal collides with the user interface in the current frame, calling the hover entry interface to process the hover event;

[0182] According to the comparison result, among the nodes where the trigger signal collides with the user interface in the previous frame and among the nodes where the trigger signal collides with the user interface in the current frame, calling the hovering interface to process the hovering event;

[0183] According to the comparison result, among the nodes where the trigger signal collides with the user interface in the previous frame, but not among the nodes where the trigger signal collides with the user interface in the current frame, the hover end interface is called to process the hover event.

[0184] In a possible implementation, the calling module 704 is specifically configured to:

[0185] Obtain the type of action triggered by the trigger request to be executed;

[0186] Determining a corresponding action execution interface to be called according to the type of action triggered by the trigger request to be executed;

[0187] The corresponding action execution interface is called to process the triggering event.

[0188] In a possible implementation manner, the target execution component interacts with a management system.

[0189] The receiving module 701 is specifically used for:

[0190] Receive the trigger request sent by the management system, wherein the trigger request is received by the management system from the target input device, and the trigger request is used to instruct the management system to set the state of the target execution component to an active state, and to set the state of each execution component remaining among the multiple execution components except the target execution component to an inactive state.

[0191] The device provided in the embodiment of the present application can be used to perform the above Figure 2-Figure 4The technical solution of the method embodiment shown has similar implementation principles and technical effects, and will not be repeated here in the embodiments of the present application.

[0192] Optionally, Figure 8 A schematic diagram of a possible basic hardware architecture of the target execution component described in the present application is provided schematically.

[0193] See also Figure 8 The target execution component includes at least one processor 801 and a communication interface 803. Optionally, it may also include a memory 802 and a bus 804.

[0194] In the target execution component, the number of processors 801 may be one or more. Figure 8 Only one of the processors 801 is shown. Optionally, the processor 801 may be a central processing unit (CPU), a graphics processing unit (GPU) or a digital signal processor (DSP). If the target execution component has multiple processors 801, the types of the multiple processors 801 may be different or the same. Optionally, the multiple processors 801 of the target execution component may also be integrated into a multi-core processor.

[0195] The memory 802 stores computer instructions and data; the memory 802 may store computer instructions and data required to implement the above-mentioned interaction method provided in the present application, for example, the memory 802 stores instructions for implementing the steps of the above-mentioned interaction method. The memory 802 may be any one or any combination of the following storage media: non-volatile memory (e.g., read-only memory (ROM), solid state disk (SSD), hard disk (HDD), optical disk), volatile memory.

[0196] The communication interface 803 can provide information input / output for the at least one processor, and can also include any one or any combination of the following devices: a network interface (eg, Ethernet interface), a wireless network card, and other devices with network access functions.

[0197] Optionally, the communication interface 803 may also be used for the target execution component to perform data communications with other computing devices or terminals.

[0198] Further optional, Figure 8A thick line represents bus 804. Bus 804 can connect processor 801 with memory 802 and communication interface 803. Thus, through bus 804, processor 801 can access memory 802, and can also use communication interface 803 to exchange data with other computing devices or terminals.

[0199] In the present application, the target execution component executes the computer instructions in the memory 802, so that the target execution component implements the above-mentioned interaction method provided in the present application, or enables the target execution component to deploy the above-mentioned interaction device.

[0200] From the perspective of logical function division, for example, Figure 8 As shown, the memory 802 may include a receiving module 701, a processing module 702, an acquisition module 703, and a calling module 704. The inclusion here only refers to the fact that when the instructions stored in the memory are executed, the functions of the receiving module, the processing module, the acquisition module, and the calling module can be realized respectively, without limiting the physical structure.

[0201] The present application provides a computer-readable storage medium, and the computer program product includes computer instructions, and the computer instructions instruct a computing device to execute the above-mentioned interaction method provided by the present application.

[0202] The present application provides a computer program product, comprising computer instructions, wherein the computer instructions are executed by a processor to perform the above interaction method.

[0203] The present application provides a chip, comprising at least one processor and a communication interface, wherein the communication interface provides information input and / or output for the at least one processor. Further, the chip may also include at least one memory, wherein the memory is used to store computer instructions. The at least one processor is used to call and run the computer instructions to execute the above-mentioned interaction method provided by the present application.

[0204] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0205] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0206] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional units.

Claims

1. An interactive method, characterized in that: Applied to a target execution component, the target execution component is one of a plurality of execution components, one execution component corresponds to one input device, the method comprises: receiving a trigger request, wherein the trigger request is sent by a target input device, the target execution component corresponds to the target input device, the state of the target execution component is an active state, the states of the remaining execution components among the multiple execution components except the target execution component are inactive states, and the trigger request includes an identity identifier of the target input device; caching the trigger request in a preset action queue, and after receiving an update instruction, performing a trigger signal collision detection based on a user interface; After the trigger signal collision detection, a trigger request is obtained from the preset action queue as a trigger request to be executed according to a preset order; According to the trigger request to be executed, a corresponding action execution interface is called to process the trigger event, and a processing result of the action execution interface is displayed on the user interface.

2. The method according to claim 1, characterized in that Before calling the corresponding action execution interface to process the trigger event according to the trigger request to be executed, the method further includes: Determine whether the action triggered by the currently executed trigger request is within the action cycle; The calling of a corresponding action execution interface to process a trigger event according to the trigger request to be executed includes: If the action triggered by the currently executed trigger request is not within the action cycle, then according to the to-be-executed trigger request, the corresponding action execution interface is called to process the trigger event.

3. The method according to claim 2, characterized in that After determining whether the action triggered by the trigger request currently being executed is within the action cycle, the method further includes: If the action triggered by the trigger request currently being executed is within the action cycle, determining whether the action triggered by the trigger request to be executed is mutually exclusive with the action triggered by the trigger request currently being executed; The calling of a corresponding action execution interface to process a trigger event according to the trigger request to be executed includes: If the action triggered by the trigger request to be executed is not mutually exclusive with the action triggered by the trigger request currently being executed, then according to the trigger request to be executed, calling the corresponding action execution interface to process the trigger event; If the action triggered by the to-be-executed trigger request is mutually exclusive with the action triggered by the currently-executed trigger request, then after the currently-executed trigger request is executed, the corresponding action execution interface is called according to the to-be-executed trigger request to process the trigger event.

4. The method according to claim 2 or 3, characterized in that: The trigger request carries an activation flag, and the activation flag is used to indicate whether the action triggered by the trigger request is an activation action; The determining whether the action triggered by the trigger request currently being executed is within the action cycle includes: Determining, according to the activation identifier carried by the trigger request currently being executed, whether the action triggered by the trigger request currently being executed is an activation action; If the action triggered by the currently executed trigger request is an activation action, it is determined that the action triggered by the currently executed trigger request is within an action cycle.

5. The method according to claim 3, characterized in that: The determining whether the action triggered by the trigger request to be executed is mutually exclusive with the action triggered by the trigger request currently being executed includes: Obtaining the type of the action triggered by the trigger request to be executed and the type of the action triggered by the trigger request currently being executed; Determine whether the type of the action triggered by the trigger request to be executed is consistent with the type of the action triggered by the trigger request currently being executed; If the type of the action triggered by the to-be-executed trigger request is consistent with the type of the action triggered by the currently-executed trigger request, it is determined that the action triggered by the to-be-executed trigger request is not mutually exclusive with the action triggered by the currently-executed trigger request.

6. The method according to any one of claims 1 to 3, characterized in that After the trigger signal collision detection, before obtaining a trigger request from the preset action queue in a preset order as a trigger request to be executed, the method further includes: Based on the nodes detected by the trigger signal collision with the user interface in the previous frame, and the nodes detected by the trigger signal collision with the user interface in the current frame, the corresponding hover processing interface is called to process the hover event, and the processing result of the hover processing interface is displayed on the user interface.

7. The method according to claim 6, characterized in that The hover processing interface includes a hover entry interface, a hover stay interface and a hover end interface; The method of detecting the node where the trigger signal collides with the user interface in the previous frame and the node where the trigger signal collides with the user interface in the current frame according to the collision of the trigger signal, calling the corresponding hover processing interface to process the hover event includes: Compare the node where the trigger signal collides with the user interface in the previous frame with the node where the trigger signal collides with the user interface in the current frame; According to the comparison result, for a node that is not among the nodes where the trigger signal collides with the user interface in the previous frame but is among the nodes where the trigger signal collides with the user interface in the current frame, calling the hover entry interface to process the hover event; According to the comparison result, among the nodes where the trigger signal collides with the user interface in the previous frame and among the nodes where the trigger signal collides with the user interface in the current frame, calling the hovering interface to process the hovering event; According to the comparison result, among the nodes where the trigger signal collides with the user interface in the previous frame, but not among the nodes where the trigger signal collides with the user interface in the current frame, the hover end interface is called to process the hover event.

8. The method according to any one of claims 1 to 3, characterized in that The calling of a corresponding action execution interface to process a trigger event according to the trigger request to be executed includes: Obtain the type of action triggered by the trigger request to be executed; Determining a corresponding action execution interface to be called according to the type of action triggered by the trigger request to be executed; The corresponding action execution interface is called to process the triggering event.

9. The method according to any one of claims 1 to 3, characterized in that The target execution component interacts with the management system; The receiving a trigger request comprises: Receive the trigger request sent by the management system, wherein the trigger request is received by the management system from the target input device, and the trigger request is used to instruct the management system to set the state of the target execution component to an active state, and to set the state of each execution component remaining among the multiple execution components except the target execution component to an inactive state.

10. An interactive device, characterized in that: Applied to a target execution component, the target execution component is one of a plurality of execution components, one execution component corresponds to one input device, the apparatus comprises: a receiving module, configured to receive a trigger request, wherein the trigger request is sent by a target input device, the target execution component corresponds to the target input device, the state of the target execution component is an active state, the states of the remaining execution components among the multiple execution components except the target execution component are in an inactive state, and the trigger request includes an identity identifier of the target input device; A processing module, used for caching the trigger request in a preset action queue, and performing a trigger signal collision detection based on a user interface after receiving an update instruction; An acquisition module, used for acquiring a trigger request from the preset action queue as a trigger request to be executed according to a preset order after the trigger signal collision detection; The calling module is used to call the corresponding action execution interface to process the trigger event according to the trigger request to be executed, and display the processing result of the action execution interface on the user interface.

11. The device according to claim 10, characterized in that The calling module is specifically used for: Determine whether the action triggered by the currently executed trigger request is within the action cycle; If the action triggered by the currently executed trigger request is not within the action cycle, then according to the to-be-executed trigger request, the corresponding action execution interface is called to process the trigger event.

12. A target execution component, characterized in that: include: processor; Memory; as well as Computer programs; The computer program is stored in the memory and is configured to be executed by the processor, wherein the computer program includes instructions for executing the method according to any one of claims 1 to 9.

13. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and the computer program enables the server to execute the method according to any one of claims 1 to 9.

14. A computer program product, characterized in that The method comprises computer instructions, wherein the computer instructions are executed by a processor to perform the method according to any one of claims 1 to 9.

Images