KR101094610B1 - Method for controlling call of intellignet network through circuit management of receipt connection - Google Patents

Abstract

The present invention relates to a call control method of an intelligent network service through an incoming connection line management. By connecting incoming calls as many as the number of incoming lines applied at the time of subscription, it is possible to operate a stable system by preventing the departure of subscribers and reducing network load. The purpose of the present invention is to provide a call control method for an intelligent network service through an incoming connection line management that can be appropriately provided.

To this end, the present invention, the call control method of the intelligent network service, the receiving line confirmation step of confirming the incoming line in response to a call connection request from the caller side; Determining whether to manage incoming connection line management on the identified incoming line; A line number checking step of checking the maximum number of lines previously applied, the number of lines currently being used, and the number of lines available for communication as the determination result is the incoming connection line management; A call control step of controlling a call according to the identified maximum number of previously requested lines, the number of lines currently being used and the number of lines available for call; And a synchronization step of synchronizing the corresponding change data history with another system as the call is connected according to the call control of the call control step and the number of lines currently being used and the number of available lines are changed.

Incoming line, line management, intelligent network service, service control system, service management system, number portability, LNP, congestion call, centralized call

Description

Call control method of intelligent network service through incoming connection line management {METHOD FOR CONTROLLING CALL OF INTELLIGNET NETWORK THROUGH CIRCUIT MANAGEMENT OF RECEIPT CONNECTION}

The present invention relates to a call control method of an intelligent network service through incoming connection line management, and more particularly, by connecting incoming calls as many as the number of incoming call lines applied for subscription, it is possible to prevent the departure of subscribers and reduce the network load, thereby enabling stable system operation. And it relates to a call control method of the intelligent network service through the incoming connection circuit management, which can provide limited resources appropriately.

1 is a configuration diagram of an intelligent network system for providing a call control service.

The intelligent network system includes a service management system (SMS) 100, a service control point (SCP) 110, and a PSTN-based intelligent network switch (SSP) in a public switched telephone network (PSTN) network. Point) (120), PSTN / BcN-based intelligent network switch (SSW: SoftSwitch) (130), next-generation intelligent network peripheral (AIP: Advanced Intelligent Peripheral) (140), third party interworking exchange that may cause failures due to an increased number of incoming calls. (IGS: Interconnection Gateway Switch) 150 and a terminating local exchange (LE) 160 that handles local number portability (LNP) numbers switched to third party carriers.

Here, the service management system (SMS) 100 is connected to the service control system (SCP) 110 and the data system 101, and the data system 101 is connected to the terminal 102. The service management system 100 manages subscription information and number of lines and call processing of a plurality of service control points (SCPs) 110.

The service control system 110 manages network configuration information and subscriber information, and controls the network control information according to network-level service control logic. That is, the service control system 110 performs a function of managing the entire process of the intelligent network service.

The PSTN-based Service Switching Point (SSP) 120 analyzes the requested call and determines whether it is an intelligent network service when a telephone service request is made from a telephone network subscriber. If the requested call is an intelligent network service, the PSTN-based intelligent network switch 120 requests the service control system 110 for call control information necessary for processing the intelligent network service, and uses the control information transmitted from the service control system 110 to the subscriber. Provide the desired call service.

On the other hand, the PSTN-based intelligent network exchange (SSP) 120 is connected to the mobile gateway (Mobile G / W) 121 and the originating local exchange (LE) 122 based on the PSTN. The mobile gateway 121 is connected to the mobile terminal 123 for processing voice calls in the current network for intelligent network services (15XY or 080, etc.), and the originating local exchange 122 processes voice calls or calls for complaints. It is connected to the PSTN-based voice terminals (124 and 125) to perform the.

Meanwhile, the PSTN / BcN-based intelligent network switch (SSW) 130 processes video calls of VoIP-based SoIP exchange (IMS) 132, which is IP-based and Session Initiation Protocol (SIP), and SoIP and 3G terminals. It is connected to a video gateway (Video G / W) (131). Here, the video gateway 131 is connected to a mobile switching center (MSC) based on a WCDMA network, and the mobile switching center (MSC) 133 is connected to a 3G terminal (video) 134. It is. In addition, the IMS 132 is connected to a SoIP terminal (video) 135 that processes voice calls in a VoIP network.

The PSTN / BcN-based intelligent network switch (SSW) 130 is connected to the VRS hosting server 170, and the VRS hosting server 170 is connected to the client server 173 and the voice / video destination terminal 174 located at the client call center. It is. Here, the IP-based VRS hosting server 170 includes an IP Private Automatic Branch eXchange (IP PABX) 171 and an Interactive Video & Voice Response (IVVR) 172.

Meanwhile, the called local exchange (LE) 160 is connected to the called terminal 161.

The third party interlock exchange 150 is connected to the third party local exchange 151 through a third party vendor network, and the third party local exchange 151 is connected to the third party terminal 152.

The centralized intelligent network system shown in FIG. 1 connects an incoming call to a physically configured circuit and provides a corresponding announcement (eg, congestion or self-customized announcement).

In some examples, the conventional centralized intelligent network system has a problem that it is difficult to manage the originating call for the LNP called number of the other company, the customer number with a large number of calls to the line and the IP-based called number that is difficult to manage the line physically. Hereinafter, the operation of the conventional centralized intelligent network system corresponding to the LNP called number of the other company, the customer number with a large number of calls generated over the line, and the IP-based called number which is difficult to manage the circuit will be described in detail.

The service provider's customers use the enterprise intelligent network number of the highly recognized representative number (e.g., 1588, 1577, and 080, etc.) among the numbers providing the same type of service in the competitive environment of the intelligent network service including the representative number in the fierce marketing war. . The customer of such a carrier may move to another carrier having a relatively low line cost while maintaining a high representative number. To do this, the customer applies only the minimum number of lines required by a well-known telecommunication company (for example, five lines, etc.), and allows the other telecommunications company to transfer the number of lines more than the previous price. In particular, telecom operators are using it as a means of attracting subscribers in the sense that customers can reduce line costs. Therefore, a carrier with a high representative number is difficult to retain subscribers and attract new subscribers.

Here, in the case of a customer who uses the called party number using local number portability (LNP) to another carrier while using the representative number of the first carrier (for example, 1577 and 1588), the first carrier Knows only the number of incoming lines for the first carrier that the customer applied for. That is, the first communication company cannot know the number of lines actually used by the user applying to another communication company.

In particular, when a user uses an LNP line with another carrier, the carrier is not controlled by the number of physical lines applied to the carrier, but by mutual agreement between the carriers (for example, technically using a call transfer function). All calls originating from the first carrier are forwarded through a third party interworking gateway (G / W) exchange.

For example, when a customer pays for the line and the cost that the customer has applied for, the carrier establishes a line for it. After that, since the transferred LNP line is a subscriber line of another telecommunication company, information on a line in use through number portability cannot be known from the first telecommunication company. Therefore, the first carrier cannot control the actual call connection. At present, all outgoing calls originating from the first carrier network are transferred and the transferred outgoing calls are forwarded to other carriers and connected.

2 is an explanatory diagram of line management of a subscriber who has been ported to a called party number of a third party through LNP.

As shown in FIG. 2, the subscription customer terminal 231 applies three lines to the 'A' telecommunications company in order to use the national representative number of the telecommunications company 'A'. 'A' constitutes three applied lines. Subsequently, subscribers move to the 'B' carrier and apply for 30 lines from the 'B' carrier. For example, a subscription customer uses a number of counselor terminals 251 and wired terminals 252 that are numbered 30 lines to the 'B' carrier.

After the number transfer, the originating call of the wired terminal and the wireless terminal 221, which is received by the subscribing customer terminal 231, passes through the SSP / SSW 220 of the PSTN network, and then through the local exchange 230 of the 'A' telecommunication company. It is delivered to an interlocking G / W switch (IGS) 240. In addition, the third party interworking G / W exchanger 240 is a plurality of agent terminals 251, which are customer terminals that have been ported to the LNP line from the 'A' carrier via the incoming local exchange (LE) 250 of the PSTN / VoIP network of the third party. And transfers to wired terminal 252.

A subscriber may use a larger incoming line provided by the 'B' carrier while maintaining the representative number of the 'A' carrier and using the minimum incoming line (eg, three lines) required by the 'A' carrier. In this case, the service control system (SCP) 210 on the 'A' carrier side needs to control the line by the actual number of lines subscribed to by the 'A' carrier. If the service control system (SCP) 210 does not control the line for the application line, the subscribers of the 'A' telecommunications carrier, which is the leading telecommunications company, move the telecommunications carrier to reduce the telecommunication costs, and the 'B' telecommunications company establishes more incoming lines. use. If the number of subscribers increases, the 'A' telecommunications company has a problem in that it is forced to take a disadvantage in reducing sales and operating services.

3 is a diagram illustrating an exemplary embodiment of an error in the destination exchange due to congestion occurring on a specific day in the related art.

Let's take a look at the case where the registered customer operates the golf course reservation number or the event number representative on the specific day.

Circuits congested on specific or eventful calls will increase the load on the terminating network and the exchange. For example, the number of lines of the ARS of the client company is limited on the settlement date of the financial sector. If there are many calls that want financial transactions, the destination exchange that accepts the financial ARS will fail due to network load and system load due to congested incoming calls. In addition, the event call congestion control also has a problem that the incoming call control is difficult. In addition, the incoming call control becomes difficult even for a number in which the number of lines is relatively small but the generated calls are momentarily collected. That is, in the case of reserved calls of golf courses across the country, there are few counseling agents related to reservations, but the number of generated calls may burst instantly. In this case, there is a problem that the network and communication resources can not be stably operated.

As shown in FIG. 3, a subscription customer operating a golf course reservation number or an event representative number that is driven on a specific day may operate a counselor terminal 331 or a golf reservation counselor terminal 332. For example, the golf reservation counselor terminal 332 uses five lines.

When the centralized call occurs instantaneously from the wired terminal and the wireless terminal 321, the instantaneous centralized call is transferred to the incoming local exchange 330 through the SSP / SSW 320 under the control of SCP 310 of the PSTN network. Here, when the incoming line is instantaneously concentrated with respect to the number of lines applied during the first subscription, a failure occurs in the incoming exchange 330.

That is, subscribers can reduce communication costs by operating less incoming lines compared to outgoing calls. On the other hand, there is a problem in that a communication provider providing a service and a network causes a failure of the network and the destination exchange 330 due to the network congestion of the called party due to an incoming call that is not actually connected to a call generated at the calling party.

In this case, other subscriber stations accommodated in the destination exchange 330 will be affected. In order to solve this problem, a service provider providing a service and a network may reduce a load through a physical configuration of redundant or redundant relay networks or terminators connected to the terminating line. However, if the generated call bursts in a short moment, the network and the destination exchange 330 will inevitably be overloaded. Even in this case, it is necessary to reduce the amount of incoming calls compared to the outgoing call by providing the service only for the number of lines requested by the service provider and the available lines for actual consultation.

PSTN-based circuits, which can use only physically defined circuits, are easy to manage in terms of circuit management since only the circuits subscribed to the service provider are provided to customers. In addition, when the transition to the IP network due to network evolution or the transition is completed in the future, the incoming line management is required for the IP-based circuit.

4 is a diagram illustrating an embodiment of a call line management in an IP-based VRS hosting device.

As shown in FIG. 4, when a call is concentrated from a SoIP terminal (video), a 3G terminal (video), and a wired terminal 421, the SSW 420 generates a call (eg, under the control of SCP 410). For example, the call 1000 may be transmitted to the IP PABX 431. Then, the IVVR 432 processes the originating call input through the IP PABX 431 according to the subscriber-specific scenario.

Here, the VoIP-based VRS hosting device 430 established by the communication service provider, that is, the line that can be operated in the centralized ARS-type line management is limited. If the line management assigned to a particular subscriber is not performed, it may damage other subscribers joining the same hosting line. The service of the hosting device 430 (eg, the 1588 VRS service) does not provide a limited number of lines as many as the number of subscription lines of a subscription customer, but processes the amount of calls generated first.

As an example, it will be assumed that the VRS hosting device 430 having a total of 2000 lines allocates a line to 100 subscribers every 20 lines to provide a service. If you have 100 subscribers, you can use 20 lines per subscriber. The line fee is paid for as many lines as you apply. In this case, the VRS hosting device 430 should be able to make the incoming connection as much as the line cost by making a call connection for the incoming call player.

However, when a call for a specific number of a specific subscriber is congested in the VRS hosting device 430 as described above, a subscriber may occupy all the lines held by the VRS hosting device 430. In this case, another subscriber may not be able to receive the hosting service of the VRS hosting device 430. When a call is continuously made to one subscriber continuously, the VRS hosting device 430 may control the ongoing call by distributing a circuit. However, in case of temporary congestion, the VRS hosting device 430 is difficult to control the generated call in real time, and there is a problem that it is difficult to control itself in the IP PABX 431.

Therefore, the prior art as described above, there is a problem that the management of third party LNP called number, the management of the number of calls generated more than the line, and the management of IP-based called number that is difficult to physically manage the line, the present invention to solve this problem Is the task.

Therefore, the present invention is capable of stable system operation by preventing the departure of subscribers and reducing the network load by making the incoming connection as many incoming circuits as applied for the subscription, and intelligent network service through the incoming connection circuit management, which can adequately provide limited resources. Its purpose is to provide a call control method.

The objects of the present invention are not limited to the above-mentioned objects, and other objects and advantages of the present invention which are not mentioned can be understood by the following description, and will be more clearly understood by the embodiments of the present invention. Also, it will be readily appreciated that the objects and advantages of the present invention may be realized by the means and combinations thereof indicated in the claims.

The present invention is to solve the above problems, by connecting incoming calls as many as the number of incoming calls applied for subscription, it is possible to operate a stable system to prevent the departure of subscribers, reduce the network load, it is characterized in that it provides a limited resource appropriately .

More specifically, the method of the present invention includes a call control method for an intelligent network service, comprising: a called line identification step of confirming a called line according to a call connection request from a calling party; Determining whether to manage incoming connection line management on the identified incoming line; A line number checking step of checking the maximum number of lines previously applied, the number of lines currently being used, and the number of lines available for communication as the determination result is the incoming connection line management; A call control step of controlling a call according to the identified maximum number of previously requested lines, the number of lines currently being used and the number of lines available for call; And a synchronization step of synchronizing the corresponding change data history with another system as the call is connected according to the call control of the call control step and the number of lines currently being used and the number of available lines are changed.

delete

In addition, the method of the present invention further includes the step of re-adjusting the number of available lines and the initial number of lines according to the difference in the volume of calls generated by processing in a plurality of regions.

The present invention as described above, by making the incoming connection as the number of incoming lines applied for subscription, it is possible to stably operate the system by preventing the departure of the subscriber, reducing the network load, there is an effect that can provide adequate resources.

For example, the present invention has the effect of preventing the departure of customers moving to another telecommunication company for the purpose of reducing the line cost by controlling the call connection according to the number of incoming lines.

In addition, the present invention has the effect of reducing the load on the destination network and the switch for the line congested with a specific day or event call. For example, the number of lines of the ARS of the client company is limited on the settlement date of the financial sector. In the case of a large number of calls for financial transactions, the destination exchange that accepts the financial ARS fails due to network load and system load due to the bursting incoming call. The present invention has the effect of stably operating the network and communication resources by controlling the call control on the calling party to the customer's incoming line. In addition, the present invention has the effect that the incoming call can be controlled by the above method even in the congestion control of the event call. In addition, the present invention has an effect that can be applied to a number in which the number of generated calls is instantaneously collected while the number of lines is relatively small. That is, in the case of a national golf course reservation issue, there is a small number of reservation-related counselors, but the present invention can be applied even when a generation call is suddenly congested.

The present invention has an effect that can be used for PSTN-based or VoIP-based hosting equipment, that is, a centralized ARS-type line management. The hosting equipment (for example, 1588 VRS service) is not configured to use the limited number of lines as many as the number of subscription lines of the subscription customer, but to process as much as the number of calls generated first. For example, if the number of lines of hosting equipment is 2,000 lines and the number of subscribers is 100, 20 lines can be used per subscriber, and the line fee is paid for the number of lines applied. However, when a call of a specific number congested at a specific time, users of the remaining subscription numbers may not use the service. In this case, the present invention has the effect of making the incoming connection as much as the payment of the circuit cost by controlling the call connection according to the number of incoming lines.

BRIEF DESCRIPTION OF THE DRAWINGS The above and other objects, features and advantages of the present invention will become more apparent from the following detailed description of the present invention when taken in conjunction with the accompanying drawings, It can be easily carried out. In the following description, well-known functions or constructions are not described in detail since they would obscure the invention in unnecessary detail. Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

In order to solve the problems of third-party LNP called number management, incoming number management with high number of calls per line, and IP-based called number management that is difficult to manage physically, the incoming call applied by the customer in the centralized intelligent network based service The incoming call is controlled through the incoming line management by monitoring the actual connected call for the number of lines.

In addition, the present invention in real time using the data change propagation function between the service control system in charge of call processing in the intelligent network system and the subscriber data for the call originating from multiple systems and regions, and the subscriber management data. It is possible to manage the fluctuation data. Existing called line management connects incoming calls to physically configured lines and provides corresponding announcements (such as runaway or self-customized announcements).

5 is a configuration diagram of an embodiment of a real-time intelligent network call processing system to which the present invention is applied.

The real-time intelligent network call processing system includes a service management system (SMS) 510, a plurality of service control systems (SCP1 to SCPn) 520, a PSTN / VoIP-based intelligent network switch (SSP / SSW) 530, a third party interworking exchange (IGS). 540, an incoming local exchange (LE) 550, and a VRS hosting device 560. Here, the intelligent network switch (SSP / SSW) 530 is connected to the wired terminal 531 and the wireless terminal 532. The VRS Hosting Device 560 also includes an IP PABX 561 and an IVVR 562.

In the real-time intelligent network call processing system, the voice-based wired terminal 531 and the wireless terminal 532 transmit the called number using the representative number. Then, the intelligent network switch (SSP / SSW) 530 connects to each individual called number terminal or call center terminal according to the line management type of the customer carrier under the control of the service control systems (SCP1 to SCPn) 520. In an embodiment, the plurality of service control systems (SCP1 to SCPn) 520 connects to the corresponding terminal according to the case of the LNP incoming line, the congestion call processing, and the line of the VRS hosting device, respectively. Here, the terminal is a third party number mobile terminal 541 connected to a third-party interlocking exchange (IGS) 540 in the case of an LNP terminating line, an agent terminal 551 connected to a local terminating switch (LE) 551, and VRS hosting It becomes a VoIP terminal connected with the device 560.

6 is a flowchart illustrating a call control method through the management of the number of called lines according to the present invention.

When the customer uses the representative number (1577 or 1588, etc.), the destination number is ported (LNP) to other carriers, and the call management of the line sharing line will be described.

The customer enters subscriber information and the number of incoming lines on the subscription screen (602). That is, the customer requests the representative number to secure the available representative number, and enter the incoming number you want to receive.

