CN111865664B - ORB object life cycle management method and system - Google Patents
ORB object life cycle management method and system Download PDFInfo
- Publication number
- CN111865664B CN111865664B CN202010570367.2A CN202010570367A CN111865664B CN 111865664 B CN111865664 B CN 111865664B CN 202010570367 A CN202010570367 A CN 202010570367A CN 111865664 B CN111865664 B CN 111865664B
- Authority
- CN
- China
- Prior art keywords
- emssession
- orb
- user
- time
- objects
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5003—Managing SLA; Interaction between SLA and QoS
- H04L41/5009—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
- H04L41/5012—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF] determining service availability, e.g. which services are available at a certain point in time
- H04L41/5016—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF] determining service availability, e.g. which services are available at a certain point in time based on statistics of service availability, e.g. in percentage or over a given time
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- Probability & Statistics with Applications (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
A method and a system for managing the life cycle of an ORB object relate to the field of network management and comprise the following steps: associating the emsSession object of the user with other dynamic ORB objects of the user; and when the user calls endSession operation or the user does not perform any operation through the emsSession object within the set time, releasing all ORB objects associated with the emsSession object one by one. The invention can lead the network management server to achieve long-term stable operation and meet the requirement of long-term stable operation of the telecommunication network management service.
Description
Technical Field
The present invention relates to the field of network management, and in particular, to a method and system for managing the lifecycle of an ORB object.
Background
Corba (Common Object Request Broker Architecture) is a mature middleware technology widely used for interfacing communications between software systems, and has also found wide application in telecommunications network management. In telecommunication network Management, a Corba interface is used for managing an EMS (Element Management System) and carrying out standard Support published by the existing international standard organization, and an NML-EML (network Element Management layer-network Management layer) interface specification published by a TMF (TeleManagement Forum) is a northbound interface standard between OSS (Operation Support Systems) and the EMS which are most widely applied at present. In the process of managing the EMS by using the Corba interface, because the OSS client and the EMS server are often connected through a wide area network, the network connection has the possibility of interruption; meanwhile, the number of OSS manufacturers is large, the software development level is uneven, and the client often breaks down in operation. If the Object Request Broker (ORB) Object at the service end in Corba cannot be effectively managed in the above scenario, the situation of memory leakage, abnormal access and the like occurs in the EMS side server, which seriously affects the stable operation of the EMS network management server and causes a challenge to the stable operation of the telecommunication network management service.
Disclosure of Invention
Aiming at the defects in the prior art, the invention aims to provide an ORB object life cycle management method and system, so that a network management server can run stably for a long time, and the requirement of long-time stable running of telecommunication network management service is met.
To achieve the above object, in one aspect, a method for managing an ORB object lifecycle includes:
associating the emsSession object of the user with other dynamic ORB objects of the user; and when the user calls endSession operation or the user does not perform any operation through the emsSession object within the set time, releasing all ORB objects associated with the emsSession object one by one.
Preferably, all existing emsSession objects are periodically traversed, and when the time difference between the occurrence time of the latest access of the emsSession object and the current time is greater than the set time, it indicates that the corresponding user does not perform any operation through the emsSession object within the set time.
Preferably, the time when the last access occurred is recorded in the emsssession object by maintaining a time record variable.
Preferably, the maintaining of the time record variable adopts a timer updating or login operation updating mode.
Preferably, the user's remaining dynamic ORB objects include various manager objects and various iterator objects.
Preferably, the emsssession object, the manager object and the iterator object are divided into three layers from top to bottom, each iterator object is subordinate to a certain manager object on the previous layer, and each manager object is subordinate to a certain emsssession object on the topmost layer.
In another aspect, an ORB object lifecycle management system is provided, comprising:
the correlation module is used for correlating the emsSession object of the user with other dynamic ORB objects of the user;
the first judgment module is used for judging whether a user calls an endSession operation;
the second judgment module is used for judging whether the user does not perform any operation through the emsSession object within the set time;
and the release module is used for releasing all ORB objects associated with the emsSession object one by one when the first judgment module judges that the user calls the endSession operation or the second judgment module judges that the user does not perform any operation through the emsSession object within the set time.
Preferably, the judging process of the second judging module includes: each emsSession object records the time when the last access occurred, periodically traverses all the existing emsSession objects,
if the time difference between the latest access occurrence and the current time is greater than the set time, indicating that the corresponding user does not perform any operation through the emsSession object within the set time;
and if the time difference between the latest access occurrence and the current time is less than or equal to the set time, indicating that the corresponding user operates the emsSession object within the set time, and judging the next emsSession object.
Preferably, the time when the latest access of the emsSession object occurred is recorded by a timer update or a login operation update.
Preferably, the user remaining dynamic ORB objects include various manager objects and various iterator objects;
the emsSession object, the manager object and the iterator object are divided into three layers from top to bottom, each iterator object belongs to a certain manager object in the previous layer, and each manager object belongs to a certain emsSession object at the topmost layer.
One of the above technical solutions has the following beneficial effects:
the invention can make EMS network management service effectively manage ORB object in memory under various conditions, and make network management service achieve the purpose of long-term stable operation.
The invention can effectively manage the ORB dynamic object in Corba-based server software development; the problems of continuous memory increase, memory leakage and program crash caused by insufficient memory due to the fact that the ORB object of the server cannot be normally recycled due to the problem of client software or the problem of network environment in the actual complex operation environment are avoided, and the requirement for long-time stable operation of telecommunication management software is met.
Drawings
FIG. 1 is a diagram illustrating an ORB object hierarchy according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. In addition, the technical features involved in the embodiments of the present invention described below may be combined with each other as long as they do not conflict with each other.
The embodiment of the invention provides a method for managing an ORB object life cycle, which comprises the following steps:
associating the user emsSession object with the other dynamic ORB objects of the user;
and when the user calls endSession operation or the user does not perform any operation through the emsSession object within the set time, releasing all ORB objects associated with the emsSession object one by one.
In the embodiment, the ORB object is used on the EMS service end side based on the TMF NML-EML interface specification, and a user can dynamically generate an ORB object after logging in. Wherein the emsSession object represents a session between the OSS and the EMS, and each user has only one emsSession object.
After the emsSession object of the user is associated with the rest dynamic ORB objects of the user, the ORB objects are defined to be owned by the emsSession object, and all the owned ORB objects can be found through the emsSession object, or vice versa.
Since an ORB object can be specified to exist for a long time (static) or exist for a short time (dynamic) at the time of creation, and a static ORB object has no problem of life cycle management, the objects involved in the present embodiment are all dynamic ORB objects.
Based on the first embodiment, the present invention further provides an embodiment for determining that the user does not perform any operation on the emsssession object within the set time, and releasing all associations of the emsssession object of the user one by one, specifically including the following steps:
s1, regularly traversing all the existing emsSession objects;
s2, judging whether the time difference between the latest access occurrence time of the emsSession object and the current time is greater than the set time, if so, entering S3; if not, the process proceeds to S1.
S3, it indicates that the corresponding user does not perform any operation through the emsssession object within the set time, and it can be considered that the session has been abnormally closed due to timeout. And carrying out the destruct of the emsSession object, further releasing all the associations with the emsSession object, and simultaneously releasing the memory variables and other resources bound with the ORB objects.
The setting time may be preset according to different situations, for example, 4 hours. The periodic traversal may set different traversal periods, such as daily, hourly, etc.; but also when the user logs in.
Preferably, in the above step, when the user invokes the endSession operation, it is not necessary to wait for timeout determination, and the emsssession object should be immediately destructed, so that all the associations of the emsssession object of the user are released one by one, and the memory variables and other resources bound to the ORB objects are also released at the same time.
In this embodiment, the time when the last access occurred is recorded by maintaining a time recording variable in the emsssession object.
Preferably, a timer is used to trigger the timeout detection. Since all operations from the OSS are completed by the ORB object, when any operation from the user occurs, the ORB object can sense the operation, and at this time, the timer of the emsssession object to which the ORB belongs needs to be updated, so as to determine whether the operation is overtime. Recording the latest access time on the emsSession object, and updating the time when all related calling operations are performed; and judging whether the time difference between the time of the latest access of the emsSession object and the current time is greater than the set time, and if so, judging that the session is overtime.
Preferably, when the user logs in, the latest access occurrence time is recorded on the emsSession object, and the user login operation is used as the update condition of the latest access occurrence.
Based on the above embodiments, an embodiment of an ORB object hierarchy relationship is provided. As shown in fig. 1, the ORB objects include three types, which are an emsssession object, various manager objects, and various iterator objects, and define three hierarchical relationships among the three types of objects, where the top layer is the emsssession object, the middle layer is the manager object, and the bottom layer is the iterator object. Each iterator object is subordinate to a manager object at the upper layer, and each manager object is subordinate to an emsSession object at the topmost layer. Each object is created by an operation on its parent object, the release of each object is taken care of by its parent object, and the release of each child object is performed when the parent object is released.
The invention also provides an ORB object life cycle management system which specifically comprises an association module, a first judgment module, a second judgment module and a release module.
And the association module is used for associating the emsSession object of the user with the rest dynamic ORB objects of the user.
The first judging module is used for judging whether a user calls an endSession operation.
And the second judgment module is used for judging whether the user does not perform any operation through the emsSession object within the set time.
And the release module is used for releasing all ORB objects associated with the emsSession object one by one when the first judgment module judges that the user calls the endSession operation or the second judgment module judges that the user does not perform any operation through the emsSession object within the set time.
The specific judgment process of the second judgment module comprises the following steps:
each emsSession object records the time when the last access occurred, and periodically traverses all the existing emsSession objects.
And if the time difference between the latest access occurrence and the current time is greater than the set time, indicating that the corresponding user does not perform any operation through the emsSession object within the set time, and releasing all ORB objects related to the emsSession object.
And if the time difference between the latest access occurrence and the current time is less than or equal to the set time, indicating that the corresponding user operates the emsSession object within the set time, and judging the next emsSession object.
Specifically, the time when the latest access of the emsSession object occurs is recorded through timer update or login operation update.
The embodiment of the invention is applied to the scene of data access through the NML-EML interface defined by TMF, and the OSS acquires the data in the EMS through the interface; the Corba interface service development method is suitable for Corba interface service development of a service end (namely an EMS end), and relates to a northbound interface service module of the EMS.
An example of a specific application scenario is provided below. The scenario of this embodiment is: a certain client side obtains historical alarm data in an EMS through a Corba interface, an EMS server needs to create iterator objects for obtaining the historical alarm data in batches in the process that a user obtains the historical alarm data, a batch of historical alarm data can be returned by calling the interface on the iterator object every time, and the returned current batch of historical alarm data is stored in the iterator object.
If the client software has defects, the iterator object created by the client software is not actively released after the Corba interface is called, so that the iterator object and the memory occupied by the alarm data on the iterator object cannot be released (namely, the memory leaks). By the ORB object life cycle management method in the embodiment, when the client closes the session through endSession operation, the emsSession object is destructed, and the server software can automatically and recursively release the iterator object created by the user, so that memory leakage is avoided, and the problem of program crash caused by insufficient memory is solved.
When the network is interrupted, the client cannot normally call the interface of the server to release the iterator object and close the emsSession. By the ORB object life cycle management method in the above embodiment, when the session timeout time is reached, for example, the timeout time is 4 hours, that is, the time difference between the occurrence time of the latest access of the emsssession object and the current time is greater than 4 hours, the server actively clears the emsssession and the iterator object to which the emsssession belongs, including the alarm data stored therein, so as to achieve the purpose of actively releasing the memory, avoid memory leakage, and avoid program crash caused by insufficient memory.
The ORB object life cycle management method mainly aims at sessions corresponding to abnormally exited emsssession objects, and normally closed clients can normally and automatically release ORB objects under the support of a Corba middleware library, but can also adopt the method in the embodiment of the invention to perform manual management under the condition that the middleware library does not support the characteristics.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The present invention is not limited to the above embodiments, and any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present invention are included in the scope of the claims of the present invention which are filed as the application.
Claims (8)
1. An ORB object lifecycle management method, comprising:
associating the emsSession object of the user with other dynamic ORB objects of the user; the dynamic ORB object comprises an emsSession object, a manager object and an iterator object, and when the ORB object senses the operation from a user, the latest access occurrence time of the emsSession object is updated;
when a user calls an endSession operation or the user does not perform any operation through an emsSession object or a dynamic ORB object associated with the emsSession object within a set time, releasing all ORB objects associated with the emsSession object one by one;
and traversing all the existing emsSession objects regularly, and when the time difference between the occurrence time of the latest visit of the emsSession object and the current time is greater than the set time, indicating that the corresponding user does not perform any operation through the emsSession object or the dynamic ORB object associated with the emsSession object within the set time.
2. The ORB object lifecycle management method of claim 1, wherein: and recording the time of the occurrence of the last access by maintaining a time recording variable in the emsSession object.
3. The ORB object lifecycle management method of claim 2, wherein: and the time record variable is maintained in a mode of updating a timer or updating a login operation.
4. The ORB object lifecycle management method of claim 1, wherein: the user's remaining dynamic ORB objects include various manager objects and various iterator objects.
5. The ORB object lifecycle management method of claim 1, wherein: the emsSession object, the manager object and the iterator object are divided into three layers from top to bottom, each iterator object belongs to a certain manager object in the previous layer, and each manager object belongs to a certain emsSession object at the topmost layer.
6. An ORB object lifecycle management system, comprising:
the correlation module is used for correlating the emsSession object of the user with other dynamic ORB objects of the user; the dynamic ORB object comprises an emsSession object, a manager object and an iterator object, and when the ORB object senses the operation from a user, the latest access occurrence time of the emsSession object is updated;
the first judgment module is used for judging whether a user calls an endSession operation;
the second judgment module is used for judging whether the user does not perform any operation through the emsSession object or the dynamic ORB object associated with the emsSession object within the set time; the release module is used for releasing all ORB objects associated with the emsSession object one by one when the first judgment module judges that the user invokes the endSession operation or the second judgment module judges that the user does not perform any operation through the emsSession object or the dynamic ORB object associated with the emsSession object within the set time;
the judgment process of the second judgment module comprises the following steps:
each emsSession object records the time when the last access occurred, periodically traverses all the existing emsSession objects,
if the time difference between the latest access occurrence and the current time is greater than the set time, indicating that the corresponding user does not perform any operation through the emsSession object or the dynamic ORB object associated with the emsSession object within the set time;
and if the time difference between the latest access occurrence and the current time is less than or equal to the set time, indicating that the corresponding user operates the emsSession object or the dynamic ORB object associated with the emsSession object within the set time, and judging the next emsSession object.
7. The ORB object lifecycle management system of claim 6, wherein: and updating and recording the time of the latest access of the emsSession object through a timer or a login operation.
8. The ORB object lifecycle management system of claim 6, wherein: the user's remaining dynamic ORB objects include various manager objects and various iterator objects;
the emsSession object, the manager object and the iterator object are divided into three layers from top to bottom, each iterator object belongs to a certain manager object in the previous layer, and each manager object belongs to a certain emsSession object at the topmost layer.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010570367.2A CN111865664B (en) | 2020-06-18 | 2020-06-18 | ORB object life cycle management method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010570367.2A CN111865664B (en) | 2020-06-18 | 2020-06-18 | ORB object life cycle management method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111865664A CN111865664A (en) | 2020-10-30 |
| CN111865664B true CN111865664B (en) | 2022-08-02 |
Family
ID=72986263
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010570367.2A Active CN111865664B (en) | 2020-06-18 | 2020-06-18 | ORB object life cycle management method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111865664B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6560609B1 (en) * | 1999-06-14 | 2003-05-06 | International Business Machines Corporation | Delegating instance management functions to underlying resource managers |
| CN1483162A (en) * | 2000-07-27 | 2004-03-17 | BEAϵͳ��˾ | System and method for request assembling and load sharing |
| CN1642106A (en) * | 2004-01-09 | 2005-07-20 | 华为技术有限公司 | Session connection resource management optimizing method |
| CN101251797A (en) * | 2008-03-31 | 2008-08-27 | 中国船舶重工集团公司第七〇九研究所 | Element real time initiative transferring method based on domain model |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7127724B2 (en) * | 1999-02-03 | 2006-10-24 | International Business Machines Corporation | Method and apparatus for providing protocol independent naming and life cycle services in an object-oriented system |
-
2020
- 2020-06-18 CN CN202010570367.2A patent/CN111865664B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6560609B1 (en) * | 1999-06-14 | 2003-05-06 | International Business Machines Corporation | Delegating instance management functions to underlying resource managers |
| CN1483162A (en) * | 2000-07-27 | 2004-03-17 | BEAϵͳ��˾ | System and method for request assembling and load sharing |
| CN1642106A (en) * | 2004-01-09 | 2005-07-20 | 华为技术有限公司 | Session connection resource management optimizing method |
| CN101251797A (en) * | 2008-03-31 | 2008-08-27 | 中国船舶重工集团公司第七〇九研究所 | Element real time initiative transferring method based on domain model |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111865664A (en) | 2020-10-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109271233B (en) | Implementation method for establishing Hadoop cluster based on Kubernetes | |
| EP1361761A1 (en) | Telecommunications network management system and method for service monitoring | |
| US20030120666A1 (en) | Real-time monitoring of service performance through the use of relational database calculation clusters | |
| US8037341B2 (en) | Determining recovery time for interdependent resources in heterogeneous computing environment | |
| US20140096129A1 (en) | Systems and methods for installing, managing, and provisioning applications | |
| CN103383689A (en) | Service process fault detection method, device and service node | |
| US10630566B1 (en) | Tightly-coupled external cluster monitoring | |
| EP1966712A2 (en) | Load balancing mechanism using resource availability profiles | |
| AU2019201687A1 (en) | Network device vulnerability prediction | |
| CN102037681A (en) | Method and apparatus for managing computing resources of management systems | |
| US10075409B2 (en) | Terminal and application synchronization method therefor | |
| WO2020063550A1 (en) | Policy decision method, apparatus and system, and storage medium, policy decision unit and cluster | |
| CN106155763A (en) | Dispatching method of virtual machine and device | |
| CN109582459A (en) | The method and device that the trustship process of application is migrated | |
| CN112416594A (en) | Micro-service distribution method, electronic equipment and computer storage medium | |
| CN109391495A (en) | Send and receive method, apparatus, computer-readable medium and the electronic equipment of heartbeat message | |
| US8949824B2 (en) | Systems and methods for installing, managing, and provisioning applications | |
| CN111865664B (en) | ORB object life cycle management method and system | |
| US20100218202A1 (en) | Method and Apparatus for Case-Based Service Composition | |
| CN109510730A (en) | Distributed system and its monitoring method, device, electronic equipment and storage medium | |
| CN107766156B (en) | Task processing method and device | |
| US20220086693A1 (en) | Packet flow description information deployment management method, device, and system | |
| KR100797548B1 (en) | Method for monitering fault and performance of database, and system for implementing the same | |
| CN110221929A (en) | A kind of service software system architecture and its application method | |
| US11259169B2 (en) | Highly scalable home subscriber server |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |