WO2019044455A1 - 施設状況把握システムおよび方法 - Google Patents
施設状況把握システムおよび方法 Download PDFInfo
- Publication number
- WO2019044455A1 WO2019044455A1 PCT/JP2018/030024 JP2018030024W WO2019044455A1 WO 2019044455 A1 WO2019044455 A1 WO 2019044455A1 JP 2018030024 W JP2018030024 W JP 2018030024W WO 2019044455 A1 WO2019044455 A1 WO 2019044455A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- information
- facility
- link
- status
- area
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Images
Classifications
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/26—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/10—Services
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/40—Business processes related to the transportation industry
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/005—Traffic control systems for road vehicles including pedestrian guidance indicator
Definitions
- the present invention relates to a system status grasping system and method.
- Patent Document 1 the causality of the characteristics of the human flow determined from the photographed image, the mobile object diamond information, and the station entry and exit history information is expressed as an effective graph, and the probability is calculated to directly observe the congestion degree.
- a technique is disclosed to estimate the degree of home congestion that can not be achieved.
- Patent Document 1 does not assume the ease of movement of the user in the definition of congestion, so the effect is that the state of congestion can be estimated. Therefore, in Patent Document 1, it is not possible to estimate a route easy for the user to move.
- the present invention has been made in view of the above problems, and provides a facility status grasping system and method capable of calculating the load when a user moves a route in a facility and improving convenience. It is to do.
- a facility status grasping system for grasping the status regarding the flow of the user in the facility, which comprises: A space network information storage unit that stores sensor space network related information that defines the correspondence between space network information defined in an area and each sensor placed in a facility, sensor information detected by each sensor, and a sensor space network A first status information creation unit for creating link status information indicating the status of the flow of the user on the link and area status information indicating the status of the flow of the user on the basis of the related information, and the link status Information and area status information, and information of a predetermined route to be estimated, which is defined by a combination of a link and an area Path information, based on the attribute information of the user, by calculating the load when moving the predetermined path, and a moving load information creation unit that creates a movement load information.
- facility can be calculated, and the convenience can be improved.
- Explanatory drawing which shows the component of space network information typically.
- the figure which shows the example of a data structure of event influence information The figure which shows the data structural example of condition propagation information.
- the flowchart of the process which produces the status information of a sensor non-installation location The figure which shows the example of a screen delivered to a user terminal. The figure which shows another screen example.
- the facility status grasping system 1 includes the spatial network information 106 configured by a combination of the node 301, the link 302, and the area 303, and the relationship between the sensor 111 installed in various places of the facility and the spatial network information 106.
- the space network information storage unit 107 holding the sensor space network related information 105 to be defined, the sensor information 1111 acquired from the sensors 111 installed at various places of the facility, and the link status information 1081 based on the sensor space network related information 105
- a sensor installation location status information creation unit 101 that creates area status information 1082, link status information 1081 and area status information 1082 created by the sensor installation location status information creation unit 101, route information 1092 to be estimated, and attribute information Based on 1093 and Comprising a moving load information creation unit 104 for calculating a moving load information 1091 for each place of ⁇ , the.
- Sensors 111 can be located anywhere in the facility. However, the sensors 111 need not be arranged to cover all the routes in the facility. In the present embodiment, when the sensor 111 is partially installed in each route in the facility, the sensor non-installation location status information creation unit 103 estimates the human flow 304 in the location where the sensor 111 is not installed.
- the sensor non-installed location status information creation unit 103 as the “second status information estimation unit” includes the information 1081 and 1082 created by the sensor installation location status information creation unit 101 as the “first status information estimation unit” and the situation propagation analysis. Based on the information analyzed by the unit 102, a human flow 304 at a location where the sensor 111 is not installed is estimated.
- the situation propagation analysis unit 102 detects an event causing a change in the human flow 304 in the facility by comparing a plurality of link situation information 1081 and the area condition information 1082, and propagates the change in the human flow 304 due to the event into the facility.
- Situation propagation information 1083 (see FIG. 2) indicating the situation is created.
- the situation propagation analysis unit 102 Based on the situation propagation information 1083 created in the past, the situation propagation analysis unit 102 identifies the range where the change of the human flow 304 occurs due to the detected event, and creates the situation propagation information 1083 about the event for the identified range. It is also good.
- the user having the attribute moves the predetermined route. Calculate the load when walking (walkability).
- the predetermined route may be automatically selected by specifying the user's departure place and destination in the facility.
- a main route with many users may be registered in advance, and a part or all of the registered main routes may be selected as a predetermined route to be estimated.
- the facility status grasping system 1 creates, as at least a part of the moving load information 1091, a screen in which the load (also referred to as moving load) on the predetermined route scheduled to move by the user is associated with the predetermined route. , To provide users.
- the users here can include a person who moves in the facility using the facility status grasping system 1, a person who manages passage of the facility, and the like.
- the flow (person flow) 304 of the user moving in the facility can be estimated, and the load when the user moves can be calculated.
- the movement situation of a facility can be managed and usability improves.
- a facility situation grasping system 1 which grasps the situation of the flow of people and estimates a place and a route easy to move.
- FIG. 2 is a network configuration diagram including the facility status grasping system 1 according to the present embodiment.
- the facility status grasping system 1 is connected to sensors 111 installed in various places of the facility via a communication network 120. Further, the facility status grasping system 1 is connected to a user terminal 112 which is a terminal held by a user who uses the system 1 via the communication network 121.
- the communication network 120 and the communication network 121 may be a common communication network or may be networks using different protocols.
- the communication networks 120 and 121 may be either wired networks or wireless networks.
- the facility status grasping system 1 in such a network environment transmits / receives data to / from the sensor 111 and the user terminal 112 via the communication unit 110.
- the sensor 111 is a sensor that observes the condition in the facility.
- a monitoring camera an operation management system, a ticket gate system or the like can be used.
- the operation management system manages the operation status of trains arriving and departing from the station.
- the ticket gate system detects a user who passes the ticket gate.
- a sensor such as an ultrasonic sensor, an infrared sensor, a laser radar or the like may be used.
- a plurality of sensors 111 are installed at various places in the facility and connected to the facility status grasping system 1. Several types of sensors may be connected to the system 1.
- the sensor 111 may be directly connected to the facility status grasping system 1, or may be connected to the system 1 through a centralizing apparatus, a relay apparatus, or the like.
- the sensor 111 may transmit the raw data detected by the sensor 111 as it is as sensor information 1111 to the facility situation grasping system 1 as it is.
- the processing circuit in the sensor 111 or an apparatus installed between the sensor 111 and the system 1 processes the raw data detected by the sensor 111 to generate sensor information 1111, and the processed sensor information 1111 is generated. It may be sent to the system 1.
- the user terminal 112 is a terminal that a user of a station holds in an individual or a terminal that a traffic provider uses for business.
- the user terminal 112 may be, for example, a mobile phone (including a so-called smartphone), a portable information terminal, a so-called wearable terminal such as a goggle type, glasses type, bracelet type, wrist watch type, a notebook type personal computer, a tablet type personal computer A desktop type personal computer etc. can be mentioned.
- the facility status grasping system 1 is constructed on a server computer described later with reference to FIG. 3, and realizes each of the functions 101 to 109 by using computer resources such as a microprocessor, a memory, and a computer program.
- the facility status grasping system 1 includes a sensor installation location status information creation unit 101, a condition propagation analysis unit 102, a sensor non-installation location status information creation unit 103, a movement load information creation unit 104, a communication unit 110, and a space network information storage unit.
- the information processing system 107 includes a situation information storage unit 108 and a movement load information storage unit 109.
- the space network information storage unit 107 stores space network information 106 and sensor space network related information 105.
- the space network information 106 is information obtained by modeling route components constituting a route in a facility such as a location in a station yard and equipment as a network structure in which nodes, links and areas are network components.
- the space network information 106 stores, as node information 1061, link information 1062 and area information 1063, a network structure modeled from network components of nodes, links and areas.
- the sensor space network related information 105 indicates information indicating the relationship of which network component of the network components included in the space network information 106 the sensor 111 for observing the condition in the facility can grasp. Store.
- the space network information 106 and the sensor space network related information 105 are information independent of externally input information such as detection data of the sensor 111 or a request from the user terminal 112, and are created at the time of system construction or repair. However, in the case where the structure of the facility or the passable place suddenly changes due to the construction or the closing of the road, the space network information 106 and the sensor space network related information 105 may be dynamically updated. Details of data configuration examples of the information 105 and 106 will be described later.
- the sensor installation location status information creation unit 101 creates link status information 1081 and area status information 1082 based on the sensor information 1111 acquired from the sensors 111 installed at various places of the facility and the sensor space network related information 105. It is a functional module stored in the situation information storage unit 108. As shown in FIG. 3, such functional modules are implemented by a computer forming the facility status grasping system 1 executing a predetermined program (the same applies to the following).
- the sensor information 1111 may be raw data as observed by the sensor 111, or data obtained by processing the raw data so as to be easy to use, or even if the sensor 111 does not directly observe it.
- the data may be data estimated by another means (operation management system, ticket gate system, etc.), or may be data in which a plurality of sensor information are integrated. Details of processing in the sensor installation location status information creation unit 101 will be described later.
- the movement load information creation unit 104 is a functional module that calculates the load (movement load) when the user moves along the route, and creates movement load information 1091.
- Mobile load information creation unit 104 is based on link status information 1081 and area status information 1082 held by status information storage unit 108, and route information 1092 and user attribute information 1093 held by mobile load information storage unit 109. The mobile load is calculated, and mobile load information 1091 is created.
- the route information 1092 and the attribute information 1093 may create a pattern in advance, or may be acquired from the user request 1121 input from the user terminal 112. Details of the processing and the like in the movement load information creation unit 104 will be described later.
- the situation propagation analysis unit 102 is a functional module that creates the situation propagation information 1083 and stores it in the situation information storage unit 108.
- the condition propagation analysis unit 102 compares the link condition information 1081 and the area condition information 1082 possessed by the condition information storage unit 108 with the movement load information 1091 possessed by the movement load information storage unit 109 and compares the condition propagation by Information 1083 is created. Details of the processing of the situation propagation analysis unit 102 will be described later.
- the sensor non-installation location status information creation unit 103 is a functional module that creates the link status information 1081 and the area status information 1082 and stores the link status information 1081 and the area status information 1082 in the status information storage unit 108.
- the sensor non-installed location status information creation unit 103 is based on the sensor information 1111 of any sensor 111 or the link status information 1081 and the area status information 1082 and the status propagation information 1083 that the status information storage unit 108 has.
- the link status information 1081 and the area status information 1082 at the places not installed are created. Details of the processing of the sensor non-installation location status information creation unit 103 will be described later.
- the communication unit 110 is a functional module that performs communication processing with an external device such as each sensor 111 and each user terminal 112 via the communication networks 120 and 121.
- the communication unit 110 is implemented by an appropriate communication device such as a network interface card provided in a computer that constitutes the facility status grasping system 1.
- FIG. 3 is a diagram showing an example of the hardware configuration of the facility status grasping system 1 and the user terminal 112. As shown in FIG.
- the facility status grasping system 1 is realized using, for example, a computer (server computer) in which the storage device 201, the memory 202, the microprocessor (CPU in FIG. 20) 203, and the communication device 204 are communicably connected by a bus 205.
- a computer server computer
- the storage device 201, the memory 202, the microprocessor (CPU in FIG. 20) 203, and the communication device 204 are communicably connected by a bus 205.
- the storage device 201 includes, for example, an appropriate non-volatile storage element such as a solid state drive (SSD) or a hard disk drive.
- the memory 202 is configured of a volatile storage element such as a RAM.
- the microprocessor 203 executes the program 2011 and the data 2012 held in the storage device 201 by reading them into the memory 202 and the like, and performs general control of the computer system 1, and performs various determinations, operations and control processing.
- the communication device 204 implements the communication unit 110, and performs communication processing with an external device (the sensor 111 and the user terminal 112) via the networks 120 and 121.
- the storage device 201 in addition to the computer program 2011 for mounting the functional modules 101 to 104 and 110 necessary for the facility status grasping system 1 of the present embodiment, information held by the storage units 107 to 109 is also stored. ing.
- the user terminal 210 is also realized using, for example, a computer (client computer) in which a storage device 211, a memory 212, a microprocessor 213, a communication device 214, and a user interface device (UI device) 216 are connected by a bus 215.
- the microprocessor 213 reads the computer program 2111 stored in the storage device 211 into the memory 212 and executes it to realize a function for using the facility status grasping system 1.
- the service of the facility status grasping system 1 can be used via a web browser.
- the storage device 211 in addition to the computer program 2111 such as a web browser, login information for using the facility status grasping system 1, attribute information of the user using the user terminal 112, and data 2112 such as current position are stored. can do.
- the space network information 106 of the facility status grasping system 1 models the location and equipment in the station yard as a network structure having nodes, links and areas as components, and stores them as node information 1061, link information 1062 and area information 1063. .
- the node 301, the link 302 and the area 303 are schematically shown in FIG.
- the network showing the structure of the location and equipment in the station yard has a node 301 (white circle), a link 302 (solid line), and an area 303 (dotted line) as components.
- a node 301 white circle
- a link 302 solid line
- an area 303 dotted line
- the direction of the arrow indicates the movement direction
- the thickness indicates the number of people
- the length indicates the movement speed.
- Node 301 is assigned to any point in the facility.
- a line connecting two nodes is defined as a link 302.
- a range including a plurality of nodes inside is defined as an area 303.
- the node 301 is arranged, for example, at an entrance of a station, a point where the flow of people changes (start and end points of stairs, a ticket gate, and the like).
- Whether to allocate the link 302 or the area 303 to the location connecting the plurality of nodes 301 is determined according to the pattern of the situation change (for example, the flow of people).
- a link 302 is assigned to a place where the direction of the human flow 304 is fixed.
- a narrow aisle is a place where there are only two-way flows, whether the user walks forward or backwards.
- an area 303 is allocated to a place where the direction of the human flow 304 is not determined. For example, like a concourse before a ticket gate, a person walks towards a ticket gate, a person walks toward a ticket machine, a person walks toward a stair, etc., each person heads in the direction of falling apart at the speed of falling apart A place that is
- the area 303 may be formed by connecting the nodes 301, or may be set to surround the node 301 in accordance with the facility (such as a wall) of the facility.
- the data configuration of the node information 1061 is made up of records in which the values of the coordinates 10613 and the expiration date 10615 are associated using the node ID 10611 as a key.
- the node ID 10611 is a name or identification code for uniquely identifying a record.
- the coordinate 10613 is information for uniquely identifying the position of a node in a facility, and is represented by, for example, a combination of X coordinate, Y coordinate, and hierarchy based on an arbitrary place.
- the expiration date 10615 is information indicating availability of the node by day or by time. For example, at the outlet sealed by time, the condition value of the seal is stored in the expiration date 10615.
- the data configuration of the link information 1062 is made up of records in which start point node ID 10622, end point node ID 10623, link type 10624, link length 10625, link width 10626, and expiration date 10627 are associated using link ID 10621 as a key. .
- the link ID 10621 is a name or identification code for uniquely identifying a record.
- the start point node ID 10622 and the end point node ID 10623 are names or identification codes for uniquely identifying nodes given to both ends of the link, and use the node ID defined in the node information 1061.
- the link type 10624 is information in which links are classified by type, and the types are classified according to ease of movement (such as barrier-free), such as a path, stairs, escalator, and elevator.
- the link length 10625 is information on the link length, and it can be seen that, for example, the longer the length, the longer it takes to move.
- the link width 10626 is information on the width of the link, and for example, it can be understood that the wider the width, the larger the number of people can be accommodated.
- the expiration date 10627 is information indicating availability of the link by day or by time. For example, in the passage which becomes closed by time, the condition value of closed door is stored in the expiration date 10627.
- the data configuration of the area information 1063 is made up of records in which internal node ID 10633, area type 10633, area area 10635, and expiration date 10637 are associated using area ID 10631 as a key.
- the area ID 10631 is a name or an identification code for uniquely identifying a record.
- the internal node ID 10633 is a name or identification code for uniquely identifying a node present inside the area, and uses the node ID defined in the node information 1061. Note that the number of nodes present inside differs depending on the area.
- the area type 10633 is information in which areas are classified according to type, and for example, the types are classified according to differences in human flows such as before a ticket gate (outside a ticket gate), before a ticket gate (within a ticket gate), event space, and home.
- the area area 10635 is information on the area of the area, and for example, it can be understood that the larger the area, the larger the number of people can be accommodated.
- the expiration date 10637 is information indicating availability of the area by day or by time. For example, in a concourse in which an event is performed and a passable area is limited depending on the day of the week, the condition value of the passable range is stored in the expiration date 10637.
- the data configuration of the sensor space network related information 105 is configured of a space network type 1055 and a space network ID 1057 using the sensor ID 1053 as a key.
- the sensor ID 1053 is a name or an identification code for uniquely identifying a record and a sensor.
- the space network type 1055 is a name or an identification code that can specify whether the location where the situation can be observed from the sensor is a link or an area.
- the space network ID 1057 is a name or identification code for uniquely identifying a link or area where the sensor can observe the situation, and is a link ID defined by the link information 1062 or an area ID defined by the area information 1063.
- the sensor space network related information 105 associates one link or area with one sensor.
- the link or area may be divided into a plurality, or sensor information acquired from a plurality of sensors may be integrated. As described above, even if the sensor 111 does not directly observe, data estimated by another means can be used as the sensor information 1111.
- the process of the sensor installation place status information creation unit 101 will be described with reference to FIG.
- the present process may be started at any timing at which the sensor 111 transmits the sensor information 1111 or may be started at any timing set inside the facility status grasping system 1.
- the process of FIG. 9 is performed independently for each sensor 111 at each timing.
- the sensor installation location situation information creation unit 101 acquires sensor information 1111 from each sensor 111 (S1011).
- sensor information 1111 is assumed to be video information of a monitoring camera.
- the sensor information 1111 acquired from the monitoring camera 111 is configured as data in which each value of a sensor ID for uniquely identifying the sensor 111 and an image capturing time is added to image data.
- the sensor installation location status information creation unit 101 analyzes the acquired sensor information 1111 to process it into sensor processing information having items that are easy to handle or necessary for grasping the facility status (S1013).
- step S1013 for example, the person area is detected from the video information, and the feature amount of the person area is extracted.
- the configuration of the sensor processing information data in the present embodiment is each obtained by associating each value of the sensor ID, the video shooting date, and the feature amount of the person area (number of people, population density, movement direction of individual, movement speed, etc.) Composed of records.
- step S1011 and step S1013 may be performed outside the facility status grasping system 1. Instead of acquiring the sensor information 1111 from the outside of the facility status grasping system 1, the sensor information 1111 may be acquired from a sensor installed inside the system 1.
- the sensor installation location status information creation unit 101 determines which of the link and the area the sensor processing information processed in step S1013 is associated with in the space network in the facility (S1015). Sensor space network related information 105 is used for this determination. If the sensor ID of the sensor processing information and the record of the sensor space network related information 105 with which the sensor ID 1053 matches are extracted and the information indicating the link is stored in the space network type 1055, the process proceeds to step S1017. If the information indicating the area is stored in 1055, the process proceeds to step S1018.
- the sensor installation place status information creation unit 101 determines in step S1015 that the link is "link”
- the sensor installation location status information creation unit 101 creates link status information 1081 based on the sensor processing information created in step S1013 (S1017). Details of the link status information 1081 will be described later.
- the sensor installation location status information creation unit 101 determines that the area is the area at step S1015, the sensor installation location status information creation unit 101 creates area status information 1082 based on the sensor processing information created at step S1013 (S1018). Details of the area status information 1082 will be described later.
- the sensor installation place status information creation unit 101 stores the link status information 1081 or the area status information 1082 created in step S1017 or step S1018 in the status information storage unit 108 (S1019). Above, the process of the sensor installation location situation information creation part 101 is complete
- the data configuration of the link status information 1081 includes, for example, link ID 10811, date and time 10813, direction 10815, number of passing people 10816, occupancy width 10817, speed average 10818, speed dispersion 10814, and sensor presence / absence 10819.
- the link ID 10811 uses the link ID defined in the link information 1062.
- the date and time 10813 uses the value of the video monitoring date and time of the sensor processing information created in step S1013.
- the direction 10815, the passing number 10816, the occupancy width 10817, the velocity average 10818, and the velocity dispersion 10814 are calculated from the values (number of people, population density, movement direction of individual, movement speed, etc.) of person area of sensor processing information.
- the direction 10815 is a name or identification code for identifying whether the direction of the human flow 304 flows from the start point to the end point or from the end point to the start point.
- two records are generated for the direction with link ID 10811 and date and time 10813 having the same value.
- the passing number of people 10816 is information on the number of people moving in the corresponding direction per unit area and unit time.
- the occupied width 10817 is information of the width occupied by the person moving in the relevant direction among the width of the passage.
- the maximum value of the width is the value of the link width 10626 stored in the record of the link ID 10621 of the link information 1062.
- the velocity average 10818 is information on the average of the velocity of a person moving in the relevant direction.
- the velocity dispersion 10814 is information on the dispersion of the velocity of a person moving in the direction.
- the sensor presence / absence 10819 is a name or an identification code for identifying whether the record is a record created by the sensor installation location status information creation unit 101 or a record created by the sensor non-installation location status information creation unit 103. is there. Details of the processing of the sensor non-installation location status information creation unit 103 will be described later.
- the data configuration of the area status information 1082 includes, for example, area ID 10821, date and time 10823, population density 10824, moving line average 10827, moving line disturbance 10828, and sensor presence / absence 10829.
- the area ID 10821 uses the area ID defined in the area information 1063.
- the date and time 10823 uses the value of the image monitoring date and time of the sensor processing information created in step S1013.
- the population density 10824, the flow line average 10827, and the flow line disturbance 10828 are calculated from the values (number of people, population density, movement direction of individual, movement speed, etc.) of the person area of the sensor processing information.
- the population density 10824 is information on the number of people present in the area per unit area and unit time.
- the moving line average 10827 is an average vector of the entire user when the movement information of each user in the area is represented as a vector of two axes.
- the vector can be expressed using the two axes in the coordinate expression used in the coordinate 10613 of the node information 1061 and the vector direction can be expressed as the moving direction and the length as the velocity.
- the disturbance of the movement line 10828 is information that numerically represents how much the movement line vector of the individual moving in the area is disturbed.
- Each value of the motion line average 10827 and the motion line disturbance 10828 may be obtained by a general vector average or correlation coefficient, or may be obtained by a unique calculation formula.
- the sensor presence / absence 10829 is a name or an identification code for identifying whether it is a record created by the sensor installation location status information creation unit 101 or a record created by the sensor non-installation location status information creation unit 103. is there. Details of the processing of the sensor non-installation location status information creation unit 103 will be described later.
- the movement load is an index that represents the load on movement at a specific time, a specific place, and a person with a specific attribute.
- the user request 1121 as an input of the movement load information creation unit 104 will be described.
- the route information 11211 held by the user request 1121 is a set of links and areas that the user is planning to move.
- An example data configuration of the route information 11211 will be described using FIG.
- the route information 11211 includes, for example, a space network type 112111, a space network ID 112113, a date and time 112115, a start point node ID 112117, and an end point node ID 112119.
- the space network information type 112111 is a name or an identification code that can specify whether the location to which the user is moving is either a link or an area.
- the space network ID 112113 is a name or identification code for uniquely identifying the link or area, and uses the link ID defined in the link information 1062 or the area ID defined in the area information 1063.
- the date and time 112115 is information on the date and time when it is planned to move the link or area.
- the date and time 112115 may be wide-ranging information (such as a certain day or a certain time zone).
- the start point node ID 112117 and the end point node ID 112119 are information indicating the moving direction when moving the link or area, and indicate moving from the start point node 112117 toward the end point node ID 112119.
- the attribute information 11212 held by the user request 1121 is information that holds the attribute of the user, and is, for example, information of an attribute that can affect mobility such as general commuter, wheelchair user, traveler, gender, and age.
- Store The type of the attribute may be previously defined in the facility status grasping system 1 and may be selected by the user.
- the route information 1092 of the moving load information storage unit 109 is a set of route patterns when the route information 11211 of the user request 1121 is one pattern.
- the attribute information 1093 of the movement load information storage unit 109 is a set of attribute patterns when the attribute information 11212 of the user request 1121 is one pattern.
- the processing flow of the movement load information creation unit 104 will be described using FIG.
- the flowchart shown in FIG. 13 is started at a predetermined timing.
- the movement load information creation unit 104 acquires route information 11211 and attribute information 11212 held by the user request 1121 acquired from the user terminal 112. Alternatively, from the route information 1092 and the attribute information 1093 stored in advance in the moving load information storage unit 109, the pattern of the route information and the pattern of the attribute information to be the target of the moving load calculation are acquired (S1041). The following description will be given assuming that the user request 1121 has been acquired.
- the movement load information creation unit 104 repeatedly executes the processing from step S1043 to step S1046 for all the records of the route information 11211 acquired in step S1041 (S1042).
- the movement load information creation unit 104 determines whether the status information corresponding to one record of the route information acquired in step S1041 is stored in the link status information 1081 or the area status information 1082 of the status information storage unit 108, as route information. A search is made using each value of 11211 as a key (S1043).
- the movement load information creating unit 104 proceeds to step S1044, and if the status information does not exist (S1043: NO), the repetition load is ended and the process proceeds to the next loop. . If status information is present, obtain data to use that information in subsequent steps.
- step S1043 it is determined whether the record indicates link information or area information using the space network type 112111 of the route information 11211 as a key. It selects (S1044).
- step S1044 area
- step S1046 If the record indicates an area (S1044: area), the process proceeds to step S1046. If the record indicates a link (S1044: link), the process proceeds to step S1045 (S1044). The order of step S1043 and step S1044 may be reversed.
- the mobility load information creation unit 104 calculates link mobility load based on the link status information 1081 acquired in step S1043 and the corresponding link information 1062.
- the movement load is a value representing barrier-free equipment, required time, degree of collision, degree of residence, and the like as numerical values.
- a barrier-free facility information of facilities such as aisle, stairs, escalators, and elevators is acquired from the link type 10624 of the link information 1062 corresponding to the link, and the movement load is quantified by using, for example, a point system.
- equipment having a high moving load such as stairs can express moving loads as numerical values by providing high points or creating a unique calculation formula using numerical values such as the width and inclination of the passage.
- the points and formulas are changed for each attribute.
- the moving speed is generally lowered, and the user can not walk freely, and he will proceed by multiplying the existing flow.
- the link length refers to the link length 10625 of the link information 1062
- the surrounding speed refers to the speed average 10818 of the link status information 1081.
- a general average value for each attribute of the user may be stored in advance, or a value unique to the user may be set.
- Switching of processing of whether free walking or ambient flow is multiplied is performed by setting a threshold to population density (calculated from the number of passing people 10816 of the link status information 1081 and the occupancy width 10817) or setting a threshold for moving speed.
- the travel speed restrictions by the facility such as the speed of the escalator are also stored in advance.
- the collision degree uses the speed distribution 10814 of the link status information 1081. For example, as the frequency of collision increases, free walking can not be performed, and the dispersion of the velocity among users should be large. Therefore, the velocity dispersion 10814 is used as the degree of collision. Alternatively, you may create your own formula to calculate the degree of collision.
- the retention degree will be described. For example, when the speed average 10818 of the link status information 1081 of the link remains at a low speed such as 20 m / min, it is assumed that the link is stagnant and immobile. Therefore, if you know the time until the stay is resolved (for example, if you know the time until the train arrives, you can calculate from the processing capacity of the ticket gate or the window, etc.) Used as retention. You may create your own formula to calculate the degree of residence.
- step S1045 When the residence spreads (people overflow) to the link or area adjacent to the staying link, the degree of residence in the adjacent link or area is also taken into consideration.
- the degree of residence is the residence elimination time, the residence time may be added to the required time. The above is the process of step S1045.
- step S1044 If it is determined in step S1044 that the record is area information, the area movement load is calculated based on the area status information 1082 acquired in step S1043 and the corresponding area information 1063.
- the moving direction is not determined in advance, and the situation information is not associated with the moving direction.
- the moving direction in the area can be determined from the start point node ID 112117 and the end point node ID 112119 of the path information 11211. Therefore, in order to calculate the movement load in the area, a dummy link having the start point node ID 112117 and the end point node ID 112119 as both end points is set, and the movement load when moving on the dummy link is calculated.
- the dummy link length and the dummy link direction are defined using the area information 1063 corresponding to the area (S1046).
- the dummy link length calculates the distance between two points from coordinates 10613 defined by the node information 1061 corresponding to the start point node ID 112117 and the end point node ID 112119 of the route information 11211. If the movement locus is not clearly a straight line, the movement distance may be defined in advance.
- the dummy link direction is represented by a vector, like the flow line average 10827 and the flow line disturbance 10828 of the area status information 1082.
- the movement load information creation unit 104 calculates the area movement load based on the area status information 1082 acquired in step S1043 and the corresponding area information 1063 and the dummy link set in step S1046.
- the movement load is a value representing the barrier-free equipment, the required time, the degree of collision, the degree of residence, and the like as numerical values, and the basic processing flow is the same as in step S1045. The differences from step S1045 and details of the different processing will be described below.
- the barrier-free facility uses the area type 10633 of the area information 1063 as a reference destination for acquiring the facility information.
- the reference destination is not the link type 10624 of the link information 1062 described in step S1045.
- the other processes are the same as in step S1045.
- the sensor installation location situation information creation unit 101 refers to the movement speed and movement direction of the individual from the feature value of the person area of the sensor processing information created in S1013, and the direction vector of the dummy link set in step S1046 The user group moving in the direction of high correlation is extracted, and the movable speed of the user is calculated from the average value of the moving speed of the user group.
- the relationship between the population density, the flow line average, the flow line disturbance, and the movable speed may be obtained by observation or simulation and may be defined.
- the movement load information creation unit 104 can calculate the required time if the movement speed can be calculated. As in the escalator described in step S1405, when there is a restriction on the moving speed, calculation is performed using that value.
- the degree of collision will be described. For example, since the disturbance of the flow line for each user should be larger as the collision frequency is higher, the flow line irregularity 10828 of the area status information 1082 corresponding to the area is used as the collision degree. You may create your own formula to calculate the degree of collision.
- the residence degree can be processed in the same manner as step S1405, for example, since the length of the flow line average 10827 of the area status information 1082 of the area indicates the speed.
- the above is the process of step S1047.
- the movement load information creation unit 104 calculates the link movement load and area movement load calculated for each record for each movement load item (required time for required time, collision degree for collision degree) , And stored in the movement load information storage unit 109 as movement load information 1091 (S1408). Alternatively, the mobility load information creation unit 104 transmits the mobility load information 1091 to the user terminal 112 as a response to the user request 1121 received from the user terminal 112 (S1408).
- the data configuration example of the mobile load information 1091 is obtained by adding an integrated value for each mobile load item to each record of the route information 11211.
- it may be a total of numerical values if it is a required time.
- the maximum calculation value of the movement load is set as the movement load of the entire route, or the calculation formula of integration is set for each movement load item.
- the movement load value of the entire route is not necessarily calculated as a single numerical value, and a plurality of values relating to a representative or characteristic link or area may be picked up and expressed.
- the situation propagation analysis unit 102 analyzes how the situation change is propagated to each place based on the situation information of the sensor installation place. Then, based on the analysis result of the situation propagation, the sensor non-installation location situation information creation unit 103 creates the situation information of the location where the sensor is not installed.
- FIG. 14 is a flowchart showing processing performed by the situation propagation analysis unit 102. This process starts at an arbitrary timing set inside the facility status monitoring system 1. Synchronization with other processes is not necessary.
- the situation propagation analysis unit 102 constantly monitors sensor information of an arbitrary sensor 111 (for example, monitors at predetermined time intervals such as every one minute), and detects an event that may cause a change in the situation (S1021).
- the sensor in this case may be other than the sensor 111 and the sensor information 1111 which the sensor installation location situation information creation unit 101 has referred to in order to create the situation information.
- the vehicle monitors the train arrival and departure information in the operation management system, the ticket counter number information by the ticket gate system, and the like, and detects an event giving a change in the situation such as arrival of trains and a sharp increase in the number of ticket gates.
- step S1021 the sensor and sensor information referred to by the sensor installation location status information creation unit 101 for creating status information may be used.
- the link status information 1081 and the area status information 1082 created by the sensor installation location status information creating unit 101 or the mobile load information 1091 created from them are constantly monitored.
- the status change is detected as an event occurrence.
- the area status information 1082 when the population density 10824 or the disturbance of the flow 10828 exceeds a predefined threshold, the status change is detected as an event occurrence.
- the value of the movement load (barrier-free equipment, required time, degree of collision, retention degree, etc.) for each movement load item created in step S 1048 of the movement load information creation unit 104 is previously defined.
- the threshold is exceeded, the status change is detected as an event occurrence.
- items of data used to detect these status changes are referred to as status items.
- the situation propagation analysis unit 102 determines whether the event detected in step S1021 is a known event (S1022).
- step S1022 If it is a known event (S1022: YES), the process proceeds to step S1023. If it is an unknown event (S1022: NO), the process proceeds to step S1024 (S1022). The description of the determination criteria for determining whether an event is known or unknown will be described later. Here, assuming that all the events detected in step S1021 are unknown, the processes after step S1024 will be described. Details of the process of step S1023 will be described later.
- the situation propagation analysis unit 102 designates a place where the event is detected in step S1021 or a place which is surely affected by the event, and places around it (for example, a reference All places within a certain distance from the place are extracted (S1024).
- the reference location designated here and the surrounding location to be extracted are all links or areas having link status information 1081 or area status information 1082.
- the situation propagation analysis unit 102 repeatedly executes the processing of step S1026 and subsequent steps on all the places extracted in step S1024 (S1025). Furthermore, the processing after step S1027 is repeatedly executed for each combination of the condition items of the reference place and the extraction place in step S1025 (S1026).
- Situation items to be compared may be freely set for each place.
- the repeated loop compare the time series data (for example, data created every 10 minutes from 10 minutes before to 10 minutes after) of each status item of the reference place and the extraction place for each combination of the situation items Then, the similarity and the time difference are calculated (S1027). For example, cross correlation analysis of time series data is used to calculate the degree of similarity and the time difference.
- the situation propagation analysis unit 102 compares the similarity calculated in step S1027 with a predefined threshold Th (S1028). When the similarity is equal to or higher than the threshold Th (S1028: YES), the situation propagation analysis unit 102 creates the situation propagation information 1083, since the situation (people flow) is propagated between the locations of the two combinations. It stores in the information storage unit (S1029).
- step S1028 the process proceeds to a loop following the repetition of step S1026. Details of the situation propagation information 1083 will be described later. Above, the process of the condition propagation analysis part 102 is complete
- step S1022 shown in FIG. 14 and the details of step S1024 will be described.
- step S1022 in order to determine whether an event is known or unknown, event influence information shown in FIG. 15 is used.
- the event influence information is information specifying an influence range in which the situation change may occur according to the pattern of the event based on the past processing results of the situation propagation analysis unit 102.
- the event influence information includes, for example, an event ID 901, an expiration date 903, an influence space network type 905, an influence space network ID 907, and an influence status item 909.
- the event ID 901 is a name or an identification code for uniquely identifying the event described in step S 1021, and stores an ID of an event that may be influenced by a situation change from the past tendency.
- the expiration date 903 is information on the day of the week or the time zone that affects the range in which the event is stored in the record. Only the date and time corresponding to this expiration date can refer to the record.
- the influence space network type 905 is a name or an identification code that can specify whether the event where the event influences the situation change is a link or an area.
- the influence space network ID 907 is a name or an identification code for uniquely identifying a link or area where the event affects the situation change, and is defined in the link ID defined in the link information 1062 or in the area information 1063. Use the specified area ID.
- the influence status item 909 is information on the status item of the link or the area affected by the event.
- step S1022 it is searched whether there is a record corresponding to the event detected in step S1021 out of the event ID 901 and the expiration date 903 of the event influence information, and if the corresponding record is found, it is a known event. It determines with it and progresses to step S1023.
- step S1022 If it is determined in step S1022 that the event is a known event, the place and status items affected by the event detected in step S1021 are extracted by limiting to only those described in the record found in the event influence information. (S1023). In the processing after step S1025, only the extraction location and the status item need to be the target of repetition, so the number of repetition of step S1025 decreases as the event is known.
- the situation propagation information 1083 is information that holds a combination of places where the situation change is propagated and the time difference of the propagation.
- the data configuration of the situation propagation information 1083 includes, for example, an event ID 10831, a reference space network type 10832, a reference space network ID 10833, a comparison space network type 10834, a comparison space network ID 10835, a reference time 10836, a time difference 10837, and a similarity 10838.
- the event ID 10831 is a name or identification code for uniquely identifying an event that has caused a change in status.
- the event ID 10831 may not necessarily be a specific event, as long as it can uniquely identify an event by time or place, such as “an event that occurred at the first track home at 7 o'clock”.
- the reference space network type 10832 is a name or an identification code that can specify whether the place set as the reference place is the link or the area when calculating the similarity and the time difference in step S1027.
- the reference space network ID 10833 is a name or identification code for uniquely identifying the reference place, and uses a link ID defined in the link information 1062 or an area ID defined in the area information 1063.
- the comparison network type 10834 can specify whether the location set in the comparison location (the extraction location and the description in S1027) is the link or the area when calculating the similarity and the time difference in step S1027. It is a code.
- the comparison space network ID 10835 is a name or identification code for uniquely identifying the comparison place, and uses a link ID defined in the link information 1062 or an area ID defined in the area information 1063.
- the reference time 10836 is information on the date and time when a change in condition is detected at the reference place.
- the time difference 10837 is information on the difference between the time at which the status change of the reference place and the comparison place occurs.
- the similarity 10838 is information on the similarity between the time-series change of the reference place and the comparison place. In the time difference 10387 and the similarity 10838, the result calculated by the cross-correlation analysis or the like in step S1027 of the situation propagation analysis unit 102 is stored.
- the sensor non-installation location situation information creation unit 103 can create the link status information 1081 and the area status information 1082 at the sensor non-installation location. Then, the process which the sensor non-installation location status information creation part 103 performs is demonstrated using FIG. The process shown in FIG. 17 starts at an arbitrary timing set inside the facility status grasping system 1. Note that this process does not require synchronization with other processes.
- the sensor non-installed location situation information creation unit 103 determines the location (link or area) where the sensor is not installed to be estimated and the time (S1031).
- the target of estimation may be set in advance in the facility situation grasping system 1 in advance, or may be specified by the user request 1121 of the user terminal 112, for example.
- the sensor non-installation location status information creation unit 103 extracts all locations corresponding to locations around the location determined in step S1031 (for example, locations within a certain distance from the reference location) (S1032).
- the reference place and the places around the reference place are all links or areas having link status information 1081 or area status information 1082.
- the sensor non-installation location situation information creation unit 103 determines whether the estimation target determined in step S1031 corresponds to a via point of situation propagation (S1033). When the place to be estimated corresponds to the passing point (S1033: YES), the process proceeds to step S1034. If the place to be estimated does not correspond to the via point (S1033: NO), the process proceeds to step S1035.
- step S1033 the place and time extracted in step S1032 are compared with the place and time information of the situation propagation information 1083, and the situation applies before and after the place and time of the estimation target determined in step S1031. It is searched whether the record of the propagation information 1083 exists. For example, in a route that can move in order of points A, B, and C, if point B is the estimation target and the situation propagation information 1083 stores records related to points A and C, the determination result in step S1033 is "YES". It is.
- step S1033 If it is determined in step S1033 that the estimation target is a via point of status propagation, link status information 1081 or area status information 1082 of the location is created without violating the flow of the status propagation information 1083 before and after (S1034).
- not violating the flow means, for example, 100 routes from point A to point C in the case where point B is an estimation target in a route that can move in order with points A, B and C described above. If there are 50 people who come from the direction of point A, the calculation is performed such that there are 50 or more and 100 or less people at point B going from point A to point C. In the actual calculation, it is necessary to consider the distance from the point A to the point B, the distance from the point B to the point C, the branch of the passage in the middle, and the like. When there are a plurality of patterns of the situation propagation information 1083 before and after the situation, the situation information is estimated so as not to violate the flow for all the patterns.
- step S1033 if it is determined in step S1033 that the estimation target is not a via point of status propagation, the sensor non-installation location status information creation unit 103 can not find a significant relationship with the status information of surrounding locations. It is determined that there is no change in status, and link status information 1081 or area status information 1082 is created.
- the sensor non-installed location status information creation unit 103 may set the speed average so that free walking is possible as “no congestion”, and if there is a past performance statistic, the location based on that statistic You may set the information regarding the general condition of the said time.
- the sensor presence / absence 10819 of the link status information 1081 created by the sensor non-installed location status information creating unit 103 and the sensor presence / absence 10829 of the area status information 1082 are records created by the sensor non-installed location status information creating unit 103 Stores a name or identification code that can identify something.
- the record created by the sensor non-installation location status information creation unit 103 may have less information that can be estimated than the sensor installation location status information creation unit 101, and in this case, “no value” is set. This is the end of the processing of the sensor non-installation location status information creation unit 103.
- FIG. 18 shows an example of the screens 171 and 175 provided to the user terminal 112 by the facility status grasping system 1.
- the user terminal 112 here is, for example, a smartphone possessed by a user (end user) who uses traffic such as a station.
- the screens 171 and 175 are provided to different users.
- the screens 171 and 175 include user name display areas 172 and 176, route summary display areas 173 and 177, and facility map areas 174 and 178, respectively.
- locations with high moving loads are displayed as rectangles on the maps displayed in the facility map areas 174 and 178, and are distinguished by appearance such as color according to the value of moving loads. Do.
- each moving route candidate is displayed as a chevron arrow, divided into each link or area (or a plurality of links, a group obtained by putting together areas), and Depending on the appearance of the color etc. to distinguish and display.
- Each user transmits route information 11211 and attribute information 11212 to the facility status grasping system 1 as a user request 1121.
- the route candidate is a function module provided in the user terminal 112, a function module in the facility status grasping system 1, or a function module possessed by another device provided between the user terminal 112 and the facility status grasping system 1. Can be detected.
- the movement load information creation unit 104 calculates the movement load based on the attribute information 11212 of each user in each of the route candidates. For example, when one user using the screen 171 is a general commuter and the other user using the screen 175 is a wheelchair user, different moving load values are calculated. Therefore, the movable route is different between the route summary display areas 173 and 174 of one user and the route summary display areas 177 and 178 of the other user, or the coloring range of the place with high moving load is different. Or the value of the required time is different.
- the recommended route to each user is also displayed.
- the route with the lowest moving load can be proposed to the user as a recommended route by calculating and comparing the moving loads of the route candidates.
- the traffic user can easily recognize the nature (e.g. easiness of movement, facilities on the way etc.) of the respective route candidates by checking the screens 171 and 175 shown in FIG. Easy-to-use locations and routes can be easily selected, improving usability.
- FIG. 19 shows screens 181 and 185 provided from the facility status grasping system 1 to the user terminal 112.
- the user terminal 112 here is, for example, a personal computer operated by a station clerk or a commander (traffic carrier) in business.
- Screens 181 and 185 include facility map areas 184 and 188, respectively.
- the configuration of the facility map area 184, 188 is the same as that of the facility map area 174, 178 illustrated in FIG. 18, and displays a place with high moving load as a rectangle, and distinguishes according to appearance such as color according to the moving load value. Display.
- alert comments 185 and 189 are output to call station staff and the like with regard to the movement of the user.
- the alert comments 185 and 189 are also displayed in each mode.
- the mobile load By defining the mobile load, it is possible to present specific business content. Therefore, for example, if there are places with high load for commuters, comment out to guide the commuters, and if there are places with high load for wheelchair users, comment to help wheelchair users. You can put it out.
- the station clerk or the commander can recognize the movement risk level of the end user at each place by checking the screens 181 and 185 shown in FIG.
- the facility status grasping system 1 can deliver the information over the entire facility to the traffic users and the traffic operators, and the usability of the traffic users and the traffic operators is improved. Do.
- the present invention is not limited to the above embodiments, but includes various modifications.
- the above embodiments are described in detail in order to explain the present invention in an easy-to-understand manner, and are not necessarily limited to those having all the configurations described.
- Each of the configurations, functions, processing units, processing means, etc. described above may be realized by hardware, for example, by designing part or all of them with an integrated circuit.
- Each of the above configurations, functions, processing units, processing means, and the like may be realized in a cloud system by designing part or all of them, for example, with virtual machines.
- Each configuration, function, and the like described above may be realized by software by a processor interpreting and executing a program that realizes each function.
- Information such as a program, a table, and a file for realizing each function can be placed in a memory, a recording device such as a hard disk or SSD, or a recording medium such as an IC card, an SD card, or a DVD.
- control lines and the information lines indicate what is considered necessary for the description, and not all the control lines and the information lines in the product are necessarily shown. In practice, almost all configurations may be considered to be mutually connected.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Tourism & Hospitality (AREA)
- Radar, Positioning & Navigation (AREA)
- Remote Sensing (AREA)
- General Health & Medical Sciences (AREA)
- Health & Medical Sciences (AREA)
- Economics (AREA)
- Human Resources & Organizations (AREA)
- Marketing (AREA)
- Primary Health Care (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Automation & Control Theory (AREA)
- Traffic Control Systems (AREA)
- Navigation (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| JP2017168842A JP6842389B2 (ja) | 2017-09-01 | 2017-09-01 | 施設状況把握システムおよび方法 |
| JP2017-168842 | 2017-09-01 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2019044455A1 true WO2019044455A1 (ja) | 2019-03-07 |
Family
ID=65525593
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/JP2018/030024 Ceased WO2019044455A1 (ja) | 2017-09-01 | 2018-08-10 | 施設状況把握システムおよび方法 |
Country Status (2)
| Country | Link |
|---|---|
| JP (1) | JP6842389B2 (enExample) |
| WO (1) | WO2019044455A1 (enExample) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023209823A1 (ja) * | 2022-04-26 | 2023-11-02 | 三菱電機ビルソリューションズ株式会社 | 経路探索システムおよび経路探索方法 |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2021071747A (ja) | 2019-10-29 | 2021-05-06 | 日本電気株式会社 | 情報処理システム、情報処理方法及びプログラム |
| JP7609566B2 (ja) * | 2020-04-20 | 2025-01-07 | 株式会社ゼンリン | コンピュータシステム |
| JP7573984B2 (ja) * | 2020-04-20 | 2024-10-28 | 株式会社ゼンリン | コンピュータシステムおよびプログラム |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2006078294A (ja) * | 2004-09-08 | 2006-03-23 | Aisin Aw Co Ltd | ナビゲーション装置 |
| JP2006275922A (ja) * | 2005-03-30 | 2006-10-12 | Hitachi Ltd | ナビゲーションシステムおよび地図管理サーバ |
| JP2007243342A (ja) * | 2006-03-06 | 2007-09-20 | Yokogawa Electric Corp | 画像監視装置及び画像監視システム |
| JP2013073300A (ja) * | 2011-09-27 | 2013-04-22 | Dainippon Printing Co Ltd | 緊急避難誘導システム、緊急避難誘導方法、避難誘導装置、及びプログラム |
| JP2013116676A (ja) * | 2011-12-02 | 2013-06-13 | Hitachi Ltd | 人流予測装置および方法 |
| JP2014190725A (ja) * | 2013-03-26 | 2014-10-06 | Zenrin Datacom Co Ltd | 経路案内システム、経路案内方法、および、コンピュータプログラム |
| JP2015014919A (ja) * | 2013-07-05 | 2015-01-22 | 綜合警備保障株式会社 | 経路生成装置および経路生成方法 |
| US20150178642A1 (en) * | 2013-12-20 | 2015-06-25 | Amadeus S.A.S. | Dynamic travel planner |
| JP2016085014A (ja) * | 2014-10-29 | 2016-05-19 | 株式会社日立製作所 | 空調制御方法及びシステム |
| WO2016194206A1 (ja) * | 2015-06-04 | 2016-12-08 | 三菱電機株式会社 | 移動支援装置、移動支援用サーバおよび移動支援システム |
-
2017
- 2017-09-01 JP JP2017168842A patent/JP6842389B2/ja active Active
-
2018
- 2018-08-10 WO PCT/JP2018/030024 patent/WO2019044455A1/ja not_active Ceased
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2006078294A (ja) * | 2004-09-08 | 2006-03-23 | Aisin Aw Co Ltd | ナビゲーション装置 |
| JP2006275922A (ja) * | 2005-03-30 | 2006-10-12 | Hitachi Ltd | ナビゲーションシステムおよび地図管理サーバ |
| JP2007243342A (ja) * | 2006-03-06 | 2007-09-20 | Yokogawa Electric Corp | 画像監視装置及び画像監視システム |
| JP2013073300A (ja) * | 2011-09-27 | 2013-04-22 | Dainippon Printing Co Ltd | 緊急避難誘導システム、緊急避難誘導方法、避難誘導装置、及びプログラム |
| JP2013116676A (ja) * | 2011-12-02 | 2013-06-13 | Hitachi Ltd | 人流予測装置および方法 |
| JP2014190725A (ja) * | 2013-03-26 | 2014-10-06 | Zenrin Datacom Co Ltd | 経路案内システム、経路案内方法、および、コンピュータプログラム |
| JP2015014919A (ja) * | 2013-07-05 | 2015-01-22 | 綜合警備保障株式会社 | 経路生成装置および経路生成方法 |
| US20150178642A1 (en) * | 2013-12-20 | 2015-06-25 | Amadeus S.A.S. | Dynamic travel planner |
| JP2016085014A (ja) * | 2014-10-29 | 2016-05-19 | 株式会社日立製作所 | 空調制御方法及びシステム |
| WO2016194206A1 (ja) * | 2015-06-04 | 2016-12-08 | 三菱電機株式会社 | 移動支援装置、移動支援用サーバおよび移動支援システム |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023209823A1 (ja) * | 2022-04-26 | 2023-11-02 | 三菱電機ビルソリューションズ株式会社 | 経路探索システムおよび経路探索方法 |
| JP7570563B2 (ja) | 2022-04-26 | 2024-10-21 | 三菱電機ビルソリューションズ株式会社 | 経路探索システムおよび経路探索方法 |
| CN119072728A (zh) * | 2022-04-26 | 2024-12-03 | 三菱电机楼宇解决方案株式会社 | 路径搜索系统和路径搜索方法 |
Also Published As
| Publication number | Publication date |
|---|---|
| JP2019046174A (ja) | 2019-03-22 |
| JP6842389B2 (ja) | 2021-03-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9003030B2 (en) | Detecting relative crowd density via client devices | |
| JP6752435B2 (ja) | 交通システム、ダイヤ提案システム及び列車運行システム | |
| WO2019044455A1 (ja) | 施設状況把握システムおよび方法 | |
| US10904704B2 (en) | System and method for managing a mass gathering | |
| JP5902607B2 (ja) | 旅行時間情報提供装置、旅行時間情報提供方法 | |
| JP6454222B2 (ja) | データ処理システム、及び、データ処理方法 | |
| JP2019177760A (ja) | 輸送機関混雑予測システム及び混雑予測方法 | |
| JP6177715B2 (ja) | 駅混雑予測装置及び駅混雑情報提供システム | |
| JP4504825B2 (ja) | 災害時誘導システム、災害時誘導方法およびプログラム | |
| JP6859364B2 (ja) | 未搭乗者捜索装置、未搭乗者捜索方法、及びプログラム | |
| WO2013171780A1 (ja) | 交通経路分担率制御システム及び交通経路分担率制御方法 | |
| US8519850B2 (en) | Method and system for the acquisition, transmission and assessment of remote sensor data for trend analysis, prediction and remediation | |
| CN103065196A (zh) | 利用建筑物信息模型及毗邻信息的最优高效的警卫巡视配置方法 | |
| JP2017091008A (ja) | データ処理方法およびデータ処理システム | |
| JPWO2017169068A1 (ja) | 列車降車人数予測システム、混雑可視化・評価システム、および乗車可能人数算出システム | |
| JP6326177B2 (ja) | 交通状況推定システム及び交通状況推定方法 | |
| JP7264180B2 (ja) | 特典発行装置、方法、及びプログラム | |
| JP6757654B2 (ja) | 輸送サービス情報提供装置、及び輸送サービス情報提供方法 | |
| KR101172986B1 (ko) | 전시회의 부스 추천 방법 | |
| JP2018103924A (ja) | 混雑予測装置 | |
| Cimellaro et al. | Seismic performance of health care facilities using discrete event simulation models | |
| JP2019003338A (ja) | 予約管理プログラム、予約管理方法、及び予約管理装置 | |
| WO2016123661A1 (en) | Devices, frameworks and methodologies configured to enable automated monitoring and analysis of dwell time | |
| Anastasiou et al. | Deriving generalised stochastic Petri net performance models from high-precision location tracking data | |
| KR20200073952A (ko) | 건물 대피 관리 시스템 및 방법 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 18850544 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 18850544 Country of ref document: EP Kind code of ref document: A1 |