The service management system (SMS) 510 transmits the subscriber information and the number of incoming lines entered by the customer to the service control system (SCP) 520 (604). Here, the service management system (SMS) 510 stores the subscriber information and the number of called lines in the subscriber table.

When the subscribing customer converts the called number using the third party number portability (LNP), the change information about the called number changed by the number transfer is transmitted separately. The transmitted information is stored in a separate LNP called connection line management table instead of the basic called number table.

Then, when the caller attempts to call the corresponding subscriber representative number, that is, when the user calls the subscriber number (606), the intelligent network switch (SSP / SSW) 530 controls the service representative subscriber number called by the caller. Transfer to the system (SCP) 520 is switched to the incoming line management to be processed.

When the call comes up from the originator to the service control system (SCP) 520 through the intelligent network switch (SSP / SSW) 530, the service control system (SCP) 520 checks the service type in the subscriber information and selects the service option. It checks which of 2, 4, and 8 (608, 610). For example, if the service option is 2 (LNP), the service control system (SCP) 520 determines the called line management method according to the number porting according to the service option '2'.

Table 1 below is a part of the subscriber status table registered in the service control system (SCP) (520).

As shown in Table 1 above, the subscriber status table includes a subscriber number field sn (P), a service status field svcStatus, and a service option field svcOpt. For example, if the subscriber number field is '1588-2100', this indicates a representative number registered by the subscriber. If the service state field value is '0', it indicates that service is in progress. If the service option value is '2', it indicates PSTN incoming LNP line management; if the service option value is '4', it indicates congestion control (golf course reservation call, etc.); if the service option value is '8', IP-based destination line Indicates management (VRS).

If the check result 610, the service option is '2', that is, if the called number for the calling area designated by the subscriber is a third party LNP called subscriber, the service control system (SCP) 520 checks the called party number of the third party, Search for the number of lines currently available for connection and prepare to start call control (612). Subsequently, the service control system (SCP) 520 begins 614 call connection control.

As a result of the check 610, if the service option is '4', the incoming number is checked for congestion control, the number of lines currently available for connection is checked, and call control preparation is started (616). Subsequently, the service control system (SCP) 520 begins 618 call connection control.

As a result of the check 610, if the service option is '8', the incoming number is checked for VRS line control, the current number of available lines is searched and the call control is prepared to start (620). Subsequently, the service control system (SCP) 520 begins 622 call connection control.

Here, the service option is called '2' (third-party LNP), and the call control is not performed for all called numbers. Instead, the service control system (SCP) 520 is a called number number (LNP) among a plurality of called numbers. And call control is performed only for the number for which congestion control is desired. Called party number for the subscriber number is as shown in Table 2 below. Table 2 below is an example of an incoming connection line management table of the service control system (SCP) 520.

In the above [Table 2], the incoming connection line management table includes the initial line (Amax) assigned to SCP 1, the current active line assigned to SCP 1 (Acur), and the number of service control systems (SCPs) 520. Contains the number of available lines assigned to SCP 1. In addition, the incoming connection line management table includes the initial line (Bmax) assigned to SCP n, the currently active line (Bcur) assigned to SCP n, and the number of callable lines (Bneed) assigned to SCP n. In addition, the initial lines (Amax, Bmax) and the number of lines available (Aneed, Bneed) allocated for SCP processing depend on whether the service management system (SMS) 510 and the service control system (SCP) 520 are synchronized or not. Is reflected. On the other hand, the lines Acur and Bcur currently in use are not reflected depending on whether the service management system (SMS) 510 and the service control system (SCP) 520 are synchronized.

For example, if the total number of circuits assigned to SCP 1 and SCP n is 50, then the initial circuits assigned to each site are 25 and 25, which are reflected in the service management system (SMS) 510. Lines currently in use (Acur, Bcur) has an initial value of '0' and is not reflected in the service management system (SMS) 510. The number of lines available (Aneed, Bneed) is the number of lines required at each site and is reflected in the service management system (SMS) 510. Here, whether to reflect or not reflect indicates a flag for data matching between the service management system (SMS) 510 and the service control system (SCP) 520.

7 is a detailed flowchart illustrating a call control process through the management of the number of called lines according to the present invention.

First, the service control system (SCP) 520 checks the destination number to be line-controlled for the originating region to be connected (702). That is, the subscriber number is determined according to the call connection request from the caller, and the called number which needs the incoming connection line management among the plurality of registered called numbers of the corresponding subscriber number is determined and confirmed.

When the called party number to be connected is selected, the service control system (SCP) 520 checks the total number of available lines and the available number of lines for the corresponding called number currently being processed (704).

The corresponding SCP is selected from the service control systems 1 to n (SCP 1 to SCP n) (706). Here, it will be assumed that the service control system 1 is selected.

The service control system 1 checks whether the number of available lines in the service control system 1 is '0' (708).

As a result of the check 708, the service control system 1 requests the call connection to the called number to the intelligent network switch (SSP / SSW) 530, if the number of available lines is not '0' (710).

The service control system (SCP) 520 checks whether the called number connection is successful (712).

As a result of the check 712, if the incoming call number connection is successfully requested, the service control system 1, which is the SCP, decreases the number of available lines (Aneed) while increasing the value of the line (Acur) currently being used ( 714). That is, the service control system 1 (SCP 1) updates the fields of the number of lines currently being used and the number of lines available (Acur, Aneed) in the called line connection management table. Here, the DB of the service control system 1 (SCP 1) and the DB of the service management system (SMS) are updated according to the increase and decrease of the number of lines currently used and the number of lines (Acur, Aneed) that can be talked about.

When the call is terminated after the call is connected to the caller and the called party number and continues the call, the intelligent network switch (SSP / SSW) 530 reports that the call is terminated to the service control system 1 (SCP 1) (716). .

When the call termination is reported according to the process "716," the service control system 1 (SCP 1), which is the corresponding service control system, increases the number of lines available (Aneed) while decreasing the value of the current (Acur). 718). That is, the service control system 1 (SCP 1) updates the fields of the number of lines currently being used and the number of lines available (Acur, Aneed) in the called line connection management table. The DB of the service control system 1 (SCP 1) and the DB of the service management system (SMS) are updated according to the increase and decrease of the number of lines currently being used and the number of lines that can be called (Acur, Aneed).

The service control system 1 requests the intelligent network switch (SSP / SSW) 530 to terminate the call (720). Then, the intelligent network switch (SSP / SSW) 530 terminates the call connection (722).

On the other hand, if the check result 712, the incoming number connection request to the incoming call fails, the service control system 1 notifies the intelligent network switch (SSP / SSW) 530 that there is no connectable incoming line (724). Then, the intelligent network switch (SSP / SSW) 530 terminates the call connection (726).

On the other hand, the check result 708, the service control system 1 (SCP 1) checks whether the service option is '4' if the number of lines that can be called '0', that is, if there is no line that can be connected to the call (728) .

If the check result 728, the service option is 4 (e.g., congestion control or call center failure, etc.), the service control system 1 (SCP 1) to a separate agent number that can handle a separate failure specified by the customer A request is made to the intelligent network switch (SSP / SSW) 530 to connect the call (730). Then, the intelligent network switch (SSP / SSW) 530 attempts to connect a call with a congestion or a disability to a separate called number designated by the customer so that the caller terminal calls according to the corresponding scenario (732).

On the other hand, if the check result 728, the service option is not 4, the service control system 1 (SCP 1) notifies the intelligent network switch (SSP / SSW) 530 that there is no connectable incoming line (734). Then, the intelligent network switch (SSP / SSW) 530 terminates the call connection (736).

Meanwhile, a method for managing the total number of lines of the service control system 520 for processing a call based on the available line and the available line will be described in detail.

The call processing logic of the service control system 520 updates the currently used line Acur according to the line usage. The service control system 520 calculates an initial line (Amax) compared to the current number of lines (Acur) using a kind of daemon program (OLSP) in each logic every X seconds, and if the number is less than a predetermined reference value Enter a value other than '0' in (Aneed), and put '0' in 'Aneed' if it is above a predetermined threshold. For example, when the predetermined reference value is '24 / 25 ', if the initial line Amax is smaller than '24 / 25' relative to the number of lines currently used (Acur), the service control system 520 may call. Enter a nonzero value for the athlete.

The service control system 520 alternates the meta daemon program OSLP every Y minutes. For example, SCP 1 operates every 0, 10, 20 minutes, ..., etc., and SCP n operates every 5, 15, 25, ... 55 minutes. The service control system 520 readjusts the initial lines Amax and Bmax according to the number of available lines Aneed and Bneed and the initial lines Amax and Bmax. In other words, the service control system 520 performs line processing in such a manner as to adjust the number of lines available (Aneed, Bneed) as necessary.

As described above, the service control system is configured to compensate for the difference in the amount of intelligent network flows distributed and distributed through the meta daemon program (OSLP) at regular intervals, that is, the difference in the volume of incoming flows processed and processed in multiple regions. Based on the call processing change data for each service control system, the number of available lines and the initial subscription line is calculated to readjust the initial number of lines and the number of available lines.

8 is a diagram illustrating an embodiment of subscriber DB synchronization according to data change between a service control system (SCP) and a service management system (SMS) according to the present invention.

As shown in FIG. 8, the service management system (SMS) 510 includes a change data receiver 810, a change data distributor 820, a change data applicator 830, a subscriber data processing application program unit 840, A database management system (DBMS) 850 and a change data transmitter 860.

