Mobile carrier cabin interaction method and mobile carrier

Abstract

The invention provides a mobile carrier cabin interaction method and a mobile carrier, and relates to the technical field of new energy automobiles, the method comprises the steps that a first key event signal and a second key event signal sent by an automobile body controller in response to a key trigger event are received, the first key event signal is a signal triggered when a rearview mirror adjusting key is pressed down, and the second key event signal is a signal triggered when a rearview mirror adjusting key is pressed down; the second key event signal is a signal triggered when the direction control key is pressed down; determining whether a knocking condition is met based on the first key event signal and the second key event signal; and if the knocking condition is met, controlling the knocking device to knock the target. By adopting the mobile carrier cabin interaction method and the mobile carrier, the problems of high interaction difficulty and low interaction friendliness in the process of proving Buddha by the user are solved.

Description

Technical Field

[0001] The present application relates to the field of new energy vehicle technology, and more specifically, to a mobile vehicle cockpit interaction method and a mobile vehicle. Background Art

[0002] Decorative ornaments generally refer to small furnishings used to beautify or enhance functionality in homes, offices, cars, and other places. They are typically made of various materials, such as wood, metal, ceramics, glass, and plastic. Buddhist enthusiasts often place Buddhist ornaments in their cars, such as wooden fish and Buddhist beads.

[0003] Currently, users usually complete the process of worshiping Buddha by manually striking the wooden fish. Not only does the user need to hold the hammer in his hand, but he also needs to always pay attention to the position of the hammer and the target. This leads to high interaction difficulty and low interaction friendliness during the user's worship process. Summary of the Invention

[0004] In view of this, the purpose of this application is to provide a mobile vehicle cabin interaction method and a mobile vehicle to solve the problems of high interaction difficulty and low interaction friendliness during the user's worship of Buddha.

[0005] In a first aspect, an embodiment of the present application provides a mobile vehicle cabin interaction method, which is applied to a central gateway of a mobile vehicle, wherein the mobile vehicle is provided with a rearview mirror adjustment key, a direction control key, and a knocking device, including:

[0006] receiving a first key event signal and a second key event signal sent by the vehicle body controller in response to a key trigger event, wherein the first key event signal is a signal triggered when a rearview mirror adjustment key is pressed, and the second key event signal is a signal triggered when a direction control key is pressed;

[0007] Determining whether a tap condition is met based on the first key event signal and the second key event signal;

[0008] If the knocking condition is met, the knocking device is controlled to knock the target.

[0009] Optionally, determining whether the tapping condition is met based on the first key event signal and the second key event signal includes: determining whether the first key event signal and the second key event signal exist at the same time; if only the second key event signal exists, determining that the tapping requirement is met.

[0010] Optionally, determining whether the first key event signal and the second key event signal exist simultaneously includes: determining whether the first key event signal exists; and if the first key event signal does not exist, determining whether the second key event signal exists.

[0011] Optionally, the tapping device includes at least one of the following items: a physical tapping device, a virtual tapping device; the target includes at least one of the following items: a physical target when the tapping device is a physical tapping device, a virtual target when the tapping device is a virtual tapping device.

[0012] Optionally, controlling the knocking device to knock the target includes: determining whether there is a physical knocking device; if there is a physical knocking device, knocking the physical target using the physical knocking device; if there is no physical knocking device, knocking the virtual target using a virtual knocking device.

[0013] Optionally, after controlling the knocking device to knock the target, it also includes: updating the historical knocking times to obtain the latest knocking times, the historical knocking times are used to record all the knocking times before the current historical knocking times are updated starting from the first knock; using the latest knocking times, determine the current knocking times of the mobile vehicle after it is powered on.

[0014] Optionally, determining the current number of knocks after the mobile vehicle is powered on this time includes: determining the current number of knocks based on the difference between the latest number of knocks and the initial number of knocks, where the initial number of knocks is the historical number of knocks obtained when the mobile vehicle is powered on this time.

[0015] Optionally, the method also includes: sending the current number of knocks to the vehicle communication terminal corresponding to the mobile vehicle, so that the vehicle communication terminal uploads the current number of knocks to the cloud platform to synchronize the number of knocks of the mobile vehicle and the mobile terminal device.

