KR0182637B1 - Scheduling method - Google Patents

Abstract

The present invention is to provide a schedule management method for each subscriber that can receive the schedule management message recorded by the subscriber at a desired time using a special service function in the exchange, the method according to the present invention, the subscriber terminal When the code for the calendar service using the authorization, if there is a calendar message that was not previously provided normally providing it; If there is no calendar message previously not provided normally, after the code is authorized, updating the authorized time data to the schedule service start time; Allocating a channel for recording a predetermined message to record a schedule message authorized from the subscriber; When the service start time is reached, checking whether the subscriber is in an idle state, and if idle, making a call setup request several times until the subscriber responds; Returning to the code input wait state for the calendar service if the call is not answered despite several call setup requests; In response to the call setup request, a recorded schedule message is provided several times. Therefore, it is possible to conveniently manage their own schedule with a variety of messages, it is not necessary to have a separate terminal equipped with a schedule management function.

Description

Subscriber's schedule management method in exchange

1 is a functional block diagram of an exchange for performing a subscriber-specific scheduling method according to the present invention,

Figure 2a, b is a flow chart for a subscriber schedule management method according to the present invention.

* Explanation of symbols for main parts of the drawings

100: terminal 110: exchanger

111: analog subscriber control unit (ASC) 112: subscriber service control unit (SSCO)

113: number translation unit (NTR) 114: global service control unit (GSC)

115: Voice Message Service Unit (VMSU)

116: concurrent real-time operating system (CROS) 117: database (DB)

The present invention relates to a schedule management method for each subscriber in the exchange, and more particularly to a schedule management method for each subscriber using a special service.

In the existing exchange, a special service for schedule management by subscribers has a function of notifying a designated time. This is to inform certain subscribers who have registered their desired time of service with the service code that the designated time has been reached when the relevant time is reached. There is a drawback that the service is not delivered properly to the person who registered the service, and there is a problem that the contents of the anari recording guide are fixed so that various messages cannot be provided.

Accordingly, an object of the present invention is to provide a schedule management method for each subscriber that provides a schedule management message recorded by the pressurized paper directly at the time desired by the subscriber using a special service function in the exchange.

In order to achieve the above object, a method according to the present invention comprises the steps of: a subscriber authorizing a code for a calendar service using a terminal; If a code for a calendar service is authorized, checking whether there is a calendar message that is not provided for the subscriber; Outputting a message for the corresponding schedule management service, if present; If there is no calendar message that is not provided, after the code is authorized, updating the authorized time data to the schedule service start time; Allocating a channel for recording a predetermined message after the updating step; Recording a calendar message authorized from the subscriber using the assigned channel; After the registration of the schedule management message, requesting call setup from the corresponding subscriber when the service start time arrives; When the call setup request is made, checking whether the subscriber is in an unresponsive state while the call setup is requested a predetermined number of times when the subscriber is idle in the idle state; If the subscriber is not answered despite the call set up a predetermined number of times, returning to the service code authorization step; When the call setup request, the subscriber responds to the recorded schedule management message to the subscriber, characterized in that performed.

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

1 is a functional block diagram in an exchange for performing a schedule management method for each subscriber according to the present invention, and is composed of a terminal 100 such as a telephone that the subscriber can operate and an exchange 110.

Switch 110 is an analog subscriber control (abbreviated as ASC) 111, subscriber service control (hereinafter abbreviated SSCO) 112, number to carry out the method according to the invention. Number Translation (hereinafter referred to as NTR) 113, Global Service Control (hereinafter referred to as GSC) 114, Voice Message Service Unit (hereinafter referred to as VMSU) (115) ), A parallel real-time operating system (hereinafter referred to as CROS) 116, and a database (database, referred to as DB below) 117.

2 is a flowchart of a schedule management method for each subscriber according to the present invention.

Next, the operation of FIG. 2 will be described in detail with reference to FIG. 1.

In step 201, when the subscriber sets the terminal 100 to the hook-off state, and inputs a special service code (random digit information) for schedule management, the ASC 111 proceeds to step 202 and returns to normal. Check for calendar messages that are not provided.

As a result of the check, if there is no schedule management message not normally provided, the process proceeds to step 203 to transmit the authorized special service code from the terminal 100 to the SSCO 112, and the SSCO 112 is authorized special service code. Number translation to NTR 113 is requested.

The NTR 113 translates the number for the number requested in step 204, and notifies the SSCO 112 by classifying the service type according to the number translated result. The SSCO 112 updates the information of the DB 117 on the calendar special service according to the contents notified from the NTR 113. For example, when the digit data specifying the service time is received from the subscriber, the SSCO 112 updates the service time data stored in the DB 117 in step 205. The GSC 114 requests channel allocation for recording the subscriber's message. Accordingly, the GSC 114 allocates a channel to the VMSU 115 and notifies the SSCO 112 that the channel has been allocated.

Upon receiving notification that the channel is allocated, the SSCO 112 requests the ASC 111 to establish a path between the subscriber terminal 100 and the VMSU 115 in step 206. In response to this request, the ASC 111 establishes a path between the subscriber terminal 100 and a channel assigned to the VMSU 115, and uses the terminal 100 to transmit a message of an authorized subscriber through the established route to the VMSU 115. Recording). After the recording is finished, when the subscriber registers the service by completing the special service termination code existing in the terminal 100 in step 207, the SSCO 112 determines whether the service start time is reached in step 207. Check

As a result of the check, when the subscriber starts the service start time, the process proceeds from step 208 to step 209 where the SSCO 112 requests the call setup from the subscriber to the ASC 111. At this time, if the state of the subscriber is not in the idle state (Idle), the process proceeds from step 210 to step 211, and monitors until the subscriber state becomes idle (Idle) state, and if the idle state, proceeds to step 212 to be described later do. However, if the subscriber state is idle, the process proceeds from step 210 to step 212 and attempts to call the corresponding subscriber to ring.

At this time, if the subscriber does not respond, the process proceeds from step 213 to step 214 and checks whether the corresponding subscriber is in an unresponsive state even though three or more call setup requests have been made. As a result of the check, if the call is not requested three times or more, the process proceeds from step 214 to step 215 to maintain the standby state for 30 minutes, and then proceeds to step 209 to request the call setup again to the subscriber three times. The above process is repeated until the call setup request is made. However, if the subscriber does not respond despite three or more call setup requests, the process returns to step 201.

If the subscriber responds in step 213, the subscriber station proceeds to step 216 to read and provide a message recorded by the subscriber to the VMSU 115. Then, if the end code is received from the terminal 100, the operation ends in step 217.

If the end code has not been received, the process proceeds to step 218 through step 217 and checks whether the same message has been provided three or more times. As a result of the check, if the message has been provided more than three times, the operation is terminated. If not, the process proceeds from step 218 to step 219, and the standby state is maintained for 30 minutes. to provide.

On the other hand, if the check result of step 202, if there is a schedule management message that was not normally provided previously, the process proceeds from step 202 to step 220, outputs the registered message and ends the operation. Here, the schedule management message that is not normally provided is a message that is not provided because the subscriber does not respond to three call setup requests even though the subscriber is idle as described above.

As described above, the present invention implements its schedule management and corresponding messages freely by registering / changing / cancelling to the exchange by using the corresponding terminal and being notified at a desired time by the subscriber, so that the schedule can be more conveniently set. It can be managed, and there is an effect that it is not necessary to separately provide a terminal with a special function for scheduling.

Claims (2)

Authorizing a code for a calendar service by a subscriber; If a code for the calendar service is authorized, checking whether there is a calendar message which is not provided for the subscriber; Outputting a message for a corresponding schedule management service, if present; If the unscheduled schedule message does not exist, after the code is authorized, updating the authorized time data to a schedule service start time; Allocating a channel for recording a predetermined message after performing the update step; Recording a calendar message authorized from a subscriber using the assigned channel; Requesting call setup from a corresponding subscriber when the service start time arrives after registration of a schedule management message is completed; When the call setup request is made, checking whether the subscriber is in an unresponsive state while the call setup is requested a predetermined number of times or more when the corresponding subscriber is idle in the idle state; Returning to the service code authorization step if the subscriber is in an unresponsive state despite the call establishment more than the predetermined number of times; And in response to the call establishment request, providing the recorded schedule message to the corresponding subscriber when the corresponding subscriber responds. The switch of claim 1, wherein the step of outputting the message provides the schedule management message more than a predetermined number of times if the end code for the schedule management service is not received from the corresponding subscriber after the message is output. Subscriber schedule management method in the.