Meeting data creation method, meeting data creation program, meeting data creation system, and mobile terminal program

The face-to-face data creation method using mobile terminals and synchrony indices addresses the limitations of existing technologies by analyzing both positive and negative correlations in face-to-face interactions, enhancing organizational behavior analysis.

JP7592042B2Active Publication Date: 2024-11-29HITACHI LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
JP2022064550
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2022-04-08
Publication Date
2024-11-29
Estimated Expiration
2042-04-08

AI Technical Summary

Technical Problem

Existing technologies are limited in analyzing face-to-face meetings and conversations, only suitable for positive or negative correlations, failing to capture both simultaneously.

Method used

A face-to-face data creation method using mobile terminals with sensors and wireless communication to detect and analyze face-to-face interactions, incorporating synchrony and synchronicity indices to evaluate the degree of influence and synchronization between individuals.

Benefits of technology

Enables the analysis of both positive and negative correlations in face-to-face interactions, providing a comprehensive understanding of organizational behaviors.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007592042000002
    Figure 0007592042000002
  • Figure 0007592042000003
    Figure 0007592042000003
  • Figure 0007592042000004
    Figure 0007592042000004
Patent Text Reader

Abstract

To provide a meeting data creation method that can perform analysis of actions such as meetings and conversations simultaneously having both positive correlation and negative correlation when analyzing relevance of actions of individuals within an organization.SOLUTION: In a meeting data creation method, meeting detection data indicating that a possibility that an individual has met another individual is detected, is created from wireless communication detection data indicating that a mobile terminal carried by the individual has received identification information of another mobile terminal carried by the other individual via wireless communication and code image detection data indicating that the mobile terminal has detected a code image of the identification information of the other mobile terminal. Then, meeting data indicating that the individual has met the other individual is created based on an evaluation result of the meeting detection data using a synchrony index that evaluates synchrony representing a degree of influence that a movement of the individual has on a movement of the other individual and a tuning property index that evaluates a tuning property indicating a degree of tuning between body movement frequencies of the individual and the other individual.SELECTED DRAWING: Figure 11
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a meeting data creation method, a meeting data creation program, and a meeting data creation system. [Background technology]

[0002] Conventionally, the correlation between the actions of individuals in an organization has been analyzed for the purpose of improving the efficiency of organizational activities, revitalizing the organization, evaluating the results, etc. For example, Patent Document 1 discloses a technology for analyzing the correlation between the actions of individuals in a group based on sensor data collected from sensors attached to individuals. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2018-81406 A Summary of the Invention [Problem to be solved by the invention]

[0004] In recent years, there has been a strong need to acquire data on face-to-face meetings and conversations to improve the efficiency and revitalization of organizational activities. However, the above-mentioned conventional technology is limited to analyzing the association between actions having positive correlation or negative correlation, and is not suitable for analyzing the association between actions such as face-to-face meetings and conversations that have both positive and negative correlations at the same time.

[0005] The present invention has been made in consideration of the above, and aims to provide a meeting data creation method that is capable of analyzing behaviors that have both positive correlations and negative correlations at the same time, such as meeting and conversation, when analyzing the relevance of individual behavior within an organization. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems, one aspect of the present invention is a meeting data creation method in which a computer including a processor and a memory creates meeting data for analyzing meetings between a plurality of individuals within an organization, the method including a data acquisition step in which the computer acquires at least one of wireless communication detection data indicating that a portable terminal carried by the individual has received identification information of another portable terminal carried by the other individual via wireless communication and code image detection data indicating that a code image of the identification information of the other portable terminal has been detected by the portable terminal, and acceleration data detected by the portable terminal; The method is characterized in that it has a face-to-face detection data creation step of creating face-to-face detection data indicating that the possibility of the individual having come face-to-face with another individual has been detected based on the obtained data, and a face-to-face data creation step of creating face-to-face data indicating that the individual has come face-to-face with another individual from the face-to-face detection data based on an evaluation result of the face-to-face detection data using an evaluation index including at least one of a synchrony index that evaluates synchrony indicating the degree of influence of the movement of the individual on the movement of the other individual based on the acceleration data, and a synchrony index that evaluates synchrony indicating the degree of synchronization of the body movement frequencies of the individual and the other individual based on the acceleration data. Effect of the Invention

[0007] According to the present invention, when analyzing the relevance of the behavior of individuals within an organization, it is possible to analyze behaviors that simultaneously have both positive correlations and negative correlations, such as face-to-face meetings and conversations. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram showing the configuration of a meeting data creation system according to an embodiment. [Diagram 2] FIG. 4 is a diagram showing an example of an acceleration detection data log according to the embodiment. [Diagram 3] 5 is a diagram showing a short-range wireless communication detection data log according to the embodiment. FIG. [Figure 4]FIG. 4 is a diagram showing a code image detection data log according to the embodiment. [Diagram 5] FIG. 11 is a diagram showing meeting detection data according to the embodiment. [Figure 6] FIG. 4 is a diagram showing meeting data according to the embodiment. [Figure 7] FIG. 4 is a diagram showing a setting file according to the embodiment. [Figure 8] 5 is a flowchart showing an acceleration detection data recording process according to the embodiment. [Figure 9] 6 is a flowchart showing a short-range wireless communication detection process according to the embodiment. [Figure 10] 5 is a flowchart showing a code image detection process according to the embodiment. [Figure 11] 11 is a flowchart showing a meeting data creation process according to the embodiment. [Figure 12] 10 is a flowchart showing details of a synchronicity check process according to the embodiment. [Figure 13] FIG. 13 is a diagram showing the amount of METs for each terminal ID. [Figure 14] 10 is a flowchart showing details of a synchronism check process according to the embodiment. [Figure 15] 13A and 13B are diagrams showing screens for inputting setting values ​​and displaying meeting data according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. The embodiment, including the drawings, is an example for explaining the present invention, and appropriate omissions and simplifications are made for clarity of explanation. The present invention can be implemented in various other forms. Unless otherwise specified, each component may be singular or plural.

[0010] In the embodiment, a program may be described as an entity that executes a process. A computer such as a server or a client executes a program using a processor (e.g., a central processing unit (CPU), a graphics processing unit (GPU)), and performs a process defined by the program using a storage resource (e.g., a memory) and an interface device (e.g., a communication port). Therefore, the entity that executes a program and performs the process may be a processor. Similarly, the entity that executes a program and performs the process may be a controller, device, system, computer, or node having a processor. The entity that executes a program and performs the process may be a calculation unit, and may include a dedicated circuit that performs a specific process. Here, the dedicated circuit is, for example, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a complex programmable logic device (CPLD), a quantum computer, or the like.

