A geo-located web service is a web service that is offered in a particular geographical region or area. In the execution phase, a geo-located web service uses the mobile position to deliver a service. For example, a geo-located web service could be an emergency application which informs the police or firefighter administration of a particular region about the location of a car accident, using the driver's mobile phone position. In next generation (third and up generation) of mobile networks, to obtain the mobile position, a geo-located web service will interact with the position or LoCation Services (LCS) server of a mobile network operator.;A geo-located web service generates a maintainability problem of a service execution when a mobile client moves to a location area where the service is no longer offered by the SAS in execution.;This thesis proposes a new middleware system called Geo-Located Web Services Architecture (GLWSA) which extends the UDDI (Universal Description, Discovery, and Integration) registry and the MLP (Mobile Location Protocol) by adding the GLWSA topology and the factorized thematic location methods, respectively. We built a new mechanism that collects the network bandwidth and the utilization factor of a server application, maintains the consistency of collected data and uses them in the selection and the migration criteria of the SAS server. For a specific service, the network bandwidth and SAS utilization factor are collected periodically in a particular GLWSM (Geo-Located Web Services Manager) domain by sending a collect traffic message to ail SAS that offer the concerned service in this domain. Then, each SAS sends a bandwidth quotation message to the MAP (Mobile Anchor Point) of the GLWSM domain in order to get the bandwidth traffic and determines the SAS processor rate. The proposed mechanism aims to select application servers with dynamic QoS parameters (network bandwidth, server utilization factor). The main objective of the GLWSA is to propose a distributed geo-located web services discovery system that allows to maintain a service execution closest to the location context of a mobile client.;Results show that the suggested GLWSA system offers an adequate architecture to discover the geo-located Web services, to coordinate the migration of service to the nearest applications server and to locate thematically the mobile clients. It makes it possible to lookup a geo-located Web service with an average RTT (Round Time Trip) of 28 milliseconds (for a geo-located Web service without QoS) and 41 milliseconds (for a geo-located Web service with QoS). The performances of the coordination of the migration without or with quality of service are satisfactory because in both cases 98% of measurements of the average RTT of coordination respects the time on the constraint of coordination of migration (either less than or equal to 30 milliseconds). We also show that the mechanism of collection and propagation of the QoS data in GLWSA system is consistent compared to other systems also carrying out the collection of the dynamic QoS data (for example, the bandwidth). The results obtained show that the thematic location suggested offers a substantial gain in time compared to the ordinary location of a group of mobiles. (Abstract shortened by UMI.).;By referring to the mobile network specifications, the geo-located web services will be deployed on the next generation mobile networks. Then, it will be possible to a Supplier Application Server (SAS) to get the location or geographical position of a mobile client. In this point of view, an SAS is considered as a set of web services that requ ire the client position to deliver the service.
展开▼
