NZ542082A - Network planning tool - Google Patents

Abstract

A method of configuring or virtually documenting a cellular IP network architecture using a computer application is described. The method involves receiving input specifying an existing or new network site, receiving input specifying one or more elements associated with the network site, for each of one or more elements, storing data in a database structure identifying the element to associate the element with the network site, for each of the one or more elements, receiving input specifying one or more sub element modules associated with the element, for each of the one or more sub element modules, storing data in the database structure identifying the sub element module to associate the sub element module with a respective element, assigning IP addresses to the sub element modules, and storing data in the database structure specifying the IP address assigned for each sub element module.

Description

1 - No: 542082 Date: 26 August 2005 24 NOV 2006 BSCETVE d NEW ZEALAND PATENTS ACT, 1953 COMPLETE SPECIFICATION NETWORK PLANNING TOOL I, RAJ AT SARNA, a citizen of India of 9F 14 Waterloo Quadrant, Auckland, do hereby declare the invention for which we pray that a patent may be granted to us, and the method by which it is to be performed, to be particularly described in and by the following statement: I FIELD OF THE INVENTION The present invention relates to software and systems for network planning and configuration. In particular, the invention relates to, but is not limited to, software and systems for assisting in the planning and configuration of mobile telecommunications networks.

BACKGROUND TO THE INVENTION Networks, such as mobile telecommunications networks, are formed from a number of elements such as transceivers, repeaters and other components. In planning and configuring the network architecture, these components need to be recorded along with information indicating 10 their technical nature, configuration, and other key parameters. Often, information regarding their configuration and other parameters pertaining to their function need to be determined and assigned by a network administrator.

The effort required in maintaining such a log is high. Further, when changes to network configuration are made, parameters may need to be reassigned, which can have repercussions for 15 interlinked elements.

SUMMARY OF THE INVENTION It is an object of the present invention to provide software and or a system for assisting in network planning. The system and software could, for example, enable configuration of a 20 telecommunication network and automate IP network planning using a database and an interface producing documented IP planning information. This provides a commercially useful effect among other things, it decreases the human and other resources required to configure and/or document a cellular IP network architecture.

In one aspect the present invention may be said to consist in a method of configuring or 25 virtually documenting a cellular IP network architecture, using a computer application, comprising the steps of: receiving input specifying an existing or new network site, receiving input specifying one or more elements associated the network site, for each of one or more elements, storing data in a database structure identifying the element to associate the element with the network site, for each of the one or more elements, receiving input specifying one or 30 more sub element modules associated with the element, for each of the one or more sub element modules, storing data in the database structure identifying the sub element module to associate the sub element module with a respective element, assigning IP addresses to the sub element Intellectual Property Office of N.Z. 23 MAY 2008 Dcrcn/cn element, assigning IP addresses to the sub element modules, and storing data in the database structure specifying the IP address assigned for each sub element module.

In another aspect the present invention may be said to consist in a computer program for configuring or virtually documenting a cellular IP network architecture the program being 5 adapted to: receive input specifying an existing or new network site, receive input specifying one or more elements associated the network site, for each of one or more elements, store data in a database structure identifying the element to associate the element with the network site, for each of the one or more elements, receive input specifying one or more sub element modules associated with the element, for each of the one or more sub element modules, store data in the 10 database structure identifying the sub element module to associate the sub element module with a respective element, assign IP addresses to the sub element modules, and store data in the database structure specifying the IP address assigned for each sub element module.

In one aspect, the present invention may be said to consist in a computer program that can store information relating to elements in a network, define interrelationships between the 15 elements and/or information, determine parameters for one or more of the elements, and assign the determined parameters to the elements.

In another aspect, the present invention may be said to consist in a system that can store information relating to elements in a network, store interrelationships between the elements and/or information, determine parameters for one or more of the elements, and assign the 20 determined parameters to the elements.

In one embodiment, the network is a mobile communications network. The elements could be components of the network, such as transceivers and repeaters. The information could relate to configuration parameters of the elements, and technical definitions of the elements. The interrelationships could connect information with associated elements, elements to other 25 associated elements and/or show configuration relationships defining the architecture of the network. Parameters determined by the program and assigned to elements could include element identifiers and network addresses, such as IP addresses.

This invention may also be said broadly to consist in the parts, elements and features referred to or indicated in the specification of the application, individually or collectively, and any 30 or all combinations of any two or more of said parts, elements or features, and where specific integers are mentioned herein which have known equivalents in the art to which this invention relates, such known equivalents are deemed to be incorporated herein as if individually set forth.

BRIEF DESCRIPTION OF THE DRAWINGS Preferted embodiments of the invention will be described with reference to the following drawings, of which: Figures 1.1 — 1.4 show flow diagrams of a method and computer program for creating, modifying and viewing a cellular IP network architecture, Figure 2 shows a database structure of the computer programme, Figures 3.0 — 3.19 show various screen shots of the user interface of the computer program, Figure 4 shows a flow diagram for configuring or documenting a new or existing cellular IP network architecture, Figure 5 shows a flow diagram for modifying a cellular IP network architecture, Figure 6 shows a flow diagram for viewing network information of a cellular IP network architecture, Figures 7 — 22 show the logical configuration of the software and hardware for the system, and Figures 23 — 25 show a database restoration user interface, Appendix A, B shows an overview of the invention, Appendix C shows code and queries for configuring new network architectures, Appendix D shows general information in relation to IP addressing.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS Overview of One Embodiment of the Invention An overview of the functionality of the software according to one embodiment of the invention is as follows.

The system and software enables a user to configure and plan a cellular IP network architecture prior to its implementation, or to virtually or physically document or monitor or modify a cellular IP network architecture after it has been implemented. The system optionally enables automatic IP address assignment to a cellular IP network based on its configuration.

The user can select from options: create a new network site, modify an existing network site and view information of an existing network site.

When the option to create a new network site is selected, the user is taken to a graphical user interface where he/she can select a country where the new site is to be created, and then the user can enter the site name that is to be created/configured. Countries are kept in the database backend in a table of countries, hence when the user has to select a country, countries in the 5 database can be visible.

The new site name entered by the user is checked against the existing sites in the database for the selected country, and if the site already exists, the user is notified. Otherwise, the new site is stored in the database in a table of countries and their sites and notified. In this way, there is a mechanism for storage of all countries and their sites as new sites are configured for planning.

All network elements used are stored in a generic table in the database along with their abbreviations and vendors. The user is directed to the next interface page where all network elements are displayed. The selected country and the entered site are also carried forward to the next user interface so that the user knows what site in which country he/she is planning for. In this user interface page, the user can select a quantity value for the network elements for the 15 specified site of the specified country. The quantity is selected/entered by the user for respective network elements and this information is first shown on a confirmation page and then stored in the database in a table.

Another table for the country and its network elements is created automatically using queries as long as the table for that country does not already exist. The network elements are 20 compared to their abbreviations from the generic elements table and the abbreviations of network elements of the specified site that the user has given quantity greater than zero to, are selected. Then using the site name provided, an ID for the element is created by adding the site name, abbreviation of the element and a value starting from 1 (depending on the selected/entered quantity) into one word. In this way, the table of a country and its elements in 25 the database contains every site that is in the country, selected elements' abbreviation and an automatically generated elementID that has incrementing number at the end starting from 1, to depict the number of instances of the same element in the site.

All cards in network elements are stored in the database in a generic table with element names and their abbreviations. The next user interface shows all cards for the elements that the 30 user had given a quantity of greater than zero in the previous interface page. The selected country and the entered site are also carried forward to the next user interface so that the user knows what site in which country he/she is planning for. All the instances of the elements are also shown. Hence, the interface page has the required network elements, their cards and their instances from the country element table in the database. There are boxes for selection of either active or inactive for each card. Therefore, the user can specify whether a card of a specific network element with a specific element ID (which contains the site name, element abbreviation and an incrementing number depending on the quantity of that element in that site) is active or inactive. Each user interface page displays one element, its cards, its instances and selections. One 5 page displays a specific number of cards, and if more cards need to be viewed, another interface page is used. There is an option in each card interface page to go to the next element's card information. All this information of cards is shown on a confirmation page after which it is all stored in the database in tables for each element instance and their card status.

Using the table created from the user's entry of card status, a table in database is created 10 for each country, as long as it does not already exist to store the element instances (that is, elements in that site that have been specified by the user before, to have quantity greater than zero in that site) and active cards, which are selected from the previous table depending on which cards the user specified as active.

Another generic table in the database is created to store information on all interfaces in a 15 telecommunication network. The table contains the interface name, abbreviation of the elements that comprise the interface and the cards of the elements that need to be active to have the interface operational.

Another table in the database is created for each country, as long as the table for that country doesn't already exist. This table contains the network site name and its active interfaces. 20 This is generated by a set of rules. The active card table in the database from the user's input is compared to the generic tale of active cards of active elements required to have an active interface. If the active cards required in the generic table for an interface exists in the user specified active cards table for the elements required in the generic interface table, then the interface is active in that site. In this way, this particular table is populated in the database.

The user is then directed to an IP Addressing user interface. The selected country and the entered site are carried forward to the next user interface so that the user knows what site in which country he/she is planning for. All elements are displayed that have been specified before to have quantity greater than zero from the country elements table in the database. In this way, any change in the elements would mean that every user interface would show the updated 30 version. The elements' instances are shown with options for user to enter the values of first, second, third octets, fourth octet starting at, subnetmask, VLAN name and VLAN ID. This information is shown in a confirmation page after which it is stored in a table for a specific country and its IP Addresses, which is created if the table for that country (and its IP Addresses) does not already exist.

The information is stored in exacdy the same format as the user input. Another table is created with the 4th octet of the IP address being automatically populated incrementing for a particular element ID (element instance), and refreshed to increment again for the next element instance. In this way, information of IP Addresses for cards of network elements for network 5 sites are populated and each country has its information on what IP Addresses are given to what cards of network elements in what network sites.

In the start interface page of the application, if the user had selected the option to view information of existing sites, the user is directed to another interface page where the user has to select the country and site that he/she wants to view the information of. The country is shown as 10 selection from the database of existing countries and site is displayed from the database table of country and site. If the selected country does not have a site, the user is notified. When the sites of the country are displayed, the user is also told how many sites exist in that country. The user then selects a site. The user is then asked what to view, that is, whether to view all element IDs in that site, or to view all active cards in that site, or to view all active interfaces in that site or to 15 view all IP Addressing information of that site. There are more user defined viewing options that are created. The tables in the databases are appropriately selected with options to view selected column to view the information given above. This viewing is generated by queries that are triggered by the options. The user is also asked if the user wants to view the information on the application window itself or in a word excel file. Then the documentation is generated. The 20 choice of format of output is expansive.

In the start interface page of the application, if the user had selected the option to modify the existing sites, the user is directed to an interface where user has the option to: add a country, add a new network element, delete an existing network element, change quantity of an existing element at a site, add a new card to an existing element at a site, change the status of a card of an 25 existing element at a site or to delete a card from an existing element at a site.

If the user selects the option of adding a country, the user is directed to an interface where the user inputs the country name and when submit triggered, if the country already exists in the generic country table in the database, the user is notified, otherwise, the country name is added and the user is notified. This operation would be limited to user with a high level of 30 authentication.

If the user selects the option of adding a new network element, the user is prompted to input the name of the new element, name of the vendor and the abbreviation. If the element or abbreviation already exists in the generic table of elements, the user is appropriately notified, otherwise, the information is stored in the generic table in the database, and the user is notified. This operation would be limited to user with a high level of authentication.

If the user has selected the option to delete an existing network element, the user is directed to another interface page where the existing elements are displayed from the generic 5 table in the database that stores all the elements. The user can select what element he/she wants to delete and the entire row in the table of that element including its vendor, and abbreviation is deleted. This operation is again only permitted to a user of very high authenticity.

If the user has selected the option to change quantity of network elements in an existing site, the user is directed to a user interface page where the user has to select the country and the site which are displayed as selection from the appropriate tables in the database. Then a list all elements is displayed with the option to specify their quantity values. When the user specifies the new quantity values, the previous quantity values for that site are cleared, and the new values are stores. Appropriately, the country element tables are also created, as long as that country does not already have a table for elements.

If the user selected the option to add a new card to an existing element at a site, the user is taken to an interface page where the user selects the name of the network element from a display from the table of the database, and selects its abbreviation and then enters the name of a new card that needs to be added. If the card already exists, the user is notified, otherwise, the operation is performed. There is another option of whether the user wants to add multiple cards to the element, whereby, the user enters the names of cards and a stored procedure is called which enters the information to the generic card table in the database.

If the user selects the option to change the status of cards at a site, the user is directed to the interface pages described before during creation of network site, and the abovementioned operation takes place.

If the user selects to delete a card from an existing element at a site, the user is directed to an interface page where the user selects the country, site, element and from the cards display of that element, the card that the user wants to delete.

This software can either be used as web-logon with server and hosts in different countries or can be used stand-alone on a machine.

In summary, the software and system can do one or more of the following: -Provide a global, web based Network IP Planning solution.

-Assist in configuring a cellular network and assigns IP Addresses to the network automatically.

-Standardise the process of IP Address Planning for a cellular network which is currently done by Excel sheets. The system may be configured to provide an end-to-end, web-based, global solution, with database backend and customised to the architecture of an entire cellular network covering all network elements.

-Assist in IP planning of an All-IP cellular architecture.

-Standardise the naming convention used for Network IP Planning.

-Assign IP Addresses to network elements to a card level and store information in dynamically built database.

-Run stand-alone as well as on a server-client basis.

-Suggest to a user, values to fill in, and subnet sizes and messages to assist in the planning of an IP network.

-Configure the network in various countries, with parameters like network sites, subnets, interfaces, network elements and cards of network elements. This configuration is assigned IP Addresses which form a dynamic relationship with the network information.

-Provide a front-end user interface with which the user interacts and provides information as required and the system has a backend database which keeps generic tables and computes network configuration and automatically and intelligently assigns IP Addresses to the whole network. This information including others in the database can be viewed on the system or on applications like Microsoft Excel.

-Provide a facility to modify and manage the existing network configurations.

-Be customisable to any cellular architecture.

Description of One Embodiment of the Invention The functionality of the software according to one embodiment of the invention is as follows, with reference to Figures 1.1 to 22. Figures 1.1 to 1.4 show flow diagrams indicating the method/architecture of the software and user activity in accordance with the invention. Figures 7 to 22 show schematically the logical configuration of hardware/software for implementing the method of Figures 1.1 to 1.4. Figure 2 shows the logical structure of the database tables. Figures 3.0 to 3.19 show screen shots demonstrating an example of use of the software. Figures 4 to 6 show flow diagrams indicating the methods for creating, viewing and modifying IP network plans. The paragraph numbering refers to reference numerals in Figures 1.1 to 1.4, Figures 3.0 to 3.19 and Figures 7 to 22. Figure 1.1 shows an overview of the software architecture. Figures 1.2 to 1.4 show aspects of the architecture in further detail.

Note: the software's backend database is preferably in Microsoft SQL Server. It contains 5 three types of tables: - -Reference — tables whose content is never changed or hardly ever changes. These form the information base for the NIPP software. Example is the NetworkElements table, which contains the network elements available to be setup at any given time at a network site. See Figure 2.1 for these tables.

-User Created — these are tables which are created and populated on the fly. Example the NewZealand_Elements table, which is created when the first time a network site is configured in New Zealand. It contains a list of all elements in New Zealand and which site they are in. See Figure 2.2 for these tables -Updated/Runtime — these are tables that get updated on a regular basis as the NIPP 15 software gets used. Example is the Country_Site table, which gets populated everytime a site is configured in the software. See Figure 2.3 for these tables. 1. The IP Planning solution allows the user to configure the cellular network in an All-IP architecture whereby IP Addresses are assigned to network elements. It is not necessary that all 20 network elements are assigned IP Addresses as it depends on the user and what network configuration is required. In this interface, the user is introduced to the system which prompts the user to either elect to create a new network (Figure 1.2), view the information on an existing network (Figure 1.3) or modify an existing network (Figure 1.4).

This interface in the first instance exposes basic functionalities of the system. Creating a 25 new network refers to simulated virtual configuration of a network site in a selected country and step-by-step allocation of resources to the network including network elements, cards, subnets, logical interfaces and IP Addresses. This is all stored in the database in a relationship-centric arrangement. The data is stored in the database and retrieved, manipulated and user-generated runtime tables are created which keep the records of new and existing networks. Multiple 30 network sites can be configured in a country and all countries in the world are available to be configured in the system. When created, this data is stored and accessed online as the system is web-based.

Connections between the network elements, cards, subnets, logical interfaces and IP Addresses are created virtually and their relationships are stored in the database. Naming convention for the cellular IP Planning is also standardised in this system when a new network is created. The output of creation of network configuration is that the user is provided with all information about the network as well as IP Address information of every network element to a card level on Microsoft Excel and on the application itself.

Viewing of the network information leads the user to an array of options to view which are, number of existing network sites (network sites that have been configured in the system) in a country, network elements and their naming convention in the site, all available subnets in the site, all cards of network elements and their status and all IP information of the network site/network element/country. All this information can be viewed in Microsoft Excel or be saved 10 as a file in Microsoft Excel.

Modifying the network refers to editing the values and information that is stored regarding a network site including adding network elements, removal of network elements, modification to status of network elements, adding cards to network elements, modification to status of cards of network elements, changing, deleting and adding of subnets and modifying IP Address 15 information of existing network sites. A screenshot of the user interface is shown in Figure 3.1 and it can be seen how the user has been given the choice to create, view or modify the network. Figure 4 shows a flowchart representing the steps taken to create a new network, Figure 5 shows the steps taken to view all information and Figure 6 represents the steps taken to modify/manage the existing network configurations/network sites. 2. This interface in the system is used by the user to initiate creation of a network site. This creation of the network site could be a simulation of a physically existing network site or a nonexistent network site which is being planned to be physically implemented in the future. This system allows the user to configure a network anywhere in the world on the computer using this 25 system, configure it with network resources, assign IP Addresses automatically, print the output on this system or on applications like Microsoft Excel and also manage the existing sites.

A screenshot of the interface is shown in figure 3.2 which indicates how the user is directed to select a country to create the site in, and enter the name of a network site. Figure 4 which is a flowchart representing creation of a new network site shows these steps of selecting a country 30 and entering a site in box (a). A list of all countries in the world are stored in the database in a generic/reference table 'countries' as shown in Figure 2 table (a). This table has a column named Ccntrf which is where all the country names are listed. The system extracts this list from the database and displays it on the user interface for the user to select. Next, the user can enter a network site name that is to be created/configured. The new site name entered by the user is 35 checked against the existing sites in the database in updated table 'county,_site> as shown in Figure 2 table 0 corresponding to the selected country, and if the site already exists, the user is notified. Otherwise, the new site is stored in the database in the table (f) called ' country_site' as shown in Figure 2. In this way, there is a mechanism for storage of all countries and their sites as new sites are configured for planning. A relationship between the new network site and the country in 5 which it is configured is established. This relationship holds in the future manipulation of data as new resources are configured onto the network. The country and site names are then defined as 'session variables' in the system. This ensures that even while the user continues with network IP Planning onto other interfaces and manipulates, inputs and output data, the names of country and site are fixed for that specific session and are visible on all interfaces for reference. 10 As this process is initiated again, new relational combination of country and site names is made into 'session variables' for that specific session. This carrying forward of selected country | and site to the next user interface until that particular session ends is done so that the user knows what site and in which country he/she is planning the network. 3. The next user interface displays all network elements on the screen for user to select and specify their respective quantity in the network site. These are candidate elements that can be used in the network site. Elements, for example, can be routers, switches, firewalls, base stations (BSC), antennas (Node B), MSCs, HLRs, servers and the like. This is not an exhaustive list, and other elements will be known to those skilled in the art. All network elements are stored in a 20 generic table in the database along with their abbreviations and vendor names. This table in the database is shown in Figure 2 table (b) called 'nwelementf with the columns namely 'element, 'abbreviation' and 'vendorThe system extracts the network element names and displays them on the screen. This display is dynamic because it is automatically updated if there are new network element entries into the 'nmlementi generic table, so that the user can work with the most updated 25 list of network elements at all times. This dynamic system increases the efficiency in terms of time and effort for network configuration/IP planning. Along with the names of network elements that are displayed on the screen, there are also dropdown boxes where the user can select the quantity value of the respective network elements which can range from 0 to as many as there might be required since that range can be manipulated with the platform that the system 30 runs on. A screenshot of the user interface is shown in Figure 3.3.