[0016] Optionally, the historical number of knocks includes the historical number of physical knocks or the historical number of virtual knocks, and the current number of knocks includes the current number of physical knocks or the current number of virtual knocks.

[0017] In a second aspect, an embodiment of the present application further provides a mobile vehicle, including a vehicle body controller and a central gateway;

[0018] The body controller is configured to detect whether a rearview mirror adjustment key and a direction control key on the mobile vehicle are pressed, and to send a first key event signal to the central gateway when the rearview mirror adjustment key is pressed, and to send a second key event signal to the central gateway when the direction control key is pressed;

[0019] The central gateway is used to execute the steps of the above-mentioned mobile vehicle cabin interaction method.

[0020] The embodiments of the present application bring the following beneficial effects:

[0021] The embodiments of the present application provide a mobile vehicle cockpit interaction method and a mobile vehicle, which can determine whether a knocking condition is met based on a first key event signal and a second key event signal sent by a vehicle body controller, and control a knocking device to knock on a target when the knocking condition is met, thereby realizing the use of an existing automotive electronic control system to complete the Buddha worship operation. Compared with the mobile vehicle cockpit interaction method in the prior art, it solves the problems of high interaction difficulty and low interaction friendliness during the user's Buddha worship process.

[0022] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can be obtained based on these drawings without creative work.

[0024] Figure 1 A flow chart of a mobile vehicle cabin interaction method provided in an embodiment of the present application is shown;

[0025] Figure 2 A schematic flow chart of a method for controlling a striking device according to an embodiment of the present application is shown;

[0026] Figure 3 A structural schematic diagram of a mobile vehicle provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0027] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application for which protection is claimed, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, each other embodiment obtained by those skilled in the art without making creative work falls within the scope of protection of the present application.

[0028] It is worth noting that before the present application was filed, decorative ornaments generally referred to small furnishings used to beautify the environment or increase functionality in places such as homes, offices, and cars, and were usually made of various materials, such as wood, metal, ceramics, glass, and plastic. For Buddhist enthusiasts, they usually place some Buddhist decorations in their cars, such as physical wooden fish and Buddhist beads. Currently, when users worship Buddha, they usually do so by manually striking the wooden fish. This not only requires the user to hold the hammer in their hands, but also requires the user to always pay attention to the position of the hammer and the target. This leads to problems of high interaction difficulty and low interaction friendliness during the user's worship.

[0029] Based on this, an embodiment of the present application provides a mobile vehicle cabin interaction method to reduce the difficulty of interaction during user worship and improve the interaction friendliness.

[0030] See also Figure 1 , Figure 1 This is a flow chart of a mobile vehicle cabin interaction method provided in an embodiment of the present application. Figure 1 As shown, the mobile vehicle cabin interaction method provided by the embodiment of the present application includes:

[0031] Step S101, receiving a first key event signal and a second key event signal sent by a vehicle body controller in response to a key trigger event;

[0032] Step S102, determining whether a tapping condition is satisfied based on the first key event signal and the second key event signal;

[0033] Step S103: If the knocking condition is met, control the knocking device to knock the target.

[0034] The mobile vehicle cabin interaction method provided in the embodiment of the present application can determine whether the knocking conditions are met based on the first key event signal and the second key event signal sent by the vehicle body controller, and control the knocking device to knock on the target when the knocking conditions are met, thereby realizing the use of the existing automotive electronic control system to complete the Buddha worship operation, and solving the problems of high interaction difficulty and low interaction friendliness during the user's Buddha worship process.

[0035] To facilitate understanding of this embodiment, the following takes the mobile vehicle cockpit interaction method applied to the central gateway of the mobile vehicle as an example to illustrate the above exemplary steps provided in the embodiment of the present application. Among them, the mobile vehicle is provided with a rearview mirror adjustment key, a direction control key and a knocking device.

[0036] In step S101 , a first key event signal and a second key event signal sent by a vehicle body controller in response to a key trigger event are received.

[0037] In this step, the mobile vehicle may refer to a movable device that carries people or loads items. As an example, the mobile vehicle may be a new energy vehicle or a freight truck.

[0038] The body controller may refer to BCM (body control module), also known as the body computer.

[0039] The central gateway may refer to a CCU (Connectivity Control Unit).

[0040] A key trigger event may refer to an event in which a key is pressed.

[0041] The first key event signal is a signal triggered when the rearview mirror adjustment key is pressed, and the second key event signal is a signal triggered when the direction control key is pressed.

[0042] The rearview mirror adjustment button is used to start the rearview mirror adjustment, usually a physical adjustment button set on the main driver's door.

[0043] The direction control key is used to adjust the angle of the rearview mirror when the rearview mirror adjustment key is pressed. It is usually located next to the rearview mirror adjustment key on the main driver's door. In other words, if the direction control key is pressed without pressing the rearview mirror adjustment key, the rearview mirror will not move.

[0044] In this embodiment of the present application, the BCM detects in real time whether the mirror adjustment key and the directional control key are pressed. When the BCM detects that the mirror adjustment key and / or the directional control key are pressed, a key trigger event is triggered. At this time, the BCM determines whether the mirror adjustment key and the directional control key are pressed simultaneously. If it is determined that the mirror adjustment key and the directional control key are pressed simultaneously, the vehicle body controller adjusts the mirror based on the specific directional control key pressed. For example, the directional control keys include the "up," "down," "left," and "right" directional control keys. When "up" is pressed, the mirror is rotated upward.

[0045] When the BCM detects that the rearview mirror adjustment key and / or directional control key are pressed, a key trigger event is triggered and the BCM sends a key event signal to the CCU. The key event signal is a CAN signal and includes a first key event signal and a second key event signal. The first key event signal is recorded as rearview_adjust_event, and the second key event signal is recorded as dir_press_event.

[0046] The CCU receives the first key event signal and the second key event signal to perform subsequent processing according to the first key event signal and the second key event signal.

[0047] In step S102 , based on the first key event signal and the second key event signal, it is determined whether a tap condition is satisfied.

[0048] In this step, the tapping condition may refer to a condition that needs to be satisfied when the tapping device is used to tap the target.

[0049] In the implementation of this application, after the CCU receives the first key event signal and the second key event signal, it determines whether the first key event signal and the second key event signal exist at the same time. If the first key event signal does not exist and the second key event signal exists, it is determined that the tapping requirement is met.

[0050] In step S103 , if the tapping condition is met, the tapping device is controlled to tap the target.

[0051] In this step, the knocking device includes at least one of the following items: a physical knocking device, a virtual knocking device; the target includes at least one of the following items: a physical target when the knocking device is a physical knocking device, a virtual target when the knocking device is a virtual knocking device.

[0052] The physical striking device and the physical target can be placed on the center console of the vehicle's cabin. For example, the physical striking device includes a mechanical shaft and a striking stick, and the physical target can be a physical wooden fish, with the striking stick fixed to the mechanical shaft. The virtual striking device and the virtual target can be set up in the vehicle's computer. For example, the virtual striking device can be a virtual striking stick, and the virtual target can be a virtual wooden fish.

[0053] In this embodiment of the present application, if the knocking condition is determined to be met, that is, when the rearview mirror adjustment key is not pressed and the direction control key is pressed, the electronic drive unit drives the mechanical shaft of the physical knocking device to rotate back and forth once, achieving a knocking action on the physical wooden fish, and the knocking time is recorded in the electronic drive unit. At the same time, the vehicle computer can display the knocking animation of the virtual knocking stick striking the virtual wooden fish and the total number of knocks since the mobile vehicle was powered on, i.e., the current knock count.

[0054] Refer to the following Figure 2 To introduce the specific processing process of the central gateway controlling the knocking device.

[0055] Figure 2 FIG. 1 shows a flow chart of a method for controlling a knocking device according to an embodiment of the present application. Figure 2 As shown, the knocking device control method includes:

[0056] Step S201: receiving a first key event signal and a second key event signal.

[0057] The central gateway CCU receives the dir_press_event signal sent by the BCM when the direction control key is pressed and the rearview_adjust_event signal sent by the BCM when the rearview mirror adjustment key is pressed.

[0058] Step S202: Determine whether a first key event signal exists.

[0059] If the first key event signal exists, it means that the rearview mirror adjustment key is pressed. At this time, the knocking device cannot be controlled to knock the target, and the process returns to step S201. If the first key event signal does not exist, it means that the rearview mirror adjustment key is not pressed, and the process returns to step S203.

[0060] Step S203: Determine whether a second key event signal exists.

[0061] If the second key event signal exists, it means that the direction control key is pressed. At this time, the tapping device can be controlled to tap the target, and step S204 is executed; if the second key event signal does not exist, it means that the direction control key is not pressed, and the key event signal detection is continued, and step S201 is returned to execution.

[0062] Step S204: Determine whether there is a physical knocking device.

[0063] Here, communication may be established with the electronic driving unit, and based on a feedback signal from the electronic driving unit, it may be determined whether a physical striking device exists.

[0064] If there is a physical knocking device, step S205 is executed; if there is no physical knocking device, step S207 is executed.

[0065] Step S205: tapping the physical target using the physical tapping device.

[0066] At this time, the central control unit (CCU) sends a physical knock control signal (real_beat_event) to the electronic drive unit. After receiving the real_beat_event, the electronic drive unit drives the mechanical shaft of the physical knock device to rotate back and forth once to perform a knock on the physical target. Then, step S206 is executed.

[0067] Step S206: Update the number of tapping times.

[0068] After executing a knock on the entity target, the electronic drive unit will update the locally recorded historical entity knock count to obtain the latest entity knock count, that is, add one to the historical entity knock count. At the same time, the electronic drive unit will also record the time point of the knock. Among them, the historical entity knock count is the entity knock count recorded before the electronic drive unit updates the entity knock count this time. The historical entity knock count is used to record the total entity knock count from the first entity knock to the current entity knock count. In this way, when the electronic drive unit updates the entity knock count next time, it will use the latest entity knock count as the new historical entity knock count to add one to the historical entity knock count.

[0069] At the same time, the central gateway CCU will periodically obtain the latest physical knock count from the electronic drive unit and use the latest physical knock count to determine the current physical knock count since the mobile vehicle was powered on. Then, the current physical knock count is sent to the vehicle controller IDCU by routing the real_beat_event signal. For example: The CCU determines the current physical knock count based on the difference between the latest physical knock count and the initial physical knock count. The initial physical knock count is the historical physical knock count obtained by the CCU from the electronic drive unit when the mobile vehicle was just powered on.

[0070] Step S207: tapping the virtual target using the virtual tapping device.

[0071] The central control unit (CCU) sends a virtual beat control signal (virtual_beat_event) to the vehicle controller (IDCU). The CCU then updates the locally recorded historical virtual beat count by adding one to the historical virtual beat count to obtain the latest virtual beat count. Upon receiving the virtual_beat_event, the IDCU displays an animation of the virtual beat device striking the virtual target and the current virtual beat count since the vehicle was powered on on the vehicle screen.

[0072] In one example, when the mobile vehicle is powered on, the CCU determines whether an electronic drive unit exists to obtain a historical number of physical knocks as the initial number of physical knocks. If there is no electronic drive unit, the CCU uses the historical number of virtual knocks recorded locally as the initial number of virtual knocks when the mobile vehicle is powered on this time, and determines the current number of virtual knocks based on the difference between the latest number of virtual knocks and the initial number of virtual knocks.

[0073] In one example, the owner of the mobile vehicle also carries a mobile terminal device, such as a mobile phone. In order to synchronize the number of knocks between the mobile vehicle and the mobile terminal device, the current number of knocks can be sent to the vehicle communication terminal (TBOX) corresponding to the mobile vehicle. The TBOX regularly uploads the current number of knocks and the time point of the knock to the cloud platform (TSP). The mobile phone APP can obtain the current number of knocks and time by communicating with the TSP to display the current number of knocks and the business logic related to the current number of knocks on the mobile phone APP. Among them, the current number of knocks includes the current number of physical knocks or the current number of virtual knocks, and the historical number of knocks includes the historical number of physical knocks or the historical number of virtual knocks.

[0074] Based on the same inventive concept, a mobile vehicle corresponding to the mobile vehicle cabin interaction method is also provided in the embodiment of the present application. Since the principle of solving the problem by the mobile vehicle in the embodiment of the present application is similar to the above-mentioned mobile vehicle cabin interaction method in the embodiment of the present application, the implementation of the mobile vehicle can refer to the implementation of the method, and the repeated parts will not be repeated.

[0075] See also Figure 3 , Figure 3 This is a structural diagram of a mobile vehicle provided in an embodiment of the present application. Figure 3 As shown in , the mobile vehicle 300 includes a body controller 310 and a central gateway 320;

