WO2002051194A1 - Position based information retrieval system - Google Patents
Position based information retrieval system Download PDFInfo
- Publication number
- WO2002051194A1 WO2002051194A1 PCT/SE2001/002917 SE0102917W WO0251194A1 WO 2002051194 A1 WO2002051194 A1 WO 2002051194A1 SE 0102917 W SE0102917 W SE 0102917W WO 0251194 A1 WO0251194 A1 WO 0251194A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- information
- request
- arrangement
- hat
- mobile station
- Prior art date
Links
Classifications
-
- 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
- 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
Definitions
- the present invention relates to an information distribution system, for exchanging information with a mobile station primarily based on the position of said mobile station, the system comprising: an interface arrangement for interfacing said mobile station into the system, an arrangement for processing an inquiry from said mobile station, an arrangement for retrieving information from a data base, an arrangement for transferring said information in a structured form to said mobile station, means to generate an Information Request Process (IRP), a processing arrangement to process said RP comprising means for analyzing incoming requests and adapting the request to an information provider type request, and means to retrieve information and produce a replay to said request that matches capabilities of the MS where the request originated from.
- IRP Information Request Process
- EP 853 287 relates to a method for transmission of information to the user, in which a search terminal is used for sending an information query, which is received and processed. Further, in the method, information is searched for, and the retrieved information is transmitted to the search terminal. The information is received and displayed to the user by the search terminal.
- a system for transmitting information to a user comprises a search terminal for sending an information query, means for receiving and processing of the information query, means for retrieving information, means for transmitting the information to the search terminal, and means for receiving the information and presenting it to the user on the search terminal, The information retrieval is arranged to be conducted at least partly on the basis of the location and/or travel route of the user
- US 5,978,687 relates a method for call establishment in a cellular radio system including a mobile " services switching center and a private branch exchange connected thereto, and a visitor location register for storing subscriber data on subscribers located within the service area of the mobile services switching center.
- the private branch exchange receives a connection establishment request from a subscriber located within its service area, the private branch exchange checks whether the private branch exchange is the home private branch exchange of the subscriber that sent the connection establishment request. If the private branch exchange is the home private branch exchange of the subscriber, the private branch exchange performs independently authentication, activation of ciphering procedures and assignment of a temporary subscriber identity and only thereafter sends a connection establishment request to the mobile services switching center. If the first call-related message sent by the private branch exchange to the mobile services switching center is a connection establishment request instead of a service request, the mobile services switching center initiates connection establishment without an interrogation to the visitor location register.
- US 6,085,081 relates to a method for allocating a user identification (ID) in a mobile communication network for a connection between a communication terminal and the mobile communication network.
- the user identification is a temporary user identification (TID).
- the method comprises at least the following steps: examining if the mobile station has a user ID, if the mobile station has no user ID, the mobile communication network allocates a TID for the connection, and the mobile communication network transmits the TID to the mobile station.
- a mobile station subscriber can access data from an informational database and have it forwarded to a desired destination.
- a database associated with the informational database maintains subscriber profiles.
- the informational database receives a data request, it uses a mobile station identifier to acquire subscriber profile information. Using that profile information, the requested data is forwarded to a destination designated in the profile in a SMS format.
- the initially mentioned system further comprises means for handling temporary users in the system, said means for handling said temporary users at least comprising a portion for handling said temporary user in communication with said temporary users original system and accessing information in said original system or a portion for allowing said temporary user to obtain a temporary user account for accessing information in the system.
- the system is flexible and can accept inputs from several sources; thus, the requests can originate from one or several of Internet, a wireless Applications Protocol or a Short Messages Service (SMS) Gateway.
- SMS Short Messages Service
- an Information Request Broker is arranged to supervise said Information Request Process and if the process is terminated unexpected, said request broker generates an error response to a requesting client.
- a Content Handling Arrangement comprising a number of layers.
- a first layer is arranged to analyze incoming requests and call an appropriate module in a second layer in order to retrieve information and when said information has been retrieved from said second layer a response is built that matches the characteristics of the terminal where the request originated.
- a third Layer is arranged, which contains a number of adapters for retrieving information from internal or external data sources. References to the information together with a geo-coded data are stored in databases.
- the second layer is arranged to conduct spatial searches for the requested information and, hence, the second layer contains a Spatial Search in which searches for the N nearest of a certain category of information is carried out.
- the IRP is mainly arranged to analyse a request and calls an appropriate module in said second layer.
- the stored data comprises one or several of hotels, stores, restaurants, concert halls, including open hours, pricing, contact information, events, event schedule, time, weather of a location, forecast, points of interest, regions, street intersections and advertising locations.
- the system comprises a language handler for translation of phrases and synonyms between phrases, and a context and an identifier identifies a phrase.
- a response to said request is matched to the terminal where the request originated from and a terminal type corresponding answer is returned.
- the system is provided with a scheduler, which handles operations that are to be executed in future and also handles repetitive operations.
- a scheduler which handles operations that are to be executed in future and also handles repetitive operations.
- the system can be adapted to different users; therefore, the system comprises a Personal Profile handling arrangement, which contains information about users of the system.
- the information contains one or several of MSISDN of the user, a current location of a user and a corresponding timestamp, name and nickname of the user, a list of the friends and the corresponding attributes such as last position of a friend, nickname, MSISDN and a Boolean value describing if the friend can position the user and the group membership, a list of the Finder groups, an email address of the user, a preferred language, a list of the stored positions, a search radius, max hits, and a list of interests.
- the system is connected to a Geo Coding arrangement, which can handle data which is not geo-coded and during the information transaction, it provide the information with geocode.
- the system may comprises statistic collecting in order to obtain knowledge about the usage of the system.
- the invention also refers to a method for exchanging information with a mobile station primarily based on the position of said mobile station.
- the method comprises the steps of providing means for handling temporary users in the system, said means for handling said temporary users at least comprising a portion for handling said temporary user in communication with said temporary users original system and accessing information in said original system and/or a portion for allowing said temporary user to obtain a temporary user account for accessing information in the system.
- the invention also relates to a method of facilitating sale of information exchange with a mobile station in an information distribution system primarily based on the position of said mobile station (MS).
- the system comprises: an interface arrangement for interfacing said mobile station into the system, an arrangement for processing an inquiry from said mobile station, an arrangement for retrieving information from a data base, an arrangement for transferring said information in a structured form to said mobile station.
- the method comprises the steps of: authentication control of the user said MS, receiving a service related request from said user, generating an Information Request Process (IRP) by said processing arrangement, processing said IRP, analyzing incoming requests and initiating an Adapter in order to retrieve information, adapting the request to an information provider type request, retrieving information from said information provide, producing a replay to said request that matches capabilities of the MS where the request originated from, transferring said reply to said MS through said interface arrangement, registering and charging said user for said information.
- IRP Information Request Process
- FIG. 1 is a block diagram over the system according to the invention
- Fig. 2 is a block diagram illustrating layers in one section of the system according to the invention.
- Fig. 3 is a block diagram illustrating a part of the system according to the invention.
- Fig. 4 is a schematic overall view of the system according to the invention.
- the system according to the present invention is adapted for handling large amounts of information that can be presented in different ways.
- the system is a request/response system that creates responses based upon the incoming request.
- a normal question is of the type "Where is the nearest place of type X?" whose matching response is a list of the restaurants sorted by the distance from the requesting terminal.
- the actual content used by the system can either be stored locally in the content database or externally at one or more content providers. Upon a request information is fetched either from the local database or from an external content (information) provider. Information from several sources can be combined in order to fulfill the response to a request. It is the content handling core of the system that makes this flexible handling of information possible.
- the main schematic architecture of the invention is illustrated in fig. 1.
- the architecture In order to make the system flexible, the architecture must allow requests from different types of sources without the need to handle and store information in a way that is dependent from the way requests are made and the way information is to be presented.
- the system 100 handles this situation by using two main blocks, the Information Request Broker 110 (IRB) and the Content Handling Core 120 (CHC), which together provide a flexible system.
- IRB Information Request Broker 110
- CHC Content Handling Core
- the system receives a number of incoming requests.
- the incoming requests for information may originate from several sources and are directed to the IRB 110.
- the sources may be one or several of Internet 111, a wireless Applications Protocol 112 or a Short Messages Service (SMS) Gatewayl 13 connected to the IRB through for example HTTP Servers 114, 115 and an SMS client 116.
- SMS Short Messages Service
- the IRB creates one or several Information Request Processes, IRPs 131, which will execute in an Information Request Space 130, IRS.
- IRB exports a simple API, which when called by a client spawns an Information Request Process that will exists in the IRS. When the process has finished its task and generated a response it can be terminated.
- the IRB may, depending on the load of the IRS, choose to not spawn an IRP and instead generate an appropriate error response to the requesting client.
- the Information Request Broker supervises the Information Request Process(es) and if the process is te ⁇ ninated unexpected, the broker can generate an error response to the requesting client. By doing this, the client always receives some type of response, at least as long as the Information Request Broker resides.
- the CHC 120 is in the illustrated embodiment divided into three layers 121-123 and it also contains a Spatial Search Engine 124 in which searches for the N nearest of a certain category of information can be carried out.
- the three layers are Template Layer 121, Adapter Layer 122 and the Content Layer 123.
- the layers are for architectural reasons, and also for code maintenance reasons, strictly hierarchical. This means that no intra- layer calls are allowed to take place. It also means that it is not allowed to bypass a layer.
- the function of the layers is:
- Template Layer 121 analyses incoming requests and calls the appropriate module in the Adapter Layer 122 in order to retrieve information.
- a response will be built that matches the capabilities of the terminal where the request originated. For example, a WAP phone request to the system will create a response containing WML.
- An SMS request will create a simple text response, and so on.
- Content Layer 123 contains two kinds of adapters, External Content Adapters 124 and Content Database Adapters 125.
- the Content Database Adapters 125 communicate with a Content Database 127.
- An External Content Adapter 124 is used for fetching information from external providers 126, i.e. information that is not stored locally in a local memory arrangement.
- references to the information together with geo-coded data are stored in a Spatial Search Engine 128 but the actual information can be stored in an external database.
- This kind of adapters encapsulates an external protocol used for retrieving the information and exports a simple API to modules in the Adapter Layer 122.
- the Content Database Adapter is used in the same way as an External Content Adapter but the actual information is stored in the local Content Database.
- Adapter Layer 122 makes spatial searches for the requested information. Information that is stored locally in the Content Database 125, is accessed via Content Database Adapters 125 in the Content Layer 121 and information that are stored externally are fetched via the External Content Adapter.
- the Content Handling Core also contains a Spatial Search Engine 129 that can make efficient searches for information based on category and spatial data. Performance is linear in memory space and O(nlogn) performance time.
- the Information Request Process analyses the request and calls the appropriate module in the Template Layer of the Content Handling Core.
- the Content database stores and organizes all data used by the application. This includes, for example content, categories, events, user, language and more. Content holds information about all searchable items in the system.
- the Content can be of many different types; the basic common denominator is that they consist of location information. All types do not have to be explicitly presented to the end user, but are rather used by application to perform tasks. Different type of contents store different type of data. Example of different types of content is (see also fig. 2):
- Events including Event schedule, time
- Weather of the location including forecast
- the categories are connected in a hierarchical structure and are used both for navigation and categorization of content. There are a few category types; a single category can have one or more types, for example:
- Menu used for navigation and is presented in user interface.
- Content categorizes connected content. Content can have many categorizations
- Content of the above first type (Stores, hotels etc) are usually connected to one or more categories of both type Menu and Content, because this type of content is usually browsed by its category.
- weather content for example, belongs to a category that cannot be browsed.
- User data can include stored positions, e.g., "my list” (bookmarks), finder application data (friends, groups).
- the Language handles translation of phrases and synonyms between phrases.
- a context and an identifier can identify a phrase. Thus, the same phrase can exists in different contexts and have different translation between languages in each context.
- Phrases can have one or more synonyms in each language. "Accommodation”, for example, can have the synonym "Hotels" in English.
- the Template Layer module 121 analyses the request and calls one or more modules in the Adapter Layer 122 in order to retrieve information.
- the modules in the Adapter Layer 122 direct one or more requests to External Content Providers 126 and/or to the internal Content Database 125 via modules in the Content Layer.
- the Adapter Layer also makes spatial searches for the requested information and also initiates searches in the Content Database via the Content Layer.
- the Template Layer modules builds a response matching the terminal where the request originated from. For example, a WAP phone request to the system will create a response containing WML. An SMS request will create a simple text response.
- Tables 1-3 describe the exemplary contents of each layer.
- Each box in each layer is provided with a reference sign including the layer number and box number (indicated in the parenthesis), beginning from 1 and from left to right in fig. 2.
- Templates A template is used for handling incoming requests in detail and is supposed to generate an (121) appropriate response depending on the type of the querying request (terminal, protocol, actual query).
- the response When a request originates from a WAP phone, the response should be a WML page. Requests originating from a SMS should result in a response that is a simple text string containing less than 160 (standard setup) characters.
- a template in general, uses one or more templates in order to fulfill the request.
- Channel The channel template handles the concept of chat channels, where it is possible to post messages
- the content template handles searches for the 'n' nearest of a certain category, such as the 5
- the content data template generates detailed information about a specific content, like address,
- IPR calls the error handler template when an exception occurs in the template (or underlying
- Find The find template generates a list of the different kind of search variants, like search for the
- Friends The friends template implements the user interaction for the Finder. It can generate all the
- Menu The menu template generates menus. It can display adverts (both textual and images) as the first
- the Advert adapter is used in order to retrieve a certain advertising.
- the setting template generates menus for the different kinds of settings available and also takes (1218) care of changes made by the user.
- a change in the setting normally affects the user profile.
- SMS The SMS template is always used upon incoming requests originating from a sms.
- the template (1219) can handle basic Finder functionality and also simple searches for the nearest specified object (like the nearest hotel).
- the system may also be provided with a Scheduler 150, which handles operations that are to be executed in the future and can also handle jobs that are repetitive.
- An example is fetching weather data twice a day.
- the system can be arranged with a Personal Profile handling arrangement 140.
- the Content Handling Core 120 uses Personal Profiles 140 to fulfill its tasks.
- the Personal Profile contains information about the users of the system such as the current position of the user, MSISDN etc.
- Personal Profiles are stored persistently in the Personal Profile Database 141 and the user can be allowed to change parts of a profile.
- the Personal Profile may contain the following information about the user:
- MSISDN of the user This is the unique key for the personal profile.
- M is a configurable parameter of the system.
- a list of the friends and the corresponding attributes such as last position of a friend, nickname, MSISDN and a Boolean value describing if the friend can position the user and the group membership.
- a list of the stored positions can be used whenever the user would like to move to another position and make content search relative to that position.
- Search radius This parameter is used whenever a search for the nearest object of some category is performed.
- Max hits This parameter is used whenever a search is performed and the result is to be displayed, then as a maximum “Max hits” hits are to be found in the response.
- This parameter can be used for generating advertisements that may be of interest for the user.
- a critical part of the system is the quality of the content stored in the Content Database. If the content is of no interest to the end users, they simply won't use the offered services. On the other hand, if the content is of interest to the users, they will use it and hopefully frequently. In order to achieve this goal, it is very important that the content is geo-coded accurately, i.e. it can provide geographical information to the users.
- the system can be connected to a Geo Coding arrangement 300, schematically illustrated in fig. 3, which can handle data which is not geo-coded and during the information transaction, it "geocodes" the information, e.g., based on the address, postal code etc., of the content. This process will lead to a categorization of the content and a spatial location containing latitude and longitude.
- the Geo Coder arrangement 300 comprises a Geo Coder Engine 310, which uses a Geo Code Database 320 in order to complete its task.
- the Geo Code Database contains the base for performing geo-coding, such as the layout and position of streets, their name, postal code etc.
- the Geo Coder Engine 310 can be provided with two front-ends, one for third party provisioning 330 where content can be entered, added or deleted by a third party.
- the other front-end 340 is aimed for importing larger amounts of data that are to be geo-coded automatically and stored in the Content Database 127, for example Yellow Pages, or the like.
- Fig. 4 is a schematic overall view of the system 100 according to the invention.
- the system relies on having one or more High Availability databases as the core for storing information and Personal Profiles.
- Each Host contains the Information Request Broker 110, the Information Request Space 130, the Content Handling Core 120 and the support for Personal Profiles as well as the Mobile Location System (MLS) client 143.
- the method used for load sharing and redundancy between the Hosts is very simple and in a communications network 420, e.g.
- LAN Local Area Network
- WAN Wide Area Network
- RRDNS 410 Round Robin DNS
- the clients dynamically look up which Host to use in the RRDNS 410 prior to a request. Accessing the Hosts in this way will create an even load on every host and it will also make the system robust since, upon a Host failure, the remaining hosts can still serve the client.
- the system comprises an Operation and Maintenance Host (OMH) 430, which contains the interface for doing manual control of the system. It also serves as the point where all notifications, alarms and similar are sent from the Hosts and databases.
- OMH may include Fault management, which covers handling of alarm list, includes resend, ceasing etc, possibility to set alarm levels, Performance management, functions for reading counters/statistics from the system, supports live, batch mode reading of counters/statistics, and Configuration management, which supports read/set configuration parameters for the application.
- a temporary operator can allow a subscriber to have a temporary account for accessing the information in the temporary network. This is achieved through SBR 460.
- the SBR 460 allows a guest user to obtain a temporary account and access the information needed.
- the profile of the guest user is copied from the host network.
- the temporary operator may charge the host operator for the used services.
- a language module (LM) 470 can be connected to the system.
- the LM checks incoming requests and determines the language and if the language is not agree with the local or database language, both the request and the database are translated.
- the system is provided with a Scheduler Host 440, which contains the scheduler used for performing timer-based tasks in the system.
- the scheduler can handle tasks in several ways, e.g. executing retries of a task that fails, reschedule a task and similar.
- An example of a task is daily fetch of weather forecasts that are stored in the Content Database.
- the Operation and Maintenance Host and the Scheduler Host are co-located in the same hardware, e.g. the same host.
- the system may use statistics in order to obtain knowledge about the usage of the system, e.g. which content that seems to be interesting for the users.
- Content hit counters can be used for colleting data about which contents that really are of interest for the users.
- the counters can be anonymous, e.g. knowledge about which users that visited a certain page or selected certain content are not stored.
- user usage counters can be arranged in order to acquire knowledge about what content a certain user often uses. This information can later be used.
- PBR Position Based Roaming
- SBR System Base Roaming
- PBR via a connection to the mobile location system 143, when the subscriber (mobile station) is in another network, e.g. during a journey abroad, it is possible that the temporary host network, under an agreement with the main operator, allows the subscriber to access the information in the content database of the main (home) operator, i.e. the temporary operator accesses the home operator network and retrieves required information.
- an arrangement 450 for handling temporary visitors can be arranged. The positioning is done by the temporary operator or a position broker and supplied to the home operator. The position is obtained through the MLS 143 connected to an external position provider arrangement 460.
- the temporary host which can have the same or a similar system according to the invention, transmits the request to the home operator, which handles the request, prepares and returns a reply as described above.
- the home operator which handles the request, prepares and returns a reply as described above.
- all settings (profile) of the user are preserved in the home operator database.
- the temporary host network can (preferably, under an agreement with the main operator) provide the subscriber with a temporary account 460.
- the subscriber will be able to access same or similar information from the temporary operator, hi this case, if the language of the temporary operator differs from the subscribers language, a language module 470 can be used to translate and form the request and retrieved information, as described above.
- a convert or 480 can be used to convert the information exchange between the temporary operator and the original operator.
Abstract
Description
Claims
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2002217706A AU2002217706A1 (en) | 2000-12-21 | 2001-12-21 | Position based information retrieval system |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US25763500P | 2000-12-21 | 2000-12-21 | |
US60/257,635 | 2000-12-21 | ||
SE0004802-5 | 2000-12-21 | ||
SE0004802A SE0004802D0 (en) | 2000-12-21 | 2000-12-21 | Position based information retrieval system |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2002051194A1 true WO2002051194A1 (en) | 2002-06-27 |
WO2002051194A9 WO2002051194A9 (en) | 2002-12-05 |
Family
ID=26655349
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/SE2001/002917 WO2002051194A1 (en) | 2000-12-21 | 2001-12-21 | Position based information retrieval system |
Country Status (2)
Country | Link |
---|---|
AU (1) | AU2002217706A1 (en) |
WO (1) | WO2002051194A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE102004043169A1 (en) * | 2004-09-03 | 2006-03-09 | Claas Selbstfahrende Erntemaschinen Gmbh | Electronic data exchange system |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5727057A (en) * | 1994-12-27 | 1998-03-10 | Ag Communication Systems Corporation | Storage, transmission, communication and access to geographical positioning data linked with standard telephony numbering and encoded for use in telecommunications and related services |
EP0838967A2 (en) * | 1996-10-23 | 1998-04-29 | Siemens Aktiengesellschaft | Method for location specific registration of mobile terminals to base station of a communication network |
EP0851696A2 (en) * | 1996-12-24 | 1998-07-01 | At&T Wireless Services, Inc. | Method of wireless retrieval of information |
EP0853287A2 (en) * | 1996-12-31 | 1998-07-15 | Nokia Mobile Phones Ltd. | Method for transmission of information to the user |
US5930699A (en) * | 1996-11-12 | 1999-07-27 | Ericsson Inc. | Address retrieval system |
US5978687A (en) * | 1993-06-23 | 1999-11-02 | Nokia Telecommunications Oy | Method for establishing a call in a cellular radio system depending on whether the a PBX is the home PBX of the requesting mobile subscriber |
US6085081A (en) * | 1997-01-31 | 2000-07-04 | Nokia Mobile Phones Ltd. | Method for allocating a user identification |
-
2001
- 2001-12-21 AU AU2002217706A patent/AU2002217706A1/en not_active Abandoned
- 2001-12-21 WO PCT/SE2001/002917 patent/WO2002051194A1/en not_active Application Discontinuation
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5978687A (en) * | 1993-06-23 | 1999-11-02 | Nokia Telecommunications Oy | Method for establishing a call in a cellular radio system depending on whether the a PBX is the home PBX of the requesting mobile subscriber |
US5727057A (en) * | 1994-12-27 | 1998-03-10 | Ag Communication Systems Corporation | Storage, transmission, communication and access to geographical positioning data linked with standard telephony numbering and encoded for use in telecommunications and related services |
EP0838967A2 (en) * | 1996-10-23 | 1998-04-29 | Siemens Aktiengesellschaft | Method for location specific registration of mobile terminals to base station of a communication network |
US5930699A (en) * | 1996-11-12 | 1999-07-27 | Ericsson Inc. | Address retrieval system |
EP0851696A2 (en) * | 1996-12-24 | 1998-07-01 | At&T Wireless Services, Inc. | Method of wireless retrieval of information |
EP0853287A2 (en) * | 1996-12-31 | 1998-07-15 | Nokia Mobile Phones Ltd. | Method for transmission of information to the user |
US6085081A (en) * | 1997-01-31 | 2000-07-04 | Nokia Mobile Phones Ltd. | Method for allocating a user identification |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE102004043169A1 (en) * | 2004-09-03 | 2006-03-09 | Claas Selbstfahrende Erntemaschinen Gmbh | Electronic data exchange system |
US8204960B2 (en) | 2004-09-03 | 2012-06-19 | Claas Selbstfahrende Erntemaschinen Gmbh | Electronic data exchange system and method |
Also Published As
Publication number | Publication date |
---|---|
AU2002217706A1 (en) | 2002-07-01 |
WO2002051194A9 (en) | 2002-12-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP0976254B1 (en) | Telecommunications apparatus and method | |
EP0861565B1 (en) | Data service in a mobile communication network | |
US6912545B1 (en) | Location-code system for location-based services | |
US7242949B2 (en) | Multimedia information and information inquiry download service | |
US6205126B1 (en) | Method and apparatus for automatically determining an ISP local access number based on device location | |
EP1060632B1 (en) | Method, arrangement and apparatus for providing information | |
CN100343849C (en) | System and method for providing location-relevant services using stored location information | |
US20020035609A1 (en) | Location bookmark system and method for creating and using location information | |
US20080183828A1 (en) | Communication system | |
US20020019699A1 (en) | Address presentation system | |
WO2003081391A2 (en) | Location based service provider | |
JP4339379B2 (en) | Presence information management method and presence information management system | |
JP2001344265A (en) | Method and system for region information provision using real name | |
KR100813398B1 (en) | Location-based mobile office system and its implementation using portable telecommunication terminal and unified messaging system | |
KR20090001855A (en) | System and method for searching and providing information using a mobile instant messaging service by analysing users' dialogue and location | |
CN101331485A (en) | Improving location-based searches by measuring location-based clickthrough measurements using implicit location | |
WO2002051194A1 (en) | Position based information retrieval system | |
CN102209095A (en) | Service management system and method for providing service information | |
CN1265611C (en) | Position service system based on hand-free telephone and position service providing apparatus and method | |
JP2002268970A (en) | Accessing method, information processor and information providing device | |
KR20010098255A (en) | Integrated information service system and method and advertisement system and method for use therein | |
WO2002058426A1 (en) | A system for facilitating delivery of location-dependent information to mobile devices | |
KR20040001216A (en) | The method of the advertisement and call connection considering the user's current location in next generation network | |
KR100789276B1 (en) | Enterprise detail information service method using mobile | |
KR100748089B1 (en) | Method for providing individual information based on user data management open api |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ CZ DE DE DK DK DM DZ EC EE EE ES FI 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 SD SE SG SI SK SK SL TJ TM TN TR TT TZ UA UG US UZ VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 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 CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE 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 | ||
AK | Designated states |
Kind code of ref document: C2 Designated state(s): AE AG AL AM AT AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ CZ DE DE DK DK DM DZ EC EE EE ES FI 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 SD SE SG SI SK SK SL TJ TM TN TR TT TZ UA UG US UZ VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: C2 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 CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
122 | Ep: pct application non-entry in european phase | ||
NENP | Non-entry into the national phase |
Ref country code: JP |
|
WWW | Wipo information: withdrawn in national office |
Country of ref document: JP |