[0011] The program may be installed in the computer from a program source. The program source may be, for example, a program distribution server or a computer-readable storage medium. When the program source is a program distribution server, the program distribution server may include a processor and a storage resource that stores the program to be distributed, and the processor of the program distribution server may distribute the program to be distributed to other computers. Also, in an embodiment, two or more programs may be realized as one program, or one program may be realized as two or more programs. The "YYY program" executed by the processor may be expressed as a "YYY unit."

[0012] (Configuration of the face-to-face data creation system S) FIG. 1 is a diagram showing the configuration of a meeting data creation system S according to an embodiment.

[0013] The meeting data creation system S includes a plurality of mobile terminals 1, an external storage 2, and a server (meeting data creation server) 3. The plurality of mobile terminals 1, the external storage 2, and the server 3 are communicatively connected via a network N. The network N may be a public network or a closed network, and may be a wireless communication network or a wired communication network.

[0014] The mobile terminal 1 is a general-purpose computer having a wireless communication function, such as a smartphone having a mobile wireless communication function or a wireless LAN (Local Area Network) communication function and a short-range wireless communication function. In this embodiment, the short-range wireless communication is Bluetooth Low Energy (registered trademark), but other wireless communication standards may be used. The multiple mobile terminals 1 are carried by multiple subjects (individuals) in an organization for which meeting data according to this embodiment is to be created. Each mobile terminal 1 is assigned a terminal ID. The terminal ID is in the format of a predetermined prefix + terminal identification number, thereby preventing radio wave reception from short-range wireless devices of the same standard that are unrelated to the meeting data creation system S.

[0015] A code image (e.g., a two-dimensional code image) that visualizes the assigned terminal ID is attached to the mobile terminal 1. The code image may be attached not only to the mobile terminal 1 but also to one or more locations on the body of the subject carrying the mobile terminal 1. When the code image is attached to multiple locations on the subject's body, the size of the code image may be different depending on the attachment location. The code image may be attached not only to the body of the subject but also to a predetermined location in the space in which the subject moves. Alternatively, the code image may be displayed on the screen of the mobile terminal 1. The mobile terminal 1 and the code image are attached to each subject so that the imaging unit of the mobile terminal 1 can capture the code images of the subject and the other subjects when the subject and the other subjects are in a positional relationship and posture that are considered to be face-to-face. "Face-to-face" refers to, for example, a case in which the subject receives the terminal ID of the other subject's mobile terminal 1 with a certain or higher reception radio wave intensity by short-distance wireless communication using the subject's own mobile terminal 1 and detects the terminal ID code image of the other subject's mobile terminal 1 with the camera of the subject's own mobile terminal 1, but is not limited to this.

[0016] The mobile terminal 1 includes a storage unit 11, a processor 12, a memory 13, an acceleration sensor 14, a short-range wireless communication unit 15, a camera 16, and a network communication unit 17. The storage unit 11 is a storage device such as a storage. The processor 12 is a microprocessor such as a CPU, and executes various programs in cooperation with the memory 13, which is a main storage device. The acceleration sensor 14 is a six-axis acceleration sensor that can acquire acceleration data and geomagnetic data, but may be a three-axis acceleration sensor that can acquire only acceleration data. The short-range wireless communication unit 15 is a communication module for performing short-range wireless communication to transmit and receive a terminal ID to and from another mobile terminal 1. The camera 16 is an example of an imaging unit, and may be any sensor that captures an image. The network communication unit 17 is a communication module for performing mobile wireless communication or wireless LAN communication.

[0017] The storage unit 11 stores an acceleration detection program 111, a short-range wireless communication detection program 112, and a code image detection program 113. The acceleration detection program 111, the short-range wireless communication detection program 112, and the code image detection program 113 are executed by the processor 12 to perform an acceleration data detection process (FIG. 8), a short-range wireless communication detection process (FIG. 9), and a code image detection process (FIG. 10), respectively.

[0018] The storage unit 11 also stores a short-range wireless communication device ID list 1L2 and a code image list 1L3. The short-range wireless communication device ID list 1L2 is a list in which terminal IDs of the portable terminals 1 carried by the subjects of the organization for which the meeting data 3D2 according to this embodiment is to be created are preregistered. The code image list 1L3 is a list of code images of the terminal IDs preregistered in the short-range wireless communication device ID list 1L2.

[0019] The storage unit 11 also stores an acceleration detection data log 1D1, a short-range wireless communication detection data log 1D2, and a code image detection data log 1D3.

[0020] (Acceleration detection data log 1D1) 2 is a diagram showing an example of an acceleration detection data log 1D1 according to an embodiment. The acceleration detection data log 1D1 is a log of acceleration data and geomagnetic data acquired from the acceleration sensor 14 in, for example, 50 milliseconds by the acceleration detection program 111 for each mobile terminal 1. The acceleration data and geomagnetic data are acquired in association with the movement of a subject carrying the mobile terminal 1. The acceleration detection data log 1D1 is a time-series log in, for example, a CSV (Comma Separated Value) format.

[0021] As shown in FIG. 2, the acceleration detection data log 1D1 has columns of "date", "time", "AccX axis (X-axis acceleration)", "AccY axis (Y-axis acceleration)", "AccZ axis (Z-axis acceleration)", "MagX axis (X-axis geomagnetism)", "MagY axis (Y-axis geomagnetism)", and "MagZ axis (Z-axis geomagnetism)". "AccX axis (X-axis acceleration)", "AccY axis (Y-axis acceleration)", and "AccZ axis (Z-axis acceleration)" are three-axis acceleration data. "MagX axis (X-axis geomagnetism)", "MagY axis (Y-axis geomagnetism)", and "MagZ axis (Z-axis geomagnetism)" are three-axis geomagnetic data. Note that, when the acceleration sensor 14 is a three-axis acceleration sensor, "MagX axis (X-axis geomagnetism)", "MagY axis (Y-axis geomagnetism)", and "MagZ axis (Z-axis geomagnetism)" store 0.

[0022] The network communication unit 17 performs daily processing to transmit, for example, a daily acceleration detection data log 1D1 to the external storage 2. The daily acceleration detection data log 1D1 transmitted to the external storage 2 is stored in an acceleration detection data file 2D1 for each terminal ID of the mobile terminal 1.

[0023] (Short-distance wireless communication detection data log 1D2) 3 is a diagram showing a short-range wireless communication detection data log 1D2 according to an embodiment. The short-range wireless communication detection data log 1D2 is a log of short-range wireless communication detection data indicating that the terminal IDs of other portable terminals 1 are received, for example, at 5-second intervals, via the short-range wireless communication unit 15 by the short-range wireless communication detection program 112 for each portable terminal 1. The terminal IDs of other portable terminals 1 are received as the subject carrying the portable terminal 1 moves. The short-range wireless communication detection data log 1D2 is, for example, a chronological log in a CSV format. The short-range wireless communication detection program 112 screens only the terminal IDs preregistered in the short-range wireless communication device ID list 1L2 and stores them in the short-range wireless communication detection data log 1D2.

[0024] The short-range wireless communication detection data log 1D2 has columns of "date," "time," and "short-range wireless communication detection ID and radio wave strength," as shown in Fig. 3. In the column of each ID in the row of each date and time, the radio wave strength is stored if the corresponding terminal ID is detected by short-range wireless communication, and 0 is stored if the corresponding terminal ID is not detected. Note that, for ease of explanation, the radio wave strength of short-range wireless communication is represented as a positive value in Fig. 3.

[0025] The network communication unit 17 performs daily processing to transmit, for example, a short-range wireless communication detection data log 1D2 on a daily basis to the external storage 2. The short-range wireless communication detection data log 1D2 on a daily basis transmitted to the external storage 2 is stored in a short-range wireless communication detection data file 2D2 for each terminal ID of the mobile terminal 1.

[0026] (Code image detection data log 1D3) 4 is a diagram showing a code image detection data log 1D3 according to the embodiment. The code image detection data log 1D3 is a log of code image detection data indicating that the code image of another portable terminal 1 is detected by the code image detection program 113 via the camera 16 at intervals of, for example, one second for each portable terminal 1. The code image of the other portable terminal 1 is detected as the subject carrying the portable terminal 1 moves. The code image detection data log 1D3 is a time-series log in, for example, a CSV format.

[0027] The code image detection program 113 can detect multiple code images at the same time, but combines identical code images detected at the same time into one. The code image detection program 113 can also adjust the frequency of capturing code images by the camera 16. The code image detection program 113 screens only the code images of terminal IDs preregistered in the code image list IL3 and stores them in the code image detection data log 1D3.

[0028] The code image detection data log 1D3 has columns of "date," "time," and "code image detection ID," as shown in Fig. 4. In the column of each ID in the row of each date and time, "1 (flag)" is stored if the camera 16 detects a code image of the corresponding terminal ID, and 0 is stored if the camera 16 does not detect a code image of the corresponding terminal ID.

[0029] The network communication unit performs daily processing, for example, to transmit the code image detection data log 1D3 on a daily basis to the external storage 2. The code image detection data log 1D3 on a daily basis transmitted to the external storage 2 is stored in a code image detection data file 2D3 for each terminal ID of the mobile terminal 1.

[0030] The unit of data amount and processing period for transmitting the acceleration detection data log 1D1, the short-range wireless communication detection data log 1D2, and the code image detection data log 1D3 to the external storage 2 are not limited to daily units and daily intervals, and may be other time units and processing periods. Alternatively, transmission may be in real time.

[0031] (External storage 2) The external storage 2 is a storage that can be accessed by a plurality of mobile terminals 1 registered in the meeting data creation system S via a mobile wireless communication function or wireless LAN communication. The external storage 2 may be either an online storage or an on-premise storage. The external storage 2 stores an acceleration detection data file 2D1, a short-range wireless communication detection data file 2D2, and a code image detection data file 2D3 for each terminal ID of the mobile terminal 1. The formats of the acceleration detection data file 2D1, the short-range wireless communication detection data file 2D2, and the code image detection data file 2D3 are the same as those of the acceleration detection data log 1D1 (FIG. 2), the short-range wireless communication detection data log 1D2 (FIG. 3), and the code image detection data log 1D3 (FIG. 4).

[0032] (Server 3 configuration) The server 3 includes a storage unit 31, a processor 32, a memory 33, a coprocessor 34, a communication unit 35, and a display unit 36. The storage unit 31 is a storage device such as a storage. The processor 32 is a microprocessor such as a CPU, and executes various programs in cooperation with the memory 33, which is a main storage device, and the coprocessor 34. The coprocessor 34 is a processor for specific processing such as an arithmetic processor, and executes arithmetic processing under the control of the processor 32. The communication unit 35 is an interface for the server 3 to communicate with the mobile terminal 1 and the external storage 2 via the network N. The display unit 36 ​​is an output device equipped with a display screen that displays information. The display unit 36 ​​may be an external device connected to the server 3.

[0033] The storage unit 31 stores a meeting data creation program 311, a synchronicity check program 312, a synchronization check program 313, and a body orientation (body direction) estimation program 314. The storage unit 31 also stores meeting detection data 3D1 and meeting data 3D2. The storage unit 31 also holds a setting file 3C.

[0034] The meeting data creation program 311, the synchrony check program 312, the synchronization check program 313, and the body orientation estimation program 314 are executed by the processor 32 to respectively perform a meeting data creation process (FIG. 11), a synchrony check process (FIG. 12), a synchronization check process (FIG. 14), and a body orientation estimation process of the meeting data creation process (step S107 in FIG. 11).

[0035] (Face-to-face detection data 3D1) FIG. 5 is a diagram showing meeting detection data 3D1 according to an embodiment. The meeting detection data 3D1 is data indicating that the possibility that the subject carrying the mobile terminal 1 has met another subject has been detected. As shown in FIG. 5, the meeting detection data 3D1 includes columns of "Terminal ID", "Date", "Time", "ID1", "ID2", etc. The meeting detection data 3D1 is managed for each terminal ID shown in "Terminal ID". "ID1", "ID2", etc. are terminal IDs of the mobile terminal 1 registered in the meeting data creation system S. Radio wave intensity is stored in the column of each ID in the row of each date and time of the meeting detection data 3D1. This radio wave intensity is a radio wave intensity equal to or greater than a threshold stored in the column of the short-range wireless communication detection data file 2D2 (FIG. 3) of the same date and time and terminal ID as the column in which "1" is stored in the code image detection data file 2D3 (FIG. 4).

