CN103630375A - Fault diagnosis method and system of on-board unit and on-board unit - Google Patents
Fault diagnosis method and system of on-board unit and on-board unit Download PDFInfo
- Publication number
- CN103630375A CN103630375A CN201210307643.1A CN201210307643A CN103630375A CN 103630375 A CN103630375 A CN 103630375A CN 201210307643 A CN201210307643 A CN 201210307643A CN 103630375 A CN103630375 A CN 103630375A
- Authority
- CN
- China
- Prior art keywords
- failure information
- obu
- information
- execution failure
- described execution
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The application discloses a fault diagnosis method and system of an on-board unit (OBU) and an OBU. The fault diagnosis method comprises the following steps of a failure information storage execution step and a failure information providing execution step. To be specific, according to the failure information storage execution step, when an OBU runs a designated flow, if the instruction execution fails, corresponding execution failure information is recorded to a storage zone in the OBU; and according to the failure information providing execution step, the OBU provides the execution failure information for external reading equipment. According to the application, the technicist can carry out diagnosing on the OBU fault accurately, rapidly and conveniently during the repairing process, thereby improving the repairing speed of the OBU and ensuring the repairing quality. Moreover, the technicist of the OBU manufacturer can analyze and evaluate the execution failure information recorded in the OBU so as to perfect all links, including designing, testing and using and the like, of the product, thereby minimizing the repair rate of the product.
Description
Technical field
The application relates to a kind of intelligent transportation (ITS:Intelligent Transportation System) field, relates in particular to method for diagnosing faults, OBU and the system of a kind of board units (OBU:On-board Units).
Background technology
Dedicated Short Range Communications, (DSRC:Dedicated Short Range Communications) technology is for the roadside device (RSU:Road Side Unit) on road and the short distance communication between the OBU on vehicle, to realize deducting fees or monitoring vehicle, for example, in electric non-stop toll (Electronic Toll Collection:ETC) system, OBU on RSU and vehicle carries out the mutual of microwave signal, makes vehicle automatic fee in the situation that not stopping.
Along with develop rapidly and the widespread use of DSRC technology, and the going from strength to strength of OBU customer group scale, people have proposed requirements at the higher level to the maintenance of OBU.Once OBU is damaged, first need accurately to find out reason and the concrete link that fault occurs, OBU is carried out to fault diagnosis, generally, cause the reason that OBU reprocesses mainly to comprise improper use, technological problems, normal damage etc.Part reprocessed products are easy to confirm failure cause by some tests; Yet, because some fault occurs under specific environment for use, the practical application scene of its generation cannot be reduced by technician or simulate, and therefore has some reprocessed products just not too easily to confirm failure cause (what for example improper use caused reprocesses) to be unfavorable for reprocessing of OBU.
Summary of the invention
The technical problem underlying that the application will solve is that a kind of method for diagnosing faults of being convenient to OBU to safeguard, board units and system are provided.
For solving the problems of the technologies described above, according to the application's first aspect, the application provides a kind of method for diagnosing faults of board units, comprises the following steps:
Carry out failure information storing step: board units is specified in the process of flow process in operation, if instruction is carried out unsuccessfully, corresponding execution failure information is recorded in to the storage area in described board units;
Carry out failure information step is provided: board units offers outside fetch equipment by described execution failure information.
In a kind of embodiment, the concrete mode that records described execution failure information comprises: described execution failure information comprises fault type, failure command, failed at least one in replying.
In a kind of embodiment, the form that records of described execution failure information is failure record structure, array, function, variable or pointer.
In a kind of embodiment, described execution failure information also comprises call number, records after described execution failure information at every turn, and the call number of the described execution failure information of record adds 1 automatically next time.
In a kind of embodiment, record in the process of described execution failure information at every turn, also described execution failure information is carried out to data check, and be recorded in described execution failure information after generating check code.
In a kind of embodiment, record in the process of described execution failure information at every turn, also described execution failure information is backed up.
In a kind of embodiment, described appointment flow process comprises at least one of once issuing in flow process, secondary offering flow process, activation testing process, transaction flow.
In a kind of embodiment, described execution failure information storing step also comprises: if instruction runs succeeded, the information that runs succeeded of correspondence is also recorded in to the storage area in board units.
According to the application's second aspect, the application provides a kind of board units, comprising:
Carry out judge module: carry out failure information memory module: for specify the process of flow process in board units operation, if when instruction is carried out unsuccessfully, corresponding execution failure information is recorded in to the storage area in board units;
Carry out failure information module is provided: for described execution failure information is offered to outside fetch equipment.
In a kind of embodiment, described execution failure information memory module comprises structure generation unit, and for failed regeneration interrecord structure body, the information in described failure record structure comprises fault type, failure command, failed at least one in replying.
According to the application's the third aspect, the application provides a kind of fault diagnosis system of board units, comprises above-described board units, and described outside fetch equipment.
The application's beneficial effect is: the specifying information that the application breaks down in actual application to OBU carries out record, be convenient to technician carries out accurately the fault of OBU according to these information in rework process, diagnosis fast, not only can improve the speed of reprocessing of OBU, guarantee to reprocess quality, and the technician of being convenient to OBU manufacturer is by the execution failure information recording in assessment and analysis OBU, improve the design/test/links such as use of product, reduce to greatest extent the repair rate of product, thereby meet user's user demand, also be convenient to user based on these information, the quality of OBU is distinguished and selected, thereby select desirable OBU manufacturer.
Accompanying drawing explanation
Fig. 1 is the method for diagnosing faults process flow diagram of the OBU of a kind of embodiment of the application;
Fig. 2 is the process flow diagram that the OBU of a kind of embodiment of the application once issues;
Fig. 3 is the process flow diagram of the OBU secondary offering of a kind of embodiment of the application;
Fig. 4 is that the OBU of a kind of embodiment of the application activates the process flow diagram detecting;
Fig. 5 is the process flow diagram of the OBU arm's length transaction of a kind of embodiment of the application;
Fig. 6 is that the OBU of a kind of embodiment of the application carries out the process flow diagram of fault diagnosis in arm's length transaction process;
Fig. 7 is the process flow diagram of read failure information from the OBU of a kind of embodiment of the application;
Fig. 8 is the structured flowchart of the OBU of a kind of embodiment of the application.
Embodiment
Below by embodiment, by reference to the accompanying drawings the application is described in further detail.
In the embodiment of the present application, the execution failure information that OBU is occurred in carrying out all kinds of instruction process carries out record, is convenient to carry out accurately in OBU rework process and fault diagnosis fast.
Embodiment mono-:
Please refer to Fig. 1, the method for diagnosing faults of the present embodiment OBU mainly comprises the following steps:
Step S101: carry out failure information storing step, OBU is in the process of all kinds of appointment flow processs of operation, and whether decision instruction carries out failure, if instruction is carried out unsuccessfully, corresponding execution failure information is recorded in to the storage area in OBU.
As one of crucial DSRC equipment, in order to meet technical standard and user demand, OBU can experience the flow process of multiple instruction from produce actual use procedure, mainly comprises once distribution, secondary offering, activation and test and actual transaction flow.In every kind of flow process, OBU again can be according to carrying out a plurality of instructions according to a definite sequence, in most cases, these instructions all can successful execution, under fortuitous event, also can be because the reasons such as OBU improper use, technological problems, signal intensity, normal damage cause instruction to be carried out unsuccessfully, in this case, OBU is recorded in inner specific storage area by software by corresponding execution failure information.For example storage space can adopt take up room less EEPROM or Flash to carry out information storage, suppose that EEPROM amount of capacity is 2Kbyte, carry out the storage space that failure information only takies 106 bytes for every, maximum can be supported 19 records, can certainly increase according to actual needs the capacity of EEPROM.
The content of the execution failure information of each record can comprise call number, fault type, failure command, unsuccessfully one or more of information such as reply, for the character of record trouble, facilitate technician in the process of reprocessing, understand rapidly the reason of fault generation and how to solve fault.Call number is for carrying out order differentiation and statistics to repeatedly carrying out failed instruction, and each record is carried out after failure information, and the call number in the execution failure information next time recording adds 1 automatically.Each record is carried out in the process of failure information, also can carry out data check to carrying out failure information, and be recorded in execution failure information after generating check code, avoid information to be tampered at memory period, in order to improve processing speed and outside fetch equipment, carry out the speed of data check, the mechanism of data check adopts CRC check.Further, each record is carried out in the process of failure information, also can back up carrying out failure information, further improves the reliability of data processing.
The recording mode of carrying out failure information has multiple, for example, in the present embodiment, software in OBU can generate an interrecord structure body err_record in order to record concrete execution failure information, and structure definition comprises call number, the instruction (abbreviation failure command) while occurring unsuccessfully, replying or the crc check code of information (be called for short unsuccessfully and reply), structure etc. while occurring unsuccessfully.Or in other embodiment, the form that records of carrying out failure information also can be array, function, variable or pointer etc.
In addition, in each flow process, except failure information carried out in record, according to real needs, if instruction runs succeeded, also the information that runs succeeded of correspondence also can be recorded in to the storage area in OBU, to read these data by outside fetch equipment in the situation that of needs.The recording of information mode that the runs succeeded failure information of also can consulting and carrying out, carries out record with the form of structure.
Step S102: carry out failure information step is provided, according to specific needs, OBU offers outside fetch equipment by execution failure information, such as reprocessing at equipment, regularly detect, in the process such as maintenance, can carry out this step.Particularly, outside fetch equipment can be emulator, hand-held set etc., and it has the compatible data-interface mutually with OBU, can to OBU, send information read step by data-interface, and read one by one the execution failure information of storing in OBU, certainly, also can read one by one the information that runs succeeded wherein.For the sake of security, in the time of outside fetch equipment reading information, also need it to carry out one by one data check, reading information just in the successful situation of data check only, otherwise this information is made as invalid.
Below the once distribution flow process of OBU, secondary offering flow process, activation testing process, transaction flow are introduced respectively.
As shown in Figure 2, the flow process of once issuing of OBU is mainly used in replacing and when OBU dispatches from the factory, is loaded in the default key in ESAM, publishing system carries out key dispersion (concrete dispersion process can with reference to the related content in GB) according to the individual information of OBU, because the individual information of each OBU has uniqueness, therefore therefore the key after each OBU is replaced also just has uniqueness, this flow process is mainly carried out when equipment dispatches from the factory.Idiographic flow is:
Distribute the software to obtain OBU individual information -- issue device to send OBU BST broadcast instructions -- OBU wake up from hibernation individual -- release software -- OBU to release information equipment to provide VST response -- issue device OBU extraction according to the individual information of OBU distributed key -- issuing software replacement of master key -- issued to send OBU key substitution command Transfer equipment, channel.rq -- OBU to embedded security control module (ESAM:Embedded, Secure, Access, Module) send instructions and obtain key substitution results -- OBU key substitution results in Transfer, channel.rs is sent to the issuing equipment -- return the key to release software release equipment replacement -- issuing replacement success software to determine the key, if the success of a end of the issue (if not successful to replace key) -- notice OBU release link SetMMT.rq+Evenreport -- OBU success prompts to issue device is then transferred to a sleep mode.
As shown in Figure 3, OBU once issues the individual information that flow process is mainly used in writing car owner, these individual informations such as car plate, engine mumber, the number-plate number, vehicle (lorry, minibus), start and stop the date etc., conventionally in each outlet, carrying out.After distribution, operating personnel will confirm by observing the last information showing of distributed software, and the information being write to guarantee is all correct.Idiographic flow is:
Distributed software is obtained OBU individual information, and---issuing equipment is to OBU transmission BST broadcasting instructions---wakes OBU up---OBU provides VST to reply to issuing equipment, and---individual information of issuing equipment extraction OBU---distributed software shows OBU information, and---distributed software arranges the guarantee period of OBU, and---issuing equipment sends change system information instruction Transfer channel.rq to OBU, and---OBU also obtains change result to ESAM transmission instruction, and---OBU sends to issuing equipment by change result Transfer channel.rs, and whether successful change by the judgement of---issuing equipment returns to change result to distributed software---distributed software from dormant state, if success, arranges information of vehicles, license plate number for example,---issuing equipment sends change information of vehicles instruction Transfer channel.rq to OBU, and---OBU sends instruction and obtains change result to ESAM, and---OBU sends information of vehicles change to issuing equipment and replys Transfer channel.rs---issuing equipment returns to change result to distributed software---distributed software and judge whether to change successfully tonnage vehicles etc. (if unsuccessful, resetting the guarantee period), be read some as information of vehicles (otherwise resetting information of vehicles)---distributed software is sent GetSecure.rq instruction to OBU---OBU to ESAM send instruction read information of vehicles---OBU provides response message GetSecure.rs to issuing equipment---because information of vehicles is ciphertext, Output rusults---distributed software shows and reads information of vehicles issuing equipment after to its deciphering, judging that whether it is wrong---secondary offering finishes, distributed software notice OBU discharges link and provides information---issuing equipment notice OBU discharges link SetMMT.rq+Evenreport---, and OBU provides distribution successfully to point out and proceed to park mode to issuing equipment.
As shown in Figure 4, activate testing process and be mainly that can remove the dismounting position in ESAM and detect OBU normal communication on vehicle, a mock trading also can be done in indivedual provinces, for example zero consumption checking (detaining 0 yuan) is done last inspection and can normally be used on vehicle to guarantee OBU before the formal use of OBU.Idiographic flow is:
Handheld device is sent broadcasting instructions search OBU-OBU and is waken up from dormant state, and---OBU provides VST to reply to handheld device, and---handheld device shows OBU individual information, and---handheld device prepares to remove a dismounting Transfer channel.rq, and---OBU sends instruction and obtain execution result---OBU returns to handheld device by execution result Transfer channel.rs---to ESAM, and handheld device judges whether to remove successfully, being to read information of vehicles Get Secure.rq,---OBU sends instruction and obtains execution result to ESAM, and---the information of vehicles Get Secure.rs after OBU encrypts to handheld device loopback---decipher and show that OBU provides information and proceeds to park mode to handheld device information of vehicles---handheld device notice OBU discharges link SetMMT.rq+Evenreport---by handheld device.
As shown in Figure 5, transaction flow is most crucial link in OBU application, is also the link of the problem that the most easily breaks down, and mainly refers to that the RSU of ETC track entrance or outlet and OBU carry out the process that data interaction realizes vehicle toll.Although track pattern is divided into entrance, outlet and opens three kinds, difference for OBU, the instruction that under different track patterns, antenna issues is distinguished to some extent, but protocol level there is no substantial difference.Idiographic flow is:
Lane system notified the antenna in RSU to stop transaction last time, and---antennae polling sends BST broadcasting instructions to OBU, and---OBU is waken up after entering antenna coverage areas, and---OBU provides the VST signal in entry communication region to antenna---day line drawing OBU information---, and lane system judges that whether OBU is legal, by antenna, to read information of vehicles Get Secure.rq(otherwise notice antenna termination transaction)---OBU sends instruction to ESAM and reads the information of vehicles after encryption, and---OBU is to antenna loopback information of vehicles Get Secure.rs, and------------antenna reads the IC-card information Transfer channel.rq of OBU, and---OBU sends instruction to IC-card---OBU is to antenna return response information Transfer channel.rs---, and antenna judges whether to run succeeded the continuous business of lane system notice antenna lane system recording information of vehicles antenna deciphering information of vehicles, to consume Transfer channel.rq(otherwise lane system stops conclude the business and provides alarm also no through traffic)---OBU sends instruction to IC-card---OBU is to antenna return response information Transfer channel.rs---, and antenna judges whether Transaction Success, to discharge link (otherwise lane system stops conclude the business and provides alarm also no through traffic) SetMMT.rq+Evenreport---OBU provides information and proceeds to park mode to antenna, after lane system Transaction Success, notify track to let pass simultaneously---lane system judges whether vehicle has rolled track away from, to continue to send broadcasting instructions (otherwise continuing judgement).
Embodiment bis-:
As shown in Figure 6, the present embodiment provides OBU in transaction flow, to realize a kind of idiographic flow of fault diagnosis, mainly comprises the following steps:
Step S601:OBU is waken up after entering the antenna coverage areas of RSU.
Step S602: system and outside fetch equipment are carried out to initialization.
Step S603:OBU judges whether Transaction Success, is to go to step S606, otherwise goes to step S604.
Step S604:OBU generates corresponding failure record structure rr_record, as a carrying, this carries out the record of failure information to each structure, comprising fault type failure command, unsuccessfully reply, also comprise call number and check code, call number of every record adds 1 automatically.
Step S605: store the value of rr_record in the storage area of OBU, carry out crc data check simultaneously and avoid memory period data to be tampered, also can back up record as required.
Step S606: record the information that runs succeeded.
Step S607: store the information that runs succeeded in the storage area of OBU.
Step S608: after information storage, OBU proceeds to park mode.
Certainly, in other flow processs, similar with above step, once carrying out, OBU in the process of a certain instruction, there is carrying out failed situation, OBU just records execution failure information and store the form by failure record structure, so as in the process of fault diagnosis as diagnosis basis.
Embodiment tri-:
As shown in Figure 7, the present embodiment provides and OBU has been carried out in the processes such as fault diagnosis, detection, utilizes outside fetch equipment to read the step of the execution failure information of OBU storage, mainly comprises following flow process:
First step S 701:OBU receives information read requests after being connected with outside fetch equipment by modes such as wireless communication interface, serial ports, emulators.
Step S702: first outside fetch equipment reads total number of record, i.e. instruction carry out unsuccessfully from number of times, and the failure record structure of getting call number N=1 starts to read its specifying information.
Step S703: read N the specifying information in structure.
Step S704: carry out CRC data check, and judge that whether verification is successful, is to enter step S705, otherwise enters step S708.
Step S705: read the prompting of information to OBU loopback.
Step S706: get call number N+1.
Step S707: whether judgement record runs through, is to enter step S711, reads next record otherwise get back to step S703.
Step S708: the record that reads backup.
Step S709: carry out CRC data check, and judge that whether verification is successful, is to enter step S705, otherwise enters step S710.
Step S710: the information void in whole of this record is set, is about to data and is set to full 0.
Step S711:OBU proceeds to other logical process steps, for example, can proceed to dormant state.
Outside fetch equipment obtains after these records, can to the fault of OBU, carry out accurately according to specifying information wherein, diagnosis fast, certainly also can coordinate the log information of assistant software, determine the reason that causes fault, and provide valuable clue for reprocessing, not only be conducive to improve the speed of reprocessing of OBU, guarantee to reprocess quality, and the technician of being convenient to OBU manufacturer is by the execution failure information recording in assessment and analysis OBU, improve the quality of OBU, thereby avoid or reduce OBU when carrying out dependent instruction, again occurring relevant fault from now on, effectively reduce failure rate.
For example in the dependent instruction of OBU following link in carrying out each flow process, may occur failure, the situation that each instruction leads to the failure may have following several, but only has the failure that a kind of situation causes first to occur, software only records situation about occurring at first.
Instruction one: [OBU wakes up from dormant state]
Situation one: OBU is waken up rear clock handoff failure:
After waking up, situation two: OBU can not receive instruction
Instruction two: [OBU provides VST and replys]
Situation one: BST resolves unsuccessfully
Situation two: loopback VST failure
Instruction three: [reading information of vehicles Get Secure.rs]
Situation one: instruction is resolved unsuccessfully
Situation two: ESAM answer failed
Instruction four: [the Transfer channel.rs such as system information, clear dismounting position are replaced, changed to key]
Situation one: instruction is resolved unsuccessfully
Situation two: ESAM answer failed
Situation three: IC-card answer failed
Instruction five: [information after establishing a communications link receives]
Situation one: information receive time-out
Situation two: CRC check failure
Situation three: signal intensity is low
Instruction six: [link release] from OBU bring in see every do not go to this link all think Fail Transaction.
Situation one: do not receive SetMMI
Situation two: do not receive EvenReport
For the execution failure information of above all kinds of situation records, technician can be according to following table to the fault type that may occur, analyzing failure cause, and proposition solves the way of fault:
Embodiment tetra-:
As shown in Figure 8, the present embodiment provides a kind of OBU that realizes above each embodiment, and the OBU fault diagnosis system being comprised of this OBU and exterior read-write equipment, and OBU mainly comprises carrying out failure information memory module 10 and carrying out failure information provides module 20:
Wherein, carry out failure information memory module 10 for specify the process of flow process in OBU operation, when if instruction is carried out unsuccessfully, corresponding execution failure information is recorded in to the storage area in OBU, for example carry out failure information memory module 10 and can comprise structure generation unit, be used for utilizing Software Create failure record structure, carry out failure information and comprise fault type, failure command, failed at least one in replying, certainly also can comprise call number and check code etc.
Carrying out failure information provides module 20 for according to specific needs, and execution failure information is offered to outside fetch equipment.
It will be appreciated by those skilled in the art that, in above-mentioned embodiment, all or part of step of the whole bag of tricks can come instruction related hardware to complete by program, this program can be stored in a computer-readable recording medium, and storage medium can comprise: ROM (read-only memory), random access memory, disk or CD etc.
Above content is the further description of the application being done in conjunction with concrete embodiment, can not assert that the application's concrete enforcement is confined to these explanations.For the application person of an ordinary skill in the technical field, not departing under the prerequisite of the application's design, can also make some simple deduction or replace, all should be considered as belonging to the application's protection domain.
Claims (10)
1. a method for diagnosing faults for board units, is characterized in that, comprises the following steps:
Carry out failure information storing step: board units is specified in the process of flow process in operation, if instruction is carried out unsuccessfully, corresponding execution failure information is recorded in to the storage area in described board units;
Carry out failure information step is provided: board units offers outside fetch equipment by described execution failure information.
2. the method for claim 1, is characterized in that, the concrete mode that records described execution failure information comprises: described execution failure information comprises fault type, failure command, failed at least one in replying.
3. method as claimed in claim 2, is characterized in that, the form that records of described execution failure information is failure record structure, array, function, variable or pointer.
4. method as claimed in claim 2, is characterized in that, described execution failure information also comprises call number, records after described execution failure information at every turn, and the call number of the described execution failure information of record adds 1 automatically next time.
5. method as claimed in claim 2, is characterized in that, records in the process of described execution failure information at every turn, also described execution failure information is carried out to data check, and is recorded in described execution failure information after generating check code.
6. method as claimed in claim 2, is characterized in that, records in the process of described execution failure information at every turn, also described execution failure information is backed up.
7. the method as described in any one in claim 1-6, is characterized in that, described appointment flow process comprises at least one of once issuing in flow process, secondary offering flow process, activation testing process, transaction flow.
8. the method as described in any one in claim 1-6, is characterized in that, described execution failure information storing step also comprises: if instruction runs succeeded, the information that runs succeeded of correspondence is also recorded in to the storage area in board units.
9. a board units, is characterized in that, comprising:
Carry out failure information memory module: for specify the process of flow process in board units operation, if when instruction is carried out unsuccessfully, corresponding execution failure information is recorded in to the storage area in board units;
Carry out failure information module is provided: for described execution failure information is offered to outside fetch equipment.
10. a fault diagnosis system for board units, is characterized in that, comprises board units claimed in claim 9, and described outside fetch equipment.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210307643.1A CN103630375B (en) | 2012-08-27 | 2012-08-27 | A kind of method for diagnosing faults of board units, board units and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210307643.1A CN103630375B (en) | 2012-08-27 | 2012-08-27 | A kind of method for diagnosing faults of board units, board units and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103630375A true CN103630375A (en) | 2014-03-12 |
| CN103630375B CN103630375B (en) | 2017-06-23 |
Family
ID=50211655
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210307643.1A Active CN103630375B (en) | 2012-08-27 | 2012-08-27 | A kind of method for diagnosing faults of board units, board units and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103630375B (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108171969A (en) * | 2016-12-07 | 2018-06-15 | 罗伯特·博世有限公司 | For in terms of mistake check for detect parking stall seizure condition sensing system scheme and equipment |
| CN109920073A (en) * | 2019-02-20 | 2019-06-21 | 深圳成谷科技有限公司 | A kind of ETC method of commerce and the roadside unit antenna for ETC transaction |
| CN110427010A (en) * | 2019-05-27 | 2019-11-08 | 苏州思卡信息系统有限公司 | A kind of vehicle-mounted OBU unusual condition warning system and method |
| CN111158943A (en) * | 2019-12-20 | 2020-05-15 | 航天信息股份有限公司 | Fault diagnosis method and apparatus, storage medium, electronic device |
| CN111741489A (en) * | 2020-06-09 | 2020-10-02 | 福耀玻璃工业集团股份有限公司 | OBU fault detection method, OBU device and OBU fault detection system |
| CN117914347A (en) * | 2024-03-19 | 2024-04-19 | 广州铭创通讯科技有限公司 | DSRC switch on-off control method and device based on abnormal optimization of control signals |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1304487A (en) * | 1999-05-11 | 2001-07-18 | 罗伯特·博施有限公司 | Diagnostic test device for motor vehicles which comprises portable testing apparatus |
| CN101031455A (en) * | 2004-08-24 | 2007-09-05 | 夏普株式会社 | Display system |
| CN101136069A (en) * | 2007-09-18 | 2008-03-05 | 深圳市金溢科技有限公司 | Issuing method of ETC electronic label |
| CN102184576A (en) * | 2011-03-09 | 2011-09-14 | 东南大学 | Vehicle-mounted unit of 5.8 GHz electronic toll collection system |
| CN202049350U (en) * | 2011-03-09 | 2011-11-23 | 东南大学 | Vehicle-mounted unit of 5.8GHz ETC system |
-
2012
- 2012-08-27 CN CN201210307643.1A patent/CN103630375B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1304487A (en) * | 1999-05-11 | 2001-07-18 | 罗伯特·博施有限公司 | Diagnostic test device for motor vehicles which comprises portable testing apparatus |
| CN101031455A (en) * | 2004-08-24 | 2007-09-05 | 夏普株式会社 | Display system |
| CN101136069A (en) * | 2007-09-18 | 2008-03-05 | 深圳市金溢科技有限公司 | Issuing method of ETC electronic label |
| CN102184576A (en) * | 2011-03-09 | 2011-09-14 | 东南大学 | Vehicle-mounted unit of 5.8 GHz electronic toll collection system |
| CN202049350U (en) * | 2011-03-09 | 2011-11-23 | 东南大学 | Vehicle-mounted unit of 5.8GHz ETC system |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108171969A (en) * | 2016-12-07 | 2018-06-15 | 罗伯特·博世有限公司 | For in terms of mistake check for detect parking stall seizure condition sensing system scheme and equipment |
| CN108171969B (en) * | 2016-12-07 | 2022-04-01 | 罗伯特·博世有限公司 | Solution and device for checking a sensor system for detecting the occupancy state of a parking space in terms of errors |
| CN109920073A (en) * | 2019-02-20 | 2019-06-21 | 深圳成谷科技有限公司 | A kind of ETC method of commerce and the roadside unit antenna for ETC transaction |
| CN110427010A (en) * | 2019-05-27 | 2019-11-08 | 苏州思卡信息系统有限公司 | A kind of vehicle-mounted OBU unusual condition warning system and method |
| CN111158943A (en) * | 2019-12-20 | 2020-05-15 | 航天信息股份有限公司 | Fault diagnosis method and apparatus, storage medium, electronic device |
| CN111158943B (en) * | 2019-12-20 | 2024-03-22 | 航天信息股份有限公司 | Fault diagnosis method and device, storage medium and electronic equipment |
| CN111741489A (en) * | 2020-06-09 | 2020-10-02 | 福耀玻璃工业集团股份有限公司 | OBU fault detection method, OBU device and OBU fault detection system |
| CN111741489B (en) * | 2020-06-09 | 2022-11-08 | 福耀玻璃工业集团股份有限公司 | OBU fault detection method, OBU device and OBU fault detection system |
| CN117914347A (en) * | 2024-03-19 | 2024-04-19 | 广州铭创通讯科技有限公司 | DSRC switch on-off control method and device based on abnormal optimization of control signals |
| CN117914347B (en) * | 2024-03-19 | 2024-05-31 | 广州铭创通讯科技有限公司 | DSRC switch on-off control method and device based on abnormal optimization of control signals |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103630375B (en) | 2017-06-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103630375A (en) | Fault diagnosis method and system of on-board unit and on-board unit | |
| CN101714263B (en) | Vehicle management method and management system for electronic toll collection lane | |
| EP0798668B1 (en) | An automatic toll charging system and a vehicle-mounted unit used in the automatic toll charging system | |
| CN112152673B (en) | CPC card transaction testing method and device under antenna interference | |
| CN102486884B (en) | Point-of-sale (POS) machine with use region limitation function and method thereof | |
| CN108711197A (en) | The method and apparatus that a kind of power to board units is adaptively adjusted | |
| CN102789654A (en) | Method and system for protocol conformance testing of electronic toll collection core equipment | |
| CN112016520A (en) | AI-based traffic violation voucher generation method, device, terminal and storage medium | |
| KR20130072578A (en) | Automatic fare collection device with anti-dismantling the vehicle control system and automatic fare collection devices using the same method for preventing dissolution | |
| CN105243706A (en) | Control method, control device and control system of entrance and exit of vehicles in garage | |
| CN107833296A (en) | A kind of activation OBU method and OBU | |
| CN112152674B (en) | Method and device for testing CPC card pre-reading mechanism under antenna interference | |
| CN100433071C (en) | System and method for automatically collecting vehicle information | |
| CN110827429B (en) | Truck ETC lane PSAM card blacklist checking method and device | |
| CN111105512B (en) | Truck ETC lane service data processing method, equipment and storage medium | |
| CN105488853B (en) | The method of park pricing and its mark label of parking, inspection terminal and server | |
| JP5295716B2 (en) | Automatic ticket gate and automatic ticket gate system with safe mode | |
| CN105825679A (en) | Method for realizing rapid and remote on-line locking of violation special vehicle | |
| CN212473388U (en) | Anti-disassembly type vehicle-mounted unit system | |
| CN112235015B (en) | CPC card pre-reading mechanism test method and device | |
| CN111038441A (en) | Anti-disassembly type vehicle-mounted unit system and application method | |
| CN109285227A (en) | RFID road-surface concrete service management platform | |
| CN113298965A (en) | Method and system for preventing PSAM card locking of ETC lane system | |
| CN115731628A (en) | ETC traffic monitoring method, road side unit, vehicle-mounted unit and storage medium | |
| CN201681423U (en) | Rail traffic ticket processing intelligent terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C53 | Correction of patent of invention or patent application | ||
| CB02 | Change of applicant information |
Address after: Nanshan District Keyuan Road Shenzhen city Guangdong province 518057 Tsinghua building A building 12 layer Applicant after: SHENZHEN GENVICT TECHNOLOGY CO., LTD. Address before: Nanshan District Keyuan Road Shenzhen city Guangdong province 518057 Tsinghua building A building 12 layer Applicant before: Shenzhen Jinyi Technologies Co., Ltd. |
|
| COR | Change of bibliographic data |
Free format text: CORRECT: APPLICANT; FROM: SHENZHEN JINYI TECHNOLOGIES CO., LTD. TO: SHENZHEN GENVICT TECHNOLOGY CO., LTD. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |