KR100727747B1 - Method for modifying data structure of intelligent system into year/month/day and computer readable medium recording program therefor - Google Patents

Abstract

A method for changing a structure of flat rate member data into a year/month/day structure from a month/day structure in an intelligent network system and a computer-readable recording medium storing a program thereof are provided to prevent fault of a flat rate service according to year change by changing the data structure and stable change a database by managing charging records of the flat rate service simultaneously with changing the database. The database loads a flat rate service data table(S301). A charging day of the flat rate member is read from the data table and is compared with the current day(S303). In case that the charging day of the flat rate member is prior to the current day, a current year is appended to the charging day(S305). In the case that a charging month is different more than two months or the charging day is within one month, a monthly rate is charged(S313). In the case that the current day is prior to the charging day, the previous year is appended to the charging day(S317).

Description

METHOD FOR MODIFYING DATA STRUCTURE OF INTELLIGENT SYSTEM INTO YEAR / MONTH How to Change Monthly Service Data of Intelligent Network System from Month / Day Structure to Year / Month / Day Structure / DAY AND COMPUTER READABLE MEDIUM RECORDING PROGRAM THEREFOR}

1 is a block diagram of a mobile communication system for providing a voice call monthly service.

2 is a diagram showing a data table of a monthly fixed service subscriber managed by a conventional intelligent network system.

3 is a flowchart illustrating a method of managing a charging history by adding a year field to a data table of monthly subscribers in an intelligent network system according to a first embodiment of the present invention.

4 is a flowchart illustrating a method of managing a charging history by adding a year field to a data table of monthly subscribers in an intelligent network system according to a second embodiment of the present invention.

5 is a flowchart illustrating a method of managing a charging history by adding a year field to a data table of monthly subscribers in an intelligent network system according to a third embodiment of the present invention.

The present invention relates to an intelligent network system of a mobile communication network, and more particularly, to a method of changing a data structure of a monthly subscriber in an intelligent network system of a mobile communication network.

The billing method for the mobile communication service can be largely divided into a postpaid billing method and a prepaid billing method.

Postpaid billing is a method in which subscribers who have subscribed to a mobile communication service use the service for a certain period of time and then charge for the used service. Prepaid billing is a form of depositing a certain amount of money to a mobile communication service provider before using a mobile communication service, and receiving a mobile communication service within a limit of the amount of the deposit.

Recently, the monthly payment service, which has been modified from the prepaid billing method, has appeared and is gaining popularity. Monthly service is a service that uses a mobile communication service within a certain amount of limit, but bills a certain amount for post payment.

1 is a block diagram of a mobile communication system for providing a voice call monthly service.

As shown in FIG. 1, a mobile communication system providing a voice call monthly service includes a mobile communication terminal 110 using a monthly service, an exchange 130 performing voice call exchange, whether to subscribe to a monthly service, and a subscriber's location. The home location register 150 manages information, and the like, and the intelligent network system 170 performs management on a monthly fee service.

When the monthly subscriber attempts to make a call using the mobile terminal 110, the exchange 130 requests routing information to the home location register 150. Then, the home location register 150 recognizes that the subscriber is a monthly subscriber from the profile information of the calling subscriber and transmits a response message including routing information to the intelligent network system 170 accordingly to the exchange 130.

The exchange 130 receiving the response message from the home location register 150 transmits the call connection request message to the intelligent network system 170 according to the routing information included in the response message. Subsequently, the intelligent network system 170 which has received the call connection request message from the exchange 130 transmits a charge processing request message including the maximum talk time information that the subscriber can talk to to the exchange 130.

The exchange 130 receiving the charge processing request message from the intelligent network system 170 connects the call paths of the calling party and the called party. When the call is completed within the maximum call time included in the charge processing request message, the charge processing report message including the call information is transmitted to the intelligent network system 170. The intelligent network system 170 subtracts the monthly fee of the calling subscriber according to the call information included in the charging processing report message transmitted from the exchange 130. As such, when the subscriber runs out of the monthly fee in the month, the calling subscriber can no longer talk, and when the monthly fee is charged in the next month, the subscriber can call again.

In order to provide such a monthly service, the intelligent network system 170 manages data such as subscriber's monthly service subscription, charge charge date, pause state, charge charge, and the like. However, these data currently managed in the intelligent network system is managed only by months (months) and days (excluding years), causing problems in billing history management and civil complaints management. However, simply adding the year field to the database and recording the year in the year field collectively causes the following problems.

In general, the intelligent network system manages the monthly service based on the charge charging date. Therefore, if you add the year field to the database and record the year year in the year field, some of the subscribers who suspended the monthly service in the previous year and then cancel the suspension in this year will have the latest charge charging date. In the future, the monthly fee will not be charged, and the subscriber will not be able to use the monthly service.

The present invention has been proposed to solve the above problems, and a method for changing / managing data of intelligent monthly service subscribers into a structure of year / month / day and a program for realizing the method can be read by a computer. The purpose is to provide a recording medium.

Other objects and advantages of the present invention 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 for achieving the above object, as a method of changing the structure of the month / day to the structure of the year / month / day in the intelligent network system that manages the monthly service subscribers based on the charge date of the month / day structure, ( a) loading a monthly service data table from a database; (b) comparing the charging date with the current date of the monthly service subscriber recorded in the data table; (c) adding the year to the charging date if the charging date of the monthly service subscriber is before the current date; And (d) adding last year's year to the charging date if the charging date of the monthly service subscriber is after the current date.

Preferably, after the step (c), if the charge month (month) of the monthly service subscriber is different from the current month more than two months, the step of charging a monthly fee; may further include a.

Preferably, after the step (c), if the charge date of the monthly service subscriber is a month ago, the step of charging a monthly fee; may further include.

Advantageously, the current date is February 28, and after the step (c), if the charging date of the monthly service subscriber is any one of January 29, 30 and 31, charging the monthly fee It may further include;

Preferably, the current date is 30 days of the month (month) with 30 days, and after the step (c), the month of the month of the month where the charge date of the monthly service subscriber is 30 days前 月) 31 days if the charge of a monthly fee; may further include.

Preferably, after the step (d), if the monthly service subscriber is not in a suspended state, charging a monthly fee; may further include a.

In addition, the present invention is a recording medium recording a program for changing the structure of the month / day to the structure of the year / month / day in the intelligent network system that manages the monthly service subscribers based on the charging date of the month / day structure, The program includes a first function of loading a monthly service data table from a database; A second function of comparing a charging date and a current date of a monthly service subscriber recorded in the data table; A third function of adding the year to the charging date if the charging date of the monthly service subscriber is before the current date; And a fourth function of adding a last year year to the charging date if the charging date of the monthly service subscriber is after the current date.

The above objects, features and advantages will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, whereby those skilled in the art may easily implement the technical idea of the present invention. There will be. In addition, in describing the present invention, when it is determined that the detailed description of the known technology related to the present invention may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

2 is a diagram illustrating a data table of a monthly fixed service subscriber managed by a conventional intelligent network system.

As shown in FIG. 2, the monthly table service data table managed by the intelligent network system includes a subscriber telephone number field (MDN) 201, a subscription field (Regi_date) 203, and a pause status field (Status) 205. ), A refill date field (Refill_date) 207, an amount field (Amount) 209, a balance field (Remain) 211 and the like.

The subscription field 201 records the subscriber's initial monthly service subscription, the suspended status field 205 records whether the monthly service subscriber has suspended the monthly subscription service, and the recharge date field 207 charges the monthly fee. Record the date. When the subscriber is in the paused state, i.e., the amount and balance of the subscriber whose " YES " is recorded in the pause state field 205 in FIG. 2, a null value is recorded. When the pause is released, the pause state field 205 is recorded as "NO", the amount is filled in the amount field 209 again, and the balance is recorded in the balance field 211 according to the currency usage.

Meanwhile, the principle in which values are recorded in the joined field 201 and the charging date field 207 will be described below. For example, if subscriber A subscribes to a monthly fee service on June 17, 2005, and the monthly fee is charged on that day, the intelligent network system records June 17, 2005, the subscriber's membership in the join field 201. At the same time, June 17 is recorded in the charging date field 207. The amount is then recorded in the amount field 209.

Subsequently, if subscriber A continues to use the service without suspending the monthly service, the intelligent network system recharges the monthly fee of subscriber A on July 27, 2005. At this time, the intelligent network system updates the charging date field recorded as June 27 to July 27.

However, if subscriber A suspended his monthly subscription service on August 15, 2005 and released his suspension on March 15, 2006, July 27 is recorded in the recharge date field 207 and is currently Since the date is March 15, 2006, the intelligent network system recognizes the charging date as the future and cannot charge the monthly fee of subscriber A. Therefore, the year should be recorded in the filling date field 207.

The intelligent network system of a mobile communication network includes a ROM, a RAM, a CPU, an operating system, a network interface, a storage device, and a database. In this case, the database stores the data table of the monthly service subscriber as shown in FIG. 1, and the storage device changes the data structure of the monthly service subscriber as shown in FIG. 1 from month / day to year / month / day and charges the monthly service subscriber. Store the program to manage the details. The operating system of the intelligent network system runs the program to execute the routines of FIGS. 3 to 5.

3 is a flowchart illustrating a method of managing a charging history by adding a year field to a data table of monthly subscribers in an intelligent network system according to a first embodiment of the present invention.

As shown in FIG. 3, first, the intelligent network system loads a data table of a monthly service subscriber as shown in FIG. 1 from a database (S301). Then, it is determined whether the charging date is earlier than the current date by comparing the charging date of any one subscriber in the data table of FIG. 2 (S303). That is, the charging date recorded in the charging date field 207 of the subscriber in the data table of FIG. 2 is compared with the current date.

If the charging date of the subscriber is earlier than the current date, the year is added to the charging date of the subscriber (S305). As a result, the charging date of the subscriber is managed by year / month / day /. Subsequently, the intelligent network system determines whether the corresponding subscriber is in a suspended state (S307). If the subscriber is in a suspended state, the subscriber does not charge the monthly fee (S309). It will be managed as year / month / day by adding year to subscriber's recharge date, but do not charge monthly fee because it is in a suspended state.

On the other hand, when the subscriber is not in the suspended state in step S307, the intelligent network system determines whether the month of the charging date of the subscriber is more than two months from the current month (S311). If the month of recharging date is more than two months different from the current month when it is not in a pause state, the subscriber has paused the monthly service and released the pause on today's date.

If the subscriber's charging month differs from the current month by more than two months, the intelligent network system determines that the subscriber releases the suspension today and charges the monthly fee (S313). The subscriber's charging date is updated to today's date.

However, if the charging month of the subscriber in step S311 does not differ by more than two months from the current month, the intelligent network system determines whether the charging date of the subscriber is one month ago (S315). For example, if today's date of changing the database is June 27, it is determined whether the subscriber's charging date is May 27.

If the charging date of the subscriber is one month ago in step S315, the intelligent network system charges the monthly fee of the subscriber (S313). That is, since the subscriber changes the DB on the day that the monthly fee is charged, the intelligent network system charges the monthly fee of the subscriber. If the subscriber's charging date is not one month earlier, the monthly fee has already been charged on another date and the DB change is not considered today.

On the other hand, as a result of the determination in step S303, if the charging date of the subscriber is after the current date, the intelligent network system adds the last year year to the charging date of the subscriber (S317). If the charging date is after the current date, the subscriber has suspended the monthly service. With the monthly service, the month of recharge date is renewed monthly, but the date of recharge after the current date means that the month of recharge date has not been renewed.

However, even if the subscriber's charging date is later than the current date, the subscriber may cancel the current suspension of changing the DB, and the intelligent network system determines whether the subscriber has canceled the suspension (S319). That is, the pause state field 205 of the subscriber is checked in the table of FIG.

If the subscriber terminates the suspension, the intelligent network system charges the monthly fee of the subscriber (S321). The subscriber's charging date is updated to today's date. Otherwise, if the subscriber is in a suspended state, the intelligent network system does not charge the monthly fee of the subscriber (S323).

As such, when the DB change process is completed for one subscriber, steps S303 to S323 are performed for the other subscriber. This process is repeated for all the subscribers of the table of FIG.

4 is a flowchart illustrating a method of managing a charging history by adding a year field to a monthly subscriber's data table in an intelligent network system according to a second embodiment of the present invention.

As shown in FIG. 4, the intelligent network system first loads a data table of a monthly service subscriber as shown in FIG. 2 from a database (S401). In operation S403, the charging date of any one subscriber is compared with the current date in the data table of FIG. 2 to determine whether the charging date is earlier than the current date. That is, the charging date recorded in the charging date field 207 of the subscriber in the data table of FIG. 2 is compared with the current date.

If the charging date of the subscriber is earlier than the current date, the year is added to the charging date of the subscriber (S405). As a result, the charging date of the subscriber is managed by year / month / day /. Subsequently, the intelligent network system determines whether the corresponding subscriber is in a suspended state (S407). If the subscriber is in a suspended state, the monthly fee of the subscriber is not charged (S409). It will be managed as year / month / day by adding year to subscriber's recharge date, but do not charge monthly fee because it is in a suspended state.

On the other hand, when the subscriber is not in the suspended state in step S407, the intelligent network system determines whether the charging date of the subscriber is one of January 28, 29, 30, 31 (S411). If the subscriber is not in a paused state and has a charging date before January 28, the monthly fee was charged before the DB change today (that is, February 28).

If it is determined in step S411, if the charging date of the corresponding subscriber is any one of January 28, 29, 30, 31 days, the intelligent network system charges the monthly fee of the subscriber (S413). In other words, a subscriber who charged on January 28 should charge on February 28, and a subscriber who charged on January 29, 30, and 31 would have to charge on February 28 because there is no February 29, 30, or 31 days. do. Therefore, if the charging date of the subscriber is January 28, 29, 30, 31 days, the intelligent network system charges the monthly fee of the subscriber.

On the other hand, as a result of the determination in step S403, if the charging date of the subscriber is after the current date, the intelligent network system adds the last year year to the charging date of the subscriber (S415). If the charging date is after the current date, the subscriber has suspended the monthly service. With the monthly service, the month of recharge date is renewed monthly, but the date of recharge after the current date means that the month of recharge date has not been renewed.

However, even if the subscriber's charging date is later than the current date, the subscriber can cancel the current suspension of changing the DB, and the intelligent network system determines whether the subscriber has canceled the suspension (S417). That is, the pause state field 205 of the subscriber is checked in the table of FIG.

If the subscriber terminates the suspension, the intelligent network system charges the monthly fee of the subscriber (S419). The subscriber's charging date is updated to today's date. Otherwise, if the subscriber is in a suspended state, the intelligent network system does not charge the monthly fee of the subscriber (S421).

As such, when the DB change process is completed for one subscriber, steps S403 to S421 are performed for the other subscriber. This process is repeated for all the subscribers of the table of FIG.

FIG. 5 is a flowchart illustrating a method of managing a charging history by adding a year field to a monthly subscriber's data table in an intelligent network system according to a third embodiment of the present invention. This is the case. For example, changing the DB on April 30.

As shown in FIG. 5, the intelligent network system first loads the data table of the monthly service subscriber as shown in FIG. 2 from the database (S501). In operation S503, it is determined whether the charging date is earlier than the current date by comparing the charging date of any one subscriber with the current date in the data table of FIG. 2. That is, it is determined whether the charging date recorded in the charging date field 207 of the subscriber in the data table of FIG. 2 is before April 30.

If the charging date of the subscriber is earlier than the current date, the year is added to the charging date of the subscriber (S505). As a result, the charging date of the subscriber is managed by year / month / day /. Subsequently, the intelligent network system determines whether the corresponding subscriber is in a suspended state (S507). This is done by checking the pause state field 205 in FIG. If the subscriber is in a suspended state, the subscriber does not charge the monthly fee (S509). It will be managed as year / month / day by adding year to subscriber's recharge date, but do not charge monthly fee because it is in a suspended state.

On the other hand, if the subscriber is not in the suspended state in step S507, the intelligent network system determines whether the charging month of the subscriber is different from the current month more than two months (S511). If the charge month differs from the current month by more than two months when it is not paused, the subscriber has paused the monthly fee service and released the pause on today's date.

If the subscriber's charging month is more than two months different from the current month, the intelligent network system determines that the subscriber has released the pause today and charges the monthly fee (S513). The subscriber's charging date is updated to today's date.

However, when the charging month of the subscriber does not differ from the current month by more than two months in step S511, the intelligent network system determines whether the charging date of the subscriber is one of 30, 31 (S515). For example, if today's date of changing the DB is April 30, it is determined whether the subscriber's charging date is one of March 30 and 31.

If, in step S515, the charging date of the corresponding subscriber is any one of 30 days and 31 days, the intelligent network system charges the monthly fee of the corresponding subscriber (S513). For example, a subscriber who charged on March 30 must charge on April 30, and a subscriber who charged on March 31 must charge on April 31. However, since April has 31 days, subscribers whose March 31 is the charging date will be charged on April 30.

On the other hand, as a result of the determination in step S503, if the charging date of the subscriber is after the current date, the intelligent network system adds the last year year to the charging date of the subscriber (S517). If the charging date is after the current date, the subscriber has suspended the monthly service. With the monthly service, the month of recharge date is renewed monthly, but the date of recharge after the current date means that the month of recharge date has not been renewed.

However, even if the subscriber's charging date is later than the current date, the subscriber can cancel the today's suspension of changing the DB, and the intelligent network system determines whether the subscriber's suspension has been terminated (S519). That is, the pause state field 205 of the subscriber is checked in the table of FIG.

If the subscriber terminates the suspension, the intelligent network system charges the monthly fee of the subscriber (S521). The subscriber's charging date is updated to today's date. Otherwise, if the subscriber is in a suspended state, the intelligent network system does not charge the monthly fee of the subscriber (S523).

When the DB change process is completed for one subscriber, steps S503 to S523 are performed for the other subscriber. This process is repeated for all the subscribers of the table of FIG.

As described above, the method of the present invention may be implemented as a program and stored in a recording medium (CD-ROM, RAM, ROM, floppy disk, hard disk, magneto-optical disk, etc.) in a computer-readable form. Since this process can be easily implemented by those skilled in the art will not be described in more detail.

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.

The present invention as described above, by changing the monthly service subscriber data from the month / day structure to the year / month / day structure, there is an effect that can prevent the monthly service failure due to the year change. In addition, the present invention has the effect of enabling a stable database change by changing the database in the intelligent network system and simultaneously manage the charge history of the monthly payment service.

Claims (7)

A method of changing the structure of the month / day to the structure of year / month / day in an intelligent network system that manages monthly service subscribers based on a charging date of a month / day structure, (a) loading a monthly service data table from a database; (b) comparing the charging date with the current date of the monthly service subscriber recorded in the data table; (c) adding the year to the charging date if the charging date of the monthly service subscriber is before the current date; And (d) adding last year to the charging date if the charging date of the monthly service subscriber is after the current date; and changing the data structure of the monthly subscriber in the intelligent network system. The method of claim 1, After step (c), (c-1) charging a monthly fee if the monthly charge of the monthly service subscriber is different from the current month by more than two months; further comprising the step of changing the data structure of the monthly subscriber in the intelligent network system . The method of claim 1, After step (c), and (c-1) charging a monthly fee if the charging date of the monthly service subscriber is one month ago. The method of claim 1, The current date is February 28, After step (c), (c-1) if the charging date of the monthly service subscriber is any one of January 29, 30 and 31, charging a monthly fee; changing the data structure of the monthly subscriber in the intelligent network system further comprising: Way. The method of claim 1, The current date is 30 days of the month (30) day number, After step (c), (c-1) charging a monthly fee if the charging date of the monthly service subscriber is 31 days in the previous month of the month of which the number of days is 30 days; monthly payment subscribers in an intelligent network system further comprising: To change the data structure of a file. The method according to any one of claims 1 to 5, After step (d), (d-1) if the monthly service subscriber is not in a suspended state, charging a monthly fee; the method of changing the data structure of the monthly subscriber in the intelligent network system, further comprising. A recording medium recording a program for changing the structure of the month / day to the structure of the year / month / day in an intelligent network system that manages a monthly service subscriber based on a charging date of a month / day structure, A first function of loading a monthly service data table from a database; A second function of comparing a charging date and a current date of a monthly service subscriber recorded in the data table; A third function of adding the year to the charging date if the charging date of the monthly service subscriber is before the current date; And And a fourth function of adding a last year to the charging date if the charging date of the monthly service subscriber is after the current date.

Images