The selection of quantity of network elements is also depicted in the chronology of creation of network site in Figure 4 box (b). In the database, a table for the selected country and its network elements is created automatically run-time using queries which are explained here: a new table is created if a table for that country does not already exist for adding network elements, 35 the network elements are compared to their abbreviations from the generic elements table and the abbreviations of network elements of the specified site that the user has given quantity greater than zero to, are selected. Then using the site name provided, an ID for the element is created by adding the site name, abbreviation of the element and a value starting from 1 (depending on the selected quantity) into 1 word. This is the naming convention that the system 5 has inventively automatically generated using the method outlined above. This simplifies the process of IP network planning significantly as it is presently (before the invention) being done manually on spreadsheets.

An example of a table that is created/updated in the database for a country with the element ID and quantity is in Figure 2 table (h) called 'NewZealandJELEMENTS'. The columns 10 of the table include the site name, abbreviation of the network element and the element ID (auto-generated naming convention). An example of a configured site in New Zealand is FT which is in the first column, an abbreviation of a network element HLR is HR which is in the second column and the resulting auto-generated naming convention element ID is FTHRl which is in the third column.

If on the user interface, the user had selected a quantity of 3 for network element HLR, the first three rows would have FTHRl, FTHR2 and FTHR3 in the third column. In this way, the table of a country and its elements in the database contains every site that is in the country, selected elements' abbreviation and an automatically generated element ID that has an incrementing number at the end starting from 1, to depict the number of instances of the same 20 element in the site. 4. The next interface is to configure sub element modules on the network elements. Sub element modules can be any modules that are adapted to be used in a network element. They could include, for example, ports, network cards, sub interfaces and sub modules. This is not an 25 exhaustive list, and those skilled in the art will appreciate that there are other sub element modules that could be used. The following description refers to the use of the system/software for configuration of network cards. This is by way of example only, and it will be appreciated that the same description could apply to other sub element modules, such as those mentioned above. Any reference to a network card in the following description could be extrapolated to 30 meaning a sub element module. Network cards are network elements' capability modules, in other words, cards could provide different functions or could be for the purpose of capacity requirement or signalling/data requirements. Network elements that have been selected by the user to be configured to the selected site (with quantity greater than 0) now have to have cards configured. All cards for all network elements are stored in the database in a generic/reference 35 table called 'nwcards' as shown in Figure 2 table (k). They are stored in the table along with element names and their abbreviations. This user interface page displays all network elements that were selected to have quantity greater than 0 in the previous user interface page. These elements are depicted by their unique element IDs.

If the user selects an element ID and clicks on 'View cards', all the cards in the generic table 5 'nwcards' are extracted on the screen and the user can look at them to make sure that he/she needs all of them to be finally assigned IP Addresses. If not, the user can enable specific cards by selecting them and clicking on enable cards. Otherwise, in the auto-generated, run-time table of the country of that session for cards would be created (if it did not already exit in which case it would be updated), the site name, the auto-generated element ID of selected network elements 10 and all its respective cards would be populated.

An example of an auto-generated table is <Nen>Zealand_CARDS' as shown in Figure 2 table (m), which for example would have a site name of FT, element ID of FTHRl and card name of CCSUO-EO. Figure 4 box (c) shows the step of viewing cards of network elements in the chronology of process of creating a network site. A screenshot of this user interface is shown in 15 Figure 3.4 and it can be seen that the appropriate element IDs are extracted by the system and cards of the respective network elements can be viewed and specific cards can be enabled if required otherwise all network cards are used for configuration and finally IP Address Assignment. 5. The next user interface provides the user 2 choices of either continuing with IP Network Planning by assigning active interfaces and Subnet Addresses to the network or continuing with IP Network Planning by assigning IP Addresses to network elements individually, in other words without assigning subnets or interfaces. A screenshot of the user interface is shown in Figure 3.5. If the user chooses the former, he/she would be directed to a user interface where active 25 interfaces would be intelligently computed and extracted from the database and subnets assigned and new user-generated tables in the database would be created. This is all dynamic processing, in other words, if any value is modified, it would lead to changes in all relationships of the changed data. If the user chooses the latter, IP Addresses are simply assigned to all cards of network elements without assignment of subnet addresses. This step of the process of this system is 30 illustrated in the flowchart in Figure 4 decision box (d) which has two outcomes of box (e) which is 'Subnet IP Address Assignment' or box (h) which is 'Individual Network Element IP Address Assignment'.

These choices are provided to the user so that he/she has the freedom to assign IP Addresses without assigning them in particular subnets. Scenarios might arise in Network IP 35 Planning where this becomes vital. For instance, if the whole network has been assigned subnet addresses and IP addresses within those subnets, but there is a new addition to the network and without adding to the existing pattern of IP Addresses in the network, the planner wants to try to assign a specific address to the new element, he/she could opt for individual IP Address Assignment. 6. The next user interface relates to the first choice of selecting active interfaces and assigning subnet addresses to the network. There is a generic/reference table has been created in the database called 'nwinterj'aces' which contains a list of all network interfaces as shown in Figure 2 table (g). Comparing the list of active network elements in the 'country_ELEMENTS' table in the 10 database (for instance, NewZealand_ELEMENTS) with the names of the network elements in the generic interfaces table in the database ('nwinterfaces'), the system is queried to pick the active interfaces and displayed on screen. These values are also inserted/updated into a new/existing user-generated, run-time table in the database for the country in session, for instance NewZealand_ActiveInterface as shown in Figure 2 table (j). This table contains the 15 name of the site and the active interfaces. For instance, an entry in the table could be FT for the site and Mc for the active interface.

Next, comparing the active interfaces in the 'country_ActiveInterface' table with the interfaces in the interface generic/reference table, corresponding element abbreviations are extracted and they are compared with the element abbreviations in the 'country_ELEMENTS' 20 table to extract the naming convention element IDs which are corresponding to the active interfaces. Hence, as shown in the flowchart in Figure 4 in box (g), the user can select the active interface from the list of active interfaces and click to view network elements which correspond to those interfaces. A screenshot of this user interface page is available as Figure 3.6.

The user can then click on 'Subnet size for Selected Interface' to populate the subnet mask 25 in the empty boxes for entering subnet address. The selected active interface is compared with the interfaces in the generic/reference table in database called 'SubnetSize' and the corresponding value of subnet mask is extracted and it appears in the empty box for subnet mask in the subnet address as mentioned above. These relationships form the basis of all extraction, insertion and updating of the database. The values of subnet mask are suggestions to the planner and depend 30 on the anticipated size of the network. For an extremely large networklike in China, the number of connections are very large which would mean the subnet mask value would be smaller while in a smaller network site in New Zealand would require a larger value of subnet mask.

Next, with the active interface selected, the right network element selected and the value for subnet mask entered, the user has to populate the octets of the subnet address. The last octet 35 is usually left as 0 but the user can fill whichever value that is required and also the subnet mask which is populated automatically can also be overwritten by the user by simply clicking on the number and writing over it. Then the add subnet button is pressed which provides a message confirming the assignment of the specified subnet address to the specified logical interface. Another table in the database is created/updated run-time as a result, in the form of 5 'country_SubnetList' which is updated with the site name, interface name, values of the four octets and the subnet mask. An example table in the database would be 'NewZealand_Subnet List' which would have a row that reads site name of FT, interface name of Mc, four octets of the values 110, 33, 10, 0 and the subnet mask of 28. This table is shown in Figure 2 table (s).

Next, the user can click on 'Continue with Network IP Planning' to move to the next user 10 interface for assigning of the IP Addresses to the network. It can be seen in the flowchart of Figure 4 in box (g) that the user clicks on 'Subnet Size' to get suggested value of subnet mask for the subnet address followed by entering the octet values of subnet addresses of respective logical interfaces. 7. Purpose of this user interface is to assign IP Addresses in the subnets assigned to network elements in selected interfaces. Active interfaces are shown on the screens which are extracted from the 'country_ActiveInterface' table in the database using a SQL query using a SELECT command where the condition is that the site in the table is same as the specified site in session. When clicked on 'Assigned Subnets', the user can see a datagrid on the application window with 20 the site name, interface name, values of the 4 octets and subnet mask. This information is extracted from the database from the 'country_SubnetList' table, condition being where the site name is the same as the name of network site in session. Similarly, Element IDs of network elements in that site are also extracted from the 'country_ELEMENTS table in the database' where the country is the one that is in session.

Next this system selects the first three octet values from the subnet address that had been stored in the previous user interface in a user_generated run-time table in the database 'country_SubnetList' where the country could be anyone that is in session. Hence, when the user selects the active interface to assign IP Address in and the network element to assign IP Address to, and clicks on to assign subnet address for that interface to that network element, the system 30 suggests valus for the first three octets in the IP Address as they automatically appear in empty boxes for the IP Address. The values of the first three octets and the subnet mask are extracted from the 'country_SubnetList' table in the database (where country is the one in session) where the selected active interface is the listed active interface in the country_SubnetList database.

The user has to enter the value of the last octet, VLAN name and VLAN ID, which are 35 simply identifiers of the network. Once the user presses the submit button, the IP Address in the subnet corresponding to the active interface is assigned to all cards of the selected network element. In this way, IP Addresses can be assigned in another subnet if configured in the same active interface to either the same network element which already has been assigned IP Address in the first subnet or another network element. Hence, the same network element could be 5 assigned IP Addresses in multiple subnets or multiple network elements could be assigned IP Addresses in the same subnet.

The IP Addresses assigned to network elements are automatically, uniquely assigned to all the cards of that network element. The last octet value entered by the user is taken as the value in the IP Address for the first card in the network element. The last octet value in the IP Address 10 for the second card in the selected network element is automatically an incremented value from the last one so that the IP Address is unique. In this way, the last value of the octet in a network element for all the cards is basically just incremented so that the IP Address value is unique.

The IP Address octet values, the subnet mask, VLAN Name, VLAN ID, the name of the site, the name of the selected active interface and element ID of the selected network element the 15 IP Address is being assigned to, are all inputted into a new/existing table in the database which is auto-generated run-time called 'country_InterfaceIPAddress' where the country is the one that is in session.

