JP4384905B2 - Information sharing method and information sharing processing program - Google Patents

Description

  The present invention relates to an information sharing method and an information sharing processing program capable of sharing information among a plurality of users in a community.

Conventionally, an information sharing system that performs information sharing using a centralized server manages the entire system using the centralized server, which causes a problem that the cost for maintenance of the centralized server becomes enormous. On the other hand, an information sharing system (hereinafter referred to as a network community system) that can share information without requiring a centralized server has been proposed. In this network community system, an autonomous agent moves between a plurality of terminals, records a specific message embedded in the agent on the terminal, and forms a network community based on the recorded specific message. Information sharing. Such an information sharing system is disclosed in Patent Document 1 below.
JP 2001-144754 A (FIG. 2)

  However, in a network community system such as that disclosed in Patent Document 1, each terminal stores information for identifying other terminals necessary for acquiring information possessed by other terminals, such as a mail address. When the mail address is changed, the mail address stored in each terminal must be corrected, which is troublesome.

  The present invention is for solving the above-described problem, and does not require the cost for maintenance of a centralized server, and an information sharing method capable of sharing information without retaining information on other terminals between communities and An object is to provide an information sharing processing program.

In order to achieve the above object, according to the present invention, based on terminal program information belonging to a terminal, the terminal is composed of terminals for a user to participate in order to achieve a certain purpose, Searching for a community having a common purpose based on a participation condition to the community including the purpose set by the user among a plurality of communities sharing information between the terminals to achieve the purpose; the information search result, which moves a step with the target that has been set Ru said to join the terminal itself to the community in case of finding the community having a common purpose, between the terminal and shared among the terminals To the community program information having at least one of the shared information or the identification information of the terminal holding the shared information Handing over at least one of information held by the terminal of the user participating in the community or identification information of the terminal of the user, and the community program information that moves between the terminals when acquiring the shared information of the community Capturing the shared information to the captured community program information, and based on the shared information acquisition request, at least the shared information or the identification information of the terminal holding the shared information Acquiring one from the community program information, and, when acquiring identification information of the terminal holding the shared information, requesting the terminal to acquire the shared information based on the acquired identification information. An information sharing method is provided.

Moreover, in the information sharing method of the above invention, the terminal joins the community when the terminal finds the community having the same purpose as the set purpose as a result of searching the community and joins the community. It is a preferable aspect of the present invention to further include a step of inquiring whether or not.

Moreover, in the information sharing method of the above invention, it is a preferred aspect of the present invention that the terminal further includes a step of leaving the community when the terminal satisfies a predetermined exit condition from the community.

