WO2006015536A1 - Procede de notification d'une operation d'enregistrement - Google Patents

Procede de notification d'une operation d'enregistrement Download PDF

Info

Publication number
WO2006015536A1
WO2006015536A1 PCT/CN2005/001212 CN2005001212W WO2006015536A1 WO 2006015536 A1 WO2006015536 A1 WO 2006015536A1 CN 2005001212 W CN2005001212 W CN 2005001212W WO 2006015536 A1 WO2006015536 A1 WO 2006015536A1
Authority
WO
WIPO (PCT)
Prior art keywords
notification
notification log
log
record
memory
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.)
Ceased
Application number
PCT/CN2005/001212
Other languages
English (en)
Chinese (zh)
Inventor
Li Yang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority claimed from CNB2004100801970A external-priority patent/CN100550762C/zh
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2006015536A1 publication Critical patent/WO2006015536A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3466—Performance evaluation by tracing or monitoring
    • G06F11/3495—Performance evaluation by tracing or monitoring for systems
    • 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/06—Management of faults, events, alarms or notifications
    • H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications

Definitions

  • the present invention relates to a log management technique, and more particularly to an implementation method for operating a notification log between a network management system and a managed network in a third generation (3G) mobile communication network through a northbound interface (Itf-N).
  • 3G third generation
  • Itf-N northbound interface
  • the system includes a network management system 11 and a managed network 12.
  • the network management system mainly includes an integration reference point (IRP) manager 13, and the managed network has two forms, and may mainly include an IRP agent (Agent) 14 and a managed network element 15, as shown in FIG. 1A;
  • the IRP agent '14 can also be placed inside the managed network element 15 as part of the managed network element, see Figure 1B.
  • the interface between the IRP manager 13 and the IRP agent 14 is the northbound interface (Itf-N).
  • the IRP proxy 14 is used to directly manage the managed network element 15, and thus may also be called a network element manager.
  • the IRP manager 13 is configured to send a management command to the IRP agent 14 and receive a report about the internal event of the network sent by the IRP agent 14, that is, a notification; the IRP agent 14 is used to directly manage the network element, and the receiving IRP manager 13 sends the message.
  • the management command returns an operation response to the IRP manager 13, and can also actively notify the IRP manager 13 when needed.
  • the managed network 12 will actively generate notifications about internal events of the managed network and save this Logging of some notifications.
  • the log volume of these notifications is called a notification log record, and each notification record contains the information content of the notification, the time of the notification log record, and the unique identifier (ID) of the notification log record.
  • the information content of the notification further includes the time of occurrence of the internal event of the network, the type of the event, the filterable domain of the notification, and other domains.
  • the filterable domain is a set of domains that can be filtered in the notification.
  • the filterable domain may include a sender or an alarm level of the notification, and the filter domain may also include an event occurrence time and an event type. Other domains are information that cannot be filtered.
  • the IRP proxy 14 needs to keep multiple notification logs, and the notification content contained in each notification message may be different.
  • the IRP agent 14 needs to report the notification log to the IRP manager 13.
  • the IRP proxy 14 may implement multiple notification logs to meet the needs of different IRP managers 13 requiring different notification logs.
  • the current 3GPP SA5 is discussing the management operations of the IRP manager 13 on the managed network notification log, including the command managed network 12: create, delete, query, suspend, resume notification log operations; The operation of notifying the notification log record in the notification is also deleted, and the IRP agent is also sent to the IRP manager to send the volume domain value alarm operation.
  • the command managed network 12 create, delete, query, suspend, resume notification log operations
  • a primary object of the present invention is to provide an implementation method of a notification log operation to meet the operational requirements of the management system for the managed network notification log.
  • An implementation method for operating a notification message which is applicable to a communication system including a management system and a managed network, wherein the method stores the notification log records of the managed network in a memory, and has respective The referrer that references the condition corresponds to a different notification log, and the managed network maps the operation for the notification log to the operation of the corresponding referencer of the memory.
  • the operation of the notification log is to create a notification log operation, and the specific process of the managed network mapping the operation to the memory processor is:
  • the managed network saves the notification log attribute in the managed network according to the creation parameter, and includes a notification log category set and a filter required in the creation parameter, and a reference device is created for the memory of the storage notification record, the reference device and the reference device
  • the notification log attribute corresponds.
  • the reference condition of the memory referencer includes at least: a notification in the notification log attribute, a log identifier, a maximum space that the notification log can occupy, a notification log record life cycle, and a notification log category set and filter required in the creation condition.
  • the operation of the notification log is to delete the notification log operation
  • the specific process of the managed network mapping the operation to the memory referrer is:
  • the operation of the notification log is to suspend the notification log operation
  • the specific process of the managed network mapping the operation to the memory processor is:
  • the notification log record logged into the memory after the suspend start time and before the suspend end time is not visible in the memory referrer.
  • the operation of the notification log is a recovery notification log operation, and the specific process of the managed network mapping the operation to the memory processor is:
  • the reference condition is such that the notification log record counted in the memory after the suspend end time is visible in the memory reference.
  • the operation of the notification log is a notification logging operation in the query notification log, and the specific process of the managed network mapping the operation to the operation of the memory referrer is:
  • the corresponding memory reference device is found according to the notification log identifier to be queried, and the notification log record in the memory that meets the reference condition of the memory reference device is used as the query result.
  • the notification log record that meets the query condition is obtained from the notification log record that meets the reference condition of the memory reference device, and the obtained result is used as the query result.
  • the query condition includes at least one of the following conditions: an identifier of the notification log record, a time of entry, an event time of notifying the content of the message, an event type, or a filterable domain of the notification information content.
  • the operation of the notification log is to delete the notification logging operation in the notification log, and the specific process of the managed network mapping the operation to the operation of the memory referrer is:
  • the corresponding memory reference device is found according to the notification log identifier of the notification log record to be deleted, and the deletion condition is superimposed in the reference condition of the memory reference device, and the log record matching the deletion condition is filtered from the memory reference device.
  • the deletion condition includes at least one of the following conditions: an identifier of the notification log record, a time of entry, an event time of notifying the content of the information, an event type, or a filterable domain of the content of the notification information.
  • the memory stores a notification log record using a database table, and the memory reference device is a database view of the database table.
  • the memory stores an alert log record in an extensible markup language XML file, and the memory referencer is a reference to the XML file.
  • the reference to the XML file is stored in an XML file, and the attributes of the notification log are stored in an XML file.
  • the operation of the notification log is a query notification log operation, and the specific process of the managed network mapping the operation to the memory I is:
  • the corresponding notification log attribute is found according to the notification log identifier to be queried, the notification log attribute is updated by the corresponding memory reference, and the updated notification log attribute is used as the query result.
  • the memory uses a database table to store a notification log record
  • the memory reference device is a database view of the database table
  • the specific process of updating the notification attribute corresponding to the memory reference device is:
  • A2 determining the running status of the notification log according to the judgment result of the management state and availability
  • A3. Update the current notification log record, the current notification log record space, the management status, and the available in the notification log attribute by using the query and judgment results of the foregoing steps a1 and a2. Sex and operational status.
  • the memory stores the notification log record in an extensible markup language XML file
  • the memory referencer is a reference to the XML file
  • the specific process of updating the notification log attribute corresponding to the memory reference device is:
  • A2. Determine the running status of the notification log according to the judgment result of the management state and availability
  • the current notification log record, the current notification log record space, the management status, the availability, and the running status in the notification message attribute are updated by using the query and judgment results of the foregoing steps A1 and A2.
  • the operation of the notification log is a record number capacity alarm operation of the notification log, and the specific process of the managed network mapping the operation to the memory reference device operation is:
  • b Querying a memory reference device corresponding to the notification log, updating a notification log attribute corresponding to the memory reference device, and finding a predefined maximum space of the notification message in the updated notification log attribute, using the pre- Define the maximum space divided by the average occupied space of the log records obtained in step a, and obtain the maximum number of log records that can be saved in the notification log; c. Query the current log record number of the notification log in the updated notification log attribute, and obtain the ratio of the current log record number to the maximum number of log records obtained in step b, and then query in the notification log attribute.
  • the record number field value of the notification log if the obtained ratio is greater than the record number field value, send a capacity alarm notification or an alarm level change notification to the network manager; if the obtained ratio is less than the predefined alarm domain value, send clear Alarm notification or alarm level change notification.
  • the operation of the notification log is a recording space capacity alarm operation of the notification log, and the specific process of the managed network mapping the operation to the operation of the memory reference device is:
  • the memory reference device corresponding to the notification log is found, the notification log attribute corresponding to the memory reference device is updated, and the current occupied space and the maximum occupied space are queried in the updated notification log attribute to obtain the current occupied space and the maximum occupied space.
  • the ratio of the record space field value of the notification log if the ratio is greater than the record space domain value, send a capacity alarm notification or an alarm level change notification to the network manager; if the obtained ratio is smaller than the predefined alarm domain value , then send a clear alarm notification or an alarm level change notification.
  • the memory uses a database table to store a notification log record
  • the memory reference device is a database view of the database table
  • the specific steps of updating the notification attribute corresponding to the database view are:
  • step B Update the current notification log record and the current notification log record occupying space in the notification log attribute corresponding to the database view according to the query result of step A.
  • the memory stores the notification log record in an extensible markup language XML file, the memory referencer is a reference to the XML file, and the specific steps of the update XML file reference corresponding notification log attribute are:
  • A obtain a reference condition from the found XML file reference;
  • B querying, in the XML file of the storage notification log record, the current notification log record that meets the reference condition according to the obtained reference condition; multiplying the current notification log record number by the average occupied space of each notification log record, Obtaining the current notification log record occupying space; using the obtained current notification log record number and the current notification log record occupying space to update the current notification log record number and the current notification log record occupying space in the notification log attribute corresponding to the XML file reference.
  • the reference device of the memory may be a database view or an XML file reference, and all the log records of the notifications involved in the notification are saved in the memory, and the memory reference device obtains the memory according to the reference condition.
  • FIG. 1 is a network management architecture diagram proposed by 3GPP SA5;
  • FIG. 2 is a block diagram of a database view implementation notification log operation according to the first embodiment of the present invention
  • FIG. 3 is a flowchart of implementing a notification log operation in an IRP proxy according to Embodiment 1 of the present invention
  • FIG. 4 is a block diagram of an operation of implementing a notification log by using an XML file reference according to Embodiment 2 of the present invention
  • FIG. 5 is a flowchart of implementing a notification log operation in an IRP proxy according to Embodiment 2 of the present invention. Mode for carrying out the invention
  • the core idea of the present invention is to store all the notified log records in the memory of the IRP agent, and use the reference device of the memory to represent the notification log, and the reference device is used to select the notification log record in the memory that meets certain conditions, and They form a collection, which is the notification log required by the IRP manager.
  • the memory referencer can be a database view for a database table or a reference to an Extensible Markup Language (XML) piece.
  • the memory referencer has a reference condition by which the IRP manager filters the log records of the notifications that do not meet the reference conditions thereof, so that only the notification log records in the memory that meet the reference conditions can be seen.
  • the set of notification log records that are seen is the notification log, and the operation of the notification log sent by the IRP manager to the IRP agent is mapped to the operation of the memory referencer.
  • the memory uses a database table to store a notification log record
  • the memory reference device is a database view of the database table, and stores all notified log records in the database table, and uses the database table
  • the view represents the notification log
  • the database view is used to reflect the notification log to the IRP manager, and the operation of the notification log sent by the IRP manager to the IRP agent is mapped to the operation of the database view.
  • the above database view is a view for a database table for storing log records, through which the IRP manager can see some or all of the contents of the notification log record table 22.
  • the set of log records that are seen is the notification log. Therefore, in the first embodiment, the database view may also be referred to as a notification log view.
  • the notification log view is used to implement the operation of the notification log in the IRP proxy.
  • a notification log operation processing process 21 a notification log record table 22, a notification log manager table 23, a notification log view manager 24, and a notification log suspension record table 25 are created in the IRP proxy. among them:
  • the notification log operation processing process 21 is configured to receive a notification log operation request from the IRP manager, determine the validity of the operation request parameter, and perform corresponding operation processing on the notification log, and return the processing result to the IRP manager.
  • the notification log operation requests from the IRP manager include: create, delete, query, suspend, resume notification log operations, and query and delete the log records in the notification log; the notification log operation processing process 21 also takes the initiative
  • the capacity domain value alarm operation is initiated, and the capacity domain value alarm is sent to the IRP manager.
  • the notification log record table 22 is a database table for storing log records of notifications, and performs operations such as adding and deleting the log records of the notifications.
  • the log records for these notifications are called notification log records, which contain the unique identifier (ID) of the log record, the time of entry for the notification log record, and the information field for the notification.
  • the information field of the notification further includes the time of occurrence of the internal event of the network, the type of the event, the filterable domain of the notification, and other domains.
  • the IRP agent issues a notification, it needs to add a notification log record to the log record table 22.
  • the current time to add the log record is the time of the notification log record.
  • the IRP agent periodically checks the time between the crediting time of each log record and the current time. When the logging time of a certain notification log record is greater than the current time, the life cycle of the notification log record specified by any one of the notifications is exceeded. The log record is deleted.
  • the notification log manager table 23 is used for recording and managing the notification log required by the IRP manager.
  • the attributes of the recorded notification log include: 1. The identifier of the notification log; 2. The notification date The creation time of the ambition, that is, the Universal Time Coordinated (UTC); 3. The notification category set, that is, the set of notification types for notifying the log record; 4.
  • the filter that is, the filtering condition of the notification log to the notification, the filtering The condition is other than the notification category, for example, the notification event time and the event type are used as the filtering conditions, and only the log records satisfying the filtering condition are recorded in the notification log; 5.
  • the log is full, that is, when The action of notifying the log when the log record fills the notification log space may be a wrap action that deletes the old notification log record, or a halt action that no longer receives the notification log record; Space, that is, the maximum storage space that the notification log can occupy; 7. The current occupied space, that is, the storage space currently occupied by the notification log; 8. The current number of log records, that is, the number of log records currently stored in the notification log; Record the life cycle, that is, notify the log record life cycle specified in the document, beyond this The log record of the life cycle will be deleted from the notification log. 10.
  • the capacity alarm field value, the capacity alarm field value can be two types, respectively: the number of records indicating the current number of records and the maximum number of records.
  • the alarm space alarm field value indicating the current occupied space and the maximum occupied space percentage.
  • only one of the two capacity alarm domain values is selected for capacity alarm judgment, when the current capacity of the notification log exceeds the capacity.
  • the alarm field value is generated, an alarm is generated.
  • the capacity alarm field value may be multiple, and each capacity alarm field value corresponds to one alarm level. 11.
  • the management status indicates whether the notification log is suspended.
  • Availability indicates whether the notification log is working properly, that is, whether the log record is full, or is not in the scheduling period; 13.
  • Running status indicating whether the log is working normally.
  • the notification log manager table 23 can also perform operation management on the notification log, for example, adding a notification log, deleting a notification message, querying a notification log attribute, calculating a maximum number of records of the log, sending a record space domain value alarm, and sending a record number field. Value alarms and other operations.
  • the notification log view manager 24 is configured to record and manage the notification log view corresponding to the notification log, for example, an operation of creating, deleting, modifying, and querying the notification log view.
  • the notification log manager table 23 and the notification log view manager 24 jointly record, manage, and operate the notification log.
  • the notification log manager table 23 and the notification may also be notified.
  • the log view manager 24 merges and only records, manages, and operates the notification log by the notification view manager 24, including: recording the attributes of the notification log, adding the notification log, deleting the notification log, querying the notification log attribute operation, and creating , delete, modify, and query the operation of the notification log view.
  • the notification log suspension record table 25 is used to suspend and resume the notification log, and records the suspension of the notification log.
  • the contents recorded include: notification status, suspend start time, and suspend end time, and the suspend end time is the recovery time of the notification log.
  • the notification log view manager 24 and the notification log suspension record table 25 may be pre-established, or may be established when the IRP proxy receives the creation notification log command request and the suspension notification command request, which may be based on the database.
  • the storage capability, access performance selection establishes one or more notification log view manager 24 and notification log suspension record table 25.
  • the notification log record table 22 is pre-established, and one or more log record tables 22 can be created according to the storage capacity of the database and the access performance selection.
  • FIG. 3 is a flowchart of implementing a notification log operation in an IRP proxy according to the first embodiment. Referring to Figure 3, the process mainly includes:
  • Step 31 The IRP proxy receives an operation request from the IRP manager for the notification log; the operation request may be a create, delete, query, suspend, and resume notification log operation, and query and delete the notification log record operation.
  • the different operation requests directly call the processing process 21 in the IRP proxy for processing.
  • the creation notification log operation request includes a creation parameter of the notification log required by the IRP manager, that is, a property of the notification log, including: a notification category set, a filter, a log full action, a maximum occupied space, and a log record life cycle. And capacity alarm field values.
  • Step 321 The processing process 21 of the IRP agent adds a notification log to the notification log manager table 23 according to the creation parameter of the notification log, and establishes a property of the newly added notification message, a notification category set in the attribute, a filter,
  • the log full action, maximum occupied space, ambiguous record life cycle, and capacity alarm field values are the same as described in the creation parameters; at the same time, the IRP agent invokes the notification log view manager 24 as the notification based on the filter in the creation parameter ⁇ Create a corresponding notification log view.
  • the reference condition of the notification log view may be a combination of the following conditions: a notification log identifier in the notification log attribute, an identifier of the notification log record, a credit time, a filter for notifying the content of the information, a suspend start time, and a suspend end time
  • the filter condition for notifying the content of the message can be: Only log records recorded in a certain period of time, log records of certain event types, or other filterable domain restrictions, through which the IRP Manager is notified You can view the log records that meet their specified criteria; there is no pending start time and pending end time in the notification log view that was just created.
  • Step 322 The IRP agent returns a response to the creation of the notification log operation to the IRP manager, including the status identifier of whether the creation is successful. If the creation is successful, the identifier of the successfully created notification log is also included.
  • the deletion notification log operation request further includes an identifier of the notification log to be deleted.
  • Step 331 the processing process 21 of the IRP proxy invokes the notification log view manager 24 and the notification log manager table 23 to perform a deletion operation, and notifies the log manager table 23 to delete the corresponding notification according to the identifier of the notification log to be deleted included in the operation request.
  • the log attribute, the notification log view manager 24 deletes the corresponding notification log view according to the identifier of the notification log.
  • the pending notification log operation request further includes an identifier of the notification log to be suspended.
  • Step 341 the processing process 21 of the IRP proxy invokes the suspend notification log operation of the notification log suspension record table 25 and the modification view operation of the notification log view manager 24, that is: Add a notification log in the notification log suspension record table 25.
  • the notification flag is the notification log identifier in the operation request
  • the suspension start time is the current time of the operation
  • the suspension end time is "forever"
  • the notification log view manager 24 is in accordance with the operation request.
  • the notification log identifier modifies the reference condition of the corresponding view, that is, adds a filter condition, which is: After the suspension start time, before the suspension end time, the notification log in the new entry notification log record table 22 is recorded in the notification log view. Not visible in the middle.
  • the notification view manager 24 does not modify the reference condition of the view, notifies the log suspension record table 25 that the corresponding notification is not modified.
  • Step 342 The IRP agent returns a suspension notification log operation response to the IRP manager, where the response includes a status identifier of whether the suspension is successful, and if the suspension is successful, the identifier of the notification log that is successfully suspended is also included.
  • the recovery notification log operation request further includes an identifier of the notification log to be restored.
  • Step 351 the processing process 21 of the IRP proxy invokes the recovery notification log operation of the notification log suspension record table 25 and the modified view operation of the notification log view manager 24, namely:
  • the alert suspension record table 25 finds the corresponding notification log suspension record according to the notification log identifier in the operation request, and modifies the suspension end time therein to the current time; the notification log view manager 24 identifies the notification log according to the operation request. Modify the reference condition of the corresponding view so that the log records recorded in the notification log record table 22 can appear in the view.
  • the notification log view manager 24 does not modify the reference condition of the view, and notifies the log suspension record table 25 that the corresponding notification log suspension record is not modified.
  • Step 352 The IRP agent returns a recovery notification log response to the IRP manager, where the response includes a status identifier of whether the recovery is successful, and if successful, an identifier of the notification log that is successfully restored.
  • the query notification log operation request includes an identifier of the notification log to be queried.
  • step 361 and step 362 are performed;
  • Step 361 the processing process 21 of the IRP proxy invokes the notification log manager table 23 to perform a query operation, and notifies the log manager table 23 according to
  • the identifier of the notification log in the operation request obtains the corresponding notification log view, and the corresponding notification log attribute is updated by the notification log view:
  • the current notification log record number is queried in the database view corresponding to the notification log identifier, and the current notification log record is calculated.
  • the calculation process is as follows: Query the occupied space of the notification log record table and the total number of records.
  • the management status of the notification log is judged according to the last notification log suspension record, for example: If the last notification log suspension record suspends the start time before the current time, and the suspension ends When the time is infinite, the management state is suspended. Then, according to the current notification log, whether the occupied space reaches the maximum occupied space, the availability of the notification log is judged, and if the maximum occupied space is reached, it is unavailable, and if it is not reached, it is available; then the running of the notification log is judged according to the management status and availability.
  • the notification log is at If the status is suspended or unavailable, the running status is abnormal (Disabled), otherwise the running status is Enabled. Finally, the current log record, current occupied space, and management status in the notification log attribute are updated according to the above query and judgment result. , availability and operational status.
  • Step 362 The IRP proxy returns the updated query log attribute as a query result, and returns a query operation response to the IRP manager, where the response includes a status identifier of whether the query is successful, and if the query is successful, the notification is successfully queried.
  • the properties of the log are the following properties:
  • the processing process 21 of the IRP agent invokes the notification log view manager 24 according to the notification log in the operation request.
  • the identifier obtains the view corresponding to the notification log, and then updates the corresponding notification log attribute through the notification log view, and finally returns the notification log attribute of the query.
  • the operation request of the notification log record in the query notification log includes the notification log identifier to be queried.
  • the operation request may further include a query condition, which may be regarded as another reference condition superimposed on the notification log reference, for example, the query condition may be a combination of the following conditions: an identifier of the notification log record, Time, the event time of the information content, the event type, or other filterable domain of the notification information content; in addition, the operation request may further include a return form of the query result required by the IRP manager, and the return form is an XML file format.
  • step 371 and step 372 are performed;
  • Step 371 the processing process 21 of the IRP proxy invokes the notification log view manager 24 to perform the query notification logging operation, that is, the notification log view manager 24 finds the corresponding notification log view according to the notification log identifier in the operation request, where In the notification log view, query the notification log records that meet the specified query conditions; if the IRP manager requests to return the query results in an XML document manner, the query log recordsets that are queried are combined into one.
  • the XML document is stored in the IRP proxy.
  • IRP Manager Request The log record with the event time of 02: 00 in the notification log with ID 1 is the log record with the event time of 02: 00.
  • the IRP agent finds the notification log corresponding to the notification log with the ID of 1, and then finds all the log records with the event time of 02: 00 in the notification log view.
  • Step 372 The IRP agent returns a response recorded in the query notification log to the IRP manager, where the response includes a status identifier of whether the query is successful, and if successful, the notified notification log identifier and the query result. If the IRP manager requests to return the query result in an XML document manner, the XML document composed of the notified notification log record set is returned to the IRP manager in the storage location of the IRP proxy, if the IRP manager does not require XML The document mode returns the query result, and returns the queried notification record set to the IRP manager.
  • the operation request of the notification log record in the deletion notification log includes a notification log identifier and a deletion condition
  • the deletion condition may be a combination of the following conditions: an identifier of the notification log record, a credit time, an event time of the notification information content, and an event type. , or notify other filterable fields of the message content.
  • step 381 and step 382 are performed;
  • Step 381 the processing process 21 of the IRP agent invokes the notification log view manager 24 to perform the log record in the deletion notification log, that is, the notification log view manager 24 searches for the corresponding notification log view according to the notification log identifier in the operation request, and
  • the reference condition of the notification view is modified, that is, the filtering condition corresponding to the deletion condition is superimposed, so that the IRP manager does not see the log record that meets the deletion condition from the notification log view, and the log is deleted from the notification message.
  • the filtered logs are recorded in the notification log record It still exists in Table 22, so other notification log views can still take advantage of this log record.
  • Step 382 The IRP agent returns an operation response to the IRP manager, where the response includes a status identifier for deleting whether the record is successful, and if successful, the notification log identifier of the notification log record is successfully deleted.
  • the IRP Manager requests: The notification log record with an event time of 02: 00 in the notification log with ID 1 is deleted.
  • the IRP agent finds the notification log view corresponding to the notification log with the ID of 1.
  • the filter in the notification log view is modified, that is, a filter condition is superimposed:
  • the time of all events in the notification log view is 02:
  • the notification log of 00 is filtered out.
  • the IRP agent will permanently delete the notification log record from the log record table 22, and thereafter, from any one of the notifications This notification log record is not visible in the log view.
  • the above is the flow of the IRP agent operating the notification log based on the received operation request.
  • the IRP agent also actively performs a capacity alarm operation on a notification log.
  • the capacity alarm operation can be performed in two ways: recording the number capacity alarm operation and recording the space capacity alarm operation. In the actual implementation process, only one of the operations is selected. If the recording capacity alarm operation is performed, go to step 391; if the recording space capacity alarm operation is performed, go to step 394.
  • Step 391 the processing process 21 of the IRP agent invokes the notification log record table 22 to find the number of log records in the log record table 22 and its occupied space, and divides the occupied space by the number of records, to obtain an average of each log record. Average occupied space;
  • Step 392 the processing process 21 of the IRP proxy invokes the notification log manager table 23 According to the notification log identifier included in the operation request, the corresponding notification log view is found, and the corresponding notification log attribute is updated by the notification log view, which mainly includes updating the current log record number, current occupied space, availability, and running status;
  • the predefined maximum space in the notification log attribute is obtained by dividing the predefined maximum space by the average occupied space of the log obtained in step 391, and obtaining the maximum number of log records that the notification log can save;
  • the method for searching for the notification log attribute corresponding to the notification log identifier included in the operation request may be: IRP proxy
  • the processing process 21 first calls the notification message view manager 24 to find the corresponding notification log view, and then finds the corresponding notification log attribute.
  • Step 393 The notification log manager table 23 queries the current log record number of the notification log, and obtains the ratio of the current log record number to the maximum log record number obtained in step 392, and then requests the log manager table 23 to query the notification log. The number of capacity alarm field values is recorded. If the obtained ratio exceeds the record number capacity alarm field value, a capacity alarm notification is sent to the IRP manager.
  • step 393 the obtained ratio is compared with the domain value of each level, if the ratio exceeds the record capacity of an alarm level. If the alarm domain value is sent, the ITP manager sends a notification of the corresponding level of the alarm. If the alarm notifications of different levels have been sent, the alarm level modification notification is sent. If the ratio falls below the lowest level of the recordable capacity alarm field value, a clear alert is sent.
  • the above capacity alarm operation may be performed periodically, or may be triggered by the Nth record adding operation of the notification log record manager, where N is a natural number.
  • Step 394 the processing process 21 of the IRP agent invokes the notification log manager table 23 to perform the following operations: according to the notification log identifier included in the operation request, the notification log corresponding to the query
  • the method for updating the corresponding notification log attribute by using the notification log view which mainly includes updating the current log record number, calculating and updating the current occupied space, availability, and running status, and calculating the current occupied space is the same as the method described in step 361.
  • the current occupied space and the maximum occupied space in the notification log attribute are queried, the ratio of the current occupied space to the maximum occupied space is obtained, and then the recording space capacity alarm field value of the notification log is queried, if When the ratio exceeds the recording space capacity alarm domain value, a capacity alarm notification is sent to the IRP manager.
  • the method for searching for the notification log attribute corresponding to the notification log identifier included in the operation request may be: IRP proxy
  • the processing process 21 first calls the notification log view manager 24 to find the corresponding notification log view, and then finds the corresponding notification log attribute.
  • step 394 the obtained ratio is compared with the domain value of each level, if the ratio exceeds the recording space capacity of an alarm level. If the alarm domain value is sent, the ITP manager sends a notification of the corresponding level of the alarm. If the alarm notifications of different levels have been sent, the alarm level modification notification is sent. If the ratio falls below the lowest level of the record space capacity alarm field value, a clear alarm is sent.
  • the above capacity alarm operation may be performed periodically, or may be triggered by the Nth record adding operation of the notification log record manager, where N is a natural number.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the memory stores an notification log record by using an Extensible Markup Language (XML) file, where the memory reference device is a reference to the XML file, and all the notified records are stored in the IRP proxy.
  • XML Extensible Markup Language
  • the reference to the XML file represents the notification log, and the operation of the notification log by the IRP agent is mapped to The operation referenced by the XML file.
  • the reference conditions for the XML file reference include the notification log "notification category set” and “filter” attributes required by the IRP manager, and the IRP manager filters out the log records of notifications that do not meet the reference condition, so only the view can be seen.
  • the log record content in the XML file that meets the reference condition, and the set of log records seen is the notification log. Therefore, in the present invention, the XML file reference may also be referred to as a notification log reference.
  • the reference condition of the XML file reference is stored in another XML file, and each XML file is referenced as an element storing the reference condition XML file.
  • a notification log record XML file which is used to store a log record of the notification, in which the log record of each notification is expressed as A notification log record element.
  • the current time to add the notification log record is the time of the notification log record.
  • the IRP agent periodically checks the time interval between the entry time and the current time of each log record. When the log time of a notification log record is greater than the current time, the lifetime of the notification log record specified by any notification log. , the log record is removed from the notification log record XML file.
  • the notification log attribute XML file used to store the notification log attribute, in which the attribute of each notification log is represented as a notification log attribute element.
  • the notification log refers to an XML file, and is used to store a reference condition of the notification log reference, that is, an XML file reference corresponding to the notification log.
  • a reference condition of the notification log reference that is, an XML file reference corresponding to the notification log.
  • each element identifies a reference condition corresponding to the notification log.
  • the record contained in the corresponding notification log can be seen in the notification log record XML file.
  • This embodiment utilizes the notification log to reference the notification log reference in the XML file to implement the operation of the notification log in the IRP proxy.
  • the notification log suspends the record XML file, and is used for storing the suspend record of the notification log.
  • the content of the suspend record includes: a notification log identifier, a suspend start time, and a suspend end time, and the suspend end time is a notification.
  • the recovery time of the log In the XML file, each notification log pending record is represented as a notification log.
  • the notification log operation processing process 41, the notification log record manager 42, the notification log manager 43, the notification log reference manager 44, and the notification are created in the IRP agent.
  • the notification log operation processing process 41 is configured to receive a notification log operation request from the IRP manager, determine the validity of the operation request parameter, and perform corresponding operation processing on the notification log, and return the processing result to the IRP manager.
  • the notification log operation requests from the IRP manager include: create, delete, query, suspend, resume notification, and query, delete the notification log record in the notification log; in addition, notify the log operation process 41 will also send a volume domain value alert to the IRP manager.
  • the notification log record manager 42 is configured to manage the notification log record XML file, add, delete or read the notification log record in the notification log record XML file as needed, and record the XML file according to the notification log.
  • the current number of records and the current footprint calculate the average space per log record.
  • the notification log manager 43 is configured to manage the notification log attribute XML file, and may add a notification log, a deletion notification log, a query notification log attribute, a maximum number of records of the calculation log, and a transmission record in the notification log attribute XML file as needed.
  • the notification log reference manager 44 is configured to manage the notification log reference XML file, and may create and delete a notification in the notification log reference XML file as needed. References, can modify or query the reference conditions of the notification log reference.
  • the notification log manager 43 and the notification log reference manager 44 respectively manage the notification log attribute XML file and the notification log reference XML file to jointly record, manage, and operate the notification log, and the present invention
  • the notification log XML attribute file and the notification log reference XML file may also be merged, and the notification log manager 43 and the notification log reference manager 44 are merged, and only the notification log reference manager 44 operates on the notification log attribute and the reference XML file.
  • And recording, managing, and operating the notification log including: recording the properties of the notification log, adding the notification log attribute, deleting the notification log attribute, querying the notification log attribute, calculating the maximum number of records of the log, sending the record space field value alarm, Send record number field value alarm, update notification log current record number and update notification log current record space operation, and create notification log reference, delete notification log reference, modify reference condition of notification log reference, and obtain reference condition of notification log reference Wait for the operation.
  • the notification log suspension manager 45 is used to suspend and resume the notification log, and records the suspension of the notification log in the notification log pending record XML file.
  • the contents recorded include: notification log identifier, suspend start time, and suspend end time, which is the recovery time of the notification log.
  • the above notification log reference manager 44 and the notification log suspension manager 45 may be pre-established, or may be established when the IRP proxy receives the create notification log command request and the suspend notification command request.
  • the present invention can also establish one or more notification log record XML files according to the storage capacity of the XML file, access performance, and notify the log to use the XML file and the notification log to suspend the record XML file.
  • FIG. 5 is a flowchart of implementing a notification log operation in an IRP proxy according to the embodiment. Referring to Figure 5, the process mainly includes:
  • Step 51 The IRP agent receives the operation of the notification from the IRP manager. Request, and process according to the category of the operation request;
  • the operation requests may be creation, deletion, query, suspend, and resume notification log operations, and query and delete notification log recording operations in the notification log.
  • step 521 and step 522 are performed;
  • Step 521 The processing process 41 of the IRP proxy invokes the add notification log operation of the notification log manager 43 according to the creation parameter of the notification log to add a notification log attribute element in the notification log attribute XML file, and the notification category in the notification log attribute
  • the collection, filter, log full action, maximum footprint, logging lifecycle, and capacity alarm field values are the same as described in Creating Parameters; meanwhile, the IRP proxy invokes the notification log reference manager 44 based on the notification category in the creation parameters.
  • the collection and filter create a corresponding notification log reference for the notification log in the notification log reference XML file.
  • the notification reference includes a notification log identifier and a reference condition in the notification log attribute, and the reference condition may be a combination of the following conditions: an identifier of the notification log record, a credit time, a filter for notifying the content of the information, a suspension start time And suspend the end time.
  • the filter condition for notifying the content of the information may be: only requiring logging of a certain period of time, logging of certain event types, or other restrictions of the filterable domain, by which the IRP manager can View to the log record specified by the creation parameter; the suspension start time and the suspension end time are not included in the notification log reference just created.
  • Step 522 The IRP agent returns a response to the creation of the notification log operation to the IRP manager, including the status identifier of whether the creation is successful. If the creation is successful, the identifier of the successfully created notification log is also included.
  • step 531 and step 532 are performed;
  • Step 531 the processing process 41 of the IRP proxy invokes the notification log reference manager 44.
  • the notification log manager 43 performs a deletion operation, and the notification log manager 43 deletes the corresponding notification log attribute in the notification log attribute XML file according to the identifier of the desired deletion notification log included in the operation request, and notifies the log reference manager 44 according to the notification.
  • the identifier of the log deletes the corresponding notification log reference in the notification log reference XML file.
  • Step 532 The IRP agent returns a deletion notification log operation response to the IRP manager, where the response includes a status identifier of whether the deletion is successful. If the deletion is successful, the identifier of the successfully deleted notification log is further included.
  • step 541 and step 542 are performed;
  • Step 541 the processing process 41 of the IRP proxy invokes the suspend notification log operation of the notification log suspension manager 45 and the modification reference operation of the notification log reference manager 44, that is, the notification log suspension manager 45 suspends in the notification log.
  • Add a notification ⁇ hang record in the record XML file where the notification log identifier is the notification log identifier in the operation request, the hang start time is the current time of the operation, and the hang end time is "forever"; the notification log reference
  • the manager 44 finds the corresponding notification log reference in the notification log reference XML file according to the notification log identifier in the operation request, and modifies the reference condition of the notification log reference, that is, adds a filtering condition, the content is: after the suspension start time Before the end time is suspended, the notification log record in the new log notification XML file is not visible in the notification log reference.
  • the notification log reference manager 44 does not modify the referenced reference condition, and notifies the log suspension manager 45 that the notification log hangs the corresponding notification log in the XML file. to modify.
  • Step 542 The IRP agent returns a suspension notification log operation response to the IRP manager, where the response includes a status identifier indicating whether the suspension is successful, and if the suspension is successful, the identifier of the notification log that is successfully suspended is further included.
  • the IRP proxy receives the recovery notification log operation request, then steps 551 and 552 are performed;
  • Step 551 the processing process 41 of the IRP agent invokes the recovery notification log operation of the notification log suspension manager 45 and the modification reference condition operation of the notification log reference manager 44, that is, the log suspension manager 45 according to the notification in the operation request
  • the log identifier finds a corresponding notification log suspension record from the notification log suspension record XML file, and modifies the suspension end time therein to the current time; the notification log reference manager 44 identifies the slave notification log according to the notification in the operation request.
  • the corresponding notification log reference is found in the reference XML file, and the reference condition of the notification log reference is modified, so that after the operation, the log record recorded in the notification log record XML file can appear in the notification log.
  • the notification log reference manager 44 does not modify the reference condition of the corresponding notification log reference, and notifies the log suspension record table 45 that the corresponding notification log suspension record is not changed.
  • Step 552 The IRP agent returns a recovery notification log response to the IRP manager, where the response includes a status identifier of whether the recovery is successful, and if successful, an identifier of the notification log that is successfully restored.
  • step 561 to step 567 are performed;
  • Step 561 the processing process 41 of the IRP proxy invokes the notification log manager 43 to operate, that is: the notification log manager 43 first requests the notification log reference manager 44 to look up the notification log reference XML file according to the notification log identifier in the operation request. Corresponding notification log reference, obtaining the reference condition of the notification log;
  • Step 562 Query, according to the obtained reference condition, the number of current notification log records that meet the reference condition in the notification log record XML file, that is, read the notification log that meets the reference condition in the notification log record XML file, and specify that the output result format is "output record number";
  • Step 563 The notified logging manager 42 queries the number of the records in the notification log record XML file and the occupied space thereof, and divides the occupied space by the number of log records to obtain an average occupied space of each log record;
  • Step 564 Multiply the obtained current notification log record number by the average occupied space of each log record, and obtain the current occupied space of the notification log.
  • Step 565 Determine the management status of the notification log according to the last notification log suspension record, for example: If the suspension start time of the latest notification log suspension record is before the current time, and the suspension end time is infinitely long, Then, the management state is a suspended state; then, according to the current notification log, whether the occupied space reaches the maximum occupied space, the availability of the notification log is determined, and if the maximum occupied space is reached, it is unavailable, and if it is not reached, it is available; then, according to the management state and availability The running status of the notification log. If the notification log is in a suspended state or is unavailable, the running state is abnormal, otherwise the running state is normal.
  • Step 566 Search for the corresponding information from the notification log attribute XML file according to the notification log identifier in the operation request.
  • the notification log attribute according to the above query calculation and judgment result update notification log attribute, the current log record, the current occupied space, the management status, the availability and the running status.
  • Step 567 The attribute of the updated notification log is used as a query result, and the query operation response is returned to the IRP manager, where the response includes a status identifier of whether the query is successful, and if the query is successful, the query result is also included.
  • the IRP agent processing process 41 only calls the notification log reference manager. 44 performs a query operation, that is, firstly, according to the identifier of the notification log in the operation request, the reference condition of the corresponding notification log is found in the reference XML file, and then the current record number and current possession of the corresponding notification attribute are updated according to the reference condition. Space, and then get the properties of the notification log.
  • step 571 and step 572 are performed;
  • Step 571 the processing process 41 of the IRP proxy invokes the notification log reference manager 44 to perform the query notification logging operation, that is, the notification log reference manager 44 finds the corresponding information from the notification log reference XML file according to the notification log identifier in the operation request.
  • the notification message is referenced, and the reference condition of the notification log reference is obtained, and the reference condition is transmitted to the notification log record manager 42 to notify the log record manager 42 to find out from the notification log record XML file according to the reference condition.
  • the notification log record of the condition is referenced, and the found notification log records are collected into an XML file and stored in the IRP proxy.
  • the operation request of the notification log record in the query notification log further includes the query condition
  • the notification that meets the reference condition and the query condition is read from the notification log record XML file.
  • Log records, and the found notification records are collected into an XML file and stored in the IRP proxy.
  • IRP Manager Request The log record with the event time of 02: 00 in the notification log with ID 1 is the log record with the event time of 02: 00.
  • the IRP agent finds the notification reference corresponding to the notification log with the identifier 1 and obtains the reference condition. Then, in the notification log record XML file, all the notifications that meet the reference condition and the event time is 02: 00 are found. Logging.
  • Step 572 The IRP agent returns a query response to the IRP manager, where the response includes a status identifier of whether the query is successful, and if successful, further includes a query log identifier that is queried and a storage location of the XML file that records the query result. .
  • the IRP manager can find the XML file based on the storage location.
  • step 581 and step 582 are performed;
  • Step 581 the processing process 41 of the IRP proxy invokes the notification log reference manager 44.
  • the notification log record operation is performed in the deletion notification log, that is, the notification log reference manager 44 searches for the corresponding notification log reference in the notification log reference XML file according to the notification log identifier in the operation request, and modifies the reference condition of the notification log reference. That is, the deletion condition is superimposed in the reference condition, so that the IRP manager does not see the notification log record that meets the deletion condition from the notification log reference, and the effect of deleting the log record from the notification log is reached.
  • the filtered log records still exist in the notification log record XML file, so other notification log references can still obtain the notification log record.
  • Step 582 The IRP agent returns an operation response to the IRP manager, where the response includes a status identifier indicating whether the record is successfully deleted, and if successful, the notification log identifier that has been successfully deleted by the notification log.
  • the IRP Manager requests: Delete the log record with an event time of 02: 00 in the notification log with ID 1.
  • the IRP agent finds the notification log reference corresponding to the notification log with the identifier 1 and modifies the reference condition in the notification log reference, that is, adds a filtering condition: The time of all events in the notification log reference is 02: The notification log of 00 is filtered out.
  • the notification log record in the XML file that all events with an event time of 02: 00 is invisible in the notification log reference. Therefore, the notification log that the IRP manager sees through the notification log reference no longer has the notification log record that it requests to delete.
  • the IRP agent will permanently delete the notification log record from the notification log record XML file, after that, from any one The notification date is not visible in the notification log reference, 3 ⁇ 4 ⁇ .
  • the IRP agent also sends a record number capacity alarm notification or a record space capacity alarm notification to a certain notification log: If the record number capacity alarm operation is performed, step 591 is performed; if the record space capacity alarm operation is performed, step 594 is performed.
  • the procedural process of the IRP agent is used to update the attribute of the notification log corresponding to the notification log identifier included in the operation request, and the specific process is the same as that described in steps 561 to 566. Querying the predefined maximum space in the notification log attribute, and dividing the predefined maximum space by the average occupied space of the log record obtained in step 591, and obtaining the maximum number of log records that can be saved in the notification log;
  • the notification log reference manager 44 searches for the notification log corresponding to the notification log identifier included in the operation request.
  • the method of the attribute may be: the processing process of the IRP agent 41 first calls the notification log reference manager 44 to find the corresponding notification log reference in the notification attribute and the reference XML file, and then finds the notification log corresponding to the notification log reference. Attributes.
  • Step 593 The notification log manager 43 queries the notification log attribute XML file for the current log record number in the updated notification log attribute, and obtains the ratio of the current log record number to the maximum log record number obtained in step 592, and then requests The notification log manager 43 queries the record number capacity alarm field value in the notification log attribute, and if the obtained ratio exceeds the record number capacity alarm field value, sends a capacity alarm notification to the IRP manager.
  • the number of recordable capacity alarm field values may be multiple, and there are grades.
  • the obtained ratio is compared with the domain value of each level. If the ratio exceeds the record number capacity alarm of an alarm level If the domain value is used, the ITP manager sends a notification of the corresponding level of the alarm. If the alarm notification of different levels has been sent, the notification of the alarm level modification is sent. When the ratio falls below the lowest level of the record number capacity alarm field value, a clear alarm is sent.
  • the foregoing capacity alarm operation may be performed periodically, or may be triggered by the Nth record adding operation of the notification logging manager, where the N is a natural number.
  • Step 594 the processing process 41 of the IRP agent invokes the notification log manager 43 to: update the attribute of the notification log corresponding to the notification log identifier included in the operation request, and the specific process is the same as described in steps 561 to 566. And querying the current occupied space and the maximum occupied space in the updated notification log attribute, obtaining the ratio of the current occupied space to the maximum occupied space, and then querying the record space capacity alarm field value of the notification log, if the ratio is crossed The recording space capacity alarm domain value sends a capacity alarm notification to the IRP manager.
  • this step searches for a method of notifying the notification log attribute corresponding to the notification log identifier included in the operation request.
  • the processing process 41 of the IRP agent first calls the notification log reference manager 44 to find a corresponding notification log reference in the notification log attribute and the reference XML file, and then finds the notification log attribute corresponding to the notification log reference.
  • the recording space capacity alarm field value may be multiple, and there is a level.
  • the obtained ratio is compared with the domain value of each level. If the ratio exceeds the alarm space capacity alarm of a certain alarm level. If the domain value is used, the ITP manager sends a notification of the corresponding level of the alarm. If the alarm notification of different levels has been sent, the notification of the alarm level modification is sent. If the ratio falls below the lowest level of the record space capacity alarm field value, a clear alarm is sent.
  • the above capacity alarm operation may be performed periodically, or may be triggered by the Nth record adding operation of the notification log record manager, where N is a natural number.
  • Both the first embodiment and the second embodiment adopt a memory referencer to represent the notification log, and the operation of the notification log is mapped to the operation of the memory referencer.

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un procédé de notification d'une opération d'enregistrement utilisée pour permettre à un système de gestion de gérer les enregistrements de notification du réseau géré dans le réseau de communication. Ce procédé consiste à stocker en mémoire les enregistrements de notification du réseau géré, à utiliser les indicateurs qui correspondent à la mémoire et qui contiennent des termes particuliers pour représenter différents enregistrements de notification, après quoi le réseau géré mappe l'opération d'enregistrement de notification en tant qu'opération à indicateur correspondante de ladite mémoire. Ce procédé peut permettre de répondre aux besoins d'un système de gestion pour gérer les enregistrements de notification du réseau géré.
PCT/CN2005/001212 2004-08-08 2005-08-08 Procede de notification d'une operation d'enregistrement Ceased WO2006015536A1 (fr)

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
CN200410055485 2004-08-08
CN200410055486 2004-08-08
CN200410055486.5 2004-08-08
CN200410055485.0 2004-08-08
CN200410080197.0 2004-09-24
CNB2004100801970A CN100550762C (zh) 2004-08-08 2004-09-24 一种对通知日志进行操作的实现方法

Publications (1)

Publication Number Publication Date
WO2006015536A1 true WO2006015536A1 (fr) 2006-02-16

Family

ID=35839133

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2005/001212 Ceased WO2006015536A1 (fr) 2004-08-08 2005-08-08 Procede de notification d'une operation d'enregistrement

Country Status (1)

Country Link
WO (1) WO2006015536A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110750253A (zh) * 2019-10-28 2020-02-04 深圳前海环融联易信息科技服务有限公司 日志规范方法、装置、计算机设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5940830A (en) * 1996-09-05 1999-08-17 Fujitsu Limited Distributed document management system
WO2002082276A1 (fr) * 2001-04-09 2002-10-17 Computer Associates Think, Inc. Systeme et procede de reorganisation de donnees stockees
WO2003025801A1 (fr) * 2001-09-21 2003-03-27 Polyserve, Inc. Système et procédé de mise en oeuvre de la journalisation dans un environnement multi-noeud

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5940830A (en) * 1996-09-05 1999-08-17 Fujitsu Limited Distributed document management system
WO2002082276A1 (fr) * 2001-04-09 2002-10-17 Computer Associates Think, Inc. Systeme et procede de reorganisation de donnees stockees
WO2003025801A1 (fr) * 2001-09-21 2003-03-27 Polyserve, Inc. Système et procédé de mise en oeuvre de la journalisation dans un environnement multi-noeud

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110750253A (zh) * 2019-10-28 2020-02-04 深圳前海环融联易信息科技服务有限公司 日志规范方法、装置、计算机设备及存储介质

