| Literature DB >> 27058544 |
Weiping Zhu1,2, Weiran Chen3, Zhejie Hu4, Zuoyou Li5, Yue Liang6, Jiaojiao Chen7.
Abstract
Mobile group consumption refers to consumption by a group of people, such as a couple, a family, colleagues and friends, based on mobile communications. It differs from consumption only involving individuals, because of the complex relations among group members. Existing data collection systems for mobile group consumption are centralized, which has the disadvantages of being a performance bottleneck, having single-point failure and increasing business and security risks. Moreover, these data collection systems are based on a synchronized clock, which is often unrealistic because of hardware constraints, privacy concerns or synchronization cost. In this paper, we propose the first asynchronous distributed approach to collecting data generated by mobile group consumption. We formally built a system model thereof based on asynchronous distributed communication. We then designed a simulation system for the model for which we propose a three-layer solution framework. After that, we describe how to detect the causality relation of two/three gathering events that happened in the system based on the collected data. Various definitions of causality relations based on asynchronous distributed communication are supported. Extensive simulation results show that the proposed approach is effective for data collection relating to mobile group consumption.Entities:
Keywords: asynchronous; data collection; distributed; mobile group consumption
Year: 2016 PMID: 27058544 PMCID: PMC4850996 DOI: 10.3390/s16040482
Source DB: PubMed Journal: Sensors (Basel) ISSN: 1424-8220 Impact factor: 3.576
Figure 1An illustration of mobile group consumption. Several people wander around a shopping mall with different regions. Each person is denoted by a node, and those belonging to groups have the same shape, except for the circle. The circle nodes denote the people who do not belong to groups (i.e., individuals). The picture on the left is a snapshot of people at timestamp , and the picture on the right is a snapshot of people at timestamp after .
Figure 2Temporal relations based on different kinds of clocks. and are devices, each of which is represented by a time axis oriented from the left to right. are events that happened in devices at different timestamps. An arrow from one event to another represents a message transfer. According to the physical clock, the sequence of events can be directly determined by their timestamps (e.g., is before ). According to the logical clock, the sequence of events is determined by message passing (e.g., is before ) or local timestamps (e.g., is before ).
Figure 3The architecture of the simulation system for mobile group consumption. The solid arrows represent data flows. The dashed arrows represent the influence between two models.
Figure 4A three-layer distributed data collection framework.
Figure 5Causality detection based on three different definitions. Each event is presented by a segment. The message passing is presented by a dashed arrow from the sender to the receiver.
Notations in the algorithms.
| Variable Name | Description |
|---|---|
| ID of a shop | |
| PROMOTION( | promotion information broadcast by |
| the variable denoting whether a consumer accepts a promotion | |
| current location of a consumer | |
| the first shop sending the message | |
| the previous shop sending the message | |
| ID of an event | |
| the depth of | |
| the vector clock attached to a message | |
| the vector clock maintained by a consumer or a shop | |
| the number of consumers in a shop | |
| a collection recording detailed consumer IDs in a shop | |
| ID of a consumer | |
| a function to generate the ID of a new event | |
| the threshold of gathered consumers to denote the occurrence of a gathering event | |
| the type of causality relation to be detected | |
| a list of events received by the current shop | |
| the initiator of | |
| the initiator of | |
| a flag recording the detection result of the first part of SSEE ( | |
| the parent of the current shop in the routing tree | |
| the children of the current shop in the routing tree | |
| the parent of the current shop in the routing tree regarding | |
| MSG_NTER( | a message denoting that |
| MSG_OUT( | a message denoting that |
| START | a message denoting the start of a gathering event |
| END | a message denoting the end of a gathering event |
| SUCCESS | a message denoting a successful detection of a causality relation |
| REVERSE | a message to notify the reverse of the routing tree |
| E | the specification of an event that needs to be detected |
| denotes whether the current node is the coordinator of E |
Figure 6The number of event patterns vs. the number of groups.
Figure 7The number of event patterns vs. the duration of a promotion.
Figure 8The number of event patterns vs. affecting distance.
Figure 9The number of event patterns vs. the interval between two promotions.
Figure 10The number of event patterns vs. the number of groups.
Figure 11The number of event patterns vs. T.
Figure 12The number of event patterns vs. affecting distance.
Figure 13The number of common event patterns/the max number of messages between two events vs. the number of groups.
Figure 14The number of common event patterns/the max number of messages between two events vs. the affecting distance.