[0076] The vehicle body controller 310 is configured to detect whether a rearview mirror adjustment key and a direction control key on the mobile vehicle are pressed, and to send a first key event signal to the central gateway when the rearview mirror adjustment key is pressed, and to send a second key event signal to the central gateway when the direction control key is pressed;

[0077] Central gateway 320 is used to execute the above Figure 1 The steps of the mobile vehicle cabin interaction method in the method embodiment shown are specifically implemented in accordance with the method embodiment and will not be described in detail here.

[0078] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

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

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

[0081] 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.

[0082] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0083] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solutions of the present application, rather than to limit them. The scope of protection of the present application is not limited thereto. Although the present application has been described in detail with reference to the above-mentioned embodiments, those skilled in the art should understand that any person skilled in the art can modify or easily conceive of changes to the technical solutions described in the above-mentioned embodiments within the technical scope disclosed in the present application, or perform equivalent replacements for some of the technical features thereof. These modifications, changes, or replacements do not deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A mobile vehicle cockpit interaction method, characterized in that: A central gateway applied to a mobile vehicle, wherein the mobile vehicle is provided with a rearview mirror adjustment key, a direction control key and a knocking device, including: Receiving a first key event signal and a second key event signal sent by the vehicle body controller in response to a key trigger event, wherein the first key event signal is a signal triggered when the rearview mirror adjustment key is pressed, and the second key event signal is a signal triggered when the direction control key is pressed; Determining whether a tapping condition is met based on the first key event signal and the second key event signal; If the knocking condition is met, the knocking device is controlled to knock the target.

2. The method according to claim 1, characterized in that The determining whether a tapping condition is met based on the first key event signal and the second key event signal includes: Determining whether the first key event signal and the second key event signal exist at the same time; If only the second key event signal exists, it is determined that the tapping requirement is met.

3. The method according to claim 2, characterized in that The determining whether the first key event signal and the second key event signal exist at the same time includes: Determining whether the first key event signal exists; If the first key event signal does not exist, determining whether the second key event signal exists.

4. The method according to claim 1, characterized in that: The knocking device includes at least one of the following items: a physical knocking device, a virtual knocking device; The target includes at least one of the following items: a physical target when the knocking device is a physical knocking device, and a virtual target when the knocking device is a virtual knocking device.

5. The method according to claim 4, characterized in that Controlling the knocking device to knock a target comprises: Determine whether a physical striking device exists; If the physical knocking device exists, knocking the physical target with the physical knocking device; If the physical knocking device does not exist, the virtual knocking device is used to knock on the virtual target.

6. The method according to claim 4, characterized in that After controlling the knocking device to knock the target, the method further includes: The historical tapping times are updated to obtain the latest tapping times, wherein the historical tapping times are used to record the total tapping times from the first tapping to the current update of the historical tapping times; The latest number of knocks is used to determine the current number of knocks of the mobile vehicle after it is powered on.

7. The method according to claim 6, characterized in that The determining the current number of tapping times of the mobile vehicle after it is powered on comprises: The current number of knocks is determined based on the difference between the latest number of knocks and the initial number of knocks, where the initial number of knocks is the historical number of knocks obtained when the mobile vehicle is powered on this time.

8. The method according to claim 6, characterized in that The method further comprises: The current number of knocking times is sent to the vehicle communication terminal corresponding to the mobile vehicle, so that the vehicle communication terminal uploads the current number of knocking times to the cloud platform to synchronize the number of knocking times of the mobile vehicle and the mobile terminal device.

9. The method according to claim 6, characterized in that The historical number of knocks includes the historical number of physical knocks or the historical number of virtual knocks, and the current number of knocks includes the current number of physical knocks or the current number of virtual knocks.

10. A mobile vehicle, characterized in that: The mobile vehicle includes a body controller and a central gateway; The body controller is used to detect whether a rearview mirror adjustment key and a direction control key on the mobile vehicle are pressed, and when the rearview mirror adjustment key is pressed, send a first key event signal to the central gateway, and when the direction control key is pressed, send a second key event signal to the central gateway; The central gateway is used to execute the steps of the mobile vehicle cabin interaction method as described in any one of claims 1 to 9.

Images