Procedure for the management of a subscriber database in a...

Telephonic communications – Plural exchange network or interconnection – Interexchange signalling

Reexamination Certificate

Rate now

  [ 0.00 ] – not rated yet Voters 0   Comments 0

Details

C379S207030, C379S230000

Reexamination Certificate

active

06175623

ABSTRACT:

FIELD OF THE INVENTION
The present invention relates to a procedure for managing a subscriber database maintained in a telephone exchange on the basis of changes in subscriber data.
DESCRIPTION OF RELATED ART
The management of subscriber data in a telephone exchange includes the management of all data relating to the subscriber. Subscriber data are maintained in a subscriber database. Subscriber data are used in conjunction with invoicing, dialling and other functions associated with the telephone exchange and setup of calls by subscribers.
In this application, ‘decimal position’ refers to a so-called decimal position number of the subscriber, which in the telephone exchange database corresponds to the record number of e.g. a file called Interfaces. Decimal position range refers to an area in this file.
In earlier practice, decimal position numbers were only used for local interfaces. The subscriber module always has a constant number of interface positions; therefore, a constant-sized range of decimal positions is reserved for a local interface when a module is being created. The size of the range cannot be changed. Thus, it can be assumed that each module has one continuous decimal position range reserved for it.
To facilitate the operations pertaining to a given module, there is a directory in which a reference to the beginning of the decimal position range of the module is stored when the module is being created. When operations are to be carried out on the entire module, the beginning of the decimal position range is obtained from the directory and the file is read from that point onward until a record belonging to another module is encountered.
At present, decimal position numbers are also used for V5 interfaces. V5 interfaces (V5.1 and V5.2) are defined in the ETSI (European Telecommunications and Standards Institute) standards of the ETS 300 324 and ETS 300 347 series. V5 interfaces enable subscribers belonging to a physically separate access network to be connected to a telephone exchange using a standard interface. A dynamic concentrator interface V5.2 consistent with the ETS 300 347-1 and 347-2 standards consists of one or more (1-16) PCM (Pulse Code Modulation) cables. One PCM cable comprises 32 channels, each of which with a transfer rate of 64 kbit/s, i.e. 2048 kbit/s in all. The V5.2 interface supports analogue telephones as used in the public telephone network, digital, such as ISDN (Integrated Services Digital Network) basic and system subscriptions as well as other analogue or digital terminal equipment based on semi-fixed connections. A static multiplexer interface consistent with the ETS 3000 324-1 and 324-2 standards consists of one 2048 kbit/s PCM cable. Except for the ISDN system subscription, the V5.1 interface supports the same subscriber types as the V5.2 interface.
When a V5 interface is being created, the number of subscribers that may be comprised in the interface cannot be known for sure. Therefore, in the case of V5 interfaces, it must be possible to reserve and release decimal position ranges as needed after the interface has been created. Thus, a V5 interface may have an arbitrary number of decimal position ranges of different sizes reserved for it. Between the ranges there may be a vacant range, a range reserved for another V5 interface or a range reserved for a local interface or all or these.
For each V5 interface, the directory may contain one reference, several references or no references, depending on the number of decimal position ranges existing for the interface and on whether there are free or reserved records between them. If there are only free records between the ranges belonging to the same V5 interface, the latter range is not included in the directory because the file browsing structure of the TDL language used for processing the data in the database skips free records.
The problem is on what basis the directory is to be updated when ranges are reserved or released in the database.
SUMMARY OF THE INVENTION
The object of the present invention is to eliminate the aforesaid problem. A specific object of the present invention is to present a new type of procedure for updating the directory in a telephone exchange when decimal position ranges are reserved or released in the database.
As for the features characteristic of the present invention, reference is made to the claims.
In the procedure of the invention for the management of the subscriber data of a subscriber database in a telephone exchange with a V5 interface and/or local interface connected to it, a decimal position range is reserved for local subscribers in conjunction with the creation of a subscriber module. The range is released when the module is deleted. The decimal position range or ranges for a V5 interface are reserved and released by a separate command or in conjunction with the creation or deletion of the subscriber. Further, in the procedure of the invention, data indicating the locations of the decimal position ranges are updated in a directory. According to the invention, the directory is updated on the basis of the content of the range preceding and/or the range following the decimal position range to be reserved or released. A decimal position range may comprise one or more decimal positions.
Thus, the directory operations pertaining to the reservation of a decimal position range are greatly dependent on the content of the ranges or records surrounding the range to be reserved, and also on whether a part of the range to be reserved has already been reserved for the same V5 interface or for some other purpose.
The inference process relating to the updating of the directory data is as follows. If the range to be reserved or a part of it has already been reserved for another V5 or local interface, no reservation can be made and therefore no directory operation is needed. On the other hand, if the range to be reserved or a part of has already been reserved for the same V5 interface as the range currently to be reserved, the directory operation is very easy. The range previously reserved is removed from the directory if it is present in it, and the range to be reserved is added to the directory. No other directory operations are needed.
Generally, the range to be reserved is completely free before the reservation. Before a range reservation is made, the reserved range preceding the range to be reserved is examined to establish whether it belongs to the same V5 interface, a different V5 interface or a local interface. If the range belongs to the same V5 interface, then the range to be reserved need not be added to the directory. If the range belongs to a local interface or another V5 interface, then the range to be reserved has to be added to the directory.
After the range preceding the range to be reserved has been checked, an actual reservation is made and at the same time the range being reserved is added to the directory if this is necessary according to the principles described above. Upon reserving the range, the procedure verifies whether the range following the reserved range needs to be present in the directory.
The range following next after the reserved range may belong to the same V5 interface, a different V5 interface or a local interface. If this next range belongs to a local interface, no further directory operations are needed. If the next range belongs to the same V5 interface as the reserved range and the range preceding the reserved range did not belong to the same V5 interface as the reserved range, then the range must be deleted from the directory. If the next range belongs to a different V5 interface than the reserved range but to the same V5 interface as the range preceding the reserved range, then the range must be added to the directory.
Further, if all three ranges belong to different V5 interfaces, then only the reserved range has to be added to the directory. If all three ranges belong to the same V5 interface, no changes are needed in the directory.
When a range belonging to a given V5 interface is to be released, the range preceding

LandOfFree

Say what you really think

Search LandOfFree.com for the USA inventors and patents. Rate them and share your experience with other people.

Rating

Procedure for the management of a subscriber database in a... does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Procedure for the management of a subscriber database in a..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Procedure for the management of a subscriber database in a... will most certainly appreciate the feedback.

Rate now

     

Profile ID: LFUS-PAI-O-2437763

  Search
All data on this website is collected from public sources. Our data reflects the most accurate information available at the time of publication.