For instance, in NewZealand_InterfaceIPAddress table in the database (as shown in Figure 2 table (dj) after IP Address assignment might read in the first row: FT for site name in the first 20 column, Mc for Active Interface in the second column, FTHRl for element ID in the third column and octet values of the IP Address in the corresponding subnet in the fourth, fifth, sixth and seventh column like 110, 33, 52, 8. The table would also contain 28 in the eighth column for subnet mask, 'CS_Control Plane' for VLAN name in the ninth column and 190 for VLAN ID in the tenth column. These IP Addresses are automatically assigned to all the cards of selected 25 network elements for selected active interfaces in selected subnets in selected network sites in the selected country. Hence, relationships between these parameters are dynamic and any change results in changes in the corresponding configuration as the appropriate values are extracted from the database.

From the country_InterfaceIPAddress table (where the country is the one in session) in the 30 database, queries are used to count the number of assignments in each network element, in other words the number of cards that unique IP Addresses have been assigned to, and the system hence, outputs a message on the screen after every network element assignment suggesting to the user what value of the last octet the user should fill in for the next assignment in the same subnet so that the IP Addresses are unique. The system also outputs a message notifying the user that IP 35 Addresses have been assigned to specific network elements in specific interface in specific subnet. These steps as an example are shown in the flowchart in Figure 4 box (g). A screenshot of the user interface is provided in figure 3.7. 8. If the user had selected to individually assign IP Addresses to network Elements without 5 the use of subnet and interfaces in the user interface relating to numeral 5 in Figure 1, then the user would be have been prompted to select the network elements to assign the IP Addresses to, as shown in box (i) of flowchart in Figure 4 and subsequently, the user would populate the octets of the IP Address and press submit. These steps are also shown in Figure 4 boxes (j) and (k). The unique IP Addresses would then be assigned to all the cards that had been configured to the 10 specific network element which the IP Address is being assigned to and the values are stored in the database in the 'country_InterfaceIPAddress' table where the country is the one that is in session. A screenshot of the user interface is shown in figure 3.8. 9. This user is directed to the viewing user interface from the first user interface in the system 15 (main menu) which provides the choice to create a new network, view information on existing network or modify an existing network. If the user had selected to view information on an existing network, the process followed is outlined in Figure 5 as it is shown step-by-step.

The user first selects the country in which he/she wants to view the site information in and then selects the sites in that country. The list of countries is extracted from the database to show 20 on the screen and once the country is selected, the sites for that country are obtained from the country's 'country_ELEMENTS' table in the database where the country is the one that is selected by the user. The system also generates a message notifying the user of the number of network sites in that country. Hence, when the network site is also selected, a bunch of options are presented to the user. As shown in box (c) in Figure 5, one of the choices for the user is to 25 view all configured network elements in the site and their auto-generated naming convention. Also, as shown in box (d) in Figure 5, the user can view all Subnet Addresses configured to the network site that is selected. This is done by extracting information from auto-generated tables in the database which are specific for the countries, for instance, NewZealand_SubnetList. This information can also be sent to Excel for viewing. A screenshot of the user interface is provided 30 in Figure 3.9.

. The user can also click to view cards of configured network elements in a site for which he/she is directed to another user interface. The user has to select the country and site and then the network elements which are configured to that specific site become visible as they are extracted from the database. By selecting the element IDs of the configured network elements, all cards that are configured to those network elements are shown on the application. These are extracted from the generic table of cards called the 'nwcards' table in the database. This information can also be printed to applications like Microsoft Excel. A screenshot of the user interface is provided as figure 3.10. 11. The user can view IP Address information on this user interface. The system queries the database with SELECT SQL command to extract all information from the country InterfacelPAddress table in the database which contains all the IP Address assignment ✓ — o information. This is all displayed on the screen for a particular country and it can be printed on 10 Excel as well. A screenshot of the user interface is provided in figure 3.11. 12. This user interface is the main interface for modification to existing network sites and their information and configuration. As shown in Figure 6, boxes (a), (b), (c), (d), (e), (f), (g) and (h), the user can select to add new network elements to the database, modify the status of cards of network elements, add new cards to network elements in the database, modify the quantity of network elements, change delete and add subnets in the site and finally modify IP Address information configured to a network site. A screenshot of this user interface in provided in Figure 3.12. 13. If the user clicks to be directed to add new network elements in the database, the user is prompted to enter the name of the new element, name of the vendor of the element and element abbreviation. If the element or abbreviation already exists in the generic table of elements, the user is appropriately notified, otherwise the information is stored in the generic table in the database, and the user is notified. The generic table in the database where network elements are 25 kept is shown in Figure 2 table (b) called 'nmlements'. A screenshot of the user interface is provided in Figure 3.13. 14. If the user clicks to be directed to remove existing network elements, the existing network elements are first displayed from the generic table in the database that stores all the elements. The 30 user can then select which element he/she wants to delete and the entire row in the table of that element including its vendor and abbreviation is deleted. This action is dynamic, so if the user decides to go to creation of network site and all the network elements are extracted from the database, the most updated version of network elements would be extracted so that the Network IP Planning can be run-time and most efficiendy done. A screenshot of the user interface is 35 provided in figure 3.14.

. If the user selects to add a new card to an existing element at a site, the user is taken to this interface page where the user selects the name of the network element from a display from the table of the database, and selects its abbreviation and then enters the name of a new card that needs to be added. If the card already exists, the user is notified, otherwise, the operation is performed. There is another option where the user might want to add multiple cards to the element, whereby the user enter the names of cars and a stored procedure is called which enters the information to the generic card table in the database. One of the features that is being worked on is that the card, element and other information can be direcdy fed another system like a Nokia 10 backbone system. A screenshot of the interface is provided in figure 3.15. 16. If the user selects the option to change the status of cards at a site, the user is directed to this interface and the operation performed is identical to the one in interface referred by the numeral 4 of figure 1. A screenshot of the interface is provided in figure 3.16. 17. If the user selects the option of changing the quantity of network elements in a network site, the user is directed to this interface and the operation performed is identical to the one in interface referred by the numeral 3 of Figure 1. A screenshot of the interface is provided in figure 3.17. 18. If the user is to add, delete or change the subnet values, he/she is directed to this interface where the operation is identical to the one described in interface referred by the numeral 6 of figure 1. The user is then directed to the interface referred to by numeral 7 in Figure 1. A screenshot of the interface is provided in figure 3.18. 19. If the user is to modify IP Address values, he/she is directed to this interface where the operation is identical to the one described in interface referred by the numeral 8 of figure 1. A screenshot of the interface is provided in figure 3.19.

Overview of Restoration of Database A brief description of database restoration will be described with reference to the screen shots in Figures 23 to 25. The process enables the software to be used. i) After creating your new SQL Server Registration on MS SQL Server 2000. ii) Go to the Action sub-menu in the File menu and select the "New database" menu item. iii) Enter a database name and press OK. This name will refer to the database in which you will restore NIPP's original database, with all the generic and other data. iv) Now right click on the database icon that is created with the name you just entered. Select "all tasks" and then "Restore database". The window in Figure 23 appears. v) In the options tab, select the checkbox "force restore over existing database". vi) Return to 7the general tab and select the "From device" radio button instead of the currently selected "Database" option. vii) Leaving the default options, press the "Select Devices" button. This will bring up the window in Figure 24. viii) Here press the "Add" button, and the window in Figure 25 pops up. iv) Here, under the filename radio button, select the NIPPSystemDb.bak file provided, and press OK. 22 APPENDIX A Intellactuat Property Office of N.Z. 23 HAY 2008 RECEIVED 23 9/07/05 Idea of connection of software with MML terminal: software to software interaction - integration - called 'business-to-business transaction' issues since nothing manual control over software 4 be able to stop software 4 therefore, issue of constant data backup -> change in conceptual issues and considerations This software has functionalities: 1) Using generic tables, user able to configure a telecommunications network for every network site in any city in any country. 2) The network that the user (IP Planner) has configured using the software covers every detail. 3) The details covered are country, city, network site, network elements, cards of network elements, all interfaces, IP Address ranges for each interface, IP Address for each network link (i.e. IP addresses for cards). 4) Configuration of network can be updated at any time by modifying the existing configuration.

) Modifications include adding/deleting network elements, adding/deleting network sites, adding/deleting cards in various network elements, creation/removal of interfaces, changes in types of elements that form an interface, change in rules that define assigning of IP Address ranges to interfaces, complete change in assigning rules by change from IPv4 to IPv6, change in IP addresses assigned to individual links (i.e. cards) as fixed values given for different network sites/cities/countries. 6) Being able to view any information of the network required by the user. 7) Specific information provided to the customer. 8) Security of the software. 9) Web-logon, usability and access to particular users.

) Documentation, manuals and training provided by developers. 11) User can change configuration of a particular network site or user can change configuration of network products i.e. changing generic tables. 12) Administrator adds various changes in network (e.g. an extra card) in the generic table, user can change (location based) the network configuration but cannot add something which is not in generic table already. Therefore, modification of configuration of network can be done on a location basis as well as worldwide generic tables can be changed by administrator. 13) Access control developed with worldwide administrator having highest priority (access to generic tables), country administrators and users with lowesjjauihaqty. t 5 JUL 2008 24 Commercialization advantages: 1) The telecommunications company can charge customers more for service as desired information provided to the customer from software, access to which can be granted of varying degree to customers. 2) Telecommunications Company can charge licensing fee to other companies that want to use this software to automate their IP Planning functions. 3) Elimination of the need of staff in IP Planning working in an administrative capacity. 4) Future-proof ) Competitive edge over other telecommunications companies. 6) Faster roll-out of changes in networks as planning time reduced due to efficient system. 7) Innovation goodwill in the telecommunications community. 8) Financial advantages as scope of technologies of future change (flexibility - quick adaptation, on-demand business) 9) Easy adaptation of software to changes in network.

Boxing & Unboxing int i = 123; object o = i; int j = (int) o; Improvements to design 1) For prior to confirm pages (pages 2, 4, 6) -have another page that shows a warning whether sure to cancel, yes or no -if yes, continue as indicated -if no, leave back at the user entry page -no change in database 2) For IP Assign.ASPX (page 6) and Confirm_IP.ASPX (page 7) - add another column saying 'Start Octet 4 with' 3) In table (g), flip around the columns and rows The file 'ITSjips.datl' on Win 2000 Pro CD is needed. PROBLEM IN INSTALLING 'ITS'.

Actions Taken: 1) ITS_tip.dat 1 found in a compressed file on Win 2K Pro CD 2) New VisualStudio.NET 2003 Prerequisites CD created. 3) All services apart from MS services stopped before installation. 4) Prerequisites including .NET framework installed ) Then installation with CD1 & CD2 ofVS.NET 2003 STEP1: Prerequisites STEP2: VisualStudio.NET 26 APPENDIX B 27 1.0 INTRODUCTION This project involves research and development of a software package for Vodafone's 3rd generation (3G) cellular network. The project is sponsored by Nokia New Zealand and will be used for IP (Internet Protocol) network planning. Nokia conducts the planning and implementation of cellular networks that are operated by Vodafone in New Zealand. Currently, IP planning of cellular networks is conducted manually. This software package would be designed to automate the abovementioned planning function. This project will be divided into two phases: research and implementation. Research phase involves understanding cellular network design and communication. Implementation phase delves into application and development of the software package using Oracle database and SQL language. Prior to the implementation phase, this report also discusses the required specifications for the development of software. 2.0 SCOPE OF PROJECT Vodafone has an existing cellular network called 2nd Generation (2G) Network. With the advent of 3G network, new network elements, links and multiple cellular base sites are added to the existing network. Scope of this package in terms of functionality is that it will be able to plan the communication framework1 for these changes in the network.

A timeline is also decided for the completion of this project which entails the research phase being done by end of April, 2005. Implementation phase, which involves understanding and application of the development tools, will be instigated from May to July. It is proposed that an alpha version of the software package will be delivered by 15th August. If time permits, functions of the package will be further optimised to produce the final version. As planned, we are in the process of development of the package. 3.0 RESEARCH CONDUCTED 3.1 Background to Cellular Network Prior to delving into the development of our package, we need to firstly, understand basics of a cellular network.

Cellular Networks have evolved in the recent years from GSM2 technology to the latest 3G technology, inherently differing in data/voice transmission capacity. GSM cellular technology 1 Communication between elements in a cellular network 2 Global System for Mobiles 28 comprises of a network formed by 3 subsystems: NMS3, BSS4 and NSS5. The basic GSM cellular network is illustrated in the following diagram: Base station system (BSS) is an entity responsible for communicating with mobile phones in a certain area. A BSS may consist of one or more base stations (BS). BSS interfaces with Mobile Switching Subsystem (MSS) that performs the switching functions in its area of operation and maintains a database of all subscribers in the covered area. Network management system (NMS) controls and monitors the resources of a network. It records their use and performance in order to provide telecommunication services. For further details regarding functionality of all network elements, please refer to Appendix—.

Our project concentrates on the latest cellular network technology, 3G. 3G is based entirely on the GSM network topology with appendage of network elements as shown in the following illustration: 3 GPRS provides connectivity to various types of data networks 4 Combination of exchanges and the basic transmission equipment which together form the basis for network services Network Management System 29 3G network differs from the existing GSM network mainly in terms of more services provided and a higher data transmission rate. 3.2 Communication fundamentals 3G mobile network consists of various interfaces between network elements. These interfaces constitute the communication framework in the network. Various protocols are also used for communication via the interfaces. These concepts form the underlying basis of development of the software package.

IP is the basic communication protocol used to transmit data over networks, on private as well as public networks, also in the case of 3G cellular network. Communication over IP involves transfer of information in the form of packets. These packets contain addresses of the source network element and also the destination element. These IP addreses are assigned to all network links for communication.

Automation that the software package will be designed to perform, would also include assigning IP addresses to various network links.

More details of IP addressing attributes are given in Appendix —. 3.3 Nokia IP Architecture Nokia requires a deliverable, which is capable of performing functions related to the IP architecture of 3G network. IP architecture includes planning, structuring, and assigning IP communication framework. The software package, in detail, requires incorporation of Nokia's existing IP architecture. Therefore, extensive research of the IP framework is imperative for development of the software package.

Nokia's current IP architecture is illustrated in the following diagram. The purpose of the diagram is to show how four different types of interfaces (Gi, Gn, Ga, O&M) connect the network element (SGSN) on the left hand side to network elements on the right hand side. These interfaces also connect network elements on the right hand side to each other. The connections via these interfaces are implemented using IP communication. It can also be seen that redundancy has been considered, as there are more than one communication paths from SGSN to various network elements. 4.0 NETWORK SPECIFICATIONS FOR DEVELOPMENT OF SOFTWARE 4.1 Network capacity requirements / constraints New Zealand cellular network coverage is based from 4 different sites. These sites are Lambie Drive and France Steet in Auckland, one in Wellington city and one in Christchurch city. However, this software package is required to be able to accommodate 200 sites in a particular network.

Another requirement is that this software should be able to expand the cellular network in the case of increasing number of multiple network elements of the same type in each site. For example, being able to accommodate 10 base stations in a certain area that only has 2 existing base stations.

When this software builds the network communication framework, it is also required to consider the factor of redundancy. In another words, there should be more than one network link paths, especially to and from key elements in the network.

In a particular network, elements have specific configuration which corresponds to the current capacity requirements. The configuration can either be upgraded or degraded as the number of subscribers and their mobile usage changes. This package is required to be able to upgrade the framework accordingly. 31 4.2 Specifications of IP address assigning IP addressing in the network is based around four IP address blocks. The first 3 are from private address space and the last is public registered address space. This concept is vital in the functionality of the software as the package will be able to assign IP addresses in the network according to the requirement of which network link should be visible from the outside world (public) and which should not be visible (private). .0 SOFTWARE IMPLEMENTATION PROPOSED .1 Decision to use Oracle & SQL There are 3 development objectives in software development: databases, coding to manipulate data in the databases and the user interface.

In order for the software tool to have access to all the information of every network element in the 3G network, for instance, its configuration, number of multiple elements of the same type, its connectivity etc, we need to develop databases. Oracle is chosen as the tool to develop the databases required by our software and SQL is the programming language that will be used to instruct and manipulate data in the databases.

Oracle is chosen over other database development tools for various reasons. Firstly, it is known that Nokia's network can support Oracle databases, as other applications using Oracle databases exist on the network. Secondly, Oracle databases are relational databases, which are preferred over the other type of databases, heirarchical databases. Relational databases are where the end user does not need to know how the data is extracted. This type of database is appropriate for our software package. For information on components of a relational database and an example illustrating the concept, please refer to Appendix —.

SQL, the programming language used for instructing the Oracle databases is an easy language to use, as it is very database-functions-specific and has a very few, limited commands that are precise and easy to use. A list of SQL commands is given in Appendix—. .2 Development of Top Level User Interface 32 The 3rd objective of the implementation phase is development of the top level user interface. The user of this package, who is an IP Planner, will enter information based on certain questions that the software package will ask. According to the input, the software should be able to search, manipulate and perform other functions on the data in the databases appropriately. This interface with the user would be in the form of dialog boxes, and is decided to be built using the programming language C#.NET on Visual Studio.NET platform. This language is chosen because of the ease of development, as it involves clicking and dragging of objects. 6.0 PROJECT MANAGEMENT 6.1 Resources used Nokia provides the following resources to assist us through our project: • IBM Thinkpad T30 Laptop • Nokia Intranet access • Oracle software • Visual Studio.NET (In progress) • Security access to Nokia facilities in Auckland 6.2 Timeline & Planning The final goal of this project is to deliver to the customer, in our case Vodafone as a customer of Nokia, an effective IP planning software. In order to achieve the goal, it is required us to have clear understanding of the Nokia specific 3G network and the ability to develop a software package as the end product. Therefore this project is divided into two phases: research and implementation. The duration of the project is specified as approximately 29 weeks by the part IV project committee. A timeline of the project has been made at an early stage by academia of the committee.

We have decided that the research phase is to be completed within 1/3 of the specified duration, which is approximately 9 weeks. The research phase can be further divided into two sections: general communication background and Nokia specific cellular architecture. By consulting the IP planning personnel in Nokia, former is allocated to extend for a duration of 2 weeks; latter is allocated to extend for a duration of 7 weeks. Interim Report preparation and documentation is planned to be done between 18th April and 8th May. Implementation phase will be carried out during the next 14 weeks by 15th August. During the 3 weeks from 5th August to 26th August, we will prepare the final report documentation.

From 19th August to 2th September, conference and exhibition preparation is planned to be done. The rest of the two weeks will be allocated to preparation of the project exhibition. Appendix — illustrates the detailed time management and planning of the project, as well as current progress in the form of Ghant chart. 6.3 Progress As planned, the basic research objectives of the project have been achieved. This includes understanding of cellular network, communication fundamentals and Nokia 3G IP architecture. We have moved on to the implementation phase and are currently learning Oracle database creation techniques. 6.4 Difficulties During the research phase, one of the difficulties we faced was complexity of the IP fundamental theory. There is a vast array of information that is available on the areas of our interest. It is our task to identify relevant information to the project at each stage.

Regarding the implementation phase, the main difficulty we can foresee is the limitation of time that is rendered for being able to learn and apply 2 different software development packages, Oracle/SQL and Visual Studio.NET. 7.0 CONCLUSIONS This project aims to deliver a software package as an end product for Nokia New Zealand. Purpose of the software package mainly includes automating IP (Internet Protocol) address assigning and updating cellular network IP framework. It also interfaces with the user in order to obtain inputs, which are used for modifications of IP architecture, and outputs information in a manner that is required by the customer. As an academic exercise, project objectives are carefully evaluated and milestones planned in order to meet the requirements and deadlines. It has been decided that this project should be divided into phases of research and implementation. First 9 weeks of the duration is allocated to the research phase and next 14 weeks to implementation phase. Subsequently, conduction of a seminar, exhibition of our results and documentation of the final report will last until 16th September. Regarding division of work, research is purposely done jointly, while during software implementation, we plan to undertake parts of development separately. This software package will be designed with New Zealand cellular network as a model but would also be able to apply in other networks as long as the capacity requirement does not exceed specifications. 34 BSS - Base Station Subsystem The Base Station Subsystem consists of the following elements: • Base Station Controller (BSC) • Base Transceiver Station (BTS) • Transcoder The Base Station Controller (BSC) is the central network element of the BSS and it controls the radio network. This means that the main responsibilities of the BSC are: Connection establishment between the MS and the NSS, mobility management, statistical raw data collection as well as interface signalling support.

The Base Transceiver Station (BTS) is a network element maintaining the Air interface. It takes care of Air interface signalling, Air interface ciphering and speech processing. In this context, speech processing refers to all the functions the BTS performs in order to guarantee an error free connection between the MS and the BTS.

The Transcoder (TC) is a BSS element taking care of speech transcoding, that is, it is capable of converting speech from one digital coding format to another and vice versa.

Network Switching Subsystem (NSS) The elements of NSS that have been discussed are: • MSC (Mobile Services Switching Centre) • VLR (Visitor Location Register) • HLR (Home Location Register) The MSC is responsible for controlling calls in the mobile network. It identifies the origin and destination of a call, as well as the type of a call. An MSC acting as a bridge between a mobile network and a fixed network is called a Gateway MSC.

An MSC is normally integrated with a VLR, which maintains information related to the subscribers who are currently in the service area of the MSC. A unique number called the MSRN number is assigned to locate a specific subscriber's information.

