JP4709251B2 - Subscriber information management apparatus and subscriber information management method - Google Patents

Description

  The present invention relates to a subscriber information management device and a subscriber information management method, and more particularly to a subscriber information management device and a subscriber information management method for managing subscriber information which is information related to a subscriber.

  When changing the mobile carrier (carrier) used by a subscriber, the phone number used by the currently contracted carrier (hereinafter referred to as the relocation source carrier) It can continue to be used even after a contract with a new carrier (hereinafter referred to as the new carrier). This is called mobile phone number portability (hereinafter referred to as MNP).

In this MNP, it is important to make it possible to continue to use the services and contents used during the contract with the transfer source carrier even after the contract with the transfer destination carrier.
For this reason, there is known a technique for easily performing information transfer processing related to content distribution during carrier transfer by MNP (hereinafter referred to as MNP port-in) (for example, see Patent Document 1). There is also known a technique for handing over contents used in a mobile phone to a transfer destination carrier when changing a carrier contract (for example, see Patent Document 2).

  Here, the incoming call processing to the mobile terminal device of the subscriber who has performed MNP port-in will be described with reference to FIG. Consider a case where there are three carriers A to C as shown in FIG. In this case, when a call is made from the mobile terminal device of the carrier A subscriber to the mobile terminal device of the subscriber in which the MNP port-in from the carrier B to the carrier C is performed, the following processing is performed.

That is, when a call is transmitted from a mobile terminal device of a subscriber of carrier A (step S1), a transfer process to carrier B is performed based on the call number in the exchange of carrier A (step S2). In the carrier B as the transfer destination, access is made to a subscriber DB (Data Base), and incoming call reading processing is performed (step S3). As a result, it can be seen that the called subscriber is a subscriber who has entered the MNP port. For this reason, the signal is turned back (step S4) and transferred to the carrier C (step S5). The incoming call reading process is also performed on the carrier C (step S6). Thereafter, the incoming call processing for the destination mobile terminal apparatus is performed by the exchange (step S7).
Japanese Patent Laid-Open No. 2001-197021 JP 2007-60715 A

By the way, it is considered that customer satisfaction is improved if a special service is provided to a subscriber who has a communication contract with MNP. For example, a service in which a so-called Welcom message is transmitted to the mobile terminal device used by the subscriber at the time of MNP port-in can be considered.
However, in the above-described prior art, the subscriber with whom the communication contract is made cannot be determined by the mobile phone number portability, and only the same service as the subscriber with which the communication contract was originally made is provided.
The present invention has been made to solve the above-described problems of the prior art, and an object of the present invention is to provide a subscriber information management apparatus, a subscription, which can realize a service only for a subscriber for whom a communication contract has been made by the MNP. Is to provide a person information management method.

A subscriber information management apparatus according to claim 1 of the present invention is a subscriber information management apparatus for managing subscriber information, which is information relating to a current subscriber of the own carrier network, and makes a communication contract by mobile phone number portability. And subscriber information management means for managing the subscriber information together with identification information capable of identifying the current subscriber of the own carrier network by shifting from the other carrier network to the own carrier network (for example, FIG. 2) and service execution means for executing a service for the current subscriber that has been transferred from another carrier network to the own carrier network based on the management content of the subscriber information management means. (For example, corresponding to the subscriber DB signal processing unit 12 in FIG. 2). According to such a configuration, since it is possible to determine that a communication contract has been made based on the mobile phone number portability, it is possible to realize a service only for the subscriber.

The subscriber information management device according to claim 2 of the present invention is characterized in that, in claim 1, the identification information is flag information added to the subscriber information. By using the flag information, it is possible to determine that a communication contract has been made based on mobile phone number portability, and it is possible to realize a service only for the subscriber.
A subscriber information management device according to claim 3 of the present invention is characterized in that, in claim 1, when a mobile communication carrier can be identified by a telephone number band, the telephone number band is used as the identification information. To do. If the determination is made based on the telephone number band, it is possible to determine that the communication contract has been made based on the portable telephone number portability, and it is possible to realize a service only for the subscriber.

A subscriber information management method according to claim 4 of the present invention is a subscriber information management method for managing subscriber information, which is information relating to a current subscriber of the own carrier network, wherein a communication contract is made by mobile phone number portability. And storing the subscriber information together with identification information capable of identifying the current subscriber of the own carrier network by moving from the other carrier network to the own carrier network (for example, in FIG. (Corresponding to step S13) and a service execution step (for example, step S20 in FIG. 7) for executing a service for the current subscriber that has been transferred from the other carrier network to the own carrier network based on the storage contents in the storage step And the like. According to such a method, since it is possible to determine that a communication contract has been made based on the mobile phone number portability, it is possible to realize a service only for the subscriber.

  According to the present invention, it is possible to determine that a communication contract has been made by the MNP by storing the subscriber information together with identification information that can identify that the subscriber has made a communication contract by the MNP. Therefore, a service only for the subscriber can be realized.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the drawings referred to in the following description, the same parts as those in the other drawings are denoted by the same reference numerals.
(Configuration example of mobile communication system)
FIG. 1 is a block diagram showing a configuration example of a mobile communication system including a subscriber information management apparatus according to an embodiment of the present invention. Referring to the figure, the mobile communication system implements subscriber DB apparatus 1 which is a subscriber information management apparatus for controlling services to subscribers on a network, customer management at a window, number management, etc. A customer DB device 2 that places a service order on the subscriber DB device 1, an NW (Network) data generation device 3 that generates a message to be transmitted to the subscriber, and an exchange 4 that performs an exchange process. A radio cell 10 is formed by a radio base station (not shown). When the mobile terminal device 5 of the subscriber with whom the communication contract is made is located in the radio cell 10, the subscriber can receive the mobile communication service.
The subscriber DB device 1 corresponds to, for example, a well-known HLR (Home Location Register).

(Subscriber DB device)
FIG. 2 is a diagram illustrating a functional configuration example of the subscriber DB apparatus 1 in FIG. As shown in the figure, the subscriber DB apparatus 1 includes a subscriber information management unit 11, a subscriber DB signal processing unit 12, and an NW data management unit 13. The subscriber DB device 1 can be realized by using a known server device including a CPU (Central Processing Unit), a memory, a fixed disk device, a communication interface, and the like. Then, the subscriber information management unit 11, the subscriber DB signal processing unit 12, and the NW data management unit 13 can be realized by the CPU executing a predetermined program to control each unit of the apparatus.

The subscriber information management unit 11 manages the MNP port-in information and the transmitted status when the subscriber number for which the service order is made is not a subscriber number based on its own number band. In addition, when the transmitted status is notified from the subscriber DB signal processing unit 12, the subscriber information management unit 11 sets the transmitted status as “transmitted”.
Here, the MNP port-in information and the transmitted status can be managed as flag information. In that case, these flags may be added to the subscriber information for management. FIG. 3 is a diagram illustrating an example of one entry of subscriber information managed by the subscriber information management unit 11. For example, as shown in FIG. 5A, the MNP port-in subscriber flag 112 and the transmitted flag 113 are added to the subscriber information 111 such as the subscriber number, and the subscriber information management unit 11 manages the information. Is done. The initial value of the transmitted flag 113 is a value indicating that transmission has not been completed (that is, transmission has not been performed). A case where the initial value of the flag is not set may be defined as “untransmitted”.

  By the way, whether or not the subscriber is an MNP port-in subscriber can be determined by the subscriber number band. That is, for the subscriber number, a number band assigned to each carrier is determined. For this reason, if the number band of the subscriber number is confirmed, it can be determined whether or not the subscriber is an MNP port-in subscriber. Therefore, the MNP port-in subscriber flag 112 can be omitted from the management target. That is, as shown in FIG. 5B, only the transmitted flag 113 may be added to the subscriber information 111 for management. In this case, the number band is used as information that can identify that the subscriber has a communication contract made by the MNP.

  In this way, if the number band is confirmed, it can be determined whether or not the contract has been made by the MNP, so there is no need to provide an MNP port-in subscriber flag. However, if the determination is made based on the number band, it cannot be determined that the contract has been made by the MNP in the following cases. In other words, if the contract destination is changed from one carrier to another carrier and then returned to the original carrier, the number band is the original carrier, so it cannot be determined that the contract has been made by MNP, and the service is provided. I can't. Therefore, in order to determine the case, it is necessary to add the MNP port-in subscriber flag as shown in FIG.

Returning to FIG. 2, the subscriber DB signal processing unit 12 checks the MNP port-in subscriber flag and the transmitted flag at the time of subscriber location registration, and if not transmitted, refers to the NW data and refers to the subscriber's mobile terminal. A message by SMS (Short Message Service) is transmitted to the apparatus. Further, when the subscriber DB signal processing unit 12 receives the transmission completion notification, the subscriber DB signal processing unit 12 notifies the subscriber information management unit 11 of the transmission completion.
When the message content is read from the subscriber DB signal processing unit 12, the NW data management unit 13 reads the NW data information and transmits it to the mobile terminal device of the subscriber.

(Customer DB device)
FIG. 4 is a diagram illustrating a functional configuration example of the customer DB device 2 in FIG. As shown in the figure, the customer DB device 2 has a customer information management unit 21 that registers customer information in the subscriber DB device 1 when there is a service order. The customer DB device 2 can be realized by using a known server device including a CPU, a memory, a fixed disk device, a communication interface, and the like. And the customer information management part 21 is realizable because CPU executes a predetermined program and controls each part of an apparatus.

(NW data generator)
FIG. 5 is a diagram illustrating a functional configuration example of the NW data generation device 3 in FIG. As shown in the figure, the NW data generation device 3 has an NW data generation unit 31 for registering message contents to be transmitted as NW data to a subscriber who has entered the MNP port. The NW data generation device 3 can be realized by using a known server device including a CPU, a memory, a fixed disk device, a communication interface, and the like. The NW data generation unit 31 can be realized by the CPU executing a predetermined program to control each unit of the apparatus.

(switch)
FIG. 6 is a diagram showing a functional configuration example of the exchange 4 in FIG. As shown in the figure, the exchange 4 has an exchange signal processing unit 41 that transmits necessary information such as location registration to the subscriber DB apparatus 1 and the mobile terminal apparatus 5. The exchange 4 can be realized by using a well-known server device including a CPU, a memory, a fixed disk device, a communication interface, and the like. The exchange signal processing unit 41 can be realized by the CPU executing a predetermined program to control each unit of the apparatus.

(System operation example)
Next, an example of the operation of this system will be described with reference to FIG.
First, the contents of a message to be transmitted to a subscriber who has made an MNP port-in (hereinafter referred to as an MNP port-in user) are registered in advance in the NW data generation device 3 as NW data (step S11). Thereafter, it is determined whether there is a service order of the MNP port-in user (step S12). If there is a service order (step S12: Yes), subscriber information is stored (step S13). The subscriber number included in the stored subscriber information is confirmed (step S14).

As a result of this confirmation, if the subscriber number is a number band of a different carrier (step S15: Yes), the MNP port-in subscriber flag is set (step S16). When the subscriber number is the number band of the carrier that manages the own device, the MNP port-in subscriber flag is not set.
After that, when there is location registration by the mobile terminal device (step S17: Yes), it is determined whether the subscriber is an MNP port-in user (step S18). Whether or not the user is an MNP port-in user can be determined by checking the MNP port-in subscriber flag added to the subscriber information. Further, when the MNP port-in subscriber flag is not added, it can be determined based on the subscriber number band.

  If the subscriber is an MNP port-in user (step S18: Yes), it is determined whether the transmitted flag is set to “transmitted” (step S19). When the transmitted flag is not set to “transmitted” (step S19: No), the message registered in step S11 is transmitted (step S20). After sending this message, the sent flag is set to “sent” (step S21).

Note that if the subscriber is not an MNP port-in user in step S18 (step S18: No) and if the transmitted flag is set to “transmitted” in step S19 (step S19: Yes), the process remains as it is. End.
Furthermore, an example of the operation of this system will be described with reference to FIG.
Message contents to be transmitted to the MNP port-in user are registered in advance in the NW data generation device 3 as NW data (step S11).

When there is a service order for MNP port-in subscriber registration from the customer DB device 2 (step S12), the subscriber DB device 1 confirms the subscriber number. Then, the subscriber DB device 1 sets the MNP port-in subscriber flag when it is not the number band of the carrier that manages the own device (that is, when it is the number band of a different carrier).
When there is location registration by the mobile terminal device (step S17a), a notification of completion of the location registration process is made (step S17b), and then determination is made regarding message transmission. That is, when the MNP port-in subscriber flag is present and the message transmission completion flag is “not transmitted”, the SMS message is transmitted to the subscriber's mobile terminal device (step S19). After transmitting this message, the subscriber DB device 1 manages the transmitted flag set to “sent”, and therefore does not transmit the same message thereafter.

  As described with reference to FIG. 3A, when the MNP port-in subscriber flag is used, the MNP port-in subscriber flag is added to the input information from the customer DB device 2 to the subscriber DB device 1. Need to be. Therefore, in that case, the customer DB device 2 has a configuration different from that of the conventional device. For this reason, it is necessary to change the specifications of the customer DB device 2 together with the subscriber DB device 1.

  In contrast, as described with reference to FIG. 3B, when the MNP port-in subscriber flag is not used, the input information from the customer DB device 2 to the subscriber DB device 1 is included in the MNP port-in subscriber. There is no need to add a flag. Therefore, in that case, the customer DB device 2 can divert the device having the same configuration as the conventional one as it is. For this reason, if the specification of the subscriber DB device 1 is changed, a service for only the MNP port-in user can be realized, and there is no need to change the specification of the customer DB device 2.

(Operation sequence)
FIG. 9 is a sequence diagram showing the operation of the mobile communication system. The figure shows signals sent and received by a mobile terminal device (MT: Mobile Terminal) 5, an exchange 4, and a subscriber DB device 1.
In the figure, when the mobile terminal device 5 moves and enters the wireless cell 10, a location registration signal (Attach Request) is transmitted from the mobile terminal device 5 to the exchange 4 in order to perform location registration (step S101). . When the exchange 4 receives this location registration signal, authentication information (MAP (Mobile Application Protocol) Send Authentication info) is transmitted from the exchange 4 to the subscriber DB device 1 (step S102). When the subscriber DB apparatus 1 receives this authentication information, an authentication response (MAP Send Authentication ack) is transmitted from the subscriber DB apparatus 1 to the exchange 4 (step S103).

Then, a location registration request (MAP Update Location Request) is transmitted from the exchange 4 to the subscriber DB device 1 (step S104).
Here, when the VLR (Visitor Location Register) method is adopted, it is necessary to download a part of the location registration information to the exchange. For this reason, a subscriber data request (MAP Insert Subscriber Data Request) is transmitted from the subscriber DB device 1 to the exchange 4 (step S105). In response to this request, a subscriber data response (MAP Insert Subscriber Data Response) is transmitted from the exchange 4 to the subscriber DB device 1 (step S106).
Thereafter, a location registration response (MAP Update Location Response) is transmitted from the subscriber DB device 1 to the exchange 4 (step S107).

Next, a location registration acceptance signal (Attach Accept) is transmitted from the exchange 4 to the mobile terminal device 5 (step S108). Then, a location registration completion signal (Attach Complete) is transmitted from the mobile terminal device 5 to the exchange 4 (step S109).
In addition, the subscriber DB device 1 determines whether or not to perform information transmission based on the MNP port-in subscriber flag and the transmitted flag, and when transmitting the information, it is registered by the NW data generation device. Information is acquired (step S110). This acquired information is transmitted as a message by SMS, for example (step S111). If the message transmission is successful, the transmitted flag is changed to “transmitted” (step S112).
Note that the message in step S111 may be transmitted by a function of the device by transmitting a request from the subscriber DB device 1 to a device (not shown) for realizing SMS.

(Modification)
In the above example, the case of transmitting the Welcom message has been described, but other messages may be transmitted. For example, a warning message or an advertisement message may be transmitted. Furthermore, not only message transmission but also various services can be realized. For example, it is possible to realize services such as discounting usage fees or assigning points depending on the timing of MNP port-in. In this way, the special service can be provided to the MNP port-in user because the subscriber information is managed together with the identification information that can identify the subscriber with whom the communication contract is made by the MNP. It is.
As described above, customer satisfaction can be improved by providing a special service only to the MNP port-in user.

(Subscriber information management method)
In the mobile communication system described above, the following subscriber information management method is adopted. That is, a subscriber information management method for managing subscriber information, which is information related to the current subscriber of the own carrier network, in which a communication contract is made by mobile phone number portability, and from another carrier network to the own carrier network A storage step (for example, corresponding to step S13 in FIG. 7) for storing the subscriber information together with identification information that can be identified to identify the current subscriber of the own carrier network, and storage in the storage step A subscriber information management method including a service execution step (for example, corresponding to step S20 in FIG. 7) for executing a service for the current subscriber that has been transferred from another carrier network to the own carrier network based on the content is adopted. Has been. According to such a method, since it is possible to determine that a communication contract has been made by the MNP, it is possible to realize a service only for the subscriber.

(Summary)
According to the prior art, services provided to MNP port-in subscribers and other subscribers can be made uniform, but a special service is provided only to MNP port-in users such as sending a Welcom message. I can't. On the other hand, in the present invention, since the subscriber information is managed together with the identification information that can be identified as a subscriber with whom a communication contract has been made by the MNP, the MNP is transmitted at the time of location registration. Special services can be provided only to port-in users.

  The present invention can be used when a service is provided only to a subscriber who has a communication contract with an MNP.

It is a block diagram which shows the structural example of the mobile communication system containing the subscriber information management apparatus by embodiment of this invention. It is a figure which shows the function structural example of the subscriber DB apparatus in FIG. It is a figure which shows the example of the flag added to subscriber information. It is a figure which shows the function structural example of the customer DB apparatus in FIG. It is a figure which shows the function structural example of the NW data generation apparatus in FIG. It is a figure which shows the function structural example of the switching device in FIG. It is a flowchart which shows the operation example of a mobile communication system. It is a figure which shows the operation example of a mobile communication system. It is a sequence diagram which shows operation | movement of a mobile communication system. It is a figure which shows the incoming call process to the mobile terminal device of the subscriber in which MNP port in was performed.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Subscriber DB apparatus 2 Customer DB apparatus 3 NW data generation apparatus 4 Switch 5 Mobile terminal apparatus 10 Wireless cell 11 Subscriber information management part 12 Subscriber DB signal processing part 13 NW data management part 21 Customer information management part 31 NW data generation Unit 41 exchange signal processing unit 111 subscriber information 112 MNP port-in subscriber flag 113 transmitted flag

Claims (4)

A subscriber information management device that manages subscriber information, which is information related to the current subscriber of the own carrier network, where a communication contract is made by mobile phone number portability, and a transition from another carrier network to the own carrier network is made. Based on the management information of the subscriber information management means and subscriber information management means for managing the subscriber information together with identification information that can identify the current subscriber of the own carrier network. And a service execution means for executing a service for the current subscriber who has shifted to the own carrier network .   The subscriber information management apparatus according to claim 1, wherein the identification information is flag information added to the subscriber information.   2. The subscriber information management apparatus according to claim 1, wherein the telephone number band is used as the identification information when a mobile communication carrier can be identified by a telephone number band. A subscriber information management method for managing subscriber information, which is information related to the current subscriber of the own carrier network, where a communication contract is made by mobile phone number portability, and a transition is made from another carrier network to the own carrier network. with Te identification information capable of identifying that the current subscriber of its own carrier network, a storing step of storing the subscriber information, based on the contents stored in said storing step, transition from another carrier network to its own carrier network And a service execution step of executing a service for the current subscriber.

Images