RU2467505C2 - Obtaining server identifier based on device location - Google Patents

Abstract

FIELD: physics, communications.

SUBSTANCE: invention relates to mobile communication. The technical result is achieved owing to that a unique identifier of a network node is used to request from a database location-dependent information for a device connected to said node. An identifier of at least one server serving an area in which said device is located is then retrieved by using said location-dependent information.

EFFECT: enabling a mobile device to determine its local server when making an emergency call.

24 cl, 9 dwg

Description

FIELD OF TECHNOLOGY

The present invention relates to a method, apparatus and database for obtaining a server identifier, for example (but not limited to) an emergency call response unit.

BACKGROUND

Device location is useful information for many applications. The device can rely on its access network to provide location information. This service may be provided by a location configuration server (LCS). However, the device may request that the LCS server provide a location reference in the form of a Uniform Resource Indicator (URI) or a set of URIs, which allows the device to distribute its location information. An LCS server can be accessed through a protocol, for example, HELD (HTTP Enabled Location Discovery, HTTP Location Support), which retrieves location information.

Schuizrinne, H., "Location-to-URL Mapping Architecture and Framework", Dec. 2006 describes the architecture of a display server, with a display client (search tool or resolver) and a display server (resolver or other servers) to find out server addresses. The request message contains location information and a service identifier encoded as a Uniform Resource Name (URN) (see, for comparison, Schulzrinne, H., "A Uniform Resource Name (URN) for Services", Aug 2006) from a LoST client (Location-to Server Translation) to the LoST server. The LoST server uses its database to map input values to one or more Unified Resource Identifiers (URIs) and returns these URIs with additional information, such as, for example, indications of service boundaries, in a response message to the LoST client. If the server cannot service the request itself, it can, in turn, request another server or return the address of another LoST server.

