KR100359450B1 - Method for linkage with SMS and multi SCP in intelligent network system - Google Patents

Abstract

The present invention relates to a method for interworking between SMS and multi-SCP for effectively managing service data distributed to each SCP when multiple SCPs are configured in an intelligent network. Allows the operator to change the information that can distinguish commonly accepted data into the MMC, and sends this request to the corresponding SCP when a data change request is received by SMS based on the above information, and the received SCP receives the data The result of the change processing is returned to the SMS, and if the data of a specific SCP is changed, the SCP notifies the SMS of the change, and referring to the above information, it is determined whether to apply only to the SMS or to apply to another SCP. If it needs to be applied to, request that SCP change data. In addition, if SCP fails to change data, SMS will retry for a certain number of times and notify the operator of the final failure.

Description

{Method for linkage with SMS and multi SCP in intelligent network system}

The present invention relates to a method of interworking between SMS and multi-SCP for effectively managing service data distributed and accommodated in each SCP when multiple SCPs are connected to an intelligent network. In particular, the present invention can register / view / delete a system accommodated by each data type. It relates to a method of interworking between SMS and multi-SCP that allows the operator to change / view the data distributed by SCP according to the distributed acceptance criteria according to the MMC (Man-Machine Command).

In general, an intelligent network system refers to equipment capable of generating and processing a service desired by a service provider.In an intelligent network, SSP (Service Switching Point), which is a switching device, and SCP (Service Control Point), which is a service control device, are network elements. And a Service Management System (SMS) as a service management device, Intelligent Peripheral (IP) as an intelligent peripheral device, and a Service Creation Environment (SCE) as a service development environment for creating and providing service logic.

1 is a block diagram illustrating a network structure of an intelligent network system in a conventional mobile communication.

As shown therein, a plurality of mobile terminal (MS) 10, a base transceiver system (BTS) 20 for transmitting / receiving messages with mobile subscribers, and a base station for managing the BTS 20 (base station) Controller (30), personal communication eXchange (PCX) 40 as an exchange station, home location register (HLR) 50 as a home location register, service switching point (SSP) 70 as an exchange device, and origination SCP (Service Control Point) 83 for storing the number for the subscriber, Service Management System (SMS) 81, which is a management system supporting SCP (83), and Intelligent Peripheral (IP), an intelligent peripheral device ( 84) and a service creation environment (SCE) 82, which is a service development environment for creating and providing service logic.

First, when the calling subscriber attempts to call the called subscriber, the mobile terminal 10 transmits a call signal to the BTS 20, and the BTS 20 performs a message transmission / reception operation with the mobile terminal 10. The call signal transmitted from the mobile terminal 10 is received.

Next, the BSC 30 manages the BTS 20, performs a message transmission / reception operation, and transmits the call signal to the PCX 40 when a call signal is input through the BTS 20.

The PCX 40 performs an operation of requesting or supplying information stored in the HLR 50, and the HLR 50 stores and manages the telephone number of the calling subscriber, and the SCP 83 is information about the user. Save subscriber's phone number.

Referring to the configuration of a general intelligent network system having such a configuration in detail as follows.

The BTS 20 provides an interface through a wired connection with a base station controller (BSC) 30 and a wireless connection between a mobile station (Personal Station) and basically moves through a wireless interface with the mobile terminal 10. Provide information about the subscriber.

The base station controller (BSC) 30 is located between the base station (BTS) 20 and the switching center (PCX) 40, the gateway / Local Communication Interconnection Network (G / LCIN), Call Control Processor (CCP), TSB It consists of a Transcoder Selector Bank and a Base Station Manager (BSM) subsystem, and performs control and hand-off of wireless and wired links.

The PCX 40 is located between the HLR 50 and the BSC 30 in the DCN and supports connection between the PCN in the DCN and the external network (PSTN, DCN, Other Network) in the DCN. It also provides basic and supplementary service functions to subscribers, and supports a database for temporary storage of subscriber information by the internally implemented visitor location register (VLR) (not shown), and access exchange subsystem (ASS: Access Switching Subsystem), Interconnection Network Subsystem (INS), and Center Control Subsystem (CCS).

The HLR 50 is a database for storing permanent subscriber information of the CDMA digital mobile communication system using the PCX 40 and CCS NO.7 common line signaling method for location registration, subscriber information management, call processing and It performs an additional service function, and consists of a BEP (Back End Processor), FEP (Front End Processor), and T1 / E1 MUX Operation Maintenance Processor (OPM).

Next, the SSP 70 is a special type of electronic exchange that connects a service user and an intelligent network. That is, the intelligent network service call is recognized from the call user's call and the SCP 83 is notified of this. Upon receiving the information necessary for processing the intelligent network service call from the SCP 83, the call is connected to the desired destination, and the call time and the called number are recorded on a disk or a magnetic tape. Usually, the existing switch 40 is used as the SSP 70 by adding a communication function with the SCP 83, an intelligent network service recognition function, and an intelligent network charging function.

Next, the SMS 81 is a management system supporting SCP 83. It manages data records of service subscribers necessary for service control, and provides the latest version of service logic and data to SCP 83. On the other hand, the service subscriber can change his or her service data using this system, and the SMS 81 is responsible for reporting various measurement data of SCP 83, service processing errors, etc., and outputting network management information. The SMS 81 usually resides in an intelligent network in the form of a separate system or connection with SCP 83 that connects SCP 83 with the public data network.

The SCP (83) has service logic and data that manages the entire process of intelligent network service processing, and usually uses a commercial computer or a special type of electronic exchange that can process a large amount of transactions in real time as an SCP. SCP (83) can provide various intelligent network services, or it can have different SCPs for each service. In addition, service logic and data in SCP 83 can be supplied with the latest version from SMS 81, if necessary.

The intelligent network in this conventional mobile communication system is composed of one SCP, and SCP and SMS each have intelligent network service data. However, if an intelligent network consists of multiple SCPs, some intelligent network service data will be common to all SCPs, some service data will be distributed and accommodated, and SMS should accommodate all service data.

Therefore, the SMS should distribute data to each SCP distributed and receive data and ensure the consistency of the data contained in each SCP for the data that is common to all SCPs. Is to accommodate all intelligent network service data, and there is a problem that cannot be handled by a 1: 1 interworking structure between SMS and SCP.

Accordingly, the present invention is proposed to solve the above problems of the prior art,

An object of the present invention is to send a request to the SCP when the data change request is received by the SMS based on the conditions to accommodate the service data set in the SCP, and the received SCP returns the result of the data change processing to the SMS, If the SCP data is changed, the SCP notifies the SMS of the change, and if it is necessary to apply only to SMS or to apply to another SCP by referring to the above information, it is necessary to apply to that SCP. By requesting data change, if an intelligent network consists of multiple SCPs, an intelligent network system provides an interworking method between SMS and multiple SCPs to effectively manage service data distributed to each SCP.

The present invention for achieving the above object,

Setting a condition for accommodating service data to each SCP from the SMS to the MMC, and determining whether the request is to create / modify / delete data from the SMS to the SCP or to request to create / modify / delete data from the SCP to the SMS;

If it is determined that the data request is from the SMS to the SCP, checking whether the received data is distributed or updated for all the SCPs;

If the check result is distributed data update, controlling to generate data from the specific SCP by transmitting a data generation request from the SMS to the specific SCP;

If the check results in updating the received data for all SCPs, SMS sends a data generation request for all SCPs to control the generation of data in each SCP;

Checking whether the data contained in the SCP is updated or if the data contained in all the SCPs is updated when the data generation / modification / deletion request from the SCP is requested by the determination result;

Updating the SMS database corresponding to the specific SCP whose data has been changed if the check result is distributed and updated data, and transmitting the result to the specific SCP;

In the case of updating the data received for all SCPs as a result of the check, the method is characterized in that it comprises a step of controlling to generate data in the corresponding SCP by sending data corresponding to any SCP by SMS.

In addition, if the SCP that receives the data update request to each SCP fails the data generation process, the SMS processing this retries a certain number of times, and if the final failure, the console of the SMS OMP (Operation Maintenance Processor) It outputs a message to (console, control panel) to notify the operator, it characterized in that the operator can take action on the failure.

1 is a block diagram showing a network structure of an intelligent network system in a conventional mobile communication,

2 is a view showing a brief configuration between the SMS and multi SCP for explaining the interworking method between the SMS and the multi SCP according to the present invention,

3 is a flowchart illustrating an interworking method between an SMS and a multi-SCP for managing service data distributed and accommodated in a plurality of SCPs in an intelligent network system according to the present invention.

<Explanation of symbols for the main parts of the drawings>

10 ..... Mobile Station (MS)

20 ..... Base Transceiver Subsystem

30 ..... Base Station Controller

40 ..... Personal Communication eXchange (PCX)

50 ..... Home Location Register

60 ..... Customer Service Billing System

70 ..... Service Switching Point (SSP)

80 ..... Intelligent Network System

81 ..... Service Management System

82 ..... Service Creation Environment (SCE)

83 ..... SCP (Service Control Point)

84 ..... Intelligent Peripheral

Hereinafter, a preferred embodiment of a method for interworking between an SMS and a multi-SCP in the intelligent network system of the present invention according to the above technical concept will be described in detail with reference to the accompanying drawings.

FIG. 2 is a diagram illustrating a brief configuration between an SMS and a multi-SCP for explaining an interworking method between the SMS and the multi-SCP according to the present invention, and FIG. 3 illustrates service data distributed and accommodated in a plurality of SCPs in the intelligent network system according to FIG. 2. This is a flow chart showing the interworking method between SMS and multi SCP for management.

As shown in this, the SMS (Service Management System) 200 manages information that can distinguish the data accommodated in common and the data accommodated distributed in each SCP (Service Control Point) (101 ~ 100 + n), This information allows the operator to register / view / delete the system accommodated by each data type, and the operator can change / view the MMC according to the distributed acceptance conditions set for the data distributed by SCP (100).

Upon receiving a data change request to the SMS 200 based on the above information, the request is sent to the corresponding SCP whose data has been changed, and the received SCP returns the result of the data change process to the SMS 200.

In addition, when only the data of a specific SCP is changed, when the SCP is notified of the changed information to the SMS 200, it is applied only to the SMS 200 by referring to the information as described above or applied to other SCP by determining whether to apply to another SCP If necessary, request the SCP to modify the data. At this time, if the SCP fails to change the data, the SMS 200 performs a retry for a predetermined number of times, and informs the operator of the final failure in case of failure.

Here, the conditions for accommodating service data to each SCP from the above-described SMS to the MMC are set as follows.

add-data-conf scp0, frp, all (save all freephone data on SCP0)

add-data-conf scp1, frp, all (save all freephone data on SCP1)

add-data-conf scp2, frp, all (save all freephone data in SCP2)

add-data-conf scp0, prepaid, mdn

(Some prepaid data is stored in SCP0, based on mdn)

add-data-conf scp1, prepaid, mdn

(Some prepaid data is stored in SCP1, based on mdn)

add-data-conf scp2, prepaid, mdn

(Some parts of prepaid data are stored in SCP2, based on mdn)

set-mdn-limit scp0, prepaid, 1000000, 3999999

(Mdn stores prepaid data in SCP0 from 1000000 to 3999999)

set-mdn-limit scp1, prepaid, 4000000, 7999999

(Mdn stores prepaid data in SCP1 from 4000000 ~ 7999999)

set-mdn-limit scp2, prepaid, 8000000, 99999999

(Mdn stores prepaid data in SCP2 from 8000000 to 999999999)

In addition, the dispersion acceptance condition may be a data generation date in addition to mdn.

Referring to Figure 3 attached to the SMS and multi-SCP interworking method having such a configuration in detail as follows.

As shown in FIG. 3, in step ST11, a condition for accommodating service data to each SCP from SMS to MMC is set, and in step ST12, it is determined whether a request is made to create / modify / delete data from SMS to SCP, and as a result, the SCP in SMS is determined. If it is a low data request, the process proceeds to step ST13. As a result, if the data request is not from the SMS to the SCP, the process proceeds to step ST23 to determine whether it is a data creation / modification / deletion request from the SCP to the SMS.

When the process proceeds to step ST13, it is checked whether the data is distributed and accommodated. As a result, if the data is requested to be distributed in SMS in step ST14, the specific SCP receives the data in step ST15. The generation process is performed and the processing result is transmitted to the SMS. The received SMS checks the data generation processing result of the SCP in step ST16. If the result is failure, the SMS retries the specific SCP in step ST17. do.

When the check result of step ST13 updates the data received for all SCPs, in step ST18, when the SMS sends a data generation request for all SCPs, all the SCPs process the data generation in step ST19 and transmit the result to SMS. If the received SMS checks the data generation processing result of all SCPs in step ST20, if all fail, retry the all SCPs in step ST21, and if the data generation fails only in the specific SCP as a result, In ST22, SMS only retries specific SCPs that fail to generate data.

Next, when the determination result of the step ST13 is a request for creation / change / deletion of data from the SCP to the SMS, it is checked whether the data is distributed or accommodated in all the SCPs in step ST24. If the data of a specific SCP is changed in step ST25, it is transmitted to the SMS. In step ST26, the SMS updates the SMS database corresponding to the specific SCP whose data has been changed, and then transmits the result to the specific SCP.

If the check result is the data update accepted for all SCPs, if the data of any SCP is changed in step ST27, it is transmitted to the SMS, and in step ST28, if the SMS requests data update to all the SCPs except the arbitrary SCPs, In step ST29, after updating data of all SCPs except for the arbitrary SCPs, the processing result is transmitted to the SMS.

Next, the SMS checks the result of the transmitted process in step ST30 and if it fails, retry the process in the SMS.

If the SMS receives a data update request to each SCP, the SCP fails to generate the data, and the SMS that processes the SMS retries a predetermined number of times, and in case of the final failure, the console of the SMS OMP (Operation Maintenance Processor) It outputs a message to (console, control panel) and notifies the operator so that the operator can take action on the failure.

Referring to Figure 2 attached to the SMS and multi-SCP interworking method having such a configuration described as an example as follows.

First, in the case of requesting data creation / modification / deletion from the SMS to the SCP, when updating distributed data,

For example, when creating a subscriber 422-8888 in the prepaid service, the SMS 200 sends a data generation request to the second SCP 102, which receives the second SCP 102 to process the data generation and send the SMS ( 200) to send the result. If the result is a failure, the SMS 200 performs a retry with the second SCP 102.

Next, when updating the data contained in all SCPs,

For example, when generating a group id 100 in the freephone service, the SMS 200 sends a data generation request to the first SCP 101, the second SCP 102, and the third SCP 103. Each SCP (101, 102, 103) processes the data generation and gives the data generation processing result to the SMS (200). If all SCP 100's processing results are unsuccessful, retries are performed to all SCPs 100, and if only second SCP 102 fails to generate data, retries are performed only to second SCP 102.

Next, in the case where the data distributed / received in the step of creating / modifying / deleting data by SMS from SCP is updated

For example, when the data of the prepaid subscriber 200-1234 of the first SCP 101 is changed, the data is transmitted to the SMS 200, and the SMS 200 updates the SMS database DB and then the first SCP 101 is updated. To pass the result.

Next, when updating the data contained in all SCPs,

For example, when the data of frp group 100 of the second SCP 102 is changed, the data is transmitted to the SMS 200, and the SMS 200, which receives the data, sends a data update request to the first SCP 101 and the third SCP ( 103). The first SCP 101 and the third SCP 103 return the data update processing result to the SMS 200, and if the processing result is unsuccessful, the SMS 200 retries again.

If the SMS 200 makes a data update request to the SCP 100 and the SCP 100 fails to generate the data, the SMS 200 processing the SMS 200 retries a predetermined number of times and finally fails. At the time of printing, a message is output to the console of the SMS operator management processor so that the operator can take action.

According to the present invention "method of interworking between SMS and multi-SCP in the intelligent network system", the service data can be managed without changing the software regardless of how many scps are added in the future intelligent network, and the service data accommodation method in the SCP Even changes (from distributed acceptance to all acceptance and all acceptance to distributed acceptance) have the advantage of being able to process service data without software changes.

Claims (5)

In the intelligent network system consisting of SMS and a plurality of SCPs, Setting conditions for accommodating service data to each SCP from the SMS to the MMC, and determining whether to request data creation / modification / deletion from SMS to SCP or data creation / modification / deletion request from SCP to SMS; If the result of the determination is a data request from the SMS to the SCP, checking whether the data is distributed and accommodated for all SCPs; If the check result is distributed data received by the SMS, sending a data generation request from the SMS to a specific SCP and controlling to generate data from the specific SCP; If the check results in updating the data received for all SCPs, the SMS controls to generate data in each SCP by sending a data generation request for all SCPs; Checking whether the data update is distributed or accommodated in all SCPs when the data generation / modification / deletion request from SCP to SMS is requested; Updating the SMS database corresponding to the specific SCP whose data has been changed if the checked result is distributed and updated data, and transmitting the result to the specific SCP; In the case of updating the data received for all SCPs as a result of the check, the step of controlling data to be generated by the corresponding SCP by transmitting data corresponding to the arbitrary SCP to the SMS and multi-system in the intelligent network system, characterized in that How to link between SCPs. The method of claim 1, wherein the controlling to generate data in the specific SCP comprises: Transmitting a data generation request from the SMS to a specific SCP; generating data from the specific SCP and transmitting the processing result to the SMS; and determining the processing result from the SMS and retrying in case of failure Interworking method between the SMS and the multi-SCP in the intelligent network system, characterized in that it comprises a step. The method of claim 1, wherein the controlling to generate data in all the SCPs comprises: Transmitting a data generation request from the SMS to all SCPs; generating data from each SCP and transmitting the processing result to the SMS; and determining the processing result from the SMS and failing the results from all SCPs. In the case of the retry with all the SCP, and if it is determined that only a specific SCP fails, and performing the retry only to the specific SCP that failed to generate data SMS and multi-SCP in the intelligent network system, characterized in that Interlocking method. The method of claim 1, wherein the transmitting of data corresponding to the arbitrary SCP by SMS to control to generate data in the corresponding SCP includes: If the data of the arbitrary SCP is changed, sending it to the SMS, and requesting data update to all the SCPs except the arbitrary SCP from the SMS which has received this; After the data update request, sending a result of processing in all SCPs except the arbitrary SCPs by SMS; And determining the processing result in the SMS that has received the processing result and performing retry in case of failure. The method of claim 1, wherein if the SMS makes a request for updating data to each SCP, and the received SCP fails to perform the data generation process, the SMS retries a predetermined number of times. Method of interworking between SMS and multi SCP in the intelligent network system, characterized in that further comprises the step of notifying the operator by outputting a message to the console (console, control panel) of the Maintenance Processor.