Moreover, in the information sharing method of the above invention, it is a preferable aspect of the present invention that the terminal further has a step of inquiring whether or not to leave when the terminal satisfies the leaving condition from the community. .

  According to the present invention, there is provided an information sharing processing program for executing the information sharing method according to any one of claims 1 to 4 by a computer.

  According to the present invention, there is provided an information sharing processing program for executing the information sharing method according to any one of claims 1 to 4 by an in-vehicle device.

  The information sharing method and information sharing processing program of the present invention have the above-described configuration, do not require the cost of maintenance of the centralized server, and can share information without holding information on other terminals between communities. it can.

  Hereinafter, embodiments of the present invention will be described with reference to FIGS. FIG. 1 is a diagram for explaining an information sharing method according to an embodiment of the present invention. FIG. 2 is a diagram for explaining participation in a plurality of communities in the information sharing method according to the embodiment of the present invention. FIG. 3 is a flowchart for explaining a method of joining a community in the information sharing method according to the embodiment of the present invention. FIG. 4 is a flowchart for explaining a method of joining a community in the information sharing method according to the embodiment of the present invention. FIG. 5 is a flowchart for explaining a method of leaving the community in the information sharing method according to the embodiment of the present invention. FIG. 6 is a flowchart for explaining a method of leaving the community in the information sharing method according to the embodiment of the present invention.

  FIG. 7 is a diagram for explaining community division in the information sharing method according to the embodiment of the present invention. FIG. 8 is a diagram for explaining community coupling in the information sharing method according to the embodiment of the present invention. FIG. 9 is a flowchart for explaining the information sharing method according to the embodiment of the present invention. FIG. 10 is a diagram for explaining congestion avoidance using the information sharing method according to the embodiment of the present invention. FIG. 11 is a diagram for explaining the realization of smooth running using the information sharing method according to the embodiment of the present invention. FIG. 12 is a diagram for explaining the realization of danger prediction using the information sharing method according to the embodiment of the present invention. FIG. 13 is a diagram for explaining another pattern for realizing risk prediction using the information sharing method according to the embodiment of the present invention. FIG. 14 is a diagram for describing use of a service area using the information sharing method according to the embodiment of the present invention.

  First, an information sharing method according to an embodiment of the present invention will be described with reference to FIG. Here, a case will be described in which the information sharing method according to the embodiment of the present invention is applied to a community 100 composed of vehicles 101A and 101B and a PDA (Personal Digital Assistant) 102. Although the community 100 is composed of the vehicles 101A, 101B, and the PDA 102 for the sake of convenience, strictly speaking, community program information to be described later moves between the terminals mounted on the vehicles 101A and 101B and the PDA 102, respectively. . Hereinafter, when the vehicle becomes a component of the community, it is considered that the community program information moves on the terminal mounted on the vehicle. Here, the terminal means, for example, a car navigation system, an in-vehicle PC, a mobile phone terminal, a PDA, or the like. Further, the configuration of the community 100 is not limited to the configuration of only the vehicles 101A, 101B, and the PDA 102. The community 100 is configured to share information and achieve a certain purpose (hereinafter also referred to as a common purpose). Here, the common purpose refers to, for example, early arrival at the same destination or enhancement of information between persons having the same interest, hobby, and preference. The community 100 includes, for example, a community for going to the same amusement park, a community for exchanging information about restaurants, and a community for exchanging information between users having the same vehicle type.

  As shown in FIG. 1, sharing of information is realized by moving community program information between the vehicles 101 </ b> A, 101 </ b> B, and PDA 102 constituting the community 100. The community program information is a program that moves between a plurality of terminals constituting the community 100, has at least one of identification information or information permitted by the user, and operates independently, for example, an agent. The community program information may be data. The identification information refers to information for specifying each of the terminals constituting the community 100, for example, information such as a URL. Also, the information permitted by the user (hereinafter also referred to as user permission information) is information that the user is allowed to share information, for example, information for achieving the above-described common purpose, the user himself / herself Information on the current location of the user, information on the weather, temperature, humidity, and congestion of the surroundings of the user himself.

  Information sharing when the community 100 is a community for exchanging information about restaurants will be described below. When the user of the vehicle 101A wants to share information about a French restaurant in Shibuya, for example, the terminal program information described below sets a flag for information acquisition and stops at the terminal where the flag is set. Capture information. The terminal program information makes an acquisition request for information about the French restaurant in Shibuya to the captured community program information, and acquires the identification information when the community program information has only the identification information described above based on the acquisition request. Based on the acquired identification information, the terminal program information inquires of the terminal in the community 100 whether or not it has information on a French restaurant in Shibuya. Get restaurant information. The inquiry here is made directly to the terminal based on the URL, for example. The terminal program information is a program that operates independently as well as the process of acquiring information as described above, searching for the community 100 that can participate as described later, and also performing the process of joining the searched community 100, For example, an agent. However, the present invention is not limited to these processes, and processes necessary for information sharing may be performed.

  If the community program information includes only the user permission information or the user permission information and the identification information, the user permission information may be acquired without acquiring the identification information. In the acquisition here, at least one of the community program information and the terminal program information has a function of selecting information corresponding to the information requested by the terminal from the user permission information. Thereby, it is not necessary to make an inquiry about information to terminals in the community 100, and desired information can be acquired immediately. In the above-described example, one community program information is moved between terminals, but the number is not limited to one, and a plurality of community program information may be moved. Thereby, desired information can be acquired more rapidly. Also, as described above, in addition to community program information moving between terminals to share information, there is a copy of community program information on each terminal, and information is shared by communicating between community program information. It is good also to do.

  In the example described above, information sharing in one community 100 has been described, but the terminal may participate in a plurality of communities. A case where the terminal participates in a plurality of communities will be described with reference to FIG. As shown in FIG. 2, the community 200A includes a vehicle 201A, a vehicle 201B, and a vehicle 201C. On the other hand, the community 200B includes a vehicle 201C, a vehicle 201D, and a vehicle 201E. The community 200A is a community that exchanges information about restaurants, for example, and the community 200B is a community that goes to the same amusement park, for example.

  At this time, since the vehicle 201C participates in both communities, information shared between both communities can be acquired, but the vehicle 201A and the vehicle 201B cannot share information on the community 200B. In addition, the vehicle 201D and the vehicle 201E cannot share information on the community 200A. If the vehicle 201A and the vehicle 201B intend to share information on the community 200B, they must participate in the community 200B. Similarly, if the vehicle 201D and the vehicle 201E intend to share information on the community 200A, they must participate in the community 200A.

  Next, a method for joining the community 100 will be described with reference to FIGS. FIG. 3 is a flowchart for explaining a case where terminal program information belonging to a terminal on the user side who intends to participate in the community 100 automatically determines participation in the community 100. The terminal program information searches for a community 100 that can participate in addition to the above-described acquisition of information, and also performs a process of participating in the searched community 100. In the terminal program information, a participation condition for the community 100 set in advance by the user is embedded. The terminal program information searches for the community 100 that matches the embedded participation condition, and as a result of the search, the matching community When 100 is discovered, the terminal is automatically joined to the community 100. More specifically, the terminal program information is, for example, a copy is generated, the generated copy of the terminal program information is moved to the community 100, the community 100 matching the participation condition is searched, and the information of the matching community 100 is detected. Is brought back to the copy source, and based on this, the terminal program information of the copy source causes the terminal to participate in the community 100. The participation condition usually refers to a condition of participating in a community that meets a common purpose, but is not limited to this, and other conditions may be added.

  As shown in FIG. 3, the terminal program information belonging to the terminal of the user who intends to participate in the community 100 searches for the community 100 having a common purpose, and whether or not the corresponding community 100 is found as a result of the search. Judgment is made (step S301). If it is determined that the corresponding community 100 has been found, the terminal program information provides the user's own identification information, for example, the URL here, to the community program information (step S302). Next, the terminal program information provides user permission information to the community program information (step S303).

  The user permission information may have an expiration date, for example, information with a time limit of 10 minutes or 18:00. In addition, although terminal program information provides the user's own identification information and user permission information in step S302 and step S303, it is sufficient to provide at least one, and it is not necessary to provide both to the community 100. The terminal program information determines participation in the community 100 (step S304). In step S301, if the community 100 having a common purpose cannot be found, the search is continued until it can be found. Alternatively, if another terminal having a common purpose cannot be found within a predetermined time and the terminal program information is found, a new community 100 may be formed with the found terminal. Good.

  Next, as described with reference to FIG. 3, a case where the user himself / herself decides to participate instead of the terminal program information determining to participate in the community 100 will be described with reference to FIG. 4. As shown in FIG. 4, the terminal program information belonging to the terminal of the user who intends to participate in the community 100 searches for the community 100 having a common purpose, and determines whether or not the corresponding community 100 is found as a result of the search. Judgment is made (step S401). When it is determined that the corresponding community 100 has been found, the terminal program information outputs community information indicating that it has been found (step S402). The terminal program information participates in the question of whether or not the user participates in the community 100 (step S403), that is, if YES, the user's own identification information, for example, the URL here is provided to the community program information (step S404). . Community information refers to information about the community 100, for example, information such as the purpose of the community 100.

  The terminal program information provides user permission information to the community program information (step S405). In addition, although terminal program information provides the user's own identification information and user permission information in step S404 and step S405, it is sufficient to provide at least one, and it is not necessary to provide both to the community 100. The terminal program information determines participation in the community 100 (step S406). Here, if the terminal program information is received in step S403 that the user does not participate in the community 100, the terminal program information is searched for another community 100 again. The terminal program information continues to be searched until it can be found in step S401 when the community 100 having a common purpose cannot be found. Or, if another terminal having a common purpose cannot be found within a predetermined time and the terminal program information is found, whether or not to form a new community 100 with the found terminal The inquiry may be made to the user.

  Next, a method for leaving the community 100 will be described below with reference to FIGS. FIG. 5 is a flowchart for explaining the flow of automatically leaving the terminal from the community 100 when it is determined that the terminal program information matches the leaving condition. Here, the exit condition refers to a condition for exiting, for example, a condition to exit when a predetermined time elapses. As shown in FIG. 5, the terminal program information determines whether or not the exit condition is met (step S501). When it is determined that the terminal program information matches the exit condition, the terminal program information transmits an exit message to the community program information (step S502). Then, the terminal program information causes the terminal to which the terminal program belongs to leave the community 100 (step S503). When the terminal leaves the community 100, the user permission information of the terminal that has left the community 100 is deleted.

  Next, as described with reference to FIG. 5, the case where the user himself / herself decides to exit instead of the terminal program information determining to leave the community 100 will be described with reference to FIG. 6. As shown in FIG. 6, the terminal program information determines whether or not the user has requested to leave the community 100 (step S601). If it is determined that the terminal program information has received a request for leaving from the user, the terminal program information transmits a leaving message to the community program information (step S602). Then, the terminal program information causes the terminal to which the terminal program belongs to leave the community 100 (step S603). When the terminal leaves the community 100, the user permission information of the terminal that has left the community 100 is deleted.

  Next, community division will be described with reference to FIG. As shown in FIG. 7, community program information 700A divides a community and divides community program information 700A itself into community program information 700B and 700C when a predetermined division condition is met. The divided community program information 700B and 700C is a copy of the community program information 700A. That is, the community program information 700B and 700C retains information included in the community program information 700A, for example, identification information and information permitted by the user as it is. The predetermined division condition is, for example, a condition for dividing when the number of terminals constituting the community becomes 10 or more, or division when the user permission information included in the community program information 700A has a certain amount of data. Say the conditions. The division condition may be a combination of these conditions.

  That is, the community program information 700A divides a community when, for example, it is determined that the number of communities has become 10 or more, and assigns community program information 700B and 700C, which are copies of the community program information 700A, to each of the divided communities. At this time, the URL that is information for specifying the community program information 700C is stored in the community program information 700B, while the URL that is information for specifying the community program information 700B is stored in the community program information 700C. Is stored. Thereby, even if it is divided, information can be shared because links are established between the communities.

  Next, community connection will be described with reference to FIG. As shown in FIG. 8, community program information 800A and 800B are combined when a predetermined combination condition is satisfied, thereby forming community program information 800C. The predetermined combining condition is, for example, a condition that combining is performed when the number of terminals constituting the community is three or less, or when the user permission information included in the community program information 800A and 800B is less than a certain amount of data. Says the condition of joining. Note that the combination condition may be a combination of these conditions. In community combination, the purpose of each community to be combined must be the same.

  Here, when the connection condition is 3 or less terminals, the connection is a condition that the connection is made. When the number of community terminals to which the community program information 800A and 800B belong is 2 and 3, respectively, the community program information 800A is While searching for a community having the same purpose, the community program information 800B also searches for a community having the same purpose. When the purpose of the community to which the community program information 800A belongs and the purpose of the community to which the community program information 800B belongs are the same, the community program information 800A and 800B are coupled to each other. As a result, the information included in the community program information 800A and 800B is combined. Here, community program information 800C after being combined may be either one of community program information 800A and 800B, or may be newly generated community program information. In more detail, the community program information 800A and 800B generate a copy of each, move the generated copy between communities, and select a community that has the same purpose and meets the connection conditions. If you find them, let them know. Thereby, the community program information 800A and 800B are combined.

  Next, an information sharing flow will be described with reference to FIG. As shown in FIG. 9, the terminal program information is composed of terminals for the user to participate in order to achieve a certain purpose, and the information is shared among a plurality of terminals in order to achieve the certain purpose. Of the plurality of communities, a community having the same purpose as the common purpose set by the user is searched (step S901). As a result of the search, the terminal program information is made to participate in the community when a community having the same purpose as the set purpose is found (step S902). The terminal program information delivers at least one of the user permission information held by the terminal of the user who participates in the community or the identification information of the user terminal to the community program information (step S903).

  The terminal program information captures community program information when acquiring user permission information possessed by terminals constituting the community (step S904). The terminal program information makes an acquisition request for user permission information based on the information desired by the user of the terminal to which the terminal program information belongs to the captured community program information (step S905). The terminal program information acquires at least one of the user permission information and the identification information in response to the user permission information acquisition request (step S906).

  Here, when the community program information includes user permission information, either the terminal program information or the community program information is based on information desired by the user of the terminal to which the terminal program information belongs. The terminal program information obtains the selected user permission information. On the other hand, when the community program information does not have user permission information but has only identification information, the terminal program information acquires identification information. When the terminal program information has acquired the identification information, the terminal program information makes an acquisition request for user permission information to the corresponding terminal based on the acquired identification information (step S907). The terminal program information acquires user permission information from the corresponding terminal based on this acquisition request. An information sharing processing program for executing the above steps may be executed by an in-vehicle device such as a computer or a car navigation system.

  Hereinafter, traffic jam avoidance using the above-described information sharing method will be described with reference to FIG. As shown in FIG. 10, all of the vehicles 1001A, 1001B, 1001C, 1001D, 1001E, and 1001F are traveling in the direction indicated by the arrow 1000. These vehicles constitute a “car community traveling in the same direction”. The vehicles 1001C, 1001D, and 1001F are vehicles that go to the same amusement park, and constitute a “car community that goes to the same amusement park”. Here, when the vicinity of the vehicles 1001D, 1001E, and 1001F is congested, the information indicating that the vehicles 1001D, 1001E, and 1001F constituting the “car community traveling in the same direction” are congested and the current The information on the user's own location is shared as user permission information within the community.

  When the terminal program information belonging to each of the vehicles 1001A, 1001B, and 1001C makes a traffic jam information acquisition request to the community program information that moves between vehicles, the terminal program information that belongs to each of the vehicles 1001A, 1001B, and 1001C User permission information including information that 1001D, 1001E, and 1001F are congested, information on the location of the traffic jam location, and the like is acquired. As a result, the vehicles 1001A, 1001B, and 1001C avoid traffic jams, the vehicle 1001B turns right and changes the route in the direction of the vehicle 1001B ', and the vehicle 1001C turns left and changes the route in the direction of the vehicle 1001C'. The vehicles 1001B and 1001C leave the “vehicle community traveling in the same direction” after changing the route. Note that the vehicle 1001C continues to participate in the “car community heading to the same amusement park” even if it turns left and leaves the “car community traveling in the same direction”.

  Next, realization of smooth running using the information sharing method described above will be described with reference to FIG. As shown in FIG. 11, there are a vehicle 1101A that is going straight in the direction indicated by the arrow 1100, a vehicle 1101B that is going to turn left at the intersection, and a vehicle 1101C that is going to turn right at the intersection. At this time, between the vehicles 1101A, 1101B, and 1101C, a “car community entering the intersection” having a common purpose of smoothly traveling at the intersection is configured. For example, since the vehicle 1101A wants to go straight through an intersection, the terminal program information belonging to the vehicle 1101A requests acquisition of information on a vehicle that turns right and left at the intersection. Based on the acquisition request, the community program information is transferred from the vehicles 1101B and 1101C to the vehicle 1101A if it has information such as route information, and if it has no information such as route information, the identification information of the vehicles 1101B and 1101C. Hand over.

  Since the terminal program information belonging to the vehicle 1101A that acquired the route information can be understood that the vehicle 1101B makes a left turn at the intersection and the vehicle 1101C makes a right turn at the intersection, for example, this is output to the car navigation system. The output in this case includes a display on the display screen and a sound. Thereby, it can drive | work an intersection smoothly. After the vehicles 1101B and 1101C make a left turn or a right turn, the vehicles 1101B and 1101C leave the “car community entering the intersection”, and the vehicle 1101A goes straight through the intersection and passes through the intersection. Exit the car community entering. In the above-described example, the community between vehicles entering the intersection has been described. However, by constructing a community between vehicles traveling in the same direction, it is possible to facilitate interruptions between vehicles. it can.

  Next, the realization of danger prediction using the information sharing method described above will be described with reference to FIG. FIG. 12A shows vehicles 1201A and 1201B traveling in the direction indicated by arrow 1200, parked vehicle 1201C parked in the travel lane of vehicle 1201A, and a mobile phone owned by a person standing in front of parked vehicle 1201C. Terminal 1202 is shown. At this time, a “terminal community existing within a predetermined radius centered on the vehicle 1201A” having a common purpose of smooth traffic between the vehicle 1201A, the vehicle 1201B, and the mobile phone terminal 1202 is formed. Here, the reason why the community centered on the vehicle 1201A is configured is that, for example, when the vehicle 1201A wants to change lanes, the community configuration for the surrounding vehicles having a common purpose of wanting smooth traffic is set. This is because they were actively encouraged.

  In other words, the vehicle 1201B and the mobile phone terminal 1202 that are prompted to form a community have a common purpose of smoothly traveling, but in this case, they did not actively want a community structure. This is because the participation in the community was a passive participation. In the community configured in this way, for example, since the vehicle 1201A wants to change lanes, the terminal program information belonging to the vehicle 1201A requests acquisition of information on the front and subsequent vehicles and people. Based on the acquisition request, the community program information is handed over to the vehicle 1201A if it has information such as the current location from the vehicle 1201B and the mobile phone terminal 1202, and the vehicle 1201B and the mobile phone if it does not have information such as the current location. The identification information of the telephone terminal 1202 is handed over.

  The terminal program information belonging to the vehicle 1201A that has acquired the current position information indicates that the vehicle 1201B is traveling behind and the person having the mobile phone terminal 1202 is in front of the parked vehicle 1201C. To that effect. The output in this case includes a display on the display screen and a sound. This makes it possible to change lanes while paying attention. When the vehicle 1201B and the mobile phone terminal 1202 are located outside a predetermined radius of the vehicle 1201A, they leave the “terminal community existing within a predetermined radius centered on the vehicle 1201A”. Then, after the vehicle 1201B and the mobile phone terminal 1202 leave the community, only the vehicle 1201A constitutes the community, and thus the community disappears.

  FIG. 12B shows the vehicles 1201D and 1201E entering the T-junction. At this time, a “terminal community that exists within a predetermined radius centered on the vehicle 1201D” is formed between the vehicle 1201D and the vehicle 1201E. Also in this case, similar to the description in FIG. 12A, the vehicle 1201 </ b> D prompted an aggressive community configuration, and thus a community centered on the vehicle 1201 </ b> D was formed. In the community configured in this way, for example, since the vehicle 1201D wants to enter a T-junction, the terminal program information belonging to the vehicle 1201D requests acquisition of information on vehicles and people entering the T-junction. Based on the acquisition request, the community program information is transferred from the vehicle 1201E to the vehicle 1201D if it has information such as the current position, and the identification information of the vehicle 1201E is transferred if it does not have information such as the current position.

  Since the terminal program information belonging to the vehicle 1201D that has acquired the current position information indicates that the vehicle 1201E enters the T-junction, for example, this is output to the car navigation system. The output in this case includes a display on the display screen and a sound. Thereby, it is possible to enter the T-junction while paying attention. When vehicle 1201E is positioned outside a predetermined radius of vehicle 1201D, vehicle 1201E leaves the “terminal community existing within a predetermined radius centered on vehicle 1201D”. Then, after the vehicle 1201E leaves the community, only the vehicle 1201D constitutes the community, and thus the community disappears.

  Next, another pattern for realizing danger prediction using the information sharing method described above will be described with reference to FIG. In FIG. 13, the vehicles 1301A and 1301B trying to make a right turn at the intersection, the motorcycle 1300 hidden behind the vehicle 1301B and going straight through the intersection, the vehicles 1301C and 1301D waiting for traffic lights, and traffic information of the intersection Sensors 1302A to 1302D to collect are shown. At this time, an “intra-intersection terminal community” having a common purpose of smoothly moving between the vehicles 1301A to 1301D and the sensors 1302A to 1302D is formed. For example, since the vehicle 1301A wants to turn right at the intersection, the terminal program information belonging to the vehicle 1301A requests acquisition of information on vehicles and people entering the intersection.

  Based on the acquisition request, the community program information is delivered from the sensor 1302A to the vehicle 1301A if it has traffic information at the intersection, and the identification information of the sensor 1302A is delivered if it does not have traffic information at the intersection. . The sensors 1302A to 1302D can obtain information on traffic conditions at intersections from a fixed point camera or the like. Since the sensor 1302A can recognize the existence of the motorcycle 1300 entering the intersection from a fixed point camera or the like, even if the motorcycle 1300 is not participating in the community, the information of the existence of the motorcycle 1300 is provided to the terminals constituting the community. Can do. The same applies to the other sensors 1302B to 1302D. The terminal program information belonging to the vehicle 1301A obtains information by directly inquiring of the sensor 1302A when the identification information is delivered.

  Since the terminal program information belonging to the vehicle 1301A that acquired the traffic condition information of the intersection indicates that the motorcycle 1300 enters the intersection, for example, the car navigation system outputs that information. The output in this case includes a display on the display screen and a sound. This makes it possible to turn right at the intersection while paying attention. When the vehicle 1301A completes the right turn at the intersection, the vehicle 1301A leaves the “inter-terminal community”. The same applies to the vehicle 1301B. The same applies to the case where the vehicle 1301D is about to turn left. When a motorcycle (not shown) traveling on the left rear of the vehicle 1301D tries to go straight through the intersection, the terminal program information belonging to the vehicle 1301D can receive information on the motorcycle (not shown) from the sensor 1302B. This makes it possible to turn left with care.

  Next, service area utilization using the information sharing method described above will be described with reference to FIG. FIG. 14 shows a service area 1400 and vehicles 1401A and 1401B traveling on a road. At this time, a “terminal community existing within a predetermined radius centered on the service area 1400” having a common purpose of resting between the service area 1400 and the vehicles 1401A and 1401B is formed. For example, since the vehicle 1401A wants to take a break, the terminal program information belonging to the vehicle 1401A requests acquisition of information on the congestion status of the service area 1400. Based on the acquisition request, the community program information is delivered to the vehicle 1401A if it has congestion status information from the service area 1400, and the service area 1400 identification information is delivered if it does not have congestion status information.

  The terminal program information belonging to the vehicle 1401A that has acquired the congestion status information causes the congestion information to be output to, for example, a car navigation system. The output in this case includes a display on the display screen and a sound. Thereby, it is possible to determine whether or not to stop at the service area 1400. In addition, it is also possible to obtain information on a meal menu and an empty space in a parking lot when stopping by. When vehicles 1401A and 1401B go outside the predetermined radius of service area 1400, they leave the “terminal community existing within a predetermined radius centered on service area 1400”. Then, after the vehicles 1401A and 1401B have left the community, the community disappears when only the service area 1400 constitutes the community. In the example described above, the case of the vehicle 1401A has been described, but the same applies to the vehicle 1401B.

  The information sharing method and the information sharing processing program according to the present invention do not require the cost of maintaining the centralized server, and can share information without holding information on other terminals between communities. It is useful for an information sharing method and an information sharing processing program that can share information among a plurality of users.

