JPH06244955A - Additional service version management system - Google Patents

Abstract

PURPOSE:To replace the service with other service without stopping the system or the service by replacing new and old services with the same service name but different version as independent additional service codes when the additional service is replaced and controlling them as if they were different services. CONSTITUTION:Upon the receipt of a call/incoming call from a subscriber, a basic call control section 2 receives an additional service code via a subscriber data management 14 of an additional service control section 1 and a service version management section 11 and starts a corresponding service scenario section 4. Upon the receipt of an additional service replacement command by a maintenance operation management section 3, the management section 11 allocates a new service with a different version to an idle area on an additional service management table to register a service registration control section 12. Old service is deleted in pairs with the addition of new service. Thus, the services are replaced with each other without stopping the service.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention is used in a switching system that provides supplementary services. The present invention relates to an additional service version number management method for managing the version number of an additional service.

[0002]

2. Description of the Related Art Conventionally, in a switching system which provides this type of additional service, when the additional service is replaced,
If the system is a single system, the system is temporarily stopped and then the files are replaced, and if the system is a dual system, the system is switched although the system is not stopped.

Here, the supplementary service is, in addition to the basic exchange service of the exchange device, for example, three-way connection, partner billing, interrupt call, and other services provided according to the user's request. For the example and the device configuration, Ohmsha "Electronic Information and Communication Handbook", 1988, second volume 2
See page 052 for details.

[0004]

The above-mentioned conventional service version management system does not have the concept of the version number of the additional service in the system. Therefore, when the additional service is replaced, the file is replaced or the system is switched. Therefore, there was a problem that the system or service had to be temporarily stopped.

The present invention solves such a problem, and an object of the present invention is to provide a system capable of exchanging services without stopping the system or service provision.

[0006]

SUMMARY OF THE INVENTION The present invention provides a basic call control unit for performing call control for accepting calls and incoming calls from subscribers and activating additional services that have occurred during that time, and an additional call control unit for controlling additional services. A service control unit and a maintenance / operation management unit that receives commands from maintenance or operation managers, and registers, changes, reads, and deletes each data.
In a supplementary service version management method including a service scenario section in which a procedure of each supplementary service provided for each common supplementary service code is recorded in a system in which supplementary service names and supplementary service versions are associated A service version number management unit that manages the additional service code and performs mutual conversion between the additional service name and the additional service code, and a service registration control unit that registers and deletes the service corresponding to the additional service code And a service status management unit that manages the service status for each additional service code and blocks the service, and a subscriber data management unit that manages the contract service of each subscriber by the additional service name and registers and deletes the contract service. The service registration control unit has the same service name and different version numbers when replacing the additional service. That replaces old and new services as independent supplementary service code, characterized in that it comprises means for controlling as another service.

[0007]

[Function] The service version management unit manages a common additional service code in the system in which the additional service name and the additional service version are associated with each other, converts the additional service name and the additional service code to each other, and registers the service. The control unit performs service registration and deletion corresponding to the additional service code.
In addition, the service status management unit manages the service status for each additional service code and blocks the service, and the subscriber data management unit manages the contract service of each subscriber by the additional service name and registers the contract service. Delete it. In this way, when replacing supplementary services, define new and old services with the same service name but different versions as independent supplementary service codes, and treat them as completely different services inside the system. Establish the concept of version number for supplementary services.

That is, when replacing an additional service, new and old services having the same service name but different versions are replaced as independent additional service codes, and are treated as completely different services in the system.

As a result, it is possible to replace the services without stopping the system or service provision by only performing the registration process for the new service and the deletion process for the old service.

[0010]

Embodiments of the present invention will now be described with reference to the drawings. FIG. 1 is a block diagram showing the configuration of the embodiment of the present invention.

In the embodiment of the present invention, a basic call control unit 2 that performs call control for accepting an outgoing call and an incoming call from a subscriber and activating an additional service that occurs during that time, and an additional service control unit that controls the additional service. 1 and the maintenance / operation management unit 3 that accepts commands from the maintenance or operation manager to register, change, read, and delete each data, and within the system in which the additional service name and the additional service version number are associated with each other. And a service scenario section 4 in which the procedure of each additional service provided for each common additional service code is recorded. Further, as a feature of the present invention, the additional service control section 1 manages and adds the additional service code. A service version management unit 11 that performs mutual conversion between a service name and an additional service code, and registers and deletes a service corresponding to the additional service code. The service registration control unit 12, the service status management unit 13 that manages the service status for each additional service code and blocks the service, and manages the contract service of each subscriber by the additional service name and registers and deletes the contract service. The service registration control unit 12 is provided with a subscriber data management unit 14 for performing different services by replacing new and old services having the same service name and different versions with independent service codes when replacing the additional services. Including means for controlling.

Next, the operation of the embodiment of the present invention thus constructed will be described.

FIG. 2 is a flow chart showing an operation flow of the embodiment of the present invention, FIGS. 3, 5 and 7 are flow charts showing a flow of service starting operation in the embodiment of the present invention, and FIG. 4 is a new flow chart in the embodiment of the present invention. FIG. 6 is a diagram showing the flow of service registration operation, and FIG. 6 is a diagram showing the flow of old service deletion operation in the embodiment of the present invention.

The basic call control unit 2 accepts a service A activation request from the subscriber and issues a service activation request to the supplementary service control unit 1 in order to convert this into a supplementary service code (I). At this time, in the supplementary service control unit 1, as shown in FIG. 3, the subscriber data management unit 14 accepts the request, inquires the supplementary service code to the service version management unit 11, and controls the supplementary service code (1) to the basic call. Part 2
Return to (). Based on the converted additional service code, the basic call control unit 2 activates the corresponding service scenario unit 4.

After that, when the additional service replacement command maintenance / operation management unit 3 receives from the maintenance / operation manager, first, an additional service code allocation request is made to register a new service, and an additional service code is assigned to the allocated additional service code. Make a registration request (II). At this time, in the additional service control unit 1, as shown in FIG. 4, the service version management unit 11 receives the additional service code allocation request, allocates a new service having a different version number to the empty area on the additional service management table, and adds the new service. Returns service code (4) (). Further, the service registration control unit 12 accepts the registration request and registers the designated additional service code (4).

Next, the old service is deleted, but if the subscriber makes a request for starting the service A in the same manner as above, it is converted because the new version number for the service A has already been registered. The service scenario section 4 corresponding to the additional service code (4) is activated (III
,).

Then, in order to delete the old service from the maintenance / operation management unit 3, a request for conversion to an additional service code is made, and after the blocking of the service corresponding to the additional service code is completed, the old service code is deleted. Make a request (IV). At this time, in the additional service control unit 1, as shown in FIG. 5, the service version management unit 11 accepts the request for conversion to the additional service code, and returns the additional service code (1) (). Further, the service registration control unit 12 accepts the service deletion request, and issues a request for blocking the designated service to the service status management unit 13. Service status management unit 1
In 3, the new service of the specified service is restricted from being started, and if the currently specified service is already started, it is confirmed that the service is completed and the blocking completion is returned.
In the request to delete the old service code, the service version management unit 11 accepts it as shown in FIG. 6 and deletes it from the additional service management table.

After this, when there is a service A activation request from the subscriber, the service scenario unit 4 corresponding to the additional service code (4) is activated as shown in FIG. 7 (V,).

[0019]

As described above, according to the present invention, in the exchange system for providing the supplementary service, when the supplementary service is replaced, a new version having the same service name but different version number,
Since the old service can be defined as an independent additional service code, only the registration process for the new service and the deletion process for the old service are performed, and the services are replaced without stopping the system or service provision. There is an effect that can be.

[Brief description of drawings]

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

FIG. 2 is a diagram showing a flow of operations of the embodiment of the present invention.

FIG. 3 is a diagram showing a flow of service starting operation in the embodiment of the present invention.

FIG. 4 is a diagram showing a flow of a new service registration operation in the embodiment of the present invention.

FIG. 5 is a diagram showing a flow of service starting operation in the embodiment of the present invention.

FIG. 6 is a diagram showing a flow of an old service deletion operation in the embodiment of the present invention.

FIG. 7 is a diagram showing a flow of service activation in the embodiment of the present invention.

[Explanation of symbols]

 1 Additional service control unit 2 Basic call control unit 3 Maintenance / operation management unit 4 Service scenario unit 11 Service version management unit 12 Service registration control unit 13 Service status management unit 14 Subscriber data management unit

Claims (1)

[Claims] 1. A basic call control unit for performing call control for accepting an incoming call and an incoming call from a subscriber and activating a supplementary service generated during that period, a supplementary service control unit for controlling the supplementary service, and maintenance or operation. For each common additional service code in the system that associates the additional service name and the additional service version with the maintenance / operation management unit that accepts commands from the administrator, registers, changes, reads, and deletes each data In the supplementary service version number management method provided with a service scenario section in which the procedures of the respective supplementary services provided are recorded, the supplementary service control section manages supplementary service codes and stores supplementary service names and supplementary service codes. Service version management section that performs mutual conversion, and service registration control that registers and deletes services corresponding to additional service codes Section, a service status management section that manages the service status for each additional service code and blocks the service, and subscriber data management that manages the contract service of each subscriber by the additional service name and registers and deletes the contract service. The service registration control unit includes means for replacing new and old services with the same service name and different versions as independent additional service codes and controlling them as different services when replacing the additional services. A supplementary service version number management method characterized in that