WO2002011464A2

WO2002011464A2 - Data bank function for mobile radio subscribers

Info

Publication number: WO2002011464A2
Application number: PCT/DE2001/002841
Authority: WO
Inventors: Steffen Engmann; Markus Placho
Original assignee: Siemens Aktiengesellschaft
Priority date: 2000-08-01
Filing date: 2001-07-26
Publication date: 2002-02-07
Also published as: DE10037510A1; WO2002011464A3; AU2001278403A1

Abstract

The aim of the invention is to provide a method with which subscriber data regarding a subscriber can be easily, ergonomically and efficiently found on the basis of the subscriber address. To this end, a control authority (20) is enabled to find subscriber addresses that contain at least one domain name by inquiring with a data bank (7) that contains at least the subscriber data and the subscriber address.

Description

⁾ u>) H ¹ I cn o Cn O <1 l £)

Φ

O: cn et

The addressing of a database according to the invention based on at least one do ain name in the subscriber address of a subscriber makes it possible to find subscriber data efficiently using ergonomically designed (because easily remembered) addresses. Addresses with the structure "Name @ Domain *," Namel .Name2 @ Subdomain.domain * etc. are easier to remember for telecommunications subscribers than pure numeric sequences. A domain usually corresponds to e.g. according to internet protocol an address area (usually managed by a server, etc.); Accordingly, a subdomain is usually one of the following a partial address range of a domain. The alphanumeric part of the name includes e.g. Letters and / or numbers and / or other characters. The invention makes it easy and efficient to find subscriber data for subscriber addresses constructed in this way.

According to one embodiment of the invention is in one

Telecommunications network provided only one subscriber database (hereinafter also abbreviated database) for subscriber data. This subscriber database can be requested by all control bodies of the telecommunications network for subscriber data of a subscriber if necessary, stating the subscriber's address (e.g. also parts of the subscriber's address). The advantage of this embodiment is that no database comparison is necessary because only one database is provided, so that the address of the database is clearly defined.

According to a further preferred embodiment of the invention, a plurality of subscriber databases are provided, each of which is identified by the subscriber addresses. This enables the load to be reduced by dividing the subscriber data into several, for example, physically separable databases. Moreover, it is possible in such a way that

FIG. 1 shows a first embodiment of a telecommunications network with a subscriber database,

FIG. 2 shows a telecommunications network with several subscriber databases,

FIG. 3 shows a telecommunications network with several subscriber databases and address servers,

Figures 4 and 5 for a telecommunications network with several subscriber databases and address servers schematically the signal flow when querying subscriber data.

FIG. 1 shows a telecommunications network 1 with a plurality of network nodes 2, 3, 4, 5, 6, which, for example, MSC,

Gateway MSC, BSC, AUC, EIR, VLR or other network components or accesses of these network components can show. A subscriber database 6 is connected to a network node 5 (for example a VLR), in which the subscriber data of all non-roaming subscribers is stored

Telecommunication network are stored and are accessible. Subscriber data can be requested from each control entity of the telecommunications network 1 from the subscriber database 6, specifying at least parts of the subscriber address (for example by specifying only the subscriber name or only name and part of the subdomains or the name and part of the subdomains and domain etc.) can be. In this case, the requesting control entity (for example MSC 2) sends at least parts of the subscriber address 6 to the subscriber database 6 (which can also be a number used in the network which corresponds to the subscriber address or which designates it) and receives the requested subscriber data back from the subscriber database 6.

FIG. 2 also shows a telecommunications network 1 with a plurality of network elements 5, 6, 7, 8, 9, for example a mobile radio network (for example UMTS mobile radio network, WAP-compatible network etc.). Several subscriber databases 7, 8, 9 are shown here, which contain the subscriber data of all or at least some subscribers. In the present example, they only contain the subscriber addresses of certain subscribers. A subscriber database 7, 8, 9 contains only the subscriber data of subscribers whose subscriber address contains a specific domain and / or subdomain (s). For example, the data of all participants with a participant address "Name @ Participant database 1.provider .de * in the

Participant database "Participant database L.provider.de * 7 and the participants with a participant address (name = any name of the participant)" Name@Teilnehmerdatenbank2.provider .de * stored in the participant database "Participant database2 * of the provider" provider * in the country de (Germany) his. A request from a control entity (network elements 2-6) for subscriber data of a telecommunications subscriber is made by sending the request to the subscriber database 7, 8 or 9, which can be identified by parts (domain and / or sub-domain and / or subdomains) of the subscriber address, and from this the Participant data are compiled and sent back to the requesting supervisory authority (for example 5).

According to FIG. 3, a plurality of subscriber databases with the designations TDB1 to TDB4 with the reference numbers 7-10 are likewise provided in a telecommunications network 1 with a plurality of control instances 2-6 (e.g. MSC, BSC, AUC, EIR, etc.). In addition, in FIG. 3 there are also a number of elements ÄV 1 to ÄV 3 called address servers with the

Reference numerals 11-13 are provided; If a control entity requires 2 subscriber data for a subscriber address, it asks for this subscriber data or the address of the subscriber database responsible for this subscriber or his subscriber address from an address server 13, which the

Returns subscriber data or the address of a database 7 containing this subscriber data. So it is possible co co fO MP »P>

Cn o Cn o Cn o Cn

PJ P- Q y 3 Φ

Hl P sQ φ PJ: l-i H G3 y cn y rt ^

P. Φ P- y ι

