JPH04160893A - Station data/subscriber data management method by object oriented software - Google Patents

Abstract

PURPOSE:To reduce the restart time by adding a function of revising a generating time of a static object and of self-delete by an instruction from the static object to the software. CONSTITUTION:An object infra manages a state of a static object B and discriminates whether the static object required for the processing is already generated or not generated yet in a memory at a message reception of a program processing execution request. When not generated yet, a content of a variable of an object A corresponding to the static object B is read from a database managing the variable, the static object B is set and the generation time is revised. Moreover, the object infra deletes the static object not required by a command from the static object B. Thus, the restart processing time is reduced.

Description

DETAILED DESCRIPTION OF THE INVENTION (Industrial Field of Application) The present invention is directed to station data, which is data created for every five stations in an exchange in which object-oriented software has been introduced.
This relates to a method of managing subscriber data.

(Prior Art) In switching software using conventional procedural language, the restart processing program manages the initial setting data of the call processing program for each restart level at the time of initial setting of the switch or restart processing, and the initial setting conditions of the data are I have done the initial settings.

Also, several years ago, when designing replacement software, variables for storing resource status were integrated into the routines that process each command. In other words, a software design method based on a concept called encapsulated object orientation is becoming extremely promising.

As for the technology in the field of object-oriented software, see IEICE Technical Research Report Vol.

87 A 337, published January 22, 1988.

Publisher: Institute of Electronics, Information and Communication Engineers 5E87-147 Toshihiro Kai and 3 others There was something described in "Exchange program configuration using object model".

Therefore, the service layer, call control layer, and rinse layer are switching function layers based on object orientation.

Application software consisting of object groups in the device hierarchy, an object interface that provides an execution environment for the application software, and an object infrastructure (hereinafter referred to as object infrastructure) consisting of real-time basic O8. Attempts have been made to build software.

Figure 2 shows the positioning of object infrastructure in exchange software.

In general, software for switching equipment can be broadly divided into programs and data. The program is called a system program, and is composed of a series of instructions that define the operating procedure for the storage program-controlled exchange to perform the intended work. The data is further divided into system data, station data, and subscriber data. System data is among the data used by the exchange to perform exchange processing.
This refers to data that is given in a fixed manner, regardless of station conditions.

Office data refers to information unique to the exchange among the data used by the exchange to perform switching processing.

Subscriber data refers to information about subscribers among the data used by the exchange to perform switching processing, and is data that provides information about the subscribers to the exchange. Therefore, it differs from subscriber to subscriber.

FIG. 6 shows a method for initializing objects in conventional object-oriented software.

The initialization function block receives the initialization trigger - (6th
In the figure, the initialization block sends an object generation request (■ in FIG. 6) to the object infrastructure.

The object infrastructure manages the creation and destruction of various objects, and the sending and receiving of messages.

When the object infrastructure receives an object generation request from the initialization function block, the object infrastructure generates various objects (■ in FIG. 6).

These generated various objects are processed by the object infrastructure by executing the initial setting program processing.
It is set as an object variable as shown in Figure 6 (■).

When station data and subscriber data are realized using object-oriented software, the station data and subscriber data are expressed as variables (object variables) within each object, as shown in FIG.

Among various objects, objects having station data and subscriber data will be referred to as static objects in the following description.

The station data/subscriber data information set in this object variable is given as an argument that specifies the contents of the variable as program inheritance information from the initial setting function block when executing the initial setting program process. The static object generated in this way always exists in the memory as long as there is no change in the station data.

(Problems to be Solved by the Invention) However, in the conventional object-oriented software data management method described above, (1) the restart processing time increases because a large number of static objects such as subscriber objects are generated;

■ A large number of static objects unrelated to the call currently being processed always reside in memory, resulting in a large amount of memory waste.

■ Since the initial setting function block needs to grasp all station data, changes to static objects are likely to have a ripple effect.

There was a problem.

In order to eliminate the above-mentioned problems, this invention shortens the restart time and makes effective use of memory by changing the generation time of static objects and adding a function that can self-destruct based on instructions from static objects. In addition, from the programmer's point of view, the setting method for station data for static object variables is done in the object infrastructure when the object is created, and by localizing the range of awareness of station data and subscriber data, a highly independent software structure can be achieved. The purpose is to

(Means for Solving the Problems) In order to solve the above-mentioned problems, the present invention provides an exchange in which object-oriented software is introduced, in which the software consists of an application program consisting of various object groups, an object interface, and a real-time basic O8. The object infrastructure has a hierarchical structure composed of object infrastructures, and the object infrastructure detects a program processing execution request for a static object from a message sending object, and the object infrastructure determines whether or not the static object has been generated. If the static object has been generated, the object infrastructure performs the step of instructing the static object to execute the program, and if the static object has not been generated, the object infrastructure generates the static object and retrieves the variable contents of the static object from the database. A step in which a static object is generated by reading and setting a variable in the static object, and the object infrastructure instructs the static object to execute a program, and if the static object determines that it does not need to exist, the static object A method for managing station data and subscriber data using object-oriented software, including the steps of sending a deletion request to an object infrastructure, and causing the object infrastructure to destroy the unnecessary static object.

(Operation) According to the present invention, the state of static objects can be managed in the object infrastructure, and when a message requesting program processing is received, it can be determined whether the static objects necessary for processing have been generated in the memory or not in the object infrastructure. If the static object has not yet been generated, the contents of object variables corresponding to the static object are read from the database that manages the static object, the static object is set, and the generation time of the static object is changed.

Furthermore, by adding a function for the object infrastructure to delete static objects that are no longer needed based on instructions from the static object, it is possible to shorten the restart processing time and make effective use of memory.

(Embodiment) Fig. 1 is a diagram showing an embodiment of the present invention, and is a sequence chart showing the operation from creation to destruction of a static object in an exchange, and Fig. 4 is an off-line diagram consisting of an object infrastructure, database database general-purpose computer, etc. FIG. 2 is a system configuration diagram illustrating the relationship between environments.

In FIG. 1, object A is a message transmission source object, and static object B is a static object necessary for executing the program processing requested by object A.

As shown in FIG. 1, request source object A issues a program processing execution request for static object B to the object infrastructure.

■ The object infrastructure determines whether static object B has been generated or not, and determines the following processing.

Capture the software resources (specifically work area, tasks in O8, etc.) required to generate ungenerated static object) B, generate static object) B, and read the variable contents of static object B from the database. , after setting the variables in static object B, the object infrastructure sends the message for program processing execution to static object l-B.
Send to.

