MXPA99008512A - Use of web technology for subscriber management activities - Google Patents

Abstract

External entity (36) data access to the customer administrative system (14) and database network elements (16) of a telecommunications network (10) is provided through a web-server (32) and an Internet (30) connection. The integrity and security of any stored data is protected through the use of a firewall (34) implemented at the web-server. In one aspect, an interface (12) is connected between the customer administrative system (14) and database network elements (16) and is also connected to the web-server (32) to handle external entity (36) requests by specifying not only which actions need to be taken but also routing the request to a proper destination. In a second aspect, the interface (12) is by-passed with respect to the handling of external entity (36) requests, with the web-server (32) specifying the actions to be taken and routing the request to the proper destination.

Description

USE OF NETWORK TECHNOLOGY FOR SUBSCRIBER MANAGEMENT ACTIVITIES CROSS REFERENCE TO RELATED REQUEST The present patent application is related to the co-pending US provisional application serial number 60 / 42,077, filed on March 28, 1997, entitled "Use of Web Technology for Subscriber Management" (Use of Network Technology for Subscriber Management), by Roch Glitho, et al, and claim priority from said co-pending provisional North American application. The disclosure of the US provisional patent application serial number 60 / 42,077 is incorporated herein by reference. BACKGROUND OF THE INVENTION Technical Field of the Invention The present invention relates to wireless telecommunications systems and, particularly, to the use of a network technology (ie, Internet) to access and manage data stored in an administrative client system ( CAS) and / or a network element such as a home location registration (HLR) database or a wireless service control node (WSCN). Description of the Related Art Reference is now made to Figure 1 where a block diagram of a portion of a telecommunications network 10 is shown which implements an interface (IF) 12 between a client administrative system (CAS) 14 and a plurality of database network elements (NE) 16. Interface 12, client administrative system 14, and database network elements 16 are interconnected through the use of a network 18 preferably comprising a network such as example, an X.25 network, separate and different from the telecommunications network 10. The telecommunications network 10 comprises a wireless communication system (eg, cellular) and the database network elements 16 comprise, for example, an address location register (HLR) or a wireless service control node (WSCN). The home location register / wireless service control node functions in the form of a database to store temporary and permanent wireless subscriber data. The permanent data stored in the home location register / wireless service control node comprises fixed information regarding the communication service subscribed by each subscriber. The temporary data stored in the home location register / wireless service control node comprises variable information as to the current location of each subscriber. In relation to the wireless service control node, additional functional operations are supported in connection with the provided subscriber services (e.g., intelligent network services). The client administrative system 14 is used to perform transactions regarding the management of permanent data stored in each network element of database 16. These administrative activities, in general, relate to transactions carried out for the purposes of creation or definition. user (ie subscriber), service activation, and the like, in relation to a given user. More particularly, the transactions are related to subscriber data management tasks such as: - Start / removal / subscription status, - Activation / cancellation of subscriber, - Supply / withdrawal / activation / passivation of service, - Definition of number C (transfer), - Code changes, and - Serial number changes. Transactions can also refer to administrative authentication tasks, such as activation / change / deactivation / authentication status. In addition, transactions are related to numbering plan settings including number range assignment, numbering plan removal, and numbering plan view. A service operator is the entity that implements and maintains the infrastructure comprising the telecommunications network 10. The service operator typically employs authorized distributors to market and sell subscriptions for telecommunications services to individual users (i.e., the subscribers). The service operator may also sell subscription blocks to anr entity known as a service provider. The service provider then markets and leases / sells these subscriptions (perhaps also through the use of its own resellers) on an individual or group basis to subscribers of end users. The access and handling of the data stored in the client administrative system 14 and the database network elements 16 is typically limited to the service operator. Regarding this aspect, the service operator is responsible through its client administrative system 14 for the control of the transactions mentioned above in relation to the administration of the permanent data stored in each network element of database 16. Now that a growing number of service providers are acquiring blocks of subscriptions for their own management. There is interest in granting the service provider access to the client administrative system 14 and each database network element 16 for purposes of transactions and / or data entry, revision and modification limited or restricted in relation to the administration tasks of the client. permanent data. Similarly, in connection with the establishment of new subscriptions, the vendors also wish to have access to the customer administrative system 14 and each database network element 16 for transactions and / or limited data entry, revision and modification purposes. or restricted. In addition, the users themselves wish to have access to their address database network element 16 for transactions and / or purposes of entry, revision and modification of limited or restricted data in relation to the maintenance of certain aspects of the permanent data including your subscription (such as your transfer, speed dial, and call sifting lists). Concerns against the maintenance of the integrity and security of the data stored in the administrative system of client 14 and each network element of database 16 must be resolved before granting said types of access to external entities. In addition, an inexpensive and user-friendly mechanism is required to provide service providers, vendors and users with transaction-related data access to the user's administrative system 14 and each database network element 16. COMPENDIUM OF THE INVENTION The present invention focuses on the above concerns in relation to accessing data related to transaction and maintaining the integrity and security of the data stored in the client administrative system and database network elements allowing access to data by external entities through a network server and an Internet connection. Sufficient security measures are implemented in a network server (for example, through the use of a firewall) to restrict the rights of external entities to access and modify stored data, in a first mode, a logical support interface of transaction, redundancy logic, request-oriented logic, and data migration logic is connected between the client administrative system and the database network elements and also the network server. All data transactions originated by external entities, requests and modifications pass through the interface, and the logic is used to specify, based on the external entity request received, the actions or the action that is required to implement the request and also to properly route the request to the appropriate client administrative system or the appropriate client administrative systems and database network elements for its management. In a second mode, the network server maintains a direct pressure with each of the client's administrative system and database network elements, thus effectively avoiding the interface in relation to the handling of requests from external entities. The functionalities of transaction logic, redundancy logic, request-oriented logic and data migration logic are then also maintained in the network server to specify on the basis of the received request, the actions to be taken and to route the request accordingly. BRIEF DESCRIPTION OF THE DRAWINGS A more complete composition of the method and apparatus of the present invention can be obtained with reference to the following Detailed Description when taken in conjunction with the accompanying drawings where: Figure 1 is a block diagram of a portion of a telecommunications network illustrating a first embodiment of the present invention; and Figure 2 is a block diagram of a portion of a telecommunications network illustrating a second embodiment of the present invention. DETAILED DESCRIPTION OF THE DRAWINGS With reference to Figure 1, a first embodiment of the present invention is described. The interface 12 functions as a service order gateway (SOG) or a service management access layer (SMAL) in relation to the management of data access between the customer administrative system 14, the base network elements of data 16 and external entities (to be described). In one aspect, the interface 12 employs a transaction logic 20 to support the client administrative system 14 and operations of external entities and transactions in terms of subscriber data management (in relation to subscriptions, similar services), authentication data as well as numbering plan data, this transaction logic 20 receives orders that originate in the administrative system of clients 14 or in an external entity, identifies the particular action or the particular actions to be taken by the client's administrative system 14 or a database network element 16 in relation to this order identifies the commands required to perform these actions, converts these commands into an appropriate format for communication and understanding by the client's administrative system or this network element database, and issues the appropriately formatted commands. The transaction-oriented logic 20 also receives response in order to order from the client administrative system 14 or identified database network element 16, converts the response (if necessary) into an appropriate format for communication and / or understanding by an administrative client system 14 or external entity that originated the order and routes the appropriately formatted response. In another aspect, the interface 12 employs redundancy logic 22 to support an automated redundancy of client management system 14 managed (and perhaps specified by external entity) of subscriber data (in relation to subscriptions, similar services), data of authentication and numbering plan data between the customer administrative system 14 and the database network elements 16. This redundancy logic 22, which operates in combination with a transaction logic 20, functions to identify for each order of Subscriber data received by the client administrative system 14 and / or by several database network elements 16 affected by the order (ie, both the primary and redundant database network elements), to identify the particular action or the particular actions to be taken by the client's administrative system and / or each database network element in relation to this order, ide ntify the commands required to perform these actions, convert each of these commands into an appropriate format for communication and / or understanding by an administrative system of clients and / or the identified database network elements, and issue the commands to each of these nodes. To support this redundancy operation, the redundancy logic 22 keeps track of the interrelationships between the various database network elements 16 in terms of the managed subscriber data, authentication data and numbering plan data, the logic of redundancy 22 correspondingly recognizes for each subscriber which of the various database network elements 16 comprises the primary database network element, and which of the various network network elements comprises the network elements of redundant database. For each order, the appropriate elements of the various database network elements 16 are identified and appropriately formatted commands are sent. In a similar way, the redundancy logic 22 recognizes which cases of redundant administration of subscriber data require updating of the client administrative system 14, and sends appropriately formatted commands. In another aspect, the interface 12 further utilizes a request-oriented logic 24 to support the request of the client administrative system 14 and / or the plurality of database network elements 16 with respect to the stored permanent information. These requests include the operation of searching the permanent data stored in the administrative system of clients 14 and / or each network element of database 16. This logic oriented towards requests 24 receives search requests, determines which one or which of the administrative system of clients 14 and database network elements 16 require a request to complete the search request, converts these requests into requests that have an appropriate format for communication and / or understanding by each individual of the necessary client administrative system and database network elements, and routes the appropriately formatted requests to the necessary client administrative system and database network element for its management. After handling by the client administrative system 14 and / or database network element 16 of the request, the search results are returned to the interface 12. The request-oriented logic 24 then collects the data from the search results returned in a file, indicates the requesting entity that originated the search request, and performs a file transfer of the data (appropriately formatted) with the entity where the request originated. In another aspect, the interface 12 employs a data migration logic 26 to support the transfer of subscriber data between the client administrative system 14, the database network elements 16, and external entities. This data release logic 26 receives migration requests, determines which nodes (such as some of the database network elements 16) comprise source and destination nodes for migration, generates migration commands that have their own format for communication and / or understanding of each individual of the necessary nodes, and routes the appropriately formatted commands to the nodes necessary for management. A more complete description of the transaction logic 20, redundancy logic 22, request-oriented logic 24 and data migration logic 26 of the interface 12 can be obtained with reference to the following co-pending, commonly assigned patent applications: - CUSTOMER ADMINISTRATIVE SUSTEM MANGEMENT OF REDUNDANT DATABASE NETWORK ELEMENTS IN A TELECOMMUNICATIONS SYSTEMS (ADMINISTRATIVE SYSTEM MANAGEMENT OF REDUNDANT DATABASE NETWORK ELEMENT CLIENTS IN A TELECOMMUNICATION SYSTEM) Serial No. 08 / 976,210, filed on November 21, 1997; - QUERY SUPPORTING INTERFACE BETWEEN TO CUSTOMER ADMINISTRATIVE SYSTEM AND DATABASE NETWORK ELEMENTS OF A TELECOMMUNICATIONS SYSTEM (REQUEST SUPPORT INTERFACE BETWEEN AN ADMINISTRATIVE SYSTEM OF CUSTOMERS AND DATABASE ELEMENTS OF A TELECOMMUNICATIONS SYSTEM) Serial No. 08 / 975,631, filed on November 21, 1997; and - MIGRATION OF SUBSCRIBER DATA BETWEEN HOME LOCATION REGISTERS OF A TELECOMMUNICATIONS SYSTEM (MIGRATION OF SUBSCRIBER DATA BETWEEN LOCALIZATION RECORDS OF ADDRESS OF A TELECOMMUNICATION SYSTEM) Serial No. 08 / 975,632, filed on November 21, 1997, Whose presentations are incorporated here by reference. The access of external entities to the telecommunications network 10 and, particularly, the interface 12 is provided through the Internet 30 and a network server 32. The interface 12 is connected to the network server 32 through a connection type. TCP / IP. The network server 32 is connected to the Internet 30 through a type of TCP / IP connection. The network server supports both the hypertext transfer protocol (HTTP) and ensures access to a hypertext transfer protocol (S-HTTP) on the Internet 30. A portfolio 34 is used to provide front-end security protection against all accesses to the internal network (ie, the telecommunications network 10 that includes the customer administrative system 14 and the network database elements 16) except those designed and authorized as legitimate service accesses. The external entities in question here include service providers, vendors and users. Using a terminal (T) or a personal computer (PC) 36 that has Internet access capabilities 30 and a programmatic network travel, the service provider, vendor or user, can obtain through the network server 32, access to limited transaction data restricted to the customer administrative system 14 and each database network element 16 of the network 10. The server 32 is correspondingly equipped with a world-wide-web address (international network) (WWW) in order to support Internet access. With this data access, and also through the use of transaction logic 20, the request-oriented logic 24 and the data migration logic 26 provided by the interface 12, the service provider, vendor or user may carry Permitted data transactions, request regarding stored information, and specify data migrations. The redundancy logic 22 of the interface 12 further ensures that backup copies of the data affected by the service provider, vendor or access to user data are properly made and distributed through the nodes for storage. Obviously it is understood that the various functionalities provided by transaction logic 20, request-oriented logic 24 and data migration logic 26 may not be available for use by all of the following: service provider, vendor or user. The firewall 34 and the network server 30 therefore function in tandem to control the nature of the access to data from entity external to the network 10, and consequently limiting in each of the service provider, vendor or user to only the types of allowed access and actions. The firewall 34 implements a type of "screened subnet" architecture. Sieved subnet firewalls employ a pair of packet filters and a host bastion (all interconnected through a subnet) as experts in the field know well. By using this firewall architecture, the guest platforms for the interface 12 and the network server 32 are profitably detached from each other. This routing mechanism supported by firewalls provides improved security. In the case in which one of the components becomes compromised, the remaining components continue to provide a line of defense against an unauthorized intrusion into the network 10 through the Internet 30. The network server 32 is programmed to support one or more types of external entity access to the network 10. Each Access type provides a different level of security. In addition, programming can specify which different classes of external entities receive different types of access. For example, a user may receive the most limited access to the network on the Internet 30. Conversely, a service provider may receive almost unlimited access to the network. The schedule further specifies the level of data access to be provided to the different classes of external entities. Again, for example, the user may be restricted to a very limited right to access, modify and create data stored on the network 10. The service provider, on the other hand, may not present the same level of restriction. A first type of network access comprises an "off-line" access. The basic operation scheme of the off-line access system is that when an external entity makes a request for data access on the Internet 30, the request is temporarily registered on the network server 32. The external entity receives a return message which indicates that the request has been registered and will be processed as soon as possible (considering, evidently, that the external entity is authorized for the level of data access required to implement this request). Once the connection with an external entity in the Internet 30 is broken, the temporarily registered request is communicated to the interface 12 for its management by the appropriate logic (s) chosen between the transaction logic 20, redundancy logic 22, logic oriented at request 24, and data migration logic 26. This access solution has an advantage insofar as it provides significant security to the network 10. However, the solution has numerous drawbacks including the network server 32 in this network access type does not support a simultaneous connection with the external entity and the information stored in the client administrative system 14 and the database network elements 16. Therefore, external entities can not see this information through their programmatic fast network review before specifying changes or modifications of data. A second type of network access includes an "offline with cache" access. The basic scheme of operation of the off-line access system with cache is the same as with the off-line system described above, with the exception that certain data of popular interest of the administrative system of clients 14 and network elements of database 16 for external entities they are stored in parallel by the network server 32 using a cache 38. With this solution, the external entity can see the hidden portion of the information stored in the client administrative system 14 and the base network elements of data 16 during your session of Internet access 30, and also review and consider this information in connection with the preparation of your request for access to data. Another benefit of this solution is the maintenance of a significant level of security for network 10 (comparable to that provided with the off-line system described above). However, the solution has several drawbacks, which include: service management command activities that affect the stored data to be duplicated at the network nodes as well as in the cache are required; synchronization of external entity data management functions with telecommunication network functions; and granting the network server 32 sufficient processing capabilities to handle not only communications from external entities but also updating the cache 38. A third type of network access comprises "on-line" access. The basic operation scheme of the online access system is to provide the external entity with interactive real-time access to the client administrative system stored in data 14 and database element 16. When an external entity makes a request of access to data on the Internet 30, the request passes through the network server 32 to the interface 12 (evidently considering that the external entity has authorization for the level of data access required to implement its request). The interface 12 then handles the received request using one or more of the following appropriate logics: transaction logic 20, redundancy logic 22, logic oriented towards requests 24 and data migration logic 26. After handling as necessary, it is generated an answer for return communication through the network server 32 to the external entity. The online access system therefore allows ^ the establishment of a communication channel on the Internet and through the data storage nodes of the network. This architecture raises important concerns regarding 1 provision of adequate security measures to protect against unauthorized access to data. The use of firewall 34 becomes an absolute requirement. In addition, other measures such as filtering requests, architecture of restricted areas for the network server and interface, low levels of permission, and security measures for guest platforms are increased in order to improve security. Other concerns with the online system relate to performance issues such as network server handling of more pending requests due to the delay between the receipt of the request and the granting of the response, and concerns about bandwidth in relation to communication links between interface 12, client administrative system 14 and database network elements 16.

A fourth type of network access comprises an "online / offline hybrid" access. The basic operation scheme of the hybrid online / offline system is to allow bringing data online from the client administrative system 14 and database network elements 16 using the request-oriented logic 24 of the interface 12 in response to requests from external entities in a manner similar to the online system described above. In the case in which the network server additionally supports the use of a cache 38, the cache is checked by the network server 32 in response to an external entity request before implementing the request-oriented logic 24 of the interface. All other data accesses to the client administrative system 14 and database network elements 16 for the purpose of accessing, modifying and creating data using transaction logic 20, redundancy logic 22, and data migration logic 26 occur in a manner similar to that described above with regard to the off-line system. Reference is now made to Figure 2 where a block diagram of a portion of a telecommunications network illustrating a second embodiment of the present invention is shown. In this mode, interface 12 is avoided in terms of data handling operations of external entity, and network server 32 (using a firewall 34) is directly connected to each of the administrative system of clients 14 and network elements of database 16 through a local network server 32 '. Obviously it will be understood that the interface 12 remains in place with its required functionality (20, 22, 24 and 26, not illustrated, see Figure 1) to handle transactions that originate in the customer administrative system 14, and also responds, as what is necessary, to external entity actions taken directly with the client administrative system 14 and database network elements 16. The network server 32 can also implement one or more of the following: transaction logic 20, redundancy logic 22, request-oriented logic 24 and data migration logic 26, as necessary and as shown, to support external entity requests and network operation 10. Network server 32 is connected to local network server 32 ' for each of the client administrative system 14 and database network elements 16 through a TCP / IP type connection. With this configuration, the interface 12 is no longer used to route external entity requests and data management activities between the client administrative system 14 and database network elements 16. The routing is handled by the network server 32 , and the processing of the requests to generate responses is handled by the local network servers 32 '. Since there are multiple destinations in the second mode for accessing the Internet from external entities (i.e., the client administrative system 14 and each of the database network elements 16), a different WWW address can be provided for each destination. However, it is convenient to keep only the unique WWW address (for example, the address of the network server 32 (as described above)) for external entity Internet access. Accordingly, an adequate routing of external entity requests and data handling activities regarding this unique address to the client administrative system 14 and each of the database network elements 16 is supported using Java manuscript and a Intelligent intermediary in the firewall 34. The advantages of reading the second modality include: a mapping based on hypertext mark-up language (HTML) to the access protocol of the administrative system of clients 14 and nodes of network elements of database 16; a local network server 32 'provided by the vendor in combination with the network node; the communication channels related to the network are separated from the telecommunications network 10; and, there is no need for the presence of an interface 12. The disadvantages of this implementation include: duplicate routing; and, added cost due to the need for local network servers 32 '. A more complete understanding of the operation of the present invention in the support of data management activities of external entities using a network technology can be obtained through the study of the following exemplary situations. Consider first the user of a cell phone. A significant amount of data recorded and controlled by the subscriber is stored in the database network elements 16. A conventional telecommunications network operation 10 allows the user to review, modify and create this data, and perhaps perform some transactions, through the mobile cell station. The primary numeric keypad of the cellular mobile station does not lend itself comfortably to access and record this data. Similarly, the small monitor provided in the mobile cell station does not lend itself comfortably for an effective review of this data. Through the present invention, the user receives network access to this stored data from network element 16 of database. It is important to note here that the security protections provided by the network server 32 and the firewall 34 prevent the user has access to the client administrative system 14, and limit access to database network elements 16 only to these user subscriptions. Through the convenience of the user's personal computer and through Internet 30, a connection is made to the network server 32. Request questions can then be made to review this stored data. In addition, data management transactions can be ordered to create and modify the stored data. Examples of fire data in relation to users comprise addressing lists, location-based service data, high-speed dialing list, and the like. Turning now to the vendors, in connection with the sale of cellular services to a user, the vendor requires to register certain subscriber information in both the administrative system of clients 14 and in network elements of database 16. The data recorded in the client administrative system 14 comprises data related to the subscription such as, for example, subscriber number (SNB), mobile subscriber number (MSNB), serial number (SRNB) as well as data related to the service. The data entry in the database network element 16 comprises the same service-related data as the aforementioned in relation to user access. The vendor access to the customer administrative system 14 and the database network element 16 in relation to other actions, activities and transactions, such as those discussed here, can also be supported. A conventional telecommunications network operation 10 required the vendor to supply the necessary information in hard copy format directly to the service operator. Through the present invention, the vendor receives access through the network to the data stored for the client in the administrative system of clients 14 and network elements of database 16. It is important to note here that the security protections provided by the network server 32 and firewall 34 limit the vendor's access to the customer administrative system 14 and database network element 16 only as necessary to establish or support the user subscriptions. Through the community of the vendor's personal computer, and through Internet 30, connection is made to the network server 32. Request requests can then be carried out to review this stored data. further, you can order data handling transactions to create or modify the stored data. Turning now to the service provider, in relation to the acquisition of subscription blocks and in relation to the marketing of these subscriptions, the service provider must register certain subscriber information in the client administrative system 14 as well as in the element of database network 16. Data entry in the customer administrative system 14 comprises subscription-related data such as subscriber number (SND), mobile subscriber number (MSNB), and serial number (SRNB). The access of the service provider to the administrative system of clients 14 in relation to other actions, activities and transactions can also be supported. Typically, data entry by the service provider is not allowed in the database network element 16. However, access to the database network element may be allowed for other actions, such as activations. A conventional telecommunications network operation 10 required that the service operator supply the necessary information in a copier format directly to the service operator. Through the present invention, the service provider has access through the network to the stored data of the client management system 14 and database network elements 16 for its subscription block. It is important to note here that the security protections provided by the network server 32 and firewalls 34 limit the access of the service provider to the client administrative system 14 and database network element 16 only as necessary to establish or support its subscription block purchased. Through the convenience of the personal computer of the service provider, and through Internet 30, a connection is made to the network server 32. Request requests can then be made to review this stored data. In addition, data handling transactions can be ordered in order to create or modify the stored data. Although the preferred embodiments of the method and apparatus of the present invention were described in the appended drawings and described in the above Detailed Description, it will be understood that this invention is not limited to the modes presented, but that numerous adjustments, modifications and modifications can be made. substitutions without departing from the spirit of the present invention in accordance with what has been proposed and defined in the appended claims.

Claims (1)

1. CLAIMS A telecommunications network that has a network element to store data in relation to telecommunications services and subscribers, and a client administrative system to perform transactions in relation to the administration to the data stored in the network element, a system for support access to data and management actions regarding the network element and client administrative system, these actions originate through external entities in relation to the telecommunications network, the system comprises: a network server that has an address of international network (WWW) and that provides an Internet connection for the communication of requests and responses between external entities and the network element and the administrative system of clients; and an interface connected to the network server and connected between the network element and the client administrative system to handle the routing of requests from external entities for access and handling of data and responses. The system according to claim 1, wherein the network element comprises a home location register. The system of claim 1, wherein the network element comprises a wireless service control node. The system according to claim 1, wherein the network server includes a firewall to protect the telecommunications network against unauthorized access from the Internet to the network element and client administrative system. The system according to claim 1, wherein the network server supports access by external entities offline to the network element and client administrative system for data access and handling purposes. The system according to claim 5, wherein the network server further includes a cache for storing a portion of the data stored in the network element and client administrative system, and where the network server also supports an online review of the data stored in the cache with offline modification of the data as stored in the network element and client administrative system. The system according to claim 1, wherein the network server supports access by external entities in line to the network element and client administrative system for data access and handling purposes. . In a telecommunications network that has a network element to store data in relation to telecommunications services and subscribers, and a client administrative system to carry out transactions in relation to the management of the data stored in the network element, a system to support access to data and management actions regarding the network element and administrative system of clients, such actions originates from entities external to the telecommunications network, the system comprises: a network server that has an address of international network (WWW) and which provides Internet-type connectivity for the communication of requests and responses between external entities and the network element and administrative system of clients; and a connection of communication links between the network server and each of the network element and client administrative system, the network server handling the routing of requests from external entities for access and handling of data and responses to them in a appropriate communication link. The system according to claim 8, wherein the network element comprises a home location register. The system according to claim 8, wherein the network element comprises a wireless service control node. The system according to claim 8, wherein the network server includes a firewall to protect the telecommunications network against unauthorized access from the Internet to the network element and client administrative system. . The system according to claim 8, where the network server supports access by external entities offline to the network element and client administrative system for data access and management purposes. The system according to claim 12, wherein the network server further includes a cache for storing a portion of the data stored in the network element and client administrative system, and where the network server also supports an online review of the data stored in the cache with offline modification of the data as stored in the network element and client administrative system. . The system according to claim 8, wherein the network server supports online access by entities external to the network element and client administrative system for data access and handling purposes. The system according to claim 8, which also includes a local network server for each of the network element and client administrative system, the local network server operates to process the received requests and generate responses.