神戸大学
>
大学院システム情報学研究科
>
計算科学基礎講座 計算知能
Research/異種位置情報サービスを連携するための統一的アプローチ
をテンプレートにして作成
開始行:
[[Research/SOA]]
* Background [#f34b78a5]
Smart combination of IoT, positioning systems and cloud
services enables a sophisticated platform to acquire and ...
smartphone is equipped with GPS. Also, various GPS module...
inside buildings or underground, where GPS cannot cover.
The enabling technologies of IPS include Wi-Fi, Bluetooth...
(PDR), IMES. Gathering such indoor/outdoor location infor...
of location-based services and applications.
The location information gathered in the cloud should be
provided as a service, so that client applications can ea...
consume the locations based on standard Web service proto...
paper. In fact, several practical services come onto mark...
IndoorAtlas. Although features and operation policies var...
the cloud for exchanging or sharing location information ...
* Challenge [#i4476e6d]
In general, there is no compatibility among different loc...
and operated. Each service is tightly coupled with the un...
to use GPS information collected by smartphones, while In...
a building. Thus, Glympse cannot directly use the data
of IndoorAtlas, and vice versa. In order to cover both in...
two services. However, the lack of compatibility forces the
application developer to use different API, and to perform
expensive data integration within the application.
Figure 1 shows the conventional architecture to integrate
the existing locating services. Let us assume an applicat...
say “where-are-you?”, with which a user A tries to find l...
either indoor or outdoor space, and is located by a certain
locating service. When A executes a query “Where is B?”,
the application has to invoke all possible locating servi...
to find B. Although the query “Where is B?” is essentially
simple, the application has to know how to invoke API and
interpret the result for every locating service. This makes
the application complex, low-performance, and non-scalable.
#ref(kulocs1.png,nolink,30%);
* Purpose and Approach [#o4bdc7eb]
To cope with the problem, in this paper, we propose a uni...
the existing heterogeneous locating services, and provide...
abstraction layer between the applications and the locating
services. To make location queries compatible among many
locating services, we design KULOCS with three technology-
independent elements [when], [where] and [who].
Based on the three elements, KULOCS integrates data
and operations of the heterogeneous locating services. In
the data integration, we propose a method that different
representation of time, heterogeneous locations and diffe...
namespace of users are consolidated by Unix time, location
labels and alias table, respectively. The location labels...
coordinates of IPS and GPS, respectively. A user of KULOC...
internally converts the label to specific representation ...
individual locating services.
For the operation integration, we propose KULOCS-API,
which integrates heterogeneous operations by possible com...
“Where is B?” of “where-are-you?” is simply implemented
by http://kulocs/where?user=B&time=now. For this, the
application needs not to know how B is located by which
service. Thus, the application can consume location infor...
#ref(kulocs2.png,nolink,30%);
終了行:
[[Research/SOA]]
* Background [#f34b78a5]
Smart combination of IoT, positioning systems and cloud
services enables a sophisticated platform to acquire and ...
smartphone is equipped with GPS. Also, various GPS module...
inside buildings or underground, where GPS cannot cover.
The enabling technologies of IPS include Wi-Fi, Bluetooth...
(PDR), IMES. Gathering such indoor/outdoor location infor...
of location-based services and applications.
The location information gathered in the cloud should be
provided as a service, so that client applications can ea...
consume the locations based on standard Web service proto...
paper. In fact, several practical services come onto mark...
IndoorAtlas. Although features and operation policies var...
the cloud for exchanging or sharing location information ...
* Challenge [#i4476e6d]
In general, there is no compatibility among different loc...
and operated. Each service is tightly coupled with the un...
to use GPS information collected by smartphones, while In...
a building. Thus, Glympse cannot directly use the data
of IndoorAtlas, and vice versa. In order to cover both in...
two services. However, the lack of compatibility forces the
application developer to use different API, and to perform
expensive data integration within the application.
Figure 1 shows the conventional architecture to integrate
the existing locating services. Let us assume an applicat...
say “where-are-you?”, with which a user A tries to find l...
either indoor or outdoor space, and is located by a certain
locating service. When A executes a query “Where is B?”,
the application has to invoke all possible locating servi...
to find B. Although the query “Where is B?” is essentially
simple, the application has to know how to invoke API and
interpret the result for every locating service. This makes
the application complex, low-performance, and non-scalable.
#ref(kulocs1.png,nolink,30%);
* Purpose and Approach [#o4bdc7eb]
To cope with the problem, in this paper, we propose a uni...
the existing heterogeneous locating services, and provide...
abstraction layer between the applications and the locating
services. To make location queries compatible among many
locating services, we design KULOCS with three technology-
independent elements [when], [where] and [who].
Based on the three elements, KULOCS integrates data
and operations of the heterogeneous locating services. In
the data integration, we propose a method that different
representation of time, heterogeneous locations and diffe...
namespace of users are consolidated by Unix time, location
labels and alias table, respectively. The location labels...
coordinates of IPS and GPS, respectively. A user of KULOC...
internally converts the label to specific representation ...
individual locating services.
For the operation integration, we propose KULOCS-API,
which integrates heterogeneous operations by possible com...
“Where is B?” of “where-are-you?” is simply implemented
by http://kulocs/where?user=B&time=now. For this, the
application needs not to know how B is located by which
service. Thus, the application can consume location infor...
#ref(kulocs2.png,nolink,30%);
ページ名:
![[PukiWiki]](image/cs27logo5.png "[PukiWiki]")
