Sie sind auf Seite 1von 26
AXE Operation & Maintenance — Exchange Data ooooooaodno 06 August, 2008 Size Alteration LRi © Device and Route Data Connection of SNTs, DIPs and devices Useful APT commands ET185 Route and B-number Analysis C7 signaling AXE O8C Exchange Data AXE Operation & Maintenance — Size Alteration ASCiCeL, Igy Size alteration is the name of the function used to change the file sizes in the data store [\ 5 of the central processor. In this store, the data related to all the blocks are stored. a The initial size of the data records in the data store is set when the exchange is installed. The information about the sizes to set originates from the customer in the form of filled in data forms or similar information. The information is referred to as exchange requirement. Customer Ericsson eral i |, Brel lao) : 1 | exchange Data Traneeript stascdecinae, | —_iteaurement foment mma wa = I Scormngsane [8 Emenee The commands with size alterations are loaded as one of the first files when loading the exchange data. This has to be done because no other data can be loaded before the file sizes in data have enough space for storage of the data. 06 August, 2000 AXE ORC Exchange Date AXE Operation & Maintenance — Size Alteration Extension of hardware requires change of file sizes in the data store. When the hardware is installed in the exchange, various operational instructions have to be used depending on hardware type (the ‘names of the instructions are "Connection of ...”). These operational instructions describe the commands and actions required to connect the new hardware in software. ‘More data required However, In most cases of size alteration, only sofware is Program Store Jaa Store affected. New incividuals Some examples: created “te handle more simultaneous call setup (see figure) | Program of = more subscribers would lke to have a certain block RE =| subscriber service E Ea ey Register incividuas = {0 add more analysis cases in the analysis tables ee ae 05 August, 2000 AXE OBC Exchonge Data a AXE Operation & Maintenance — Size Alteration Extension of hardware requires change of file sizes in the data store. When the hardware Is installed in the exchange, various operational instructions have to be used depending on hardware type (the names of the instructions are “Connection of..."). These operational instructions deseribe the commands and actions required to connect the new hardware in software. More data required However, In most cases of size alteration, only software is affected. Program Store Data Store Some examples: Now inn - to handle more simultaneous call setup (see figure) = more subscribers would like to have a certain [Program of| = subscriber service block RE - to add more analysis cases in the analysis tables 2s [Pe resister individuals inDala Store If only a size alteration Is to be made in the exchange, the ‘operational instruction “Size Alteration of Data Records" has to be followed. (08 August, 2009 AXE O8C Exchange Data 4 AXE Operation & Maintenance — Size Alteration In order to find the block or the blocks that are affected by a size alteration, the AXE system uses a numbering of the size alteration cases. This number is referred to as “size alteration event" or just SAE. The SAE is used as a parameter in all the commands related to the size alteration function. There are two different types of size alterations in the AXE: * Global size alteration event These events will affect files in more than one block. An example is the number of routes in the exchange. Several blocks in the system store information about each route and all these blocks require the same file size (e.g. blocks for statistics and supervision). + Local size alteration event These events will only affect one block in the exchange. Examples of such events are the number of devices inside one block. 08 August, 2008 AXE O8C Exchange Data 5 AXE Operation & Maintenance — Size Alteration The size alteration events (the numbers) are allocated in a special way in order to make it possible for the system to know which system (APT or APZ) and which type of event it is (local or global). The following numbering has been used inside the system: * Global events: = - APT: 000-299 - APZ: 300-499 * Local events: - APT: 500-799 - APZ: 800-999 (06 August, 2008 AXE O8C Exchange Date 6 i i AXE Operation & Maintenance — Size Alteration There are only three commands related to the function for size alteration. The three commands are: + SAAIL The command is used to increase the files in a size alteration event. * SAADI Used when decreasing the file sizes in one SAE. * SAAEP Used when printing the number of individuals currently defined for the SAE. (08 August, 2000, AXE OBC Exchange Date 7 AXE Operation & Maintenance -— Size Alteration As an example, all the blocks that have telephony devices use SAE=500. In case of changing the number of devices in the block this SAE must be used. The example below show how to increase the number of UPDN3 devices of 32: