PMC:7796058 / 42527-48931 JSONTXT

{"project":"LitCovid-PubTator","denotations":[{"id":"290","span":{"begin":1090,"end":1096},"obj":"Gene"},{"id":"291","span":{"begin":715,"end":721},"obj":"Gene"},{"id":"292","span":{"begin":519,"end":525},"obj":"Gene"},{"id":"293","span":{"begin":1137,"end":1145},"obj":"Disease"},{"id":"299","span":{"begin":2503,"end":2509},"obj":"Species"},{"id":"300","span":{"begin":1311,"end":1319},"obj":"Disease"},{"id":"301","span":{"begin":1822,"end":1830},"obj":"Disease"},{"id":"302","span":{"begin":2233,"end":2241},"obj":"Disease"},{"id":"303","span":{"begin":2400,"end":2408},"obj":"Disease"},{"id":"307","span":{"begin":3527,"end":3533},"obj":"Gene"},{"id":"308","span":{"begin":3446,"end":3452},"obj":"Gene"},{"id":"309","span":{"begin":3197,"end":3203},"obj":"Gene"},{"id":"317","span":{"begin":3980,"end":3986},"obj":"Gene"},{"id":"318","span":{"begin":3829,"end":3835},"obj":"Gene"},{"id":"319","span":{"begin":3613,"end":3619},"obj":"Gene"},{"id":"320","span":{"begin":4143,"end":4154},"obj":"Species"},{"id":"321","span":{"begin":4036,"end":4044},"obj":"Disease"},{"id":"322","span":{"begin":4106,"end":4114},"obj":"Disease"},{"id":"323","span":{"begin":4370,"end":4378},"obj":"Disease"},{"id":"328","span":{"begin":5352,"end":5358},"obj":"Gene"},{"id":"329","span":{"begin":5206,"end":5212},"obj":"Gene"},{"id":"330","span":{"begin":5625,"end":5633},"obj":"Disease"},{"id":"331","span":{"begin":5809,"end":5817},"obj":"Disease"},{"id":"333","span":{"begin":6039,"end":6045},"obj":"Gene"}],"attributes":[{"id":"A290","pred":"tao:has_database_id","subj":"290","obj":"Gene:59286"},{"id":"A291","pred":"tao:has_database_id","subj":"291","obj":"Gene:59286"},{"id":"A292","pred":"tao:has_database_id","subj":"292","obj":"Gene:59286"},{"id":"A293","pred":"tao:has_database_id","subj":"293","obj":"MESH:C000657245"},{"id":"A299","pred":"tao:has_database_id","subj":"299","obj":"Tax:9606"},{"id":"A300","pred":"tao:has_database_id","subj":"300","obj":"MESH:C000657245"},{"id":"A301","pred":"tao:has_database_id","subj":"301","obj":"MESH:C000657245"},{"id":"A302","pred":"tao:has_database_id","subj":"302","obj":"MESH:C000657245"},{"id":"A303","pred":"tao:has_database_id","subj":"303","obj":"MESH:C000657245"},{"id":"A307","pred":"tao:has_database_id","subj":"307","obj":"Gene:59286"},{"id":"A308","pred":"tao:has_database_id","subj":"308","obj":"Gene:59286"},{"id":"A309","pred":"tao:has_database_id","subj":"309","obj":"Gene:59286"},{"id":"A317","pred":"tao:has_database_id","subj":"317","obj":"Gene:59286"},{"id":"A318","pred":"tao:has_database_id","subj":"318","obj":"Gene:59286"},{"id":"A319","pred":"tao:has_database_id","subj":"319","obj":"Gene:59286"},{"id":"A320","pred":"tao:has_database_id","subj":"320","obj":"Tax:11118"},{"id":"A321","pred":"tao:has_database_id","subj":"321","obj":"MESH:C000657245"},{"id":"A322","pred":"tao:has_database_id","subj":"322","obj":"MESH:D007239"},{"id":"A323","pred":"tao:has_database_id","subj":"323","obj":"MESH:C000657245"},{"id":"A328","pred":"tao:has_database_id","subj":"328","obj":"Gene:59286"},{"id":"A329","pred":"tao:has_database_id","subj":"329","obj":"Gene:59286"},{"id":"A330","pred":"tao:has_database_id","subj":"330","obj":"MESH:C000657245"},{"id":"A331","pred":"tao:has_database_id","subj":"331","obj":"MESH:C000657245"},{"id":"A333","pred":"tao:has_database_id","subj":"333","obj":"Gene:59286"}],"namespaces":[{"prefix":"Tax","uri":"https://www.ncbi.nlm.nih.gov/taxonomy/"},{"prefix":"MESH","uri":"https://id.nlm.nih.gov/mesh/"},{"prefix":"Gene","uri":"https://www.ncbi.nlm.nih.gov/gene/"},{"prefix":"CVCL","uri":"https://web.expasy.org/cellosaurus/CVCL_"}],"text":"5.2. Proximity-Based Contact Tracing\nFor the purposes of this research the third floor of the CCIT building was selected for an experiment. After extracting the related metadata such as room names for the rooms from the IndoorGML, 12 Estimote Proximity beacons were spatially distributed between 12 different cell spaces. The contact tracing technique applied for this research was designed in a way that protects user privacy. The application detects the proximal appearance of users within the proximity zone of each beacon by considering the value of the Received Signal Strength Indicator (RSSI) that was broadcasted by the beacons. The duration of appearance of the user in the proximity zone defined for each beacon and the corresponding date and time information for this proximal appearance are the only information stored in the internal storage of mobile phones. Figure 8b shows a screenshot of the developed mobile application for collecting different types of observations including BeaconID, time, date, and the duration that the target user spent in the proximal zone of each beacon. Assuming that the incubation period of COVID-19 is two weeks, the application will work as a background service that saves data internally for a two-week period.\nIn situations in which the user becomes a positive COVID-19 case, he/she can voluntarily share data captured within the past two weeks with the backend database management system. An AWS product Amazon Cognito was used to control user authentication and access to data storage. As shown in Figure 8c, users are required to sign in/up for an Amazon Cognito account in order to share their information. After signing in as an authorized client, users can publish their internal information to the Amazon cloud as shown in Figure 8d. All of the data related to the COVID-19 cases will be stored and managed in the DynamoDB database in the Amazon cloud. Our developed application was connected to the DynamoDB using another AWS product, the IoT Core. When new data is added to cloud storage, the contact tracing application will look for any matches between the backend data and the data stored internally in the user device. If it finds any matches that show that a confirmed COVID-19 positive case and the target user were close to each other for more than 15 min, the application will then notify the target user about potential exposure to COVID-19 and alert cleaning staff to disinfect the place. This process is shown in Figure 9. A demo of people trajectories is shown in Supplementary Materials.\nThere are various methods for indoor positioning, such as WiFi, BLE beacons, or dead reckoning. Using BLE technology is cost-effective compared to other indoor positioning techniques, which use maintenance, installation, and cabling costs. Generally, Bluetooth devices cost ~20× less than WiFi devices and have a similar WiFi accuracy [60].\nIn this paper, we focused on BLE proximity detection for contact tracing instead of precise positioning. Three categories of user location will be of importance for this paper including immediate (less than 60 cm), near (1–6 m), and far (\u003e10 m) distance of the Bluetooth receiver from active BLE beacon. On the other hand, it was still a challenge working with BLE signals that are interfered with by structures. Indoor setting and layout have direct effects on radio waves used in Bluetooth technology. Another challenge was that the different beacon types and battery states produce different signal strengths, so using one beacon library for all types of beacons was problematic.\nIn this paper, an active BLE beacon is placed in each IndoorGML cell (e.g., room). Moreover, we focus on proximity detection (i.e., immediate (within 0.6 m away), near (within about 1–8 m), and far (is beyond 10 m) distances from the active BLE beacon) to make indoor spatiotemporal trajectories using IndoorGML cell connectivity. We avoided having to determine the exact range by way of careful beacon placement to prevent overlaps. In the context of COVID-19 spread, locating in the immediate and near distance from the infected host would be dangerous for coronavirus transmission (through droplet transmission). Accordingly, different health organizations such as WHO recommended two meters distance from others. As a result, proximity detection should be of more importance in the COVID-19 context. In other words, considering precise positioning would only increase the computation cost in this specific application. Describing an indoor location using IndoorGML graph cell also helps with privacy. Considering privacy concerns for individual tracking, especially in indoor environments, we believe that proximity positioning respects user privacy more than precise positioning.\nDepending on the size of the data, type of beacons, and network bandwidth, mobile proximity detection performance may differ. In our experiment, various beacons such as Estimote (https://estimote.com/), Accent Systems (https://accent-systems.com/) and Radius Networks (https://www.radiusnetworks.com/) have been evaluated using the developed app on the Samsung Galaxy S9 smartphone. Our results demonstrated that the app could capture a beacon’s proximity of fewer than 60 milliseconds, which is enough for our case study. The complexity of the position determination depends on the beacon software development kit; however, the complexity is O(n) in the worst-case scenario. Concerning the duration spent in a room, we detected and recorded durations of less than five seconds when walking past beacons in a corridor. Significance of time for the sake of COVID-19 risk was not considered important for durations less than 15 min, which was standard practice. So, our sampling and recording intervals were much better than was required for COVID-19 risk evaluation.\nThe mobile application publishes a JSON payload to the AWS IoT Core cloud data management system in which: Online service: A single record showing the presence of a user in the proximity of an active BLE beacon is published to the AWS IoT core.\nOffline service: An array of records showing the user’s pretenses in a time window is published to the AWS cloud.\nA JSON payload showing a single enriched proximity location captured by the developed smartphone app is shown in Supplementary Materials. For more information regarding contact tracing app can be found in [61]."}

