WO2003081391A2 - Location based service provider - Google Patents
Location based service provider Download PDFInfo
- Publication number
- WO2003081391A2 WO2003081391A2 PCT/US2003/008628 US0308628W WO03081391A2 WO 2003081391 A2 WO2003081391 A2 WO 2003081391A2 US 0308628 W US0308628 W US 0308628W WO 03081391 A2 WO03081391 A2 WO 03081391A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service
- location
- request
- user
- server
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/52—Network services specially adapted for the location of the user terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
- H04L67/306—User profiles
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9537—Spatial or temporal dependent retrieval, e.g. spatiotemporal queries
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
- H04W4/029—Location-based management or tracking services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
Definitions
- the present invention pertains generally to the field of location-based information systems.
- GPS Global Positioning Systems
- GPS utilizes signals transmitted by a number of in- view satellites to determine the location of a GPS antenna which is connected to a receiver.
- Each GPS satellite transmits two coded L-band carrier signals which enable some compensation for propagation delays through the ionosphere.
- Each GPS receiver contains an almanac of data describing the satellite orbits and uses ephemeris corrections transmitted by the satellites themselves. Satellite to antenna distances may be deduced from time code or carrier phase differences determined by comparing the received signals with locally generated receiver signals. These distances are then used to determine antenna position. Only those satellites which are sufficiently above the horizon can contribute to a position measurement, the accuracy of which depends on various factors including the geometrical arrangement of the satellites at the time when the distances are determined.
- Locations may be specified by various means, both actual and representational, including geocodes, centroids, and street vectors/segments. These and other terms are used by various technologies to provide systems and methods for delivering spatially-dependent services.
- a geocode is a specification of a position using a suitable coordinate system and at a granularity that is sufficient for a particular application. For example, a geocode specifying a latitude and a longitude specifies a position on the surface of the earth. A geocode may also specify a height above the surface of the earth. A geocode encompasses providing spatial information in a form other than specifying the longitude and the latitude. Other examples of geocodes include postal centroids that are associated with areas sharing a common zip code. A centroid is a geographic center of an entire area, region, boundary, etc. for which the specific geographic area covers. A familiar example is the association between a centroid and a postal code, such as the ZIP codes defined and used by the United States Postal Service.
- Street vectors are address ranges assigned to segments of individual streets.
- Street vectors assist in displaying digitized computer-based street maps. Often, street vectors appear as left and right side address ranges, and may be also used for geocoding a particular address to a particular street segment.
- geocodmg is the act, method or process of assigning x and y coordinates (usually but not limited to latitude and longitude) to records, lists and files containing location information (full addresses, partial addresses, zip codes, census FIPS codes, etc.) for cartographic or any other form of spatial analysis or reference.
- Geocoding encompasses assigning spatial parameters to data to visualize information and exploring relationships based on spatial distribution. Some examples include census data or survey data that identify the residences of individuals with a particular income bracket, ethnicity, political affiliations, employment, and the like.
- Geocoding is often performed by running ungeocoded (referred to hereafter as “raw data”) information such as a list of customers through software and/or data which performs table lookup, fuzzy logic and address matching against an entire “library” of all known or available addresses (referred to hereafter as “georeferenced library”) with associated x,y location coordinates.
- raw data running ungeocoded
- fuzzy logic performing fuzzy logic and address matching against an entire "library” of all known or available addresses
- a georeferenced library may be compiled from a number of varied sources including US Census address information and US postal address information, along with Zip Code boundaries and other various sources of data containing geographic information and/or location geometry. If a raw data address cannot be matched exactly to a specific library street address (known as a "street level hit"), then an attempt may be made to match the raw data address to geographic hierarchy of point, line or region geography of ever decreasing precision until a predetermined tolerance for an acceptable match is met. The geographic hierarchy to which a raw data record is finally assigned is also known as the "geocoding precision.” Geocoding precision tells how closely the location assigned by the geocoding software matches the true location of the raw data. Geocoding technology generally provides for two main types of precision: street level and postal ZIP centroid.
- Street level precision is the placement of geocoded records at the street address. Street level precision attempts to geocode all records to the actual street address. In all likelihood, some matches may end up at a less precise location such as a ZIP centroid (ZIP+4, ZIP+2, or ZIP code) or shape path (the shape of a street as defined by points that make up each segment of the street.
- ZIP centroid ZIP+4, ZIP+2, or ZIP code
- shape path the shape of a street as defined by points that make up each segment of the street.
- interface is commonly used in describing software and devices.
- the term “interface” differs from a "user interface” in that a user interface is a presentation made to a user offering various choices, information, and operable elements such as buttons, knobs, and the like.
- a user interface may include physical components as well as transient displayed information.
- An interface in contrast, in the context of object oriented ("OO") languages represents methods that are supported either by the interface itself in some OO languages, or provided in the interface as abstract methods which are provided by classes implementing the interface.
- OO object oriented
- a familiar example of the latter kind of OO paradigms is JAVA, which allows platform independent coding of software.
- a method and system are disclosed for providing extensible or stand-alone location enabled services.
- the disclosed method and system provide services that may also utilize the internet using an extensible Markup Language Application Interface (XML- API).
- XML- API extensible Markup Language Application Interface
- These services enable a collection of applications to manage information specific to mobile locations, provide services, including real-time services, with complete or partial integration via a common service manager.
- the XML- API forms a platform that ties together the key services commonly used in the development of these mobile location applications.
- mobile location is integrated with other location sensitive data, such as maps or demographics of a particular region or the location of businesses and consumers to enable a richer service offering for customers of wireless carriers and service providers.
- Examples of such services may include obtaining one or more routes between a starting point and a destination; providing a geocode corresponding to an address; providing an address corresponding to a geocode; providing maps as image files encompassing specified geocodes, locations, or addresses; obtaining a position for a mobile device; obtaining the identity of a location; obtaining one or more geographic features near a location; managing person profile data; providing a map corresponding to a location; providing a coordinate geometry service for carrying out geometric calculations and measurements; performing coordinate transfonnations; providing traffic related info nation; generating enterprise specific maps; and providing an enterprise profile.
- the illustrative embodiments disclose integration of the various services, they may be offered at various levels of granularity down to offering stand-alone services or any combination of services.
- FIGURE 1 is an illustration of an exemplary context for providing an integrated location-based service platform.
- FIGURE 2 is a schematic representation of an integrated location-based service platform.
- FIGURE 3 is an illustration of various interactions at a service manager in the course of providing services via an integrated location-based service platform.
- FIGURE 4 is an illustration of an integrated location-based service platform along with the various service provider modules, spatial servers accessed by the service provider modules, third party servers and data repositories used to respond to service requests.
- FIGURE 5 is an illustration of an integrated location-based service platform for providing location based services that integrate the London subway with vehicular traffic routes and pedestrian traffic routes.
- FIGURE 6 is an illustrative embodiment of the present invention that includes a communication system comprising a central server and a peer-to-peer location- based information system.
- FIGURE 7 is an illustration of the interactions between a mobile user and a peer-to-peer system for providing location based services.
- FIGURE 8 further illustrates interactions between a client and an integrated location-based service platform performing multiple functions
- FIGURE 9 illustrates storage of sale and authorization information in a location based system that allows secure access and public access with more limited privileges.
- FIGURE 10 is a flow chart indicating the actions available to a store administrator.
- FIGURE 11 is a flow chart indicating the actions available to a user who has been provided with a list of local-content servers.
- FIGURE 12 shows the Java panels conesponding to the various steps described in FIGURE 11.
- FIGURE 13 shows a user interface viewed by a user upon starting a mall and store browsing application on his mobile device.
- FIGURE 14 shows a user interface displaying a list of local-content servers serving the user's location.
- FIGURE 15 shows a user interface that allows the user to indicate whether the user wishes to enter a store name, or to select a store by specifying a product.
- FIGURE 16 shows a user interface that allows the user to indicate whether the user wishes to enter a product name, or to select a product by category.
- FIGURE 17 shows a user interface displaying categories of items for which a mall-server contains sale information.
- FIGURE 18 shows a user interface displaying a list of stores having sale items in a mall-server database in the category selected by the user.
- FIGURE 19 shows a user interface displaying sale items in a local-content server database for the specific store.
- FIGURE 20 shows a user interface displaying information about a sale item selected by the user.
- FIGURE 21 shows a user interface displaying a map showing the location of a store relative to the user.
- FIGURE 22 shows a user interface displaying a map zoomed-in to show the store location in more detail.
- FIGURE 23 illustrates an exemplary architecture for an embodiment of the location sensitive event service.
- FIGURE 24 provides another illustration of an architecture providing a location sensitive event service.
- FIGURE 25 summarizes an illustrative process for generating ordered lists of events conesponding to user profiles.
- a method and system for providing one or more location-based services with the aid of a markup language based interface with one or more service managers and access to one or more databases is disclosed.
- the method and system are typically, but not as a requirement for practicing the invention, implemented via at least one server, possibly in the form of a servlet, and a database that in combination with specified location information, enables delivery of customized services, options, and offers to customers.
- the method and system extend the advances made in determination of location of mobile users to offer customized location-based services.
- these services also integrate, when desirable, demographic data to generate services suited to various demographic segments and markets. Such demographic data includes user preferences, geographical distribution of users, mobility patterns and the like.
- the method and system of the present invention leverage wired and/or wireless connectivity, including that over the Internet, to provide services of interest to consumers.
- a prefened embodiment of the present invention includes providing an integrated location-based service platform, an example of which is the miAwareTM set of services provided by the Maplnfo® Corporation of Troy, NY as part of its Mobile Location Services (MLS).
- miAwareTM includes an XML based API that enables both implementation and efficient communication of various requests and responses as described at, milocate.mapinfo.com/miAware/, a copy of which, dated March 19, 2003, is attached as APPENDIX to this application.
- Such an integrated location-based service platform for instance, the miAwareTM, provided by the Maplnfo® Corporation of Troy, NY, provides numerous services and facilities including providing a route to a target, finding a nearest specified type of target, geocoding, geodecoding, and determining a mobile position service for a person with a mobile device such as a GPS or cell phone and the like. These services are accessed via user interfaces and underlying XML APIs.
- FIGURE 1 illustrates a typical context for providing an integrated location-based service platform.
- Users 100 including mobile users, access via antenna 105 gateway 110 and location server 115.
- Location server 115 may further connect to the Internet 120 or to portal platform 125 to provide an integrated location-based service platform.
- FIGURE 2 illustrates a schematic representation of an integrated location- based service platform.
- Client requests 200 are directed to service manager 205, which is in contact with a service catalogue 210 containing a description of various services available via service manager 205.
- the service catalogue is preferably in the form of document-type definitions ("DTD") or a schema (e.g., specified under the OpenLS standard), or any other suitable format specifying the form of requests and responses for obtaining a particular service.
- DTD document-type definitions
- schema e.g., specified under the OpenLS standard
- requests are sent encoded in a markup language such as XML. Such use of a markup language allows a large number of interfaces to be provided to a variety of services at a common portal, service manager 205.
- communications by various services 215, as part of service provider level 220, with service manager 205 are also encoded in a markup language in accordance with a DTD specification that requires support for resource management and methods for starting and terminating a particular module with support for multi-threading.
- This enables a service to register itself with service manager 205 and publish itself to service catalogue 225, where it may be discovered, along with the syntax for service requests directed to the service, by client requests directed to the service catalogue 225.
- This architecture makes the integrated location-based service platform flexible since various different services may be added or removed from the integrated location-based service platform to provide customized services. With the ease of adding new services or terminating existing services, the integrated location-based service platform provides a common platform for accessing a variety of location-based services. It should be noted that many of the services accessed through service manger 205 may also be provided as stand alone services, possibly concunently with providing access via service manager 205.
- FIGURE 3 provides an illustration of various interactions at a service manager in the course of providing services via an integrated location-based service platform.
- Service request 305 elicits service response 310 to client 300.
- service request 305 and response 310 may be transmitted via a network, such as Internet 315, to service manager 320.
- Service manager 320 has integrated location-based service platform configuration information 325, as well as information about the various available services in service catalogue 330.
- service manager 320 In response to receiving service request 305, service manager 320 generates service object 335, which is directed to service provider interface 340 specified in service request 305.
- Service response object 345 generated by the service provider via service provider interface 340 is sent to service manager 320, which in turn, generates service response 310 directed to client 300.
- FIGURE 4 illustrates an integrated location-based service platform along with various service provider modules, spatial servers accessed by the service provider modules, third party servers and data repositories used to respond to service requests.
- Request 400 from client 405 is received at integrated location-based service platform server 410 via service provider interface 415.
- Service provider interface 415 directs request 400 to one of service modules providing services for positioning 420, coordinate system transformation 425, position refinement 430, finding location 435, geodecoding 440, profiling 445, geocoding 450, Cogo 455 (coordinate geometry service), finding nearest geographical of interest 460, mapping 465, routing 470, and administration 475.
- service modules position refinement 430, finding location 435, geodecoding 440, finding nearest geographical of interest 460, and mapping 465 communicate with spatial server 480, which may be a MapXtreme® Server provided by Maplnfo® Corporation, accessing in turn relational database 482.
- routing 470 accesses routing server 485 while geocoding 450 accesses spatial server 490, which may be a MapMarker® Server provided by Maplnfo® Corporation.
- modules for profiling 445 access third party directory server 492, which, in turn, accesses LDAP 494, while positioning 420 accesses third party location server 496.
- the result sent by one or more of the various service modules is used to generate response 498 to request 400.
- response 498 may integrate information from more than one service module.
- the present invention encompasses a system including: a routing module that receives and routes requests to an appropriate response module; a plurality of response modules registered with the routing module for responding to different types of requests; a plurality of spatial servers from which the response modules retrieve spatial information to be used in responding to the requests; and an interface for adding response modules to the system.
- the interface further includes methods for publication of information regarding the response module to the service manager, also refened to as the routing module, including information required for starting or tenriinatiiig a particular response module, and methods to allocate or deallocate resources.
- the system of the present invention further encompasses: a servlet within a platform independent implementation (JAVA).
- the servlet is in communication with a service catalog to determine or update available services/response modules and a user profile and geographic database.
- the servlet also provides support for one or more of HTTP/POST, XML, and SOAP, while being adapted to forward requests to a registered response module, which module, in turn, receives spatial information from a spatial server, and sends results to the routing manager for generation of the response to the request.
- the system of the present invention also encompasses the functionality of a response sent to a different address than the address from which the request was received.
- the system of the present invention further encompasses a plurality of spatial servers that may include one or more of: a routing server (Routing J ServerTM) for obtaining one or more routes between a starting point and a destination; a geocoding server (e.g., MapMarker J ServerTM) for providing geocodes conesponding to an address; a geodecoding server (e.g., MapMarker J ServerTM) for providing an address conesponding to a geocode; and a mapping server (MapXtreme serverTM) for providing maps as image files encompassing specified geocodes, locations, or addresses.
- a routing server (Routing J ServerTM) for obtaining one or more routes between a starting point and a destination
- a geocoding server e.g., MapMarker J ServerTM
- MapMarker J ServerTM geodecoding server
- MapXtreme serverTM MapXtreme server
- the system of the present invention also encompasses at least one service module comprising: an interface for receiving a request; an interface for generating a response to the request; and an interface for initializing and shutting down the service module.
- Embodiments of the system of the present invention may also encompass services such as obtaining one or more records containing a geocode conesponding to an address; obtaining an address conesponding to a geocode; obtaining a route to a destination; obtaining a position for a mobile device; obtaining the identity of a location; obtaining one or more geographic features near a location; and a person profile data; providing a map conesponding to a location; a coordinate geometry service for carrying out geometric calculations and measurements; performing coordinate transformations; providing traffic related information; generating enterprise specific maps; and providing an enterprise profile.
- services such as obtaining one or more records containing a geocode conesponding to an address; obtaining an address conesponding to a geocode; obtaining a route to a destination; obtaining a position for a mobile device; obtaining the identity of a location; obtaining one or more geographic features near a location; and a person profile data; providing a map conesponding to a location; a coordinate geometry service
- Embodiments of the system of the present invention may also encompass
- Pass-Thru Service refers to a service provider creating a service request specification that contains a request of another service or server (typically encoded in XML as well).
- the Pass-Thru Service facility extracts a request content (or payload) from the request document in the original request envelope, passes this payload to another server (third-party server) that accepts the XML request, processes the payload, and wraps the response payload back into an envelope for returning the response document.
- the integrated location-based service platform, or its modules may not only receive requests, it may also make requests and process the response thereto.
- FIGURE 5 illustrates an example of an integrated location-based service platform for providing routing information in London, U.K.
- the integrated location- based service platform preferably comprises service manager 500, which receives requests 502 from user 504.
- User 504 may request a route that could include walking, driving and subway legs for providing the lowest cost, shortest distance, and/or shortest time or other specifications. Alternatively, a default specification may be provided to the user.
- User 504 sends request 502 via interface 506, which allows additional requests to be sent as well.
- Interface 506 is extensible and includes tube (i.e., subway) interface 508 for communicating with tube service 510 underlying service manager 500. Extensibility denotes providing interfaces to allow anyone including third parties to extend the functionality of the system.
- a subway routing module for a city may be added without the need for express integration for incorporating the functionality directly into the routing modules. It is prefened that such modules are registered only following an authentication or a limited gate-keeping step to ensure that the module provider is trusted, as well as retain a measure of control over potential providers of service modules. To the user, the added functionality appears seamlessly integrated.
- Service manager 500 sends a request object 512 to tube schedule service 514, which is part of service providers 516.
- Tube schedule service 514 requests information from tube map server 518, which is one of the spatial servers 520, and receives information 522 in response thereto. This information enables service provider modules 516, such as tube schedule service 514 to generate response object 524 for service manager 500 in response to processing request 502.
- Service manager 500 in turn, generates response document 526 for sending to user 504 via interface 506.
- FIGURE 5 also illustrates that service providers 516 (response modules) may provide various services that may have security components as well.
- a service provider providing security or personal profile information may provide permissions that enable all users to (1) access one or more of all applications; (2) access some services by way of some applications only; (3) allow specified user to access specified services; or (4) characterize the profile of an enterprise.
- the wireless carrier may provide additional services through intuitive and automated interfaces that allow a user to advertise event such as a garage sale.
- This service is enhanced in value by the smooth integration of the functionality for providing directions from existing modules integrated via the with directions to the garage sale generated in a customized fashion for individual users, such as user 504, based on use of the tube, walking and/or driving.
- User 504 may be provided information, for instance that regarding the garage sale, in response to detecting user 504 via LAN/WiFi 530. Such detection triggers, preferably with the consent of the user, the obtaining of profile and preference information for user 504 over a secure Wide Area Network (WAN) 540.
- WAN Wide Area Network
- user 504 may be presented with a choice of or information about malls and supplier stores 550 in the vicinity, along with directions to a supplier store from a location of user 504. All of these activities are preferably carried out automatically, thus integrating user 504 with the sunoundings.
- the choice of mall stores may be provided by a wireless carrier along with information about a garage sale in the vicinity.
- WiFi is not necessary for accessing information about a garage sale or a store in a shopping mall.
- Such information could be provided by way of local data going back through the carrier to the device being carried by the end user.
- the connection is still preferably point-to-point in the sense that a handoff request is given to the system(s) to hold the mall information even if the mall returns it back to the carrier for delivery rather than delivering it directly.
- Garage sale advertising functionality may interact with a carrier in a similar way.
- the wireless provider brokers an arrangement with a person wishing to hold a garage sale and the person wishing to have the garage sale (or any other similar activity) provides the details for the garage sale by interacting through an interface managed by the carrier or other agent without any need for direct intervention by the carrier or other agent. In some embodiments there may not even be a charge for such a service, but likely there will be a charge if that matters.
- the party advertising the garage sale provides an address for where the garage sale is being held, the canier or other agent knows the location of the sale and can therefore provide the end user wishing to know about any sales in the vicinity of the end user.
- the actual details about the selected sales are then delivered preferably in response to a user request.
- WiFi functionality is likely to be used if a user were looking for a sale rather than push sales related information to a user.
- mobile users for instance, moving in a vehicle or walking through a neighbourhood, are sensed via carrier detection and interaction.
- the provider of the 'sale' or any event in general may provide advertisement and notice of the event along with directions and other sophisticated functions without the need of any programmer by merely using a friendly user-interface to guide them through the setting up of such a service to make their local event detectable through the carrier or other agent.
- the present invention comprises stand-alone services that may be provided by stand-alone service providers or by service providers that may be accessed both through an integrated location-based service platform and directly.
- An example is provided by a peer-to-peer location-based information system (LBS) in which locally relevant information may be maintained by local entities, such as local businesses.
- LBS peer-to-peer location-based information system
- the present invention comprises a combination of location-based service and personalization, in which locally- and personally-relevant information is automatically provided to users based on their location and previously-stored personalization information.
- the peer-to-peer aspect and the personalized localization aspects are combined into a single system.
- a central server maintains personalization information in the form of a customer profile, and maintains a list of servers providing locally relevant information, and automatically refers the user to a server providing information relevant to the user's location.
- the profile is used to refer the user only to information that matches the user's profile, and/or to provide the server providing locally relevant information with the ability to personalize the information for the user.
- the present system and method comprise a site adapted to host one or more location-based services.
- a Service Provider Java API is preferably provided, which is a set of Java interfaces and classes for development of new services. New services can be deployed to the existing set of services hosted by a the site. Once deployed, services may be accessed from the outside world.
- a service provider In order to deploy a new service, a service provider preferably implements three main interfaces: ServiceProvider, ServiceRequest, and ServiceResponse.
- ServiceProvider is the main interface to a provider.
- a ServiceProperties object is passed into the provider so configuration information specified in the Service Catalog can be utilized. Since initialisation is only a one time operation, global information necessary for performing service requests in a multi-threaded environment should be cached.
- the provider At shutdown, the provider preferably de-allocates resources so to avoid memory leakage and/or holding up unnecessary resources (e.g. database connections). These tasks are performed by methods such as init(), shutdownQ, getServiceRequestO, and perform().
- the ServiceRequest contains parsed information of a request document.
- the provider creates the ServiceRequest object based on the input request document.
- This object parses the content of the document and provides information for rendering a request.
- the ServiceRequest is passed into the provider at a later stage for carrying out the service request.
- Implementation of this interface also provides capability to create request document conformaning to a suitable DTD, such as the miAwareServiceRequest DTD, which includes specifications for methods (e.g. setDistanceUnit() of the RouteRequest object) that are available for filling the content of this document including setters & getters toXMLdocument().
- a ServiceResponse object contains results of a service request and is returned after a service is rendered. This object also provides methods for publishing its content to a XML document conforming to the miAwareServiceResponse DTD. In addition, this object is also able to parse its own response XML document and provides "get" methods (e.g. getTotalTime() of the RouteResponseQ object) for retrieving the content.
- get e.g. getTotalTime() of the RouteResponseQ object
- a client Java API which comprises a set of helper classes grouped by services, which assist Java application developers to publish service requests and retrieve information from a response document.
- the client is super thin due to no dependency on core software.
- the client needs W3C compliant SAX/DOM parsers (which are provided by many entities such as Sun®, Oracle®, IBM®, etc).
- These messages are encoded in a markup language, and include a location of interest and a plurality of nested tags, preferably conforming to the XML specification, such that the message comprising an outer tag indicates a first service.
- the inner tag is associated with a plurality of attributes for processing the request so that at a user interface (supported in a thin client) one or more fields conesponding to the plurality of attributes are presented to receive data for providing the first service or the result of a service request.
- the location of interest may be provided by many different means, such as user input, a base station location signal, an address, a geocode, two or more base station signals detected by a mobile phone, and two or more GPS signals.
- a part of the request is forwarded to a service provider module by using the nested tag structure.
- the tags conespond to requests for services such as routes to a specified destination, a list of local servers for obtaining local information, an ordered list of events, a list of products or services, a location, a map, a list of nearest geographical features, transformed coordinates, an event matching service, a traffic monitoring service, a peer-to-peer communication shopping service, a user profile service, and a location aware service.
- the attributes provide data for an address, authenticating information, personal preference information, event description, a route, geographically accessible locations, product description, traffic conditions, weather conditions, a map, and coordinates transformation.
- a central LBS server in the peer- to-peer system maintains a database of local-content servers (peers) providing locally relevant information that is spatially indexed so as to permit the network addresses of the local-content servers to be resolved based on a provided indication of the location of a user.
- a database may include records indicating categories of content available from at least a portion of the servers.
- the LBS server When a user of a mobile device accesses the system of the present invention by running a client program for interacting with the LBS server, the LBS server is provided with an indication of the user's geographic location.
- the client system may comprise a cellular telephone comprising a location determination system such as GPS or any mobile positioning technology, and Java.
- the LBS server uses the indication of the user's geographic location to query the database for local-content servers providing information or services relevant to the area of the user's geographic location. If the results include only one local-content server, the user is preferably re-directed to the local-content server. If the results include more than one local-content server, the user is preferably provided with a list of links to local-content servers.
- the LBS server may not include information about the content or services provided by the local-content servers, thus avoiding the need for updates when the content or services provided by local-content servers are updated.
- the LBS server database includes records indicating the categories of content or services provided by at least a portion of the local-content servers.
- the information and/or services provided by local-content servers are preferably maintained by entities, such as businesses, that also provide goods and/or services through facilities physically located near the geographic locations for which the local-content servers provide information and/or services. There is no requirement for the local-content servers to be physically located in or near geographic areas for which the local-content servers provide information and/or services.
- local-content servers are maintained locally by area organizations, such as shopping malls, and may be accessed by local-content providers, such as stores within the shopping mall.
- wireless access is provided for maintenance by local-content providers.
- Personalization services may be provided by the LBS server, or by the local- content servers, or both, hi a prefened embodiment, personalization services are provided by local-content servers, which act upon infonnation provided from a customer profile maintained by the LBS server operator. In this way, only personally relevant local content is provided to the user.
- personalization services are preferably provided by Maplnfo® Corporation's miAwareTM profile module. Servers running Maph ⁇ fo®'s miAwareTM also preferably provide LBS services and local-content services.
- An illustrative embodiment of the present invention includes a communication system comprising a central LBS server, a plurality of local-content servers called, a central database (repository) attached to the central LBS server containing one or more URL of each local-content server, a plurality of local-content databases (repositories) attached to each local-content server, and a map server.
- Each local-content database preferably comprises product and sales information of stores in a shopping mall.
- Each central LBS server and local-content server may, for instance, be implemented as an Apache Tomcat web server with Java Servlets with the databases or repository being an Oracle database accessed by Servlets via JDBC.
- An example map server preferably comprises Maplnfo® Corporation® 's MapXtremeJavaTM 3.1 servlet for retrieving maps for specific local malls, as shown in FIGURE 6. Collaborations of these system components are shown in FIGURE 7 and FIGURE 8.
- a mobile user 700 sends a request to the central LBS server, hosted by integrated location-based service platform 705 via a wireless carrier gateway 710 and Internet 715.
- the central LBS server may be hosted independent of integrated location-based service platform 705 as well.
- the request seeks the address of local-content servers, possibly including local-content server 720 serving the user's geographical location.
- the request preferably further comprises an indication of the geographical location of the mobile user, such as the user's approximate latitude and longitude, although such an indication is not required for practicing the invention since it may be obtained automatically via a location determination service by triangulation or other means.
- central LBS server 600 Upon receiving the request, central LBS server 600, illustrated in FIGURE 6, preferably implemented as a collection of servlets, forwards the message to mall selection servlet 605 residing in server 600.
- Mall selection servlet 605 includes a listing of various malls and may be connected to an integrated location based service platform.
- Mall selection servlet 605 then parses the message to obtain the user's geographical location and queries database 610, with the aid of mall specific service 630, for the name and URL of local-content servers, such as local-content server 720 of FIGURE 7, serving the user's location.
- Central LBS server 600 then responds to the request with a list of names and URLs of the local-content servers serving the user's location.
- central LBS server 600 may be a standalone server including store information and administrative operations capability via mall specific servlet 615, mapping and directions from mapping servlet 620 and local service integration by integrated location-specific platform 625.
- mall specific servlet 615 may serve as the front-end to an integrated location specific services platform.
- FIGURE 6 also shows store table 635 and sales table 640 for providing various services, and which tables are preferably stored in RDBMS 610.
- the mobile user establishes contact with specific local-content server 720, by sending a request with privileges of either a mall administrator or a simple end-user. If only one local-content server was found by central LBS server 600, the mobile user client may be redirected to local-content server 720 without the user's intervention. Otherwise the user is presented with a display comprising a list of local- content servers servicing the user's location. The list may be filtered based on personalization information stored on the user's client 700 or provided by central LBS server 600.
- FIGURE 8 further illustrates interactions between clients 800 and 840 and an integrated location-based service platform performing multiple functions.
- Client 800 sends a request to a central operations center, e.g., using a wireless link, and is connected to central LBS server 810 (which could also be an integrated location-based service provider).
- the request may comprise a mall map, store location, sales/specials, updating of sale data and the like.
- Integrated location-based service provider 810 connects to repository 815 to retrieve necessary information, and may further request second local central LBS server 820, if required, for a map, a specific location, or specials.
- Second central LBS server 820 in turn communicates with a map service 825 or specials service 830, in communication with repository 835 for determining available specials, hi addition, client 840, being in the vicinity, directly communicates with second central LBS server 820 for services.
- FIGURE 9 comprises authentication (password) infonnation for stores in the mall.
- the stores table 900 comprises authentication (password) infonnation for stores in the mall.
- the user is prompted for a password. If the password matches the password for the store in the stores table 910, the user is allowed to administer the store sale information stored in the sales table for that store.
- FIGURE 10 is a flow chart indicating the actions available to a store administrator, which allow remote monitoring of stores with the possibility of conducting inspections and the like if required.
- step 1000 in FIGURE 10 a user with store administrator privileges chooses a mall to access.
- step 1005 the store administrator is presented with a secure login screen.
- Control passes to step 1010 in the event the login fails, and preferably at least a limited number of retries are allowed by transferring control to step 1005.
- Limiting retries is prefened, but not required, since it counters denial of service attacks and other security breaches.
- step 1015 controls flows to step 1015, during which sales for a target store may be retrieved.
- the administrator may elect to, during step 1020, add, update, or delete a sale.
- control flows to step 1025 for entering a new sale, which may be approved in step 1030 or fail during step 1035; step 1040 for deleting a sale, which may be approved in step 1045 or fail during step 1050; and step 1055 for selecting a sale for updating during step 1060, which may be approved in step 1065 or fail during step 1070 respectively.
- FIGURE 11 is a flow chart indicating the actions available to a user who has been provided with a list of local-content servers by the central LBS server or may have received a splash screen image during step 1102, possibly of a promotion, advertisement, or a message indicating start of an application.
- selection or a response results in a user receiving a mall list selection followed by, during step 1105, selection of a store search method.
- the user may, during step 1110 find a store by name; or during step 1115 find stores based on products.
- Control following store selection flows from steps 1110 and 1130 to step 1135, during which the display of a target store's sales list information is selected. Control then flows to step 1140, during which sale information is displayed. Directions to or maps for the target store may then be obtained during steps 1145 and 1150 with various degrees of specificity, denoted by selection of a zoom parameter value.
- FIGURE 12 indicates the conesponding Java panels used by the example application illustrated in FIGURE 11.
- step 1102 conesponds to map panel 1202, which is shown in FIGURE 13, step 1100 to selection panel 1200, and so on.
- Conesponding panels in FIGURE 12 are labeled in a manner similar to the labeling in FIGURE 11.
- the individual user interface is depicted in FIGURES 13 - 22, which are described in greater detail next.
- FIGURE 13 conesponding to 1202 and 1102
- the user has started a client application on his mobile device, preferably a java-enabled cell phone using a mobile positioning system.
- a request including an indication of the user's location is sent to the central LBS server.
- the central LBS server responds with a list of local-content servers serving the user's location, which is displayed on the user's client system as illustrated in FIGURE 14, conesponding to step 1100 and panel 1200.
- two malls are near the user, the Crossgates mall and the Colonie Center mall. If the user selects the Crossgates mall 1402 and selects "OK" 1401, the user is presented the display illustrated in FIGURE 15, which conesponds to step 1105 and panel 1205.
- FIGURE 15 illustrates a user interface that allows the user to indicate whether the user wishes to enter a store name, or to select a store by the item offered on sale. If the user selects "Sales by store name” 1502, and then selects "OK” 1501, the user is presented a text-box display for entering a store name. If the user selects "stores by sale item,” and then selects "OK” 1501, the user is presented with the display illustrated in FIGURE 16, which conesponds to step 1115 and panel 1215.
- FIGURE 16 illustrates a user interface that allows the user to indicate whether the user wishes to enter an item name, or to select an item by category. If the user selects "sale item by name” 1603 and then selects "OK” 1601, the user is presented a text-box display for entering an item name. If the user selects "sale item by category” 1602 and then selects "OK” 1601, the user is presented with the display illustrated in FIGURE 17, which conesponds to step 1120 and panel 1220.
- FIGURE 17 illustrates a user interface displaying categories of items for which the mall-server contains sale information, which user interface also allows the user to select a sale category. If the user selects "Dress Shoes” 1702 and then selects "OK” 1701, the user is presented with the display illustrated in FIGURE 18, which conesponds to step 1130 and panel 1230.
- FIGURE 18 illustrates a user interface displaying a list of stores having sale items in the mall-server database in the category selected by the user, and allows the user to select a store. If the user selects the store "DSW” 1802 and then selects "OK” 1801, the user is presented with the display illustrated in FIGURE 19, which conesponds to step 1135 and panel 1235.
- FIGURE 19 illustrates a user interface displaying sale items in the local- content server database for the DSW store selected by the user. If the user selects the item "Dress Shoes” 1902 and then selects "OK” 1901, the user is presented with the display illustrated in FIGURE 20, which conesponds to step 1140 and panel 1240.
- FIGURE 20 illustrates an interface displaying information about the sale item selected by the user, which user interface also allows the user to request a map showing the location of the store relative to the user. If the user selects "OK" 2001, the user is presented with the display illustrated in FIGURE 21, which conesponds to step 1145 and panel 1245.
- FIGURE 21 illustrates a user interface displaying a map showing the location of the store relative to the user and allowing the user to request a zoomed-in map showing the store location in more detail. The user's location is shown as a pair-of-shoes icon 2102, and the store's location is shown as a dot icon with the name (or abbreviation) of the store 2103.
- the map is automatically scaled to show both the user and the store locations. If the user selects "OK" 2101, the user is presented with the display illustrated in FIGURE 22, which conesponds to step 1150 and panel 1250.
- FIGURE 22 illustrates a map zoomed-in to show the store location in more detail.
- Local-content server servlet 720 (or 615) preferably provides JAVA calls for both administrators and end users. These calls include: getSalesByStoreName( ⁇ store name>);getSalesByStoreLogin( ⁇ password>);deleteSale(existing sale record);addNewSale(sale to create record); updateSale(existing sale record in DB); getStoresByProduct( ⁇ product name>); and getStoreInfo( ⁇ store name>). In alternative embodiments additional or alternative calls may be provided for allowing both administration and browsing by users based on their respective privilege levels.
- location based services can be offered in accordance with the present invention in an integrated location based service platform or as stand-alone services.
- the services range from sales promotions, discovering nearby stores, locations to matching events and generating maps using various modes of transportation.
- an integrated location based service platform may further include a plurality of third party servers such as those accessible at a network address conesponding to a response to a request for at least one geographic feature.
- the geographic feature is preferably an address of a location-based-information-system server associated with a user location, which preferably provides: personalization data as part of the person profile service; and links to one or more local servers associated with the user location and conesponding to input profile data or a user profile.
- the location-based-information-system server preferably redirects a user to a first local server, or provides a choice of local servers.
- a local server may provide additional user profile information, and information about one or more of sales, promotions, availability of a product or service, alternative sellers of a specified product close to the user location, or alternative providers of a specified service close to the user location.
- a user interface responsive to one or more taps or strokes on a pad, one or more clicks of an input device, or a voice command is provided to a client.
- Such a user interface is also useful for making subsequent requests (such as using a nearest geographic feature to get to content of local stores on local servers and directions to a store using the routing service).
- location based services is a location sensitive event service, such as the CoolEvent® service offered by the Maplnfo® Corporation, which service finds a list of events that are of interest to a service subscriber or other user, based on the user's location and preferences stored in a profile.
- This service like the peer-to- peer location based service may be offered in association with an integrated method and system, such as the miAwareTMsystem offered by the Maplnfo® Corporation, described previously, or be provided as a stand-alone service.
- the returned events are sorted by distance between the user's cunent location and an event place. A demographic analysis is performed to returned selected events.
- the design underlying the location sensitive event service is not limited to use in locating events, but, without limitation, may also be used for a variety of other applications, such as wireless advertising, or in generating matches for dating services.
- the design underlying the location sensitive event service is also intelligent such that increased use of the service results in refining the user profile without additional end user input.
- the present system and method may also be used, for example, in a dating service to determine whether to introduce individuals based on their profiles.
- the location sensitive event service may also provide content filtering capabilities in the user profiles - i.e., options to allow users to preselect content which they would like to find, either on demand or as a result of polling.
- FIGURE 23 illustrates an exemplary architecture for an embodiment of the location sensitive event service.
- User 2301 subscribes to the location sensitive event service provided via servlet 2305.
- Web scraper 2320 culls possible events from event sources 2325 to generate events in event database 2330.
- Event database 2330 is processed in accordance with demographic event model 2310 to generate a list of suitable events for the servlet 2305.
- subscribers 2335 provide information 2340, which is used to augment user profile database 2345 and generate and refine demographic user model 2315.
- Servlet 2305 matches the user profile with the event profile to generate an ordered list of events that may be provided to user 2301.
- Information 2340 preferably includes personal preferences such as music, art and food and any other preferences or parameters of interest. This information is used by the CRM engine to sort events matching a user's interests.
- personal preferences such as music, art and food and any other preferences or parameters of interest. This information is used by the CRM engine to sort events matching a user's interests.
- An example set of personal preferences is as follows:
- Additional personal information that may be relevant includes:
- Resident Type owner/renter etc
- Type of occupation student/blue collar/ service/white collar/executive
- Example behavioral characteristics(with optional groups) may include:
- FIGURE 24 Another view of an architecture providing a location sensitive event service, operating as a customer relation management tool, is illustrated in FIGURE 24.
- Client 2400 communicates, for instance over the web using web protocols such as HTTP and with markup languages like XML to specify various interfaces, with location sensitive event service servlet 2405.
- Client 2400 for instance the CoolEventsTM client supported by Maplnfo® Corporation, may be a J2ME MJDlet and, furthermore, it may be based on existing MLS services. This allows most of the basic functions of MLS such as mapping, routing and geocoding to be also used.
- Location sensitive event service servlet 2405 communicates with profile database 2410 of mobile location service subscribers to obtain personal preferences for a particular user. Such personal preferences may be generated with the additional aid of personal extension database 2415.
- Location sensitive event service servlet 2405 may be implemented as a allows stand-alone implementation, although, integrated location-based service provider 2420 may be used for relation management service as well.
- optional customer relation management engine 2425 designed specifically for this application or a functional equivalent, can directly interact with location sensitive event service servlet 2405 instead of integrated location-based service provider 2420.
- CRM customer relation management
- a CRM engine specifically designed for this purpose can be made available, including as an alternative or to supplement the miAwareTM system.
- the illustrative miAwareTM service for CRM mentioned previously in the context of FIGURE 24 accepts an XML request which includes login ID and cunent location of the client.
- the service retrieves personal information through miAwareTM profiler using the login ID, then gets personal preference data.
- An XML element is then created and sent to the CRM engine.
- the returned list of events is sent back to the client.
- the MapXtendTM service typically includes the following functions.
- MLS profiler database
- additional databases may manage personal preference data.
- This database may be linked to the profiler database by, for instance, the user's login name.
- this event service event list can be returned as MXTD DAR (representing the MapXtend specifications).
- Start a command to start a session. If the user has already logged in, e.g., with miConnect, the user's profile may be automatically retrieved, otherwise a login by the user provides a login name and password. Alternative authentication methods may also be employed, if desired, to start the session.
- Start command preferably triggers a search by the CRM engine to return an original recommendation of events for the user, in accordance with a cunent location (preferably the user's) and profile data.
- Route map this command requests a map centered at a chosen event place, with, preferably, a routing line highlighted on the map.
- directions this command requests a textual, or an alternative such as Braille or audio, description of routing directions for the client to get to the event place.
- Personal Preferences are advantageously stored in a preferences database that lists user preferences.
- a look-up table for coded preferences assists in accessing the database.
- Exemplary table entries may look like:
- Preference code codes are grouped (music, sports, activities).
- a rank value is used to indicate the priority that the user gives to a certain type of an event category (e.g., basketball in Sports), this is an input value from the user.
- an event category e.g., basketball in Sports
- a score is calculated for the user on each event. This score is used to rank the events.
- user registration for the present session may be accomplished using one or more web-pages and an appropriate wizard.
- the first page may be a modified version of the current miProfilerTM provided by Maplnfo® Corporation.
- a second page may collect additional personal information, advantageously (but not necessarily) in a way similar to the first page.
- a third page collects personal preferences. The user selects an option and ranks it.
- expandable DHTML elements may cover many preference classes (for instance, music, sports, sports viewer, activities, alcoholic beverages and movies), some classes may result in a long list.
- a scrollable list box may hold the selections, with buttons for the user to select the items into another list box in which the items are sorted according to which button is clicked.
- An event database is also preferably built and updated for providing a location sensitive event service as illustrated in FIGURE 23.
- a real world event database should be dynamic and typically changes daily.
- Subscribing to an external database such as Toronto.com is a possible maintenance mechanism with the aid of an exemplary client program to access such an external service.
- a web scraper designed to scrape a particular website, e.g., Toronto.com, may be created to access event data from the website.
- Some example profiles are: 1) a 26 year old, male University of Toronto student on a Friday evening; 2) a 46 year old Bay street business man on a Friday night with without the wife; 3) a typical Mississauga housewife with 3 children.
- an interface to an optional CRM Engine is also preferably provided.
- language-specific APIs Java/C# etc
- An exemplary XML API may comprise the following input and output:
- Inputs three elements: personal data, preferences and address.
- Personal data preferably includes items required by miProfilerTM plus additional attributes.
- Preferences is preferably a sequence of preference codes and ranks.
- each event element preferably including an event name, and a detailed description comprising a place, date and time.
- attribute abstraction is possible in a location sensitive event service.
- a personal preference set including a person's preferences on music, sports, sports to watch, movies, activities and beverage taltes
- the preferences are divided into six(6) groups each of which may be given an equal weight of 1/6 points.
- a person's musical preferences may be ranked as: l. JAZZ (1.0)
- each event being assigned attributes of six (6) types, e.g., music, sports, sports to watch, movies, activities, and alcohol/beverage tastes, since an event belongs to certain types, and may be more one type than another, weights may be assigned to each type. For instance, a concert could be assigned weights like:
- Activities score 0.6 (go to a restaurant with friends met) * 0.16667 * 0.2 (event weight)
- Age age may be divided into age groups of ⁇ 18(0), 18-25(1), 26 - 35(2), 36 -
- each age group jump decreases 1/6 points. For example, if the persons age is > 65 (6) and the event is for person between 18-25 (1), then the age point will be: 1 - (6-1) 1 6 1/6.
- Bundled Demographic data including marketed bundles such as PsyteTM two psyte codes may be compared directly to show the closeness between them.
- Marital status single(O), widowed(l), divorced(2), separated(3), non-steady partner(4), steady partner(5), common law(6), married(7).
- Employment status full time employed (10.1), part time employed(10.2), full time student (20.1), part time student(20.2), unemployed(30).
- 1.0 if the difference between the event and the user is greater than 1.0, 1.0 may be used.
- Top three music A model that compares the choices may be employed to take into account music type as well as sequence of choices.
- Top six favorite sports to participate same as music.
- the abovementioned attributes are common to most events. For some events, some attributes are more important than others, or less important, or don't count at all. This may be adjusted by giving each attribute a weight.
- a standardized vector is a vector that is scaled to the means of all possible values. Since the comparison is canied out between two attribute vectors for an event: event attributes and preference attributes, and attribute values are taken from a big range, they must be standardized to range in a common scale (e.g., 0.0 to 1.0, or 0 to 100) to make the comparison possible. To standardize a preferences vector, means and standard deviations of all attributes may be calculated using all records in the database. Then attribute k may be standardized as: zsftt)
- Standardization of Events may be undertaken after all the events are assigned attributes. They may be standardized by the same procedure as for personal preferences.
- FIGURE 25 summarizes a process for generating ordered lists of events conesponding to user profiles.
- Profiles database 2500 is used to generate standardized profile database 2505 reflecting the distribution of various attributes that are part of the various profiles.
- the standardized profile database allows generation of attributed personal preferences 2530 that can be compared in the manner illustrated above.
- event database 2510 leads to attributed event profile 2515.
- the event and personal profile attributes are then subjected to multivarient comparison 2520 to effect matching by generating scores for each match.
- the scores for different matches are then compared 2525 to generate the ordered lists actually used to plan events, or to provide users with available event related details.
- event planning, generation of directions based on multiple modes of transportation, or managing/browsing stores in the vicinity are illustrative examples of location based services. Any combination of these services may be integrated using the integrated location based services platform in a dynamic manner since new services can be added, or existing services updated with the aid of the XML encoded specifications. Adding a service is as simple as choosing a unique name followed by publishing the service to the service manager in the specified manner. The limited rules for adding and publishing services, being themselves encoded in XML, are both easy to follow and readily available.
- responses to requests for particular services may elicit information about sales, promotions, products, services, or events associated with a user profile or preference, preferably ananged in a sorted list for selection of one or more entries.
- Each event is, preferably, associated with a plurality of weighted event attributes types and values of event attribute subtypes.
- each user profile comprises a plurality of weighted profile attributes (such as those organized into vectors and matrices). These allow for generation of a similarity score based on shared attributes and their respective weights in arriving at a list of events matched to the user profile or vice versa.
- the profile attributes may be standardized using the available data in the various databases, such as the event and the profile databases, to improve the comparison between profiles and event attributes.
- the present invention includes a stand-alone service for assisting a user to locate stores, directions to such stores and browse various products and services.
- the service is configured to receive a request from a client device (e.g., a thin client on a cell phone), and retrieve a record comprising an identifier of a second server system that is better suited to provide content from the specified location (e.g., a sale at a specified store in a mall).
- the service may be further configured for one or more of adding, deleting, and updating of store sale records, retrieving a map from a map server, or a record based on request location criterion and a user profile.
- the user profile may include personalization information, which may be useful in providing personalized information about services available in a geographic area of interest.
- the present invention also encompasses a communication system comprising a server system, for instance, the miAwareTM system of Maplnfo® Corporation, that is configured to provide a location and an ordered list of events matched to a user profile to a client device (e.g., a cell phone).
- a server system for instance, the miAwareTM system of Maplnfo® Corporation
- Each event in the list of events is associated with weighted event attributes types and values of event attribute subtypes
- the user profile is associated with weighted profile attributes, which are used to compute a similarity score.
- the profile attributes may be standardized using statistics (such as a mean and a standard deviation) of the profile attributes in a database having a plurality of user profiles, and, similarly, the event attributes may be standardized using statistics based on the event attributes in an event database. Then, the similarity scores between events in a database and a specified user profile may be calculated by summing, over the events in the database, the square of the differences between standardized event attributes and conesponding standardized specified user profile attributes, or, alternatively, by summing, over substantially all users in the database, the square of the differences between standardized user profile attributes and conesponding standardized specified event attributes.
- the present invention includes a method for providing location based services.
- the method may be illustratively be described as comprising the steps of receiving a request for a service in a message encoded in a markup language (XML) at the service manager; optionally authenticating the request; determining whether the service is available at a plurality of service modules registered with the service manager (by accessing the catalog of services); forwarding an enor message in response to determining that the service is not available at the plurality of service modules; forwarding the request to a service module (the request object) in response to determining that the service is available; and sending a result received from the service module (the response object) to a client device (as an XML encoded response).
- XML markup language
- the client device sending the request may have a different address than the address of the client device receiving the result, or, alternatively, the client device (e.g., browser on a cell phone) is redirected to another server (the local-content server).
- the client device e.g., browser on a cell phone
- a method for providing location based information in accordance with the invention includes receiving a request that also comprises information identifying a user and a location (e.g., the cell phone location) to enable retrieval of the user profile and one of more records based on said request and a location criterion.
- the local- content server located in this manner may provide additional details such as information about sales, promotions, availability of a product or service, alternative sellers of a specified product close to the location, or alternative providers of a specified service close to the location.
- the present invention includes a method for providing a list of events matched to a user profile comprising comparing a user profile (e.g., via the miAwareTM system or a standalone system) with a database of events with the aid of profile attributes from the user profile and event attributes; generating similarity scores for events conesponding to the user profile; ordering the list of events according to one or more of a location criterion, a specification (e.g., a personal preference), and the similarity scores; and providing at least an ordered subset of the list of events to the user.
- a user profile e.g., via the miAwareTM system or a standalone system
- a database of events with the aid of profile attributes from the user profile and event attributes
- generating similarity scores for events conesponding to the user profile ordering the list of events according to one or more of a location criterion, a specification (e.g., a personal preference), and the similarity scores; and providing at least an ordered subset of the list of events to
- the event is assigned a weight with respect to each attribute type and a value for an attribute subtype (may be considered to be an event matrix).
- the user profile includes values for the profile attributes (a profile vector), wherein one or more of the event types and profile attributes are weighted to reflect their relative significance.
- the described method is suitable for not only for determining matched events, but also for providing a list of users matched to an event (e.g., useful for determining whether the demographics are favorable for staging a proposed event, targeting an enriched audience with advertising, and the like).
- This may include comparing an event with a database of user profiles with the aid of profile attributes from the user profiles and event attributes; and generating a list of users with their conesponding similarity scores.
- the list of users may be ordered according to a location criterion, a specification, or the similarity scores.
- the present invention includes design of a suitable thin client by a module for constructing service requests aided by helper classes to construct and submit service requests to the service manger.
- the module is implemented with no dependence on core server software to make it independent of the server and incorporates a parser to process responses received from the service manager.
- miAware is the provider of Maplnfo's location enabled services over the internet in the form of an extensible Markup Language Application Interface (XML- API). These services enable a collection of applications to manage information specific to mobile locations.
- XML- API forms the platform to tie together key services commonly used in the development of these mobile location applications.
- Wireless caniers and service providers are constantly looking for new and enhanced service offerings for their customers. Many of them are combining mobile location with wireless web access.
- Clients range from PDA's and phones to telematic devices that communicate through an operator's network to a gateway.
- the gateway platform integrates Intelligent Network (IN) protocols with Internet Protocols (IP). This provides the means for an application running on the miAware platform to have secure access to resources inside the operator's network.
- the location server (MPC or GMLC) integrates the operators network with position determining equipment. This allows an application to determine the subscriber's approximate position.
- the miAware platform provides the service building blocks that operate on location data to implement location aware applications.
- Mobile location enabled services provide end users with mobile Internet access to infonnation that is relevant to their location such as nearby businesses, routing directions, and personalized marketing offers. These services offer advantages for telecommunication equipment vendors and carriers, and convenience for end user customers. Carriers can differentiate themselves in the competitive marketplace by offering new, exciting, and useful services on their Networks, helping them attract and keep customers, and grow their revenues. Subscribers can now use their web-enabled mobile phone or Personal Digital Assistant (PDA) to access information and services relevant to where they are. Page 3 of 10
- Maplnfo offers a suite of technology and applications that enables wireless service providers to deliver mobile location services from mobile Internet environments.
- Maplnfo's Mobile Location Suite is comprised of location processing engines, geocoding, map generation, routing, geographic data, and location enabled services. These services communicate with each other and with third party systems and user devices through XML.
- miAware acts as a platform for location aware applications, such as the applications provided with the Mobile Location Suite. It exposes location processing to developers in an XML environment, so that new applications can be easily integrated into the existing system. It also makes it easy to integrate new features based on customer requests. miAware is installed at and managed by the wireless carrier or service provider, giving them full control over their service offerings.
- the following services are bundled with an miAware deployment. New services can be developed and added to the existing collection using the miAware Service Provider API.
- Geodecode This service returns address information associated with a given Longitude/Latitude. This information could include postal code, city, and street intersections. This service helps your customers find useful information from a map about where they are right now or about their destination.
- Route This service lets you add turn-by-turn driving directions to your web-based application. It lets you calculate either the shortest distance or quickest timed route between any two points. This service returns text-based driving directions and spatial points to your users.
- FindLocation This service provides searching functions for either street names, business names, or cross street names for a given street name in order to help identify a geographical location.
- mapping - This service provides the capability of creating mapping images from geographic data.
- the data can be stored in Maplnfo TAB files, in an RDBMS, or in an OGC Geographic Meta Language format. Multiple image formats (e.g., GIF, JPEG, PNG, etc.) are supported.
- a map image can be returned either as a BASE-64 encoded document or an URL of a file located on the miAware server.
- CoordSys This service provides the capability to transform GML geometries from one coordinate system to another.
- CoordSysService depends on the Maplnfo implementation of OGC coordinate systems and transformations (Geometry.dtd and MapXtendGML.dtd).
- Position Refinement - The Position Refinement Service provides the capability of refining the position of a mobile device user based upon the points of interest (POI) that can be identified within the area of the user.
- POI points of interest
- Administration Service This service provides the capability to administrate the miAware server through an XML API.
- This XML API allows administrators to: Query all information about their miAware server and services running, update the configuration properties of the miAware server and services, and perform operations on the services running on the server.
- miAware uses industry standards to expose location processing to developers. It provides a concise, consistent, flexible and scaleable XML environment for the creation of new location-based services.
- Location enabled services are provided as a self-contained and modular location centric process, which can be described, published, located, and invoked over a network. These services can be used dynamically by mobile location applications or other mobile awareness services to manage information specific to a request.
- miAware you can quickly and easily integrate applications into existing systems and rapidly add new features based on customer requests.
- location-based applications can be developed using native programming languages such as Java or C++. Page 5 of 10 Documentation
- miAware Online documentation contains all sections of the product documentation. This includes: a product guide, a developers guide, the XML API reference guide, administration guide, and the JAVA API documentation.
- miAware When installing miAware, the installation will create the following directories and files inside the miAware main directory: index.html - miAware home page.
- /dtd Contains the miAware and specific service DTD's.
- /samples Contains all of the miAware demo applications, including the client and service- provider Java code and the sample request, response, and service-profile XML's.
- /data - Contains all data files for miAware, including LDAP specific object class and attribute definition files.
- /lib - miAware core libraries including all of the verified classes (jar files) for the miAware runtime, service providers, and client applications.
- /packages - Contains the miAware service deployment descriptor (miAwareSDD.xml) and the miAware service packages.
- the descriptor contains the names of all required files such as jar files, apidoc directory, configuration files, and service catalog entry.
- Routing Performs routing according to a given start and end locations of the route. A summary and optional street segments/points of the route are returned.
- Geocoding Performs geocoding on a given address. Allows one of the postal code centroid, street, or intersection match.
- Geodecoding Performs reversed-geocoding of a given location. Support postal code, city, county, state, or street intersection look up.
- Each demo can display a request XML document in a new window based on values and settings entered through the HTML form. If the request is submitted, results (response document) are shown in a new window. Note: For the demo to run, you must have installed the appropriate service via the service installer. For Instruction on how to install a service, please see the Service Install Guide. You must also use Internet Explorer 5.x or newer.
- a simple service example is the Hello World demo. This service example will take user defined properties values and return (or echo) a simple response based on the user's choices. There are two main groups of user defines properties, greeting message properties and response properties:
- the XML request document will be displayed. This document will contain all of the specified properties, including the miAware header (blue text), the Page 8 of 10 miAware properties and elements (red text), and the user defined property values (black text).
- the request XML document is processed by the Hello World service and a response XML is returned based on that request.
- the polite property specified in the request is now processed and the word 'Sir!' is returned if that property was true. : FiiAware Demo - Microsoft Internet EKDiorer M miAware Hello World Demo
- XML and miAware miAware employs a request/response model based on the extensible Markup Language (XML) technology and the HTTP protocol.
- miAware service requests and responses are XML documents with specific syntax and semantic governed by conesponding Document Type Definitions (DTD).
- DTD Document Type Definitions
- Extensible Markup Language abbreviated XML
- XML Extensible Markup Language
- XML documents are class of data objects called XML documents, and partially describes the behavior of computer programs which process them.
- XML is an application profile or restricted form of SGML[ISO 8879].
- SGML restricted form of SGML[ISO 8879].
- XML documents are conforming GML documents.
- XML documents are made up of entities (or better described as storage units), which contain either parsed or unparsed data. Parsed data is made up of characters, some of which form character data, and some of which form markup. Markup encodes a description of the document's storage layout and logical structure. XML provides a mechanism to impose constraints on the storage layout and logical structure.
- DTD Document Type Definition
- miAware is a provider of Maplnfo's location enabled services (LES) (e.g., geocoding, routing, find nearest, etc.). It employs a request/response model based on the extensible Markup Language (XML) technology and the HTTP protocol. miAware service requests and responses are XML documents with specific syntax and semantics governed by conesponding Document Type Definitions (DTD).
- LES Maplnfo's location enabled services
- XML extensible Markup Language
- DTD conesponding Document Type Definitions
- Java servlets are used to direct requests and responses between the Clients and Servers.
- a servlet is a Java-based web server extension application, which answers client requests.
- Servlets are not tied to a specific client-server protocol, but they are most commonly used with HTTP and the word "Servlet” is often used in the meaning of "HTTP Servlet”.
- Servlets are secure, since they operate within the context of a secure manager, similar to applets.
- the servlet API is a standard Java extension, and therefore portable and platform-neutral.
- Server extension APIs including the Java servlets and CGI, share the request/response model of HTTP since they operate within the context of an HTTP request.
- miAware clients submit a service request (XML document) as an HTTP POST to the miAware Service Manager at a known URL.
- the miAware Service Manager dispatches it to a conesponding service provider, which has previously been registered to handle the request.
- the service will dispatch a request to a spatial server or third-party server to complete the task (accessing a database or LDAP server for data).
- the Service Manager After the service has complete the request, the Service Manager will create a response XML document and return the rendered response to the client.
- This document contains either the requested results or fault information (FaultResponse) if an error occurs.
- faultResponse fault information
- the HTTP status is always set to HTTP_OK (200) in either situation. The requestor needs to examine the response document to determine where a failure has occurred.
- the following workflow shows the movement of information from the point of the client request to the point where the client receives a response:
- One of many clients submits a request to a miAware Service Manager (could have multiple service manages) over HTTP at a known URL (the location of the miAware instance or server.
- a miAware Service Manager could have multiple service manages
- HTTP HyperText Transfer Protocol
- URL the location of the miAware instance or server.
- the Service Manager authenticates the request with account information in a LDAP Page 3 of 7 directory, then dispatches that request to the corresponding Service Provider through a Service Request Object. It obtains configuration information and service specific information from the miAwareConfig.xml and miAwareServiceCatalog.xml files.
- the Service Provider generates a response and returns a Service Response Object.
- the Service Manager then forwards the response document to the client.
- Client parses the document for results or e ⁇ or information.
- miAware Service Manager Two key components of miAware is the Service Manager and the Service Providers. These two components interact to process the service request and produce a service response for a client. miAware Service Manager
- the miAware Service Manager is a threaded servlet listening on requests over the Page 4 of 7
- HTTP/POST It can be configured and deployed to local specifications according to custom settings stored in the miAwareConfig.xml file.
- the types of services managed by a specific miAware site are controlled by a service catalog named miAwareServiceCatalog.xml.
- This XML document contains service definitions such as the service name, implementation class, dependant libraries, and URLs of external third-party services (if remote services are used). Newly developed services may be added to the catalog or published to the Service Manager as they become available. Similar, existing services can be turned "off-line" or removed all together.
- a service request When a service request a ⁇ ives, the XML document is validated to make sure it is a well- formed miAware request. The requestor is then authenticated with the information given in the 'Header' of the envelope. The name of the requested service specified in the TargetService attribute is used to dispatch a service provider to render the request.
- the Service Manager creates a ServiceRequest object based on the given XML document and passes it onto the Service Provider's performQ method to initiate the operation. The Service Provider responds with a ServiceResponse object, which either contains successful results or a Fault Response. The Service Manager generates an XML document from the Service Response object using the toXMLDocumentQ method then forward it to the requestor through the HTTP channel.
- Profile data include user account information and business categories such as types of restaurants and a list of customer locations. Such information is stored in a LDAP server and accessible by service providers via API calls.
- miAware Service Provider miAware services are handled by Service Providers. They are dispatched by the Service Manager dynamically to handle a specific service registered previously to miAware. Between the Service Manager and a Service Provider is a Service Provider interface. This is a link between the Service Manager and the provider used to initialize and shutdown the providers as well dispatching the service request and receiving the service response.
- the miAware Service Provider Java API is a set of Java interfaces and classes which enable development of new miAware services. New services can be deployed to the existing set of services hosted by a miAware site. Once deployed, services can be accessed from the outside world.
- a service provider must implement tliree main interfaces: ServiceProvider, ServiceRequest, and ServiceResponse:
- a ServiceProperties object is passed into the provider so configuration information specified in the Service Catalog can be utilized. Since initialisation is only a one time operation.
- the provider should cache global information necessary for performing service requests in a multi-threaded environment.
- the provider must de-allocate occupied resources so to avoid memory leakage and/or holding up unnecessary resources (e.g. database connections).
- a ServiceRequest object must be created by the provider based on the input request document. This object should parse the content of the document and provide information available for rendering a request. The ServiceRequest will be passed into the provider at a later stage to carry out a service request. Implementation of this interface must also provide capability to create a miAware request document conformance to the miAwareServiceRequest DTD. Page 6 of 7
- Set method (e.g. setDistanceUnit() of the RouteRequest object) should be available for filling the content of this document. o setters & getters o toXMLdocument()
- a ServiceResponse object must be returned after a service is rendered. This object must provide methods for publishing its content to a XML document conformance to the miAwareServiceResponse DTD. In addition, this object must also be able to parse its own response XML document and provide "get" methods (e.g. getTotalTime() of the RouteResponse() object) for retrieving the content. o setters & getters o toXMLdocument()
- the miAware Client Java API is a set of helper classes grouped by services, which assist Java application developers to publish service requests and retrieve information from a response document.
- miAware services are managed by dedicated service providers.
- the miAware framework allows new service providers to be "plugged” in, as they become available.
- a miAware service provider must conform to a specific infrastructure to allow a seamless integration. This document provides a set of guidelines to assist the development of miAware compliant service providers.
- DTDs Two Document Type Definitions (DTDs) must be available. These DTD govern the syntax and semantics of the request and response XML documents of the service being developed.
- Service requests must be identified by a distinct XML root element (e.g. GeocodeRequest).
- GeocodeResponse The same goes to service responses (e.g. GeocodeResponse).
- the service request and response documents must also conform to the miAwareServiceRequest and miAwareServiceResponse envelopes. That is, a service request and response must be contained within their corresponding envelope.
- Both DTDs must be defined in a single file named XXX.dtd, where XXX may be the name of the service. For example, Geocoder.dtd for the Geocoder Service.
- a service provider must implement the ServiceProvider, ServiceRequest, and ServiceResponse interfaces.
- Service provider developers must ensure their implementation operates correctly in a multi-threaded environment. That is, an instance of the service provider is initialized once at startup then dispatched concurrently to handle multiple incoming requests. At shutdown, the provider must also ensure all allocated resources are disposed and that there is no memory leakage.
- the name of the provider implementation class (e.g. com.mapinfo.miAware.services.Geocoder.GeocodeService) must be clearly identified in the miAwareServiceCatalog.xml so an instance of it can be created dynamically by the miAware Service Manager. Page 3 of 5
- Implementation of the ServiceRequest interface must not have dependency on server-side logic. This allows the same implementation to be deployed on the client-side as a help class to create XML request documents.
- the request class must provide set methods to populate the content of the XML request document programmatically. For example, the setTimeUnit method of the RouteRequest objects that assigns a time unit value to the TimeUnit attribute of the RouteRequest element.
- implementation of the ServiceResponse interface must not have dependency on service-side logic. This allows the same implementation to be deployed on the client-side as a help class to retrieve results from a response XML document.
- the response class must provide get methods so content can be retrieved programmatically. For example, the getTotalTime method of the RouteResponse objects that obtains the total travelling time from the TotalTime attribute of the RouteRequest element.
- This class must also provide constructors, which allow an instance of the response object to be created from an XML document.
- Helper classes e.g. miAwareRequest and miAwareResponse
- miAwareRequest and miAwareResponse are available in various miAware packages, which can be used to ease implementation of the request and response classes. Please refer to the miAware API Javadoc for details.
- Service providers must be localizable according to a given locale and an encoding method. That is, texts and messages issued by the provider must be encoded in the specified language (German) and character set (UTF-8). The same localization rule also applies to response XML documents.
- the desired locale and encoding settings are given respectively in the Language and Encoding attributes of the miAwareServceRequest envelope. This information can be retrieved programmatically using the getLocale, getEncoding, getResponseLocale, and getResponseEncoding methods of the RequestEnvelope object.
- ListResourceBundle subclasses To support localization, all texts and messages must be externalized in one or more ListResourceBundle subclasses. These classes must be packaged in their own JAR file separate from the core JAR files. Also, their source files must be available so that new classes can be created for other locales without recompiling the core.
- XML Parsers miAware currently employs Apache's Xerces package for parsing XML documents. It is strongly recommended that service provider developers also use this parser to avoid incompatibility with other vendors. Please refer to the Xerces documentation for details.
- the com.mapinfo.miAware.xml package provides a set of help classes for XML parsing and publishing. Service developers are urged to utilize these classes to manipulate their XML documents.
- Setup and/or runtime parameters e.g. host/port of an external server
- Setup and/or runtime parameters that required by the service provider must be externalized in configuration files so their settings can be changed without code recompilation.
- Developers can choose to define parameters directly in the Page 4 of 5 miAwareServiceCatalog or supply a path to an external configuration file. In either case, detailed description of the parameters and/or configuration files must be documented with instructions on how to alter their values for different deployments.
- test harness must be available to verify if the service provider operates conectly per design.
- the test harness must be in the form of standalone Java programs, which exercises all functionality and logical branches of the service provider. Test results must be logged in a file with each test case clearly identified. An "expected-result” log will also be needed so it can be used as a reference for "correct” results.
- the service provider must be certified for the SUN Solaris 2.7+, Windows NT, and Windows 2000 platforms.
- the miAware Service Provider Java API allows new services to be developed and deployed to a miAware server instance. Once deployed, these services can be accessed over the wireless network. New services can also be distributed and deployed on other miAware sites from a Service Provider Package (SPP). This document describes the procedure for creating, deploying, and packaging new miAware services.
- SPP Service Provider Package
- the sample Hello World service echoes a given text message in the response.
- a trailing message may be appended to this message based on a specified option.
- the HelloWorld request document must accept an input text message as well as an option for the trailing message. They are represented by the RequestDoc element and the Polite attribute respectively.
- the Content element of the HelloWorld response document is used to return the input message with an optional trailing message.
- miAware provides a mechanism that supports service- specific properties for configuration purposes. These properties are defined in the miAwareServiceCatalog.xml file and are accessible through the Service Provider API.
- the name of the service (e.g., HelloWorld) must be determined. It must be unique amongst all officially registered miAware services.
- the service name is stored in the miAwareServiceCatalog.xml file under the Service entry of the provider. Service requests are dispatched to the corresponding provider based on this name. Page.2 of 12
- a request DTD and a response DTD must be designed and created for a new service.
- the syntax and semantics of these DTD files are based on the information from the design process.
- the root element of the request DTD must be contained within the miAwareServiceRequest envelope (a sub-element of miAwareServiceRequest).
- the miAwareServiceRequest envelope also carries additional information required by miAware.
- the HelloWorld request DTD below depicts the relationship between the Hello WorldRequest root element and the envelope:
- the root element of the response DTD must be a sub-element of miAwareServiceResponse.
- the miAwareServiceReponse envelope carries a service- specific response as well as a FaultResponse definition.
- the FaultResponse element contains information of a failed service request.
- the HelloWorld response DTD below depicts the relationship between the Hello WorldResponse root element and the miAwareServiceResponse envelope.
- Both the request and response DTDs must be stored in a single file with a ".dtd” extension (e.g., Hello WorldService.dtd).
- the name of the file should be the name of the service for easy identification.
- miAware employs the following naming convention on elements, attributes, and default attribute values for consistency ( all services must follow this convention):
- a service provider must implement three main interfaces: ServiceProvider, ServiceRequest, and ServiceResponse.
- the ServiceProvider interface is a link between the miAware Service Manager and the provider. It is used to initialize and shutdown the provider as well dispatching requests.
- the ServiceRequest interface manages parsing and publishing of request documents.
- the ServiceResponse interface handles results of a service.
- helper classes are available from the miAware Service Developer API, which can simplify service implementation.
- the com.mapinfo.miAware.common package contains the Java implementation of the common XML elements (e.g., Address, Point) described by the Services XML- API documentation. Service providers should re-use these classes instead of creating their own.
- miAware uses the Apache Xerces parser for manipulating XML documents. The DOM parser of Xerces is available from the com.mapinfo.miAware.xml.XMLDocument class. This class manages DTD caching and additional logic in resolving DTD references. Service implementation should use this class for all XML parsing.
- URLClassLoader loader new URLClassLoader(url, getClassO-getClassLoaderO) miAware maintains information of all registered services in a Service Catalog located in ⁇ MIAWAI ⁇ >/WEB-rNF/conf ⁇ g/miAwareServiceCatalog.xml. Each service occupies an entry in this file delimited by the ⁇ Service> and ⁇ /Service> elements. To install a new service, a new entry must be created and added to the catalog according to the syntax and semantics given by the DTD below. This DTD is also available from the ⁇ MIAWARE>/WEB-rNF/config/miAwareServiceCatalog.dtd file.
- miAwareServiceCatalog Root element of the service catalog that contains definitions of one or more miAware services.
- Name of the service. It must be unique within a miAware instance. This name matches the TargetService attribute in the request envelope.
- Classlnfo Information of the service provider implementation class and dependant libraries Class Name of the Java class that implements the
- ServiceProvider interface For example, com.mapinfo.miAware.services.router.RouterService.
- Property Service property required by the operation of the service are key-value pairs. Multiple entries may be specified.
- Every miAware service must provide an implementation class (e.g., com.mapinfo.miAware.services.HelloWorlcLHello World) of the ServiceProvider interface.
- This class is loaded dynamically when the miAware server starts up.
- the name of this class is obtained from the service definition in the service catalog (miAwareServiceCatalog.xml).
- Service provider implementation must extend the miAwareProvider abstract class so that startup and shutdown of the service can be managed correctly by the Service Manager when multiple threads are running. A service will delay shutdown until all of its outstanding request threads are complete.
- a ServiceProperties object is passed into the provider via the init() method. This allows the configuration information specified in the service catalog to be utilized. Since initialization is a one-time operation, the provider should cache global information, necessary for performing service requests, in a multi-threaded environment. Service providers must synchronize its initialization with the Service Manager by calling super.init ( ⁇ ServiceProperties-Instance>) from their init() method.
- the shutdown() method is invoked.
- the service provider must free up resources such as memory and database/server connections to avoid memory leakage and/or Page 6 of 12 hold up unnecessary resources.
- resources such as memory and database/server connections to avoid memory leakage and/or Page 6 of 12 hold up unnecessary resources.
- a Java VM will recycle memory occupied by objects as long as there is no references to them. Services can be shut down and restarted many times within the same Java VM session of a container (e.g., Tomcat). If a service provider does not clean up these connections, unnecessary memory usage may accumulate for each shutdown and startup operation.
- a ServiceRequest object must be created and returned by the provider via its getServiceRequestO method based on the input document. This object must parse the content of the document obtained from the given InputStream and store relevant information for rendering a request.
- the ServiceRequest object will be passed into the provider at a later stage to render the request "set" methods (e.g., setRequestDocs() of the HelloWorldRequest object).
- the ServiceRequest must be made available for filling the content of a request document programmatically, enabling a request document to be published via a Java interface.
- a ServiceResponse object must be returned by the perform() method after a service is rendered. This object must provide methods for publishing its content to an XML document, conforming to the service DTD. In addition, this object must be able to parse its own response document and make such information available through the provided "get" methods (e.g., getResponseDocs() of the Hello WorldResponse() object). Service providers must notify the Service Manager from their perform() method prior to processing a request and after a request is complete. The startPerform( ⁇ ServiceRequest-Instance>) method must be called before processing a request and endPerform() after it is complete.
- miAwareRequest Every miAware service provider must provide an implementation of the ServiceRequest interface.
- a convenient abstract class com.mapinfo.miAware.services.miAwareRequest is available from the miAware API which can simplify this implementation. It is recommended that developers create a subclass of miAwareRequest. This class provides methods for handling the following logic:
- a request envelope contains information of the requestor, locale, and character encoding which are required for processing the request.
- ServiceRequest As a subclass of miAwareRequest, an implementation of ServiceRequest is required to provide logic for the following constructors and methods:
- HelloWorldRequest from the HelloWorld service is available as a reference.
- Source code is located in ⁇ MIAWARE>/samples/java. Developers are urged to use this service as a template for their implementation.
- the following descriptions provide a walk-through of the HelloWorldRequest class to reveal required logic of a ServiceRequest implementation.
- the parse() method provides logic to extract content of a HelloWorld request document using a DOM parser.
- a DOM document object that represents the request XML is obtained from the XMLDocument class via miAwareRequest. All of the element and attribute values parsed from the document are stored in the instance variables or objects of supporting classes. For example, the RequestDoc and Content classes hold information given by the RequestDoc and Content elements. This information is accessible by the appropriate "get" methods.
- the toXMLDocumentO method is an implementation of the abstract method of miAwareRequest. It publishes the content (previously populated by the "set" methods) of the instance as XML using the XMLAttrList and XML Writer helper classes. The XML document conforms to the HelloWorld request DTD.
- a response envelope contains information of the locale and character encoding of the response document.
- ServiceResponse As a subclass of miAwareResponse, an implementation of ServiceResponse is required to provide logic for the following constructors and methods:
- a sample implementation class, Hello WorldResponse from the HelloWorld service is available as a reference.
- Source code is located in ⁇ MIAWARE>/samples/java. Developers are urged to use this service as a template for their implementation.
- the following descriptions provide a walk-through of the Hello WorldResponse class to reveal required logic of a ServiceResponse implementation.
- the ⁇ arse() method provides logic to extract content of a HelloWorld response document using a DOM parser. All of the element and attribute values parsed from the document are stored in the instance variables or objects of supporting classes. For example, the ResponseDoc and Content classes hold information given by the ResponseDoc and Content elements. This information is accessible by the appropriate "get" methods. Page 9 of 12 XML Publishing
- the toXMLDocument() method is an implementation of the abstract method of miAwareResponse. It publishes the content of the instance as XML using the XMLAttrList and XML Writer helper classes. The XML document conforms to the HelloWorld response DTD.
- New services can be distributed and installed on other miAware sites.
- the miAware Administrator Tool of the Enterprise Manager Console can be used to install services from a SPP. This requires components of a new service to be bundled in a Service Provider Package (SPP).
- SPP Service Provider Package
- the miAware Service Installer tool can be used to install services from a SPP.
- a sample SPP that contains all of the core services can be found in the ⁇ MI A WARE>/WEB -INF/packages directory.
- a Service Provider Package contains the following information: Page 10 of 12
- a miAwareSDD.xml file (Service Deployment Descriptor) that contains the definition of one or more services. Each service occupies an entry in the file and must conform to the DTD described below.
- the SDD file must be located at the root directory of the package.
- Each contains components of a service.
- the directory name is the name of service (e.g., RouteService) specified in the miAwareSDD.xml file.
- RouteService e.g., RouteService
- the structure and layout below depict the organization of the service components.
- miAwareSDD Root element of the service deployment descriptor that contains definitions of one or more miAware services.
- the Service Installer displays this information on the service configuration dialog.
- the Service Installer displays this information on the service configuration dialog.
- ServiceProvider interface For example, com.mapinfo.miAware.services.router.RouterService.
- the Service Installer displays this information on the service configuration dialog.
- Optional Specifies whether the property is optional ("true”) or mandatory ("false”). A mandatory property is highlighted on the service configuration dialog.
- a miAware Pass-Thru Service is used when a service provider wants to create an miAware service request that contains an request of another service or server which accept XML request.
- the Pass-Thru Service extracts a request content (or payload) from the request document in a miAware envelope, passes this payload to another server (thirdparty server) that accepts the xml request, processes the payload, and wraps the response payload back into a miAware envelope and returns the response document.
- the Pass-Thru Service treats any xml elements inside the miAware Envelope as the request or response content (payload), and will pass tins payload to and from the thirdparty server, not processing the information.
- RequestDTD This property indicates the URL of the dtd to parse information in the request xml that will be sent to the thirdparty server. If this property is missing, no dtd will be included in the xml to be sent to this server.
- ServerURL This property indicates the URL of the thirdparty server, which is going to handle the thirdparty xml request contained in the pass through request. It Page 2 of 3 can start with either "http:” or "https:”, which support normal http and SSL connections respectively.
- ServerURL is used when the service provider need to use a servlet connection to talk to the thirdparty server.
- ServerHost and ServerPort are used when a socket connection is required. If this property is missing, the PassThroughService will look for the ServerHost/ServerPort property, and try to use a socket connection to talk to the thirdparty server. If both the ServerURL and ServerHost/ServerPort are provided, the service provider will use servlet connection as a prior option.
- the miAware Pass-Thru service provides the ability to pass additional properties for thirdparty servers.
- Thirdparty servers may need additional connection properties when the Pass-Thru service attempts to connect to that server (these properties may be added to the miAwareServiceCatalog.xml file as service properties). All properties that are not predefined in the Pass-Thru service, such as RequestDTD, ResponseDTD, and ServerURL, will be treated as additional connection properties and will be used as the HTTP connection properties.
- Mapinfo MapMarker Java is used as the thirdparty server, it requires a connection property called "MI_XMLProtocolRequest".
- MI_XMLProtocolRequest a connection property called "MI_XMLProtocolRequest”.
- the Pass-Thru service catalog entry for a request to the MapMarker Java geocode server that sends a response back to the client may look like the following:
- MI_XMLProtocolRequest MI_XMLProtocolVersion
- MI_XMLProtocolTransactionId MI_XMLProtocolTransactionId properties
- the miAware Pass-Thru service provides the ability to perform pre and post processing on XML request and response documents. Tins however required the service provider developer to extend the Perform( ) Method in the Pass-Thru service, adding the required logic to do the pre and post processing.
- This example illustrates a new service that will inherit the PassThroughService and processes the payload before it is sent to the backend server and processes the XML response before it is sent to the client.
- miAware is the provider of Maplnfo's location enabled services over the Internet in the form of an extensible Markup Language Application Interface (XML- API). These services enable a collection of applications to manage information specific to mobile locations.
- XML- API forms the platform to tie together key services commonly used in the development of these mobile location applications.
- miAware services employ a request and response model based on the extensible Markup Language (XML) technology and the HTTP protocol. These miAware service requests and responses are XML documents governed by corresponding Document Type Definitions (DTDs).
- DTDs Document Type Definitions
- An XML document is returned after a service is rendered. This response document contains either the requested results or fault information if an error has occurred.
- the service XML API is a subset of the miAware XML API that provides among other things, common DTD's and an envelope for the request/response for all supported services. This envelope contains general information including authentication and common parameters (e.g., language settings).
- the miAware Client Package provides a Java API which can be used to communicate with a miAware server, publish a service-specific XML request, and extract results from a response document returned by miAware.
- Each of the miAware services provides specific request, response, and supporting classes that correspond to the elements defined by the DTDs for the particular service.
- the GeocodeRequest class is the Java representation of the GeocodeRequest element defined in the Geocoder.dtd.
- the GeocodeResponse class maps to the Page 2 of 8
- GeocodeResponse element All of the sub-elements referenced by these classes have their Java mappings available from the API.
- the purpose of the request class is to enable developers to construct and fill a service request XML document without having in-depth knowledge of the XML syntax.
- developers can instantiate a request object (e.g., GeocodeRequest) and use the provided "set" methods to fill the document based on their requirements. Once the object is populated, a well-formed and syntactically correct request can be published using the toXMLDocument method.
- This document can now be submitted to a miAware Server for processing, using another helper class named com.mapinfo.miAware.client.miAwareConnection.
- the miAwareConnection class takes a given document in the form of a String object, a File object, or an InputStream and submits it to a miAware server at the specified URL (e.g., http://milocate.mapinfo.com/miAware/servlet/miAware).
- the miAware server returns an XML document in a byte stream which contains either the results or a fault response if any e ⁇ ors were encountered.
- the purpose of the response class is to provide XML parsing of the response document so developers can extract the content using the supplied "get” methods.
- the objective is to ease the knowledge of the XML syntax.
- Sample client Java programs are available for each supported service. You can find these files in the ⁇ miAware_Client> /samples/java directory. Samples XML request and response documents are also available in ⁇ miAware_Client>/samples/xml. ⁇ miAware_Client> is the root directory where the miAware Client Package is installed.
- miAware uses the Apache's Xerces parser for XML parsing. For compatibility reasons, developers are urged to use this parser instead of a parser from another vendor.
- HTML-based documentation for miAware is available from ⁇ miAware_Client>/doc. It provides an overview of the miAware product, description of the XML API (DTDs) for each service, as well as javadocs for the services and client developer APIs. To view these documents, launch a web browser and open the ⁇ miAware_Client>/index.html page.
- DTDs XML API
- Java interfaces and classes for building a client application are located in the following packages: com.mapinfo.miAware.admin (Administration) com.mapinfo.miAware.client (Communication) com.mapinfo.miAware.common (Common XML elements) com.mapinfo.miAware.coordsys (Coordinate System Transformations) com.mapinfo.miAware.geom (Managing GML V2 Simple Geometries) com.mapinfo.miAware.xml (XML parsing/publishing) com.mapinfo.miAware.services (Services framework) com.mapinfo.miAware.services.FindLocation (Find-The-Nearest Service) com.mapinfo.miAware.services.FindNearest (Find-Location Service) com.mapinfo.miAware.services.Geocoder (Geocode Service)
- Geodecoder (Geodecode Service) com.mapinfo.miAware.services.Hello World (Sample Service) com.mapinfo.miAware.services.Position (Mobile Positioning Service) com.mapinfo.miAware.services.Profile (Profiling Service) com.mapinfo.miAware.services.Router (Route Service) com.mapinfo.miAware.services.Cogo (Coordinate Geometry Service) com.mapinfo.miAware.services.CoordSys (Coordinate System Service) com.mapinfo.miAware.services.Mapping (Mapping Service) com.mapinfo.miAware.services.PositionRefine (Position Refinement Service) Page 5 of 8 Communicate With The miAware Server
- the miAware server accepts requests as a HTTP/POST.
- a class named "miAwareConnection” is available in the com.mapinfo.miAware.client package.
- An object of this class is instantiated with a URL of the miAware server which will handle the request.
- File file new File ("c: /services/route.xml")
- InputStream miAware. submit (routeRequest) ;
- a response document is returned in a byte stream by the miAware server. You can either extract its content using your own parsing logic or make use of the service classes.
- a request document contains a header and a service request. Both of these must be contained within an envelope.
- Java classes available for creating these components. The example below describes step-by-step how to create a route request document using appropriate miAware classes:
- a header contains information of the requestor for authentication purposes. It also specifies the target service to be rendered.
- the com.mapinfo.miAware.common.Header class is the Java mapping of the Header element. The statement below instantiates a Header object for a route request with the requestor name and password being "demo" and "demo".
- the "mapinfo.com” parameter specifies the site of the requestor. Where "RouteService” is the name of a registered service known to the miAware server.
- Header header new Header ("demo” , “demo”, “mapinfo.com”, “RouteService”) ; Page 6 of 8
- the request envelop is managed by the com.mapinfo.miAware.services.RequestEnvelope class. It takes an ID and a Header object as input.
- the ID is an unique value supplied by the application which will be echoed back in the response document so that a specific request/response pair can be matched up in a asynchronous environment.
- There are other optional settings that can be set in the envelope such as the language binding of the document. Please refer to the XML- API document for details.
- RequestEnvelope envelope new RequestEnvelope ("1", header);
- the content of a request can be created from a service-specific request and its supporting classes. Which ones to use is based on the services supported by the application.
- the request object e.g., RouteRequest
- This object contains other objects that corresponds to elements (e.g., Itinerary, Point) defined by the service request DTD.
- elements e.g., Itinerary, Point
- RouteRequest request new RouteRequest (envelope) ;
- Point startLocation new Point (new Coord (-73.86668,
- Point endLocation new Point (new Coord(-73.87877,40.83081) ) ;
- Itinerary [] its new Itinerary [1] ; its [0] s new Itinerary ("1" , startLocation, endLocation); request. setltineraries (its) ;
- Service-specific response and supporting classes provide parsing logic that extracts content of a response document and makes it available through appropriate get" methods.
- the response object e.g., RouteResponse
- This object contains other objects that corresponds to elements (e.g., Route, Street) defined by the service response DTD.
- Below sample code that instantiates a route response object from an XML document with classes from the com.mapinfo.miAware.services.Router package.
- RouteResponse routeResp new RouteResponse (is) ;
- FaultResponse fault routeResp.getFaultResponse() ;
- Route [] routes routeResp.getRoutes () ; if (routes !s null) ⁇
- a LDAP directory is a repository that provides storage and fast access of object-oriented hierarchically structured information. Although this may sound like a database, the content and the structure of the directory is defined by the entries it contains (a directory generally contains or interacts with a database internally). A specific schema that contains object classes and attributes controls the type of information each entry may carry.
- an object class defines the collection of attributes that can be used to define an entry.
- the LDAP standard provides these basic types of object classes:
- LDAP is a repository for two distinct groups of information: enterprise-related and person-related.
- enterprise-related information is a list of devices and applications supported by an enterprise.
- person-related information LDAP will store specific information like personal details, enterprise assignments, location information, etc.
- Profile data is grouped under a logical root called Enterprise, identified by a unique name (e.g. miaware.com). Multiple enterprises can coexist, each containing a variation of information based on the same LDAP schema. An enterprise is subdivided into multiple groups in a hierarchical structure according to the information the group carries and their logical relationships between them. Page 2 of 4
- Some of these groups contain data for different geographic regions (e.g. US, UK), hence their content is further categorized by localities.
- a locality is a geographic division such as a county, country subdivision (e.g., state/province), or any political boundary. Groups that support locality will carry a locality data element that identifies entries for a specific locale.
- each profile group contains:
- Map Profile - Information enables MapXtreme Java to generate maps of pre-defined geographic regions with specific symbologies (e.g., marker of restaurants) at various scale levels.
- Person Profile - Information of a person within an enterprise This includes account information such as name, address, device information, and various preferences.
- Buddy Subscription Contains references of people who subscribed to the 'Buddy' service. Subscribers are able to choose other subscribers as their contacts, whom will be notified for events.
- Point-Of-Interest (POI) Profile Information that supports personalized content within an enterprise.
- a POI profile cascades into four levels: Theme, Group, Category, and Sub-category. Each level carries a unique code, a description, and an alias.
- a person can create their own POI profile by selecting various entries from the enterprise's POI.
- Organization Unit Logical grouping of people. Each organization unit is identified by a unique name (e.g., Engineering). A person can belong to multiple groups. For Page 3 of 4 example, Alex is a member of the Engineering, QA, and Documentation groups.
- An entry can belong to more than one object class.
- the entry for a person is defined by the person object class, but may also be defined by attributes in the inetOrgPerson, groupOfNames, and organization object classes.
- the server's object class structure determines the required and allowed attributes for a particular entry.
- a person entry may be defined by the following object class structure:
- the inetOrgperson object class should not be placed on an entry until the person and organizationalPerson object classes have been defined.
- the data populating a directory is represented as attribute-value pairs.
- the commonName, or en, attribute is used to store a person's name.
- John Doe can be represented in the directory as en: John Doe.
- LDAP In LDAP there are two types of attributes: required and allowed. Required attributes must be present in an entry, while allowed attributes are optional in an entry. Each attribute has a corresponding syntax definition.
- the syntax definition describes the type of information the attribute contains.
- the syntax of the attribute is used by LDAP to perform various sorting and matching operations. The table below describes the attribute syntax types:
- Binary bin Values for this attribute are binary.
- Boolean boolean This attribute may have two values: On or off, True or False, Yes or No.
- Telephone tel Values for this attribute are telephone numbers (identical to cis, but blanks and dashes are ignored during comparisons).
- Distinguished Name dn Values for this attribute are distinguished names.
- Integer int Values for this attribute are numbers.
- the miAware LDAP schema includes many object classes and attributes that may be used to meet most directory server requirements. This schema may be extended with new object classes and attributes to meet evolving requirements for the directory service. When adding a new attribute to the schema, a new object class should be created to extend the attribute. Adding a new attribute to an existing object class may compromise the server's compatibility with existing clients that rely on the standard LDAP schema, and may cause problems with the server when trying to upgrade.
- miaddrpostalcode ente ⁇ rise postal code miaddrpostalcodeaddon ente ⁇ rise postal code add-on
- Name Description ou locality container (ou stands for organizational unit. LDAP use this attribute to provide a logical unit for multiple entries of the same type) description locality container description
- Name Description en device identifier or name description device description e.g., iPAQ
- midevicetypeid device type e.g., Phone, Palm, or other device mideviceresolution device resolution WxH e.g., 640x480 Page 5 of 21 midevicecolormodel device color model e.g., bw, color, or greyscale mideviceimageformat device image format e.g., jpg, bmp, wbmp, tiff, png, __t _, mideviceparameters holds specific parameters for applications midevicemodel evice model e.g., iPAQ, iDEN, or other device
- miappname application name miapptype type of application e.g., application or service mideviceref reference to the device that : supports this application milocality reference to the locality where this application is available miappparam application specific configuration parameters url location where a new version of the application is available for download miappreleasedate application release date
- a personal profile contains entries for a person in the ente ⁇ rise PersonProfile.
- a Person Profile includes account information, personal data, service provider specific data, a collection of applications installed, a list of all devices owned by a person, location information, and rules for position access control.
- Installed applications A list of installed applications. An entry contains installation date, references to application profile related entries (dn), and a short description.
- Devices A list of owned devices. Each entry contains a reference to a device profile entry, state of device (ON/OFF/OUT OF SERVICE), and a device identifier assigned by the ca ⁇ ier provider.
- Mobile location information A limited list of entries describing a person's position or coordinates at a given time. A maximum number of entries in a mobile location container for each person is specifed. A typical entry in mobile location specifies the position at a distinct moment.
- Possition access control Contains rules controlled by a person filtering access from outside.
- Name Description uid user account identifier must be unique in PersonProfile for this directory instance use ⁇ assword user account password sn last name en first name mail person's email address url person's web page telephonenumber phone numbers, could be multiple facsimiletelephonenumber person's fax number
- Name Description description person's description mibuddyref reference to a buddy of this person in the buddy service could be multiple mideviceref reference to device profile entries (dn) mipersonappinstalldate date of application installation mipersonappref reference to application profile entries (dn) mipersondeviceid identifier for a person's device mipersonfoldref reference to a person's folder in a locationbook container mipersongroupref reference to the organizationalunit group in which this person is member SMS address mipersonsmsaddress SMS address mipersonmmsaddress MMS address, can be a phone#, IP or email address en common name for this person, for contact definition this is the company name
- mibuddyref points to a PersonProfile YES entry that belongs to buddy mipersonfoldref points to a corresponding YES locationbook entry mipersonappref points to an YES ApplicationProfile entry (for apps installed by person) mideviceref points to a DeviceProfile YES entry (for devices owned by a person)
- a location book profile may contain multiple folders that can be defined, populated, and updated by its owner. Inside each folder a person can store one or more contacts (individuals or companies).
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Mobile Radio Communication Systems (AREA)
- Information Transfer Between Computers (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP03719430.5A EP1488646B1 (en) | 2002-03-19 | 2003-03-19 | Location based service provider |
AU2003223314A AU2003223314B2 (en) | 2002-03-19 | 2003-03-19 | Location based service provider |
CA2479838A CA2479838C (en) | 2002-03-19 | 2003-03-19 | Location based service provider |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US36582002P | 2002-03-19 | 2002-03-19 | |
US60/365,820 | 2002-03-19 | ||
US37880502P | 2002-05-07 | 2002-05-07 | |
US60/378,805 | 2002-05-07 | ||
US41143502P | 2002-09-17 | 2002-09-17 | |
US60/411,435 | 2002-09-17 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2003081391A2 true WO2003081391A2 (en) | 2003-10-02 |
WO2003081391A3 WO2003081391A3 (en) | 2004-02-05 |
Family
ID=28457770
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2003/008628 WO2003081391A2 (en) | 2002-03-19 | 2003-03-19 | Location based service provider |
Country Status (5)
Country | Link |
---|---|
US (2) | US7386318B2 (en) |
EP (1) | EP1488646B1 (en) |
AU (1) | AU2003223314B2 (en) |
CA (1) | CA2479838C (en) |
WO (1) | WO2003081391A2 (en) |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2007068986A2 (en) * | 2005-12-16 | 2007-06-21 | Kate-Kom D.O.O. | Device and procedure for managing short lived and free created content for value added telecomunication services |
WO2008113162A1 (en) * | 2007-03-19 | 2008-09-25 | Redknee Inc. | Extensible data repository |
EP2192568A1 (en) * | 2007-09-13 | 2010-06-02 | Mitsubishi Electric Corporation | Map drawing device |
US8620532B2 (en) | 2009-03-25 | 2013-12-31 | Waldeck Technology, Llc | Passive crowd-sourced map updates and alternate route recommendations |
US9366542B2 (en) | 2005-09-23 | 2016-06-14 | Scenera Technologies, Llc | System and method for selecting and presenting a route to a user |
US9736618B1 (en) | 2005-04-04 | 2017-08-15 | X One, Inc. | Techniques for sharing relative position between mobile devices |
CN109145073A (en) * | 2018-08-28 | 2019-01-04 | 成都市映潮科技股份有限公司 | A kind of address resolution method and device based on segmentation methods |
US20210180979A1 (en) * | 2018-08-31 | 2021-06-17 | Denso Corporation | Vehicle-side device, method, and non-transitory computer-readable storage medium for uploading map data |
US20210248636A1 (en) * | 2018-07-27 | 2021-08-12 | Ki Eob PARK | Distributed network system for operating group for nodes included in system |
Families Citing this family (176)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6505123B1 (en) | 2000-07-24 | 2003-01-07 | Weatherbank, Inc. | Interactive weather advisory system |
US7512932B2 (en) * | 2002-03-22 | 2009-03-31 | Sun Microsystems, Inc. | Language and object model for describing MIDlets |
US20030182626A1 (en) * | 2002-03-22 | 2003-09-25 | Eran Davidov | On-demand creation of MIDlets |
US20060149624A1 (en) * | 2004-12-30 | 2006-07-06 | Shumeet Baluja | Generating and/or serving local area advertisements, such as advertisements for devices with call functionality |
US8427303B1 (en) | 2002-06-27 | 2013-04-23 | Geomass Limited Liability Company | System and method for providing media content having attributes matching a user's stated preference |
US8102253B1 (en) | 2002-06-27 | 2012-01-24 | Earthcomber, Llc | System and method for notifying a user of people, places or things having attributes matching a user's stated preference |
US7071842B1 (en) | 2002-06-27 | 2006-07-04 | Earthcomber, Llc | System and method for locating and notifying a user of a person, place or thing having attributes matching the user's stated preferences |
US11257094B2 (en) | 2002-10-23 | 2022-02-22 | Catalina Marketing Corporation | System and method of a media delivery services platform for targeting consumers in real time |
US8626130B2 (en) * | 2005-08-23 | 2014-01-07 | Modiv Media, Inc. | System and method for user controlled log-in; interacting and log-out |
US9811836B2 (en) | 2002-10-23 | 2017-11-07 | Modiv Media, Inc | System and method of a media delivery services platform for targeting consumers in real time |
US10657561B1 (en) | 2008-08-20 | 2020-05-19 | Modiv Media, Inc. | Zone tracking system and method |
US8783561B2 (en) | 2006-07-14 | 2014-07-22 | Modiv Media, Inc. | System and method for administering a loyalty program and processing payments |
US10430798B2 (en) | 2002-10-23 | 2019-10-01 | Matthew Volpi | System and method of a media delivery services platform for targeting consumers in real time |
US7761386B2 (en) * | 2003-06-15 | 2010-07-20 | Mordechai Teicher | Method and apparatus for arranging social meetings |
US7305398B2 (en) * | 2003-06-15 | 2007-12-04 | Mordechai Teicher | Apparatus and method for managing social games |
US8090602B2 (en) * | 2003-06-15 | 2012-01-03 | Mordechai Teicher | Method and apparatus for leisure and entertainment merchandising |
US7330112B1 (en) * | 2003-09-09 | 2008-02-12 | Emigh Aaron T | Location-aware services |
US7818317B1 (en) | 2003-09-09 | 2010-10-19 | James Roskind | Location-based tasks |
US7849075B2 (en) | 2003-09-15 | 2010-12-07 | Ab Initio Technology Llc | Joint field profiling |
US7296026B2 (en) * | 2003-12-15 | 2007-11-13 | J2 Global Communications | Method and apparatus for automatically performing an online content distribution campaign |
US7512125B2 (en) * | 2003-12-19 | 2009-03-31 | Solace Systems, Inc. | Coding of routing protocol messages in markup language |
US20050193106A1 (en) * | 2004-03-01 | 2005-09-01 | University Of Florida | Service discovery and delivery for ad-hoc networks |
US8509814B1 (en) * | 2004-03-24 | 2013-08-13 | Sprint Spectrum L.P. | Method and system for integrating location based services into retail applications |
US7532899B2 (en) | 2004-04-15 | 2009-05-12 | At&T Mobility Ii Llc | System for providing location-based services in a wireless network, such as locating sets of desired locations |
US7693752B2 (en) | 2004-05-26 | 2010-04-06 | Hothand, Inc. | Mobile commerce framework |
US10032452B1 (en) | 2016-12-30 | 2018-07-24 | Google Llc | Multimodal transmission of packetized data |
US8843931B2 (en) | 2012-06-29 | 2014-09-23 | Sap Ag | System and method for identifying business critical processes |
US7647024B2 (en) | 2005-10-03 | 2010-01-12 | Sellerbid, Inc. | Method and system for improving client server transmission over fading channel with wireless location and authentication technology via electromagnetic radiation |
US7603131B2 (en) | 2005-08-12 | 2009-10-13 | Sellerbid, Inc. | System and method for providing locally applicable internet content with secure action requests and item condition alerts |
US20060046743A1 (en) * | 2004-08-24 | 2006-03-02 | Mirho Charles A | Group organization according to device location |
SE528585C2 (en) * | 2004-09-21 | 2006-12-19 | Ericsson Telefon Ab L M | Method and systems for providing position-based services in a cellular communication network |
US7308251B2 (en) * | 2004-11-19 | 2007-12-11 | Broadcom Corporation | Location-based authentication of wireless terminal |
US7627425B2 (en) | 2004-11-26 | 2009-12-01 | Microsoft Corporation | Location aware mobile-device software development |
US20060123014A1 (en) * | 2004-12-07 | 2006-06-08 | David Ng | Ranking Internet Search Results Based on Number of Mobile Device Visits to Physical Locations Related to the Search Results |
US20060235856A1 (en) * | 2004-12-16 | 2006-10-19 | Halcrow Michael A | Route generation for task completion by a location-aware device |
US20060161469A1 (en) * | 2005-01-14 | 2006-07-20 | Weatherbank, Inc. | Interactive advisory system |
US8832121B2 (en) * | 2005-02-02 | 2014-09-09 | Accuweather, Inc. | Location-based data communications system and method |
US7725112B2 (en) * | 2005-02-08 | 2010-05-25 | Nokia Corporation | System and method for provision of proximity networking activity information |
JP4742660B2 (en) * | 2005-04-25 | 2011-08-10 | 富士ゼロックス株式会社 | Document processing system |
EP1720031A1 (en) * | 2005-05-04 | 2006-11-08 | Siemens Aktiengesellschaft | A method for providing a service to a terminal, the corresponding system and apparatus |
US7848765B2 (en) | 2005-05-27 | 2010-12-07 | Where, Inc. | Location-based services |
US9118774B2 (en) | 2005-07-21 | 2015-08-25 | Google Inc. | Dispatch system to remote devices |
US20070033089A1 (en) * | 2005-08-04 | 2007-02-08 | Microsoft Corporation | User interface and geo-parsing data structure |
US8160614B2 (en) * | 2005-08-05 | 2012-04-17 | Targus Information Corporation | Automated concierge system and method |
US7702545B1 (en) * | 2005-09-08 | 2010-04-20 | Amazon Technologies, Inc. | System and method for facilitating exchanges between buyers and sellers |
GB2430506A (en) * | 2005-09-21 | 2007-03-28 | Ibm | Content management system |
US20070073694A1 (en) * | 2005-09-26 | 2007-03-29 | Jerome Picault | Method and apparatus of determining access rights to content items |
WO2007053687A2 (en) * | 2005-11-01 | 2007-05-10 | Vesco Oil Corporation | Audio-visual point-of-sale presentation system and method directed toward vehicle occupant |
KR100772184B1 (en) | 2005-12-01 | 2007-11-01 | 한국전자통신연구원 | System and Method for providing navigation service using open API |
US7840567B2 (en) * | 2006-01-17 | 2010-11-23 | International Business Machines Corporation | Method and apparatus for deriving optimal physical space and ambiance conditions |
US8229467B2 (en) | 2006-01-19 | 2012-07-24 | Locator IP, L.P. | Interactive advisory system |
WO2007085023A2 (en) * | 2006-01-20 | 2007-07-26 | Josef Berger | Systems and methods for operating communication processes using a personalized communication web server |
US7702456B2 (en) | 2006-04-14 | 2010-04-20 | Scenera Technologies, Llc | System and method for presenting a computed route |
US8910044B1 (en) | 2006-08-22 | 2014-12-09 | Aaron T. Emigh | Playlist incorporating tags |
US20080059299A1 (en) * | 2006-09-01 | 2008-03-06 | Admob,Inc. | Delivering ads to mobile devices |
US7925982B2 (en) * | 2006-09-01 | 2011-04-12 | Cheryl Parker | System and method of overlaying and integrating data with geographic mapping applications |
JP2010503928A (en) * | 2006-09-12 | 2010-02-04 | ウェイポート,インコーポレーテッド | Deliver location-based services in a distributed environment without direct control through access points |
US8087088B1 (en) * | 2006-09-28 | 2011-12-27 | Whitehat Security, Inc. | Using fuzzy classification models to perform matching operations in a web application security scanner |
US8826139B1 (en) | 2007-02-02 | 2014-09-02 | Resource Consortium Limited | Searchable message board |
KR100867992B1 (en) | 2006-12-08 | 2008-11-10 | 한국전자통신연구원 | System for providing address service using Geocoding API in open service platform and method using the same |
US20080147652A1 (en) * | 2006-12-14 | 2008-06-19 | Bellsouth Intellectual Property Corporation | Physical address verification within electronic documents |
US8364689B2 (en) * | 2006-12-22 | 2013-01-29 | Verizon Patent And Licensing Inc. | Methods and apparatus for providing a location based search |
US7768395B2 (en) * | 2007-01-19 | 2010-08-03 | Gold Steven K | Brand mapping |
US8634814B2 (en) | 2007-02-23 | 2014-01-21 | Locator IP, L.P. | Interactive advisory system for prioritizing content |
US7941764B2 (en) * | 2007-04-04 | 2011-05-10 | Abo Enterprises, Llc | System and method for assigning user preference settings for a category, and in particular a media category |
US8688368B2 (en) * | 2007-04-09 | 2014-04-01 | Microsoft Corporation | Image-based localization for addresses |
SE0700918L (en) * | 2007-04-16 | 2008-10-17 | Teliasonera Ab | Device, method and method of telecommunication and data communication systems |
US7996148B2 (en) * | 2007-05-10 | 2011-08-09 | Avi Bergman | System and method for obtaining map coordinates to fixed location |
US20080313037A1 (en) * | 2007-06-15 | 2008-12-18 | Root Steven A | Interactive advisory system |
US9141960B2 (en) * | 2007-06-22 | 2015-09-22 | Varia Holdings Llc | Venue and event recommendations for a user of a portable media player device |
US8165087B2 (en) * | 2007-06-30 | 2012-04-24 | Microsoft Corporation | Location context service handoff |
US8050690B2 (en) | 2007-08-14 | 2011-11-01 | Mpanion, Inc. | Location based presence and privacy management |
US8583079B2 (en) | 2007-08-14 | 2013-11-12 | Mpanion, Inc. | Rich presence status based on location, activity, availability and transit status of a user |
US8489111B2 (en) * | 2007-08-14 | 2013-07-16 | Mpanion, Inc. | Real-time location and presence using a push-location client and server |
US8504450B2 (en) * | 2007-08-31 | 2013-08-06 | Ebay Inc. | Mobile remittances/payments |
US20100274475A1 (en) * | 2007-09-25 | 2010-10-28 | Route 66 Switzerland Gmbh | System and method for providing navigational information |
US8254961B2 (en) * | 2007-10-23 | 2012-08-28 | Verizon Patent And Licensing Inc. | Retail-related services for mobile devices |
EP2214439A1 (en) * | 2007-10-31 | 2010-08-04 | Mitsubishi Electric Corporation | Mobile communication system, base station, mobile station, and base station installation method |
US20090177523A1 (en) * | 2008-01-07 | 2009-07-09 | Michael Routtenberg | System And Method For Compiling Market Information Associated With Consumer Activity And Geographic Location |
US20090204672A1 (en) * | 2008-02-12 | 2009-08-13 | Idelix Software Inc. | Client-server system for permissions-based locating services and location-based advertising |
JP4535163B2 (en) * | 2008-04-08 | 2010-09-01 | ソニー株式会社 | Information processing system, communication terminal, information processing apparatus, and program |
US20090307263A1 (en) * | 2008-06-06 | 2009-12-10 | Sense Networks, Inc. | System And Method Of Performing Location Analytics |
KR101063287B1 (en) * | 2008-06-10 | 2011-09-07 | 삼성전자주식회사 | Method and system for providing service information using location information |
TWI442319B (en) * | 2008-09-08 | 2014-06-21 | Mitac Int Corp | The method of receiving and sending the service activity message and its portable electronic device and service platform |
US8001174B2 (en) * | 2008-09-17 | 2011-08-16 | Calamp Corp. | Application process in communication system using central processor for forwarding request to destination processor based on connection status |
EP2169570A1 (en) * | 2008-09-25 | 2010-03-31 | Infogin LTD | Mobile sites detection and handling |
US7984151B1 (en) | 2008-10-09 | 2011-07-19 | Google Inc. | Determining placement of user data to optimize resource utilization for distributed systems |
US9143934B2 (en) * | 2008-11-25 | 2015-09-22 | Lance Parker Ip, Llc | System and method for remote control of a mobile device |
US9113342B1 (en) * | 2008-11-25 | 2015-08-18 | Dominic M. Kotab | Methods for determining and displaying a local page for a mobile device and systems thereof |
US8494560B2 (en) * | 2008-11-25 | 2013-07-23 | Lansing Arthur Parker | System, method and program product for location based services, asset management and tracking |
US9143923B2 (en) * | 2008-11-25 | 2015-09-22 | II Lansing Arthur Parker | System and method for remote control of a mobile device |
US8621089B2 (en) * | 2008-12-23 | 2013-12-31 | Verizon Patent And Licensing Inc. | Method and system for providing supplemental visual content |
US9742821B2 (en) | 2008-12-23 | 2017-08-22 | Verizon Patent And Licensing Inc. | Method and system for dynamic content delivery |
US8433998B2 (en) * | 2009-01-16 | 2013-04-30 | International Business Machines Corporation | Tool and method for annotating an event map, and collaborating using the annotated event map |
US20110113100A1 (en) * | 2009-03-21 | 2011-05-12 | Mpanion, Inc. | System for sharing favorites and enabling in-network local search based on network rankings |
US20100278379A1 (en) * | 2009-05-01 | 2010-11-04 | Lmr Inventions, Llc | Location based image acquisition |
US8194541B2 (en) | 2009-05-29 | 2012-06-05 | Nokia Corporation | Method and apparatus for providing a collaborative reply over an ad-hoc mesh network |
US8135735B2 (en) | 2009-07-10 | 2012-03-13 | Geodex, Llc | Computerized system and method for tracking the geographic relevance of website listings and providing graphics and data regarding the same |
US9201973B2 (en) * | 2009-07-10 | 2015-12-01 | Geodex Llc | Computerized system and method for tracking the geographic relevance of website listings and providing graphics and data regarding the same |
US20110029352A1 (en) * | 2009-07-31 | 2011-02-03 | Microsoft Corporation | Brokering system for location-based tasks |
KR20110039905A (en) * | 2009-10-12 | 2011-04-20 | 삼성전자주식회사 | Method and system for providing advertising |
US8560608B2 (en) | 2009-11-06 | 2013-10-15 | Waldeck Technology, Llc | Crowd formation based on physical boundaries and other rules |
KR101270747B1 (en) * | 2009-11-19 | 2013-06-03 | 한국전자통신연구원 | Apparatus and Method for recommending service |
US20120063367A1 (en) | 2009-12-22 | 2012-03-15 | Waldeck Technology, Llc | Crowd and profile based communication addresses |
US8688502B2 (en) * | 2010-02-24 | 2014-04-01 | Oracle International Corporation | Business intelligence dashboards for performance analysis |
US20110205231A1 (en) * | 2010-02-24 | 2011-08-25 | Oracle International Corporation | Mapping data in enterprise applications for operational visibility |
US9020534B2 (en) * | 2010-02-25 | 2015-04-28 | Qualcomm Incorporated | Location-based mobile device profile aggregation |
WO2011109751A1 (en) * | 2010-03-05 | 2011-09-09 | The Dun And Bradstreet Corporation | Location-aware business data retrieval |
US8874710B2 (en) * | 2010-04-27 | 2014-10-28 | Nokia Corporation | Access network discovery |
US8463247B2 (en) * | 2010-06-08 | 2013-06-11 | Verizon Patent And Licensing Inc. | Location-based dynamic hyperlinking methods and systems |
US20120003964A1 (en) * | 2010-06-30 | 2012-01-05 | Armstrong Soo | Method, System, and Computer Program Product for Providing Customized Information to Mobile Devices |
US8433335B2 (en) | 2010-06-30 | 2013-04-30 | Research In Motion Limited | Method and apparatus for sharing information from a communication device |
US20120036444A1 (en) * | 2010-07-01 | 2012-02-09 | Andersen Ann-Cabell Baum | Systems and Methods for Interactive Web-based Social Networking and Activities Coordination |
KR20120015888A (en) * | 2010-08-13 | 2012-02-22 | 삼성전자주식회사 | Mobile device and control method thereof |
KR101681098B1 (en) * | 2010-08-16 | 2016-12-01 | 삼성전자주식회사 | Method for providing local service using local service information server based on distributed network and terminal apparatus |
US8804574B2 (en) * | 2010-10-01 | 2014-08-12 | Telefonaktiebolaget L M Ericsson (Publ) | Language dependent positioning and signalling |
US8452837B2 (en) * | 2010-11-03 | 2013-05-28 | Google Inc. | Data delivery |
US20120123870A1 (en) * | 2010-11-16 | 2012-05-17 | Genband Inc. | Systems and methods for enabling personalization of data service plans |
US20120158445A1 (en) * | 2010-12-16 | 2012-06-21 | Cox Communications, Inc. | Geo-Spatial Mapping and Service Provision Analysis |
US8930391B2 (en) | 2010-12-29 | 2015-01-06 | Microsoft Corporation | Progressive spatial searching using augmented structures |
KR101889120B1 (en) | 2011-01-28 | 2018-08-16 | 아브 이니티오 테크놀로지 엘엘시 | Generating data pattern information |
US9848290B2 (en) * | 2011-03-10 | 2017-12-19 | Aruba Networks, Inc. | Location based computerized system and method thereof |
US8874750B2 (en) * | 2011-03-29 | 2014-10-28 | Mobitv, Inc. | Location based access control for content delivery network resources |
US8538679B1 (en) | 2011-04-08 | 2013-09-17 | Oberweis Dairy, Inc. | Enhanced geocoding |
US8650024B1 (en) * | 2011-04-13 | 2014-02-11 | Google Inc. | Generating address term synonyms |
US20140323159A1 (en) * | 2011-11-09 | 2014-10-30 | Rockstar Consortium Us Lp | Method and system for providing relevant information to a mobile device |
US9779450B2 (en) | 2011-12-13 | 2017-10-03 | Ebay Inc. | Mobile application to conduct an auction based on physical presence |
US8850575B1 (en) * | 2011-12-30 | 2014-09-30 | Emc Corporation | Geolocation error tracking in transaction processing |
JP2015510637A (en) * | 2012-02-01 | 2015-04-09 | マパス インテリジェンツ,エルエルシー | Geocoding of points of interest and service route delivery as well as audit site performance and sales methods and equipment |
US20130244685A1 (en) | 2012-03-14 | 2013-09-19 | Kelly L. Dempski | System for providing extensible location-based services |
US9922334B1 (en) | 2012-04-06 | 2018-03-20 | Google Llc | Providing an advertisement based on a minimum number of exposures |
US20130277422A1 (en) * | 2012-04-22 | 2013-10-24 | Abb Inc. | System and method for requesting and delivering targeted information |
RU2012116582A (en) * | 2012-04-25 | 2013-10-27 | Неирон.Ком.Лимитед | METHOD AND SYSTEM OF USER INFORMATION ABOUT GOODS AND (OR) SERVICES AND MACHINE READABLE MEDIA |
US10776830B2 (en) | 2012-05-23 | 2020-09-15 | Google Llc | Methods and systems for identifying new computers and providing matching services |
US10152723B2 (en) | 2012-05-23 | 2018-12-11 | Google Llc | Methods and systems for identifying new computers and providing matching services |
CN104704797B (en) | 2012-08-10 | 2018-08-10 | 纽昂斯通讯公司 | Virtual protocol communication for electronic equipment |
US11184448B2 (en) * | 2012-08-11 | 2021-11-23 | Federico Fraccaroli | Method, system and apparatus for interacting with a digital work |
US9031579B2 (en) * | 2012-10-01 | 2015-05-12 | Mastercard International Incorporated | Method and system for providing location services |
JP6357162B2 (en) | 2012-10-22 | 2018-07-11 | アビニシオ テクノロジー エルエルシー | Data profiling using location information |
US9137631B2 (en) | 2012-12-27 | 2015-09-15 | Pitney Bowes Inc. | Location-based service provider method and system having a user controlled location privacy mechanism |
US10735552B2 (en) | 2013-01-31 | 2020-08-04 | Google Llc | Secondary transmissions of packetized data |
US10650066B2 (en) | 2013-01-31 | 2020-05-12 | Google Llc | Enhancing sitelinks with creative content |
US9892026B2 (en) | 2013-02-01 | 2018-02-13 | Ab Initio Technology Llc | Data records selection |
US9317872B2 (en) | 2013-02-06 | 2016-04-19 | Muzak Llc | Encoding and decoding an audio watermark using key sequences comprising of more than two frequency components |
US20140279053A1 (en) * | 2013-03-14 | 2014-09-18 | Did-It | System and method for applying spatially indexed data to digital advertising bids |
US9084218B2 (en) | 2013-05-23 | 2015-07-14 | Pitney Bowes Inc. | Location-based service provider method and system having a user controlled location privacy mechanism |
US9351105B2 (en) | 2013-07-02 | 2016-05-24 | Sap Se | Location based applications |
CN110602807B (en) * | 2013-09-26 | 2022-09-20 | 弗思特费斯有限公司 | Method for controlling main interface of communication terminal, communication terminal and computer readable storage medium |
US9208204B2 (en) * | 2013-12-02 | 2015-12-08 | Qbase, LLC | Search suggestions using fuzzy-score matching and entity co-occurrence |
US20170017501A1 (en) * | 2013-12-16 | 2017-01-19 | Nuance Communications, Inc. | Systems and methods for providing a virtual assistant |
JP2015115024A (en) * | 2013-12-16 | 2015-06-22 | コニカミノルタ株式会社 | Profile management system, information equipment, profile update method, and computer program |
WO2015094262A1 (en) * | 2013-12-19 | 2015-06-25 | Hewlett-Packard Development Company, L.P. | Personalized shopping and routing |
US11487732B2 (en) | 2014-01-16 | 2022-11-01 | Ab Initio Technology Llc | Database key identification |
EP3594821B1 (en) | 2014-03-07 | 2023-08-16 | AB Initio Technology LLC | Managing data profiling operations related to data type |
US20170286684A1 (en) * | 2014-05-30 | 2017-10-05 | Beestripe Llc | Method for Identifying and Removing Malicious Software |
WO2015184431A1 (en) * | 2014-05-30 | 2015-12-03 | Vioozer Inc. | System and process for location-based informationretrieval |
CN103984764B (en) * | 2014-05-30 | 2017-03-08 | 石家庄铁道大学 | Perceive the personalized method for secret protection of query semantics based on road network |
US9787560B2 (en) | 2015-06-04 | 2017-10-10 | Microsoft Technology Licensing Llc | Effective service node traffic routing |
US10305996B2 (en) * | 2015-12-07 | 2019-05-28 | Prn Productions, Inc. | System, device, and method for service coordination |
KR102321903B1 (en) | 2016-02-17 | 2021-11-05 | 위드인마일, 인크. | System for managing communication portal based on geographical address, communication portal server and managing method thereof |
US11068791B2 (en) * | 2016-09-14 | 2021-07-20 | International Business Machines Corporation | Providing recommendations utilizing a user profile |
US20180150923A1 (en) * | 2016-11-30 | 2018-05-31 | Corelogic Solutions, Llc | Property study workflow system |
US10593329B2 (en) | 2016-12-30 | 2020-03-17 | Google Llc | Multimodal transmission of packetized data |
US10708313B2 (en) | 2016-12-30 | 2020-07-07 | Google Llc | Multimodal transmission of packetized data |
JP6908948B2 (en) * | 2017-08-14 | 2021-07-28 | ウィズインマイル, インク.Withinmile, Inc. | Communication portal management system, communication portal server and portal server management method |
US11068540B2 (en) | 2018-01-25 | 2021-07-20 | Ab Initio Technology Llc | Techniques for integrating validation results in data profiling and related systems and methods |
WO2019157149A1 (en) | 2018-02-12 | 2019-08-15 | The Chamberlain Group, Inc. | Movable barrier operator having updatable security protocol |
US10327098B1 (en) * | 2018-04-30 | 2019-06-18 | Paypal, Inc. | Locations platform for managing and providing of user experiences |
US11028633B2 (en) | 2018-12-06 | 2021-06-08 | The Chamberlain Group, Inc. | Automatic control of a movable barrier |
US10837217B2 (en) | 2019-01-24 | 2020-11-17 | The Chamberlain Group, Inc. | Movable barrier imminent motion notification system and method |
US10846956B2 (en) | 2019-01-24 | 2020-11-24 | The Chamberlain Group, Inc. | Movable barrier imminent motion notification system and method |
US11200285B2 (en) * | 2019-04-11 | 2021-12-14 | Sap Se | Geocoding administrative areas with user-defined content |
US11578527B2 (en) | 2019-07-08 | 2023-02-14 | The Chamberlain Group Llc | In-vehicle device for controlling a movable barrier operator |
CN111431968B (en) * | 2020-02-26 | 2021-09-21 | 华为技术有限公司 | Cross-device distribution method of service elements, terminal device and storage medium |
US11601209B2 (en) * | 2020-11-25 | 2023-03-07 | At&T Intellectual Property I, L.P. | Modeling radio wave propagation in a fifth generation (5G) or other next generation network |
WO2022160036A1 (en) * | 2021-01-29 | 2022-08-04 | Groupe Beatconnect Inc. | Shared digital environment for music production, creation, sharing and the like |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2000004730A1 (en) | 1998-07-20 | 2000-01-27 | Signalsoft Corp. | Subscriber delivered location-based services |
CA2416253A1 (en) | 2000-07-28 | 2002-02-07 | American Calcar Inc. | Technique for effective organization and communication of information |
WO2002017567A2 (en) | 2000-08-25 | 2002-02-28 | Yogogo Limited | Wireless communications system with location-dependent services |
WO2002017654A2 (en) | 2000-08-22 | 2002-02-28 | Telefonaktiebolaget L.M. Ericsson (Publ) | Systems, methods and computer program products for identifying items of interest that are geographically proximate to wireless communicator users |
Family Cites Families (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH01214711A (en) * | 1988-02-23 | 1989-08-29 | Toshiba Corp | Navigation apparatus |
AU2261292A (en) * | 1991-06-21 | 1993-01-25 | Unitech Research, Inc. | Real time three dimensional geo-referenced digital orthophotograph-based positioning, navigation, collision avoidance and decision support system |
US5603031A (en) * | 1993-07-08 | 1997-02-11 | General Magic, Inc. | System and method for distributed computation based upon the movement, execution, and interaction of processes in a network |
US5470233A (en) * | 1994-03-17 | 1995-11-28 | Arkenstone, Inc. | System and method for tracking a pedestrian |
US5796634A (en) * | 1997-04-01 | 1998-08-18 | Bellsouth Corporation | System and method for identifying the geographic region of a geographic area which contains a geographic zone associated with a location |
US6363411B1 (en) * | 1998-08-05 | 2002-03-26 | Mci Worldcom, Inc. | Intelligent network |
US6101496A (en) * | 1998-06-08 | 2000-08-08 | Mapinfo Corporation | Ordered information geocoding method and apparatus |
US6292743B1 (en) * | 1999-01-06 | 2001-09-18 | Infogation Corporation | Mobile navigation system |
US6516337B1 (en) * | 1999-10-14 | 2003-02-04 | Arcessa, Inc. | Sending to a central indexing site meta data or signatures from objects on a computer network |
US6604046B1 (en) * | 1999-10-20 | 2003-08-05 | Objectfx Corporation | High-performance server architecture, methods, and software for spatial data |
US6373817B1 (en) * | 1999-12-30 | 2002-04-16 | At&T Corp. | Chase me system |
US20020000999A1 (en) * | 2000-03-30 | 2002-01-03 | Mccarty John M. | Address presentation system interface |
US6552670B2 (en) * | 2000-05-26 | 2003-04-22 | Switchboard Incorporated | Location encoder |
US6542749B2 (en) * | 2000-06-10 | 2003-04-01 | Telcontar | Method and system for connecting proximately located mobile users based on compatible attributes |
US20020055852A1 (en) * | 2000-09-13 | 2002-05-09 | Little Erik R. | Provider locating system and method |
US6484033B2 (en) * | 2000-12-04 | 2002-11-19 | Motorola, Inc. | Wireless communication system for location based schedule management and method therefor |
US20020111154A1 (en) * | 2001-02-14 | 2002-08-15 | Eldering Charles A. | Location based delivery |
US6944447B2 (en) * | 2001-04-27 | 2005-09-13 | Accenture Llp | Location-based services |
US7340691B2 (en) * | 2001-06-25 | 2008-03-04 | International Business Machines Corporation | Method, system, and program for accessing calendar information for shadowed users from a database |
US7068189B2 (en) * | 2001-07-03 | 2006-06-27 | Nortel Networks Limited | Location and event triggered notification services |
US7010779B2 (en) * | 2001-08-16 | 2006-03-07 | Knowledge Dynamics, Inc. | Parser, code generator, and data calculation and transformation engine for spreadsheet calculations |
EP1286558A1 (en) * | 2001-08-20 | 2003-02-26 | Alcatel | Mobile radio network and terminal for location-dependent services |
EP1320270A1 (en) * | 2001-12-11 | 2003-06-18 | Sony International (Europe) GmbH | System for deploying location-based services |
US7081579B2 (en) * | 2002-10-03 | 2006-07-25 | Polyphonic Human Media Interface, S.L. | Method and system for music recommendation |
-
2003
- 2003-03-19 US US10/392,370 patent/US7386318B2/en not_active Expired - Lifetime
- 2003-03-19 CA CA2479838A patent/CA2479838C/en not_active Expired - Lifetime
- 2003-03-19 EP EP03719430.5A patent/EP1488646B1/en not_active Expired - Lifetime
- 2003-03-19 AU AU2003223314A patent/AU2003223314B2/en not_active Ceased
- 2003-03-19 WO PCT/US2003/008628 patent/WO2003081391A2/en active Search and Examination
-
2008
- 2008-06-03 US US12/132,481 patent/US20080233927A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2000004730A1 (en) | 1998-07-20 | 2000-01-27 | Signalsoft Corp. | Subscriber delivered location-based services |
CA2416253A1 (en) | 2000-07-28 | 2002-02-07 | American Calcar Inc. | Technique for effective organization and communication of information |
WO2002017654A2 (en) | 2000-08-22 | 2002-02-28 | Telefonaktiebolaget L.M. Ericsson (Publ) | Systems, methods and computer program products for identifying items of interest that are geographically proximate to wireless communicator users |
WO2002017567A2 (en) | 2000-08-25 | 2002-02-28 | Yogogo Limited | Wireless communications system with location-dependent services |
Non-Patent Citations (1)
Title |
---|
See also references of EP1488646A4 |
Cited By (33)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10341808B2 (en) | 2005-04-04 | 2019-07-02 | X One, Inc. | Location sharing for commercial and proprietary content applications |
US10750311B2 (en) | 2005-04-04 | 2020-08-18 | X One, Inc. | Application-based tracking and mapping function in connection with vehicle-based services provision |
US10856099B2 (en) | 2005-04-04 | 2020-12-01 | X One, Inc. | Application-based two-way tracking and mapping function with selected individuals |
US9967704B1 (en) | 2005-04-04 | 2018-05-08 | X One, Inc. | Location sharing group map management |
US10791414B2 (en) | 2005-04-04 | 2020-09-29 | X One, Inc. | Location sharing for commercial and proprietary content applications |
US10750309B2 (en) | 2005-04-04 | 2020-08-18 | X One, Inc. | Ad hoc location sharing group establishment for wireless devices with designated meeting point |
US10750310B2 (en) | 2005-04-04 | 2020-08-18 | X One, Inc. | Temporary location sharing group with event based termination |
US10149092B1 (en) | 2005-04-04 | 2018-12-04 | X One, Inc. | Location sharing service between GPS-enabled wireless devices, with shared target location exchange |
US10341809B2 (en) | 2005-04-04 | 2019-07-02 | X One, Inc. | Location sharing with facilitated meeting point definition |
US9736618B1 (en) | 2005-04-04 | 2017-08-15 | X One, Inc. | Techniques for sharing relative position between mobile devices |
US9749790B1 (en) | 2005-04-04 | 2017-08-29 | X One, Inc. | Rendez vous management using mobile phones or other mobile devices |
US9854402B1 (en) | 2005-04-04 | 2017-12-26 | X One, Inc. | Formation of wireless device location sharing group |
US9854394B1 (en) | 2005-04-04 | 2017-12-26 | X One, Inc. | Ad hoc location sharing group between first and second cellular wireless devices |
US10165059B2 (en) | 2005-04-04 | 2018-12-25 | X One, Inc. | Methods, systems and apparatuses for the formation and tracking of location sharing groups |
US9942705B1 (en) | 2005-04-04 | 2018-04-10 | X One, Inc. | Location sharing group for services provision |
US9955298B1 (en) | 2005-04-04 | 2018-04-24 | X One, Inc. | Methods, systems and apparatuses for the formation and tracking of location sharing groups |
US10313826B2 (en) | 2005-04-04 | 2019-06-04 | X One, Inc. | Location sharing and map support in connection with services request |
US10299071B2 (en) | 2005-04-04 | 2019-05-21 | X One, Inc. | Server-implemented methods and systems for sharing location amongst web-enabled cell phones |
US9883360B1 (en) | 2005-04-04 | 2018-01-30 | X One, Inc. | Rendez vous management using mobile phones or other mobile devices |
US10200811B1 (en) | 2005-04-04 | 2019-02-05 | X One, Inc. | Map presentation on cellular device showing positions of multiple other wireless device users |
US9366542B2 (en) | 2005-09-23 | 2016-06-14 | Scenera Technologies, Llc | System and method for selecting and presenting a route to a user |
WO2007068986A3 (en) * | 2005-12-16 | 2007-08-02 | Kate Kom D O O | Device and procedure for managing short lived and free created content for value added telecomunication services |
WO2007068986A2 (en) * | 2005-12-16 | 2007-06-21 | Kate-Kom D.O.O. | Device and procedure for managing short lived and free created content for value added telecomunication services |
WO2008113162A1 (en) * | 2007-03-19 | 2008-09-25 | Redknee Inc. | Extensible data repository |
EP2192568A1 (en) * | 2007-09-13 | 2010-06-02 | Mitsubishi Electric Corporation | Map drawing device |
EP2192568A4 (en) * | 2007-09-13 | 2014-02-26 | Mitsubishi Electric Corp | Map drawing device |
US9140566B1 (en) | 2009-03-25 | 2015-09-22 | Waldeck Technology, Llc | Passive crowd-sourced map updates and alternative route recommendations |
US9082077B2 (en) | 2009-03-25 | 2015-07-14 | Waldeck Technology, Llc | Mobile private assisted location tracking |
US8620532B2 (en) | 2009-03-25 | 2013-12-31 | Waldeck Technology, Llc | Passive crowd-sourced map updates and alternate route recommendations |
US20210248636A1 (en) * | 2018-07-27 | 2021-08-12 | Ki Eob PARK | Distributed network system for operating group for nodes included in system |
CN109145073A (en) * | 2018-08-28 | 2019-01-04 | 成都市映潮科技股份有限公司 | A kind of address resolution method and device based on segmentation methods |
US20210180979A1 (en) * | 2018-08-31 | 2021-06-17 | Denso Corporation | Vehicle-side device, method, and non-transitory computer-readable storage medium for uploading map data |
US11920948B2 (en) * | 2018-08-31 | 2024-03-05 | Denso Corporation | Vehicle-side device, method, and non-transitory computer-readable storage medium for uploading map data |
Also Published As
Publication number | Publication date |
---|---|
AU2003223314B2 (en) | 2007-04-05 |
WO2003081391A3 (en) | 2004-02-05 |
US20040023666A1 (en) | 2004-02-05 |
CA2479838C (en) | 2011-02-08 |
EP1488646A2 (en) | 2004-12-22 |
US20080233927A1 (en) | 2008-09-25 |
EP1488646B1 (en) | 2017-05-03 |
CA2479838A1 (en) | 2003-10-02 |
EP1488646A4 (en) | 2011-11-02 |
AU2003223314A1 (en) | 2003-10-08 |
US7386318B2 (en) | 2008-06-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2479838C (en) | Location based service provider | |
US9729381B2 (en) | Unified geograhic database and methods of creating, maintaining and using the same | |
JP4928695B2 (en) | Environment interactive context-oriented device and method | |
US7100204B1 (en) | System and method for determining network users' physical locations | |
US8160614B2 (en) | Automated concierge system and method | |
US7747704B2 (en) | Context aware computing devices and methods | |
US7472202B2 (en) | Context-aware systems and methods, location-aware systems and methods, context-aware vehicles and methods of operating the same, and location-aware vehicles and methods of operating the same | |
US20020035609A1 (en) | Location bookmark system and method for creating and using location information | |
US20040203854A1 (en) | Formatting location information based on output device specifications | |
US20020119788A1 (en) | Context-aware and location-aware cellular phones and methods | |
JP2004506964A (en) | Context-aware system and method utilizing hierarchical tree structure | |
Mabrouk et al. | Opengis location services (openls): Core services | |
WO2002063853A2 (en) | Unified geographic database and metod of creating, maintaining and using the same | |
Martire et al. | Location Based Services architecture for simple mobile services | |
Bychowski et al. | OpenGIS® Location Services (OpenLS): Core Services | |
Kofahl et al. | Location concepts for the web | |
LocationLogic | Autodesk LocationLogic: A Technical View | |
Spriestersbach et al. | Improving the Usability of Mobile Enterprise Applications by Applying Location and Situation Information | |
Peng et al. | The application of multi-agent and CORBA in mobile-GPS system | |
LocationLogic | Autodesk® LocationLogic: A Technical Overview | |
WO2002051194A1 (en) | Position based information retrieval system | |
CA2355585A1 (en) | Location bookmark system and method for creating and using location information |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2003223314 Country of ref document: AU |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2479838 Country of ref document: CA |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1418/KOLNP/2004 Country of ref document: IN |
|
REEP | Request for entry into the european phase |
Ref document number: 2003719430 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2003719430 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 2003719430 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: JP |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: JP |
|
WWG | Wipo information: grant in national office |
Ref document number: 2003223314 Country of ref document: AU |
|
DPE1 | Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101) |