Abstract:
A method for managing a network system via a managed object (MO), wherein a system administrator inputs to a network element connected to a maintenance terminal, a system ID for a network element under network management. The network element to be managed receives the system ID and sends back its own address to the network element connected to the maintenance terminal. The network element connected to the maintenance terminal, when receiving the address, sends a MO generator Protocol Data Unit (PDU) to the network element to be managed, and then allows the network element to be managed to generate a MO therein. The network element connected to the maintenance terminal also receives the MO generator PDU from the network element to be managed, and generates the MO for the network element to be managed on its own network element.

Description:
BACKGROUND OF THE INVENTION  
         [0001]    The continuing spread of the information society, as well as the colossal size and complexity of network systems have made network management increasingly indispensable. In the international standard for networks called Open Systems Interconnection (OSI), a method has been proposed for carrying out network management by using a model called “Managed Object” (hereafter abbreviated to MO) modeled on an actual system. The OSI managed object can define by all objects managed on a network. The attributes and action can be described by an “object oriented” concept.  
           [0002]    This invention is described presuming the use of OSI managed objects. The OSI managed objects and overall principle relating to OSI managed objects are described here.  
           [0003]    The principle of OSI managed objects is first explained using FIG. 7. The structure of the SAP address for OSI and the AP-Title and AE-Title are described in FIG. 7.  
           [0004]    The architecture and the protocol in OSI are defined utilizing a layer model.  
           [0005]    The SAP (Service Access Point) is defined as the access point for each OSI layer. The SAP for the network layer for example, is the NSAP (Network Service Access Point) and the SAP for the presentation layer is the PSAP (Presentation Service Access Point). Addresses for their access points are respectively called the NSAP address and the PSAP address with the relation shown in FIG. 7A. In other words, the PSAP address is made by adding to the header, a selector consisting of supplemental information for the transport layer, session layer and presentation layer constituting the upper network layers. The selector consisting of supplemental information for each layer is called the OSI selector.  
           [0006]    The OSI, on the other hand, uses a principle called the AE-Title to access the network system as seen from the application layer. As shown in FIG. 7B, the AE-Title is comprised of an AE qualifier and an AP-Title. The AE qualifier describes attributes of the application. The AP-title is expressed in layers for univocally identifying each network operating point and the tail of the AP-Title contains a system number. The previously described SAP address is a physical address, and the AP-Title is a system logic address.  
           [0007]    The OSI managed object can be defined according to user&#39;s needs. The OSI provides a standard address management MO for address management. Typical MO is listed in Table 1. An instance for each class is generated for performing network management, and attributes are recorded in that instance.  
                       TABLE 1                           ADDRESS           ITEM   MANAGEMENT           NO.   MO CLASS   DESCRIPTION                   1   sap2   Holds attributes presentation layer               service access point (PSAP)       2   communicationsEntity   Holds distinguishing name (DN) of               corresponding sap2 as the attribute.           ApplicationProcess   Holds the attributes of the AP-Title.       3       Each instance has an AE qualifier added               to the instance ID, and manages the AE-               Title required for establishing an               association.                  
 
           [0008]    The Sap2 class as described in Table 1 is address information relating to PSAP. The application process class is information relating to the AE-Title and the AP-Title. The DN of the communication entity class is an index for identifying the instance of the Sap2 class.  
           [0009]    The core of each network system defined in the above mentioned OSI possesses an NSAP address and a PSAP address. An address independent of these NSAP and PSAP addresses, and available for defining a system ID to allow recognizing a system, would prove convenient.  
           [0010]    The TARP (Target ID Address Resolution Protocol) function defined in GR-253-CORE of Bellcore, changes the system nickname consisting of the TID (Target Identifier), to the system NSAP address, and conversely changes the NSAP address to the TID. A function is also possessed for notifying other systems that the TID and NSAP addresses have been changed.  
           [0011]    In a system comprised of mutually linked network elements, MO listed on the other party&#39;s network element are needed on the network element connected to the graphical local craft terminal in order to maintain network systems in remote locations. Therefore, when making new additions to the network elements such as when expanding the network elements or when changing the addresses of those network elements, the MOs listed in the network element that was changed, must be made and distributed to all network elements that attempt to access the network element that underwent the changes, creating the problem of an increasingly large maintenance or servicing work load.  
         SUMMARY OF THE INVENTION  
         [0012]    The present invention aims to reduce the servicing workload on a system administrator, by automatically generating a MO and allowing access, even in a case without the MO for the changed network element, just by entering to the network element directly connected to a graphical local craft terminal, the system ID and address of a network element that underwent the changes or expansion.  
           [0013]    In order to achieve the object, the present invention is provided to perform the following processing in a network system. When system expansion or its address change occurs in a network element, a system administrator enters the system ID or the network address of the network element that underwent the changes or expansion. The network element directly connected to the graphical local craft terminal, with use of its function to change the system ID-address that changes the system ID to an NSAP address and vice versa, sends the data entered by the system administrator, to the other party&#39;s network element. The other party&#39;s network element sends back corresponding data based on the function.  
           [0014]    The network element directly connected to the graphical local craft terminal, afterwards sends its own system No., PSAP address and system ID to the other party&#39;s network element. The other party&#39;s network element then generates an MO based on these data, and in the same way sends back its own system No., PSAP address and system ID. Based on the data returned from the other party&#39;s network element, the network element directly connected to the graphical local craft terminal, generates the MO of the other party&#39;s network element. Thus, through the Mo generated on both network elements, the system administrator can access the other party Is network element via the graphical local craft terminal so as to perform maintenance work.  
           [0015]    In short, the MO is automatically generated and sent so that the system administrator is relieved of the task of making and sending an MO to thereby alleviate the workload on the system administrator. 
       
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0016]    [0016]FIG. 1 is a system block diagram showing the network system of the present invention;  
         [0017]    [0017]FIG. 2 is a system block diagram showing the network system of the present invention when a new network element D has been added;  
         [0018]    [0018]FIG. 3 is a communications sequence chart for the network management method of the first embodiment of the present invention;  
         [0019]    [0019]FIG. 4 is a communications sequence chart for the network management method of the first embodiment of the present invention;  
         [0020]    [0020]FIG. 5 is a communications sequence chart for the network management method of the second embodiment of the present invention;  
         [0021]    [0021]FIG. 6 is a communications sequence chart for the network management method of the second embodiment of the present invention; and  
         [0022]    [0022]FIG. 7 illustrates the structure of the SAP address of the OSI, the AP-Title, and AE-Title. 
     
    
     DESCRIPTION OF THE PREFERRED EMBODIMENTS  
       [0023]    The system structure of the network system of the present invention is first described while referring to the FIG. 1.  
         [0024]    [0024]FIG. 1 is a system block diagram of the network system of the present invention.  
         [0025]    In this network system, the network element A 10 , the network element B 20 , and the network element C 30  are connected in link topology allowing mutual communication.  
         [0026]    Each network element possesses an address management MO 100  which consists of a MO of an OSI as explained previously, and network management is performed by means of this MO. An address management control function  110  in each network element constitutes the means for accessing this MO. A system ID-address change function  120  is a function to alternately change the system ID assigned to this system and the NSAP address of the OSI. A communication control function  130  is a function for communication of that network element with other network elements. The network element A 10  connected to a graphical local craft terminal  00  is configured to allow servicing all these network elements.  
         [0027]    MOs for the system A, system B, and system C are generated as the address management MO 100  of the network element A 10 . The network element A 10 , the network element B 20 , and the network element C 30  are in this way also capable of being maintained from the network element A 10 .  
         [0028]    Address management MO for other network elements are in the same way generated in the network element B 20  and the network element C 30  so that other systems are interactively recognized and network management performed.  
         [0029]    The first embodiment of the present invention is next described assuming the use of the above-mentioned network system structures, while referring to FIG. 2 through FIG. 4.  
         [0030]    [0030]FIG. 2 is a system block diagram showing the network system of the present invention when a new network element D 40  has been added. In this configuration, a new network element D 40  has been added between the network element A 10  and the network element C 30 .  
         [0031]    [0031]FIG. 3 and FIG. 4 are communications sequence charts for the network management method of the first embodiment of the present invention.  
         [0032]    The network management method of the present invention in this case, automatically generates an MO in each network element, with the object of alleviating the network management workload.  
         [0033]    The following description, of the network element A 10 , assumes the system ID is TOKYO, the NSAP address is aaa, and the system No. is 100. The description of the added network element D, on the other hand, assumes the system ID is OSAKA, the NSAP address is ddd, and the system No. is 400.  
         [0034]    The system ID is added to each network element and is a kind of nickname.  
         [0035]    In the network management method of the present embodiment, the system ID “OSAKA” of the added network element D 40  is input to the network element A 10  via the graphical local craft terminal  00 . The address management MO  100  for the network element D can in this way be generated in the network element A 10  having graphical local craft terminal  00  as shown in FIG. 2, while the address management MO  100  for network element A can be generated in the newly added network element D 40 . The method for generating the MO is described next.  
         [0036]    First of all, when attempting to connect to the network element A 10 , an association request is issued from the graphical local craft terminal  00  (SQ 3 - 2 ), and a response is normally received from the network element A 10  (SQ 3 - 3 ). A connection is in this way established, and communication is afterwards possible to the network element A 10  from the graphical local craft terminal  00 . After the network element A 10  becomes accessible, the system ID OSAKA of the network element D, is input from the graphical local craft terminal  00  (SQ 3 - 4 ).  
         [0037]    The network element A 10  assembles a PDU (Protocol Data Unit) from the system ID input through the system ID-address change function  120 , to inquire about the NSAP address in each network element, and sends the PDU along the network (SQ 3 - 5 ). Note that this PDU for asking the NSAP address from the system ID is called a Type 1 PDU.  
         [0038]    If the item in the PDU request does not match the system IDs of the network element B 20  and the network element C 30 , the PDU is sent to the next connected network element D 40 . If the network element D 40 , after comparing the Type 1 PDU data with its own system ID, finds that the Type 1 PDU data matches its own system ID, it sends back a PDU set with network element  40 &#39;s own NSAP address of ddd to the network element A 10  (SQ 3 - 6 ). Note that the PDU set with the system ID and the NSAP address of ddd is called a Type 3 PDU.  
         [0039]    The network element A 10 , when receiving this Type 3 PDU, extracts the NSAP address of ddd from the PDU, adds OSI selectors to, and makes a PSAP address (SQ 3 - 7 ). Note that a PSAP address is made by adding to the NSAP address, a transport layer, session layer and presentation layer as shown in FIG. 7A.  
         [0040]    The network element A 10  next extracts the PSAP address from the Sap2 class instance attribute of its own address management MO  100  (SQ 3 - 8 ).  
         [0041]    The network element A 10 , using its own system ID of TOKYO, its own PSAP address and its own system number of 100, generates one PDU, and directly sends the PDU to the network element D 40  (SQ 3 - 9 ). Note that this PDU is called an MO generator PDU. The PSAP address of the network element D 40  is known at this stage so the PDU can be sent directly to the network element D 40  without being sent by way of other network elements.  
         [0042]    The network element D 40  receives this MO generator PDU, and generates an address management MO  100  for the network element A 10  by utilizing the PSAP address and system number of this received PDU.  
         [0043]    The network element D 40  checks to determine whether or not an address management MO  100  corresponding to the network element A 10  is already present (SQ 3 - 10 ). The network element D 40 , if not present, generates an address management MO  100  corresponding to the network element A 10 , based on the MO generator PDU (SQ 3 - 11 ), while, if already present, it checks to determine whether the PSAP address within the message matches the managed PSAP address (SQ 3 - 12 ). If the two addresses are matched, then no processing is implemented. However if not found to be a match, then the address is determined to have been changed, and the previously existing address management MO  100  corresponding to the network element A 10  is deleted. An address management MO  100  is then again generated corresponding to the network element A 10 , utilizing the MO generator PDU (SQ 3 - 13 ).  
         [0044]    Next, the network element D 40  receives the MO generator PDU from the network element A 10 , and when the processing is finished, generates an MO generator PDU per its own system ID of OSAKA, own NSAP address of ddd, and own system number of 400, and sends this PDU to the network element A 10  (SQ 3 - 14 ). Here also, the network element D 40  already knows the PSAP address for the network element A 10 , so the MO generator PDU can be sent directly to the network element A 10 .  
         [0045]    Hereafter, in the same way, the network element A 10  receives the MO generator PDU from the network element D 40 , and the procedure for generating an address management MO  100  corresponding to the network element D 40  using the system number and the PSAP address of the received PDU is explained.  
         [0046]    First of all a check is made to find if an address management MO  100  corresponding to the network element D 40  is already present (SQ 3 - 15 ). If not present, then an address management MO  100  relating to the network element D 40  is made based on the MO generator PDU (SQ 3 - 16 ). If already present, then a comparison is made to find if the PSAP address within the message matches the managed PSAP address (SQ 3 - 17 ) and if the two addresses are matched, no processing is implemented. However if not found to be matched, the address is determined to have been changed, and the previously existing address management MO  100  corresponding to the network element D 40  is deleted. An address management MO  100  is then again generated corresponding to the network element D 40 , utilizing the MO generator PDU (SQ 3 - 18 ).  
         [0047]    An address management MO  100  is in this way mutually generated in both the network element A 10  and the network element D 40  as shown in FIG. 2. The network element A 10  then, sends back the NSAP address ddd, and the system number 400 of network element D 40  to the graphical local craft terminal  00  as a message that the processing is complete.  
         [0048]    When the above processing is complete, a system administrator makes an association request to the network element D 40  using the graphical local craft terminal  00  (SQ 3 - 20 ) and a normal reply is received (SQ 3 - 21 ). A connection with the network element D 40  is established in this way and various operations relating to network management on the network element D 40  are now possible, from the local graphical terminal connected to the network element A 10 .  
         [0049]    The second embodiment of the present invention is next explained while referring to FIG. 5 and FIG. 6 assuming the above network element structure as a prerequisite. FIG. 5 and FIG. 6 are communications sequence charts for the network management method of the second embodiment of the present invention.  
         [0050]    As explained in the first embodiment, when the network structure of FIG. 1 is changed to the structure of FIG. 2, the system ID of the network element D 40  is input from the graphical local craft terminal  00 , and by changing the system ID to an NSAP address, generates the address management MO  100 .  
         [0051]    In the present embodiment, the network structure is the same, however contrary to the first embodiment, the NSAP address is input from the graphical local craft terminal  00 , the NSAP address changed to a system ID, and the address management MO  100  generated.  
         [0052]    During servicing of the network element, sometimes the address of the network element is known but the system ID constituting the nickname is not known. Or even if the system ID is known, it may have been changed, doubts exist and a check must sometimes be made. At such times, the functions explained for this embodiment are useful.  
         [0053]    In the case of this embodiment, a new network element D has been added between the network element A 10  and the network element C 30 , in the network element structure of FIG. 1.  
         [0054]    In the network management method of this embodiment also, the same as in the first embodiment, an MO is automatically generated in each network element with the aim of alleviating the network management workload. Contrary to the network management method of the first embodiment however, an NSAP address of ddd of the added network element D is input from the graphical local craft terminal  00 . As shown in FIG. 2, the generating of an address management MO  100  of network element D in the network element A 10  having the graphical local craft terminal  00 , and also the generating of an address management MO  100  of the network element A in the newly added network element D 40 , is the same as the first embodiment.  
         [0055]    First of all, an association request is issued from the graphical local craft terminal  00  connected to the network element A 10  (SQ 5 - 2 ), and a normal reply received from the network element A 10  (SQ 5 - 3 ). A connection is in this way established, and communication is afterwards possible to the network element A 10  from the graphical local craft terminal  00 . After the network element A 10  becomes accessible, the NSAP address of ddd of network element D, is input from the graphical local craft terminal  00  (SQ 5 - 4 ).  
         [0056]    The network element A 10  assembles a PDU (Protocol Data Unit) from the system ID input from the graphical local craft terminal  00  by the system ID-address change function  120 , to inquire about the system ID to each system element that was input, and sends the PDU over the network (SQ 5 - 5 ). This PDU for asking the system ID from the NSAP address is called a Type 5 PDU.  
         [0057]    Here, unlike the first embodiment, the NSAP address of the network element D 40  is known so the PDU can be sent directly to the network element D 40 .  
         [0058]    When the Type 5 PDU arrives at the network element D 40 , a Type 3 PDU set with the network element D 40 &#39;s own system ID of OSAKA is sent back to the network element A 10  (SQ 5 - 6 ).  
         [0059]    When the network element A 10  receives the Type 3 PDU, it extracts the NSAP address from that PDU, adds the OSI selectors, and thereby makes a PSAP address made (SQ 5 - 7 ).  
         [0060]    The network element A 10  next extracts the PSAP address from the sap2 class instance attribute of its own address management MO  100  (SQ 5 - 8 ). The network element A 10  then generates MO generator PDU using its own system ID of TOKYO, its own PSAP address and its own system number of 100, and directly sends the PDU to the network element D 40  (SQ 5 - 9 ).  
         [0061]    These procedures are the same as for the first embodiment. The procedures from here onwards are also completely identical to the first embodiment. This MO generator PDU is received in the network element D 40 , and an address management MO  100  for the network element A 10  is generated from the PSAP address and system number of this received PDU.  
         [0062]    First, a check is made to determine whether or not an address management MO  100  corresponding to the network element A 10  is already present (SQ 5 - 10 ). If not present, an address management MO  100  for the network element A 10  is then generated, based on the MO generator PDU (SQ 5 - 11 ). However, if already present, a comparison is made to find if the PSAP address within the message matches the managed PSAP address (SQ 5 - 12 ) and if the two addresses are matched, then no processing is implemented. However if not found to be matched, then the address is determined to have been changed, and the previously existing address management MO  100  corresponding to the network element A 10  is deleted. An address management MO  100  is then again generated corresponding to the network element A 10 , based on the MO generator PDU (SQ 5 - 13 ).  
         [0063]    Next, the network element D 40  receives the MO generator PDU from the network element A 10 , and when the processing is finished, generates an MO generator PDU using its own system ID of OSAKA, own PSAP address, and its own system number of 400, and sends this PDU to the network element A 10  (SQ 5 - 14 ).  
         [0064]    The network element A checks to find if an address management MO  100  corresponding to the network element D 40  is already present (SQ 5 - 15 ). If not present, then an address management MO  100  relating to the network element D 40  is made based on the MO generator PDU (SQ 5 - 16 ). If already present, the network element A 10  compares to find if the PSAP address within the message matches the managed PSAP address (SQ 5 - 17 ) and if the two addresses are matched, then no processing is implemented. However if not found to be matched, then the address is determined to have been changed, and the previously existing address management MO  100  corresponding to the network element D 40  is deleted. An address management MO  100  is then again generated corresponding to the network element D 40 , based on the MO generator PDU (SQ 5 - 18 ).  
         [0065]    An address management MO  100  is in this way mutually generated in both the network element A 10  and the network element D 40  as shown in FIG. 2. The network element A 10  then, the same as in the first embodiment, sends back an NSAP address of ddd and system number 400 of network element D 40  to the graphical local craft terminal  00  as a message that the processing is complete.  
         [0066]    When the above processing is complete, a system administrator makes an association request to the network element D 40  using the graphical local craft terminal  00  (SQ 5 - 20 ) and a normal reply is received (SQ 5 - 21 ). A connection with the network element D 40  is established in this way and various operations relating to network management on the network element D 40  are now possible, from the local graphical terminal connected to the network element A 10 .  
         [0067]    In the present invention, when a change in the system has occurred such as the adding of a network element, even in the case that there is no MO related to the network element of the other party, on the graphical local craft terminal connected the network element, a MO can automatically be made and the network element of the other part can be accessed by just entering the system ID and address of the network element of the other party. In this way, a network system and a network management method can be provided that alleviate the load on a system administrator.