If the LoST URL contains the host name instead of the IP address (Internet Protocol, Internet Protocol), clients must use the name owner pointer (for example, U-NAPTR, as described, for example, in Daigle, L., "Domain-based Application Service Location Using URIs and the Dynamic Delegation Discovery Service (DDDS), Oct. 2006.

The architecture for emergency calls makes it possible to apply the concept of LoST servers and HELD servers. The LoST server is responsible for converting the location information into the URIs of the nearest PSAP (Public Safety Answering Point) nodes, and the HELD server is responsible for providing the user's location information. The location-LoST protocol specification describes an XML-based protocol for mapping service identifiers and geographic or city location information into service contact URIs. In particular, this can be used to determine location-appropriate PSAPs for emergency services.

A common problem in locating IP emergency calls is figuring out which LoST or HELD server to use. This is because LoST or HELD services have boundaries. For example, a typical LoST server may determine whether a PSAP location belongs to the state territory to which the PSAP belongs. Or, in large countries, a regional network operator can provide a LoST server that can determine the locations where that operator has a coverage area. Similar situations may also apply to HELD servers.

The geographic limitations of the LoST and HELD servers lead to another problem: how can a device, such as a terminal device, find the URI or IP address of a LoST or HELD server that can provide location information to the terminal?

The current solution is to use the Dynamic Host Configuration Protocol (DHCP) to retrieve the URI or IP address of the LoST server, as defined in the Internet project "A Dynamic Host Configuration Protocol (DHCP) based Location-to-Service Translation Protocol (LoST) Discovery Procedure "(see http://tools.ietf.org/id/draft-ietf-ecrit-dhc-lost-discovery-02.txt for comparison). However, while this solution is technically suitable for stationary terminals that usually receive an IP address with DHCP, this solution is not suitable for wireless networks (for example, the IP Multimedia Subsystem (IMS)).

Mobile devices (such as mobile terminals or mobile nodes) typically do not use DHCP to obtain an IP address when using access networks with General Packet Radio Services (GPRS) with an IP connection. Instead, these devices use GPRS procedures (for example, activation of the Packet Data Protocol (PDP) context) to obtain IP addresses.

On the other hand, since the mobile device can move, it can go beyond the PSAP. Therefore, this mobile device may need to determine its local LoST / HELD server at the time of the emergency call, but not earlier.

SUMMARY OF THE INVENTION

An object of the present invention is to provide such a mechanism for obtaining a server location that is suitable for any (fixed and mobile) devices.

This goal is achieved by a method comprising:

- the use of a unique identifier for a network node to query location-dependent information from a database for a device connected to this node; and

- determining the identifier of at least one server serving the area in which the specified device is located by using the specified information, depending on the location.

The above method can be implemented as a computer program product executed on a computing device, comprising code means for implementing the corresponding steps above.

Additionally, the above goal is achieved by using a device containing a service access tool configured to use the node identifier of the network node to which the specified device is connected when requesting location-dependent information from the database for this device, as well as configured to determine the identifier by at least one server serving the area in which the specified device is located by using the specified requested information.

The above device can be implemented as / in a stationary or mobile network element or node, in a stationary or mobile terminal device, or in the form of a module, chip or set of chips implemented in these nodes, elements or devices.

In addition, the above goal is achieved using a database configured to store location-dependent information in association with the node identifiers of a network node, wherein the database is configured to output the location-dependent information in response to a request sent to corresponding node identifier.

Accordingly, the device is able to find the address of its local proxy with minimal configuration. In particular, the location-specific address of local servers (for example, local LoST and HELD servers) does not need to be preconfigured, but can be found. Alternatively, the device can construct or set the default server address (s) based on a unique identifier. The device can then perform a regular server request or a request using the default self-sustaining server addresses to obtain local-address-specific local server addresses. The database can be provided with default addresses to return the required server addresses. The device can then contact local servers using the returned server addresses. Since the default server address can reach the host access level, any number of local servers can be represented in the database in order to balance the load.

In accordance with the first aspect, the network may be a wireless (mobile) network, and the device may be a wireless (mobile) device.

In accordance with a second aspect, the unique identifier may comprise a cell identifier of a cellular transmission system.

According to a third aspect, the unique identifier may comprise an address of a medium access control layer of a wireless LAN access point.

In accordance with a fourth aspect, the unique identifier may comprise a terminal line identifier.

Of course, any combination of the above unique identifiers can be used as a unique identifier.

In accordance with a fifth aspect, a default server address may be set in the mobile device using at least portions of the cell identifier. In a specific implementation example, the cell identifier may be a global cell identifier, with the default server address being set based on at least one of the following: mobile network code, mobile country code, and location area code of the global cell identifier.

In various embodiments, location-dependent information may be requested by querying a domain name. The identifier may comprise a uniform resource identifier. The database can be implemented as a domain name server. In a specific embodiment, the domain name server may comprise or combine at least one server from the translation server and the location server, which serve the network node to obtain the identifier of the at least one server.

Location-specific information may be requested based on a resource record of the name owner pointer.

In addition, the location-dependent information may comprise an identifier (eg, address) of at least one server or, alternatively, an identifier of at least one server from a translation server and a location server. In a specific example, the transformation server may comprise a location-server transformation server (eg, a LoST server), and the location server may comprise a location server with a hypertext transfer protocol (eg, a HELD server). The server address can also be for the SUPL Location Platform (SLP), Secure User Plane Location (SUPL), Enhanced SUPL Location Platform (E-SLP) and SUPL Positioning Center.

This solution can be applied to the emergency call service when the corresponding server operates as a public safety response node.

The device may be a fixed network device equipped with a radio receiver used to extract, for example, a cell identifier from existing radio signals, in order to use the extracted cell identifier to request location-dependent information from a database.

Further useful modifications are defined in the dependent claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will now be described on the basis of embodiments, with reference to the relevant drawings, in which:

1 is a schematic diagram showing a network architecture in which the present invention may be implemented;

2 is a schematic signal diagram in accordance with a first embodiment of the present invention;

figure 3 shows an example configuration of a resource record in accordance with the first embodiment of the present invention;

4 is a schematic signal diagram in accordance with a second embodiment of the present invention;

figure 5 shows a schematic structure of a global cell identifier;

6 is a schematic signal diagram in accordance with a third embodiment of the present invention;

7 is a flowchart of a configuration procedure in accordance with a third embodiment;

on Fig schematically shows the blocks of a mobile device and a database, in accordance with various variants of implementation of the present invention; and

9 is a block diagram of a software implementation in accordance with a fourth embodiment of the present invention.

DESCRIPTION OF EMBODIMENTS

Embodiments of the present invention will now be described based on an emergency IP call function in a cellular network environment. A cellular network environment is used as an illustrative example of a network environment where the present invention can be used. The present invention can be applied to any type of wireless or fixed network.

Figure 1 shows a schematic representation of the basic network architecture in which the present invention can be implemented. A cellular radio access network 300, such as a UMTS Terrestrial Access Network (UTRAN) of a Universal Mobile Telecommunication System (UMTS), in accordance with Long Term Evolution (LTE) technology or a third generation partnership project (3 ^The 8th edition ^rd Generation Partnership Project (3GPP) is connected to a mobile terminal (e.g., user equipment (UE) 10) via an access device 20, such as a radio network node in the form of a base station (Enhanced Node B (eNode B) or Node B ( Node B)). The radio access network 300 provides access to specific IP network servers, such as the Internet. These specific servers comprise a DNS server 32, a designated LoST server 34, a designated HELD server 36, an SLP server (Secure User Level Location Platform (SUPL)) 35, and a PSAP 38 to which emergency calls are routed.

In accordance with various embodiments, the UE equipment 10 transmits a request 40 to a domain name server (DNS) to request an identifier (e.g., server address, etc.) of at least one HELD server 36, LoST server 34, and SLP server 35.

In cellular networks, for example, radio access network 300, the equipment 10 of the UE is able to determine the identifier of the cell to which it is connected. Typically, a Cell Identifier (CI) or a Cell Global Identity (CGI) is broadcast and used in radio signaling between the UE 10 and the radio access network 300. Therefore, the UE equipment 10 constantly knows the CI or CGI of the radio cell. In addition, the Third Generation Partnership Project (3GPP) determines that a mobile device, such as UE equipment 10, should include the CI or CGI used when signaling using the Session Initiation Protocol (SIP).

In the embodiments described below, a database 32 is provided that accepts CI or CGI, as well as the corresponding 3G and LTE cell identifiers, as input to the requests and returns various information including, but not limited to, the URI of the LoST server 34 and server 36 HELD serving the geographical area in which the honeycomb is physically located.

In an alternative implementation (not shown), the UE equipment 10 may also use the media access control (MAC) address of the wireless base station (e.g., a wireless local area network (WLAN) access point or WIMAX network) to which the UE equipment 10 is connected in the same way, to determine the appropriate HELD and LoST servers serving the area of this base station.

In the example of FIG. 1, database 32 is implemented as a DNS server, which may also be called Dynamic Discovery Service (DDDS), or, similarly, as a representation of a new DNS server assigned to define LoST and HELD servers.

In the first embodiment, the CI and CGI identifier (s) are used as new input types in the DNS query, and the DNS functionality is configured to determine the respective HELD and LoST servers based on the radio cell in which the UE equipment 10 is currently located. In other embodiments, the CI and CGI identifier (s) are used as input in the DNS query, and the DNS functionality is configured to determine the URIs of any telecommunications service available to the terminal in the area corresponding to the CI and CGI identifier (s). As a specific implementation example, the U-NAPTR request type can be used, presented as an example in the specification of RFC 4848, Section 3 of the Internet Engineering Task Force (IETF). The corresponding DNS query output uses existing protocol elements described in RFC 4848, section 4, or based on those elements.

When the access operator properly configures its domain name system (DNS), any terminal device (for example, UE equipment 10) can query the DNS to look for the corresponding LoST, HELD server, or URI (s) of any relevant telecommunication service.

2 is a schematic signal diagram in accordance with a first embodiment of the present invention.

The UE equipment 10 finds the address of its DNS server 32 according to the standard procedure (for example, pre-configured, via DHCP, or PDP context activation). Equipment 10 UE also defines its CI. Further, the UE equipment 10 must find its assigned LoST server 34 and HELD server 36, but it does not know the addresses of the servers configured by the access operator.

In step 101, the UE equipment 10 sends a DNS NAPTR request that contains the current CI or CGI and the requested protocol (e.g., LoST or HELD). In the case of a CGI, it is formatted in a hierarchical manner in which the various fields that make up the CGI are separated by a dot. Then, at step 102, the DNS server 32 sends a DNS response containing the address of the local LoST or HELD server (or both), which can be extracted from the server configuration. Then, the UE equipment 10 may, in step 103, initiate a standard HELD request (eg, “HTTP GET”) to obtain detailed location information, which is sent in step 104 in the HELD response (eg, “HTTP 200” (OK)). With this detailed information, the UE 10 can make a LoST request (for example, "HTTP POST") in step 105 to find out the SIP protocol address of the local PSAP 38, which is returned in step 106 in the LoST response (for example, "HTTP 200 "(OK)).

Finally, the UE equipment 10 can make an emergency call at step 107 and address it to the local (and nearest) PSAP 38.

It should be noted that this embodiment and all subsequent embodiments can be used not only in emergency calls, and the UE equipment 10 can use any local services.

Figure 3 shows an example configuration of a NAPTR resource record in DDDS, which can be used in the first embodiment. First, two new U-NAPTR applications are defined, called Cell Identifier (CI) and Global Cell Identifier (CGI), which are then associated with LoST and HELD protocols.

5 shows the relationship between CI and CGI. CGI contains the identification of the local area and CI. The local area identification contains a mobile country code (MCC), a mobile network code (MNC), and a location area code (LAC).

FIG. 4 is a schematic signal diagram of an improved system according to a second embodiment, where three nodes or servers are combined together, that is, a DNS server 32, a LoST server 34, and a HELD server 36. In a second embodiment, the UE equipment 10 makes a DNS NAPTR request in step 201 and receives a response in step 202. The response contains a local PSAP address (or any other local address of the requested service). Then, in step 203, the UE equipment 10 can make an emergency call or call any other localized service, for example, by generating a SIP INVITE message.

6 is a schematic signal diagram in accordance with a third embodiment of the present invention, which does not require any changes to the DNS. The proposed acquisition procedure provides self-provisioning of equipment with 10 UE addresses of LoST and / or HELD servers (for example, in the form of URIs) based on CGI, or for secure user level location (SUPL) with self-provision with an E-SLP (Enhanced SUPL Location Platform, improved SUPL location platforms). The UE equipment 10 can then use the URIs provided by itself in the DNS query to obtain the IP addresses of the LoST, HELD, and E-SLP servers, respectively.

The diagram and steps shown in FIG. 6 are similar to those shown in FIG. 2, excluding the initial creation step or process where server default addresses are created or set based on CGI.

A similar construction process can be applied when constructing an SLP or E-SLP address when a SUPL initiation terminal (s) with SUPL capability (SUPL Enabled Terminal, SET) is initiated towards the E-SLP server. SUPL uses user-level storage media to transmit location information (for example, to support the Global Positioning System (GPS)) and to support technology-dependent positioning protocols between the SET terminal and the network. SUPL provides an efficient way to transmit the location information required to calculate the location of the SET terminal. Further details regarding SUPL can be obtained from the specifications of the Open Mobile Alliance (OMA).

It should be noted, however, that the procedures and concepts of the first and second embodiments can also be applied to extracting the address for the SLP or E-SLP server.

7 shows an example flowchart of a configuration procedure in accordance with a second and third embodiment. This procedure or mechanism can be used, for example, to configure the default address of the LoST / HELD / E-SLP server.

At step 301, the first 5 or 6 digits of the CGI are retrieved (depending on whether a two or three digit MNC is used). Then, at step 302, these numbers are divided into MCC and MNC. If the MNC is two-digit, then zero may be added at the beginning.

In step 303, the extracted MCC, MNC (obtained in steps 301 and 302) and LAI are used to create a default domain name according to the following expression (the expression below is based on Appendix E of 3GPP TS 23.003):

"mnc <MNC>. mcc <MCC>. lai <LAI> .pub.3gppnetwork.org".

Finally, in step 304, the label “held.”, “Lost.” Is added to the beginning of the configured domain name by default or "e-slp.".

As an example, if the CGI used is "234150999999999" and MCC = 234, MNC = 15 and LAI (LAC + CI) = 0999999999, the following configured domain names can be obtained by default for different types of servers:

LoST server: "lost.mnc015.mcc234.lai0999999999. Pub.3gppnetwork.org",

HELD server: "held.mnc015.mcc234.lai0999999999.pub.3gppnetwork.org",

E-SLP server: "e-slp.mnc015.mcc234.lai0999999999.pub.3gppnetwork.org".

So, if the UE equipment 10 has not received the HELD / LoST / E-SLP server URI, then the UE equipment 10 constructs the URIs in accordance with the above diagram. The UE equipment 10 then performs a standard DNS query using the default URIs to obtain the IP addresses of the HELD / LoST / E-SLP servers. The DNS server 32 may be provided with default addresses for returning IP addresses during a normal DNS query. Then, the UE equipment 10 can connect to the HELD / LoST / E-SLP servers using the obtained IP addresses, after which the call process continues as usual. Since the fully qualified default domain name (Fully Qualified Domain Name, FQDN) reaches the cell level, any number of HELD / LoST / E-SLP servers can be represented in the DNS server for load balancing purposes.

On Fig schematically shows the blocks of a mobile device and a database that can be used in the above embodiments. The description is based on an example of emergency service implementation.

The UE equipment 10 comprises a radio frequency (RF) unit 21 for transmitting and receiving radio signals to / from a radio access network 300. If an emergency trigger (ET) is activated (for example, by pressing an emergency call button, etc.), the address generation function (or block 23) determines a unique identifier, as described in the above embodiments, and sends this unique identifier to the generation function a message (or block 22) that generates a DNS query with a specific unique identifier transmitted to the DNS server 32.

The DNS server 32 contains means or an access control unit (Access Control, AC) 14, which provides access to the database. The database contains a section of 12-1 pointers and an associated section of 12-2 addresses. In pointers section 12-1, IDs ID-Idn are stored, which may correspond to the above CIs, MAC addresses, default addresses, as examples of unique identifiers of the access device 20. The address section 12-2 stores server addresses (for example, LoST, HELD or E-SLP server addresses) associated with the identifiers in the pointer sections 12-1.

When a DNS query with a unique identifier is received through the radio access network 300 from the equipment 10 of the UE, the access control unit 14 accesses the database pointer section 12-1 (using the unique identifier as a pointer) and receives the associated server address (s) from the address section 12-2 . The extracted address (es) is then forwarded to the UE equipment 10 in the corresponding DNS response and can be used to access the PSAP 38 to initiate emergency call processing.

FIG. 9 is a block diagram of an alternative software implementation in accordance with a fourth embodiment. The required functionalities can be implemented in any mobile device 400 with a processing unit 410, which can be any processor or computing device with a control unit that performs control based on program procedures of a control program stored in memory 412. The control program can also be stored separately, on computer readable media. The program code instructions are retrieved from the memory 412 and loaded into the control unit of the processing unit 410 to execute the program steps of the above functionalities shown in Figs. 7 and 8, which can be implemented as the above program procedures. Program steps can be performed based on DI input and can generate DO output. The DI input may correspond to a CGI, MAC address, or other unique identifier of the radio access device in question, and the DO output may correspond to a server request forwarded to the DNS server 32 or any other proxy server used to retrieve the desired identifier.

As a result, the above embodiments may be implemented as a computer program product comprising code means for generating each individual step of a signaling procedure and executed on a computer device or data processor of a receiving device (e.g., Node B 20) or a transmitting device (e.g., equipment 10 UE) , respectively.

As a result, a method, device, system and computer program product are described in which a unique identifier of a node (for example, an access node) of a radio network is used to request location-dependent information from a database for a mobile device connected to the node. Then, using the information depending on the location, the identifier of at least one server serving the area in which the mobile device is located is retrieved.

It is clear that this invention can be easily extended to any service and network environment (fixed and wireless), where location-dependent information is required to access a server offering the requested service. The server can provide any telecommunication services and is not limited to the types of servers mentioned in the preferred embodiments. More specifically, the present invention is not limited to the above network environment of these embodiments. This invention can be implemented in any network environment (for example, the invention can be used in wired networks where a stationary device, such as a computer or landline telephone, is connected to the network). Moreover, any type of unique identifier of any type of node can be used to query the server. A line identifier (line ID) may be used as an example, in addition to or as an alternative to the above CI and MAC addresses. Moreover, the line identifier can be stored in the node (which covers the network devices and terminal devices) to which the device is connected, thus being a unique identifier for each line and connected device. Therefore, the term “unique identifier” is intended to mean any type of line identifier, including a specific identifier of a terminal (device). Moreover, more than one unique identifier of a node may exist, while a node may have several devices connected via several lines, where each line has a unique line identifier. Since the line identifier in this case is unique for each line, it is also unique for each connected device. The unique identifier (s) of the line can be stored and assigned in the node to which the device is connected.

The LoST server may also provide a PSAP address (or URI of any telecommunication service / server) corresponding to the terminal line identifier (ID). The line identifier may be the telephone number of the terminal device. An embodiment may thus vary within the scope of the following claims.

Claims (24)

1. A method for determining an identifier, comprising:
a) using the unique identifier of the network node to request from the database the identifier of at least one server for the device connected to the specified node; and
b) determining the identifier of at least one server serving the area in which the specified device is located;
however, the request contains the default server address set in the specified device using at least parts of the specified unique identifier. 2. The method according to claim 1, wherein said node is a component of a wireless network, and said device is a wireless device. 3. The method according to claim 1, wherein said node is a component of a fixed network, and said device is a stationary device. 4. The method according to claim 1, wherein said unique identifier comprises at least one of the following: a cell identifier of a cellular transmission system, an address of a medium access control level for a LAN access point, and a device line identifier. 5. The method according to claim 4, wherein said cell identifier is a global cell identifier, wherein said server address is set by default based on at least one of the following: mobile network code, mobile country code and location area code of the specified global identifier honeycombs. 6. The method according to any one of claims 1 to 5, in which the specified identifier of at least one server is requested using a request sent to the domain name system. 7. The method according to any one of claims 1 to 5, in which the server address by default contains a unified resource identifier. 8. The method according to any one of claims 1 to 5, wherein said database is implemented as a domain name system server. 9. The method of claim 8, wherein said server of a domain name system comprises at least one server from a translation server and a location server that service said network node to obtain said at least one indicated server identifier. 10. The method according to any one of claims 1 to 5, in which the specified server functions as a response node of the public security service. 11. The method according to any one of claims 1 to 5, also containing a request for the specified identifier of at least one server based on the resource record of the name owner pointer. 12. The device for determining the identifier, containing means of access to the service, configured to use the identifier of the network node to which the specified device is connected, when requesting from the database the identifier of at least one server, the specified at least one server serving the area, where the specified device is located, and the specified service access tool is configured to set the default server address using at least parts of the specified unique th ID. 13. The device according to item 12, in which the specified node is a component of a wireless network. 14. The device according to item 12, in which the specified node is a component of a fixed network. 15. The device according to item 12, in which the specified unique identifier contains at least one of the following: cell identifier of the cellular transmission system, the address of the medium access control level for the LAN access point and the line identifier. 16. The device according to clause 15, in which the specified cell identifier is the global identifier of the cell, and the default server address is configured to set it by default, based on at least one of the following: mobile network code, mobile country code and code the location area of the specified global cell identifier. 17. The device according to any one of p-16, in which the specified means of access to the service is configured to request the specified identifier of at least one server using a request sent to the domain name system. 18. The device according to any one of paragraphs.12-16, which is a mobile device. 19. The device according to any one of paragraphs.12-16, in which the specified means of access to the service is configured to provide the specified server address by default with a unified resource identifier. 20. The device according to any one of paragraphs.12-16, in which the specified means of access to the service is configured to request the specified identifier of at least one server based on the resource record of the name owner pointer. 21. A database configured to store server identifiers in association with network node identifiers, wherein the database is configured to output at least one of the indicated identifiers by the server in response to a request sent to the corresponding node identifier, said request containing a server address default, including at least parts of the specified network host identifiers. 22. The database according to item 21, in which the specified unique identifier contains at least one of the following: cell identifier of the cellular transmission system, the address of the medium access control level of the LAN access point and the identifier of the line of the device connected to the network node. 23. The database according to item 21 or 22, which is implemented as a server of a domain name system. 24. Machine-readable medium containing a computer program containing code means for implementing the steps of the method according to any one of claims 1 to 11, when executed in a computing device.

Images