It is a figure for demonstrating the information sharing method which concerns on embodiment of this invention. It is a figure for demonstrating participation in a some community in the information sharing method which concerns on embodiment of this invention. It is a flowchart for demonstrating the method to participate in a community in the information sharing method which concerns on embodiment of this invention. It is a flowchart for demonstrating the method to participate in a community in the information sharing method which concerns on embodiment of this invention. It is a flowchart for demonstrating the leaving method from a community in the information sharing method which concerns on embodiment of this invention. It is a flowchart for demonstrating the leaving method from a community in the information sharing method which concerns on embodiment of this invention. It is a figure for demonstrating the division | segmentation of a community in the information sharing method which concerns on embodiment of this invention. It is a figure for demonstrating the coupling | bonding of a community in the information sharing method which concerns on embodiment of this invention. It is a flowchart for demonstrating the information sharing method which concerns on embodiment of this invention. It is a figure for demonstrating the congestion avoidance using the information sharing method which concerns on embodiment of this invention. It is a figure for demonstrating implementation | achievement of smooth driving | running | working using the information sharing method which concerns on embodiment of this invention. It is a figure for demonstrating realization of danger prediction using the information sharing method which concerns on embodiment of this invention. It is a figure for demonstrating the other pattern of implementation | achievement of a risk prediction using the information sharing method which concerns on embodiment of this invention. It is a figure for demonstrating utilization of the service area using the information sharing method which concerns on embodiment of this invention.