[0036] For example, in the code image detection data file 2D3 (FIG. 4), the ID4 and ID5 columns in the row with the "Date" set to "2021-09-29" and the "Time" set to "08:30:05" are both set to "1". On the other hand, the radio wave intensity "178" in the ID4 column in the row with the "Date" set to "2021-09-29" and the "Time" set to "08:30:05" in the short-range wireless communication detection data file 2D2 (FIG. 3) is greater than or equal to the threshold value Th1 (see FIG. 7, e.g., 100). Therefore, the radio wave intensity "178" is stored in the corresponding column of the face-to-face detection data 3D1. The radio wave intensity "33" in the ID5 column in the row with the "Date" set to "2021-09-29" and the "Time" set to "08:30:05" in the short-range wireless communication detection data file 2D2 (FIG. 3) is less than the threshold value Th1. Therefore, the radio wave strength "33" is not stored in the corresponding field of the meeting detection data 3D1, but rather 0 is stored.

[0037] (Face-to-face data 3D2) FIG. 6 is a diagram showing meeting data 3D2 according to an embodiment. The meeting data 3D2 is data indicating that a subject carrying a mobile terminal 1 has met another subject, and is data for analyzing meetings between multiple subjects in an organization. As shown in FIG. 6, the meeting data 3D2 includes columns of "Terminal ID", "Date", "Time", "Body movement frequency", "Body orientation", "Number of people meeting", "ID1", "ID2", and so on. The meeting data 3D2 is managed for each terminal ID shown in "Terminal ID". The meeting data 3D2 is information obtained by extracting rows corresponding to at least one of "with synchrony" and "with synchrony" from the meeting detection data 3D1 (FIG. 5), and calculating and adding "Body movement frequency", "Body orientation", and "Number of people meeting". "Presence or absence of synchrony" is determined by a synchrony check process (FIG. 12). "Presence or absence of synchrony" is determined by a synchrony check process (FIG. 14).

[0038] (Configuration file 3C) Fig. 7 is a diagram showing a setting file 3C according to an embodiment. The setting file 3C stores various parameters that define the operation when the server 3 executes the meeting data creation process (Fig. 11). The server 3 reads the setting file 3C when the meeting data creation program 311 is started. The setting file 3C includes the items "Use / Not Use of Near Field Communication", "Near Field Communication Radio Wave Intensity Threshold Th1", "Use / Not Use of Code Image", "Check / Not Check Synchronicity", "Synchrony Threshold Th2", "Check / Not Check Synchronicity", "Synchrony Threshold Th3", and "Both / One of Synchronicity and Synchronicity".

[0039] "Short-distance wireless communication use / not use" sets whether or not to use the short-distance wireless communication detection data file 2D2 when the server 3 executes the meeting detection data creation process (step S103 in FIG. 11). "Short-distance wireless communication radio wave intensity threshold Th1" is a threshold used when the server 3 executes the meeting detection data creation process to determine whether or not to store the radio wave intensity stored in the short-distance wireless communication detection data file 2D2 in the meeting detection data 3D1.

[0040] "Use / non-use of code image" sets whether or not to use the code image detection data file 2D3 when the server 3 executes the meeting detection data creation process (step S103 in FIG. 11). At least one or both of "Use / non-use of short-distance wireless communication" and "Use / non-use of code image" are set to "Use".

[0041] "Check synchrony / not check synchrony" is a setting value for whether or not to execute the synchrony check process (FIG. 12), and if "check synchrony", the synchrony check process is executed, and if "not check synchrony", the synchrony check process is skipped. "Synchrony threshold Th2" is a threshold for determining the presence or absence of synchrony by the synchrony check process (step S109c in FIG. 12).

[0042] "Check synchrony / not check synchrony" is a setting value for whether or not to execute the synchrony check process (Fig. 14); if "check synchrony", the synchrony check process is executed, and if "do not check synchrony", the synchrony check process is skipped. At least one of "check synchrony / not check synchrony" and "check synchrony / not check synchrony" is set to "check". "Synchrony threshold Th3" is a threshold value used when determining the presence or absence of synchrony by the synchrony check process (step S110e in Fig. 14).

[0043] "Both / either synchrony and synchrony" sets whether to add a value in which both or at least one of synchrony and synchrony are equal to or greater than a threshold value when adding the value of the meeting detection data 3D1 as meeting data to the meeting data 3D2. If "both synchrony and synchrony" is set, a value in which synchrony is equal to or greater than a threshold value Th2 and synchrony is equal to or greater than a threshold value Th3 is added to the meeting data 3D2 as meeting data. If "either synchrony and synchrony" is set, a value in which synchrony is equal to or greater than a threshold value Th2 or synchrony is equal to or greater than a threshold value Th3 is added to the meeting data 3D2 as meeting data.

[0044] (Acceleration detection data recording processing) 8 is a flowchart showing the acceleration detection data recording process according to the embodiment. First, in step S11, the acceleration detection program 111 of the mobile terminal 1 starts the acceleration sensor 14 and performs initial settings such as clearing the internal memory and resetting the timer. Next, in step S12, the acceleration detection program 111 acquires acceleration data from the acceleration sensor 14. Next, in step S13, the acceleration detection program 111 adds / updates the acceleration data acquired in step S12 to the internal memory. Every time step S13 is executed, the acceleration data in the internal memory is overwritten.

[0045] Next, in step S14, the acceleration detection program 111 determines whether t1 milliseconds (for example, 50 milliseconds) have passed since the most recent timer reset. If t1 milliseconds have passed since the most recent timer reset (step S14 YES), the acceleration detection program 111 proceeds to step S15, and if t1 milliseconds have not passed since the most recent timer reset (step S14 NO), the acceleration detection program 111 returns to step S12. t1 can be changed as appropriate.

[0046] In step S15, the acceleration detection program 111 acquires a current time stamp. Next, in step S16, the acceleration detection program 111 assigns the time stamp acquired in step S15 to the acceleration data stored in the internal memory and stores the data in the acceleration detection data log 1D1. Next, in step S17, the acceleration detection program 111 clears the internal memory and resets the timer. Next, in step S18, the acceleration detection program 111 determines whether or not to end the acceleration detection data recording process. If the acceleration detection program 111 wishes to end the acceleration detection data recording process (step S18 YES), it ends the acceleration detection data recording process, and if the acceleration detection data recording process is to be continued (step S18 NO), it returns the process to step S12.

[0047] (Short-distance wireless communication detection processing) 9 is a flowchart showing a short-distance wireless communication detection process according to the embodiment. First, in step S21, the short-distance wireless communication detection program 112 of the mobile terminal 1 starts the short-distance wireless communication unit 15 and performs initial settings such as clearing the internal memory and resetting the timer. Next, in step S22, the short-distance wireless communication detection program 112 receives radio waves of short-distance wireless communication. Next, in step S23, the short-distance wireless communication detection program 112 judges whether or not short-distance wireless communication including reception of a terminal ID has been detected. If the short-distance wireless communication detection program 112 detects short-distance wireless communication including reception of a terminal ID (step S23 YES), the program proceeds to step S24, and if the short-distance wireless communication including reception of a terminal ID has not been detected (step S23 NO), the program proceeds to step S25.

[0048] In step S24, the short-range wireless communication detection program 112 adds or updates the short-range wireless communication detection data determined to have been received in step S23 to the internal memory. Every time step S24 is executed, the short-range wireless communication detection data in the internal memory is overwritten.

[0049] In step S25, the short-range wireless communication detection program 112 judges whether t2 seconds (for example, 1 second) have passed since the last timer reset. If t2 seconds have passed since the last timer reset (step S25 YES), the short-range wireless communication detection program 112 proceeds to step S26, and if t2 seconds have not passed since the last timer reset (step S25 NO), the program returns to step S27. t2 and t3 can be appropriately changed so as to satisfy t2≦t3.

[0050] In step S26, the short-range wireless communication detection program 112 transmits the terminal ID of its own device by short-range wireless communication. Next, in step S27, the short-range wireless communication detection program 112 judges whether t3 seconds (for example, 5 seconds) have passed since the most recent timer reset. If t3 seconds have passed since the most recent timer reset (step S27 YES), the short-range wireless communication detection program 112 proceeds to step S28, and if t3 seconds have not passed since the most recent timer reset (step S27 NO), the program returns to step S32.

[0051] In step S28, the short-range wireless communication detection program 112 judges whether the terminal ID of the short-range wireless communication detection data currently stored in the internal memory has been preregistered in the short-range wireless communication device ID list 1L2 (FIG. 1). If the terminal ID of the short-range wireless communication detection data currently stored in the internal memory has been preregistered (step S28 YES), the short-range wireless communication detection program 112 proceeds to step S29. On the other hand, if the terminal ID of the short-range wireless communication detection data currently stored in the internal memory has not been preregistered (step S28 NO), the short-range wireless communication detection program 112 proceeds to step S32.

[0052] In step S29, the short-range wireless communication detection program 112 acquires a current time stamp. Next, in step S30, the short-range wireless communication detection program 112 assigns the time stamp acquired in step S29 to the short-range wireless communication detection data stored in the internal memory and stores the data in the short-range wireless communication detection data log 1D2. Next, in step S31, the short-range wireless communication detection program 112 clears the internal memory and resets the timer. Next, in step S32, the short-range wireless communication detection program 112 determines whether or not to end the short-range wireless communication detection process. If the short-range wireless communication detection process is to be ended (step S32 YES), the short-range wireless communication detection program 112 ends the short-range wireless communication detection process, and if the short-range wireless communication detection process is to be continued (step S32 NO), the program returns to step S22.

[0053] (Code image detection processing) 10 is a flowchart showing the code image detection process according to the embodiment. First, in step S41, the code image detection program 113 of the mobile terminal 1 starts the camera 16 and performs initial settings such as clearing the internal memory and resetting the timer. Next, in step S42, the code image detection program 113 acquires an image from the camera 16. Next, in step S43, the code image detection program 113 detects a code image from the camera image from the camera 16.

[0054] Next, in step S44, the code image detection program 113 determines whether or not a code image has been detected in step S43. If a code image has been detected in step S43 (YES in step S44), the code image detection program 113 advances the process to step S45.

[0055] In step S45, the code image detection program 113 adds or updates the code image detection data determined to have been detected in step S44 in the internal memory.

[0056] Next, in step S46, the code image detection program 113 judges whether t4 seconds (for example, 1 second) have passed since the last timer reset. If t4 seconds have passed since the last timer reset (step S46 YES), the code image detection program 113 proceeds to step S47, and if t4 seconds have not passed since the last timer reset (step S46 NO), the code image detection program 113 returns to step S42.

[0057] In step S47, the code image detection program 113 judges whether the code image detection data currently stored in the internal memory has been preregistered in the code image list 1L3 (FIG. 1). If the code image detection data currently stored in the internal memory has been preregistered (step S47 YES), the code image detection program 113 proceeds to step S48. On the other hand, if the code image detection data currently stored in the internal memory has not been preregistered (step S47 NO), the code image detection program 113 proceeds to step S51.

[0058] In step S48, the code image detection program 113 acquires a current time stamp. Next, in step S49, the code image detection program 113 assigns the time stamp acquired in step S48 to the code image detection data stored in the internal memory and stores the data in the code image detection data log 1D3. Next, in step S50, the code image detection program 113 clears the internal memory and resets the timer. Next, in step S51, the code image detection program 113 determines whether or not to end the code image detection process. If the code image detection process is to be ended (step S51 YES), the code image detection program 113 ends the code image detection process, and if the code image detection process is to be continued (step S51 NO), the code image detection program 113 returns the process to step S42.

[0059] (Face-to-face data creation processing) 11 is a flowchart showing a meeting data creation process according to the embodiment. First, in step S101, the meeting data creation program 311 of the server 3 acquires the short-range wireless communication detection data file 2D2 from the external storage 2. Next, in step S102, the meeting data creation program 311 acquires the code image detection data file 2D3 from the external storage 2. In steps S101 and S102, the meeting data creation program 311 acquires the short-range wireless communication detection data file 2D2 and the code image detection data file 2D3 having the same timestamp. The processor 32 of the server 3 realizes a data acquisition unit by executing step S101 or S102.

[0060] Next, in step S103, the meeting data creation program 311 determines the time stamp and ID fields corresponding to the condition satisfaction, where "1" (code image detected) is stored in the code image detection data file 2D3 and radio wave intensity equal to or greater than the threshold Th1 is stored in the short-range wireless communication detection data file 2D2. Then, the meeting data creation program 311 creates meeting detection data 3D1 by extracting the radio wave intensity stored in the field corresponding to the condition satisfaction. The processor 32 of the server 3 executes step S103 to realize a meeting detection data creation unit.

[0061] Next, in step S104, the meeting data creation program 311 acquires the acceleration detection data file 2D1 from the external storage 2. In step S104, the meeting data creation program 311 acquires the acceleration detection data file 2D1 having the same timestamp as the short-range wireless communication detection data file 2D2 and the code image detection data file 2D3 acquired in steps S101 and S102.

[0062] Next, in step S105, the meeting data creation program 311 calculates a gravity-removed acceleration by removing the influence of noise such as gravity from the acceleration of the acceleration detection data file 2D1 acquired in step S14.

[0063] Next, in step S106, the meeting data creation program 311 acquires geomagnetic data from the acceleration detection data file 2D1 acquired in step S104. Next, in step S107, the meeting data creation program 311 calls the body orientation estimation program 314 (FIG. 1) and performs a process of estimating the body orientation of the subject from the gravity-removed acceleration calculated in step S105 and the geomagnetic data acquired in step S106. In the body orientation estimation process, the Euler angles indicating the body orientation of the subject are estimated using a rotation matrix based on the gravity-removed acceleration calculated in step S105 and the geomagnetic data.

[0064] Next, in step S108, the meeting data creation program 311 inputs the meeting detection data 3D1 created in step S103.

[0065] Next, in step S109, the meeting data creation program 311 calls the synchronicity check program 312 and performs a synchronicity check process on the values ​​of the columns of the meeting detection data 3D1 for each terminal ID input in step S103. The details of the synchronicity check process will be described later with reference to FIG.

[0066] Next, in step S110, the meeting data creation program 311 calls the synchronization check program 313 and performs a synchronization check process on the values ​​of the columns of each ID in the meeting detection data 3D1 for each terminal ID input in step S103. The details of the synchronization check process will be described later with reference to FIG.

[0067] Next, in step S111, the meeting data creation program 311 creates meeting data 3D2 based on the value of the meeting detection data 3D1 according to the values ​​of meeting data flag A and meeting data flag B, which are set in the synchrony check process in step S109 and the harmony check process in step S110, which will be described later. In step S111, the meeting data creation program 311 stores "body movement frequency," "body orientation," and "number of people meeting" in association with each row of the meeting data 3D2. The meeting data creation program 311 calculates the total number of ID columns in which non-zero values ​​are stored in each row of the meeting data 3D2 as the "number of people meeting."

[0068] Note that the synchronization check process in step S109 and the conformity check process in step S110 are not limited to this, and other evaluation indices may be used to check the correlation between the movements or actions of the subjects in the meeting detection data 3D1.

[0069] (Synchronicity check process) 12 is a flowchart showing details of the synchrony check process (step S109 in FIG. 11) according to the embodiment. In the synchrony check process, the meeting detection data 3D1 is evaluated from the viewpoint of synchrony, which indicates the degree of influence that the movements of the subjects have on each other.

[0070] First, in step S109a, the synchrony check program 312 calculates the amount of METs (Metabolic Equivalents) of the activity of each subject from the time-series gravity-removed acceleration of the subject of each terminal ID output based on the acceleration detection data file 2D1 in step S105. The amount of METs indicates how many times the intensity of the activity is compared to the resting state. The method shown in Patent Document 1 (JP Patent Publication 2018-81406 A) is used to calculate the amount of METs. The amount of METs of each subject calculated in step S109a is data for each terminal ID of the mobile terminal 1 held by each subject, as shown in FIG. 13.

[0071] Next, in step S109b, the synchrony check program 312 calculates the transfer entropy T between all two terminal IDs based on the probability distribution obtained from the time series of the feature amount, using the METs amount for each terminal ID calculated in step S109a as a feature amount. The transfer entropy is also called advection entropy. In this case, the transfer entropy T is a numerical value obtained by assuming that the METs amount of the two terminal IDs are random variables X and Y, respectively, and quantifying the information flow between the two random variables X and Y that occurs during the time lapse from time t to time t+1 as an average information amount. The transfer entropy T between two random variables X and Y includes transfer entropy T (X → Y) in the direction of X → Y that represents the influence of X on Y, and transfer entropy T (Y → X) in the direction of Y → X that represents the influence of Y on X. These two transfer entropies T are called bidirectional transfer entropy. In step S109b, the synchrony check program 312 calculates the bidirectional transfer entropy T between all two terminal IDs. The transfer entropy T is calculated using the method disclosed in Patent Document 1 (JP 2018-81406 A).

[0072] Next, in step S109c, the synchrony check program 312 determines whether the difference in bidirectional transfer entropy T calculated in step S109b is equal to or greater than the synchrony threshold Th2 for all values ​​of the meeting detection data 3D1 that indicate meeting detection (i.e., input radio wave strength). The synchrony check program 312 then sets the meeting data flag A to 1 for values ​​of the meeting detection data 3D1 that satisfy the condition that the difference in bidirectional transfer entropy T is equal to or greater than the threshold Th2. Meeting data flag A = 1 indicates that the value of the meeting detection data 3D1 is a value to be stored in the meeting data 3D2 as meeting data because the synchrony condition is satisfied.

[0073] (Synchronization check process) 14 is a flowchart showing details of the synchrony check process according to the embodiment. In the synchrony check process, the meeting detection data 3D1 is evaluated from the viewpoint of synchrony, which indicates the degree of synchrony of the body movement frequencies between the subjects.

[0074] First, in step S110a, synchrony check program 313 calculates the body movement frequency (zero crossing) for each of all terminal IDs. Triaxial acceleration data acquired from acceleration sensor 14 of portable terminal 1 worn by the subject is converted into uniaxial acceleration values, and the period in which this value, after removing the effects of gravity, crosses the zero axis, is called the zero crossing period. Body movement frequency (zero crossing) is a value calculated based on the zero crossing period as the number of times the acceleration value on one axis increases and decreases within a unit time. Body movement frequency (zero crossing) is a well-known quantity (zero crossing frequency) that represents the state of movement of the subject's body based on the subject's acceleration data.

[0075] Next, in step S110b, synchrony check program 313 calculates the probability distribution of body movement frequencies (zero crossings) of all terminal IDs over the analysis period. Next, in step S110c, synchrony check program 313 calculates the joint probability distribution of body movement frequencies (zero crossings) between every two terminal IDs over the analysis period. Next, in step S110c, synchrony check program 313 uses the calculation results of steps S110b and S110c to calculate a synchrony index S of body movement frequencies (zero crossings) over the analysis period. AB is calculated using formula (1) described below.

[0076] Next, in step S110e, the synchrony check program 313 checks the synchrony index S calculated in step S110d for all values ​​with face-to-face detection stored in the face-to-face detection data 3D1 (i.e., the input radio wave intensity). AB The synchrony check program 313 then determines whether the synchrony index S is equal to or greater than the synchrony threshold Th3 (FIG. 7). AB For values ​​of the meeting detection data 3D1 that satisfy the condition that is equal to or greater than the threshold value Th3, the meeting data flag B is set to 1. The meeting data flag B=1 indicates that the value of the meeting detection data 3D1 is a value to be stored in the meeting data 3D2 as meeting data because the synchronicity condition is satisfied.

[0077] Steps S110b to S110d will be described in detail. In step S110b, the synchrony check program 313 calculates, for example, the frequency distribution D of the body movement frequency (zero crossing) of the subject A (terminal ID=A) over the analysis period. A Calculate the frequency distribution D A By normalizing the sum of these to 1, the probability distribution p of subject A's body movement frequency (zero crossing) over the analysis period is obtained. A Similarly, the synchrony check program 313 calculates the probability distribution p B Calculate.

[0078] In step S110b, synchrony check program 313 sets the ranks of the body movement frequency (zero crossing) of subject A (terminal ID=A) as the rows of the matrix, and sets the ranks of the body movement frequency (zero crossing) of subject B (terminal ID=B) as the columns of the matrix. Then, synchrony check program 313 calculates the joint distribution D in the field where the rows and columns corresponding to the body movement frequencies (zero crossings) of subject A and subject B at each timestamp over the analysis period intersect. AB The synchrony check program 313 adds +1 to the frequency of the joint distribution D AB By normalizing the sum of these to 1, the joint probability distribution p AB Calculate.

[0079] Then, in step S110d, the synchronization index S of all two terminal IDs (terminal ID=A, B) is calculated from the formula (1) using the calculation results of steps S110b to S110c. AB Calculate.

[0080]

number

[0081] Synchrony index S AB is an example of an index for evaluating the degree of synchronization between the body movement frequencies of subject A (terminal ID=A) and subject B (terminal ID=B). Synchrony index S AB is the joint probability distribution p AB This indicates how far apart subject A and subject B are compared to when they are independent. AB The larger the value, the more likely it is that subject A and subject B are synchronized rather than independent.

[0082] In addition, the synchrony index S AB The only case where subject A (terminal ID=A) and subject B (terminal ID=B) are independent is when the synchrony index S ABis defined above as two-dimensional (i.e., synchrony between two people is evaluated), but it can be expanded to three or more dimensions (i.e., the number of people evaluating synchrony is three or more). Any index can be used, not limited to formula (1), as long as it evaluates the degree of synchrony between the body movement frequencies of subject A and subject B.

[0083] (Screen 36D for inputting settings and displaying face-to-face data) FIG. 15 is a diagram showing a screen 36D for inputting setting values ​​and displaying meeting data according to the embodiment.

[0084] The server 3 can display the meeting detection data 3D1 created by the meeting data creation process (FIG. 11) on a screen 36D as shown in FIG. 15. The screen 36D displayed on the display unit 36 ​​includes a meeting data display area 36D1, an editing area 36D2 for the setting file 3C, and a recalculation button 36D3.

[0085] The user changes various setting values ​​in the editing area 36D2 and presses the recalculate button 36D3. In response to this, the meeting data creation program 311 of the server 3 re-executes the meeting data creation process and displays the re-execution result in the display area 36D1. That is, the server 3 accepts the change in the setting value of the setting file 3C, re-executes the meeting data creation process according to the changed setting value, and updates the meeting data 3D2 displayed in the display area 36D1.

[0086] According to this embodiment, acceleration data of the subject, near-field wireless communication detection data indicating the possibility of a meeting with another subject, and code image detection data are collected using a mobile terminal 1 such as a smartphone equipped with an acceleration sensor, a near-field wireless communication function, a camera, and a wireless communication function. The acceleration data, the distance wireless communication detection data, and the code image detection data collected by the mobile terminal are stored in an external online storage. The server 3 creates meeting detection data 3D1 indicating the possibility of a meeting between the subjects from the near-field wireless communication detection data and the code image detection data. The server 3 then evaluates the meeting detection data 3D1 by an evaluation process such as a synchrony check process and a sympathy check process, and creates meeting data 3D2 from the meeting detection data 3D1 when there is a certain correlation such as synchrony and sympathy between the actions of the subjects.

[0087] Therefore, according to this embodiment, it becomes possible to generate meeting data 3D2 for analyzing the relevance of the behavior of individuals in an organization using general-purpose hardware. It also becomes possible to analyze behaviors that have both positive correlations and negative correlations at the same time, such as meeting and conversation.

[0088] In addition, the setting file 3C allows the user to change parameters such as the thresholds used in various evaluation processes, the selection of input files when creating various data, and which indicators (such as synchrony or harmony) the results of the relevance check process are based on to be reflected in the creation of the face-to-face data 3D2.

[0089] Therefore, according to this embodiment, the operation of the meeting data creation system S can be flexibly determined, and when analyzing the relevance of the behavior of individuals in an organization, the analysis can be performed while changing parameters, which diversifies the viewpoints and approaches of the analysis. Therefore, the user may obtain new knowledge through the analysis.

[0090] The present invention is not limited to the above-described embodiments, and includes various modified examples. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and are not necessarily limited to those having all of the configurations described. In addition, it is also possible to replace a part of the configuration of one embodiment with the configuration of another embodiment, and to add the configuration of another embodiment to the configuration of one embodiment, as long as there is no contradiction. In addition, it is possible to add, delete, replace, integrate, or distribute a part of the configuration of each embodiment. In addition, the configurations and processes shown in the embodiments can be appropriately distributed, integrated, or replaced based on processing efficiency or implementation efficiency. [Explanation of symbols]

[0091] 1: Mobile device, 2: External storage, 3: Server

Claims

1. A meeting data creation method in which a computer including a processor and a memory creates meeting data for analyzing meetings between a plurality of individuals in an organization, the method comprising: a data acquisition step in which the computer acquires at least one of wireless communication detection data indicating that a portable terminal carried by the individual has received identification information of another portable terminal carried by the other individual via wireless communication and code image detection data indicating that a code image of the identification information of the other portable terminal has been detected by the portable terminal, and acceleration data detected by the portable terminal; a meeting detection data creation step in which the computer creates meeting detection data indicating that a possibility that the individual has met another individual has been detected based on the data acquired by the data acquisition step; a meeting data creation step in which the computer creates, from the meeting detection data, the meeting data indicating that the individual has met the other individual, based on the meeting detection data, on the basis of an evaluation result of the meeting detection data using an evaluation index including at least one of a synchrony index that evaluates synchrony indicating the degree of influence that the movement of the individual has on the movement of the other individual, based on the acceleration data, and a synchrony index that evaluates synchrony indicating the degree of synchrony between the body movement frequencies of the individual and the other individual, based on the acceleration data; A meeting data creation method comprising the steps of:

2. The meeting data creation method according to claim 1, In the data acquisition step, the computer acquires the wireless communication detection data, the code image detection data, and the acceleration data from an external storage device in which the wireless communication detection data, the code image detection data, and the acceleration data are stored via the network by the portable terminal. A meeting data creation method comprising:

3. The meeting data creation method according to claim 1, The meeting data creation step includes a synchrony evaluation step of evaluating the meeting detection data based on the synchrony index by the computer, The synchrony evaluation step includes: a body movement frequency calculation step in which the computer calculates a body movement frequency of the individual based on acceleration data acquired by the mobile terminal in association with the movement of the individual; a probability distribution calculation step in which the computer calculates a first probability distribution of the body movement frequency of the individual and a second probability distribution of the body movement frequency of the other individual; a joint probability distribution calculation step in which the computer calculates a joint probability distribution of the body movement frequency of the individual and the body movement frequency of another individual; a synchrony index calculation step in which the computer calculates the synchrony index based on the first probability distribution, the second probability distribution, and the joint probability distribution; Including, In the meeting data creation step, the computer creates the meeting data from the meeting detection data based on a comparison result between the synchrony index value and a synchrony threshold value. A meeting data creation method comprising:

4. The meeting data creation method according to claim 3, In the meeting data creation step, the computer associates the meeting data with the body movement frequency of the individual and stores the meeting data. A meeting data creation method comprising:

5. The meeting data creation method according to claim 3, The meeting data creation step includes a synchrony evaluation step in which the computer evaluates the meeting detection data based on the synchrony index, The synchrony evaluation step includes: a feature calculation step of the computer calculating a feature of the movement of the individual based on the acceleration data; a synchrony index calculation step of calculating the synchrony index based on a probability distribution obtained from a time series of the feature amount of the individual and the other individual, Including, In the meeting data creation step, the computer creates the meeting data from the meeting detection data based on a comparison result between a difference between the value of the synchrony index for evaluating the influence of the movement of the individual on the movement of another individual and the value of the synchrony index for evaluating the influence of the movement of the other individual on the movement of the individual, and a synchrony threshold value. A meeting data creation method comprising:

6. The meeting data creation method according to claim 3, The computer has a setting file that stores a setting value of the synchrony threshold, In the meeting data creation step, the computer creates the meeting data from the meeting detection data in which the synchrony index value is equal to or greater than the synchrony threshold value stored in the setting file. A meeting data creation method comprising:

7. The meeting data creation method according to claim 5, The computer has a setting file that stores a setting value of the synchrony threshold, In the meeting data creation step, the computer creates the meeting data from the meeting detection data in which the difference is equal to or greater than the synchronicity threshold value stored in the setting file. A meeting data creation method comprising:

8. The meeting data creation method according to claim 1, The computer receives only the wireless communication detection data, only the code image detection data, and a setting file for storing a setting value for determining whether to acquire the wireless communication detection data or the code image detection data, In the data acquisition step, the computer acquires the data in accordance with the set values. A meeting data creation method comprising:

9. The meeting data creation method according to claim 1, The computer has a setting file for storing a setting value as to whether the meeting data is to be created from the meeting detection data based on only the synchrony index, only the synchrony index, or both the synchrony index and the synchrony index; In the meeting data creation step, the computer creates the meeting data from the meeting detection data in accordance with the set value. A meeting data creation method comprising:

10. The meeting data creation method according to any one of claims 7 to 9, a setting change receiving step in which the computer receives a change to the setting value; a meeting data updating step in which the computer updates the meeting data according to the changed setting value; A meeting data creation method comprising the steps of:

11. The meeting data creation method according to claim 1, the meeting data creation step includes a body orientation estimation step of estimating a body orientation of the individual based on acceleration data and geomagnetic data detected by the mobile terminal, In the face-to-face data creation step, the computer associates the face-to-face data with the body orientation of the individual and stores the data. A meeting data creation method comprising:

12. A meeting data creation program for causing a computer including a processor and a memory to function as a meeting data creation server that creates meeting data for analyzing meetings between a plurality of individuals within an organization, the program comprising: The computer, a data acquisition unit that acquires at least one of wireless communication detection data indicating that a portable terminal carried by the individual has received identification information of another portable terminal carried by the other individual via wireless communication and code image detection data indicating that a code image of the identification information of the other portable terminal has been detected by the portable terminal, and acceleration data detected by the portable terminal; a meeting detection data creation unit that creates meeting detection data indicating that a possibility that the individual has met another individual is detected based on the data acquired by the data acquisition unit; a synchrony index for evaluating synchrony indicating the degree of influence of the movement of the individual on the movement of the other individual based on the acceleration data, and a synchrony index for evaluating synchrony indicating the degree of synchrony of the body movement frequencies of the individual and the other individual based on the acceleration data, based on an evaluation result of the meeting detection data using an evaluation index including at least one of the following: A face-to-face data creation program to function as.

13. A meeting data creation system for creating meeting data for analyzing meetings between a plurality of individuals within an organization, comprising: The meeting data creation system includes: A plurality of mobile terminals carried by each of the individuals; A meeting data creation server; Each of the mobile terminals is An acceleration sensor; a wireless communication unit that transmits identification information of the terminal and receives identification information of other portable terminals carried by other said individuals; an imaging unit for detecting a code image of the identification information of the other portable terminal; an acceleration detection unit that records acceleration data detected by the acceleration sensor; a wireless communication detection unit that records wireless communication detection data indicating that the identification information of the other portable terminal has been received by the wireless communication unit; a code image detection unit that records code image detection data indicating that the code image has been detected by the imaging unit; a communication unit that transmits the acceleration data, the wireless communication detection data, and the code image detection data to an external storage device connected via a network, The meeting data creation server includes: a data acquisition unit that acquires at least one of the wireless communication detection data and the code image detection data, and the acceleration data from the external storage device via the network; a meeting detection data creation unit that creates meeting detection data indicating that a possibility that the individual has met another individual is detected based on the data acquired by the data acquisition unit; a meeting data creation unit that creates the meeting data indicating that the individual has met the other individual from the meeting detection data based on an evaluation result of the meeting detection data using an evaluation index including at least one of a synchrony index that evaluates synchrony indicating the degree of influence that the movement of the individual has on the movement of the other individual based on the acceleration data, and a synchrony index that evaluates synchrony indicating the degree of synchrony between the body movement frequencies of the individual and the other individual based on the acceleration data; and A meeting data creation system comprising:

Citation Information

Patent Citations

  • System for visualizing measurement of attention degree

    JP2010061328A

  • Organization communication visualization system

    JP2012128882A

  • Network analysis method, server and network analysis system

    JP2018081406A

  • Support device and program

    JP2020008981A

  • Data transfer method, data transfer system, terminal device, and program

    JP2020123190A