The service management system (SMS) 510 transfers data between the service control system (SCP) and the service management system (SMS) 510 by the call processing logic in the service control system 520 and changed according to the processed result. Allow the mechanism to reflect the change. Here, the service management system (SMS) 510 performs a master database function for managing subscriber data and call processing data of a plurality of service control systems (SCPs). In addition, the service management system (SMS) 510 transfers the changed data to another service control system (SCP) or handles reception.

The initial number of lines handled by Service Control System 1 (SCP 1) and the number of lines available (Aneed, Amax) must be changed and updated in real time in the database (DB) of the service control system 520, and at another site or another system. Must be passed to the same service logic.

For example, the plurality of change data receivers 810 receive the changed data from the service control system 1 (SCP 1) to the service control system n (SCP n), respectively (801).

The plurality of change data distributors 820 receive the change data received by the change data receiver 810, respectively (802) and distribute the change data to the change data applicator 830 (803).

The plurality of change data applicators 830 processes the change data distributed by the change data distribution unit 820 so that the change data related to each other may be stored, and transmits the change data to the database management system (DBMS) 850 (operation 804).

The database management system (DBMS) 850 DB triggers the change data transmitted from the change data applicator 830 according to the control 805 of the subscriber data processing application program unit 840 and stores the change data in the integrated subscriber table (806). .

The change data transmitter 860 receives the change data stored in the subscriber table (807), and transmits the changed data to the service control system 1 (SCP 1) to the service control system n (SCP n) corresponding to each site (808). .

When the change data is delivered to each site in the integrated subscriber table of the database management system (DBMS) 850, the corresponding service control system (SCP) receives the change data and changes its database.

As described above, the actual call is connected according to the call control, and the corresponding change data details are synchronized to the call processing system of another region as the number of lines and the number of lines available for the current incoming number are changed.

At this time, the change data of the service control system which is separately processed in real time with respect to the generation call distributed locally is transmitted and synchronized using subscriber data management and database trigger of the service management system managing the service control system.

9 is a flowchart illustrating an example of message processing performed in an intelligent network call processing system for incoming line management according to the present invention.

First, when the service user subscribes to the representative number service and the called number is registered as a number port number (LNP) number, the representative number, the called number line, and the type of service registered by the customer should be transmitted to the intelligent network system.

Here, the caller attempts to call the intelligent network representative number (for example, 1588-xxxx) to which the service user subscribes using the calling phone 950 (902). When a connection is attempted, the call request information triggered from the originating exchange at the caller side to the intelligent network switch (SSP / SSW) 960 includes a call request such as an intelligent network identification number 1588, a calling number and a type of the calling telephone 950. Information is included.

The intelligent network switch (SSW / SSP) 960 recognizes the intelligent network number for the representative number and initializes an initial detection operation (IDP) for requesting the representative number service to the service control system (SCP) 970 in which the service is registered. Transmit 904. Here, the initial detection operation (IDP) is an operation for requesting service start to the service control system 970 by a trigger detected by the intelligent network switch (SSP / SSW) 960.

On the other hand, the service control system 970 checks the service type of the subscriber number in the subscription information, and determines whether the call should be controlled by performing the call line management. If the call number requires call control, the service control system 970 attempts to connect to the called number if there is a number of available lines by comparing the number of incoming calls with the lake currently being processed by the service control system 970 (906). .

The service control system 970 is an intelligent network switch (SSP / SSW) 960, a call connection operation (Connect), a billing operation (FCI: Furnishment Charging Information (FCI), an event report operation (RRBE: RequestReportBCSM Event), And after the call connection, transmits a call connection information request operation (CIRQ: CallInformationRequest) that reports whether the call between the caller and the called line is terminated and the connection time thereof. That is, the service control system 970 transmits the charging operation (FCI) and the incident report operation (RRBE) together (908). Here, the event report operation (RRBE) is an operation requesting a report on a call event, such as busy or no answer, from the service control system 970 to the intelligent network switch. In particular, after a call connection, a call connection information request operation (CIRQ) for reporting whether the call between the caller and the called line is terminated and the connection time thereof is transmitted. Call connection information request operation is an essential operation for managing the number of currently connected lines and sends an event for monitoring that the call or consultation is terminated after being connected to the called number.

After the service control system 970 transmits a call connection operation, a billing operation (FCI), an incident report operation (RRBE), and a call connection information request operation (CIRQ) message, the video called number connection is attempted. The call is set up (910).

When a call is connected between the calling party and the called number, the intelligent network switch 960 reports an event report event (ERB: Event Report BCSM) to the service control system 970 (912).

The service control system 970 reported that the incoming call is connected to the caller increases the call connection count corresponding to the service control system 970 being processed in the line management table of the subscriber called party number currently monitored by '1' (914). .

Then, the call between the caller and the agent of the called number is on the connection (916), and the caller or the agent ends the call (918).

Then, the intelligent network switch 960 transmits a call connection report (CIRP) to the service control system 970 (920). The service control system 970 decreases 922 in the current call connection count corresponding to the system being processed (922).

Thereafter, since the call is terminated, according to the call termination procedure, the service control system 970 transmits a release call to the intelligent network switch 960 to automatically terminate the call (924).

On the other hand, the method of the present invention as described above can be written in a computer program. And the code and code segments constituting the program can be easily inferred by a computer programmer in the art. In addition, the written program is stored in a computer-readable recording medium (information storage medium), and read and executed by a computer to implement the method of the present invention. The recording medium may include any type of computer readable recording medium.

The present invention described above is capable of various substitutions, modifications, and changes without departing from the technical spirit of the present invention for those skilled in the art to which the present invention pertains. It is not limited by the drawings.

1 is a configuration diagram of an intelligent network system for providing a call control service;

2 is an explanatory diagram of line management of a subscriber who has been ported to a called party number of a third party through LNP;

3 is an exemplary explanatory diagram of a failure of an incoming exchange due to congestion occurring on a specific day in the prior art;

4 is a diagram illustrating an embodiment of a call line management in an IP-based VRS hosting device.

5 is a configuration diagram of an embodiment of a real-time intelligent network call processing system to which the present invention is applied;

6 is a flow chart of an embodiment of a call control method through the management of the number of called lines according to the present invention;

7 is a detailed flowchart illustrating an exemplary embodiment of a call control process through the management of an incoming line number according to the present invention;

8 is a diagram illustrating an embodiment of subscriber DB synchronization according to data change between a service control system (SCP) and a service management system (SMS) according to the present invention;

9 is a flowchart illustrating an example of message processing performed in an intelligent network call processing system for incoming line management according to the present invention.

* Explanation of symbols for the main parts of the drawings

500: data system 510: service management system

520: service control system 530: intelligent network switch

540: third party interlocking exchange 550: incoming local exchange

560: VRS Hosting Device

Claims (10)

delete In the call control method of the intelligent network service, A called line checking step of checking a called line according to a call connection request from the calling party; Determining whether to manage incoming connection line management on the identified incoming line; A line number checking step of checking the maximum number of lines previously applied, the number of lines currently being used, and the number of lines available for communication as the determination result is the incoming connection line management; A call control step of controlling a call according to the identified maximum number of previously requested lines, the number of lines currently being used and the number of lines available for call; And Synchronization step of synchronizing the change data details with other systems as the call is connected according to the call control of the call control step and the number of lines currently being used and the number of available lines are changed. Call control method of an intelligent network service comprising a. The method of claim 2, The synchronization step, Call control method of an intelligent network service for transmitting and synchronizing the change data history by using subscriber data management and database triggers. The method of claim 2, Re-adjusting the number of available lines and the initial number of lines according to the difference in the volume of incoming calls processed in a plurality of regions; Call control method of the intelligent network service further comprising. The method of claim 2, The number of lines checking step, As the result of the determination is the incoming connection line management, the maximum number of lines previously applied, the number of lines currently being used, and the number of available lines are checked using the incoming connection line management table. The incoming connection line management table, A subscriber number field indicating a representative number; A called number field indicating a called number for which incoming call line management is required; A field indicating an initial number of circuits allocated to each service control system; The number of circuits currently in use among the circuits allocated to the respective service control systems; And A field indicating the number of available lines in the lines allocated to the respective service control systems. Call control method of an intelligent network service comprising a. The method of claim 5, The call control step, If there is a available line, connecting a call to the called number; Decreasing the number of lines available for communication while increasing a value of a line currently being used in the called line connection management table according to the call connection; Increasing the number of available lines as the call is terminated while decreasing the value of the line currently being used in the called line connection management table; And If there is no available line, verify that the call is busy control and connect the call to a separate destination number specified by the customer. Call control method of an intelligent network service comprising a. The method according to any one of claims 2 to 6, The determining whether the line management, Determining whether the incoming connection line management should be performed using the subscriber state table for the identified incoming line, The subscriber state table, A subscriber number field indicating a representative number registered by the subscriber; A service status field indicating a service status of whether it is currently in service or not; And Service option fields indicating PSTN incoming LNP line management, congestion control, or IP-based incoming line management Call control method of an intelligent network service comprising a. The method according to any one of claims 2 to 5, The determining whether the line management, The call control method of the intelligent network service is determined to perform the incoming connection line management when the identified incoming line is the number of the destination line ported to another communication company. The method according to any one of claims 2 to 5, The determining whether the line management, And determining that the incoming call line management should be performed when the identified incoming line is the incoming line in which the number of calls generated by the line exceeds the number of lines compared to the preset time (congestion call). The method according to any one of claims 2 to 5, The determining whether the line management, Intelligent network service that determines that incoming call line management should be performed when the checked call line is an IP-based call line (VRS call line processing a video scenario for an IP-based video call) that is difficult to physically manage line. Call control method.

Images