JP2015176376A - Count related information management server and count related information management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To easily collect and manage information required as a result of a traffic volume survey without imposing troublesome work.SOLUTION: A count related information server 10A receives count execution information indicating execution of counting and, on the basis of the count execution information and area position information indicating existence positions of predetermined areas, identifies predetermined areas in which user terminals 501-50N exist during the counting, execution time information indicating a time during the counting, and count numbers which are counted in the predetermined areas where the user terminals 501-50N exist. Count related information including the identified predetermined areas and count numbers and count time information that is the identified execution time information are registered in a count related information DB 23.

Description

  The present invention relates to a count related information management server and a count related information management program for managing count related information including a count number counted by a user operation using a user terminal in a predetermined area.

  Conventionally, when conducting traffic surveys on the streets, the surveyor counts the number of each survey target item using a survey form or a portable counter, and the counted information is transferred to a predetermined survey table and compiled. The method of doing was common.

  However, there is a problem in that the operation of transferring the counted information to paper is complicated, and it takes time from the time of the survey to the completion of the aggregation. In addition, each investigator had to investigate each measurement location and time.

  In order to solve such a problem, there is a traffic data measurement system and a traffic survey method that use a mobile phone as a counter by starting a program built in the mobile phone (see Patent Document 1-2). As a result, the investigator was able to acquire the measurement location and measurement time by using the GPS function of the mobile phone.

JP 2007-018314 A JP 2004-302816 A

  In the conventional traffic data measurement system and the traffic survey method described above, the latitude / longitude information is simply specified as the measurement location, and the information necessary for the measurement location such as the bus stop and the name of the station is still an investigator. There was a problem that there was a need to check separately.

  An object of the present invention is to solve the above-described problems and to easily collect and manage necessary information as a result of a traffic volume survey without forcing a troublesome work.

  The count related information management server of the present invention is a count related information management server that manages count related information including a count number counted by a user's operation using a user terminal in a predetermined area, and the location of each predetermined area The area position information storage means for storing area position information indicating, the predetermined area, the count time information indicating the time counted in the predetermined area, and the count number counted in the predetermined area are associated with each other Based on the count related information storage means for storing the count related information, the count execution information receiving means for receiving the count execution information indicating that the count has been performed, and the count execution information and the area position information, the user terminal at the time of counting At the time of execution that shows the predetermined area where the Specifying means for specifying information and a count number counted in a predetermined area where the user terminal was present, a predetermined area and a count number specified by the specifying means, and an execution specified by the specifying means And count related information registration means for registering count related information including count time information as time information in the count related information storage means.

  With the above configuration, it becomes possible to easily collect and manage the necessary information as a result of the traffic volume survey without complicating troublesome work.

  The count execution information receiving unit may be configured to receive the count execution information from the user terminal.

  The count execution information includes terminal location information indicating the location of the user terminal, and the specifying unit is configured to determine whether the user terminal exists at the time of counting based on the terminal location information and the area location information. The area may be specified.

  The count execution information includes operation end time information indicating a time at which a predetermined count end operation is performed on the user terminal, and the specifying unit specifies the operation end time information as the execution time information. May be.

  The user terminal generates count execution information including a count operation number indicating the number of times the count operation has been performed on the user terminal in response to a predetermined count end operation being performed on the user terminal, The count operation number may be specified as the count number.

  The predetermined area may be an area around a boarding / exiting point where a passenger of a moving body such as a bus gets on and off, and the count number may be the number of passengers who get on and off the moving body.

  It includes operation schedule time information storage means for storing operation schedule time information in which mobile object identification information capable of uniquely specifying an object to be operated and an operation schedule time are associated with each other. The count execution information includes the mobile body identification information, and the count related information registration means stores the count related information including the mobile body identification information included in the count execution information. May be configured to be registered.

  The scheduled moving time information storage means for storing the scheduled driving time information in which the moving object identification information capable of uniquely identifying the moving object to be operated and the scheduled driving time are associated, the moving object identifying information, and the user Mobile body specifying information storage means for storing mobile body specifying information associated with user terminal identification information capable of uniquely specifying a terminal, and the user is a driver of the mobile body, and the count execution The information includes the user terminal identification information, the specifying means also specifies the moving body identification information based on the user terminal identification information with reference to the moving body specifying information, and the count related information registration means May be configured to register the count related information including the moving body identification information specified by the specifying means in the count related information storage means.

  Based on the count related information, the count number list information generating means for generating count number list information including the count number in the area around the getting-on / off point for each moving object to be operated, and the count number list information It may be configured to include count number list information output means for outputting.

  In addition, the count related information management program of the present invention causes the count related information management server to execute processing for managing count related information including a count number counted by a user operation using a user terminal in a predetermined area. In the management program, an area position information storage means for storing area position information indicating the position of each predetermined area, a predetermined area, count time information indicating a time counted in the predetermined area, and a predetermined area Count execution information reception for receiving count execution information indicating that counting has been performed in the count related information management server including the count related information storage unit that stores the count related information associated with the counted count number Processing, the count execution information, and the area position information. Therefore, the identification that specifies the predetermined area where the user terminal was present at the time of counting, the execution time information indicating the time at the time of counting, and the count number counted in the predetermined area where the user terminal was present Count related information registration for registering count related information including a process, a predetermined area and count number specified by the specifying process, and count time information which is execution time information specified by the specifying process in the count related information storage unit This is for executing processing.

  According to the present invention, it becomes possible to easily collect and manage necessary information as a result of the traffic volume survey without forcing a troublesome work.

It is a block diagram which shows the structural example of a count related information management system. It is explanatory drawing which shows the example of the storage state of area position information. It is explanatory drawing which shows the example of the storage state of count execution information. It is explanatory drawing which shows the example of the storage state of count related information. It is explanatory drawing for demonstrating the outline | summary of a count related information registration process. It is a flowchart which shows the example of a count related information registration process. It is explanatory drawing for demonstrating the example of the display screen of a user terminal at the time of count execution. It is explanatory drawing for demonstrating the example of a predetermined area specific process. It is a block diagram which shows the other structural example of a count related information management system. It is explanatory drawing which shows the example of the storage state of service scheduled time information. It is explanatory drawing which shows the example of the storage state of mobile body specific information. It is explanatory drawing which shows the other example of the storage state of count related information. It is explanatory drawing for demonstrating the other example of a predetermined area specific process. It is a flowchart which shows the other example of a count related information registration process. It is a flowchart which shows the example of count number list information generation processing. It is explanatory drawing which shows the example of a count number list information screen. It is explanatory drawing which shows the further another example of the storage state of count execution information. It is explanatory drawing which shows the example of a count execution information registration process. It is explanatory drawing which shows the further another example of a count related information registration process. It is explanatory drawing for demonstrating the other example of the display screen of a user terminal at the time of count execution. It is explanatory drawing which shows the further another example of the storage state of count related information.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a block diagram showing a configuration example of a count related information management system 100A according to an embodiment of the present invention.

  As illustrated in FIG. 1, the count related information management system 100A includes a count related information management server 10A, user terminals 501 to 50N (N is an arbitrary positive integer), and a display terminal 50. The user terminals 501 to 50N are connected to the count related information management server 10A via the base station 40 and the communication network 30 such as the Internet. The display terminal 50 is connected to the count related information management server 10 </ b> A via the communication network 30.

  Note that FIG. 1 shows a case where each component other than the mobile terminal, the counting device, and the communication cable is one, but the count related information management system 100A includes, for example, a plurality of count related information aggregation servers 10A, base station 40, a plurality of display devices 50, and the like may be included.

  User terminals 501 to 50N include mobile terminals 201 to 20N (N is an arbitrary positive integer) and counting devices 301 to 30N (N is an arbitrary positive integer), respectively. The portable terminals 201 to 20N and the counting devices 301 to 30N are connected by wireless or wired (communication cables 401 and 402), respectively. In addition, you may make it the structure which fulfill | performs the function which the counting devices 301-30N have with the input device with which the portable terminals 201-20N are provided, and you may make it the user terminal 501-50N not have the counting devices 301-30N.

  The mobile terminals 201 to 20N are terminal devices managed by a user who uses the count related information management system 100A, for example, and are configured by an information processing device such as a mobile phone terminal, a PDA, a mobile type personal computer or a dedicated device. The In this example, the mobile terminals 201 to 20N are connected to the count related information management server 10A via the base station 40 and the communication network 30, and count execution information to be described later is counted according to a request from the user. It has various functions such as a function of transmitting to 10A.

  The mobile terminals 201 to 20N in this example have a function of measuring the current position of the mobile terminals 201 to 20N (that is, the current position of the user), and receive, for example, a GPS signal sent from a GPS satellite. And a GPS sensor for measuring the position based on the GPS signal.

  A GPS sensor is a so-called GPS receiver, receives a GPS signal radiated from a GPS satellite, measures a distance (pseudo distance) between the GPS satellite and the GPS receiver itself, and receives a plurality of satellites. The position information of the mobile terminals 201 to 20N indicating the current position (GPS positioning solution) of the GPS receiver itself is calculated by simultaneously receiving the GPS signals.

  In addition, it is assumed that the mobile terminals 201 to 20N are equipped with a dedicated application for using the count related information management system 100A. This dedicated application is an application for realizing various functions such as a function of displaying the count number.

  In this example, the mobile terminals 201 to 20N access a dedicated application download website established by the count related information management server 10A via the communication network 30 in accordance with a user's operation, and downloaded from the dedicated website. Assume that you have installed the application. That is, the count related information management server 10A has a function of operating a dedicated application download site, and performs processing for providing a dedicated application in response to a request from the user terminals 201 to 20N. Note that other processing such as user registration may be performed on this download site. The dedicated application download site is not limited to the count related information management server 10A, and may be opened by another WWW server such as a server device capable of downloading various applications.

  The count device 301 in this example is provided with operation buttons for the user to perform a count operation. In this example, it is assumed that four operation buttons are provided as shown in FIG.

  The operation button may be configured to distinguish a count target, which is a target to be counted, for each button. In this case, the setting of the count target may be configured to set the count target for each button using a dedicated application for using the related information management system 100A installed in the user terminal 201, for example. That is, the dedicated application for using the related information management system 100A may be configured to have a function of setting a count target.

  The display terminal 50 communicates with the count related information management server 10A via the communication network 30, and displays information acquired from the count related information management server 10A by using a software function such as a predetermined Web application (Web browser), for example. It has the function to output to. As the predetermined Web application, a dedicated application for using the related information management system 100A described above may be used.

  The count related information management server 10A is a server managed by a system administrator of the count related information management system 100A, for example, and is configured by an information processing apparatus such as a WWW server. In this example, the count related information management server 10A executes various processes for registering the count related information in response to requests from the user terminals 501 to 50N. Further, the count related information server 10A may be configured to have a function of outputting count related information and the like to the display unit by a function of software such as a predetermined Web application (Web browser).

  In this example, the count related information management server 10A includes various DBs including an area position information DB 21, a count execution information DB 22, and a count related information DB 23 as shown in FIG. These various DBs may be inside or outside the count related information management server.

  The area position information DB 21 is a storage medium for storing area position information indicating the position of each predetermined area. FIG. 2 is an explanatory diagram illustrating an example of a storage state of area position information. As shown in FIG. 2, the area position information in this example is information in which an area name and an existing position are associated with each other.

  The area name indicates the name of the predetermined area. The predetermined area is an area set by the manager of the area position information, and indicates an area around a bus stop (hereinafter sometimes referred to as a bus stop). The predetermined area may include a public facility such as a station, a city hall, a police box or the like.

  The existence position indicates the existence position of each predetermined area, and is represented by a latitude / longitude (latitude / longitude area) indicating an arbitrary area.

  The count execution information DB 22 is a storage medium for storing information indicating that the user terminals 501 to 50N have counted. FIG. 3 is an explanatory diagram illustrating an example of a count execution information storage state. As shown in FIG. 3, the count execution information in this example is information in which the terminal position, the operation end time, and the count operation number are associated with each other.

  The terminal position indicates the presence positions of the user terminals 501 to 50N acquired by the GPS sensor function that the user terminals 501 to 50N have.

  The operation end time indicates a time when a predetermined count end operation is performed on the user terminals 501 to 50N. The count execution information DB 22 includes, in place of the operation end time, an operation start time indicating a time when a predetermined count start operation is performed on the user terminals 501 to 50N, an operation time indicating a time when the count operation is performed, and the like. It may be configured to be stored.

  The count operation number indicates the number of times the count operation has been performed on the user terminals 501 to 50N. In this example, the count operation number includes the count operation number for each operation button arranged on the user terminals 501 to 50N. That is, as shown in FIG. 3, in the user terminals 501 to 50N, the A button is the number of passengers / male, the B button is the number of passengers / female, the C button is the number of passengers / male, and the D button is the number of passengers / female. , And the number of operations performed on each operation button is stored in the count execution information DB 22 as the number of count operations.

  The count related information DB 23 is a storage medium for storing count related information in which a predetermined area, count time information indicating a time counted in the predetermined area, and a count number counted in the predetermined area are associated with each other. It is. FIG. 4 is an explanatory diagram illustrating an example of a storage state of count related information. As shown in FIG. 4, the count related information in this example is information in which an area name, an operation end time, a count number, and a count operation number are associated with each other.

  In this example, the area name indicates a predetermined area specified by a count related information registration process described later. The operation end time indicates a count time indicating a time counted in a predetermined area specified by a count related information registration process described later. Furthermore, the count number and the count operation number indicate the count number counted in the predetermined area specified by the count related information registration process described later.

  Next, the operation of the count related information management system 100A in this example will be described with reference to the drawings. Note that detailed descriptions of processes not particularly related to the present invention may be omitted.

  FIG. 5 is an explanatory diagram for explaining an outline of a count related information registration process to be described later. In FIG. 5, the count related information management server 10 </ b> A, the route bus 60, the bus stop 70, the user terminal 501 (the portable terminal 201 and the counting device 301 connected to the portable terminal 201 via the communication cable 401), driving A person 601, a passenger 602, and a user (a user who operates the user terminal 501) 701 are shown. In this example, as illustrated in FIG. 5, a case where the user 701 counts the number of people getting on and off the route bus 60 by performing a counting operation using the counting device 301 will be described as an example.

  FIG. 6 is a flowchart illustrating an example of count related information registration processing executed by the count related information management system 100A. In the count related information registration process, the count related information management server 10A (hereinafter sometimes referred to as server 10A) registers the count related information in the count related information DB 23 based on the reception of the count execution information from the user terminal 501. The process for performing is performed.

  The count related information registration process is started when a dedicated application installed in the user terminal 501 is started, for example.

  In the count related information registration process, first, the user terminal 501 receives a count input (step S101). In this example, the count device 301 receives a count input, and transmits a count signal indicating that the count has been received to the mobile terminal 201 via the communication cable 401.

  Next, the user terminal 501 determines whether or not the counting operation has ended (step S102). In this example, when the portable terminal 201 receives a pressing operation (touch panel touch operation) of an end button 82 (see FIG. 7) described later, it is determined that the counting operation has ended.

  FIG. 7 is an explanatory diagram for explaining an example of a display screen during count execution. In this example, as shown in FIG. 7, a count number display screen 81 is displayed on a display device included in the mobile terminal 201. The count number display screen 81 is provided with count number display areas 801 to 804 corresponding to the respective buttons (A button, B button, C button, D button) provided in the count terminal 301 and an end button 82. . The numerical value displayed in each count number display area 801 to 804 indicates the number of times that the count operation has been performed with each corresponding button of the count terminal 301 (count number). In this example, each time the buttons of the count terminal 301 are pressed, the numerical values displayed in the corresponding count number display areas 801 to 804 are incremented by one.

  In FIG. 7, the count number display area 801 is an area for displaying the number of “passengers / male” counted by the operation of the A button of the count terminal 301. The count number display area 802 is an area for displaying the number of “number of passengers / female” counted by operating the B button of the count terminal 301. The count number display area 803 is an area for displaying the number of “getting off person / male” counted by operating the C button of the count terminal 301. The count number display area 804 is an area for displaying the number of “getting off person / male” counted by operating the D button of the count terminal 301. The end button 82 is a button for accepting the end of counting.

  In this example, whether or not the count operation has been accepted is determined based on whether or not an operation of pressing the end button 82 has been accepted. However, the configuration is not limited to the above-described configuration. The configuration may be such that it is determined that the acceptance of the count operation has ended when no time operation (for example, 5 minutes) is accepted.

  When it is determined that the count operation has been accepted, the user terminal 501 confirms the terminal position (step S103). In this example, the mobile terminal 201 confirms position information (latitude / longitude information) indicating its own position calculated by a positioning function included in itself. In this example, for example, it is assumed that the position information indicating the self position is periodically calculated and updated. In step S103, position information indicating the self position may be calculated.

  Next, the user terminal 501 confirms the operation end time (step S104). In this example, it is assumed that the time when the count operation ends (Y in step S102) is the operation end time. Accordingly, in step S104, the time when the pressing operation of the end button 82 is accepted is confirmed as the operation end time. In addition, it is good also as confirming the reception start time (operation start time) of count operation instead of operation end time.

  Next, the user terminal 501 generates count execution information (step S105). In this example, the mobile terminal 201 generates count execution information including a count number, terminal position information, and operation end time information.

  When the count execution information is generated, the user terminal 501 transmits the generated count execution information to the server 10A (step S106).

  When the server 10A receives the count execution information from the user terminal 501 (step S201), the server 10A specifies a predetermined area based on the terminal position information included in the received count execution information (step S202). In this example, the server 10A refers to the area position information DB 21 and identifies a predetermined area closest to the position indicated by the position information included in the received count execution information.

  Hereinafter, a process (predetermined area specifying process) for specifying a predetermined area closest to the position indicated by the position information included in the received count execution information will be described with reference to the drawings.

  FIG. 8 is an explanatory diagram for explaining an example of processing for specifying a predetermined area. FIG. 8 shows a route for a (L001-01) and a route for b (L002-02). Each route has bus stops 90 to 94, and areas around the bus stop are set as predetermined areas 900 to 904. In the predetermined areas 900 to 904, the counters 701 to 705 count the number of passengers getting on and off when the route bus 60 arrives.

  In FIG. 8, the counter 701 using the user terminal 201 is located at the position (X1, Y1). Further, it is assumed that the server 10A has received the position (X1, Y1) as the count execution information (terminal position information) in step S107.

  The server 10A refers to the area position information DB 21 and identifies the bus stop 1 (bus stop 90), which is the predetermined area closest to the position indicated by the terminal position information included in the received count execution information, as the predetermined area. In this example, the position indicated by the terminal position information included in the received count execution information is included in the area position indicated by the area position information DB 21, but is included in the area position indicated by the area position information DB 21. Even if there is not, the predetermined area closest to the position indicated by the position information included in the received count execution information may be specified.

  When the predetermined area is specified based on the area position information, the server 10A specifies count time information (step S203). In this example, the server 10A specifies the operation end time information included in the received count execution information as the count time information. The count time information may be the operation start time described above.

  When the count time information is received, the server 10A specifies the count number (step S204). In this example, the server 10A specifies a predetermined total number of count operations included in the count execution information received from the user terminal 501 as the count number. In this example, the predetermined total number of count operations indicates the total number of passengers and the total number of people getting off, but may be configured, for example, a total by gender or a total by adult children.

  When the count number is specified, the server 10A specifies various information specified based on the received count execution information (the predetermined area specified in step S202, the count time specified in step S203, and the count specified in step S204). Number) is registered in the count related information DB 24, and the process here ends. In this example, the server 10A associates various types of information specified based on the received count execution information and stores them in the count related information DB 24. Various types of information specified based on the received count execution information are stored in the count related information DB 24 as shown in FIG. 4, for example.

  Here, another configuration example of the count related information management system will be described. FIG. 9 is a block diagram showing another configuration example of the count related information management system. As shown in FIG. 9, the count related information management system 100 </ b> B is different from the count related information management system 100 </ b> A (see FIG. 1) described above in that it includes a scheduled operation time information DB 24 and a moving body specifying information DB 25. In FIG. 9, the same parts as those described with reference to FIG.

  The scheduled operation time information DB 24 is a storage medium for storing scheduled operation time information indicating the scheduled operation time.

  FIG. 10 is an explanatory diagram illustrating an example of a storage state of the scheduled operation time information DB 24. As shown in FIG. 10, the scheduled operation time information in this example is associated with a route name, a route ID, a bus stop name that is an example of an area name, and a departure time that is a time of departure from each bus stop. Information. Here, the predetermined area is a bus stop, and the scheduled operation time information is related to a route bus.

  In this example, the route ID is information that can uniquely identify which route the route bus, which is a moving object to be operated, operates at which time. In this example, the route ID “L001-01” indicates the first route of the route name “bound for a (L001)”, and thereafter, “L001-02”, “L001-03”,. The route to "L001-15" is shown. Although not shown, the scheduled operation time information DB 24 may be configured to store scheduled operation time information on weekdays and scheduled operation time information on weekends.

  FIG. 11 is an explanatory diagram illustrating a configuration example of the storage state of the mobile unit identification information. The moving body specifying information DB 25 is a storage medium for storing moving body specifying information in which a route ID and a terminal ID are associated with each other.

  The terminal ID is an example of user terminal identification information that can uniquely identify the user terminals 501 to 50N. The terminal ID may be a number given to the mobile terminals 201 to 20N or the counting devices 301 to 30N.

  FIG. 12 is an explanatory diagram showing another configuration example of the count related information storage state. As shown in FIG. 12, the storage state of the count related information is different from the above-described storage state of the count related information (see FIG. 4) in that the terminal ID and the route ID are included.

  Next, the operation of the count related information management system 100B in this example will be described with reference to the drawings. Note that detailed descriptions of processes not particularly related to the present invention may be omitted.

  FIG. 13 is an explanatory diagram for explaining an example of processing for specifying a predetermined area. FIG. 13 shows a route to a (L001-01) and a route to b (L002-02). Each route has bus stops 90 to 94, and areas around the bus stop are set as predetermined areas 900 to 904. In this example, it is assumed that the predetermined areas 900 to 904 are set so that the driver's seat of the route bus 60 is located within the predetermined areas 900 to 904 when the route bus 60 stops at the bus stops 90 to 94. An example will be described in which 60 drivers 601 (see FIG. 5) count the number of passengers getting on and off at bus stops 90 to 94.

  FIG. 14 is a flowchart illustrating an example of count related information registration processing executed by the count related information management system 100B. In the count related information registration process, the count related information management server 10B (hereinafter sometimes referred to as server 10B) registers the count related information in the count related information DB 23 based on the reception of the count execution information from the user terminal 501. The process for performing is performed. In addition, about the step which performs the process similar to the count related information registration process (refer FIG. 6) which the count related information management system 100A mentioned above performs, the same step number is attached | subjected and detailed description is abbreviate | omitted.

  The count related information registration process is started when a dedicated application installed in the user terminal 501 is started, for example. In this example, the route with the route ID “L001-01” is operated, and the user terminal (user terminal 501) with the terminal ID “U0001” associated with the route ID “L001-01” is assumed. ) And the driver 601 gets on the route bus 60.

  The user terminal 501 executes the processing from step S101 to step S104, generates count execution information (step S105), and transmits the generated count execution information to the server 10B (step S106). In this example, in step S105, the mobile terminal 201 generates count execution information including a count number, terminal position information, operation end time information, and a terminal ID.

  When the server 10B receives the count execution information from the user terminal 501 (step S201), the server 10B executes the processes of steps S202 to S204.

  Next, the server 10B refers to the moving body specifying information DB 25 and specifies the route ID associated with the terminal ID included in the count execution information (step S401). By specifying the route ID, it is possible to specify the route being operated by referring to the scheduled operation time information DB 24.

  Next, the server 10B specifies various information specified based on the received count execution information (for example, the terminal ID included in the count execution information received in step S201, the predetermined area specified in step S202, The count time specified in S203, the count number specified in step S204, and the route ID specified in step S401) are registered in the count related information DB 23 as count related information, and processing here Exit.

  Note that various types of information specified based on the received count execution information are registered in association with each bus stop, for example, as shown in FIG. In this case, each bus stop in the planned stop order may be assigned in the order in which the count execution information is received. If the boarding / alighting number is 0, for example, count execution information indicating that the count number is 0 may be transmitted to the server 10B.

  FIG. 15 is a flowchart illustrating an example of count number list information generation processing executed by the count related information management server 10A or the count related information management server 10B (hereinafter also referred to as servers 10A and 10B). In the count number list information generation process, a process in which the servers 10A and 10B output the count number list information with reference to the count related information DB 23 is executed.

  The count number list information generation process is started in response to a count number list information provision request from the display terminal 50 by the operation of the user X, for example. It is assumed that the count number list information provision request includes an extraction condition. As the extraction condition, for example, a route ID, an extraction target period, an area name, and the like can be considered.

  In the count number list information generation process, first, the servers 10A and 10B specify the extraction condition based on the count number list information provision request from the display terminal 50 (step S501). Here, as the extraction condition, the route L001 and the route L002 are identified from the route ID included in the count number list information provision request, and “2014/01/10” as the extraction period included in the count number list information provision request. Is specified. The extraction period may be in units of days or hours.

  When the extraction condition is specified, the servers 10A and 10B refer to the count related information DB 23, extract the count related information for the period and route that match the specified extraction condition, and generate the count number list information (step) S502).

  When the count number list information is generated, the servers 10A and 10B output the generated count number list information (step S503), and the processing here ends. In this example, the servers 10 </ b> A and 10 </ b> B transmit the generated count number list information to the display terminal 50 in step S <b> 503. The display terminal 50 displays a count number list screen indicating the received count number list information on a display device provided therein. The servers 10A and 10B generate count number list information based on a count number list information provision request from an operator, and display a count number list screen on a display device that the server 10A and 10B have, or printing that the server 10A and 10B have. The count number list information may be printed out by the apparatus.

  FIG. 16 is an explanatory diagram showing an example of the count number list information screen. As shown in FIG. 16, the count number list information screen 1600 is provided with a display area 1601 for displaying count number list information. In the display area 1601, the route and period specified as extraction conditions, the route name (route ID in FIG. 16), the name of the bus stop, the scheduled operation time, the operation time, the delay time, and the total number of counts are displayed. An area for displaying the count number details is provided.

  Here, “operation time” corresponds to the operation end time in this example. The “delay time” indicates the difference between the scheduled operation time and the operation time, and is calculated in step S502, for example.

  FIG. 17 is an explanatory diagram showing another example of the count execution information storage state. As shown in FIG. 17, the count execution information in this example is information in which a count operation button (type of operation button), a terminal position, and a count time are associated with each other. In this example, the count execution information is generated by the user terminals 501 to 50N each time a counting operation is performed in the counting devices 301 to 30N, and accumulated in a storage medium such as a memory provided in the user terminals 501 to 50N. I will go.

  The operation buttons illustrated in FIG. 17 mean operation buttons on which a count operation has been performed on the user terminals 501 to 50N. In this example, as shown in FIG. 17, for example, when the A button of the count device 301 is pressed, the operation button “A” is stored in the corresponding item of the count execution information.

  The terminal positions shown in FIG. 17 indicate the presence positions of the user terminals 501 to 50N acquired by the GPS sensor function that the user terminals 501 to 50N have.

  The count time illustrated in FIG. 17 indicates the time when the count operation is performed on the user terminals 501 to 50N.

  FIG. 18 is a flowchart illustrating an example of count execution information registration processing executed by the user terminals 501 to 50N. In the count execution information registration process, based on the reception of the count signal from the count device 301, a process for registering the count execution information in a storage medium such as a memory provided in the mobile terminal 201 is executed.

  The count execution information registration process is started when a dedicated application installed in the user terminal 501 is started, for example.

  In the count execution information registration process, first, the user terminal 501 determines whether or not a count input has been accepted (step S501). In this example, the mobile terminal 201 determines whether or not the count signal received by the count device 301 is input via the communication cable 401.

  If it is determined that the count operation has not been accepted (N in step S501), the user terminal 501 waits until the count operation is accepted.

  If it is determined that the count operation has been received (Y in step S501), the user terminal 501 checks the terminal position (step S502). In this example, the mobile terminal 201 confirms position information (latitude / longitude information) indicating its own position calculated by a positioning function included in itself. In this example, for example, position information indicating the self position is calculated every time a count operation is received (Y in step S501).

  Next, the user terminal 501 confirms the operation time (step S503). In this example, it is assumed that the time when the count operation is accepted (Y in step S501) is the operation time. Accordingly, the user terminal 501 confirms the time at which the count operation is accepted as the operation time every time the count operation is accepted at step S503.

  Next, the user terminal 501 generates count execution information (step S504). In this example, the mobile terminal 201 generates count execution information including an operation button, a terminal position, and a count time.

  When the count execution information is generated, the user terminal 501 registers the generated count execution information in a storage medium such as a memory included in the mobile terminal 201 (step S505).

  FIG. 19 is a flowchart showing still another example of the count related information registration process executed by the count related information management system 100B. In the count related information registration process, the count related information management server 10B (hereinafter sometimes referred to as server 10B) registers the count related information in the count related information DB 23 based on the reception of the count execution information from the user terminal 501. The process for performing is performed. In addition, about the step which performs the process similar to the count related information registration process (refer FIG. 6 and FIG. 14) which the count related information management system 100A and the count related information system 100B mentioned above perform, it attaches | subjects the same step number and details. The detailed explanation is omitted.

  The count related information registration process is started, for example, when the server 10B receives access from the user terminal 501.

  In the count related information registration process, first, the server 10B receives count execution information from the user terminal 501 via a wired cable (step S601). In this example, the portable terminal 201 is connected to the server 10B via a wired cable such as a USB cable, and the server 10B receives count execution information from the portable terminal 201 via this USB cable. When the count execution information is received, the mobile terminal 201 and the server 10B may be connected by a wireless LAN such as Wi-Fi (Wireless Fidelity) or wirelessly such as Bluetooth (registered trademark). Further, the count execution information may be moved or copied to the server 10B using a removable storage medium such as a USB memory mounted on the portable terminal 201.

  Further, the mobile terminal 201 and the server 10B may be synchronized with respect to the count execution information. In this case, the synchronization process may be performed when the count execution information is transmitted and received between the mobile terminal 201 and the server 10B.

  Next, when a predetermined area is specified in step S202, the server 10B specifies count time information (step S203). In this example, the server 10B specifies the count operation end time, which is the time when the count operation is completed, among the operation time information included in the received count execution information as the count time information. In this case, for example, the latest time among the count times in which the predetermined area indicated by the terminal position included in the count execution information is the same area may be specified as the count operation end time.

  Next, the server 10B specifies the count number (step S603). In this example, the server 10B calculates the total count for each predetermined area based on the operation buttons included in the count execution information received from the user terminal 501, and specifies the calculated total as the count. That is, the number of counts (the number of passengers and the number of people getting off) for the predetermined area is calculated according to the number of counts of each operation button in which the predetermined area indicated by the terminal position is the same area.

  FIG. 20 is an explanatory diagram for explaining another example of the display screen of the mobile terminal 201 during count execution. In addition, about the structure similar to FIG. 7, the same number is attached | subjected and detailed description is abbreviate | omitted.

  Each button (A button, B button, C button, D button) shown in FIG. 20 is a button for A button to add 1 for the number of passengers, a button for B button to subtract 1 for the number of passengers, and a button for C button. A button to add 1 and a D button to subtract 1 from the number of people getting off. The count number display area 1801 displays a numerical value obtained by subtracting the number of times the B button has been counted from the number of times the A button has been counted as the number of passengers. In the count number display area 1804, a numerical value obtained by subtracting the number of times the D button has been counted from the number of times the C button has been counted is displayed as the number of people getting off. In this example, each time the buttons of the count terminal 301 are pressed, the numerical values displayed in the corresponding count number display areas 1801 and 1802 are increased or decreased by one. In this example, the operation end button 82 shown in FIG. 7 is not provided, but an end button that is pressed when the count operation in each predetermined area is ended may be provided. In this example, for example, when the operation of each button is not performed for a predetermined time (for example, 30 seconds), it is considered that the count operation is finished, and the display of the count number is reset.

  FIG. 21 is an explanatory diagram showing still another example of the count-related information storage state. As shown in FIG. 21, the count related information storage state is different from the count related information storage state described above (see FIG. 12) in that it does not include the number of count operations. Further, in this example, the number of passengers stored in the count number is the count number specified in step S203, and is the number obtained by subtracting the B button count from the A button count shown in FIG. . The number of people getting off stored in the count number is the count number specified in step S203, and is the number obtained by subtracting the count number of the D button from the count number of the C button shown in FIG.

  As described above, in the above-described embodiment, the count related information servers 10A and 10B store the area position information DB 21 that stores the area position information indicating the position of each predetermined area, the predetermined areas 900 to 904, A count related information DB 23 for storing count related information in which count time information indicating times counted in the predetermined areas 900 to 904 and counts counted in the predetermined areas 900 to 904 are associated with each other; Count execution information indicating that counting has been performed, and based on the count execution information and area position information, predetermined areas 900 to 904 where user terminals 501 to 50N existed at the time of counting, and execution indicating the time at the time of counting Time information and a predetermined area 900 to which the user terminals 501 to 50N existed The count number counted in 04 is specified, and the count related information including the specified predetermined areas 900 to 904 and the count number and the count time information that is the specified execution time information is registered in the count related information DB 23 As a result, it becomes possible to easily collect and manage necessary information as a result of the traffic volume survey without forcing troublesome work.

  That is, since the predetermined areas 900 to 904 where the user terminals 501 to 50N existed at the time of counting are specified and the count related information including the specified predetermined areas 900 to 904 is registered, it is necessary to separately check the predetermined areas. As a result of traffic volume survey, necessary information can be easily collected and managed. Therefore, it is possible to greatly reduce the burden during the traffic survey. Moreover, since the predetermined areas 900 to 904 in which the user terminals 501 to 50N exist are automatically specified, it is possible to eliminate a mistake that erroneously specifies a different predetermined area.

  Further, in the above-described embodiment, when the count related information servers 10A and 10B are configured to receive the count execution information from the user terminals 501 to 50N, they are necessary as a result of the traffic volume survey from the user terminals 501 to 50N. Since it is possible to automatically receive such information, it is possible to further reduce the work burden at the time of traffic survey.

  In the above-described embodiment, the count execution information includes the terminal position information indicating the existing positions of the user terminals 501 to 50N, and the count related information servers 10A and 10B are based on the terminal position information and the area position information. Since the predetermined area where the user terminals 501 to 50N existed at the time of counting is specified, the predetermined area can be specified using the terminal position information transmitted from the user terminals 501 to 50N, and the traffic volume As a result of the investigation, it becomes possible to easily collect and manage the necessary information without forcing troublesome work.

  In the above-described embodiment, the count execution information includes operation end time information indicating the time at which a predetermined count end operation is performed in the user terminals 501 to 50N, and the count related information servers 10A and 10B have the operation end time. Since the information is specified as the execution time information, one representative and appropriate time in each predetermined area can be specified as the execution time information without specifying each time at each count. The amount of execution information can be reduced.

  Further, in the above-described embodiment, the count indicating the number of times that the user terminals 501 to 50N have performed the count operation in the user terminals 501 to 50N in response to the predetermined count end operation in the user terminals 501 to 50N being performed. Since the count execution information including the operation number is generated and the count related information servers 10A and 10B are configured to specify the count operation number as the count number, it is not necessary to generate and transmit the count execution information for each count. The count execution information only needs to be generated and transmitted once after the count end operation, and the processing load can be reduced.

  Moreover, in embodiment mentioned above, predetermined area 900-904 is a boarding point periphery area where the passenger | crew of moving bodies, such as a bus, gets on and off, and a count number is the structure which is the number of passengers who got on and off the moving body. In this case, it becomes possible to easily collect and manage necessary information as a result of the traffic volume survey for investigating the number of passengers on the moving body such as a bus without complicating work.

  Further, in the above-described embodiment, the count related information management server 10 </ b> B is scheduled for operation in which the moving body identification information (route ID) that can uniquely identify the moving object to be operated is associated with the scheduled operation time. Scheduled operation time information DB 24 for storing information, mobile body identification information, and mobile body identification information DB 25 for storing mobile body identification information in which user terminal identification information capable of uniquely identifying user terminals 501 to 50N is associated. And the user is a driver 601 of the mobile object, the count execution information includes the user terminal identification information, and the count related information management server 10B refers to the mobile object identification information to the user terminal identification information. The mobile body identification information is also specified based on the configuration, and the count related information including the specified mobile body identification information is registered in the count related information DB 23. Can be counted by the user terminals 501 to 50N carried by the mobile driver, and collects and manages necessary information as a result of the traffic survey by a simple operation by the mobile driver. Will be able to.

  In the above-described embodiment, when the mobile driver 601 operates the user terminals 501 to 50N, the count execution information including the user terminal identification information is transmitted to the count related information management server 10B. The route ID indicating the route to be operated may be registered in the user terminals 501 to 50N, and the count execution information including the route ID may be transmitted to the count related information management server 10B. That is, the count related information management server 10B includes an operation schedule time information DB 24 that stores operation schedule time information in which mobile object identification information capable of uniquely specifying an object to be operated is associated with an operation schedule time. The user is the driver 601 of the mobile object, the count execution information includes the mobile object identification information (route ID), and the count related information management server 10B includes the mobile object identification information included in the count execution information. The related information may be registered in the count related information DB 23. In the case of such a configuration, the count related information management server 10B can be counted by the user terminals 501 to 50N carried by the driver of the mobile body without providing the mobile body specifying information DB 25. As a result of the traffic volume survey, the necessary information can be collected and managed by a simple operation by the driver of the moving body.

  Moreover, in embodiment mentioned above, count related information management server 10A, 10B is based on count related information, and count number list information including the count number in the boarding point periphery area about each moving object of each operation object Is generated and the count number list information is output, so that the result of the traffic volume survey can be easily browsed.

  Although not specifically mentioned in the above-described embodiment, the count related information management servers 10A and 10B and the user terminals 501 to 50N have various control programs (for example, count related information) stored in a storage device included in the count related information management servers 10A and 10B. In accordance with the management program, the above-described various processes (see FIGS. 6, 14, and 15) are executed.

  INDUSTRIAL APPLICABILITY The present invention is useful for easily collecting and managing necessary information as a result of a traffic volume survey without forcing a troublesome work.