Explanation of symbols

100, 200A, 200B Community 101A, 101B, 201A, 201B, 201C, 201D, 201E, 1001A, 1001B, 1001B ′, 1001C, 1001C ′, 1001D, 1001E, 1001F, 1101A, 1101B, 1101C, 1201A, 1201B, 1201C, 1201D, 1201E, 1301A, 1301B, 1301C, 1301D, 1401A, 1401B Vehicle 102 PDA
700A, 700B, 700C, 800A, 800B, 800C Community program information 1000, 1100, 1200 Arrow 1202 Mobile phone terminal 1300 Bike 1302A, 1302B, 1302C, 1302D Sensor 1400 Service area

Claims (6)

Based on the terminal program information belonging to the terminal, the terminal
A purpose set by a user among a plurality of communities configured by terminals for users to participate in achieving a certain purpose and sharing information among the terminals to achieve the certain purpose Searching for communities with a common purpose based on community participation criteria including :
Search result, comprising the steps of Ru to join the terminal itself to the community in case of finding the community having a common interest with the target that has been set,
The terminal of the user who participates in the community to community program information that moves between the terminals and has at least one of shared information that is the information shared between the terminals or identification information of the terminal that holds the shared information Handing over at least one of the information held by the user or the identification information of the terminal of the user;
When acquiring the shared information of the community, capturing the community program information moving between the terminals;
Requesting acquisition of the shared information to the captured community program information;
Acquiring at least one of the shared information or the identification information of the terminal holding the shared information from the community program information based on the request for acquiring the shared information;
When the identification information of the terminal holding the shared information is acquired, the step of making an acquisition request for the shared information to the terminal based on the acquired identification information.
An information sharing method. As a result of searching for the community, when the terminal discovers the community having a purpose common to the set purpose and joins the community, the terminal further asks whether to join the community. The information sharing method according to claim 1. The information sharing method according to claim 1, further comprising a step of leaving the community when the terminal satisfies a predetermined exit condition from the community. The information sharing method according to claim 3, further comprising a step of inquiring whether or not to leave when the terminal satisfies the leaving condition from the community.   An information sharing processing program for executing the information sharing method according to claim 1 by a computer.   An information sharing program for executing the information sharing method according to any one of claims 1 to 4 by an in-vehicle device.

Images