{"project":"LitCovid-sentences","denotations":[{"id":"T294","span":{"begin":0,"end":4},"obj":"Sentence"},{"id":"T295","span":{"begin":5,"end":36},"obj":"Sentence"},{"id":"T296","span":{"begin":37,"end":139},"obj":"Sentence"},{"id":"T297","span":{"begin":140,"end":321},"obj":"Sentence"},{"id":"T298","span":{"begin":322,"end":427},"obj":"Sentence"},{"id":"T299","span":{"begin":428,"end":636},"obj":"Sentence"},{"id":"T300","span":{"begin":637,"end":872},"obj":"Sentence"},{"id":"T301","span":{"begin":873,"end":1097},"obj":"Sentence"},{"id":"T302","span":{"begin":1098,"end":1259},"obj":"Sentence"},{"id":"T303","span":{"begin":1260,"end":1439},"obj":"Sentence"},{"id":"T304","span":{"begin":1440,"end":1537},"obj":"Sentence"},{"id":"T305","span":{"begin":1538,"end":1660},"obj":"Sentence"},{"id":"T306","span":{"begin":1661,"end":1790},"obj":"Sentence"},{"id":"T307","span":{"begin":1791,"end":1909},"obj":"Sentence"},{"id":"T308","span":{"begin":1910,"end":2006},"obj":"Sentence"},{"id":"T309","span":{"begin":2007,"end":2181},"obj":"Sentence"},{"id":"T310","span":{"begin":2182,"end":2457},"obj":"Sentence"},{"id":"T311","span":{"begin":2458,"end":2492},"obj":"Sentence"},{"id":"T312","span":{"begin":2493,"end":2559},"obj":"Sentence"},{"id":"T313","span":{"begin":2560,"end":2655},"obj":"Sentence"},{"id":"T314","span":{"begin":2656,"end":2799},"obj":"Sentence"},{"id":"T315","span":{"begin":2800,"end":2900},"obj":"Sentence"},{"id":"T316","span":{"begin":2901,"end":3005},"obj":"Sentence"},{"id":"T317","span":{"begin":3006,"end":3204},"obj":"Sentence"},{"id":"T318","span":{"begin":3205,"end":3313},"obj":"Sentence"},{"id":"T319","span":{"begin":3314,"end":3404},"obj":"Sentence"},{"id":"T320","span":{"begin":3405,"end":3583},"obj":"Sentence"},{"id":"T321","span":{"begin":3584,"end":3666},"obj":"Sentence"},{"id":"T322","span":{"begin":3667,"end":3914},"obj":"Sentence"},{"id":"T323","span":{"begin":3915,"end":4017},"obj":"Sentence"},{"id":"T324","span":{"begin":4018,"end":4199},"obj":"Sentence"},{"id":"T325","span":{"begin":4200,"end":4300},"obj":"Sentence"},{"id":"T326","span":{"begin":4301,"end":4387},"obj":"Sentence"},{"id":"T327","span":{"begin":4388,"end":4506},"obj":"Sentence"},{"id":"T328","span":{"begin":4507,"end":4588},"obj":"Sentence"},{"id":"T329","span":{"begin":4589,"end":4768},"obj":"Sentence"},{"id":"T330","span":{"begin":4769,"end":4894},"obj":"Sentence"},{"id":"T331","span":{"begin":4895,"end":5151},"obj":"Sentence"},{"id":"T332","span":{"begin":5152,"end":5291},"obj":"Sentence"},{"id":"T333","span":{"begin":5292,"end":5444},"obj":"Sentence"},{"id":"T334","span":{"begin":5445,"end":5587},"obj":"Sentence"},{"id":"T335","span":{"begin":5588,"end":5728},"obj":"Sentence"},{"id":"T336","span":{"begin":5729,"end":5834},"obj":"Sentence"},{"id":"T337","span":{"begin":5835,"end":5941},"obj":"Sentence"},{"id":"T338","span":{"begin":5942,"end":5957},"obj":"Sentence"},{"id":"T339","span":{"begin":5958,"end":6079},"obj":"Sentence"},{"id":"T340","span":{"begin":6080,"end":6096},"obj":"Sentence"},{"id":"T341","span":{"begin":6097,"end":6193},"obj":"Sentence"},{"id":"T342","span":{"begin":6194,"end":6331},"obj":"Sentence"},{"id":"T343","span":{"begin":6332,"end":6404},"obj":"Sentence"}],"namespaces":[{"prefix":"_base","uri":"http://pubannotation.org/ontology/tao.owl#"}],"text":"5.2. Proximity-Based Contact Tracing\nFor the purposes of this research the third floor of the CCIT building was selected for an experiment. After extracting the related metadata such as room names for the rooms from the IndoorGML, 12 Estimote Proximity beacons were spatially distributed between 12 different cell spaces. The contact tracing technique applied for this research was designed in a way that protects user privacy. The application detects the proximal appearance of users within the proximity zone of each beacon by considering the value of the Received Signal Strength Indicator (RSSI) that was broadcasted by the beacons. The duration of appearance of the user in the proximity zone defined for each beacon and the corresponding date and time information for this proximal appearance are the only information stored in the internal storage of mobile phones. Figure 8b shows a screenshot of the developed mobile application for collecting different types of observations including BeaconID, time, date, and the duration that the target user spent in the proximal zone of each beacon. Assuming that the incubation period of COVID-19 is two weeks, the application will work as a background service that saves data internally for a two-week period.\nIn situations in which the user becomes a positive COVID-19 case, he/she can voluntarily share data captured within the past two weeks with the backend database management system. An AWS product Amazon Cognito was used to control user authentication and access to data storage. As shown in Figure 8c, users are required to sign in/up for an Amazon Cognito account in order to share their information. After signing in as an authorized client, users can publish their internal information to the Amazon cloud as shown in Figure 8d. All of the data related to the COVID-19 cases will be stored and managed in the DynamoDB database in the Amazon cloud. Our developed application was connected to the DynamoDB using another AWS product, the IoT Core. When new data is added to cloud storage, the contact tracing application will look for any matches between the backend data and the data stored internally in the user device. If it finds any matches that show that a confirmed COVID-19 positive case and the target user were close to each other for more than 15 min, the application will then notify the target user about potential exposure to COVID-19 and alert cleaning staff to disinfect the place. This process is shown in Figure 9. A demo of people trajectories is shown in Supplementary Materials.\nThere are various methods for indoor positioning, such as WiFi, BLE beacons, or dead reckoning. Using BLE technology is cost-effective compared to other indoor positioning techniques, which use maintenance, installation, and cabling costs. Generally, Bluetooth devices cost ~20× less than WiFi devices and have a similar WiFi accuracy [60].\nIn this paper, we focused on BLE proximity detection for contact tracing instead of precise positioning. Three categories of user location will be of importance for this paper including immediate (less than 60 cm), near (1–6 m), and far (\u003e10 m) distance of the Bluetooth receiver from active BLE beacon. On the other hand, it was still a challenge working with BLE signals that are interfered with by structures. Indoor setting and layout have direct effects on radio waves used in Bluetooth technology. Another challenge was that the different beacon types and battery states produce different signal strengths, so using one beacon library for all types of beacons was problematic.\nIn this paper, an active BLE beacon is placed in each IndoorGML cell (e.g., room). Moreover, we focus on proximity detection (i.e., immediate (within 0.6 m away), near (within about 1–8 m), and far (is beyond 10 m) distances from the active BLE beacon) to make indoor spatiotemporal trajectories using IndoorGML cell connectivity. We avoided having to determine the exact range by way of careful beacon placement to prevent overlaps. In the context of COVID-19 spread, locating in the immediate and near distance from the infected host would be dangerous for coronavirus transmission (through droplet transmission). Accordingly, different health organizations such as WHO recommended two meters distance from others. As a result, proximity detection should be of more importance in the COVID-19 context. In other words, considering precise positioning would only increase the computation cost in this specific application. Describing an indoor location using IndoorGML graph cell also helps with privacy. Considering privacy concerns for individual tracking, especially in indoor environments, we believe that proximity positioning respects user privacy more than precise positioning.\nDepending on the size of the data, type of beacons, and network bandwidth, mobile proximity detection performance may differ. In our experiment, various beacons such as Estimote (https://estimote.com/), Accent Systems (https://accent-systems.com/) and Radius Networks (https://www.radiusnetworks.com/) have been evaluated using the developed app on the Samsung Galaxy S9 smartphone. Our results demonstrated that the app could capture a beacon’s proximity of fewer than 60 milliseconds, which is enough for our case study. The complexity of the position determination depends on the beacon software development kit; however, the complexity is O(n) in the worst-case scenario. Concerning the duration spent in a room, we detected and recorded durations of less than five seconds when walking past beacons in a corridor. Significance of time for the sake of COVID-19 risk was not considered important for durations less than 15 min, which was standard practice. So, our sampling and recording intervals were much better than was required for COVID-19 risk evaluation.\nThe mobile application publishes a JSON payload to the AWS IoT Core cloud data management system in which: Online service: A single record showing the presence of a user in the proximity of an active BLE beacon is published to the AWS IoT core.\nOffline service: An array of records showing the user’s pretenses in a time window is published to the AWS cloud.\nA JSON payload showing a single enriched proximity location captured by the developed smartphone app is shown in Supplementary Materials. For more information regarding contact tracing app can be found in [61]."}