Φ y

P- Λ l-i y Ω

Φ y Cn

H M

P- -S y P- or H

1-5 rt P>

P> y

N Φ y y P- ιΩ Φ

H P- Φ φ P-

P- Φ y

Hi P- Φ y y H J Φ ι-J 3

Φ & y Hi

(X H

H H PJ

P> φ ιQ y cn Φ

Φ cn cn Φ

Φ P-

Φ h y

<! Φ cx Φ l-i

P- ι-i φ

O w α co y J rt rt p- ι-i

Φ y O y y P. P "J P- P- y Φ y tr cn cn J Φ rt p. 3 PJ l-i y

Φ N cn cn f φ o

a participant database TDB 1 (7) and in a second step 18 returns it to the control entity 20, which control entity 20 asks for the participant data in the database 7 specified as the database address for the participant address in the third step 19, whereupon 7 participant data from the participant database 7 in step 21 be transmitted to the supervisory authority 20.

Claims

claims

1. Method for locating subscriber data of a subscriber of a telecommunications network, in particular mobile telecommunications network, identifiable by his subscriber address, the subscriber address containing at least one alphanumeric part of the name and a domain name, a database (7) for subscriber data being identified on the basis of at least the domain name, which database (7) contains subscriber data of the subscriber.

2. The method according to claim 1, characterized in that the subscriber data of at least all subscribers whose subscriber address contains this domain name are stored in a database.

3. The method according to claim 2, characterized in that the database can be addressed via this domain name.

4. The method of all the preceding claims, characterized in that the subscriber data of all subscribers with an address containing this subdomain are stored in a database for a subdomain.

5. The method according to any one of the preceding claims, characterized in that the database with subscriber data of subscribers with a specific subdomain name in its subscriber address can be addressed via this subdomain name.

6. The method according to claim 4 or 5, characterized in that a database with subscriber data of subscribers with a subdomain designation in their subscriber address can be addressed via the subdomain designation and the domain designation of a subscriber address.

7. The method according to any one of the preceding claims, characterized in that for a search for subscriber data of a subscriber with a subscriber address, a request from a control body (20) of a telecommunications network (1) to one of several address servers (13) of the telecommunications network (1) is sent the address server (13) determines the database address (domain; subdomain, domain) of the database (7) containing the subscriber data on the basis of the subscriber address (domain; subdomain; domain, subdomain) and sends it to the requesting control authority (20) the database address of the database (7) is sent back (18) in order to enable the requesting supervisory authority (20) to use the database address to request the subscriber data from the database (7) (19, 21)

8. The method according to any one of claims 1-7, characterized in that for a search of a control entity (20) for

A request from the control entity (20) of the telecommunication network (1) to at least one of several address servers (13) of the telecommunication network is sent (11) by the address server (13) based on a table

Participant database address of those

Participant database is determined in which participant database participant data of the participant are stored, and the address server (13) from this participant database (7) queries (14) all or certain subscriber data relating to the subscriber, whereupon the subscriber database (7) sends subscriber data back to the control unit (20) or to the address server (13) for forwarding to the control unit (20) (15).

9. The method according to claim 7 or 8, characterized in that the subscriber database - address, in which subscriber data are stored for the subscriber, is determined on the basis of the subdomain designation in the subscriber's address.

10. The method of one of the preceding claims, characterized in that the subscriber database address of a database (7), in which subscriber data of the subscriber is stored, is determined by the address server (13) on the basis of the domain name in the subscriber address.

11. The method according to any one of the preceding claims, characterized in that a database (7) determines subscriber data for a subscriber only or, inter alia, on the basis of an alphanumeric portion (name) of the subscriber address that precedes the subdomain designations and the domain designations of the subscriber address.

12. The method according to any one of the preceding claims, characterized in that the subscriber address contains an alphanumeric component before the subdomain and before the domain, the parts of which are separated from one another by at least one point or another character.

13. The method according to any one of the preceding claims, characterized in that the subscriber data details contains regarding the authentication of a subscriber and / or charging for services for the subscriber and / or a list of services that the subscriber may use and / or in which countries and / or networks the subscriber may use the services.

14. The method according to any one of the preceding claims, characterized in that Telekom unikatiorisdienstleistungen including language services and data services can be addressed comprising at least one domain via a subscriber address of a subscriber.

15. Device for performing the method according to one of the preceding claims.

16. The device (13), in particular according to claim 15,

with an input for inquiries from a telecommunications network control entity (2, 3, 4, 5, 6, 20) for subscriber data of a subscriber specifying a subscriber address of the subscriber,

with a memory or access to a memory with a table of subscriber addresses or parts of subscriber addresses and subscriber databases for subscriber data assigned to these subscriber addresses or parts of subscriber addresses, with a device for determining a

Subscriber database address of a subscriber database for subscriber data based on the subscriber address or parts of the subscriber address of the subscriber, - with a transmission device for sending the subscriber database address or in the Participant database of participant data received to the requesting control entity (20).

17. The device (13) according to claim 16, characterized in that it comprises:

a device for querying (14) subscriber data stored in a subscriber database (7) in the subscriber database (7),

- With a device for querying (14) the subscriber data from a subscriber database (7), the subscriber database address of which can be determined by the device (13) on the basis of a table by means of the subscriber address communicated to it (13) by the control device (20), - the transmitting device is designed in such a way that the subscriber data transmitted to the device (13) by the subscriber database (7) is forwarded (16) to the control device (20).