DE10260824A1 - Converting address character sequences for telecommunications system involves analyzing address sequence, constructing sequence in second format based on second numbering plan and range identifiers - Google Patents

Abstract

The method involves analyzing an address sequence in a first format based on a first numbering plan identifier (NPLI1) and telecommunications range identifier (TON1) to convert an address used by a first telecommunications system into a unique address for use in a second system at a lowest possible level and constructing the sequence in the second format on the basis of the converted address with a second numbering plan identifier (NPI2) and range identifier (TON2). The method involves analyzing an address sequence in a first format based on a first numbering plan identifier and telecommunications range identifier to convert an address used by a first telecommunications system into a unique address for use in a second telecommunications system at a lowest possible level and constructing the address character sequence in the second format on the basis of the converted address with a second numbering plan identifier and telecommunications range identifier. An independent claim is also included for the following: an arrangement for processing address sequences.

Description

The invention relates to a method for the implementation of address strings for telecommunication systems and an apparatus for using the method.

In digital communication networks usually exist different addressing formats of subscriber addresses with which establishing or maintaining a connection between telecommunications systems, which are connected to the communication networks. The participant addresses can among other things according to a so-called implicit numbering plan and / or a so-called explicit numbering plan his. For an address according to the implicit numbering plan an assignment of a telecommunications area in which the address validity with every single digit of the address. In one address according to the explicit numbering plan exist in coded form existing information elements of the address (NPI, TON) that the Define telecommunications area in which the address is valid has.

With a connection between telecommunication systems, that use different addressing formats, it is often necessary that the addressing formats due to an adaptation to signaling capabilities of the plants are implemented. Frequently require private telecommunication networks that even within this Networks an official or a private numbering plan to be used. It can therefore addresses on a telecommunication line at the same time of various numbering plans exist.

Through a historical adjustment from telecommunication system data processing programs to external Conditions (e.g. official traffic, QSIG protocol with different numbering plans, etc.) participant address treatment is often very unstructured, what possibly to incorrect signaling of subscriber addresses and / or incorrect ones Conduct telecommunications connections can. This is essentially because a conversion of the Addresses and a determination of the prefixes based on wrong criteria carried out or that the address data including the prefixes is too inflexible are. Moreover individual steps of address conversion are carried out decentrally, so that this is largely inconsistent.

• – Präfixe werden anhand der falschen Kriterien in die Adressen eingefügt oder aus den Adressen gelöscht, was in falschen Adressen und dadurch bedingt in Verbindungen zu falschen Zielteilnehmern bzw. in nicht möglichen Verbindungen resultiert;
• – ein Signalisieren von unterschiedlichen Telekommunikationsanlagenrufnummern auf verschiedenen Amtsleitungen und/oder auf privaten Netzleitungen ein und derselben Telekommunikationsanlage wird nicht oder fehlerhaft unterstützt;
• – ein Signalisieren von unterschiedlichen Anlagenrufummern auf ein und derselben Amtsleitung wird für unterschiedliche Endgeräte der Anlage nicht unterstützt;
• – ein ISDN-Nummerierungsplan wird auf privaten Netzleitungen (z.B. unter dem QSIG-Protokoll) nicht unterstützt;
• – ein privater Nummerierungsplan wird nicht unterstützt;
• – Leistungsmerkmale diverser Signalisierungsprotokolle, die ISDN-Adressen enthalten, werden nicht unterstützt;
• – Endgeräterufnummern von Telekommunikationsanlagen werden nicht eindeutig signalisiert;
• – Adressen werden mit falscher Kodierung signalisiert.

The following problems can occur:

• - Prefixes are inserted into the addresses based on the wrong criteria or deleted from the addresses, which results in incorrect addresses and therefore in connections to wrong target participants or in impossible connections;
• - Signaling of different telecommunication system numbers on different exchange lines and / or on private network lines of one and the same telecommunication system is not supported or is supported incorrectly;
• - Signaling different system numbers on one and the same trunk is not supported for different terminals in the system;
• - An ISDN numbering plan is not supported on private network lines (e.g. under the QSIG protocol);
• - a private numbering plan is not supported;
• - Features of various signaling protocols that contain ISDN addresses are not supported;
• - Terminal numbers of telecommunications systems are not clearly signaled;
• - Addresses are signaled with incorrect coding.

It is the object of the invention to provide a method that provides more reliable telecommunications connections in heterogeneous telecommunications structures. It is also the task the invention to provide a device with which the inventive method can be used.

The task is solved with a Method with the features according to claim 1 and with a device with the features according to claim 14th

Preferred developments of the invention are in the dependent claims specified.

The method according to the invention sees an assembly an address string from one of a first telecommunication system first format used in a by a second telecommunications system second format used. In an analysis step of the process the address string is analyzed in the first format based on a first numbering plan identifier NPI1 and of a first telecommunications area identifier TON1 to a subscriber address used by the first telecommunications system in one for the second telecommunications system unique format on one lowest possible Level. A set-up takes place in a set-up step the address string in the second format based on that in the Analysis step determined unique subscriber address on the Basis of a second numbering plan identifier NPI2 and a second telecommunications area identifier TON2.