The object infrastructure immediately sends a program processing execution message to the static object B, skipping the generation process of the generated static object.

(2) When static object B determines that it is no longer needed, for example after a call ends, it can request the object infrastructure to eliminate itself.

In Figure 4, the offline environment shows the contents that the object infrastructure can set for the object variables of static objects based on information about static object variables (specifically, variable structure, station data elements, etc.) and station conditions, which are information for each round. The offline environment creates
Register each static object in the database.

When the object infrastructure generates a static object, it accesses the database using a logical number indicating the identification of the static object as key information, reads the contents of the variable, and sets it in the variable area of the static object.

The variable contents to be registered in the database are created in an offline environment where the database registration contents are created independently of the exchange operation, and are registered via a communication mechanism connecting the database and the offline environment as shown in FIG.

Furthermore, although FIG. 5 shows a case where the external device is a database, where the exchange and the database are also connected by a communication mechanism, the present application is not limited to this, and the central control unit (CPU) of the exchange Memo IJ (
This also includes cases in which an exchange and database are integrated to directly control the F M ).

(Effects of the Invention) As described above in detail, according to the present invention, (1) the restart processing time can be shortened by generating and deleting static objects at the time of initialization.

■ Memory bottlenecks can be resolved by dynamically creating and destroying static objects.

■ The range of station data and subscriber data to be considered can be localized into static objects, allowing a highly independent software structure.

It has the following effects.

[Brief explanation of drawings]

Figure 1 is a sequence chart from static object generation to destruction according to the present invention, Figure 2 is a diagram showing the positioning of object infrastructure in exchange software, Figure 3 is a diagram explaining the image of objects and object variables, Figure 4 is a system configuration diagram of the object infrastructure, database, and offline environment of the present invention, and FIG. 5 is a switchboard,
FIG. 6 is a system configuration diagram in which a database and an offline environment are configured as independent systems. FIG. 6 is a diagram showing an object initialization method of conventional object-oriented software. Resting 7 toes 71:11 meeting object 7 toin 7 u0wei! 11 Figure 2

Claims (3)

[Claims] (1) In a switch that has object-oriented software installed, the software has a hierarchical structure consisting of an application program consisting of a group of various objects, an object infrastructure consisting of an object interface and a real-time base OS, and the software has a hierarchical structure consisting of an application program consisting of a group of various objects, an object infrastructure consisting of an object interface and a real-time base OS, and a message sending source object is connected to the object infrastructure. detecting a program processing execution request for a static object; a step of determining whether the object infrastructure has generated the static object; and, if the static object has been generated, the object infrastructure instructs the static object to execute the program; the static object sends a deletion request to the object infrastructure when the static object determines that its existence is unnecessary; and the object infrastructure causes the unnecessary static object to disappear. A method for managing station data and subscriber data using object-oriented software. (2) In an exchange that has object-oriented software installed, the software has a hierarchical structure consisting of an application program consisting of a group of various objects, an object infrastructure consisting of an object interface and a real-time basic OS, and the software has a hierarchical structure consisting of an application program consisting of a group of various objects and an object infrastructure consisting of an object interface and a real-time basic OS. detecting a program processing execution request for a static object; a step of determining whether the object infrastructure has already generated the static object; and if the static object has not been generated, the object infrastructure generates the static object and A static object generation step in which variable contents of a static object are read from a database and set in variables in the static object, a step in which the object infrastructure instructs the static object to execute a program, and the static object itself does not need to exist. A station data/subscriber data management method for object-oriented software, characterized in that the static object sends a deletion request to the object infrastructure when it is determined that the unnecessary static object is deleted; and the object infrastructure deletes the unnecessary static object. (3) If the static object is not created, the object infrastructure reads out the variables in the static object from the database, and the offline environment further includes a step for creating the variables and registering them in the database via the communication mechanism. 3. A station data/subscriber data management method using object-oriented software as claimed in claim 2.