Vehicle-mounted electronic tag and control method of vehicle-mounted electronic tag
Patent Information
- Application Number
- CN202611330875.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-31
- Publication Date
- 2026-09-25
AI Technical Summary
[0004]本申请实施例提供了一种车载电子标签及车载电子标签的控制方法,可以有效解决车载电子标签的ETC功能无法按需关闭,DSRC模块长期处于唤醒侦听状态,会持续消耗电池电量,从而导致车载电子标签的功耗过高,车载电子标签内置电池的使用寿命缩短的问题
[0029]本申请实施例与现有技术相比存在的有益效果是:本申请提供的车载电子标签,通过设置开关控制单元向MCU模块发送DSRC使失能状态切换指令,由MCU模块根据该指令确定DSRC模块对应的目标使失能状态,并在目标使失能状态为使能时直接控制DSRC模块使能,在目标使失能状态为失能时获取当前运行场景信息并根据当前运行场景信息判断是否允许DSRC模块失能。由此,一方面实现了DSRC模块的按需启停,使得用户在不需要使用ETC功能时能够主动关闭DSRC模块,避免DSRC模块长期处于唤醒侦听状态,从而降低了车载电子标签的功耗,延长了车载电子标签内置电池的使用寿命;另一方面MCU模块在关闭DSRC模块之前先获取当前运行场景信息并据此判断是否允许关闭,避免了在不适宜关闭的场景下因关闭DSRC模块而影响正常收费,保障了收费的准确性与安全性。
Smart Images

Figure CN122825201A_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the field of vehicle-mounted electronic tag technology, and particularly relates to a vehicle-mounted electronic tag and a control method for the vehicle-mounted electronic tag. Background Technology
[0002] The On-Board Unit (OBU) is the core on-board device in the Electronic Toll Collection (ETC) system. OBUs are typically installed on the vehicle's windshield and communicate with the Roadside Unit (RSU) via microwave through the DSRC module within the OBU to achieve vehicle identification, route information writing, and toll deduction. Currently, the ETC function of mainstream OBUs is continuously enabled after factory activation, with the DSRC module always in standby mode, constantly detecting wake-up signals from the RSU to ensure normal transaction processing when the vehicle passes through toll booths.
[0003] In related technologies, because the ETC function of the vehicle electronic tag cannot be turned off as needed, the DSRC module is in a wake-up listening state for a long time, which will continuously consume battery power, resulting in excessive power consumption of the vehicle electronic tag and shortening the lifespan of the built-in battery of the vehicle electronic tag. Summary of the Invention
[0004] This application provides an in-vehicle electronic tag and a control method for the in-vehicle electronic tag, which can effectively solve the problems that the ETC function of the in-vehicle electronic tag cannot be turned off as needed, the DSRC module is in a wake-up listening state for a long time, which will continuously consume battery power, resulting in excessive power consumption of the in-vehicle electronic tag and shortened lifespan of the built-in battery of the in-vehicle electronic tag.
[0005] In a first aspect, embodiments of this application provide an in-vehicle electronic tag, including: a microcontroller unit (MCU) module, a DSRC module, and a switch control unit; the DSRC module can be independently enabled or disabled; the switch control unit is used to send a DSRC disable state switching command to the MCU module; the MCU module is used to: in response to the DSRC disable state switching command, determine the target disable state corresponding to the DSRC module; when the target disable state is enabled, control the DSRC module to be enabled; when the target disable state is disabled, obtain the current operating scenario information of the vehicle where the in-vehicle electronic tag is located, and determine whether the DSRC module is allowed to be disabled based on the current operating scenario information.
[0006] In another possible implementation of the first aspect, the aforementioned vehicle-mounted electronic tag also includes a power module, wherein the DSRC module failure refers to cutting off the power supply path between the power module and the DSRC module, or the DSRC module failure refers to shutting down all radio frequency functions of the DSRC module through control commands.
[0007] Optionally, in another possible implementation of the first aspect, the aforementioned MCU module is specifically used for: If the current scenario for the vehicle is determined to be a scenario where shutdown is prohibited based on the current operating scenario information, the DSRC disable state switching command is intercepted while the DSRC module remains enabled. If the current scenario is determined not to be a scenario where shutdown is prohibited based on the current operating scenario information, the DSRC module is disabled.
[0008] Optionally, in another possible implementation of the first aspect, the aforementioned current operating scenario information includes high-speed entrance / exit status information; correspondingly, the aforementioned MCU module is also used for: If the status information at the highway entrance / exit is the preset status information, it is determined that the current scenario belongs to the prohibited closure scenario. The preset status information indicates that the vehicle entered the highway without paying. If the status information at the highway entrance / exit is not the preset status information, it is determined that the current scenario does not belong to the scenario where closing is prohibited.
[0009] Optionally, in another possible implementation of the first aspect, the aforementioned MCU module is specifically used for: When the DSRC disable state switching command is changed to the DSRC enable command, the target disable state is set to enable. When the DSRC disables the disability state switching command, the target is determined to be disabled.
[0010] Optionally, in another possible implementation of the first aspect, the aforementioned vehicle-mounted electronic tag further includes a storage module for storing the current disabled state of the DSRC; correspondingly, the aforementioned MCU module is specifically used for: In response to the DSRC disable state switching command, obtain the current disable state of DSRC; Given that the DSRC currently sets the disabled state to enabled, determine that the target sets the disabled state to disabled. If the DSRC currently disables the target, determine whether the target disables the target and enables it.
[0011] Optionally, in another possible implementation of the first aspect, the aforementioned MCU module is further used for: In response to a change in the disabled state of the DSRC module, update the current disabled state of the DSRC stored in the storage module.
[0012] Optionally, in another possible implementation of the first aspect, the aforementioned storage module is also used to store information about the current running scenario.
[0013] Optionally, in another possible implementation of the first aspect, the aforementioned switch control unit includes a human-machine interaction unit and / or a wireless communication unit; The aforementioned human-computer interaction unit is used to collect user operations in the human-computer interaction unit, generate DSRC to switch the disability state, and send the DSRC to switch the disability state to the MCU module. The aforementioned wireless communication unit is used to communicate with external control devices, receive DSRC disable state switching instructions issued by external control devices, and forward the DSRC disable state switching instructions to the MCU module.
[0014] Optionally, in another possible implementation of the first aspect, where the switch control unit includes a wireless communication unit, the aforementioned MCU module is further configured to: Generate a first return instruction corresponding to the DSRC disable state switching instruction issued by the external control device, and send the first return instruction to the wireless communication unit. The first return instruction carries the response result of the DSRC disable state switching instruction. Accordingly, the aforementioned wireless communication unit is also used for: Receive the first return command sent by the MCU module and forward the first return command to the external control device.
[0015] Optionally, in another possible implementation of the first aspect, the aforementioned wireless communication unit is further configured to: Receive the DSRC disable status query command issued by the external control device and forward the DSRC disable status query command to the MCU module; Accordingly, the aforementioned MCU module is also used for: Receive the DSRC disabled status query command forwarded by the wireless communication unit; Generate a second return instruction corresponding to the DSRC disable status query instruction, and send the second return instruction to the wireless communication unit, wherein the second return instruction carries the current DSRC disable status; Accordingly, the aforementioned wireless communication unit is also used for: Receive the second return command sent by the MCU module and forward the second return command to the external control device.
[0016] Secondly, embodiments of this application provide a control method for an on-board electronic tag, applied to the MCU module in the on-board electronic tag as described above. The on-board electronic tag also includes a DSRC module and a switch control unit. Accordingly, the method includes: responding to a DSRC disable state switching command sent by the switch control unit, determining the target disable state corresponding to the DSRC module; when the target disable state is enabled, controlling the DSRC module to be enabled; when the target disable state is disabled, obtaining the current operating scenario information of the vehicle where the on-board electronic tag is located, and determining whether the DSRC module is allowed to be disabled based on the current operating scenario information.
[0017] Optionally, in one possible implementation of the second aspect, the vehicle-mounted electronic tag further includes a power module, wherein the DSRC module failure refers to cutting off the power supply path between the power module and the DSRC module; or, the DSRC module failure refers to shutting down all radio frequency functions of the DSRC module through control commands.
[0018] Optionally, in another possible implementation of the second aspect, the above-mentioned determination of whether to allow the DSRC module to disable based on the current operating scenario information includes: If the current scenario for the vehicle is determined to be a scenario where shutdown is prohibited based on the current operating scenario information, the DSRC disable state switching command is intercepted while the DSRC module remains enabled. If the current scenario for the vehicle is determined to be a scenario where shutdown is prohibited based on the current operating scenario information, the DSRC module is disabled.
[0019] Optionally, in another possible implementation of the second aspect, the aforementioned current operating scenario information includes highway entrance / exit status information; correspondingly, the aforementioned method further includes: If the status information at the highway entrance / exit is the preset status information, it is determined that the current scenario belongs to the prohibited closure scenario. The preset status information indicates that the vehicle entered the highway without paying. If the status information at the highway entrance / exit is not the preset status information, it is determined that the current scenario does not belong to the scenario where closing is prohibited.
[0020] Optionally, in another possible implementation of the second aspect, the determination of the target disabling state corresponding to the DSRC module in response to the DSRC disabling state switching command sent by the switch control unit includes: When the DSRC disable state switching command is changed to the DSRC enable command, the target disable state is set to enable. When the DSRC disables the disability state switching command, the target is determined to be disabled.
[0021] Optionally, in another possible implementation of the second aspect, the vehicle-mounted electronic tag further includes a storage module for storing the current DSRC incapacitated state; correspondingly, determining the target incapacitated state corresponding to the DSRC module in response to the DSRC incapacitated state switching command sent by the switch control unit includes: In response to the DSRC disable state switching command, obtain the current disable state of DSRC; Given that the DSRC currently sets the disabled state to enabled, determine that the target sets the disabled state to disabled. If the DSRC currently disables the target, determine whether the target disables the target and enables it.
[0022] Optionally, in another possible implementation of the second aspect, the above method further includes: In response to a change in the disabled state of the DSRC module, update the current disabled state of the DSRC stored in the storage module.
[0023] Optionally, in another possible implementation of the second aspect, when the switch control unit includes a wireless communication unit, the wireless communication unit is used to communicate with an external control device, receive a DSRC disable state switching command issued by the external control device, and forward the DSRC disable state switching command to the MCU module; correspondingly, the above method further includes: Generate a first return instruction corresponding to the DSRC disable state switching instruction issued by the external control device, wherein the first return instruction carries the response result of the DSRC disable state switching instruction; Send a first return command to the wireless communication unit so that the wireless communication unit forwards the first return command to the external control device.
[0024] Optionally, in another possible implementation of the second aspect, where the switch control unit includes a wireless communication unit, the wireless communication unit is used to communicate with an external control device; correspondingly, the above method further includes: Receive the DSRC disable status query command forwarded by the wireless communication unit, wherein the DSRC disable status query command is issued to the wireless communication unit by the external control device; Generate a second return instruction corresponding to the DSRC incapacitance status query instruction, wherein the second return instruction carries the current DSRC incapacitance status; A second return command is sent to the wireless communication unit so that the wireless communication unit forwards the second return command to the external control device.
[0025] Thirdly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the control method for the vehicle-mounted electronic tag as described above.
[0026] As an example, the processor in this application embodiment can be the MCU module in the aforementioned vehicle-mounted electronic tag.
[0027] Fourthly, embodiments of this application provide a computer program product that, when run on a processor, causes the processor to execute the control method for the vehicle-mounted electronic tag as described above.
[0028] As an example, the processor in this application embodiment can be the MCU module in the aforementioned vehicle-mounted electronic tag.
[0029] The beneficial effects of this application's embodiments compared to existing technologies are as follows: The vehicle-mounted electronic tag provided in this application sends a DSRC disable state switching command to the MCU module through a switch control unit. The MCU module determines the target disable state corresponding to the DSRC module based on this command. When the target disable state is enabled, it directly controls the DSRC module to be enabled. When the target disable state is disabled, it acquires the current operating scenario information and determines whether to allow the DSRC module to disable based on the current operating scenario information. Therefore, on the one hand, it realizes on-demand start and stop of the DSRC module, allowing users to actively turn off the DSRC module when they do not need to use the ETC function, avoiding the DSRC module being in a wake-up listening state for a long time, thereby reducing the power consumption of the vehicle-mounted electronic tag and extending the lifespan of the vehicle-mounted electronic tag's built-in battery. On the other hand, before turning off the DSRC module, the MCU module acquires the current operating scenario information and determines whether to allow turning it off, avoiding the impact on normal toll collection due to turning off the DSRC module in scenarios where it is not suitable for turning it off, thus ensuring the accuracy and security of toll collection. Attached Figure Description
[0030] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0031] Figure 1 This is a schematic diagram of the structure of an on-board electronic tag provided in one embodiment of this application; Figure 2 This is a schematic diagram of the structure of an in-vehicle electronic tag provided in another embodiment of this application; Figure 3This is a schematic diagram of the structure of an in-vehicle electronic tag provided in another embodiment of this application; Figure 4 This is a schematic diagram of the structure of an in-vehicle electronic tag provided in another embodiment of this application; Figure 5 This is a schematic diagram of the structure of a data frame provided in an embodiment of this application; Figure 6 This is a schematic diagram of the structure of a data field provided in an embodiment of this application; Figure 7 This is a schematic diagram of the structure of an in-vehicle electronic tag provided in another embodiment of this application; Figure 8 This is a flowchart illustrating the control method for an on-board electronic tag provided in an embodiment of this application. Detailed Implementation
[0032] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.
[0033] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.
[0034] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.
[0035] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."
[0036] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.
[0037] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.
[0038] The following description, with reference to the accompanying drawings, details the vehicle-mounted electronic tag, the control method for the vehicle-mounted electronic tag, the storage medium, and the computer program provided in this application.
[0039] Figure 1 A schematic diagram of the structure of an in-vehicle electronic tag provided in an embodiment of this application is shown.
[0040] like Figure 1 As shown, the vehicle-mounted electronic tag includes: an MCU module, a DSRC module, and a switch control unit; wherein, the DSRC module can be independently enabled or disabled; the switch control unit is used to send a DSRC disable state switching command to the MCU module; the MCU module is used to: in response to the DSRC disable state switching command, determine the target disable state corresponding to the DSRC module; when the target disable state is enabled, control the DSRC module to be enabled; when the target disable state is disabled, obtain the current operating scenario information of the vehicle where the vehicle-mounted electronic tag is located, and determine whether the DSRC module is allowed to be disabled based on the current operating scenario information.
[0041] The MCU module, in this context, refers to the control core of the vehicle-mounted electronic tag. It is responsible for receiving and processing instructions from the switch control unit, controlling the enabling or disabling of the DSRC module, acquiring scene information, and making logical judgments. For example, the MCU module can be a low-power embedded microcontroller, which may integrate a processor core, random access memory (RAM), read-only memory (ROM), and various communication interfaces, but is not limited to these, to achieve the aforementioned functions.
[0042] The DSRC module can refer to the radio frequency transceiver component in the vehicle electronic tag that is responsible for microwave communication with the roadside unit (RSU) to realize data interaction in the ETC transaction process, including vehicle identification, route information writing and toll deduction, but it is not limited to this.
[0043] In the embodiments of this application, the DSRC module is characterized by its ability to be independently enabled or disabled. The term "independent" means that the enabling or disabling state of the DSRC module can be controlled independently of other modules in the vehicle electronic tag. That is, the MCU module can independently turn on or off the power supply or radio frequency function of the DSRC module while keeping other modules (such as the switch control unit, the ESAM module mentioned later) working normally, without having to power off or disassemble the entire vehicle electronic tag.
[0044] When the DSRC module is enabled, it is in normal working condition. Its radio frequency transceiver circuit is powered on and can detect the wake-up signal sent by the RSU in real time. After receiving a valid wake-up signal, it establishes a communication link with the RSU and completes the interaction of ETC transaction data.
[0045] When the DSRC module is disabled, it no longer detects the wake-up signal sent by the RSU and cannot communicate with the RSU, so the ETC function is temporarily disabled.
[0046] As one possible implementation, DSRC module disabling can mean cutting off the power supply path between the power module and the DSRC module; or, DSRC module disabling can mean shutting down all radio frequency functions of the DSRC module through control commands.
[0047] As an example, such as Figure 2As shown, the vehicle-mounted electronic tag also includes a power module, which supplies power to the various modules within the tag. The DSRC module can be disabled by cutting off the power supply from the power module, completely de-energizing the DSRC module. In this implementation, the MCU module can control the power supply path between the DSRC module and the power module to completely de-energize the DSRC module. For example, a controllable switch can be set between the power module and the DSRC module, and the control terminal of this switch can be connected to a General Purpose Input Output (GPIO) pin of the MCU module. When the MCU module determines that the DSRC module can be disabled, it can output a shutdown signal to the controllable switch via the GPIO pin. The controllable switch opens, the power supply to the DSRC module is cut off, and the DSRC module completely stops working and no longer consumes battery power. When it is necessary to re-enable the DSRC module, the MCU module can output an enable signal to the controllable switch via the GPIO pin. The controllable switch closes, the DSRC module resumes power supply, and the DSRC module powers on and enters normal operation (i.e., the enabled state).
[0048] Understandably, disabling the DSRC module by cutting off the power supply results in a significant power optimization effect, as the DSRC module is completely powered off during the disabling period and consumes no power. This can maximize the lifespan of the built-in battery of the vehicle electronic tag.
[0049] As an example, disabling a DSRC module can be achieved by shutting down all RF functions of the DSRC module via control commands. In this implementation, the MCU module can instruct the DSRC module to disable all its RF functions without cutting off its power supply. For example, the MCU module and the DSRC module can have a communication interface (such as a Serial Peripheral Interface (SPI) or a Universal Asynchronous Receiver / Transmitter (UART), but not limited to these). When the MCU module determines that it needs to disable the DSRC module, it can send an RF shutdown command to the DSRC module through this communication interface. After receiving the command, the DSRC module can shut down its internal RF transceiver circuitry and RF signal processing circuitry, stopping the transmission and reception of RF signals. At this time, the DSRC module no longer detects the wake-up signal from the RSU and cannot communicate with the RSU; the ETC function is temporarily disabled. However, the DSRC module's digital interface circuitry (such as the interface communicating with the MCU module) can remain operational to receive subsequent RF enable commands from the MCU module. When the DSRC module needs to be re-enabled, the MCU module can send an RF enable command to the DSRC module through the communication interface. The DSRC module will then re-enable the RF transceiver circuit and the RF signal processing circuit, restoring normal operation.
[0050] Understandably, disabling the DSRC module through the disabled radio frequency function reduces the power consumption of the vehicle electronic tag and extends the lifespan of its built-in battery, as the RF section of the DSRC module no longer consumes power during the disabled period. Furthermore, since the digital interface circuit remains powered, the MCU module does not need to wait for the DSRC module to power on again; it only needs to send an RF enable command to restore the RF function, resulting in a faster response time.
[0051] It should be noted that either of the two disabling methods described above can be selected; and the two disabling methods listed above are merely illustrative and should not be considered as limitations on this application. In actual use, one of the two methods can be selected based on the hardware design of the DSRC module, power consumption optimization goals, and response speed requirements, or other energy-efficient methods can be selected. This application does not limit this. The operating scenario information can be obtained in various ways, such as information written by the roadside unit when the vehicle passes through the ETC entrance (e.g., entrance status information), or information obtained by the vehicle-mounted electronic tag through other means (e.g., location information obtained based on the positioning module). This application does not specifically limit this. The specific content of the current operating scenario information and how the MCU module uses this information for disabling judgment will be further explained in subsequent embodiments.
[0052] As one possible implementation, such as Figure 3 As shown in the embodiments of this application, the vehicle-mounted electronic tag may also include a storage module.
[0053] The storage module can be used to store the current operating scenario information of the vehicle where the on-board electronic tag is located. This current operating scenario information can be used to characterize the current operating scenario or state of the vehicle. For example, the storage module can use non-volatile memory (electrically erasable programmable read-only memory, EEPROM, flash memory, etc.) to ensure that the data of the on-board electronic tag is not lost after power failure.
[0054] In this embodiment, the storage module can be implemented in various physical forms, as long as it can non-volatilely store the current operating scenario information. The storage module can reuse the existing embedded secure access module (ESAM) in the vehicle electronic tag, or it can be a separately set storage chip.
[0055] As one possible implementation, when the vehicle-mounted electronic tag includes a storage module, the storage module can be used to store operational scenario information.
[0056] In some implementations, the ESAM module is the security core of the on-board electronic tag, integrating a non-volatile storage area and an encryption processing unit to securely store vehicle identity information, key data, transaction records, and toll-related documents. For example, in an ETC system, the ESAM module can store files conforming to relevant standards, which may contain vehicle entry / exit status information. Since the ESAM module itself has non-volatile data storage capabilities, this application can store the current operating scenario information in the existing storage area of the ESAM module, such as directly using the entry / exit status information from relevant standard files in the ESAM as the current operating scenario information, without the need for an additional independent storage chip, which helps reduce hardware costs and simplify circuit design.
[0057] In other implementations, the storage module can also be a storage chip independent of the ESAM module, such as EEPROM or flash memory, connected to the MCU module via a communication interface, and dedicated to storing current operating scenario information (it can also be used to store other data). By setting up a separate storage module, the storage resources of the ESAM module can be avoided, resulting in faster read and write speeds.
[0058] It should be noted that, regardless of whether the ESAM module is reused or a separate storage chip is set up, as long as the storage module can non-volatilely store the current running scene information and provide it to the MCU module for reading when needed, this application does not limit the specific implementation method of the storage module.
[0059] The switch control unit refers to a functional unit in an on-board electronic tag used to receive user operations or external commands. Its function is to send a DSRC (Disabled Controller Recognition) switching command to the MCU (Microcontroller Unit) module, triggering the MCU module to perform enable or disable operations on the DSRC module. The switch control unit can be implemented in various forms, such as a physical switch or button set on the on-board electronic tag itself, and / or a communication module (such as a Bluetooth module, Near Field Communication (NFC) module, etc.) for communicating with external control devices such as mobile phones.
[0060] As one possible implementation, the switch control unit may include a human-machine interface unit and / or a wireless communication unit. The human-machine interface unit may be mounted on the vehicle-mounted electronic tag and used to collect user operations within the human-machine interface unit to generate a DSRC (Disability and Restriction Control Controller) command for switching the disabled state, and then send the DSRC command to the MCU (Microcontroller Unit). The wireless communication unit may be used to communicate with external control devices, receive DSRC commands for switching disabled states from external control devices, and forward the DSRC commands to the MCU module.
[0061] As an example, the human-computer interaction unit may include, but is not limited to, at least one of a physical switch, a voice interaction module, a motion-sensing interaction module, and a graphical user interface. The wireless communication unit may include, but is not limited to, at least one of a Bluetooth module and an NFC module.
[0062] In this embodiment, the switch control unit of the vehicle-mounted electronic tag may include only a human-machine interaction unit, only a wireless communication unit, or both. When the switch control unit includes a human-machine interaction unit, the human-machine interaction unit can be implemented using at least one (or other types) of a physical switch, a voice interaction module, a motion-sensing interaction module, and a graphical user interface. For example, the human-machine interaction unit can be implemented using only a physical switch, or simultaneously using a physical switch, a voice interaction module, a motion-sensing interaction module, and a graphical user interface. That is, the vehicle-mounted electronic tag simultaneously includes a physical switch, a voice interaction module, a motion-sensing interaction module, and a graphical user interface, allowing the user to disable the DSRC module through the vehicle-mounted electronic device itself. When the switch control unit includes a wireless communication unit, the wireless communication unit can be implemented using at least one (or other types) of a Bluetooth module and an NFC module. For example, the human-machine interaction unit can be implemented using only a Bluetooth module, only an NFC module, or simultaneously using both Bluetooth and NFC modules. That is, the vehicle-mounted electronic tag simultaneously includes both Bluetooth and NFC modules, used to disable the DMRS module through an external control device.
[0063] For example, such as Figure 4 The diagram shown illustrates the structure of another vehicle-mounted electronic tag provided in this application, including an MCU module, a DSRC module, a storage module, a physical switch, a Bluetooth module, and an NFC module. In other words, the switch control unit simultaneously includes a human-machine interface unit and a wireless communication unit. The human-machine interface unit is implemented through a physical switch, and the wireless communication unit is implemented through the Bluetooth and NFC modules, enabling external control devices to connect to the DSRC module of the disabled vehicle-mounted electronic tag via Bluetooth or NFC.
[0064] It should be noted that in actual use, any one or more combinations of the above-listed (or other feasible methods not listed) can be selected as the switch control unit. That is, one or more switch control units can be set in the vehicle electronic tag according to actual needs and specific application scenarios to provide users with diverse access points and methods to disable the DSRC module. This application embodiment does not limit this.
[0065] The DSRC disable state switching instruction can be a command sent by the switch control unit to the MCU module. This instruction instructs the MCU module to switch the state of the DSRC module. "Disabling state switching" refers to the transition between an enabled and disabled state. The DSRC disable state switching instruction carries or implicitly indicates the target state information (enabled or disabled state) that the user expects the DSRC module to achieve. After receiving the DSRC disable state switching instruction, the MCU module can parse the target state and perform corresponding operations accordingly.
[0066] The target disabled state can refer to the state that the MCU module determines based on the DSRC disabled state switching instruction, which is the state that the user expects the DSRC module to reach. This includes both enabled and disabled states. An enabled state can mean that the DSRC module is working normally and can communicate with the RSU; a disabled state can mean that the DSRC module is turned off or disabled and cannot communicate with the RSU.
[0067] In this embodiment of the application, DSRC enables the type of disability state switching command to be related to the type of switch control unit.
[0068] As one possible implementation, depending on the type of switch control unit, the DSRC can make the disability state switching command include the following two types: The first type: The DSRC disable state switching instruction explicitly carries the target disable state, that is, the DSRC disable state switching instruction can include DSRC enable instruction and DSRC disable instruction.
[0069] As an example, the DSRC enables the disability state switching instruction to carry explicit "on" or "off" semantics. After receiving the instruction, the MCU module can directly determine the target to be disabled.
[0070] For example, for wireless communication units (such as Bluetooth modules and NFC modules), the DSRC disable state switching command issued by an external control device (such as a mobile application) can carry a clear command code in the data field—for example, the DSRC enable command corresponds to the first content (such as 0x01), and the DSRC disable command corresponds to the second content (such as 0x02). The MCU module can directly determine whether the target disable state is enabled or disabled by parsing the data field.
[0071] For example, for physical switches, when the physical switch is a toggle switch, slide switch, push switch, rocker switch, or other switch with two distinct positions, different positions can correspond to different output level signals—for example, a high level is output when toggled to the "on" position, and a low level is output when toggled to the "off" position; or vice versa. Alternatively, for physical switches without distinct positions (such as touch switches), the physical switch can also output high and low levels intermittently, that is, a high level is output when the user touches the physical switch for the first time (e.g., a high level represents on), and a low level is output when the physical switch is touched again (e.g., a low level represents off), and so on. The high and low levels output by the physical switch can be used as DSRC disable switching instructions. The MCU module can determine the user's desired disable state (enabled or disabled) by detecting the high and low levels.
[0072] For example, for the voice interaction module, the user can directly say "Turn on ETC" or "Turn off ETC" via voice command (this is just an example, and other similar commands are also possible). The voice interaction module can generate the corresponding DSRC turn-on command or DSRC turn-off command based on the user's voice using voice recognition technology (that is, in this case, the DSRC disability switching command explicitly carries the target disability state).
[0073] For example, in a motion-sensing interaction module, when the module can recognize different types of user actions (such as different gestures, different tap counts, or different waving directions) and encode different types of actions into different instructions, the instruction clearly carries the target of disabling the user. For instance, the motion-sensing interaction module can be implemented using one or more of an accelerometer, gyroscope, infrared sensor, or radar sensor (it can also be implemented using other modules with motion-sensing capabilities; this application embodiment does not limit this). When a user triggers an activation instruction by performing a first type of action (such as waving upwards) or a deactivation instruction by performing a second type of action (such as waving downwards), the motion-sensing interaction module can recognize different types of actions as different instruction codes. For example, recognizing an upward wave can generate a DSRC activation instruction, and recognizing a downward wave can generate a DSRC deactivation instruction.
[0074] For example, in a graphical user interface (GUI), such as a touchscreen display, a virtual "Enable ETC" button and a virtual "Deactivate ETC" button may be displayed (for example only). When the user clicks the "Enable ETC" button, the GUI generates a DSRC activation command and sends it to the MCU module; when the user clicks the "Deactivate ETC" button, the GUI generates a DSRC deactivation command and sends it to the MCU module.
[0075] Understandably, since the DSRC disable switching instruction includes both DSRC enable and DSRC disable instructions, it inherently carries the semantic information of "enable" or "disable". Therefore, after the MCU module receives the DSRC disable switching instruction, it can directly determine whether the target disable state is enabled or disabled by parsing the instruction type (i.e., determining whether it is a DSRC enable instruction or a DSRC disable instruction).
[0076] The second type: The DSRC disable switching instruction does not explicitly carry the target disable state, but only serves as a trigger signal. The MCU module determines the target disable state on its own.
[0077] As one possible implementation, when the vehicle-mounted electronic tag includes a storage module, the current DSRC disabled state can be stored in the storage module. Upon receiving a DSRC disabled state switching command, the target disabled state can be determined based on the stored current DSRC disabled state. In this case, the DSRC disabled state switching command can be a trigger signal, which does not carry "on" or "off" semantic information. After receiving the DSRC disabled state switching command, the MCU module can obtain the current DSRC disabled state stored in the storage module and determine the target disabled state based on the current state, thus achieving state reversal. If the current disabled state is enabled, the target disabled state is disabled; if the current disabled state is disabled, the target disabled state is enabled.
[0078] For example, for a physical switch, when the physical switch is a push-button switch, tactile switch, or other switch without a position holding function, the level signal generated by each user press operation can be the same (e.g., all generate a high-level pulse or a low-level pulse). This level signal itself does not distinguish between "on" and "off", and this level signal can be the DSRC disable state switching command. Each time the MCU module detects this trigger signal (i.e., after obtaining the DSRC disable state switching command), it can read the current DSRC disable state stored in the storage module and determine the target disable state as the opposite of the current disable state.
[0079] For example, for the voice interaction module, when a user issues a voice command such as "switch ETC status" or "flip ETC" without explicitly indicating whether it is turned on or off, the voice interaction module generates the same trigger signal and sends it to the MCU module. After receiving the trigger signal, the MCU module also determines the target disabled state (flip) based on the current disabled state of DSRC.
[0080] For example, in the motion-sensing interaction module, the user can trigger a sensing signal through a specific action (such as tapping the vehicle electronic tag casing, waving the hand across the sensing area, etc.). The motion-sensing interaction module can convert the sensing signal into a trigger signal (i.e., the DSRC disable state switching command) and send it to the MCU module. Since the trigger signal itself does not distinguish between "on" and "off", the MCU module also needs to determine the target disable state (flip) itself based on the current disable state of the DSRC.
[0081] For example, for a graphical user interface, when a user clicks the "Switch ETC Status" virtual button displayed on the screen, the graphical user interface can generate a trigger signal (i.e., the DSRC disable state switching instruction) and send it to the MCU module. The trigger signal itself does not distinguish between "on" or "off". The MCU module can also determine the target disable state (flip) on its own according to the current disable state of the DSRC.
[0082] It should be noted that the two types of DSRC incapacitance switching commands mentioned above are not mutually exclusive. An on-board unit (OIN) can support one or more types of commands depending on the type of switch control unit it is configured with. For example, an OIN equipped with both a toggle switch and a Bluetooth module can receive commands from either the toggle switch (type 1) or the Bluetooth module (type 1). As another example, an OIN equipped with both a push-button switch and a Bluetooth module can receive trigger signals from the push-button switch (type 2) that do not explicitly indicate an incapacitance target, which the MCU module then automatically toggles based on the current incapacitance state. It can also receive commands from the Bluetooth module that explicitly indicate an incapacitance target (type 1). For different types of DSRC incapacitance switching commands, the MCU module can employ different methods for determining the target incapacitance state.
[0083] In this embodiment, after receiving the DSRC disable state switching instruction, the MCU module can first determine the target disable state corresponding to the DSRC module. As mentioned above, the method of determining the target disable state depends on the specific form of the DSRC disable state switching instruction. After determining the target disable state, the MCU module determines whether the target disable state is enabled or disabled, and executes different processing branches accordingly.
[0084] If the target is determined to be in an enabled state instead of a disabled state, the MCU module can directly control the DSRC module to be enabled. In this branch, the MCU module does not need to perform additional condition checks because enabling the DSRC module will not negatively affect the normal operation of the toll collection system. After the DSRC module switches from a disabled state to an enabled state, it can normally receive RSU signals and complete transactions without causing path information to be unable to be written or billing errors. For example, the MCU module can restore power supply by sending an enable signal to the DSRC module's power management circuit, or restore radio frequency function by sending an RF enable control signal to the DSRC module.
[0085] If the target is determined to be disabled, the MCU module may not immediately execute the disabling operation, but first obtain the current operating scenario information (which can be read from the storage module or calculated in real time from relevant data; this application embodiment does not limit this). This current operating scenario information characterizes the vehicle's current operating scenario or state, and its specific content may include, but is not limited to, whether the vehicle has entered a highway or is currently within a highway network. After obtaining the current operating scenario information, the MCU module can determine whether to allow the DSRC module to be disabled. When the vehicle is in certain specific scenarios (such as having entered a highway but not yet left), even if the switch control unit initiates a command to disable the DSRC, the MCU module will refuse to execute the operation, thereby preventing the DSRC module from being accidentally shut down in necessary scenarios. If the MCU module determines that the DSRC module can be disabled, it can control the DSRC module to be disabled. The disabling operation may include cutting off the power supply path between the power module and the DSRC module, or disabling all radio frequency functions of the DSRC module through control commands. The specific implementation method has been described in the DSRC module section above and will not be repeated here. If the MCU module determines that disabling the DSRC module is not allowed, it can intercept the DSRC's disable state switching command and keep the DSRC module enabled. "Interception" means that the MCU module refuses to execute the shutdown request, and the DSRC module maintains its current enabled state. In this case, the MCU module can also return a response result to the switch control unit to notify the user or external control device that the shutdown request has been rejected. For example, when the switch control unit includes a human-machine interface (HMI), the MCU module can use the indicator devices in the HMI (such as indicator lights, buzzers, displays, etc.) to prompt the user, for example, by controlling the indicator light to flash at a specific frequency or controlling the buzzer to emit a specific sound, to inform the user that the shutdown operation has been rejected.
[0086] In this way, when the vehicle-mounted electronic tag responds to the DSRC's command to switch to a disabled state, it adopts different processing strategies for enable requests and disable requests: enable requests are executed directly, while disable requests are first assessed based on the scenario before deciding whether to execute. This differentiated processing logic ensures that the DSRC module can be started and stopped as needed to reduce power consumption, while also preventing the normal use of ETC functions from being affected by shutting down the DSRC module in scenarios where it is not appropriate to shut it down.
[0087] As one possible implementation, scenarios where the DSRC module is disabled can be pre-configured according to actual usage needs. This prevents users from accidentally shutting down the DSRC module under these scenarios, ensuring the normal operation of the ETC function. Specifically, in one possible implementation of this application embodiment, the aforementioned MCU module can be used for: If the current scenario for the vehicle is determined to be a scenario where shutdown is prohibited based on the current operating scenario information, the DSRC disable state switching command is intercepted while the DSRC module remains enabled. If the current scenario is determined not to be a scenario where shutdown is prohibited based on the current operating scenario information, the DSRC module is disabled.
[0088] Among them, the "prohibited shutdown scenario" can refer to vehicle operation scenarios in which the DSRC module is not allowed to be disabled.
[0089] It should be noted that the specific content of the prohibited shutdown scenarios can be pre-configured according to actual usage requirements. As an example, when the on-board electronic tag includes a storage module, the prohibited shutdown scenarios can also be stored in the storage module for the MCU module to read and judge. For example, prohibited shutdown scenarios may include, but are not limited to, the following: the vehicle is currently within the highway network; the vehicle has entered the highway but has not yet left; the vehicle is currently in the ETC entrance lane but has not yet completed the transaction; the vehicle is in a parking lot where ETC automatic toll collection is possible but has not completed the transaction, etc. In prohibited shutdown scenarios, the DSRC module needs to remain enabled to ensure that the roadside unit can communicate normally with the on-board electronic tag to complete the path information writing or transaction operation.
[0090] In one possible implementation, the scenario that must be disabled can be configured using either a whitelist or a blacklist. The whitelist method predefines which scenarios are prohibited from being disabled. The MCU module compares the currently running scenario information with the whitelist; if a match is found, it is determined to be a prohibited scenario. The blacklist method predefines which scenarios are not prohibited from being disabled (i.e., allowed scenarios). The MCU module compares the currently running scenario information with the blacklist; if no match is found, it is determined to be a prohibited scenario. This application does not limit the specific configuration method for the prohibited scenario.
[0091] As one possible implementation, the aforementioned current operating scenario information may include highway entrance / exit status information, which indicates whether the vehicle is currently at a highway entrance or exit. The MCU module can determine whether the current scenario belongs to a prohibited closure scenario based on the highway entrance / exit status information. That is, in one possible implementation of this application embodiment, the aforementioned MCU module can also be used for: If the status information at the highway entrance / exit is the preset status information, it is determined that the current scenario belongs to the prohibited closure scenario. The preset status information indicates that the vehicle entered the highway without paying. If the status information at the highway entrance / exit is not the preset status information, it is determined that the current scenario does not belong to the scenario where closing is prohibited.
[0092] In this embodiment, when the on-board electronic tag includes a storage module, highway entrance / exit status information can be stored in the storage module of the on-board electronic tag. In one possible implementation, the storage module can reuse the ESAM module, and the highway entrance / exit status information can be stored in the relevant standard file of the ESAM module. When a vehicle passes through an ETC entrance or exit lane, the Roadside Unit (RSU) writes the corresponding entrance / exit status information to this file. Specifically, when a vehicle passes through an ETC entrance lane, after the RSU completes communication with the on-board electronic tag, it writes the entrance status information to the relevant standard file of the ESAM module. When the vehicle completes payment through the ETC exit lane, the RSU writes the exit status information to the relevant standard file. Thus, the MCU module can obtain the current highway entrance / exit status of the vehicle by reading the entrance / exit status information in the relevant standard file.
[0093] In this embodiment, the highway entrance / exit status information may include multiple values, each corresponding to a different entry / exit status. Preset status information refers to information indicating that a vehicle has entered the highway but has not yet paid; that is, the preset status information indicates that the vehicle has entered the highway through the ETC entrance but has not yet completed payment and left through the ETC exit.
[0094] In one possible implementation, the range of values for the preset status information can be determined based on the definitions of entry / exit status in relevant standards. For example, an entry / exit status value of 0x01 indicates that the vehicle is at a closed ETC / MTC mixed entrance, meaning the vehicle has entered the highway through the mixed entrance but has not yet left; an entry / exit status value of 0x03 indicates that the vehicle is at a closed ETC entrance, meaning the vehicle has entered the highway through the dedicated ETC entrance but has not yet left. Both of these statuses indicate that the vehicle has entered the highway but has not yet completed the exit payment. Correspondingly, other values (such as 0x02 indicating a closed ETC / MTC mixed exit, 0x04 indicating a closed ETC exit, or other statuses other than 0x01 and 0x03) can indicate that the vehicle is in a state of "having completed payment and left the highway".
[0095] It should be noted that the above 0x01 and 0x03 are only exemplary values of preset status information. In practical applications, other status information indicating that a vehicle has entered the highway but has not yet completed the exit payment can also be configured as preset status information according to specific technical standards or actual usage requirements. This application does not limit this.
[0096] In this embodiment of the application, after receiving the DSRC instruction to switch the disabled state and determining that the target is disabled, the MCU module can read the high-speed entrance / exit status information from the storage module and compare the status information with the preset status information to determine whether the current scenario belongs to the prohibited shutdown scenario.
[0097] As an example, the MCU module can read the ingress / exit status information from the relevant standard file of the ESAM module. If the read status information is 0x01 or 0x03 (i.e., the preset status information), the MCU module determines that the status information indicates that the vehicle is currently on the highway and has not paid, thus determining that the current scenario belongs to the prohibited shutdown scenario. The MCU module intercepts the DSRC's disable state switching instruction and keeps the DSRC module enabled. If the read status information is not 0x01 or 0x03 (e.g., 0x02 or 0x04 exit status, or 0x00 reserved status), the MCU module determines that the current scenario does not belong to the prohibited shutdown scenario and disables the DSRC module.
[0098] In this way, the MCU module can accurately determine whether a vehicle is in a prohibited shutdown scenario of "entering the highway and not paying" based on the highway entrance and exit status information stored in the storage module. This allows the DSRC module to be turned off on demand to reduce power consumption, while ensuring that the DSRC module will not be turned off while the vehicle is driving on the highway, thus guaranteeing the reliability of path information writing and normal tolling.
[0099] As one possible implementation, the MCU module can determine the target disabling state corresponding to the DSRC module using various methods based on the type of DSRC disabling state switching instruction. For example, the DSRC disabling state switching instruction sent by the switch control unit can carry a clear target disabling state indication, and the MCU module can directly parse the target disabling state from this instruction. That is, in one possible implementation of this application embodiment, the above-mentioned MCU module can be used for: When the DSRC disable state switching command is changed to the DSRC enable command, the target disable state is set to enable. When the DSRC disables the disability state switching command, the target is determined to be disabled.
[0100] In one possible implementation, the DSRC disable state switching instruction can explicitly carry "on" or "off" semantic information; that is, the DSRC disable state switching instruction can include both DSRC enable and DSRC disable instructions. Upon receiving this instruction, the MCU module can directly determine the target disable state that the user expects the DSRC module to achieve by parsing the instruction. Specifically, if the DSRC disable state switching instruction is a DSRC enable instruction, the target disable state is determined to be enabled; if the DSRC disable state switching instruction is a DSRC disable instruction, the target disable state is determined to be disabled.
[0101] It should be noted that the relationship between the DSRC disabled state switching instruction type and the type of the switch control unit, as well as the MCU module's processing method for different types of instructions, can be found in the aforementioned description of the switch control unit and the relevant description of the DSRC disabled state switching instruction, which will not be repeated here.
[0102] As one possible implementation, when the DSRC disabling state switching command sent by the switch control unit does not explicitly carry "on" or "off" semantic information, but only serves as a trigger signal, the MCU module can automatically determine the target disabling state based on the current DSRC disabling state stored in the storage module, thus achieving state reversal. In a possible implementation of this application embodiment, the aforementioned vehicle-mounted electronic tag may further include a storage module, which may also be used to store the current DSRC disabling state; correspondingly, the aforementioned MCU module may also be used for: In response to the DSRC disable state switching command, obtain the current disable state of DSRC; Given that the DSRC currently sets the disabled state to enabled, determine that the target sets the disabled state to disabled. If the DSRC currently disables the target, determine whether the target disables the target and enables it.
[0103] In one possible implementation, the current DSRC disabled state can refer to the enabled or disabled state of the DSRC module at the current moment. This current DSRC disabled state can be persistently stored in a storage module so that the MCU module can read it when needed. When the MCU module needs to perform a state switch on the DSRC module, such as when it receives a trigger signal from a push-button switch or a "switch" command from the voice interaction module (which does not explicitly carry on / off semantics), the MCU module can read the current DSRC disabled state from the storage module and determine the target state based on it. If the current DSRC disabled state is enabled, the target disabled state can be determined to be disabled; if the current disabled state is disabled, the target disabled state can be determined to be enabled, thus achieving a state reversal.
[0104] It should be noted that the relationship between the DSRC disabled state switching instruction type and the type of the switch control unit, as well as the MCU module's processing method for different types of instructions, can be found in the aforementioned description of the switch control unit and the relevant description of the DSRC disabled state switching instruction, which will not be repeated here.
[0105] As one possible implementation, after the MCU module determines the target's disabled state and completes the enable or disable operation of the DSRC module, it can persistently store the updated DSRC module's disabled state in the storage module. This ensures that the state stored in the storage module remains synchronized with the actual state of the DSRC module, thereby guaranteeing that when the MCU module receives a trigger signal (not carrying an instruction type explicitly indicating the target's disabled state), it can accurately determine the target state based on the current state. In one possible implementation of this application embodiment, the MCU module can also be used for: In response to a change in the disabled state of the DSRC module, update the current disabled state of the DSRC stored in the storage module.
[0106] In one possible implementation, after the MCU module completes the enable or disable operation of the DSRC module, it can trigger an update of the current disabled state of the DSRC in the storage module. Specifically, when the MCU module controls the DSRC module to switch from a disabled state to an enabled state (e.g., in response to a DSRC enable instruction or a state toggle instruction to perform an enable operation), or when the MCU module controls the DSRC module to switch from an enabled state to a disabled state (e.g., in response to a DSRC disable instruction and after scene judgment, disabling is allowed), the actual disabled state of the DSRC module changes. At this time, the MCU module can trigger a state update process in the storage module and write the changed current disabled state of the DSRC module into the storage module, overwriting the original current disabled state of the DSRC stored in the storage module, thereby realizing the update of the stored state.
[0107] As one possible implementation, when the switch control unit includes a wireless communication unit, the user can remotely send a DSRC (Disability Switching Controller) command to the vehicle electronic tag via an external control device (such as a mobile app) to switch the disabled state. To ensure the user can know whether their command has been successfully executed, the MCU module needs to return a response result to the external control device, thereby improving the user-friendliness and practicality of the DSRC module's disabled switching mechanism. That is, in one possible implementation of this application embodiment, when the switch control unit includes a wireless communication unit, the aforementioned MCU module can also be used for: Generate a first return instruction corresponding to the DSRC disable state switching instruction issued by the external control device, and send the first return instruction to the wireless communication unit. The first return instruction carries the response result of the DSRC disable state switching instruction. Accordingly, the aforementioned wireless communication unit can also be used for: Receive the first return command sent by the MCU module and forward the first return command to the external control device.
[0108] In this embodiment, the wireless communication unit (such as a Bluetooth module or a near-field communication (NFC) module) can be used to establish a communication connection with an external control device (such as a control application APP running on a mobile phone, tablet, or other terminal device), receive a DSRC (Disability Switching Command) issued by the external control device, and forward the command to the MCU module. In this case, to provide the user with more explicit feedback on the command execution result, the wireless communication unit can return a response result to the external control device, presenting the user with information on whether the operation was successful or failed on the interface of the external control device, thereby improving the user experience.
[0109] In one possible implementation, after receiving the DSRC disabled state switching instruction forwarded by the wireless communication unit and completing the corresponding processing operation, the MCU module can generate a corresponding first return instruction for the instruction.
[0110] For example, if the DSRC disable state switching instruction is a DSRC enable instruction, after the MCU module enables the DSRC module, it can generate a first return instruction. The response result carried in the first return instruction can be used to indicate that the DSRC module has been successfully enabled (for example, the response result is "enabled successfully").
[0111] If the DSRC disable state switching instruction is a DSRC shutdown instruction, the MCU module can obtain the current operating scenario information and determine whether DSRC module disablement is allowed. If disablement is allowed, after the MCU module disables the DSRC module, it generates a first return instruction. The response result carried in the first return instruction is used to indicate that the DSRC module has been successfully disabled (e.g., the response result is "shutdown successful").
[0112] If the DSRC disables the state switching instruction to a DSRC shutdown instruction, but the MCU module determines that the current operating scenario is a scenario where shutdown is prohibited, intercepts the instruction and keeps the DSRC module enabled, the MCU module still generates a first return instruction. However, the response result carried in the first return instruction is used to indicate that the shutdown operation has been rejected (for example, the response result is "shutdown is not allowed in the current scenario").
[0113] In this way, regardless of whether the MCU module actually performs a state switching operation, a corresponding first return instruction will be generated for each DSRC disable state switching instruction, ensuring that the user can know the result of the operation.
[0114] After generating the first return instruction, the MCU module can send the first return instruction to the wireless communication unit through its communication interface with the wireless communication unit (such as UART or SPI). The wireless communication unit then forwards the first return instruction to the external control device.
[0115] In one possible implementation, the MCU module can encapsulate the first return instruction into a response data packet conforming to the corresponding communication standard according to the communication protocol and send it to the wireless communication unit so that the wireless communication unit can forward the first return instruction to the external control device.
[0116] For example, when the wireless communication unit is a Bluetooth module, the MCU can encapsulate the first return command into a data packet format specified by the Bluetooth communication protocol, and send the first return command to the external control device through the Bluetooth module. After receiving the data packet, the external control device can parse the response result carried in the first return command and display the corresponding prompt information on the device screen (such as "ETC is enabled", "ETC is disabled", or "Currently on the highway, disabling ETC is not allowed"), so that the user can understand the result of this operation.
[0117] For example, when the wireless communication unit is an NFC module, the external control device needs to be close to the vehicle electronic tag, and the NFC module sends the first return command to the external control device through near field communication.
[0118] As one possible implementation, when the switch control unit includes a wireless communication unit, the user can not only remotely issue DSRC disablement state switching commands through an external control device, but also remotely query the current disablement state of the DSRC module through the external control device. This allows the user to confirm the current state of the DSRC module before operating the remote control function, thereby avoiding repeated or erroneous operations and further improving the user experience. In one possible implementation of this application embodiment, the aforementioned wireless communication unit can also be used for: Receive the DSRC disable status query command issued by the external control device and forward the DSRC disable status query command to the MCU module; Correspondingly, the aforementioned MCU module can also be used for: Receive the DSRC disabled status query command forwarded by the wireless communication unit; Generate a second return instruction corresponding to the DSRC disable status query instruction, and send the second return instruction to the wireless communication unit, wherein the second return instruction carries the current DSRC disable status; Accordingly, the aforementioned wireless communication unit can also be used for: Receive the second return command sent by the MCU module and forward the second return command to the external control device.
[0119] In this embodiment, when a user wants to check whether the ETC function of the vehicle-mounted electronic tag is currently enabled or disabled via an external control device (such as a mobile APP), they can initiate a status query operation through the external control device. In response to this operation, the external control device generates a DSRC disable status query command and sends it to the wireless communication unit of the vehicle-mounted electronic tag. The DSRC disable status query command differs from the aforementioned DSRC disable status switching command; the DSRC disable status query command is only used to obtain the current disable status of the DSRC module and does not initiate any status change operation.
[0120] It should be noted that the practical significance of this query function lies in the fact that the state of the DSRC module may change for various reasons (e.g., the user directly switches the state through the physical switch of the human-machine interface unit, or the MCU module intercepts the shutdown command due to scene judgment, resulting in no change in state), and the state displayed on the external control device may be inconsistent with the actual state of the DSRC module. Through the query function provided in this application embodiment, the external control device can obtain the real state of the DSRC module in real time, ensuring that the information displayed on the user interface is accurate and reliable.
[0121] As one possible implementation, when the switch control unit includes a wireless communication unit, the wireless communication unit can interact with external control devices, receiving instructions from the external control devices and forwarding them to the MCU module, as well as forwarding return instructions generated by the MCU module to the external control devices. Since instruction transmission between the wireless communication unit (such as a Bluetooth module or NFC module) and the external control device is achieved through a wireless communication link, specific communication protocols and data frame formats must be followed for data encapsulation and parsing to ensure communication stability and data consistency. Therefore, during the aforementioned data interaction process, various instructions need to be encapsulated and parsed according to the agreed data frame format. As another possible implementation, DSRC-enabled disability state switching instructions, DSRC-enabled disability state query instructions, and corresponding return instructions can all be carried by data frames. The data frame can contain a data field, which can include a data type field and a data content field. Different instructions can have different values for the data content field and / or data type field to represent different instructions. The MCU module can determine the type and specific content of the received instruction by parsing the data type field and data content field in the data field.
[0122] In one possible implementation, in addition to the data fields, the data frame may also include other fields. For example, Figure 5 A schematic diagram of the structure of a data frame provided in an embodiment of this application is shown. Figure 5 As shown, a data frame generally includes the following fields: Frame Header Control Word (ST) field, Control (CTL) field, Length (LEN) field, Data (DATA) field (i.e., data field), and Block Check Character (BCC) field. The meanings of each field in the data frame are shown in Table 1.
[0123] The ST field, which can take the value 0x50, is used to identify the start position of the data frame. The receiver can identify the start boundary of the data frame by detecting the ST field.
[0124] The CTL field can be used to indicate the type and segmentation information of data packets. Specifically, the CTL field can be 2 bytes (16 bits) long, and its highest bit (bit 15) can be used to indicate the data packet type: when bit 15 is 1, it indicates that the current data packet is the start packet, and bits 14 to 0 indicate the total number of packets n in this transmission; when bit 15 is 0, it indicates that the current data packet is a continuation packet, and bits 14 to 0 indicate the sequence number of the current data packet, which is incremented from 2 to n in ascending order, and when the sequence number is n, it indicates the last packet. Through the segmentation control mechanism of the CTL field, the sender can split long data into multiple data packets for transmission, and the receiver can recombine the received multiple data packets into complete data according to the CTL field.
[0125] The LEN field indicates the length of the DATA field, and its value is the actual number of bytes in the DATA field. Based on the value of the LEN field, the receiver can correctly extract the complete data of the DATA field from the data frame.
[0126] The BCC field is used for error checking of data frames. For example, the sender performs an XOR operation on each byte from the ST field to the DATA field, and fills the data frame with the result as the value of the BCC field. After receiving the data frame, the receiver calculates the checksum using the same checksum algorithm (XOR operation from the ST field to the DATA field), and compares this checksum with the BCC field in the data frame. If they match, the data transmission is correct; if they do not match, an error occurred during data transmission, and the receiver can request the sender to retransmit.
[0127] It should be noted that, Figure 5 The number of bytes occupied by each field shown in the table above, as well as the values and functions of each field, are merely illustrative and should not be considered as limitations on this application.
[0128] In this embodiment of the application, the DATA field (i.e., the data field) can be the core part of the transmitted data frame, used to carry specific instruction data. Figure 6 A schematic diagram of the structure of a data field provided in an embodiment of this application is shown. For example... Figure 6 As shown, the data field can include a data type (Type) field and a data content (Content) field. The Type field can be 1 byte long and indicates the data type of the instruction, i.e., what type of operation the instruction belongs to. The Content field is a variable-length field, its length determined by the specific instruction, and is used to carry the specific data content of the instruction. Taking a Bluetooth module as an example, the values of the Type field and their corresponding functional descriptions are shown in Table 2:
[0129] The AD channel can be the DSRC module switch channel defined in this application embodiment, used to switch the enable or disable state of the DSRC module and query the current enable or disable state of the DSRC module. When the data field in the data frame carrying the instruction has the data type AD, it can be determined that this is an instruction related to the enable or disable state of the DSRC module, used to implement the enable, disable, or status query operation of the DSRC module.
[0130] As an example, the values of the data content fields corresponding to each type of instruction can be pre-defined. Different types of instructions correspond to different data contents, so that the MCU module and external control devices can determine the instruction type based on the value of the data content field.
[0131] For example, the data type of the DSRC disable status query instruction can be AD, and the data content can be 0; the data type of the DSRC enable instruction can be AD, and the data content can be 1; the data type of the DSRC disable instruction can be AD, and the data content can be 2; the data type of the first return instruction can be AD, and the data content can be 3; the data type of the second return instruction can be AD, and when the read DSRC currently disables the status, the data content can be 41, and when the read DSRC currently disables the status, the data content can be 42. As another example, the data type of the DSRC disable status query instruction can be AD, and the data content can be C0; the data type of the DSRC enable instruction can be AD, and the data content can be C1; the data type of the DSRC disable instruction can be AD, and the data content can be C2; the data type of the first return instruction can be AD, and the data content can be C3; the data type of the second return instruction can be AD, and when the read DSRC currently disables the status, the data content can be C41, and when the read DSRC currently disables the status, the data content can be C42.
[0132] It should be noted that the examples above are merely illustrative and should not be considered as limitations on this application. In actual use, the values of the data content fields corresponding to different instructions can be agreed upon according to actual needs and specific application scenarios.
[0133] As one possible implementation, the Content field in the data field corresponding to the DSRC enable instruction, DSRC disable instruction, and DSRC disable status query instruction can also include the instruction code (Type), instruction length, and instruction data field. The structure of the Content field is shown in Table 3.
[0134] The instruction code field (i.e., the data at position 0 in the Content field) of the DSRC enable instruction, DSRC disable instruction, and DSRC disable status query instruction can be set to AD. The values of the instruction data (i.e., the data starting from position 2 in the Content field) of the DSRC enable instruction, DSRC disable instruction, and DSRC disable status query instruction, and their corresponding functional descriptions are shown in Table 4.
[0135] The C0 instruction can be used to query the current disabled state of the DSRC module. After receiving this instruction, the MCU module reads the current disabled state of the DSRC from the storage module and generates a return instruction. The C1 instruction is used to switch the disabled state of the DSRC module. When the instruction data is C1+0x01, it indicates a DSRC enable instruction. The MCU module determines the target disabled state to be enabled and directly controls the DSRC module to be enabled. When the instruction data is C1+0x02, it indicates a DSRC disable instruction. The MCU module determines the target disabled state to be disabled and needs to further obtain the current operating scenario information to determine whether disabledness is allowed.
[0136] As one possible implementation, the Content field in the data field corresponding to the return instruction can also include the instruction code (Type), status word, instruction length, and instruction return data field. The structure of the Content field corresponding to the return instruction is shown in Table 5.
[0137] The instruction code field (i.e., the data at position 0 in the Content field) of the return instruction can take the value BD; the values of the instruction return data (i.e., the data starting at position 3 in the Content field) and their corresponding function descriptions are shown in Table 6.
[0138] When the external control device issues a C0 query command, the MCU module can read the current disabled state of DSRC from the storage module, generate a second return command, the command code can be BD, and the command return data can be C0+0x01 (indicating that it is currently enabled) or C0+0x02 (indicating that it is currently disabled), and forward it to the external control device through the wireless communication unit.
[0139] It should be noted that the data frame format, field names, field lengths, values of each field (e.g., ST is 0x50, Type is AD or BD, instruction data is C0 or C1, status data is 0x01 or 0x02, etc.), BCC verification methods, and specific encoding methods of each instruction shown in the tables and figures above are merely exemplary illustrations of embodiments of this application and do not constitute a limitation on the scope of protection of this application. In practical applications, those skilled in the art can make appropriate adjustments or equivalent substitutions to the above data frame format, field definitions, specific values, and verification methods according to changes in specific communication protocols, hardware design requirements, or technical standards. For example, adjusting the value of the ST field, changing the encoding of the Type field, adding or deleting some fields, or using other verification algorithms, etc., as long as the functions implemented and the technical effects achieved are substantially the same as those of this application, they should all fall within the scope of protection of this application.
[0140] In addition to the aforementioned MCU module, DSRC module, switch control interface unit, storage module, and power supply module, the vehicle-mounted electronic tag provided in this application embodiment can also include other functional modules according to specific needs in practical applications to further improve the device's functionality. For example, the vehicle-mounted electronic tag may also include an ESAM module for securely storing vehicle identity information, key data, transaction records, and toll-related documents, and performing security operations such as encryption / decryption and identity authentication; it may also include an anti-tampering module for real-time monitoring of whether the vehicle-mounted electronic tag has been removed from the vehicle to prevent the tag from being transferred or stolen. The aforementioned ESAM module and anti-tampering module are conventional components in existing vehicle-mounted electronic tags, and their specific implementation methods can adopt technical solutions known in the art, which will not be elaborated upon in this application.
[0141] To more clearly illustrate the structure of the vehicle-mounted electronic tag provided in the embodiments of this application, Figure 7 A schematic diagram of the structure of a vehicle-mounted electronic tag provided in an embodiment of this application is shown. Figure 7 As shown, the vehicle-mounted electronic tag includes an MCU module, a DSRC module, a storage module, a power module, an ESAM module, an anti-tamper module, and a switch control unit. The MCU module can be electrically or communicatively connected to the DSRC module, storage module, power module, ESAM module, anti-tamper module, and switch control unit, respectively, for controlling and exchanging data with these modules. The power module can be connected to the MCU module, DSRC module, storage module, ESAM module, anti-tamper module, and switch control unit, respectively, to provide operating voltage to these modules. Figure 7The control unit for the vehicle's electronic tag is illustrated using an example comprising a physical switch, a Bluetooth module, and an NFC module. The physical switch can be mounted on the vehicle's electronic tag itself, allowing users to operate it directly from the tag. The Bluetooth and NFC modules are used for wireless communication with external control devices, receiving commands from them. In practical applications, the vehicle's electronic tag may contain only one or more of the physical switch, Bluetooth module, and NFC module, or may include other types mentioned above, and is not limited to these. Figure 7 The example shown includes all three scenarios simultaneously. It should be noted that... Figures 1-4 and Figure 7 The structural block diagram of the vehicle-mounted electronic tag shown is merely an exemplary illustration of an embodiment of this application. The module composition, connection relationships, and signal flow between modules shown do not constitute a limitation on the scope of protection of this application. In practical applications, those skilled in the art can add, delete, or recombine some modules as needed. As long as the functions implemented and the technical effects achieved are substantially the same as those of this application, they should all fall within the scope of protection of this application.
[0142] The vehicle-mounted electronic tag provided in this application embodiment sends a DSRC (Disabled Controller Recognition) disable state switching command to the MCU (Microcontroller Unit) module via a switch control unit. The MCU module determines the target disable state corresponding to the DSRC module based on this command. When the target disable state is enabled, it directly controls the DSRC module to be enabled. When the target disable state is disabled, it acquires the current operating scenario information and determines whether to allow the DSRC module to disable based on this information. Therefore, on the one hand, it enables on-demand start / stop of the DSRC module, allowing users to actively disable the DSRC module when they do not need to use the ETC (Electronic Toll Collection) function, avoiding the DSRC module being in a wake-up listening state for extended periods, thereby reducing the power consumption of the vehicle-mounted electronic tag and extending the lifespan of its built-in battery. On the other hand, before disabling the DSRC module, the MCU module acquires the current operating scenario information and determines whether to allow disabling, avoiding disruption to normal toll collection due to disabling the DSRC module in unsuitable scenarios, thus ensuring the accuracy and security of toll collection.
[0143] Corresponding to the vehicle-mounted electronic tag described in the above embodiments, this application also proposes a control method for the vehicle-mounted electronic tag. Figure 8 A flowchart illustrating a control method for an in-vehicle electronic tag provided in an embodiment of this application is shown.
[0144] like Figure 8 As shown, the control method for the vehicle-mounted electronic tag is applied to the MCU module in the vehicle-mounted electronic tag as described above. The vehicle-mounted electronic tag also includes a DSRC module and a switch control unit. Accordingly, the method includes the following steps: Step 101: In response to the DSRC disable state switching command sent by the switch control unit, determine the target disable state corresponding to the DSRC module.
[0145] Step 102: When the target disables the state to enable, control the DSRC module to enable.
[0146] Step 103: When the target causes the disabled state to be disabled, obtain the current operating scenario information of the vehicle where the on-board electronic tag is located, and determine whether the DSRC module is allowed to be disabled based on the current operating scenario information.
[0147] The vehicle-mounted electronic tag control method provided in this application embodiment determines the target disable state of the DSRC module according to the instruction by the MCU module. When the target disable state is enabled, the DSRC module is directly enabled. When the target disable state is disabled, the current operating scenario information is obtained and the user determines whether the DSRC module is allowed to disable based on the current operating scenario information. Therefore, on the one hand, the on-demand start and stop of the DSRC module is realized, allowing users to actively turn off the DSRC module when they do not need to use the ETC function, avoiding the DSRC module being in a wake-up listening state for a long time, thereby reducing the power consumption of the vehicle-mounted electronic tag and extending the lifespan of the built-in battery. On the other hand, before turning off the DSRC module, the MCU module obtains the current operating scenario information and determines whether to allow the turning off, avoiding the impact on normal toll collection due to turning off the DSRC module in unsuitable scenarios, thus ensuring the accuracy and security of toll collection.
[0148] In one possible implementation of this application, the aforementioned DSRC module disabling refers to cutting off the power supply to the DSRC module, or the aforementioned DSRC module disabling refers to disabling all radio frequency functions of the DSRC module.
[0149] Optionally, in another possible implementation of this application, step 103 above may include: If the current scenario for the vehicle is determined to be a scenario where shutdown is prohibited based on the current operating scenario information, the DSRC disable state switching command is intercepted while the DSRC module remains enabled. If the current scenario corresponding to the vehicle is determined to be a scenario where shutdown is prohibited based on the previous running scenario information, the DSRC module is disabled.
[0150] Optionally, in another possible implementation of this application, the aforementioned current operating scenario information includes highway entrance / exit status information; correspondingly, the aforementioned method may further include: If the status information at the highway entrance / exit is the preset status information, it is determined that the current scenario belongs to the prohibited closure scenario. The preset status information indicates that the vehicle entered the highway without paying. If the status information at the highway entrance / exit is not the preset status information, it is determined that the current scenario does not belong to the scenario where closing is prohibited.
[0151] Optionally, in another possible implementation of this application, step 101 above may include: When the DSRC disable state switching command is changed to the DSRC enable command, the target disable state is set to enable. When the DSRC disables the disability state switching command, the target is determined to be disabled.
[0152] Optionally, in another possible implementation of this application, the vehicle-mounted electronic tag further includes a storage module for storing the current disabled state of the DSRC; correspondingly, step 101 may include: In response to the DSRC disable state switching command, obtain the current disable state of DSRC; Given that the DSRC currently sets the disabled state to enabled, determine that the target sets the disabled state to disabled. If the DSRC currently disables the target, determine whether the target disables the target and enables it.
[0153] Optionally, in another possible implementation of this application, the above method may further include: In response to a change in the disabled state of the DSRC module, update the current disabled state of the DSRC stored in the storage module.
[0154] Optionally, in another possible implementation of this application, when the switch control unit includes a wireless communication unit, the wireless communication unit is used to communicate with an external control device, receive a DSRC disable state switching command issued by the external control device, and forward the DSRC disable state switching command to the MCU module; correspondingly, the above method may also include: Generate a first return instruction corresponding to the DSRC disable state switching instruction issued by the external control device, wherein the first return instruction carries the response result of the DSRC disable state switching instruction; Send a first return command to the wireless communication unit so that the wireless communication unit forwards the first return command to the external control device.
[0155] Optionally, in another possible implementation of this application, when the switch control unit includes a wireless communication unit, the wireless communication unit is used to communicate with an external control device; correspondingly, the above method may further include: Receive the DSRC disable status query command forwarded by the wireless communication unit, wherein the DSRC disable status query command is issued to the wireless communication unit by the external control device; Generate a second return instruction corresponding to the DSRC incapacitance status query instruction, wherein the second return instruction carries the current DSRC incapacitance status; A second return command is sent to the wireless communication unit so that the wireless communication unit forwards the second return command to the external control device.
[0156] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0157] It should be noted that the information interaction and execution process of the above method are based on the same concept as the vehicle electronic tag embodiment of this application. For details on its specific functions and technical effects, please refer to the vehicle electronic tag embodiment section, which will not be repeated here.
[0158] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps described in the various method embodiments above.
[0159] As an example, the processor in this application embodiment can be the MCU module in the aforementioned vehicle-mounted electronic tag.
[0160] This application provides a computer program product that, when run on a processor, enables the processor to execute the steps described in the various method embodiments above.
[0161] As an example, the processor in this application embodiment can be the MCU module in the aforementioned vehicle-mounted electronic tag.
[0162] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include at least: any entity or device capable of carrying computer program code to a device / electronic device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks.
[0163] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.
[0164] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0165] In the embodiments provided in this application, it should be understood that the disclosed devices / electronic devices and methods can be implemented in other ways. For example, the device / electronic device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings or direct couplings or communication connections may be through some interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.
[0166] The units described as separate components may or may not be physically separate. 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 the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0167] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.
Claims
1. A vehicle-mounted electronic tag, characterized in that, include: The system includes a microcontroller unit (MCU) module, a dedicated short-range communication (DSRC) module, and a switch control unit; the DSRC module can be independently enabled or disabled; the switch control unit is used to send a DSRC disable state switching command to the MCU module. The MCU module is used for: In response to the DSRC instruction to switch the disability state, the target disability state corresponding to the DSRC module is determined; When the target disables the state to enable, the DSRC module is enabled. When the target causes the DSRC module to become disabled, the current operating scenario information of the vehicle where the vehicle-mounted electronic tag is located is obtained, and the DSRC module is allowed to become disabled based on the current operating scenario information.
2. The vehicle-mounted electronic tag as described in claim 1, characterized in that, The vehicle-mounted electronic tag also includes a power module. The DSRC module failure refers to cutting off the power supply path between the power module and the DSRC module; or, the DSRC module failure refers to shutting down all radio frequency functions of the DSRC module through control commands.
3. The vehicle-mounted electronic tag as described in claim 1, characterized in that, The MCU module is specifically used for: If it is determined from the current operating scenario information that the current scenario corresponding to the vehicle belongs to a scenario where shutdown is prohibited, the DSRC disable state switching command is intercepted while the DSRC module remains enabled. If, based on the current operating scenario information, it is determined that the current scenario does not belong to the prohibited shutdown scenario, the DSRC module is disabled.
4. The vehicle-mounted electronic tag as described in claim 3, characterized in that, The current operating scenario information includes highway entrance / exit status information, and the MCU module is further used for: If the highway entrance / exit status information is a preset status information, it is determined that the current scenario belongs to the prohibited closure scenario, wherein the preset status information indicates that the vehicle entered the highway without paying; If the status information of the highway entrance / exit is not the preset status information, it is determined that the current scenario does not belong to the scenario where closing is prohibited.
5. The vehicle-mounted electronic tag as described in claim 1, characterized in that, The MCU module is specifically used for: When the DSRC disable state switching instruction is a DSRC enable instruction, the target disable state is determined to be enabled; If the DSRC disables the disability state switching instruction as a DSRC off instruction, the target is determined to be disabled.
6. The vehicle-mounted electronic tag as described in claim 1, characterized in that, The vehicle-mounted electronic tag also includes a storage module, which is used to store the current disabled state of the DSRC. The MCU module is specifically used for: In response to the DSRC's command to switch the incapacitated state, the current incapacitated state of the DSRC is obtained; If the DSRC currently disables the disabled state to enabled, determine that the target disables the disabled state. If the DSRC currently disables the target, then the target disables the target and enables the target.
7. The vehicle-mounted electronic tag as described in claim 6, characterized in that, The MCU module is also used for: In response to a change in the disabled state of the DSRC module, the current disabled state of the DSRC stored in the storage module is updated.
8. The vehicle-mounted electronic tag as described in claim 6, characterized in that, The storage module is also used to store the current running scenario information.
9. The vehicle-mounted electronic tag as described in any one of claims 1-8, characterized in that, The switch control unit includes a human-machine interaction unit and / or a wireless communication unit; The human-computer interaction unit is used to collect the user's operations in the human-computer interaction unit, generate the DSRC to switch the disability state, and send the DSRC to switch the disability state to the MCU module. The wireless communication unit is used to communicate with an external control device, receive the DSRC disable state switching instruction issued by the external control device, and forward the DSRC disable state switching instruction to the MCU module.
10. The vehicle-mounted electronic tag as described in claim 9, characterized in that, In the case where the switch control unit includes the wireless communication unit, the MCU module is further configured to: Generate a first return instruction corresponding to the DSRC disabling state switching instruction issued by the external control device, and send the first return instruction to the wireless communication unit, wherein the first return instruction carries the response result of the DSRC disabling state switching instruction; The wireless communication unit is further configured to: The system receives the first return instruction sent by the MCU module and forwards the first return instruction to the external control device.
11. The vehicle-mounted electronic tag as described in claim 9, characterized in that, The wireless communication unit is further configured to: Receive the DSRC disable status query command issued by the external control device, and forward the DSRC disable status query command to the MCU module; The MCU module is also used for: Receive the DSRC disabled status query instruction forwarded by the wireless communication unit; Generate a second return instruction corresponding to the DSRC incapacitance status query instruction, and send the second return instruction to the wireless communication unit, wherein the second return instruction carries the current DSRC incapacitance status; The wireless communication unit is further configured to: The system receives the second return instruction sent by the MCU module and forwards the second return instruction to the external control device.
12. A control method for a vehicle-mounted electronic tag, characterized in that, The method comprises: an MCU module applied in an on-board electronic tag as described in any one of claims 1-11, wherein the on-board electronic tag further comprises a DSRC module and a switch control unit; and the method comprises: In response to the DSRC disable state switching command sent by the switch control unit, the target disable state corresponding to the DSRC module is determined; When the target disables the state to enable, the DSRC module is enabled. When the target causes the DSRC module to become disabled, the current operating scenario information of the vehicle where the vehicle-mounted electronic tag is located is obtained, and the DSRC module is allowed to become disabled based on the current operating scenario information.
13. The method as described in claim 12, characterized in that, The vehicle-mounted electronic tag also includes a power module. The DSRC module failure refers to cutting off the power supply path between the power module and the DSRC module; or, the DSRC module failure refers to shutting down all radio frequency functions of the DSRC module through control commands.
14. The method as described in claim 12, characterized in that, The step of determining whether the DSRC module is allowed to disable based on the current operating scenario information includes: If it is determined from the current operating scenario information that the current scenario corresponding to the vehicle belongs to a scenario where shutdown is prohibited, the DSRC disable state switching command is intercepted while the DSRC module remains enabled. If, based on the current operating scenario information, it is determined that the current scenario does not belong to the prohibited shutdown scenario, the DSRC module is disabled.
15. The method as described in claim 14, characterized in that, The current operating scenario information includes highway entrance / exit status information, and the method further includes: If the highway entrance / exit status information is a preset status information, it is determined that the current scenario belongs to the prohibited closure scenario, wherein the preset status information indicates that the vehicle entered the highway without paying; If the status information of the highway entrance / exit is not the preset status information, it is determined that the current scenario does not belong to the scenario where closing is prohibited.
16. The method as described in claim 12, characterized in that, The step of responding to the DSRC disable state switching command sent by the switch control unit and determining the target disable state corresponding to the DSRC module includes: When the DSRC disable state switching instruction is a DSRC enable instruction, the target disable state is determined to be enabled; If the DSRC disables the disability state switching instruction as a DSRC off instruction, the target is determined to be disabled.
17. The method as described in claim 12, characterized in that, The vehicle-mounted electronic tag also includes a storage module for storing the current DSRC incapacitance state. The process of determining the target incapacitance state corresponding to the DSRC module in response to a DSRC incapacitance state switching command sent by the switch control unit includes: In response to the DSRC's command to switch the incapacitated state, the current incapacitated state of the DSRC is obtained; If the DSRC currently disables the disabled state to enabled, determine that the target disables the disabled state. If the DSRC currently disables the target, then the target disables the target and enables the target.
18. The method as described in claim 17, characterized in that, The method further includes: In response to a change in the disabled state of the DSRC module, the current disabled state of the DSRC stored in the storage module is updated.
19. The method according to any one of claims 12 to 18, characterized in that, When the switch control unit includes a wireless communication unit, the wireless communication unit is used to communicate with an external control device, receive the DSRC disabling state switching command issued by the external control device, and forward the DSRC disabling state switching command to the MCU module. The method further includes: Generate a first return instruction corresponding to the DSRC disabling state switching instruction issued by the external control device, wherein the first return instruction carries the response result of the DSRC disabling state switching instruction; The first return instruction is sent to the wireless communication unit so that the wireless communication unit forwards the first return instruction to the external control device.
20. The method according to any one of claims 12-18, characterized in that, When the switch control unit includes a wireless communication unit for communicating with an external control device, the method further includes: The wireless communication unit receives a DSRC disable status query instruction forwarded by the wireless communication unit, wherein the DSRC disable status query instruction is issued to the wireless communication unit by the external control device. Generate a second return instruction corresponding to the DSRC incapacitance status query instruction, wherein the second return instruction carries the current incapacitance status of the DSRC; The second return instruction is sent to the wireless communication unit so that the wireless communication unit forwards the second return instruction to the external control device.