This is advantageous a conversion of a subscriber address used by telecommunications systems in any first format in any second format supported. Furthermore, all of them can be supported with the method according to the invention Address formats (implicit, explicit) and all numbering plans (e.g. ISDN numbering plan, private numbering plans, etc.) on all telecommunication lines using all of them Protocols (e.g. DSS1, QSIG, private protocols, etc.) be achieved.

A preferred embodiment of the method according to the invention sees in the analysis step a conversion of the first numbering plan identifier NPI1 into a standard numbering plan identifier and converting the first telecommunications area identifier TON1 in a standard telecommunications area identifier. This embodiment also sees converting the standard numbering plan identifier in the construction step into the second numbering plan identifier NPI2 as well as a convert of the standard telecommunications area identifier in the second Telecommunications area identifier TON2.

This is advantageous in the analysis step converting the addressing mechanism into the invention incoming address string to a uniform, explicit Addressing format supported, what a consistent further treatment in the subsequent construction step or in mediation processes the second telecommunications system facilitated.

In a further preferred development of the method according to the invention the analysis step comprises determining one in the subscriber address Terminal number of the second telecommunications system contained in the first format.

This is advantageous correct signaling of different system numbers a switching system that, for example, due to a Connection to telecommunications networks from different network operators can result, supports. Furthermore, this can correctly signal different ones prefixes the same switching system can be achieved on different lines. Moreover is in more useful How to correctly signal subscriber addresses in the implicit addressing format to the terminal supported.

It is also cheaper Way a converting in the addressing mechanism according to the invention incoming address string in a terminal number (implicit) supported.

In a further preferred embodiment of the method according to the invention the analysis and set-up step takes place on the basis of installation data the first and the second telecommunication system.

This is advantageous an individual related to the two telecommunication systems Treatment of the individual steps of the method according to the invention supported.

In a further preferred embodiment of the method according to the invention are the setup data of the two telecommunications systems switching system related and / or telecommunication line related and / or formulated related to telecommunications terminals. Thereby can advantageously be based on different telecommunication structures (e.g. switching systems, telecommunications lines, end devices, etc.) related, individual processing of the individual steps of the method according to the invention be achieved.

The invention is described below the attached Figures closer described. It shows:

1 a basic representation of the method according to the invention;

2 a basic representation of an application of the inventive method to address strings; and

3 a schematic representation of a device with which the inventive method can be used.

• a) Einrichtungsdaten einer eigenen Telekommunikationsanlage für den ISDN-Nummerierungsplan;
• b) Einrichtungsdaten der eigenen Telekommunikationsanlage für den privaten Nummerierungsplan;
• c) Einrichtungsdaten der fremden Telekommunikationsanlage für den ISDN-Nummerierungsplan;
• d) Einrichtungsdaten der fremden Telekommunikationsanlage für den privaten Nummerierungsplan.

For improved functionality, the method according to the invention requires device data of the telecommunication structures which are involved in establishing and maintaining a telecommunication connection between the telecommunication systems. The facility data are preferably stored in tabular form in the following fourfold form:

• a) Setup data of a separate telecommunications system for the ISDN numbering plan;
• b) facility data of the own telecommunication system for the private numbering plan;
• c) Setup data of the external telecommunications system for the ISDN numbering plan;
• d) Setup data of the external telecommunications system for the private numbering plan.

The facility data for the third-party telecommunication system are preferably required if the latter is not able to signal its own system number and / or prefixes or associated identifiers. In the case of an address string of the third-party telecommunications system, the method according to the invention uses the device data for the third-party telecommunications system to check whether it is able to signal its system telephone number. Outgoing address character sequences to the external telecommunications system are brought into a format which the external telecommunications system processes can work.

The facility data stored in the tables of the telecommunications systems are based on a three-stage scheme arranged. Here are on a first (highest) level per terminal of the telecommunication system specific addressing data stored. This is especially then useful, if end devices with different system numbers to one and the same telecommunications system are switched on, for example when end devices from different companies are connected to one and the same telecommunications system.

On a second (middle) level of the facility data can for different Trunk group, that are connected to the telecommunication systems, specific Addressing data must be stored. This is particularly advantageous if if a telecommunication system to different telecommunication networks Network operator is switched on and different over each of these networks System numbers signaled.

At a third (lowest) level The facility data are specific to each telecommunications system Addressing data stored. This can be viewed as a standard case the addressing data for all end devices and all trunk group the telecommunication system are identical.

Tabelle 1 The telecommunications system call number of each telecommunications system is required in order to signal all addresses of this telecommunications system unambiguously outside the telecommunications system or within a domain. For this purpose, a database which the method according to the invention accesses contains the following table:

Table 1

• – Länderkennzahl: Bezeichnung für ein Land oder einen Dienst (z.B. 49 für Deutschland);
• – Nationale Kennzahl: Bezeichnung für eine Stadt oder einen Dienst (z.B. 69 für Frankfurt);
• – Regionale Kennzahl: Anlagenrufnummer der Telekommunikationsanlage (gültig innerhalb einer Stadt);
• – Vorgegebener Einwahlteil der Regionalkennzahl: vorgegebene Durchwahlnummer (falls die tatsächliche Durchwahlnummer dem Dienstanbieter nicht bekannt ist);

Table 1 contains the following fields for the ISDN numbering plan:

• - Country code: name for a country or a service (eg 49 for Germany);
• - National code: name for a city or a service (eg 69 for Frankfurt);
• - Regional code: system telephone number of the telecommunications system (valid within a city);
• - Predefined dial-in part of the regional code: predefined extension number (if the actual extension number is not known to the service provider);

• – Stufe-2 Regionalkennzahl: Bezeichnung einer Stufe-2 Region (nicht notwendiger Weise im geographischen Sinn);
• – Stufe-1 Regionalkennzahl: Bezeichnung für eine Stufe 1 Region (nicht notwendiger Weise im geographischen Sinn);
• – Stufe-0 Regionalkennzahl: Rufnummer der Telekommunikationsanlage, die in einer Stufe 1 Region gültig ist;
• – Vorgegebener Einwahlteil der Stufe-0 Regionalkennzahl: vorgegebene Durchwahlnummer (falls die tatsächliche Durchwahlnummer dem Dienstanbieter nicht bekannt ist).

Table 1 contains the following fields for the private numbering plan:

• - Level-2 regional indicator: designation of a level-2 region (not necessarily in the geographical sense);
• - Level 1 regional code: Name for a level 1 region (not necessarily in the geographical sense);
• - Level-0 regional code: Telephone number of the telecommunications system that is valid in a level 1 region;
• - Specified dial-in part of level 0 regional code: predefined extension number (if the actual extension number is not known to the service provider).

Unless data in table 1 needed the corresponding field remains empty.

Tabelle 2 In the event that an explicit address is to be converted into the implicit addressing format by means of the method according to the invention, information which is encoded in a "TON" field and represents the telecommunications area identifier must be converted into one or more additional digits before the address These additional digits are called TON prefixes. For this implementation, the setup data of the telecommunications systems contain the following table:

Table 2

Table 2 shows that for your own and for the foreign telecommunication system information about the Numbering plan and information about the telecommunications sector SOUND are included. The information about the Telecommunication area identifier for the ISDN numbering plan and for the private one Numbering plan designed in three stages. The numerical values for the prefixes of the Telecommunications area identifier for the private numbering plan are freely definable, so these are exemplary in the table to watch. As numerical values for the ISDN NPs are examples of those valid for Germany.

Tabelle 3 In the event that an explicit address is to be converted into an implicit address in the method according to the invention, information which is encoded in a numbering plan identifier NPI must be converted into one or more additional digits before the address. These additional digits are called NPI prefixes. The database that the method according to the invention accesses provides the following table for this implementation:

Table 3

Table 3 shows that both for your own as well for the third-party telecommunications system for the ISDN numbering plan and for the private numbering plan information for the numbering plan identifier prefix (NPI prefix) are. Here are the NPI prefixes for both ISDN numbering plan, as well as for the private numbering plan freely definable, the numerical values in the table are exemplary.

For each requires an improved mode of operation of the method according to the invention Trunk group, that is switched on to the telecommunication systems and via that Connections are set up an indexing at which level the connections are operated. For example, a line, based on the ISDN numbering plan from a telecommunications system In Dusseldorf to a telecommunications system in Frankfurt, one Level identifier "National" (possible would also be "International") to be unambiguous to be. A line according to the ISDN numbering plan from a telecommunications system in Düsseldorf to a telecommunications system in Paris has to face that Level identifiers "International" have to be unambiguous to be.

Tabelle 4 For this purpose, the database that is accessed by the addressing mechanism according to the invention has the following table:

Table 4

For the method according to the invention to function properly, it must also be defined for each line bundle of the telecommunications systems in which addressing format addresses for a connected telecommunications system are to be signaled. Possible format identifiers are:
Implicit: NPI = unknown TON = unknown
Explicit, TON = unknown: NPI ≠ unknown TON = unknown
Explicit, TON ≠ unknown: NPI ≠ unknown TON ≠ unknown

Tabelle 5 For this purpose, the database which is accessed by the addressing mechanism according to the invention provides the following table:

Table 5

How to see Tables 1 to 5 can be set-up data for both your own and for others Telecommunications system registered. A fourfold of the registered Data results from diversifying the data for the ISDN numbering plan and the private numbering plan.

Tabelle 6 In order for the method according to the invention to work properly, the line-related facility data furthermore require an indexing according to which numbering plan internal telephone numbers (extension numbers) are to be signaled outside the telecommunications system. The database provides the following table for this

Table 6

• 1. Nummerierungsplankennzeichner = ISDN (Explizit) Telekommunikationsbereichkennzeichner ≠ unbekannt, z. B. 49-211-5354-334 TON = internatinal 211-5354-334 TON = national 5354-334 TON = regional Gültige Telekommunikationsbereichskennzeichner TON sind International, National, Regional
• 2. Nummerierungsplankennzeichner = ISDN (Explizit), Telekommunikationsbereichskennzeichner = unbekannt: z. B. 00-49-211-5354-334 0-211-5354-334 5354-334
• 3. Nummerierungsplankennzeichner = unbekannt (Implizit) Telekommunikationsbereichskennzeichner = unbekannt: z. B. 0-00-49-211-5354-334 0-0-211-5354-334 0-5354-334 8-88-49-2-9943-334 8-8-2-9943-334 8-9943-334 334
• 4. Nummerierungsplankennzeichner = Privat (Explizit), Telekommunikationsbereichskennzeichner = unbekannt: z. B. 88-49-2-9943-334 8-2-9943-334 9943-334
• 5. Nummerierungsplankennzeichner = Privat (Expizit) Telekommunikationsbereichkennzeichner ≠ unbekannt: z. B. 49-2-9943-334 TON = Stufe 2 2-9943-334 TON = Stufe 1 9943-334 TON = Stufe 0 (Lokal) Gültige Telekommunikationsbereichskennzeichner TON sind: Stufe 2, Stufe 1, Stufe 0 (Lokal)

The following will refer to 1 a description of individual transformation steps provided by the method according to the invention is carried out. The blocks 1 . 2 . 3 . 4 and 5 represent addressing formats of address character strings that are transferred to the inventive method for processing. The five individual addressing formats are:

• 1. Numbering plan identifier = ISDN (explicit) telecommunication area identifier ≠ unknown, e.g. B. 49-211-5354-334 TON = international 211-5354-334 TON = national 5354-334 TON = regional Valid telecommunication area identifiers TON are international, national, regional
• 2. Numbering plan identifier = ISDN (explicit), telecommunications area identifier = unknown: e.g. B. 00-49-211-5354-334 0-211-5354-334 5354-334
• 3. Numbering plan identifier = unknown (implicit) Telecommunication area identifier = unknown: z. B. 0-00-49-211-5354-334 0-0-211-5354-334 0-5354-334 8-88-49-2-9943-334 8-8-2-9943-334 8-9943 -334 334
• 4. Numbering plan identifier = private (explicit), telecommunications area identifier = unknown: e.g. B. 88-49-2-9943-334 8-2-9943-334 9943-334
• 5. Numbering plan identifier = private (excess) telecommunications area identifier ≠ unknown: e.g. B. 49-2-9943-334 TON = Level 2 2-9943-334 TON = Level 1 9943-334 TON = Level 0 (Local) Valid telecommunication area identifiers TON are: Level 2, Level 1, Level 0 (Local)

The blocks 6 . 7 . 8th . 9 and 10 the 1 are entry points into an address conversion process. The addressing format of block 1 corresponds to the addressing format of block 9 , Block's addressing format 2 Block's addressing format 7 , Block's addressing format 3 Block's addressing format 6 , Block's addressing format 4 Block's addressing format 8th and the addressing format of block 5 is the addressing format of block 10 ,

The addressing formats of the blocks 6 . 7 . 8th . 9 and 10 can be achieved through the following transformations:
Transformation T1: conversion of the addressing format from block 6 into the block addressing format 7
Transformation T2: conversion of the addressing format from block 6 into the block addressing format 8th
Transformation T4: conversion of the addressing format from block 7 into the block addressing format 9 Transformation T5: conversion of the addressing format from block 8th into the block addressing format 10 ,

In the block 11 there is an address in implicit format, which is neither assigned to the ISDN numbering plan nor to the private numbering plan, and that by means of a transformation T3, which is a conversion of the addressing format from block 6 into the block addressing format 11 makes, can be achieved. Furthermore, the addressing format of block 11 , which can be in the form of an extension number such as 334, can be achieved by the following transformations:
Transformation T3: conversion of the addressing format from block 6 into the block addressing format 11
Transformation T6: conversion of the addressing format from block 9 into the block addressing format 11
Transformation T7: conversion of the addressing format from block 10 into the block addressing format 11 Block's addressing format 12 corresponds to Block's addressing format 9 , It is obtained through the following transformations:
Transformation T8: conversion of the addressing format from block 9 into the block addressing format 12 Transformation T10: conversion of the addressing format from block 11 into the block addressing format 12

The addressing format of the block 13 corresponds to Block's addressing format 10 , It is obtained through the following transformations:
Transformation T9: conversion of the addressing format from block 10 into the block addressing format 13
Transformation T11: conversion of the addressing format from block 11 into the block addressing format 13

Block's addressing format 14 corresponds to Block's addressing format 7 , It is obtained through a transformation T13, which is a conversion of the addressing format from block 12 into the block addressing format 14 makes.

Block's addressing format 15 corresponds to the addressing format of block B. It is obtained by a transformation T14, which is a conversion of the addressing format from block 13 into the block addressing format 15 makes.

The addressing format of the block 16 corresponds to Block's addressing format 6 , It is obtained through the following transformations:
Transformation T12: conversion of the addressing format from block 11 into the block addressing format 16
Transformation T15: conversion of the addressing format from block 14 into the block addressing format 16
Transformation T16: conversion of the addressing format from block 15 into the block addressing format 16 ,

The blocks 12 . 13 . 14 . 15 and 16 define “exit points” from the addressing mechanism according to the invention. The addressing format of block 12 corresponds to an addressing format of a block 17 , the addressing format of block 14 an addressing format of a block 18 , the addressing format of block 16 an addressing format of a block 19 , the addressing format of block 15 an addressing format of a block 20 and the addressing format of the block 13 an addressing format of a block 21 ,

The addressing formats of the blocks 17 . 18 . 19 . 20 and 21 correspond to those of the five "entry blocks" 1 . 2 . 3 . 4 and 5 , As a rule, the addressing formats of the addresses transferred to the method according to the invention are not identical to the addressing formats of the addresses supplied by the method.

The following are those with the inventive method feasible individual transformations T1 to T16 explained in more detail. One refers "Incoming" label on an address string, transmitted from the external telecommunication system to the own telecommunication system becomes. A term "outgoing" means one Address string from your own telecommunications system is transmitted to the external telecommunications system.

For the case that an implicit address in an explicit address to be converted, the in the prefix of the numbering plan identifier (NPI prefix) deleted from the address string and the encoded numbering plan identifier must match defined. The operations required for this will be performed in the transformations T1, T2 and T3. The NPI prefixes will be taken from Table 3. For incoming addresses from the foreign telecommunications system the facility data of the third party from the database for this purpose Telecommunication system used. For outgoing addresses uses the facility data of their own telecommunications system.

Transformation T1: If in the implicit Address of the NPI prefix for the ISDN numbering plan is included, it must be deleted and the coded numbering plan identifier must be set to "ISDN".

Transformation T2: If the implicit address contains the NPI prefix for the private numbering plan, it must be deleted and the coded numbering plan identifier must be set to "private". The transformation T2 thus corresponds to converting the addressing format from block 6 into the block addressing format 8th ,

Transformation T3: If none of the aforementioned NPI prefixes is contained in the implicit address, the address is treated like an internal number. This corresponds to a transition from the addressing format of the block 6 the addressing format of the block 11 ,

For the case that an implicit address in an explicit address to be implemented must contain information contained in the telecommunications area identifier prefix (TON prefix) is converted into the encoded telecommunications area identifier become. The TON prefix from the implicit address deleted become. The operations required for this are carried out by the transformations T4 and T5 provided. They are only possible if the NPI prefix is in the coded numbering plan identifier was implemented.

The TON prefixes are taken from Table 2. For incoming addresses from the third-party telecommunications system, the setup data of the third-party telecommunications system must be taken in Table 2. The setup data of your own telecommunications system must be used for outgoing addresses.

Transformation T4: If the address contains the TON prefix "International", this must be deleted and the coded telecommunications area identifier must be set to "International". This corresponds to a conversion of the block addressing format 7 to Block's addressing format 9 ,

In the event that the TON prefix "National" is contained in the address, it must be deleted from the address and the coded telecommunications area identifier must be set to "National". This also corresponds to a conversion of the block addressing format 7 the addressing format of the block 9 ,

In the event that neither the international nor the national TON prefix, but the TON prefix "Regional" is contained in the address, this must be deleted from the address and the coded telecommunications area identifier must be set to "Regional". Even if the TON prefix "Regional" is not included in the address, the coded telecommunications area identifier must be set to "Regional" (usually TON prefixes "Regional" are not used). This also corresponds to a conversion of the Addressing format of the block 7 the addressing format of the block 9 ,

Transformation T5: In the event that the TON prefix "Level 2" is contained in the address in accordance with the private numbering plan, this must be deleted from the address and the coded telecommunications area identifier must be set to "Level 2". This corresponds to a conversion of the block addressing format 8th to Block's addressing format 10 ,

In the event that the TON prefix "level 2" is not contained in the address, but instead the TON prefix "level 1", this must be deleted from the address and the coded telecommunications area identifier must be set to "level 1". This also corresponds to a conversion of the block addressing format 8th the addressing format of the block 10 ,

In the event that neither the TON prefix "level 2" nor the TON prefix "level 1" is contained in the address, but the TON prefix "local", it must be deleted from the address and the coded telecommunications area identifier must be opened "Local" can be set. Even if the local TON prefix is not included in the address, the coded telecommunication area identifier must be set to "Local" become. This also corresponds to a conversion of the addressing format of the block 8th into the addressing format of the block 10 ,

Transformations T6, T7:
The method according to the invention tries to delete the own telecommunication system call number from the address for each incoming address. If this attempt to delete is successful, the addressing format of the block is 11 the result of this deletion. This addressing format, which corresponds to an internal address or telephone number, is used as a unique address for storage in a data memory.

For the case that the attempt to delete the telecommunications system number is unsuccessful the inventive method as many parts of the telecommunications system number as possible delete the address, to be the lowest possible establish a unique level of the incoming address. This lowest possible unique address is then for uses data storage. For in the case of address signaling, the transformations T8 and T9 performed.

For each address going to the third-party telecommunications system, the method according to the invention for producing a lowest-level uniqueness attempts to delete the telecommunications system call number of the third-party telecommunications system from the address. If this attempt to delete is successful, the addressing format of the block is 11 (internal address of the external telecommunication system) the result of this deletion attempt.

This internal address is always then signaled to the external telecommunications system if this is unable to provide telecommunications system numbers and prefixes process or signal.

If the deletion attempt is unsuccessful the method according to the invention tries as many parts of the telecommunications system number as possible delete the address, around the lowest possible unique To reach address level. The telecommunications system number or parts of it are used according to the table 1 used. Alternatively, with the help of the transformations T8 and T9 adjusted the level of the telecommunications area identifier TON as will be described in more detail below.

Transformation T6: In the event that the address to be converted is available in the ISDN numbering plan and the telecommunications system number can be deleted from the address, the coded numbering plan or telecommunication area identifiers are set to “unknown”. This corresponds to a conversion of the addressing format of the block 9 the addressing format of the block 11 ,

Transformation T7: In the event that the address to be converted is available in the private numbering plan and the telecommunications system number can be deleted from the address, the coded numbering plan identifiers or telecommunications area prefixes are set to "unknown". This corresponds to a conversion of the addressing format from Block 10 into the block addressing format 11 ,

Tabelle 7 Corresponding to the coded numbering plan or telecommunications area identifier in The original address is deleted step by step according to the table below.

Table 7

Transformations T8, T9: According to the level designation of the desired telecommunication area identifier in Table 4, it may be necessary to raise the telecommunication area identifier in the outgoing direction with the device data of the own telecommunication system, or in the incoming direction with the device data of the other telecommunication system. This can be done using the missing address parts according to Table 1. Transformation T8: (usually for addresses in the outgoing direction) In the event that the level of the telecommunications area identifier is to be raised to a higher level, the coded telecommunications area identifier is set to this level and part of the outgoing address is added in accordance with Table 1. This corresponds to a conversion of the block addressing format 9 to Block's addressing format 12 ,

Transformation T9: (normally for addresses in the outgoing direction) In the event that the address is in the private numbering plan and the level of the telecommunications area identifier is to be raised to a higher level, the outgoing address is supplemented accordingly in Table 1. This corresponds to a conversion of the block addressing format 10 the addressing format of the block 13 ,

The two examples above for the transformations T8 and T9 show an increase in the coded Telecommunications area identifier from a lower up a higher one Level. In contrast, is also a lowering of the coded telecommunications area identifier from a higher possible at a lower level provided a higher level region identifier for incoming addresses belongs to the region of your own telecommunications system, or for outgoing Addresses for the region of the foreign telecommunications system. This will the regional identifier with that of your own / third-party facility data compared. For example, for a telecommunications system number the country code "49" is deleted in a telecommunications system in Germany, without making the address ambiguous. This is why made to keep the address within the system at the lowest possible bring clear level.

In the following two examples for the transformations T8, T9 is the country code "49" and the level 1 regional code "2".

Transformation T8: (normally for addresses in the incoming direction) If the address is available in the ISDN numbering plan, the coded telecommunications area identifier can be reduced from the "International" level to the "National" level by deleting the corresponding country code from the address in accordance with Table 1 , This corresponds to a conversion of the block addressing format 9 to Block's addressing format 12 , In the same way, a reduction from "national" to "regional" is also possible.

Transformation T9: (usually for addresses in the incoming direction) In the event that the address is in the private numbering plan and is to be reduced from the higher level of the telecommunications area identifier "level 1" to the lower level of the telecommunications area identifier "local", see table 1 the corresponding part is deleted from the address. This corresponds to a conversion of the block addressing format 10 to Block's addressing format 13 , Ge a lowering from "level 2" to "level 1" is also possible.

Transformations T10, T11, T12: The Transformations T10, T11 and T12 are used to parts of telecommunication system numbers to insert in addresses. The outgoing address is the telecommunications system number the own telecommunications system inserted in the address. To this The purpose is the own telecommunications system number according to the table 1 used. For the Case that the internal address (extension number) to the outside the telecommunications system or the domain in which it is valid, to be sent, it must be converted into the explicit format are built by placing the telecommunications system number in front of it becomes.

In the event that the ISDN numbering plan is preferred in the device data according to Table 6, as shown in the example below, the telecommunications system call number must be inserted according to the ISDN numbering plan. Table 4 shows the level up to which the address is added. This corresponds to a conversion of the block addressing format 11 to Block's addressing format 12 ,

If the private numbering plan for the outgoing address is preferred according to the facility data in Table 6, your own telecommunications system number must be inserted according to the private numbering plan. This corresponds to a conversion of the block addressing format 11 to Block's addressing format 13 ,

The transformations T10, T11 and T12 used for incoming addresses to the telecommunication system number insert the third-party telecommunications system into the address. To the telecommunication system number of the third-party telecommunication system taken from Table 1. If an incoming internal address (extension number) ambiguous in your own telecommunications system or in your own domain it must be made clear. This could be the case, for example be if the third-party telecommunications system is not able to signal the complete ISDN address but only the internal extension number. Then it is necessary the incoming Address around the telecommunications system number of the connected third party Supplement telecommunications system. For this purpose, first tries to convert the address into the explicit format by the transformations T1, T2, T4 or T5 described above are carried out. Only for in the event that this is not possible is (transformation T3), the telecommunications system number inserted, if this is included in the facility data according to Table 1.

In the following two examples the connected telecommunication system has the telecommunication system number 69-7505 in the ISDN numbering plan and 9021 in the private numbering plan. In the two examples it can be seen that the incoming address is not unique and by adding the foreign telecommunications system number is made clear in the respective numbering plan.

The two examples correspond to a conversion of the block addressing format 11 into the block addressing format 12 or from block 13 ,

Transformations T13, T14: In the event that an explicit address is to be converted into an implicit address, the information of the coded telecommunications area identifier must be converted into one or more additional digits before the address. In the following example, Block's addressing format is converted for this purpose 12 to Block's addressing format 14 ,

The assignment of the TON prefix to Telecommunications area identifier in the ISDN or private numbering plan is shown in Table 2. For outgoing addresses to someone else Telecommunication system must be from the setup data of this table the part of the external telecommunications system can be selected. For incoming The part of your own telecommunications system must be selected for addresses.

Transformations T15, T16: If an explicit address is to be converted into an implicit address, the information in the coded numbering plan identifier must be converted into one or more additional digits before the address. The following example shows a conversion of the block addressing format 14 to Block's addressing format 16 , It can be seen that the NPI prefix for the ISDN numbering plan "0" is placed in front of the address. So that the external telecommunications system can also process this prefix for an outgoing address, this prefix must be taken from the setup data of the external telecommunications system according to Table 3 become.

Converting the encoded numbering plan identifier in the NPI prefix can only run then if the coded telecommunications area identifier has already been in the TON prefix was converted.

The assignment of the NPI prefixes to the coded numbering plan identifiers according to the ISDN or the private one Numbering plan is shown in Table 3. For outgoing Addresses to the external telecommunications system must be from this table the part of the external telecommunications system can be taken. For incoming Addresses must have the prefix according to your own Telecommunication system chosen become.

The structure of the method according to the invention 1 shows a division into different logical units. This takes place in the transformations between the blocks 3 . 6 . 11 . 16 and 19 an exclusive treatment of the address in the implicit numbering plan.

The left two branches according to the structure 1 show a treatment of addresses in the ISDN numbering plan. The treatment includes the blocks 1 . 2 . 7 . 9 . 12 . 14 . 17 and 18 ,

The right two branches of the structure of 1 include processing of addresses in priva numbering plan. The treatment takes place in the blocks 4 . 5 . 8th . 10 . 13 . 15 . 20 and 21 ,

Furthermore, from the 1 to recognize that in the upper part of the structure shown, the address is converted into a uniform, unambiguous format at the lowest possible level. The uniform format can be an addressing format according to the block 11 or an explicit addressing format according to the blocks 9 and 10 include. Ultimately, it is the conversion of the address in the upper part of the structure from 1 an address analysis process, the analysis process transforming T1 to T7 with the addressing formats of the blocks 6 . 7 . 8th . 9 and 10 includes.

The lower part of the 1 The structure shown shows a conversion of the address from the uniform, unambiguous standard format into an address according to a desired numbering plan or telecommunications area. Ultimately, it is the lower part of the structure in 1 a synthesis process of the address, which transforms T8 to T16 with the addressing formats of the blocks 11 . 12 . 13 . 14 . 15 and 16 includes.

Furthermore, from the structure of the 1 can be seen that the method according to the invention is symmetrical in two respects. A horizontal symmetry includes the transformations of the left two branches (ISDN numbering plan) which correspond to those of the right two branches according to the private numbering plan. Tables 1 to 6 are used to select the corresponding facility data for the transformations of the addresses in the ISDN numbering plan and in the private numbering plan.

Furthermore, in the structure of 1 to recognize that the addressing formats in the upper part correspond to those in the lower part of the structure (vertical symmetry). The transformations in the lower part, which in the sense of the aforementioned synthesis form an address from the uniform address format in accordance with the desired facility data, are processed in the reverse order to the transformations in the upper part (analysis process).

The two aforementioned symmetries can advantageous for the individual steps of the method according to the invention with the facility data both your own and someone else's telecommunication system be used. A useful one This supports the reusability of programmed functions.

2 shows, using concrete examples, an appearance of the addresses in the individual blocks in the course of the method according to the invention. The figure serves to make the transformation steps carried out by the addressing mechanism according to the invention visible using address examples.

3 shows a basic representation of a device with which the inventive method can be used. The device detects 1 a receiving unit 4 that are used to receive address strings with the first telecommunications system 2 connected is. Furthermore, the device comprises an analysis unit 5 and an assembly unit 6 , Furthermore, the device comprises a transmission unit 7 with a second telecommunications system 3 connected is. The sending unit 7 is used to transmit the address string converted by the method according to the invention to the second telecommunications system 3 , Furthermore, the device according to the invention comprises a memory 8th , in which the method according to the invention is preferably stored as a data processing program. The first telecommunications system is for an address arriving from the external telecommunications system 2 the third-party telecommunications system and the second telecommunications system 3 the own. The first telecommunications system is for an address going to the external telecommunications system 2 the own telecommunication system, and the second telecommunication system 3 the stranger.

For an address arriving from the external telecommunications system becomes the analysis part of the method according to the invention with the facility data own telecommunications system. The synthesis part of the method according to the invention is in this part with the facility data of the external telecommunications system carried out, if they exist in the database.

For an address going to the external telecommunications system the analysis part of the method according to the invention with the facility data the external telecommunications system. The synthesis part of the method according to the invention for one outgoing address to the external telecommunication system is with the facility data of your own telecommunications system, if provided these are available in the database.

The method according to the invention is advantageous Way so able to address addressing insufficiency of telecommunications systems. He has to be all the more active become, the larger the Address Handling inadequacies of the telecommunications systems are pronounced, and vice versa.

It also depends on a sequential control system from whether the inventive method with its analysis and synthesis part in a single step, or processed in successive steps.

Further advantages of the method according to the invention include correct signaling of addresses in performance-specific message elements of performance features spanning telecommunications systems (such as call diversion, transfer, callback, voice memory, etc.). The return tion of the address to the uniform, unique, lowest-level standard format is used in address comparisons for performance features of telecommunications systems in an advantageous manner to check or determine whether the addresses are identical.

1

contraption to build address strings

2

first telecommunications system

3

second telecommunications system

4

receiver unit

5

analysis unit

6

construction unit

7

transmission unit

8th

Storage

Claims (18)

Method of building an address string from one used by a first telecommunication system first format with a first numbering plan identifier (NPI1) and a first telecommunications area identifier (TON1) in a second used by a second telecommunication system Format with a second numbering plan identifier (NPI2) and a second telecommunications area identifier (TON2) with the procedural steps: - Analyze the address string in the first format based on the first Numbering chart identifier (NPI1) and the first telecommunications area identifier (TON1) to one used by the first telecommunications system Address in one for the second telecommunications system unique address on one lowest possible Convert stage; and -  Build up the address string in the second format based on the converted Address with the second numbering plan identifier (NPI2) and the second telecommunications area identifier (TON2). The method of claim 1, wherein the analyzing step a procedural step - Convert of the first numbering plan identifier (NPI1) into a standard numbering plan identifier and converting the first telecommunications area identifier (TON1) into a standard telecommunications area identifier includes; and the construction step being a process step -  Convert of the standard numbering plan identifier in the second numbering plan identifier (NPI2) and converting the standard telecommunications area identifier in the second telecommunications area identifier (TON2). The method of claim 2, wherein in the building step converting the standard numbering plan identifier determined in the analysis step into a number of the second numbering plan identifier (NPI2), and converting the standard telecommunications area identifier determined in the analysis step into a number of the second telecommunications area identifier (TON2) takes place. The method of claim 2 or 3, wherein the standard numbering plan identifier and the standard telecommunications area identifier be in a coded form. Method according to one of claims 1 to 4, wherein in the analysis step a number associated with the first numbering plan identifier (NPI1) is in the coded first numbering plan identifier (NPI1) is converted and a number that corresponds to the first telecommunications area identifier (TON1) is assigned in the coded first telecommunications area identifier (TON1) is converted. Method according to one of claims 1 to 5, wherein during the conversion the address used by the first telecommunications system in the for the second telecommunications system unique address on the lowest potential Stage converting into a terminal number of the second telecommunication system he follows. The method of claim 6, wherein with the aid of the coded standard numbering plan identifier and standard telecommunications area identifier determined in the analysis step, a telecommunications system call number of the second telecommunications system from the address string in the first format is deleted so that the terminal number remains and the encoded standard numbering plan identifier and standard telecommunication area identifier are set to "unknown". A method according to claim 6 or 7, wherein the terminal number, that is known to the first telecommunications system, a telecommunications system number is placed in front of the first telecommunications system. Method according to one of the preceding claims, wherein the telecommunications area identifier (TON1, TON2) three-stage are trained and at a level change between the first and the second format an adaptation of the address to the corresponding one Stage. Method according to one of the preceding claims, wherein the analysis and set-up step based on the facility data of the first and the second telecommunications system. The method of claim 10, wherein the facility data of the two telecommunication systems related to switching systems and / or related to telecommunications lines and / or related to telecommunications terminals are formulated. Method according to one of the preceding claims, wherein the address strings in the first and / or second format part of a ISDN numbering plan, part of a private numbering plan or Are part of an implicit numbering plan, the encoded Numbering plan identifier (NPI1, NPI2) and telecommunications area identifier (TON1, TON2) can assume all values valid within the numbering plans. Method according to one of claims 1 to 12, wherein the processed Addresses Part of connection setup messages and / or of any feature messages for any protocols, what coding for the numbering plan and the telecommunications area in the address strings support. Contraption ( 1 ) for editing address strings, with: - one with a first telecommunication system ( 2 ) connected receiving unit ( 4 ) to receive an address string in a first format with a first numbering plan identifier (NPI1) and a first telecommunication area identifier (TON1); - an analysis unit ( 5 ) for analyzing the received address string on the basis of the first numbering plan identifier (NPI1) and the first telecommunication area identifier (TON1) in order to determine one of the first telecommunication system ( 2 ) received address in a for a second telecommunication system ( 3 ) convert unique address at the lowest possible level; - an assembly unit ( 6 ) for constructing the address string in the second format on the basis of the converted subscriber address with the second numbering plan identifier (NPI2) and the second telecommunication area identifier (TON2); and - one with the second telecommunication system ( 3 ) connected transmitter unit ( 7 ) for sending the from the assembly unit ( 6 ) constructed address string to the second telecommunication system ( 3 ). Device according to claim 14 with a memory ( 8th ), in which the facility data for converting the address strings is stored. Device according to one of claims 14 or 15, wherein this part of the first and / or the second telecommunications system ( 2 . 3 ) is. Apparatus according to any one of claims 14 to 16, wherein the address strings in the first and / or in the second format part of an ISDN numbering plan, Part of a private numbering plan or part of an implicit one Numbering plans, and where the coded numbering plan identifiers (NPI1, NPI2) and coded telecommunications area identifier (TON1, TON2) can accept all values valid within the numbering plans. Device according to one of claims 14 to 17, wherein either the first telecommunications system ( 2 ) and / or the second telecommunication system ( 3 ) represents a terminal that processes addresses.