JPH04336837A - Management system for connection control system additional service execution state - Google Patents

Abstract

PURPOSE:To facilitate the addition of a new service and the revision of the existing service. CONSTITUTION:The above system is a system in which plural calls are allocated to a basic call control section to realize call processing with incoming outgoing separation and subject to control, and additional service execution state management tables 15, 16 manage a link from a call to a service started from the call, or from a started service to a next service during simultaneous execution of plural services, or from a service to an interrupted service when the service is interrupted to start the other service in the logical relation of connection between a call and another call or between a call and a service. Then a function storing a state unique to each service and storing a service data 17 required for service control of each service is made independent of a basic call additional service execution section 12, and an additional service execution state management section 13 manages the execution state of a connection control system additional service.

Description

[Detailed description of the invention]

0001

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an exchange that implements additional services, and more particularly to a system for managing the execution state of connection control-based additional services.

0002

2. Description of the Related Art Conventionally, the execution status of this type of additional service has been independently managed within a service execution program for each additional service.

0003

[Problems to be Solved by the Invention] In the conventional state management method described above, when multiple services are executed simultaneously, or when a service is interrupted in the middle of service startup, another service is started, and the original service is returned after the service ends. In addition, multiple service execution programs are intricately related to each other, making maintenance work complicated. That is, there is a drawback that adding a new service or deleting or modifying an existing service does not only change the service, but also has a large impact on other services.

SUMMARY OF THE INVENTION An object of the present invention is to provide a connection control system additional service execution state management system that solves the above-mentioned problems.

[0005]

[Means for Solving the Problems] In order to achieve the above object, in the connection control system supplementary service execution state management method according to the present invention, in realizing the connection control system supplementary service provided by the exchange, calls are separated by input/output. The basic call control unit that implements the processing allocates and controls multiple calls, and the logical connection relationships between calls and calls and services are established from calls to services activated on the calls, and from multiple calls to services activated on the calls. When services are running simultaneously, from the starting service to the next service, or from a service to the suspended service when interrupting one service while starting a service, starting another service, and returning to the original service after the service has finished. The service execution program and supplementary service analysis program for each supplementary service have the function of managing the links in a tree format and storing the unique status of each supplementary service and the service data necessary for service control of each supplementary service. independently manages the execution status of the connection control system supplementary service, and has a common interface for service execution management status management for the supplementary service execution program and supplementary service analysis program.

[0006]

[Operation] Adding new services and changing existing services is made easier by making the relationship between services that can be executed concurrently loose.

[0007]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the present invention will be explained with reference to the drawings. FIG. 1 is a block diagram showing one embodiment of the present invention.

In the figure, 1 is a basic call 1 between subscribers A and B, 2 is a basic call 2 between subscribers A and C, and 3 is a basic call n between subscribers A and X. , 4 is a call control task that controls subscriber A side of basic call 1, 5 is a call control task that controls subscriber A side of basic call 2, and 6 is a call control task that controls subscriber A side of basic call n.
7 is a call control task that controls the subscriber B side of basic call 1, 8 is a call control task that controls the subscriber C side of basic call 2, and 9 is a call control task that controls the subscriber side of basic call n. This is a call control task that controls the X side.

10 is an additional service analysis program;
11 is an additional service execution program, 12 is a basic call/additional service execution unit, and 13 is an additional service execution state management unit.

Reference numeral 14 denotes an additional service execution state management unit common interface, 15 an additional service execution state management table corresponding to basic calls, 16 an additional service execution state management table corresponding to services, and 17 service data.

[0011] In this embodiment, a basic call control unit that realizes call processing by separating input and output is used to allocate and control multiple calls, and the logical connection relationships between calls and calls and services are determined from calls to calls. To the service started on that call, or from the starting service to the next service when multiple services are executed simultaneously, or from the service to the suspended service when interrupting one service and starting another service. The basic call/additional service execution unit 12 has the function of managing the links in the supplementary service execution state management tables 15 and 16 and storing the unique status of each service and the service data 17 necessary for service control of each service. The additional service execution state management unit 13 manages the execution state of the connection control system additional services independently of the above.

That is, when the basic call control task A1 that controls the basic call corresponding to the service initiator A receives a service activation event, the additional service analysis program 1
Start 0. The additional service analysis program 10 performs a competition analysis by inquiring the additional service execution state management unit 13 about the service currently activated by the subscriber, and determines whether the additional service can be activated.

[0013] In the additional service execution state management unit 13, as shown in FIG.
Additional service execution status management table 15 as shown in FIG.
16, and remembers the running services. When the service can be started, the service execution program 11 that implements the connection control system additional service is started. The service execution program 11 sends to the supplementary service execution state management section 13 a request for linkage connection between the supplementary service execution state management table 16 corresponding to the service and the supplementary service execution state management table 15 corresponding to the hunt and basic call.

[0014] The additional service execution state management unit 13 performs a linkage connection between the call and the newly activated service if it is the first service for the subscriber, and if there is an activated service, newly activated from the activated service. Automatically connect linkages to services.

The service execution program 12 controls the second call controlled by the basic call control task A2, for example, for a newly originated call in the case of a three-party call service, and for an incoming call in the case of a call waiting service. A linkage connection is made between the corresponding additional service execution state management table 15 and the additional service execution state management table 16 corresponding to the additional service.

FIG. 3 shows call waiting during a three-party call as an example of an execution state management table when a plurality of services are simultaneously executed in which three or more calls are involved. Even when a call waiting call arrives during a three-party call and an out-of-band message to that effect is sent to all related subscribers, the related call at that time is read out from the supplementary service execution state management unit 13. This makes it possible to send. Data necessary for service control, such as the trunk number for three-party calls when realizing the three-party call service, is stored as service data in the additional service execution state management section 13. The additional service execution state management unit 13 stores the service data in a manner that secures an area of the requested size without sensing the contents of the service data.

Even if one service ends when a plurality of services are activated, the additional service execution state management unit 13 automatically reorganizes the linkage in response to a request from the service execution program 11 to release the execution state management table 16 corresponding to the service.

[0018] Also, when interrupting a service midway through, executing another service, and returning to the original service, a program for interrupting and returning the service should be prepared in advance on the old service side, and saved at that point. This process can be realized by storing necessary data as service data in the additional service execution state management unit 13, by creating a common interface that can be called from any service, and by calling the program on the new service side.

[0019]

[Effects of the Invention] As explained above, the present invention allows multiple services to coexist and be executed at the same time by only being aware of the logical connection relationships between calls and calls and services at that time. Services can be controlled independently, and even when interrupting a service midway through, running another service, and returning to the original service, a program for interrupting and returning the old service is prepared in advance, a common interface is provided, and the new service side This can be easily achieved by calling the program, minimizing the impact on other services, and allowing a third party to develop new services.

[Brief explanation of drawings]

FIG. 1 is a block diagram showing one embodiment of the present invention.

FIG. 2 is a diagram showing an execution state management table of connection control system additional services corresponding to basic calls and services.

FIG. 3 is a diagram showing an example of an execution state management table when a three-party call service and a call waiting service are executed simultaneously.

[Explanation of symbols]

1 Basic call 1 (between subscriber A and subscriber B) 2 Basic call 2 (between subscriber A and subscriber C) 3 Basic call n (between subscriber A
~ subscriber Task 7 Call control task 8 to control the subscriber B side of basic call 1 Call control task 9 to control the subscriber C side of basic call 2 Call control task 10 to control the subscriber X side of basic call n Supplementary service analysis Program 11 Supplementary service execution program 12 Basic call/supplementary service execution unit 13 Supplementary service execution status management unit 14 Supplementary service execution status management unit common interface 15 Supplementary service execution status management table for basic calls 16 Supplementary service execution status management for services Table 17 Service data

Claims (1)

[Claims] Claim 1: In realizing the connection control system supplementary service provided by the exchange, a basic call control unit that realizes call processing by separating input and output is used to allocate and control multiple calls, and to control calls between calls and between calls and services. Logical connection relationships can be established from a call to a service activated on that call, from an activated service to the next service when multiple services are executed simultaneously, or from a service that is interrupted during service activation to another service. When starting a service and returning to the original service after the service ends, the link from the service to the suspended service is managed in a tree format, and the unique status of each additional service and service control for each additional service are controlled. The function of storing necessary service data is made independent of the service execution program and the supplementary service analysis program for each supplementary service, and the execution status of the connection control system supplementary service is managed, and the service is stored in the supplementary service execution program and supplementary service analysis program. A connection control system additional service execution state management method characterized by having a common interface for execution management state management.