JP6842010B2 - Systems and programs - Google Patents

Description

The present invention relates to a system, a program, and the like.

For example, a drive recorder that records vehicle status information (for example, forward image, speed, acceleration, etc.), which is information acquired by a vehicle, on a recording medium is a vehicle for transportation such as a truck, or a commercial vehicle such as a taxi or a bus. It is widely installed in vehicles, and is also being installed in general vehicles.

Some drive recorders constantly record vehicle status information, for example, when the vehicle is running, and others record vehicle status information at any time for a certain period before and after an accident or sudden braking.

The vehicle status information is recorded by the drive recorder on a removable recording medium such as a memory card such as an SD card that can be attached to and detached from the drive recorder. In many cases, the analysis of vehicle status information is generally performed by the processing of viewer application software (hereinafter referred to as a viewer application) that operates on a personal computer.

At the time of analysis, the recording medium is removed from the drive recorder of the vehicle, and the recording medium is inserted into a memory card reader connected to a personal computer for analysis such as an office. The personal computer reads the vehicle status information of the recording medium inserted into the memory card reader by the processing of the viewer application, and visualizes and displays the information on the screen (for example, Patent Document 1). As a result, it is possible to confirm and analyze the vehicle status information based on the information visualized on the screen.

JP 2011-114850

By the way, there are various recording formats on a recording medium that can be read by a personal computer. For example, a recording format that can be read by the standard functions of the computer operating system and a recording format that cannot be read by the standard functions of the computer operating system but can be read by executing a dedicated reading program on the operating system. There is something. For example, Microsoft's Windows (registered trademark; the same applies hereinafter) supports recording formats such as FAT and NTFS (hereinafter also referred to as file systems) with standard functions, but for example, recording formats such as ext4 are used. Is not supported by standard.

As the recording format of the recording medium for recording by the drive recorder, it is common to record in a recording format that can be read by the operating system in which the viewer application operates as a standard function. For example, if the operating system on which the viewer application operates is Windows, a type of FAT file system (for example, FAT32), which is a standard format that can be read by various devices, is used.

However, in a configuration in which the drive recorder records information on a recording medium in a recording format that can be read by the operating system as a standard function, the file recorded by the operating system's own file management software can be deleted, or the operating system can use it. With other software that works, it is easy to read and rewrite the information recorded by the drive recorder.

Therefore, if there is a request to prevent such rewriting of information recorded by the drive recorder such as vehicle status information using other software, the recording medium cannot be read by the standard function of the operating system. It is conceivable that the drive recorder information such as vehicle status information is stored in all or part of the recording area of the above.

However, some recording media containing a recording format area that cannot be read by such standard functions of the operating system are required to have the administrator authority of the operating system in order to read the recording medium by the security function of the operating system or the like. In such a case, if the user of the viewer application is a user who does not have such administrator authority of the operating system, the information recorded by the drive recorder such as vehicle status information is read by the viewer application and visualized. I found the problem that I couldn't.

Therefore, an object of the present invention is to solve such a problem and to provide a system and a program that are easy to use even for a user who does not have the administrator authority which is a predetermined authority in the operating system.

(1) When an application program having a function of reading information stored by a drive recorder in a predetermined area whose reading is not supported by a standard function of the operating system is operated, a request for administrator authority is displayed by the operating system. The system should have a function to control it so that it does not exist.

In this way, it is possible to make it difficult to rewrite the information recorded by the drive recorder, and to request the operating system administrator authority when operating the application program having the function of reading the information recorded by the drive recorder. Even a user who is a user (for example, a general user) who does not have the administrator authority of the operating system can read and use the information recorded by the drive recorder by this application program.

A predetermined area whose reading is not supported by the standard operating system function may be, for example, a recording format area which is not supported by the standard operating system function.

As for the operation, for example, it is preferable that the application program is running, and in particular, the process for the application program to read the information stored by the drive recorder in a predetermined area whose reading is not supported by the standard function of the operating system. It is good to prepare for the occasion. For example, the operation of the application program may be configured to include the access of other programs other than the operation of the application program. Desirably, the configuration is such that the operating system does not display the request for the administrator authority of the operating system only when the application program is accessed.

The operating system administrator authority may be the authority required to read the information stored by the drive recorder in a predetermined area where reading is not supported.

Do not display a request for administrator privileges by the operating system when operating an application program that has the ability to read information stored by the drive recorder in a given area that is not supported by standard operating system functions. The system may be controlled and provided with a function for reading and notifying the information stored by the drive recorder in a predetermined area whose reading is not supported by the standard function of the operating system.

(2) The predetermined area whose reading is not supported by the standard function of the operating system is a predetermined area in the recording medium, and the function of controlling not to display the request for the administrator authority of the operating system is specific. It is preferable to have a function to control not to display the request of the administrator authority of the operating system at the time of reading by the reading device.

In this way, the recording medium recorded by the drive recorder does not require operating system administrator authority to be read by this specific reader, and a reader other than this specific reader is required. Allows you to maintain operating system administrator privileges. For example, if the entire operating system is configured to control so that the operating system does not request the administrator authority when reading from such a recording medium, the administrator authority is widely unnecessary. On the other hand, if the operating system controls each recording medium so that it does not request administrator authority, it is necessary to set each medium so that it does not request administrator authority. Every time the media increases, it becomes necessary to ask them to grant authority. According to this configuration, such a problem can be solved. In particular, it is preferable to control the display of the request for the administrator authority of the operating system when reading by a reading device other than a specific reading device.

The recording medium may be, for example, a medium that can be carried between the drive recorder and the computer having this system. For example, it may be a USB memory or the like, but it is particularly preferable to use a card-type recording medium, for example, an SD card or the like.

The reading device may be, for example, a card reader or the like. In this way, even a general user can view the information by the application program only when the recording medium is read by a specific card reader.
The reading device may be a reading device configured to be detachable from a computer equipped with this system. For example, a USB-connected card reader or the like may be used.

A plurality of readers may be detachably configured for a computer equipped with this system, and operating system administrator authority is required when reading with a specific reader among such multiple readers. It is good to control so that the request is not displayed. Further, for example, when a reading device built in a computer equipped with this system and an external reading device are provided, it is preferable to have a function of using the built-in device as a specific reading device. By doing so, it is possible to reduce the possibility that a malicious third party or the like can read the external reader without administrator authority.

Whether or not it is a specific reading device may be determined based on, for example, identification information of the type of reading device, identification information of an individual reading device, and the like. It is preferable to use the identification information that can be acquired by the computer of the system and the operating system. For example, if the card reader is a USB connection and the operating system is Windows 8, it is necessary for each type of card reader (or, for example, the operating system). Since the card reader can be identified for each type of device driver to be used, it is preferable to use the identification information of the type of reader.

However, with such a configuration, problems such as the inability to identify each individual in the reading device identified as the same type may occur. Therefore, the control so as not to display the request for the administrator authority of the operating system when reading with a specific reading device is, for example, a reading device physically connected to the computer on which the operating system is executed. The configuration may be based on the physical identification information of the reading device for identifying the above, but the following is particularly preferable.

(3) The control for preventing the display of the request for the administrator authority of the operating system when reading with the specific reading device is a reading physically connected to the computer on which the operating system is executed. It is preferable to have a function to perform based on both the physical identification information of the reading device for identifying the device and the logical identification information recognized and assigned by the reading device by the operating system.

By doing so, for example, when a plurality of devices having the same physical identification information of the reading device are connected, the individual reading device that does not display the request for administrator authority more reliably can be identified. When reading with the reader, the request for operating system administrator authority is no longer displayed, and the request for administrator authority is not displayed even though the individual has the same physical identification information as the reader. It is possible to identify a non-target individual and display a request for operating system administrator authority when reading by that individual.

For example, a drive letter may be used as the logical identification information to which the operating system is assigned to the reader. In this way, even when it is difficult to identify an individual from the identification information possessed by the reader, it is possible to more reliably determine whether or not the individual is an individual of the reader to which the administrator authority has been granted. Will be.
(4) It is preferable to have a function for allowing the user to select the specific reading device from a plurality of reading devices connected to a computer having the system.

In this way, the user can determine the reading device to be controlled so as not to display the request for the administrator authority of the operating system from among the plurality of reading devices connected to the computer. The reading device not selected by the user may be configured not to be the specific reading device.

As a function for allowing the user to select the specific reading device from the plurality of reading devices connected to the computer having the system, for example, the plurality of reading devices connected to the computer having the system are identified. The information to be used is acquired from the reading device and displayed in a list or the like, and the reading device selected by the detected user's operation is selected as a specific reading device from the display of the list or the like. It is preferable to have a function to determine that.

(5) The function for controlling the operating system not to request the administrator authority rewrites the information in the information area used to determine whether or not the operating system requests the administrator authority. It should be a function.

In this way, it is easy to develop a program that the operating system executes with administrator privileges, such as developing a device driver for the operating system, without adding any processing that prevents the operation that requires administrator privileges. it can.

The information in the information area used by the operating system to determine whether or not to request administrator authority may be rewritten to information that controls the operating system not to request administrator authority. For example, in the case of Microsoft Windows 8, it is preferable to have a function of rewriting the information in the registry area used for determining whether or not to request administrator authority.

(6) The information area used for determining whether or not the operating system requests administrator authority may be an area that is not erased even if the operating system is shut down.

In this way, the request for administrator authority is not displayed only by executing the program that rewrites this information area once. After that, for example, prior to the execution of the application program, it is not necessary to re-execute the program that rewrites this information area one by one.

(7) The function of rewriting the information area used by the operating system to determine whether or not to request the administrator authority is a function executed before the function of reading the information recorded by the drive recorder. It is good to have.

In this way, administrator privileges are required when executing the function to read the information recorded by the drive recorder, and it becomes necessary to call a person who has administrator privileges for the operating system. It is possible to prevent the problem that the function of reading the information recorded by the drive recorder cannot be realized immediately when the information recorded by the drive recorder is to be read.

A configuration in which the function of rewriting the information area used by the operating system to determine whether or not to request administrator privileges is executed before the function of reading the information recorded by the drive recorder. For example, when preparing for the operation of an application program having a function of reading information stored by a drive recorder in a predetermined area for which reading is not supported by standard operating system functions, the state of the storage area is set. First check to determine if the operating system makes an administrator request before the ability to read the information recorded by the drive recorder if it is in a state that requires administrator privileges. It is advisable to perform a process of rewriting the information area to be used. The preparation for the operation may be, for example, the first start of the application program, but may be particularly the installation of the application program.

In addition, the operating system is a separate application program from the application program (hereinafter referred to as the information reading application) that has the function of reading the information stored by the drive recorder in a predetermined area whose reading is not supported by the standard functions of the operating system. Configure a setting application program (hereinafter referred to as the setting application) that has a function to rewrite the information area used to determine whether to request administrator privileges, first execute the setting application, and then next. It is preferable to configure the information reading application to be executed.

(8) A program for realizing a computer with a function of rewriting an information area used for determining whether or not the operating system requests administrator authority, and a function of reading information recorded by the drive recorder. It is advisable to configure the application program with the above as a separate executable file.

In this way, the computer can realize the function of rewriting the information area used to determine whether or not the operating system requests the administrator authority only for the computer that does not want to request the administrator authority. In addition to making it easier to execute the program, it is also possible to prevent the program from being installed on computers that want to require administrator privileges, which enhances security.

(9) The function of reading the information recorded by the drive recorder by the operation of the computer by the application program is configured to require the viewing authority of the information recorded by the drive recorder, which is different from the administrator authority of the operating system. You should do it.

Administrator privileges for a computer's operating system are usually granted to the administrator of the computer. On the other hand, it has been found that the authority to view the information recorded by the drive recorder is not always given to the computer administrator. Therefore, by providing a function to read the information recorded by the drive recorder with a function to request the authority to view the information recorded by the drive recorder, which is different from the administrator authority of the computer operating system, both are designated as different persons. Things can be easily realized.

(10) When an application program having a function of reading information stored by a drive recorder in a predetermined area whose reading is not supported by a standard function of the operating system is operated, the operating system requires the administrator authority of the operating system. It is preferable to have a function of disabling the function for controlling not to display.

In this way, the operating system can display a request for the administrator authority of the operating system. For example, it is possible to return to the state in which the request for the administrator authority of the operating system is not displayed once by the operating system, and then to the state in which the request for the original administrator authority is displayed.

For example, the function to control the operating system not to request administrator authority is the function to rewrite the information in the information area used to determine whether the operating system requests administrator authority. In some configurations, the information in the information area used by the operating system to determine whether to request administrator privileges is rewritten to information that controls the operating system not to request administrator privileges. In such cases, it is advisable to provide a function to convert this information into information for requesting administrator authority.

(11) Operating system When the application program having the function of determining the version of the system and reading the information stored by the drive recorder in a predetermined area whose reading is not supported by the standard function of the operating system is operated, the operating system concerned In the case of a version in which the request for the administrator authority of the operating system is not displayed by the operating system, it is preferable to configure the configuration so that the operating system does not control the request for the administrator authority of the operating system.

In particular, due to recent operating system security enhancements, there are cases where previous versions of operating systems did not require administrator privileges in such cases, but newer versions of operating systems require administrator privileges. I found that it was coming.
(12) For example, it may be configured as a program for realizing the functions described in (1) to (11) above in a computer.

According to the present invention, it is possible to provide an easy-to-use system, program, and the like even for a user who does not have administrator authority, which is a predetermined authority in an operating system.

An explanatory diagram for explaining the transfer of an SD card between a drive recorder and a personal computer. Explanatory drawing explaining an example of installation of a drive recorder in a vehicle. The block diagram explaining the electrical schematic configuration example of a drive recorder. The block diagram explaining the electric schematic configuration example of a personal computer and a device connected to a personal computer. An explanatory diagram illustrating an example of a screen displayed on a monitor by processing a personal computer by a program of the viewer application when the viewer application is executed. Explanatory drawing which shows an example of the request screen of the administrator authority which is displayed when there is no authority. Explanatory drawing which shows an example of the screen displayed by the authority change application. Explanatory drawing which shows an example of the screen displayed by the authority change application. Explanatory drawing which shows an example of the screen displayed by the authority change application. An explanatory diagram showing an example of a screen displayed by the permission change application. Explanatory drawing which shows an example of the screen displayed by the authority change application. Explanatory drawing which shows an example of the screen displayed by the authority change application. Explanatory drawing which shows an example of the screen displayed by the authority change application. Explanatory drawing which shows an example of the screen displayed by the authority change application. Explanatory drawing which shows an example of the screen displayed by the authority change application. Explanatory drawing of the dialog box for setting the sensitivity of the drive recorder which is an example of the function of the viewer application.

Hereinafter, as an embodiment of the present invention, the present system will be described based on a personal computer and an example realized by processing a program executed on the personal computer.

As shown in FIG. 1, an SD card mounted on the drive recorder 1 and recorded with vehicle status information by the drive recorder 1 was removed from the drive recorder 1 and mounted on the SD card reader / writer 36 connected to the personal computer 35. In this state, the configuration performed by the personal computer 35 is an embodiment of this system.
Windows 8 is operating as an operating system on the personal computer 35.

The SD card is a card with a capacity of 16 GB, and the first 1 GB is supported by the standard functions of the Windows 8 operating system running on the personal computer 35. FAT32 (hereinafter referred to as the first format) partition (hereinafter referred to as the first partition). ), And the remaining 15 GB is a partition (hereinafter referred to as a second partition) of a format (referred to as a second format) that is not supported by a standard function that is neither FAT32 nor NTFS but is supported by the drive recorder 1.

In the area of the first format of the first partition, for example, as shown in the display example of FIG. 5, an installer file containing an executable file of a viewer application which is an application program for displaying vehicle status information on the monitor of the personal computer 35. Is recorded. The volume label of the first partition is set to "DRIVE REC1" and recorded as information for identifying that the SD card is for this system.

As shown in FIG. 2, the drive recorder 1 has a mounting member such as a double-sided tape attached to the windshield at a position on the passenger seat side adjacent to the room mirror 4 near the center in the left-right direction on the upper part of the windshield 3 of the vehicle. It is attached and fixed. The drive recorder 1 is fixed so that the lens of the camera is directed in the direction of photographing the front of the vehicle. The drive recorder 1 is connected to the cigar socket 5 and the power cable 6, and receives power from the vehicle side when the accessory power supply of the vehicle is on.

FIG. 3 is a diagram showing a schematic electrical configuration of the drive recorder 1. As shown in FIG. 3, the drive recorder 1 includes a controller MC, a CCD camera 13, an interface 33, a GPS receiver 24, an SD card reader 31, an acceleration sensor 15, a database 32, and the like. The controller MC includes an interface 33 that is connected to the CCD camera 13 and converts the video signal from the CCD camera 13 into a digital signal that can be input to the controller MC, an acceleration sensor 15, a GPS receiver 24, an SD card reader 31, and a database. 32 are connected respectively.

The controller MC is composed of a well-known CPU, a memory such as ROM and RAM, a timer, and a microcomputer having other peripheral circuits and the like. In the ROM of the controller MC, a GPS information processing program that saves the GPS information received by the GPS receiver 24 on the SD card, a video processing program that saves the image taken by the CCD camera 13 on the SD card, and an acceleration sensor 15 Various programs such as an acceleration recording program and an OS (Operation System) that store the detected acceleration information on an SD card over time are stored, and the controller MC realizes various functions by executing such programs.

The GPS receiver 24 detects the position information of the own vehicle at the current time based on the instruction of the controller MC. The detection timing is set to every second in this embodiment. The controller MC performs a position history recording process for storing the history of position information (hereinafter referred to as position history data) in the SD card via the SD card reader 31 every second. The position information is the time obtained based on the signal from the GPS satellite, the position of the own vehicle, the speed, the latitude, the longitude, the altitude, and the like. A process of recording the history of these various data based on signals from GPS satellites is performed. The acceleration sensor 15 is a 3-axis type sensor that detects acceleration and inclination in each of the three axes (X, Y, Z), and constantly outputs the detected value to the controller MC. The controller MC associates the acceleration information of the three axes with the time information every 10 ms and stores the acceleration information history (hereinafter referred to as acceleration history data) in the SD card via the SD card reader 31. Perform processing. The SD card reader 31 reads the data of the SD card inserted from the insertion slot 18 or updates the data of the SD card under the control of the controller MC. The database 32 is a non-volatile memory (for example, EEPROM) externally attached to the controller MC. The CCD camera 13 outputs the video information constantly shot to the controller MC via the interface unit 33 that performs digital conversion to be shot. The controller MC performs a constant recording process of storing the video information input via the interface unit 33 in the SD card via the SD card reader 31 as video information (hereinafter referred to as constantly recorded video data) associated with the time. Further, when the video information is temporarily stored in the memory (video for 20 seconds in this embodiment) and the acceleration detected by the acceleration sensor 15 corresponds to the acceleration corresponding to the shock at the time of the accident, before the impact is generated. Data (referred to as event recorded video data) that links the video information temporarily stored in 20 seconds and the video information for 20 seconds after the impact occurs and the information at that time is transmitted via the SD card reader 31. Performs event recording processing to be stored in the SD card.

By these processes by the drive recorder 1, the position history data, the acceleration history data, the constantly recorded video data, and the event recorded video data are stored in the second formatted area of the second partition in the SD card. Record.

The personal computer 35 is a general notebook personal computer on which Windows 8 operates, and FIG. 4 is a schematic configuration diagram illustrating a part thereof and a device connected to the personal computer 35. As shown in FIG. 4, the personal computer 35 includes an MPU (Micro Processing Unit) 37 which is a control device. ROM 38 and RAM 39 are connected to the MPU 37. A hard disk drive 40, a keyboard 42, a touch pad (not shown), and a monitor 45 are connected to the MPU 37 via corresponding interfaces (not shown). A mouse 43, a printer 44, and an SD card reader / writer 36 are connected to the USB port of the personal computer 35. The hard disk in the hard disk drive 40 stores Windows 8 (programs and data constituting the operating system), which is the operating system of the personal computer 35, and various application programs and data operating on Windows 8.

The user can start various programs by operating the touch pad or the mouse 43 (hereinafter referred to as the pointing device) and double-clicking the start icon of the application program, and can start various programs by using the functions of the operating system. The personal computer 35 can execute the processing by the application program, and the personal computer 35 can realize a predetermined function. Hereinafter, it is referred to as clicking the mouse 43, tapping the touch pad, pressing the enter key of the keyboard 42, and the like.

The user removes the SD card on which the data is recorded by the drive recorder 1 from the drive recorder 1 and attaches it to the SD card reader / writer 36 connected to the personal computer 35.
The operating system of the personal computer 35 accesses the SD card via the USB port by attaching the SD card to the SD card reader / writer 36.

The operating system recognizes the first partition of the first format supported by the standard features in the SD card and displays a list of files in it. As a result, the installer file for the viewer app is displayed in the list. If the viewer app is not installed yet, the user can double-click this installer file on the pointing device to have the operating system run it. When the installation is completed, the app for executing the viewer app will be displayed on the operating system.

If the viewer app has been installed or has already been installed, the user can launch the viewer app by double-clicking the viewer app icon displayed on the desktop of the monitor 45 by the operating system. The operating system detects the launch operation of the viewer app and launches the viewer app.

When the viewer application is started, the same folder reference dialog as shown in FIG. 10 is displayed. The user selects the drive corresponding to the drive in which the SD card is inserted from among these drives recognized by the displayed operating system. Here, it is assumed that the drive with the drive letter "i:" displayed as "DRIVE REC1" as the volume label is the drive in which the SD card is inserted. When the user's "DRIVE REC1 i:" pointing device detects a click or other selection and a "OK" button click or the like is detected, the viewer app remembers it in the second partition of the drive in the drive letter "i:". Request the operating system to access the recorded event recording video data. The operating system receives this request from the viewer app's processing and attempts to access the event recording video data stored in the second partition, but determines that the second partition is in a format that is not supported by default. Therefore, the information in the registry area used to determine whether or not to request the administrator authority prepared for each device of the card reader of this drive does not request the administrator authority. Determine if it is a value, and if it is not a value that prevents you from requesting administrator privileges, then whether the user account currently logged in to this operating system has administrator privileges. Is determined. If the user account does not have administrator privileges, it returns information to the viewer app that administrator privileges are required. The viewer application requests the operating system to display the operating system administrator authority request dialog as shown in FIG. On the other hand, if the user account has administrator privileges, access to the second partition area for the viewer app is allowed.

The administrator authority request dialog is a dialog that prompts the user to enter the user name and password of the administrator account. Here, if the user of the viewer application enters the user name and password of the administrator account and a click of "Yes" is detected, the operating system will perform a combination of the entered user name and password. Determines if it matches the one registered in the operating system as an administrator account. If they match, the viewer app is allowed access to the second partition area, while if they do not match, the viewer app is not allowed access to the second partition area.

The viewer app determines whether or not the operating system system has given permission to access the area of the second partition, and if not, an error dialog similar to that shown in FIG. Is displayed and a click of "OK" is detected, the viewer application is closed. Unless the user name and password of the administrator account are entered in this way, the data stored in the second partition area cannot be displayed by the viewer application.

Note that the information in the registry area used to determine whether or not to request the administrator authority prepared for each device of the card reader of this drive described above does not request the administrator authority. The information in the registry area used to determine whether or not to request the administrator authority prepared for each device of the card reader of this drive in determining whether or not the value is set to If it is set to not request administrator privileges, it does not determine whether the user account currently logged in to this operating system has administrator privileges, but has administrator privileges. It does not return information that administrator privileges are required for the viewer application of. As a result, even a user without administrator authority can obtain access permission and continue the operation of this application.

The viewer app has a program that provides access to areas in the second format. The program may be configured to access areas of its own format, but access to file systems in formats not supported by the Windows standard but supported by other existing operating systems. You may want to incorporate a program for this.

If permission is obtained, the viewer app will access the data stored in the second partition area using its own program for accessing the file system in the second format. , The position history data, the acceleration history data, the constantly recorded video data, and the event recorded video data recorded by the drive recorder 1 are read into the second formatted area of the second partition in the SD card. Perform the process of displaying with.

FIG. 5 is an example of a viewer screen displayed on the monitor 45 by this process. A menu bar 52 for executing various operations is arranged at the upper position of the viewer screen 51. In order from the top to the left of the menu bar 52, the video display area 53 for displaying the reproduced video of either the constantly recorded video data or the event recorded video data stored in the SD card, and the speed in the position history data. Travel speed display area 55 for reproducing and displaying information, acceleration display area 56 for reproducing and displaying acceleration information in acceleration history data, latitude / longitude display area 57 for reproducing and displaying latitude / longitude information in position history data, acceleration A video drive button that is above the history display area 59 and has buttons for rewinding, cueing, reverse playback, pausing, playing, final forward, and fast forward in order from the left, and 20 seconds before and after the time when the acceleration history data is played back. An acceleration history display area 59 for reproducing and displaying the accelerations of the three axes in a broken line graph is arranged, and a playlist 60 and a map area 61 are arranged in order from the top in the lower right direction of the menu bar 52. It should be noted that the playback display of any area is synchronized with the same time information included in each data and displayed for playback (hereinafter, synchronizing and playing back these information is referred to as synchronous playback).

A list of event recorded video data is displayed in the playlist 60. Since this list is recorded as a group (hereinafter referred to as an event unit) of one event recorded video data (40 seconds before and after the impact occurs in this embodiment), the start time of each group (event unit). Display information. Each part displaying the time information is a button, and the user sees the time of each event displayed in the playlist 60 and clicks the button of the event to be played.

By the process, the viewer application starts synchronous playback of the event clicked by the user. The image displayed first at this time is a still image of the event recorded video data at the time when it is determined that the event has occurred. The captured image is reproduced by detecting the operation of the image drive button, and along with the reproduction, the time data corresponding to the image is displayed in the traveling speed display area 55, the acceleration display area 56, and the latitude / longitude display area 57, respectively. Is displayed, and the map area 61 is displayed with a map of the surrounding area including the point where the image was taken at that time. The acceleration history display area 59 displays the acceleration history in the three-axis directions of the captured image for a time (40 seconds in total), and the acceleration position of the time currently displayed in the image display area 53 is displayed vertically. It is plotted as a bar.

By operating the video drive button, the user can display a still image in the video display area 53 at an arbitrary position of the captured image of the file for 40 seconds, and further display a moving image arbitrarily in 40 seconds. it can. When displaying a moving image, the display of the traveling speed display area 55, the acceleration display area 56, the latitude / longitude display area 57, the acceleration history display area 59, and the map area 61 also change in synchronization with the movement. When the press of the "close" button under the playlist 52 is detected, the video display area 53 is switched to a state in which the recorded video data is always displayed, and the video is played back from an arbitrary position by operating the video drive button. It also has a function to do.
In this state of having administrator authority, the data recorded in the drive recorder 1 can be reproduced and displayed on the SD card.

However, as mentioned above, if you start the viewer app without logging in to the operating system with an account with administrator privileges, the administrator privilege request dialog is usually displayed, prompting you to enter the user name and password of the administrator account. Be done.

For example, in a company organization, the administrator authority of the operating system of a personal computer is only a specific person who is authorized as a so-called system administrator, and there are cases where the user of the viewer application does not have the administrator authority. ..

To prevent users from being asked for administrator privileges, for example, prior to installing the viewer app described above, the system administrator executes the permission change app described below to access the second partition by the viewer app. At this time, it is possible to prevent the administrator authority request dialog from being displayed.

The authority change application is stored in the USB memory and distributed to the system administrator. The system administrator inserts this USB memory into the USB port of the personal computer 35. The operating system recognizes this USB memory and displays an icon for starting the authority change application on the monitor 45.

The system administrator double-clicks this icon to start the permission change application (application program executed on the operating system).
The operation of the authority change application will be described with reference to FIGS. 7 to 15.

FIG. 7 is a confirmation screen to be displayed first when the authority change application is executed. On this confirmation screen, give the user who does not have the administrator authority the authority to display the data by the viewer application, and the system administrator can use this application with the operating system administrator authority. It needs to be executed, it may affect other software, and I want you to know the information of the device connected to this computer (not shown, but especially SD card reader / writer). It is good to display that you want to know the information of 36 models), along with the display of text information indicating each of the disclaimers and the display of text information indicating the operation instructions when agreeing and disagreeing. , Display the "Agree" button and the "Disagree" button below the display of the text information.

When the click of the "Agree" button is detected by the operation of the pointing device of the user (the user of this application is the system administrator), the device and drive to be changed as shown in FIG. 8 are selected. Display the main screen that accepts permission granting and initialization operations. This main screen has a text display of "device name" in FIG. 8, a pull-down menu provided on the right side thereof, a device name selection unit provided with an acquisition button displaying "acquire" on the right side thereof, and a "drive name" below it. Text display and the selection drive display section that says "Please select a drive" in Fig. 8 and the drive name selection section that has a selection button that says "Select" on the right side, and from the left side below it. It is a window having an initial value return button that displays "return to the initial value", an authority grant button that displays "grant authority", and an end button that displays "end" in order toward the right side.

The user first selects the card reader to which the authority is to be granted from the list of card readers displayed in the pull-down menu by clicking the acquire button in the device name selection section, and then clicks the select button to be displayed. If you select a drive in the drive selection dialog and click the permission button, the permission will be given to the selected combination of card reader and drive. On the other hand, if the default value return button is clicked or the like, the authority given to the selected combination of card reader and drive is lost, and the combination returns to the state in which the authority is required. You can also end this application by clicking the end button.
More specific processing by this application will be explained.

When the user detects that the acquisition button in FIG. 8 is clicked, the operating system is requested to acquire the list of card reader / writers connected to the personal computer 35, receives this list, and puts it in the pull-down menu as a list. (See FIG. 9). As a result, the user can select a particular card reader from the list in the pull-down menu. When a specific card reader is selected, the content of the text display displayed when the pull-down menu is not pulled down is the display such as the name of the selected card reader. For example, FIG. 9 shows four types of card reader / writers (physically one but equipped with four types of media slots and recognized by the operating system as four types of card reader / writers) connected. This is an example when it is done. Here, an example in which the card reader / writer "BUFFALO BSCR20TU3 -CF / MD USB Device (disk drive, USBSTOR \ DiskBUFFALO_BSCR20TU3_-CF / MD1.00 \ dDevice \ 00000096)" is selected will be mainly described. When this card reader is selected, the text display of the device name in the non-pulled state in the pull-down menu in Fig. 8 is "BUFFALO BSCR20TU3 -CF / MD USB Device (disk drive, USBSTOR \ DiskBUFFALO_BSCR20TU3_-CF / MD1.00 \). Of "dDevice \ 00000096)", the part up to the displayable range within the width of the text display will be displayed.

When the user clicks the selection button or the like is detected, the drive selection dialog as shown in FIG. 10 is displayed. The drive selection dialog includes a text display prompting the user to select a drive whose authority is to be changed, a drive list display unit for displaying a list of drives of the personal computer 35, and an OK button and a cancel button. When a click of the cancel button is detected, the screen returns to the main screen. The system administrator who is the user selects the drive to which the authority is granted. For example, the user can easily select an I drive having the indication "DRIVE REC1" indicating that it belongs to this system as the volume label of the SD card by identifying it as another drive unrelated to this system. .. When one drive is selected from the list of drives displayed on the drive list display unit, the OK button can be clicked.

When the click of the OK button or the like is detected, it is determined whether or not the selected drive is a valid drive, and if it is not a valid drive, an error including text information indicating that the drive is not a valid drive as shown in FIG. Display a dialog. Then, when the click of the OK button provided in the error dialog is detected, the display returns to the drive selection dialog shown in FIG. Whether or not the drive is valid is determined by inquiring the operating system to obtain and determine whether or not the drive selected in the drive selection dialog is a card reader drive. For example, when "BD-ROM drive (G :)" is selected, an error dialog is displayed because it is not a card reader drive.

On the other hand, it is determined whether or not the selected drive is a valid drive, and if it is a valid drive, the drive name of the drive selected in the drive selection dialog is displayed on the selected drive display section of FIG. .. Here, the case where "DRIVE REC1 i:" is selected will be mainly described. In this case, in the state of FIG. 8, the display of the selected drive display unit in which "Please select a drive" is displayed is changed to the display of "DRIVE REC1 i:".

When the click of the authorization button or the like is detected, it is determined whether or not the currently selected device and drive are a valid device and drive combination. Whether it is a valid device / drive combination, for example, asks the operating system which drive the selected device is assigned to and whether the assigned drive matches the selected drive. Do by.

If it is not a valid device and drive combination, the second error dialog shown in FIG. 12 is displayed. The second error dialog contains text information that indicates that a valid device and drive combination has not been selected, that a valid device and drive combination must be selected, and an OK button. Be prepared. When the click of the OK button is detected, the screen returns to the main screen.

When the combination of a valid device and drive is used, the authorization confirmation dialog shown in FIG. 13 is displayed. In the permission confirmation dialog, text information asking whether to grant permission, text information of the device name of the selected device, text information of the drive name of the selected drive, and "Yes" and "No" are displayed. It has a consent / disagree button.

If a click of the "No" button is detected, the screen returns to the main screen. On the other hand, when a click of the "Yes" button is detected, it is determined whether or not to request administrator authority when accessing the selected card reader in the registry area of Windows. Rewrite the above-mentioned information in the registry area used for Windows to a value that prevents the request for administrator authority. Since this rewriting requires administrator authority depending on the operating system, if there is no administrator authority, the administrator authority request dialog described as shown in FIG. 6 is displayed and the administrator authority is required. It will be. When the rewriting is completed, the authority grant completion dialog as shown in FIG. 15 is displayed. As mentioned above, when accessing an area of a second format that is not supported by the standard, Windows prepares this registry area for each device of the card reader in which the SD card with that area is inserted. Refer to the value to determine whether to request administrator authority, and if it is not a value that should not be requested, perform normal processing to request administrator authority, but do not perform it. In the case of, the configuration is such that the process of requesting administrator authority is not performed. Therefore, by rewriting the value of the registry area prepared for each device of this card reader to a value that does not request administrator authority, when accessing the area of the second format in the viewer application It is possible to prevent the operating system administrator authority request dialog shown in FIG. 6 from being displayed.

As shown in FIG. 15, the authority grant completion dialog includes a text display indicating that the authority has been granted, a text display indicating that the SD card reader / writer 36 is once removed from the personal computer 35 and a request for reconnection, and " It has an "OK" button. When the click of this OK button is detected, the screen returns to the main screen.

In this way, authority can be granted to a specific card reader. To remove the granted authority and return to the state where the original authority is not granted, on the main screen of FIG. 8, select the device / drive pair to which the authority is to be granted by the same operation and processing as the permission granting process, and the initial value. When a click of the return button is detected, it is confirmed whether the device and drive pair is correct by the same operation and processing as the authorization process, and if it is correct, it is selected in the Windows registry area. The information in the registry area used to determine whether to request administrator privileges when accessing the card reader is a value that does not prevent the request for administrator privileges (operating system standard). Rewrite to (value of). Among the above-mentioned authority granting processes, the difference in this authority initialization process is that the text display of "Grant authority to the following devices" in the permission grant confirmation dialog of FIG. 13 is displayed as "The following devices. The authority initialization confirmation dialog is changed to the text display of "Initialize authority", and instead of the authority grant completion dialog shown in Fig. 14, the authority change completion dialog shown in Fig. 15 is displayed. It is the processing of.
If the click of the end button on the main screen is detected, this application will be terminated.
As described above, it is possible to grant or eliminate the authority granted to a specific card reader.

When the authority is granted as shown in the dialog of FIG. 13, the user clicks "DRIVE REC1 i:" on the pointing device in the folder reference dialog in the process when the viewer application is started. When selected and the click of the "OK" button is detected, when the viewer application requests the operating system to access the event recorded video data stored in the second partition of the drive of the drive letter "i:". The information in the registry area that the operating system uses to determine whether to request administrator privileges for this card reader device on this drive should not request administrator privileges. It is determined that the value is set to, and it is not determined whether the user account currently logged in to this operating system has administrator privileges, but the viewer application with administrator privileges has administrator privileges. The information that the state is required is not returned, and even a user without administrator authority can obtain the access permission and continue the operation of the viewer application. Therefore, the position history data, the acceleration history data, the constantly recorded video data, and the event recorded video recorded by the drive recorder 1 in the second formatted area of the second partition in the SD card of this drive. The data can be read and each data can be visualized as shown in FIG. 5 described above.

As described above, the authority change application is used when the viewer application having the function of reading the information stored by the drive recorder 1 for the second partition of the SD card whose reading is not supported by the standard function of Windows 8 is operated. Windows 8 can be controlled so that the request for the administrator authority of the operating system is not displayed. Therefore, it is possible to make it difficult for the drive recorder to rewrite the data recorded in the second partition, and the operating system administrator authority is used when operating the viewer application that has the function to read the information recorded by the drive recorder. The request display is no longer performed, and the user who is a standard user of the operating system can also read and use the data recorded by the drive recorder by this application program from the display as shown in FIG.

Since the process shown in FIGS. 8 and 8 has a function of controlling not to display a request for operating system administrator authority when reading with a specific card reader, the SD card recorded by the drive recorder 1 is provided. Does not require operating system administrator privileges when reading with this card reader, and can maintain a state in which operating system administrator privileges are required for readers other than this card reader. For example, if the entire operating system is configured to control the operating system not to request administrator authority when reading from such a recording medium, the administrator authority is not widely required, and SD If the operating system controls each card so that it does not request administrator authority, it is necessary to set not to request administrator authority for each SD card, which takes time and effort such as calling a system administrator. The viewer app is not available immediately. Moreover, according to this system, such a problem can be solved. Only when the system administrator user reads the SD card with a card reader selected in advance, even a standard Windows user can view the data of the second partition with the viewer application.

Further, as shown in FIG. 13, it is controlled so that the request for the administrator authority of the operating system is not displayed when reading with the selected card reader, but it is physically connected to the personal computer 35. It has a function based on both a physical device for identifying a card reader and a drive, which is the logical identification information recognized and assigned by the card reader by the operating system. Therefore, when a card reader with the same device name is connected, the individual card reader that does not display the request for administrator authority more reliably is identified, and the operating system is managed when the card reader reads it. It is possible to prevent the display of the request for personal authority, and identify the card reader of the individual whose device name is the same as that of the card reader but not the target for not displaying the request for administrator authority. It is possible to display a request for operating system administrator authority when reading with an individual card reader.

As shown in FIG. 8, in the initial state of the main screen, instead of acquiring the list in advance in the pull-down menu and displaying it in the initial state, the pull-down menu is displayed blank and the acquisition button is clicked. In addition, the list is acquired and displayed. By doing so, it is possible to make the system administrator aware that the card reader to be authorized is connected or confirmed.

Further, since it has a function for allowing the user to select a specific card reader from a plurality of card readers connected to the personal computer 35, the user of the system administrator can use the plurality of card readers connected to the personal computer 35. It is possible to determine a card reader to be controlled so as not to display the request for the administrator authority of Windows 8 from the inside.

In addition, since the configuration is such that the information in the registry area used by Windows 8 to determine whether or not to request administrator privileges is rewritten, a program that the operating system executes with administrator privileges, such as developing a device driver for Windows 8, is provided. It can be easily realized without adding the process of developing and preventing the required operation of administrator authority.

Furthermore, since the registry area is recorded on a non-volatile recording medium such as a hard disk, it is not erased even if the operating system is shut down. Therefore, just by executing the permission change application once and rewriting this registry area, the request for administrator authority will not be displayed. Therefore, after that, for example, prior to the execution of the viewer application, it is not necessary to re-execute the authority change application one by one.
The permission change application should have a function to be executed prior to the execution of the viewer application.

It is advisable to add a function to execute the permission change application to the viewer application installer. If you do this, administrator privileges will be required when the viewer app is executed, and you will have to call the system administrator. When you try to view the data recorded by the drive recorder with the viewer app, You can prevent the problem of not being able to see immediately.

In this embodiment, the permission change application and the viewer application are configured as separate executable files. Therefore, the system administrator can easily execute the permission change application only on the personal computer that does not want to request the administrator authority. In addition, it is easy not to run the permission change application on a computer that wants to request administrator privileges, which enhances security.

The viewer application should have a function that allows only the operation manager set up in the organization separately from the system administrator to view the data in the second partition area. For example, immediately after the start of execution of the viewer application, a screen for entering the operation manager ID and password is displayed, the user is asked to enter the operation manager ID and password, and the operation manager ID and password registered in advance are displayed. If they match, it is preferable to shift to the process of displaying the folder reference dialog similar to that shown in FIG. 10 described above. In this way, it is possible to easily realize the operation by designating the system administrator and the operation manager as different persons in the organization. The operation manager may be, for example, a person who manages the vehicle in which the drive recorder 1 is installed, or a person who manages the driver of the vehicle.
Since the authority change application has a function to initialize the granted authority, it is possible to display a request for administrator authority.

It is preferable that the authority change application is configured not to rewrite the registry as described above when the version of Windows is determined and the version is the version in which the request for administrator authority is not displayed. This process is not necessary in Windows XP.

As an embodiment of the present invention, the present system has been described based on a personal computer and an example realized by a program executed on the personal computer. However, for example, if the system is configured as a program running on a terminal running a multi-user operating system. Good. For example, it may be configured as a program that runs on an operating system used for tablets and the like.

The drive recorder 1 is configured to include a camera for photographing the front of the vehicle, but may be configured not to include, for example, a camera. When a camera is provided, the shooting location may be rearward or lateral, or a combination thereof, instead of the front. Further, the shooting location may be inside the vehicle instead of outside the vehicle, or both inside and outside the vehicle may be photographed. However, it is particularly desirable to have a function to photograph the inside of the vehicle. In this way, an excellent effect is exhibited in a configuration in which vehicle status information is acquired in order to manage the driver.

In this embodiment, when the user account does not have the administrator authority, the configuration for displaying the administrator authority request dialog of the operating system as shown in FIG. 6 has been described. Is such an administrator authority request necessary? If it is necessary to obtain the administrator authority request from the operating system, the administrator authority is not required for the configuration in which the application process is terminated or interrupted on the application side. It exerts the effect of becoming.

If you click the default value return button or the like, all the privileges that have already been granted will be lost, and you may configure it to return to the state where the permission change application is not running at all.

The setting data of the drive recorder 1 may be recorded in the second partition area. For example, when a click of the gear-shaped icon at the right end of the menu bar 52 of the viewer application of FIG. 5 is detected, the operation setting screen of the drive recorder 1 is displayed as shown in FIG. When such as is detected, the setting contents of the setting items on this screen may be stored in the second partition area as the setting data of the drive recorder 1. When the power is turned on, the drive recorder 1 reads the setting data stored in the second partition and processes the contents of each setting item referred to in the processing of the drive recorder 1 as the setting contents. In this way, falsification of the setting data can be prevented, and even a user without administrator authority can easily view or change the setting data.

The invention of the present application is not limited to the configuration described in the above-described embodiment. The components of each of the above-described embodiments can be arbitrarily selected and combined within a range that can be combined. Further, it can be configured in combination with any component within a range that can be combined with any component described in the means for solving the invention.

Claims (2)

Controls that the operating system does not display a request for operating system administrator privileges when an application program operates that reads information stored by the drive recorder in a predetermined area that is not supported by standard operating system functions. System to do. A program for realizing the function of the system according to claim 1 on a computer.