10A, 10B Count related information management server 21 Area position information DB
22 Count execution information DB
23 Count related information DB
24 Scheduled operation time information DB
25 Mobile body identification information 30 Communication network 40 Base station 50 Display device 100A, 100B Count related information management system 201-20N Portable terminal 301-30N Count device 401, 402 Communication cable 501-50N User terminal

Claims (10)

A count related information management server for managing count related information including a count number counted by a user operation using a user terminal in a predetermined area,
Area position information storage means for storing area position information indicating the existence position of each predetermined area;
Count related information storage means for storing the count related information in which the predetermined area, the count time information indicating the time counted in the predetermined area, and the count number counted in the predetermined area are associated with each other;
Count execution information receiving means for receiving count execution information indicating that counting has been performed;
Based on the count execution information and the area position information, a predetermined area where the user terminal was present at the time of counting, execution time information indicating a time at the time of counting, and a predetermined area where the user terminal was present Identifying means for identifying the counted number
Count related information registration means for registering count related information including the predetermined area and count number specified by the specifying means and count time information which is execution time information specified by the specifying means in the count related information storage means And a count related information management server. The count related information management server according to claim 1, wherein the count execution information receiving unit receives the count execution information from the user terminal. The count execution information includes terminal location information indicating the location of the user terminal,
The count related information management server according to claim 1 or 2, wherein the specifying unit specifies a predetermined area where the user terminal was present at the time of counting based on the terminal position information and the area position information. The count execution information includes operation end time information indicating a time when a predetermined count end operation is performed on the user terminal,
The count related information management server according to claim 1, wherein the specifying unit specifies the operation end time information as the execution time information. The user terminal generates count execution information including a count operation number indicating the number of times the count operation has been performed on the user terminal in response to a predetermined count end operation being performed on the user terminal,
The count related information management server according to claim 1, wherein the specifying unit specifies the count operation number as the count number. The predetermined area is an area around a boarding point where passengers of moving bodies such as buses get on and off,
The count related information management server according to any one of claims 1 to 5, wherein the count number is the number of passengers who get on and off the mobile body. Including scheduled operation time information storage means for storing scheduled operation time information in which a moving object identification information capable of uniquely identifying an object to be operated is associated with an estimated operation time;
The user is a driver of the mobile body,
The count execution information includes the mobile object identification information,
The count related information management server according to claim 6, wherein the count related information registration unit registers count related information including mobile body identification information included in the count execution information in the count related information storage unit. A scheduled operation time information storage unit that stores scheduled operation time information in which a moving object identification information that can uniquely identify a moving object to be operated and an estimated operation time are associated with each other;
Mobile body identification information storage means for storing mobile body identification information in which the mobile body identification information is associated with user terminal identification information that can uniquely identify the user terminal;
The user is a driver of the mobile body,
The count execution information includes the user terminal identification information,
The specifying means also specifies the moving body identification information based on the user terminal identification information with reference to the moving body specifying information,
The count-related information management server according to claim 6, wherein the count-related information registration unit registers count-related information including mobile object identification information specified by the specifying unit in the count-related information storage unit. Based on the count related information, count number list information generating means for generating count number list information including the count number in the area around the boarding point for each moving object to be operated,
The count related information management server according to claim 7, further comprising: a count number list information output unit that outputs the count number list information. A count related information management program for causing a count related information management server to execute processing for managing count related information including a count number counted by a user operation using a user terminal in a predetermined area,
Area position information storage means for storing area position information indicating the presence position of each predetermined area, a predetermined area, count time information indicating a time counted in the predetermined area, and a count number counted in the predetermined area In the count related information management server comprising the count related information storage means for storing the count related information associated with
Count execution information reception processing for receiving count execution information indicating that counting has been performed;
Based on the count execution information and the area position information, a predetermined area where the user terminal was present at the time of counting, execution time information indicating a time at the time of counting, and a predetermined area where the user terminal was present Specific processing for identifying the count number counted by
A count related information registration process for registering count related information including the predetermined area and count number specified by the specifying process and count time information which is the execution time information specified by the specifying process in the count related information storage unit; Count related information management program to be executed.

Images