Similar Documents

Publication Publication Date Title
US10212055B2 (en) System and method for dynamically grouping devices based on present device conditions
JP5585062B2 (ja) 情報処理装置、情報処理方法、データ管理サーバおよびデータ同期システム
KR101336512B1 (ko) 분산 관리 모니터링 시스템 및 그 모니터링 방법, 구축 방법
US7818287B2 (en) Storage management system and method and program
JP3812236B2 (ja) イベント制御手段を備えたネットワーク管理システム
CN102118276A (zh) 提供性能告警服务的方法和装置
WO2010072083A1 (fr) Système de base de données fondé sur des applications web et méthode associée de gestion des données
CN101990256A (zh) 长连接管理装置及长连接通讯的链路资源管理方法
CN101710901A (zh) 一种具有p2p功能的分布式存储系统和方法
CN111782666B (zh) 一种缓存服务系统
JP2023530996A (ja) クラスタの容量縮小・拡張方法及びシステム、容量縮小・拡張制御端末、及び媒体
CN102694824B (zh) 一种用户数据存储系统及其数据访问方法
CN101247271A (zh) 性能数据的存储方法和装置
CN114900449B (zh) 一种资源信息管理方法、系统及装置
CN103036948A (zh) 网络文件处理方法、执行节点、软件即服务SaaS平台
CN113609460B (zh) 一种基于用户权限的页面加载方法及系统
CN114327849B (zh) 一种基于智能监控的资源调度方法
EP1929705B1 (fr) Procede de gestion de dispositif utilisant des noeuds a attribut additionnel et client de gestion de dispositif associe
JP2005250521A (ja) データ処理システム及びデータ処理装置及びデータ処理方法
CN101383733B (zh) 一种监测呼叫时网络状态的方法及装置
CN116846729A (zh) 一种基于云容器下多租户模式管理监控告警通知的方法
CN116483890A (zh) 数据处理方法、装置、电子设备、介质和程序产品
CN100550762C (zh) 一种对通知日志进行操作的实现方法
CN118245235B (zh) 多云平台运维方法
CN101141295A (zh) 策略管理方法

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase