KR970002709B1 - Service time detection method using time tick counter - Google Patents

Abstract

A service time detecting method using the time tick counter where has the function that records the number of time tick, that is generated after the prescribed time in the switching system. The said method detects the service time between the start point and the end point of the service through the number of time tick.

Description

Service time detection method using time tick counter

1 is a schematic structural block diagram of an ATM switch.

2 is a control flow chart for determining a reference time when restarting the operation maintenance processor.

3 is a control flow diagram for determining a reference time when starting and restarting processors other than the operation maintenance processor.

4 is a control flowchart for detecting a service time according to the present invention.

* Explanation of symbols for main parts of the drawings

100 ATM central switching subsystem 101 interconnection switching network module

102: operation maintenance processor 103: network synchronization control processor

104: broadcast call processing processor 105: central access module maintenance processor

106: remote sensor, matching processor 107: service control processor

108: number translation processor 109: magnetic tape

110: disk 111: console

150: ATM subscriber switching subsystem 151: subscriber switching network module

152: subscriber call processing processor 153: relay line call processing processor

154: broadcast call processing processor 155: subscriber exchange module maintenance processor,

156: number translation processor 157: signal processor

The present invention relates to a method for detecting a service time using a time tick counter, and in particular, adds a function to record the number of time ticks occurring after a specific time in an exchange system, and provides a service through the number of time ticks. The present invention relates to a service time detection method using a time tick counter that detects a service time between a start point and an end point, thereby ensuring time integrity and enabling reliable time management.

In general, the operation of time within an exchange system not only has a significant effect on the calculation of charges for use time, discounts on holidays, statistical functions, etc., but also periodic monitoring and real-time recovery functions provide the absolute support of time during operation. in need.

Conventionally, in order to calculate the service time, the current time is read from the operating system at the start of the service, and the current time is read from the operating system at the end of the service.

However, when a subscriber is receiving a service, it may be necessary to reschedule the processor due to a combination of hardware or an error in software. In the past, when a system needs to be rescheduled during service as described above, The service time can be increased or decreased by the difference between the previous time and the changed time. For example, if the specified time is earlier than the previous system time, the service time will be shorter than the original service time, and if the respecified time is later than the previous system time, it will be longer than the original service time. It may even be detected as a negative value if the respecified time is earlier than the current service time.

Therefore, the conventional service time detection method as described above has a problem in that it is impossible to guarantee or recover the integrity of time because the relative time is received from the operating system.

Accordingly, the present invention has been made to solve the above problems, and adds a function that can record the number of time ticks occurring after a specific time in the exchange system and the service between the service start point and the end point through the number of time ticks. It is an object of the present invention to provide a service time detection method using a time tick counter for detecting time.

In order to achieve the above object, the present invention relates to a first step of designating various hardware variables and software variables capable of preserving time ticks, and to specifying the hardware variables and software variables in the step, the current system time. A second step of reading and storing the data as a service start time; and if the service start time is stored in the step, a third step of increasing and recording the time tick until the service is terminated, and storing the service when the service is terminated while performing the step. And a fourth step of detecting a service time by using the set service start time and the number of time ticks.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

FIG. 1 shows the configuration of a general ATM switch. The ATM switch is composed of an ATM Switching Subsystem (ACS) 100 and an ATM Local Switching Subsystem (ALS) 150. The subsystems (ACS, ALS) 100 and 150 may include an interconnection switching network module (ISNM) 101 and an access switching network module (ASNM) 151, which are in charge of each function. Has

In addition, the ATM Central Exchange Subsystem (ACS) 100 includes an operation maintenance processor (OMP) 102 for operation, maintenance, and user interaction of the system, and a synchronizer control processor that performs network synchronization. Network Synchronization Control Processor (NSCP) 103, Broadcasting Call Processor (BCP) 104, which controls the overall multiple access function of the signal processing process, and ATM Central Switching Subsystem (ACS) 100 A Central Interconnection Maintenance Processor (CIMP) 105 that is responsible for controlling maintenance tasks in the ATM Central Exchange Subsystem (ACS) 100, such as fault collection and testing of hardware resources within Remote Center Interfac (RCIP), where a remote operation center or network operator controls communications with a Telecommunication Management Network (TMN) and performs protocol conversion as needed. e Processor (106), a Global Service Processor (GSP) 107 that controls system services provided throughout the system, a subscriber call processor (SCP), and a trunk line call processor (TCP) And a Number Translation Processor (NTP) 108 that responds to a number translation request from a Broadcast Call Processing Processor (BCP), and the Operational Preservation Processor (OMP) 102 comprises an ATM Switching System (ACS) ( In order to manage the operation, maintenance, and user interaction functions of 100), a magnetic display (MT), a disk (110), a console (111), a visibility display device, a printer, etc. Use

Meanwhile, the ATM subscriber switching system (ALS) 105 performs overall traffic control such as subscriber matching circuits, lock control, user parameter control (UPC), priority control, and congestion control. Subscriber Call Processor (SCP) 152 and NNI: Netwprk-Network Interface (NNI) protocol to perform call processing with the network and with the relay line matching circuit. Outgoing) performs call connection control for a call, and controls a trunk call processor (TCP) 153 that manages all functions for matching with a network, and controls an overall multiple access function of a call processing process. A subscriber switching module maintenance processor (ASMP) that manages control of maintenance tasks in the broadcast call processing processor (BCP) 154 and the ATM subscriber switching subsystem (ALS) 150. 155, and a Number Translation Processor (NTP) 156 for responding to a number translation request from a pressurizer call processor (SCP), a trunk line call processor (TCP), and a broadcast call processor (BCP). And suspend signal information cells on a User-Network Interface (UNI) / Network-to-Network (NNI) protocol, and are called a subscriber call processing processor (SCP) 152, a relay line call processing processor (TCP) 153, In addition to the broadcast call processing processor (BCP) 154, a signal processor (SH) for processing signal information (SH) is configured.

As described above, the ATM Central Switching Subsystem (ACS) 100 and the ATM Subscriber Switching Subsystem (ALS) 150 each have a plurality of processors, and there may be up to 64 processors in an actual ATM switch. All processors except for the preservation processor are called Main Processors, which maintain their respective views of software time.

On the other hand, unlike the main processor, the operation maintenance processor 102 has a system time and hardware time provided by a time generator composed of hardware. The above three times operate the system-wide time.

When the operation maintenance processor 102 is restarted as the above adjustments are made during startup or restart of the respective processors and through periodic checks, the operation sequence shown in FIG. 2 is followed.

In other words, the operation maintenance processor 102 first requests a hardware time to the network synchronization unit (201), and if the hardware time can be normally received, the hardware time itself is designated as the system time (206). If the hardware time cannot be provided due to an abnormal state of the system, it is required to supply software time to all main processors (202).

As described above, if the software time supplied from the main processors reaches a certain number (203), and if the coincidence time is more than a certain number (204), the software time is determined as the system time (206).

On the other hand, if the matching time of the software time supplied from the main processors does not reach a certain number (204), an alarm for time designation is generated and the time that the operation preservation processor 102 itself has, i.e., a real time clock (RTC) Time Clock) determines the system time (205).

When the main processors are started or restarted, the operation sequence shown in FIG. 3 is followed.

Each of the main processors requests the system time from the operation maintenance processor 102 (301). If the operation maintenance processor 102 operates normally and provides the system time, the main processor determines the system time as the current time. If 102 is an abnormal state, the system time is requested a predetermined number of times, for example, three times (302, 304). If the reception is successful, the received time is determined as the system time (305). The software time is determined by the time present (303).

Apart from starting or restarting, each processor currently running checks the consistency of the time it maintains at appropriate time intervals. The operation preservation processor periodically compares the hardware time with the system time and, if the difference between the two times is within the limits, requests the reference time from other processors and receives the received reference time, hardware time, reference time and the operation preservation processor. Each time is compared and the system time is determined as a matched time and the determined time is distributed to other processors.

Other processors except the operation maintenance processor periodically compare the difference between the system time and the self-operating time, and replace the self time with the system time if the difference between the two times is beyond the limit.

As described above, since the system time can always be reassigned, the conventional method of determining the service time with two current times of starting and ending of the service may err as described above.

However, the above problem can be solved by adding a function to record the number of time ticks that elapse after a specific time in the operating system and measuring the time interval between the start point and the end point of the service time through the number of time ticks. . In other words, the number of time ticks is managed separately from the designated system time, so that the time is re-designated during the service, so that even if there is a discrepancy in the relative current time, the service time is detected only by the first recorded time and the number of elapsed time ticks. Does not occur.

4 is the control flow of the present invention for measuring the service time, the operating system designates various hardware variables and software variables that can preserve time ticks (401) and the current system when any routine enters service processing. The time is read and stored as a service start time (402).

If service processing is in progress, the operating system increases the number of time ticks and records them (403). When service processing ends (404), the service time is detected and terminated using the stored service start time and the elapsed time ticks. (405).

As described above, the present invention adds a function to record the number of time ticks occurring after a specific time in the exchange system, and detects the service time between the service start point and the end point through the time tick counts, thereby ensuring the integrity of time and reliability. Time management is possible.

Claims (1)

A first step 401 of designating various hardware and software variables capable of preserving time ticks; A second step (402) of designating a hardware variable and a software variable in the above step and reading the current system time and storing it as a service start time; A third step (403) (404) of increasing and recording the time tick until the service is terminated when the service start time is stored in the step; When the service is terminated while performing the above steps, the service time is detected through a fourth step 405 of detecting the service time using the stored service start time and the number of time ticks. Service time detection method.