A VLR database is always temporary, whereas the HLR maintains a permanent register of the subscribers. In addition to the fixed data, the HLR also maintains a temporary database which contains the current location of its customers. This data is required for routing calls.

Network Management Subsystem The Network Management Subsystem (NMS) is the third subsystem of the GSM network in addition to the NSS and BSS. The purpose of the NMS is to monitor various functions and elements of the network. These tasks are carried out by the NMS/2000 which consists of a number of workstations, servers and a router, which connects to a Data Communication Network (DCN).

The functions of the NMS can be divided into three categories: • Fault Management • Configuration Management • Performance Management These functions cover the whole of the GSM network elements from the level of individual BTSs, up to MSCs and HLRs. 36 APPENDIX C 37 SQL (Structural Query Language) Commands SELECT retrieve information from tables UPDATE make changes to existing data in tables, indexes INSERT adds data to tables, indexes DELETE removes data from tables, indexes CREATE used to create almost any object ALTER makes changes to definition of objects and/or database settings DROP removes object from database COMMIT saves current pending changes to database ROLLBACK removes any uncommitted changes GRANT -i privilege maintenance of objects REVOKE J TRUNCATE quickly removes all data from a table RENAME objects to be renamed AUDIT track who is doing what to the database EXPLAIN PLAN view choices Oracle optimiser is making for any SQL statement ANALYZE collect statistics for Oracle cost based optimiser SET TRANSACTION used to identify a unit of work ROLES grouping user privileges 38 CREATING NEW N/W CONFIG index.aspx 1. "select country from countries order by country" 2. "select Site from country_site where Cntry = '"+country+"1" 3. "insert into country_site(site) values ('"+site+"') " +"update country_site set cntry = 1" +DropDownListl.Selectedltem +'" where site = '"+site+"'" EnterQuanti ty.aspx 1. select ELEMENTS, ele_ab from nwelements 2. INSERT into elementquantity VALUES" + " ('"+(string)Session["site"],'"+currentElement + "1,"tcurQuan tity+")"; 3. "select * from "+ tableName 4. create table "+tableName+" (SitelD varchar(50), " + "Element_abb varchar(50), Element_id varchar(50))"; . "Insert into "+country+"_ELEMENTS Values" + " (1" + site+"', '"+currentElementAbb+"'," +"'"+ site+currentElementAbb+i+"')"; addCards.aspx 1. "select Element_id from "+country+"_ELEMENTS where sitelD = 1 " + site+"'"; 2. "select Element_abb from "+country+"_ELEMENTS where Element_id = ' "+selectedElement+"' and sitelD = '"+site+"'"; 3. "select cards from nwcards where abb = '"+currentElement_abb+"' order by cards"; 4. "Insert into "+country+"_CARDS Values" + "(' "+site+"', '"+selectedElement + "'," +"1"+selectedCard+"')"; . "select * from "+ tableName 6. "create table "+tableName+" (SitelD varchar(50), " + "Element_ID varchar(50), ActiveCards varchar(50))" ActiveInterface.aspx 1. "select distinct Element_abb from "+country+"_ELEMENTS " + "where SitelD = '" + site + " ' " ; 2. "select distinct ElementAb from nwinterfaces" 3. "select Interface from nwinterfaces " +"where ElementAb = '"+Current_Element+"' 4. "Insert into "+country+"_ActiveInterface Values" + " ('"+site+"', '"+Currentlnterface+"1)"; . "select * from "+ tableName 6. "create table "+tableName+" (SitelD varchar(50), " + "Actlnterface varchar(50))"; 7. "select distinct Actlnterface from "+country+"_ActiveInterface where SitelD = '"+site+"' 8. "select distinct ElementAb from nwinterfaces where Interface = '"+ListBoxl.Selectedltem.ToString()+"'"; 39 9. "select distinct Element_abb from "+country+"_ELEMENTS where sitelD = '"+site+"' . "select distinct Element_id from "+country+"_ELEMENTS " +"where Element_abb = '"+Current_abb+"1 and SitelD = '"+site+"'"; 11. "select Subnet_Size_Mask from SubnetSize where Interface = '"+ListBoxl.Selectedltem.ToString{)+"'"; 12. "select distinct LastOctetSubnet from Subnet_Last_Octet"; 13. "Insert into "+country+"_SubnetList Values" + " (1" + site+"',1"+selectedlnterface+"1," +""+Octetl+", "+Octet2+", "+Octet3+", "+Octet4+"," +""+SubnetMask+") setupCountrySubnetlPTable(String tableName) 14. "select * from "+ tableName; . "create table "+tableName+" (SitelD varchar(50), " +"Interface varchar(50), Octetl numeric{10)," +"Octet2 numeric(10), Octet3 numeric (10), Octet4 numeric (10) "+ "SubnetMask numeric (10))"; InterfacelPAssign.aspx 1. "select distinct Actlnterface from "+country+"_ActiveInterface where SitelD = "'+site+'" "; 2. "select * from "+country+"_SubnetList where SitelD = 1 " + site+"'"; 3. "select distinct Element_id from "+country+"_ELEMENTS where sitelD = '"+site+"'"; showOctets () 4. "select Octetl from "+country+"_SubnetList where SitelD = ' " + site+"' and Interface = ' "+ListBox2.Selectedltem.ToString()+"'"; . "select Octet2 from "+country+"_SubnetList where SitelD = ' " + site+"' and Interface = ' "+ListBox2.Selectedltem.ToString()+"'"; 6. "select Octet3 from "+country+"_SubnetList where SitelD = ' "+site + "' and Interface = ' "+ListBox2.Selectedltem.ToString()+"'"; 7. "select SubnetMask from "+country+"_SubneLLisL where SitelD -'"+site+"' and Interface = '"+ListBox2.Selectedltem.ToString()+"'"; showOctetsForNextSubnet() 8. "select Octetl from "+country+"_SubnetList where SitelD = '"+site+"' and Interface = ' "+ListBox2.Selectedltem.ToString()+"'"; 9. "select Octet2 from "+country+"_SubnetList where SitelD = ' "+site+"' and Interface = ' "+ListBox2.Selectedltem.ToString()+"'"; . "select Octet3 from "+country+"_SubnetList where SitelD 1 "+site+"' and Interface = ' "+ListBox2.Selectedltem.ToString()+"'"; 11. "select SubnetMask from "+country+"_SubnetList where SitelD = '"+site+"' and Interface = ' "+ListBox2.Selectedltem.ToString()+"'"; addlnterfacelPAddToTable () 12. "select distinct Element_abb from "+country+"__ELEMENTS " 40 +"where SitelD = '"+site+"' and Element_id = '"+selectedElementID+"'"; 13. "select cards from nwcards " +"where cards like ' %0' and abb = 1"+currentab+"'"; 14. "Insert into "+country+"_InterfaceIPAddress Values" + " {' "+site+"', 1"+selectedlnterface+"', 1" + selectedElementID+"', "+CardPointer+"',"+""+Octetl+", "+Octet2+", "+Octet3+", "+Octet4+", " + ""+SubnetMask+'"+VLANname+"', "+VLANid+")"; addlnterface IPAddToTableForNextSubnet () . "s-elect distinct Element_abb from "+country+"_ELEMENTS " +"where SitelD = '"+site+"' and Element_id = ' "+selectedElementID+"'"; 16. "select cards from nwcards " +"where cards like '%1' and abb = '"+currentab+"1"; 17. "Insert into "+country+"_InterfaceIPAddress Values" + " (1 " + site+"', '" + selectedlnterface+"', '" + selectedElementID+"', "+CardPointer+"1,"+""+Octetl+", "+Octet2+", "+Octet3+", "+Octet4+","+""+SubnetMask+", '"+VLANname+"', "+VLANid+") setupCountrylnterfacelPAddressTable(String tableName) 18. "select * from "+ tableName; 19. "create table "+tableName+" (SitelD varchar(50), Interface varchar(50), "+ "Element_ID varchar(50), Cards varchar(50), Octetl numeric(10),"+ "Octet2 numeric(lO), Octet3 numeric (10), Octet4 numeric (10), "+ "SubnetMask numeric (10), VLANname varchar(50), VLANID numeric(10))"; MODIFYING A NETWORK Modifyl.l.aspx - Adding Network Elements addNewElement () 1. "insert into nwelements values ('"+TextBoxl.Text + "', 1 "+TextBox2.Text+"', '"+TextBox3.Text+"')"; 2. "insert into NewAddedElements values ('"+TextBoxl.Text+"', ' "+TextBox2.Text+"', '"+TextBox3.Text+"1)"; Button2__Click () - submit new network element to database 3. "select ELEMENTS from nwelements" 4. "select ele ab from nwelements" Modifyl.2.aspx - Removal of Network Elements UstElementsForView () 1. "select ELEMENTS from nwelements" 41 removeElement () 2. "delete from nwelements where ELEMENTS = '"+DropDownListl.Selectedltem+"'"; 3. "insert into deletedElements values ('"+DropDownListl.Selectedltem+"') " ; Modifyl.3.aspx - Change Quantity of an existing Network element at a site UstCountriesForView () 1. "select country from countries order by country" showSites () 2. "select Site from country_site where cntry = '"+DropDownListl.Selectedltem+"'"; listelements () 3. "select ELEMENTS, ele_ab from nwelements" addquantity () 4. "delete from "+DropDownListl.Selectedltem+"_ELEMENTS where SitelD = '"+DropDownList2.Selectedltem+"' . "INSERT into elementquantity VALUES('"+DropDownList2.Selectedltem+"','"+currentElement+"',"+ curQuantity+")"; setupCountryElementTable(String tableName) 6. "select * from "+ tableName 7. "create table "+tableName+" (SitelD varchar(50), Element_abb varchar(50), Element_id varchar(50))"; createElementsInCountry () 8. "Insert into "+DropDownListl.Selectedltem+"_ELEMENTS Values(1"+DropDownList2.Selectedltem+"','"+currentElementAbb+"' ,'"+ DropDownList2.SelectedItem+currentElementAbb+i+"')"; Modifyl.4.aspx - Add a new card to an Existing element at a site UstElementsForView () 1. "select ELEMENTS from nwelements" UstAbbForView () 2. "select ele_ab from nwelements" addCardO 3. "insert into nwcards values ('"+DropDownListl.Selectedltem+"', '"+DropDownList2.Selectedltem+"', '"+TextBox3.Text+"1)"; 42 modifvCards.aspx - Change the status of a Card of an existing element at a network site UstCountriesForView () 1. "select country from countries order by country" showSites () 2. "select Site from country_site where cntry = 1 "+DropDownListl.Selectedltem+"'"; showElementlnstances() 3. "select Element_id from "+country+"_ELEMENTS where sitelD = ' "+site+"' showGenericCards () 4. "select Element_abb from "+country+"_ELEMENTS where Element_id = '"+selectedElement+"' and sitelD = '"+site+"'"; . "select cards from nwcards where abb = '"+currentElement_abb+"' order by cards"; showCards () 6. "select ActiveCards from "+country+"_CARDS " + "where sitelD = '"+site+"'and Element_ID ="+ "1"+ListBoxl.Selectedltem.ToString setupCountryActiveCardsTable() 7. "select * from "+ tableName 8. "create table "+tableName+" (SitelD varchar(50), " + "Element_ID varchar(50), ActiveCards varchar(50))" addToTable () 9. "Insert into "+country+" _CARDSValues" + "('"+site+"', ' "+selectedElement+"','"+selectedCard+"')" . "select ActiveCards from "+country+"_CARDS where sitelD = 1 "+site+"'and "+ "Element_ID = '"+ListBoxl.Selectedltem.ToString()+"'" deleteCard () 11."delete from "+country+"_CARDS where ActiveCards ="+ "1"+selectedCardtoDelete+"' and Element_ID = 1"+selectedElement+"' and SitelD = '"+site+"'" 12. "select ActiveCards from "+country+"_CARDS " + "where sitelD = '"+site+"'and "+ "Element_ID = '"+ListBoxl.Selectedltem.ToString()+"1" ModifylnterfacelPAssign.aspx - IP Address assignment of Network Elements UstCountriesForView () 1. "select country from countries order by country" 43 showSites () 2. "select Site from country_site where cntry = '"+DropDownListl.Selectedltem.ToString()+"'" viewActivelnterfaces () 3. "select distinct Actlnterface from "+country+"_ActiveInterface where SitelD = '"+site+"' " viewSubnets() 4. "select * from "+country+"_SubnetList where SitelD = ' "+site+"'"; listElementID () . "select distinct Element_id from "+country+"_ELEMENTS where sitelD = 1 "+site+" showOctets () 6. "select Octetl from "+country+"_SubnetList where SitelD = '"+site+"' and Interface = ' "+ListBox2.Selectedltem.ToString()+"'"; 7. "select 0ctet2 from "+country+"_SubnetList where SitelD = '"+site+"' and Interface = '"+ListBox2.Selectedltem.ToString 8. "select 0ctet3 from "+country+"_SubnetList where SitelD = '"+site+"' and Interface = ' "+ListBox2.Selectedltem.ToString()+"' 9. "select SubnetMask from "+country+"_SubnetList where SitelD = '"+site+"' and Interface = '"+ListBox2 . Selectedltem.ToString()+"1"; showOctetsForNextSubnet () ."select Octetl from "+country+"_SubnetList where SitelD = '"+site+"' and Interface = '"+ListBox2.Selectedltem.ToString 11."select Octet2 from "+country+"__SubnetList where SitelD = ' "+site+"' and Interface = ' "+ListBox2.Selectedltem.ToString 12."select Octet3 from "+country+"_SubnetList where SitelD = ' "+site+"' and Interface = ' "+ListBox2.Selectedltem.ToString 13."select SubnetMask from "+country+"_SubnetList where SitelD = '"+site+"' and Interface = '"+ListBox2.Selectedltem.ToString addlnterfacelPAddToTable() 14."select distinct Element_abb from "+country+"_ELEMENTS " +"where SitelD = '"+site+"' and Element_id = '"+selectedElementID+"' ."select cards from nwcards where cards like * %0' and abb = '"+currentab+"' 16."Insert into "+country+"_InterfaceIPAddress Values"+ " (' "+site+"', '" + selectedlnterface+"','" + selectedElementID+"1, ' +CardPointer+"', "+Octetl + ", "+Octet2 + ", "+Octet3 + ", "+Octet4 + " "+SubnetMask+", '"+VLANname+"', "+VLANid+") 44 addlnterfacelPAddToTableForNextSubnet () 17."select distinct Element__abb from "+country+"_ELEMENTS " +"where SitelD = '"+site+"' and Element_id = '"+selectedElementID+"'"; 18."select cards from nwcards where cards like 1 %1' and abb = '"+currentab+"'"; 19."Insert into "+country+"_InterfacelPAddress Values"+ "('"+site+"', 1"+selectedlnterface+"','"+selectedElementID+"','" +CardPointer+"', "+Octetl+", "+0ctet2+", "+0ctet3+", "+0ctet4 + ", " + SubnetMask+", '"+VLANname+"', "+VLANid+")"; setupCountrylnterfacelPAddressTable() ."select * from "+ tableName; 21."create table "+tableName+" (SitelD varchar(50), Interface varchar(50), Element_ID varchar(50), Cards varchar(50), Octetl numeric(10),Octet2 numeric(lO), Octet3 numeric (10), Octet4 numeric (10), SubnetMask numeric (10), VLANname varchar(50), VLANID numeric(10))"; modifySubnet.aspx - Changing, Deleting and Adding of Subnets UstCountriesForView () 1. "select country from countries order by country"; showSites() 2. "select Site from country_site where cntry = '"+DropDownListl.Selectedltem.ToString()+"'"; viewActivelnterfaces () 3. "select distinct Actlnterface from "+country+"_ActiveInterface where SitelD = '"+site+"' "; viewSubnets () 4. "select * from "+country+"_SubnetList where SitelD = ' "+site+"' viewThirdOctet () . "select distinct Octet3 from "+country+"_SubnetList where SitelD = '"+site+"' and Interface = '"+ListBox2.Selectedltem.ToString()+"'"; replaceThirdOctet () 6. "update "+country+"_SubnetList set Octet3 = "+third+" where Octet3 = '"+DropDownList3.Selectedltem.ToString()+"' and SitelD = ' " + site+"'"; 7. "update "+country+"_InterfacelPAddress set Octet3 = "+third+" where Octet3 = '"+DropDownList3.Selectedltem.ToString()+"' and SitelD = '"+site+"' and Interface = '"+ListBox2.Selectedltem.ToString()+"'"; 45 removeSubnet () 8. "delete from "+country+"_SubnetList where Octetl = '"+first+"1 and 0ctet2 = '"+second+"' and 0ctet3 = '"+third+"' 9. "delete from "+country+"_InterfaceIPAddress where Octetl = '"+first+"' and 0ctet2 = '"+second+"' and 0ctet3 = '"+third+"'"; getsize () . "select Subnet_Size_Mask from SubnetSize where Interface = 1 "+ListBox2 . Selectedltem. ToString getLastOctetTransfer() 11."select distinct LastOctetSubnet from Subnet_Last_Octet"; addSubnetlPtoTable () 12."Insert into "+country+"_SubnetList Values" + " ('"+site+" ', '"+selectedlnterface+"'," +""+Octetl+", "+0ctet2+", "+Octet3+", "+Octet4+"," +""+SubnetMask+")"; setupCountrySubnetlPTable() 13."select * from "+ tableName 14."create table "+tableName+" (SitelD varchar(50), " + "Interface varchar(50), Octetl numeric(10)," + "Octet2 numeric(10), Octet3 numeric (10), Octet4 numeric + "(10), SubnetMask numeric (10))"; Viewing Viewl.aspx - Viewing information of existing network sites UstCountriesForView () 1. "select country from countries order by country" showSites () 2. "select Site from country_site where cntry = '"+DropDownListl.Selectedltem+"'"; viewElementID () 3. "select SitelD, Element_abb, Element_id from "+DropDownListl.Selectedltem+"_ELEMENTS where SitelD = '"+DropDownList2.Selectedltem+"'" ; viewSubnet() 4. "select * from "+country+"_SubnetList where SitelD = 1"+site+"'"; 46 ViewIP.aspx - Viewing IP Address information of existing network sites UstCountriesForView () 1. "select country from countries order by country"; showSites () 2. "select Site from country_site where cntry = '"+DropDownListl.Selectedltem+"'"; ViewIPInfo () 3. "select * from "+country+"_InterfacelPAddress " +" where SitelD = '"+site+"1 order by VLANID"; viewAHCards.aspx - Viewing Cards of Network Elements UstCountriesForView () 1. "select country from countries order by country"; showSites () 2. "select Site from country_site where cntry = 1"+DropDownListl.Selectedltem+"'"; showElementlnstances() 3. "select Element_id from "+country+"__ELEMENTS where sitelD = 1 " + site+"'"; showGenericCards () 4. "select Element_abb from "+country+"_ELEMENTS where Element = '"+selectedElement+"' and sitelD = '"+site+"'"; . "select cards from nwcards where abb = '"+currentElement_abb+"' order by cards"; 47 APPENDIX D 48 IP Addressing An IP Address uniquely identifies the (host) connection. It is independent of underlying network technology addressing. The Address allows a route to be determined to the intended system(s).

IP addresses are allocates to any network connection rather than the actual host. A host may have multiple connections, and in some cases an interface may have more than one address.

IP Packet Header The IP datagram packet header contains the following fields: VERS HLEN SERVICE TYPE TOTAL LENGTH IDENT FLAGS FRAG OFFSET TIME TO LIVE PROTOCOL CHECKSUM SRC IP ADDRESS DEST IP ADDRESS OPTIONS PADDING protocol version (currently 4) length of header in 32 bit words (normally 5) sets a precedence and Type of Service for the packet length of IP datagram in octets unique integer for each datagram controls fragmentation (DF-don't fragment and MF-more fragments) position of data in this fragment specifies how long (in router hops) the datagram is to remain in the internet ID of transport protocol - UDP, TCP, ICMP checksum for the header only 32 bit IP address of source 32 bit IP address of destination option type and data for additional facilities padding to extend options data to multiple of 4 octets 49 Classes of IP Address All addresses are based on a 32 bit integer which contains a network id and he id number of the host on that network.

The three network classes cater for different types of network requirements: Class A For very large networks with upto 16 million hosts Class B For intermediate networks with between 256 and 65k hosts Class C For small networks with less than 255 hosts In the case of this project, Class B and C IP addresses are used.

Dotted Decimal Notation A dotted decimalisation for all IP addresses is used, which represents the address as four integers, separated by decimal points. 00001010 00000001 00000010 00000011 becomes .1.2.3 Each integer gives a value of 1 octet.

Claims (39)

1. A method of configuring or virtually documenting a cellular IP network architecture, using a computer application, comprising the steps of: receiving input specifying an existing or new network site, receiving input specifying one or more elements associated the network site, for each of one or more elements, storing data in a database structure identifying the element to associate the element with the network site, for each of the one or more elements, receiving input specifying one or more sub element modules associated with the element, for each of the one or more sub element modules, storing data in the database structure identifying the sub element module to associate the sub element module with a respective element, assigning IP addresses to the sub element modules, and storing data in the database structure specifying the IP address assigned for each sub element module.

2. A method according to claim 1 wherein the step of assigning IP addresses to sub element modules comprises the steps of: receiving input specifying at least one interface associated with an element, receiving input specifying a subnet mask and subnet address for the interface, and identifying a plurality of IP addresses based on the subnet mask and subnet address, the plurality of IP addresses being for assigning to sub element modules associated with the element.

3. A method according to claim 2 further comprising the steps of: assigning a first IP address of the plurality of IP addresses to a first sub element module associated with the element, assigning a second IP address of the plurality of IP addresses to a second sub element module associated with the element, the second IP address being automatically incremented from the first IP address. 1473430 l.DOC -51 -

4. A method according to claim 3 further comprising the step of: assigning one or more subsequent IP addresses of the plurality of IP addresses to one or more respective subsequent sub element modules associated with the element, wherein each 5 subsequent IP address is automatically incremented from the previous IP address.

5 A method according to any one of claims 2 to 5 wherein the step of assigning IP addresses to sub element modules comprises the steps of: receiving input specifying one or more further interfaces associated with one or more further 10 elements, receiving input specifying a subnet mask and subnet address for each of the one or more interfaces, and for each of the one or more further elements, identifying a plurality of IP addresses based on the subnet mask and subnet address, the plurality of IP addresses being for assigning to sub 15 element modules associated with the element.

6. A method according to claim 1 wherein the step of assigning IP addresses to sub element modules comprises the steps of: receiving input specifying an element and a plurality of IP addresses to be associated with an 20 element, assigning a first IP address of the plurality of IP addresses to a first sub element module associated with the element, assigning a second IP address of the plurality of IP addresses to a second sub element module associated with the element, the second IP address being automatically incremented from 25 the first IP address.

7. A method according to claim 6 further comprising the step of: assigning one or more subsequent IP addresses of the plurality of IP addresses to one or more respective subsequent sub element modules associated with the element, wherein each 30 subsequent IP address is automatically incremented from the previous IP address. 1473430_1.DOC -52-

8. A method according to any one of claims 6 or 7 wherein the step of assigning IP addresses to sub element modules further comprises the steps of: receiving input specifying one or more further elements, and 5 for each of the one or more further elements, receiving input specifying a plurality of IP addresses to be associated with an element, for each of the one or more further elements, assigning one or more IP addresses of the plurality of IP addresses to one or more sub element modules associated with the element, wherein each subsequent IP address is automatically incremented from the previous IP address. 10

9. A method according to any preceding claim wherein the data identifying the elements comprises data defining a label for the element.

10. A method according to any preceding claim wherein the data identifying the elements 15 comprises data defining an element ID for the element.

11. A method according to any preceding claim wherein the step of receiving input specifying one or more elements associated with the network site comprises the steps of: retrieving a plurality of elements from a store, the elements being candidate elements for use 20 with that network site, displaying the plurality of elements, and receiving input specifying one or more of the displayed elements.

12. A method according to any preceding claim wherein the step of specifying one or more 25 elements associated with the network site comprises the steps of: for each element, specifying an element type and specifying a quantity of that element type.

13. A method according to any preceding claim wherein the step of receiving input specifying one or more sub element modules associated with the element comprises the steps of: 147343CM.DOC -53- receiving input specifying the element, retrieving a plurality of sub element modules from a store, the sub element modules being candidate sub element modules for use with that element, displaying the plurality of sub element modules, and 5 receiving input specifying one or more of the displayed sub element modules.

14. A method according to any preceding claim further comprising the steps of: selecting a country associated with the network site. 10 15. A method according to any preceding claim further comprising the steps of: receiving input specifying one or more portions of the network, retrieving data from the data structure relating to those portions, using the data to display information indicating the cellular IP network architecture in respect of the portions.

15

16. A method according to claim 15 wherein the portions could relate to one or more of the following: one or more network sites, one or more elements, 20 one or more interfaces, one or more sub element modules, one or more countries.

17. A method according to any preceding claim further comprising the step of specifying one or 25 more further existing or new network sites, wherein for each further network site the method comprises the steps of: receiving input specifying one or more elements associated the network site, 1473430_1.DOC -54- for each of one or more elements, storing data in a database structure identifying the element to associate the element with the network site, for each of the one or more elements, receiving input specifying one or more sub element 5 modules associated with the element, for each of the one or more sub element modules, storing data in the database structure identifying the sub element module to associate the sub element module with a respective element, and assigning IP addresses to the sub element modules, and 10 storing data in the database structure specifying the IP address assigned for each sub element module.

A method according to any preceding claim wherein an element could be one or more of: a router, a switch, a firewall, a Node B, aBSC, a MSC, a HLR, a server.

19. A method according to any preceding claim wherein a sub element module could be one or more of: 25 a port, a network card, a sub interface, a sub module. 1473430 l.DOC 18. 15 20 -55

20. A method according to any preceding claim wherein documenting or configumTgft nenular IP network architecture involves inputting a network configuration, the method further comprising the step of modifying one or more portions of the network configuration. 5

21. A computer program for configuring or virtually documenting a cellular IP network architecture, the program being adapted to: receive input specifying an existing or new network site, receive input specifying one or more elements associated the network site, ^^10 for each of one or more elements, store data in a database structure identifying the element to associate the element with the network site, for each of the one or more elements, receive input specifying one or more sub element modules associated with the element, for each of the one or more sub element modules, store data in the database structure 15 identifying the sub element module to associate the sub element module with a respective element, assign IP addresses to the sub element modules, and store data in the database structure specifying the IP address assigned for each sub element module. 20

22. A computer program according to claim 21 wherein to assign IP addresses to sub element modules the program is adapted to: receive input specifying at least one interface associated with an element, receive input specifying a subnet mask and subnet address for the interface, and identify a plurality of IP addresses based on the subnet mask and subnet address, the plurality 25 of IP addresses being for assigning to sub element modules associated with the element.

23. A computer program according to claim 22 further adapted to: assign a first IP address of the plurality of IP addresses to a first sub element module associated with the element, -56- assign a second IP address of the plurality of IP addresses to a second sub element module associated with the element, the second IP address being automatically incremented from the first IP address. 5

24. A computer program according to claim 23 further adapted to: assign one or more subsequent IP addresses of the plurality of IP addresses to one or more respective subsequent sub element modules associated with the element, wherein each subsequent IP address is automatically incremented from the previous IP address. 10

25 A computer program according to any one of claims 22 to 25 wherein to assign IP addresses to sub element modules the program is adapted to: receive input specifying one or more further interfaces associated with one or more further elements, 15 receive input specifying a subnet mask and subnet address for each of the one or more interfaces, and for each of the one or more further elements, identify a plurality of IP addresses based on the subnet mask and subnet address, the plurality of IP addresses being for assigning to sub element modules associated with the element. 20

26. A computer program according to claim 21 wherein to assign IP addresses to sub element modules the program is adapted to: receive input specifying an element and a plurality of IP addresses to be associated with an element, 25 assign a first IP address of the plurality of IP addresses to a first sub element module associated with the element, assign a second IP address of the plurality of IP addresses to a second sub element module associated with the element, the second IP address being automatically incremented from the first IP address. 1473430_1.DOC -57-

27. A computer program according to claim 26 further adapted to: assign one or more subsequent IP addresses of the plurality of IP addresses to one or more respective subsequent sub element modules associated with the element, wherein each subsequent IP address is automatically incremented from the previous IP address.

28. A computer program according to any one of claims 26 or 27 wherein to assign IP addresses to sub element modules the program is further adapted to: receive input specifying one or more further elements, and for each of the one or more further elements, receive input specifying a plurality of IP addresses to be associated with an element, for each of the one or more further elements, assign one or more IP addresses of the plurality of IP addresses to one or more sub element modules associated with the element, wherein each subsequent IP address is automatically incremented from the previous IP address.

29. A computer program according to any one of claims 21 to 28 wherein the data identifying the elements comprises data defining a label for the element.

30. A computer program according to any one of claims 21 to 29 wherein the data identifying the elements comprises data defining an element ID for the element.

31. A computer program according to any one of claims 21 to 30 wherein the step of receiving input specifying one or more elements associated with the network site comprises the steps of: retrieve a plurality of elements from a store, the elements being candidate elements for use with that network site, display the plurality of elements, and receive input specifying one or more of the displayed elements.

32. A computer program according to any one of claims 21 to 31 wherein to specify one or more elements associated with the network site the program is adapted to: 147343Q_1.DOC -58- for each element, specify an element type and specifying a quantity of that element type.

33. A computer program according to any one of claims 21 to 32 wherein to receive input specifying one or more sub element modules associated with the element the program is adapted to: receive input specifying the element, retrieve a plurality of sub element modules from a store, the sub element modules being candidate sub element modules for use with that element, display the plurality of sub element modules, and receive input specifying one or more of the displayed sub element modules.

34. A computer program according to any one of claims 21 to 33 further adapted to: select a country associated with the network site.

35. A computer program according to any one of claims 21 to 34 further adapted to: receive input specifying one or more portions of the network, retrieve data from the data structure relating to those portions, use the data to display information indicating the cellular IP network architecture in respect of the portions.

36. A computer program according to claim 35 wherein the portions could relate to one or more of the following: one or more network sites, one or more elements, one or more interfaces, one or more sub element modules, one or more countries. 1 5 JUL 2008 <%eN<*>y -59-

37. A computer program according to any one of claims 21 to 36 further adapted to specify one or more further existing or new network sites, wherein for each further network site the program is adapted to: receive input specifying one or more elements associated the network site, for each of one or more elements, store data in a database structure identifying the element to associate the element with the network site, for each of the one or more elements, receive input specifying one or more sub element modules associated with the element, for each of the one or more sub element modules, store data in the database structure identifying the sub element module to associate the sub element module with a respective element, and assign IP addresses to the sub element modules, and store data in the database structure specifying the IP address assigned for each sub element module.

38. A computer program according to any one of claims 21 to 37 wherein an element could be one or more of: a router, a switch, a firewall, a Node B, aBSC, a MSC, a HLR, a server.

39. A method according to any preceding claim wherein a sub element module could be one or more of: 1473430 l.DOC a port, a network card, a sub interface, a sub module. 1473430 l.DOC