The method of managing subscriber location information in mobile communication system
The present invention relates to the method for managing subscriber location information in mobile communication system.When moving to another place, a mobile subscriber to carry out enroll in notifications from visitor location register (after this being designated as VLR) to Home Location Register (HLR).Under request enroll in notifications and relevant same user's the overlapping situation of call processing program, the relevant same user's of protection multiposition registration before HLR enroll in notifications is in front finished.Therefore, the present invention relates to managing subscriber location information in mobile communication system, so that always correctly keep method about a HLR and a VLR positional information.
Use the digital mobile communication system of CDMA (code division multiple access) to generally comprise a Home Location Register (HLR) and a visitor location register (VLR).HLR has the database of an extra-service information that is used for managing relevant a plurality of certain user of mobile subscriber, positional information etc.Mobile switching centre use the VLR retrieval process from/to the information of the calling in the zone that the user is visiting.Therefore, HLR should keep relevant a plurality of users' accurate information.And HLR also should be only keep temporary information among the VLR separately, and temporary information is according to user's mobile generation in VLR.
But, in current mobile communication standard (IS-41-C), do not have regulation about concrete condition.Therefore, when other mobile network user attempts to call out,, HLR often breaks because can not correctly providing user profile.
Fig. 1 is the flow chart that shows a normal mobile subscriber's enroll in notifications (RN) program.It shows a travelling carriage (MS1), and a service system district (wherein having one first visitor location register VLR1) moves to the new service system district situation of (wherein having one second visitor location register VLR2) from the front.
When VLR2 senses MS1 and moves according to MS1 after the enroll in notifications that HLR sends a MS1 is called (RNI) message (ST1), HLR upgrades and the position of store M S1 in database.Here, VLR1 has the user record of a MS1.Therefore, the positional information (ST2) of HLR request VLR1 deletion MS1.Next, the VLR1 deletion is stored in the user record of the MS1 in the current database, and sends registration cancellation return results (RCRR) message (ST3) of MS1 to HLR.After receiving delete position message, HLR sends enroll in notifications return results (RCRR) message (ST4) of MS1 to VLR2.Therefore, VLR2 can produce the user record of a MS1 in database.
Fig. 2 is the flow chart that shows a mobile subscriber's call processing program.Ask the called party's of hope travelling carriage (SM2) to be called out at the MS of calling party, and MS2 is under the situation in other service system district, and Fig. 2 shows the mobile switching centre (MSC) of a calling party and the program between a HLR and the called party mobile switching centre (MSC1).
When the MS of calling party request MS2 called out, the MSC of the correspondence of the MS of calling party sent position requests (LR) message (ST11) of a MS2 to HLR.The HLR that receives LR message from MSC passes through route requests (RR) message of the VLR1 of MS2 to a MS2 of the MSC1 of correspondence transmission, so that know the routing information (ST12) of MS2.Called party's MSC1 receives RR message and distributes routing information TLDN (interim local directory number).At this moment, VLR1 has the user record of a MS2.Under the situation of the TLDN that receives MS2, MSC1 sends route requests return results (RRRR) message (ST13) of MS2 to HLR.The HLR that receives RRRR message sends position requests return results (LRRR) message (ST14) of a MS2 to the MSC of calling party.
Below explanation has the call processing program of a mobile subscriber under the situation of incorrect information of MS2 of unknown cause at HLR.
At first, the MSC of calling party is to the location request message of HLR transmission MS2, shown in Fig. 2 below (ST21).HLR sends a route requests (RR) message to the VLR1 of MS2, so that know the positional information (ST22) of MS2.Here, VLR1 does not have the user record of MS2.Therefore, VLR1 is to route requests (RR) error message of error code of HLR transmission and MS2, and wherein error message points out that this user can not be identified (ST23).
Here, HLR removes the customer position information (ST24) that is stored in the HLR database.Then, HLR sends position requests return results (LRRR) message that has the rejection cause parameter of MS2 to the MSC of calling party.As a result, call failure.
Move under the situation of a new service area at travelling carriage (MS3), user position information is deposited with at least respectively among two VLR.To in Fig. 3 of enroll in notifications (RN) flow process that shows a mobile subscriber, describe now it.
When a travelling carriage (MS3) moved to a new service area, the VLR2 in the new service area sensed MS3, and first enroll in notifications that request HLR carries out MS3 is called (RNI) (ST1).HLR upgrades the position of MS3, and with former location storage in database.Here, VLR1 still has the user record of MS3.Therefore, HLR request VLR1 carry out MS3 registration cancellation (RC) (ST2).
But, carrying out at VLR2 request HLR under the situation of the 2nd RNI (ST3), HLR answers an enroll in notifications request (RNR) and does not carry out any registration cancellation (RC) program, because it is also from the current service system.Therefore, HLR sends second enroll in notifications return results (RNRR) message (ST4) of a MS3 to VLR2.As a result, in VLR2, generate the user record of a MS3.
In addition, taking owing to MS3 or other reason is not carried out HLR under the situation of the registration cancellation request (RCR) of VLR1 request MS3, VLR1 sends registration cancellation return results (RCRR) message (ST5) that has refusal cancellation parameter to HLR.Because the RCR of MS3 is rejected, the positional information of HLR restore database, and send one the one RNRR message that has according to receiving cause parameter to VLR2, so that provide the position (ST6) of depositing MS3 again among the VLR1 of former service system therein.
When in step (ST2 or ST5), answering information dropout, operate HLR in the same manner.Although first enroll in notifications (RN) of MS3 failure, the database of VLR2 be by asking the 2nd RN (ST3) to have the user record of MS3, and the user record that is based upon in the database of VLR1 is not cancelled yet.As a result, visitor location register VLR1, VLR2 have the user record of MS3.
For the same reason, when other mobile subscriber attempted to call out, because HLR and VLR have the information of incorrect relevant relative users, HLR can not carry out normal call treatment.
Fig. 4 shows the signal processing flow of misconstruction.When a travelling carriage (MS4) moves to another service area, under the overlapping situation of the call processing program that Fig. 1 enroll in notifications (RN) extremely shown in Figure 2 and relevant same mobile subscriber occur, may make a mistake.
Move at MS4 under the situation of a new service area, VLR2 senses MS4 and calls (RNI) (ST31) to HLR request enroll in notifications.HLR upgrades the position of MS4 and the position before the storage in database.VLR1 has the user record of a MS4.Then HLR request VLR1 carry out MS4 registration cancellation (RC) (ST32).Therefore VLR1 deletes the user record of MS4.
Here, when normally having deleted the user record of MS4 in VLR1, VLR1 sends registration cancellation return results (RCRR) message (ST38) to HLR, and wherein the user record of this message informing MS4 is deleted.HLR finally sends enroll in notifications return results (RNRR) message (ST39) of VLR2 request to VLR2.And VLR2 produces the user record of MS4 in database.
But, there is such a case, the position requests of above-mentioned same MS4 (LR) message is (ST33) that sent from a mobile switching centre (MSC) that does not ask enroll in notifications (RN) before request is normally finished from the RN of VLR2.In these cases, because the positional information that is stored in the respective user in the HLR database has been updated to the information of new service system, HLR attempts to receive interim local directory number (TLDN) (ST34) by send a route requests (RR) message to a new service system.But, owing to the RN of MS4 just handles in current new service system, so VLR2 does not have the user record of corresponding MS4.Therefore, VLR2 sends the answer (ST35) of the RR error message of MS4 as RR to HLR.Subsequently, the HLR that the receives error message customer position information (ST36) of MS4 in storehouse that clears data.Next, HLR sends position requests return results (LRRR) message (ST37) to MSC.
, have another kind of situation here, the position requests of MS4 (LR) message is (ST40) that sends to HLR by the call signal request of above-mentioned same MS4 from a MSC.In this case, HLR has removed the positional information of MS4 by receiving route requests (RR) error message in step (ST36).As a result, HLR does not have the customer position information of MS4, therefore sends position requests return results (LRRR) message that has MS4 rejection reason by the corresponding M SC to request position information and makes call failure (ST41).
In addition, move at MS4 under the situation of another service area (as the explanation of example, MS4 moves in the district of a VLR1 management by accompanying drawing), VLR1 calls (RNI) message (ST42) to the enroll in notifications that HLR sends MS4.
But, because the customer position information of MS4 is eliminated in HLR database, thus not to before the VLR2 of service area registration cancellation (RC) request is proposed.And by send enroll in notifications return results (RNRR) message of MS4 to VLR1, VLR1 produces the user record of a MS4 in the VLR1 database.
VLR2 has had the user record of MS4, thereby move to a service area with active user record (by accompanying drawing as an example explanation at MS4, MS4 moves in the district of VLR2 management) situation under, enroll in notifications (RN) request is not proposed to HLR.Therefore, because HLR is just managing the incorrect customer position information of a MS4, so when other mobile subscriber attempts to call out, fail easily.
In these cases, corresponding travelling carriage (MS) user can't find the reason of broken string except call mobile communication company.And VLR operator should select and delete user record useless in the VLR database.But settling mode as described above is not basic solution, and may continue to take place same problem.
Consider the problems referred to above, first purpose of invention is will be by moving under the situation in other district from previous service area at a travelling carriage, when two VLR request HLR deposit notice when overlapping, only in single VLR, keep same user's correct temporary information and solve problem in the method for managing subscriber location information in the above-mentioned mobile communication system by a HLR.
Second purpose of the present invention be to provide a kind of in mobile communication system the method for managing subscriber location information, wherein when same user's enroll in notifications (RN) and call processing program overlapped, HLR kept the current tram of respective user.
According to an embodiment who finishes first purpose of the present invention, a kind of in mobile communication system the method for managing subscriber location information comprise: before a travelling carriage (MS) moves to during service area, in a HLR, carry out the corresponding enroll in notifications (RN) of MS, and point out enroll in notifications (RN) present; Process with the multiposition registration that in enroll in notifications (RN) processing procedure, prevents relevant same user.
According to another embodiment that finishes first purpose of the present invention, a kind of in mobile communication system the method for managing subscriber location information comprise: when a MS moves to a new service area, in a HLR, carry out the corresponding enroll in notifications (RN) of MS, and point out that in a corresponding VLR this enroll in notifications (RN) handles; With the processing procedures such as multiposition registration that in enroll in notifications (RN) processing procedure, prevent about same user.
According to another embodiment that finishes second purpose of the present invention, a kind of in mobile communication system the method for managing subscriber location information comprise: when a MS moves to a new service area, in a HLR, carry out the corresponding enroll in notifications (RN) of this MS and indicate during enroll in notifications (RN) handling; Before enroll in notifications in front (RN) is deleted, in depositing the position process, ignore about same user's multiposition registering signal with from the processing procedure of the call processing signal of a board.
According to the 4th embodiment that finishes second purpose of the present invention, a kind of in mobile communication system the method for managing subscriber location information comprise: when a MS moves to a Qu Zhongshi that new service system is provided, in a HLR, carry out the corresponding enroll in notifications (RN) of MS and in a corresponding VLR, indicate enroll in notifications (RN) to handle; Before enroll in notifications in front (RN) is deleted, deposits and ignore in the process of position about same user's multiposition registering signal with from the processing procedure of the call processing signal of a board.
By can better understanding being arranged to the present invention and using method thereof and advantage to the explanation of embodiment, wherein below with reference to accompanying drawing:
Fig. 1 is the flow chart that shows a mobile subscriber's enroll in notifications program;
Fig. 2 is the flow chart that shows a mobile subscriber's call processing program;
Fig. 3 is the flow chart of a mobile subscriber's of explanation the error situation of positional information difference repeated storage in plural VLR;
Fig. 4 is the flow chart of explanation issuable mistake when an enroll in notifications and the call processing program about the same mobile subscriber of Fig. 1 to Fig. 2 carry out superimposedly;
Fig. 5 is the flow chart that shows one embodiment of the present of invention of the mistake that prevents Fig. 3;
Fig. 6 explains to prevent it also is the flow chart of the program of contingent misoperation in the embodiment of Fig. 5;
Fig. 7 is the flow chart that shows an alternative embodiment of the invention of the mistake that prevents Fig. 4;
Fig. 8 is that explanation prevents it also is the flow chart of the program of contingent misoperation in the embodiment of Fig. 7; With
Fig. 9 shows the flow chart be used for keeping at a HLR and VLR in a mobile subscriber enroll in notifications processing procedure another embodiment of the present invention of a tram information.
Below by with reference to being described in detail corresponding to Fig. 5 to the 9 pair of method of the present invention of each embodiment of the present invention.
Fig. 5 illustrates the flow chart of the method for management one customer position information in mobile communication system according to one embodiment of present invention.It has prevented that a mobile subscriber's positional information is deposited with respectively the plural VLR MS5 moves to the situation of a new service area from previous service area under.
In the drawings, MS5 moves to a new service area from previous service area.A corresponding visitor location register (after this, one second visitor register is designated as VLR2) of new service area senses MS5 and calls (RNI) message (ST11) to first enroll in notifications of a MS5 of HLR transmission.HLR upgrades the position of MS5 and the position before the storage in database.Here, the visitor location register of front (after this, one first visitor location register is designated as VLR1) has the user record of MS5.Therefore, HLR receives an enroll in notifications and calls (RNI) message, and the enroll in notifications pending status sign (RNPF) that MS5 was set before enroll in notifications (RN) is finished is " 1 ", and wherein this sign forms in HLR database.And HLR sends registration cancellation return results (RCRR) message (ST13) of a MS5 to VLR1., pointed out that HLR carries out a kind of like this state of enroll in notifications (RN) of MS5 now here, wherein this state is that enroll in notifications pending status sign (RNPF) is set to the state of " 1 ".Therefore, enroll in notifications pending status sign (RNPF) place value of MS5 change into relevant all other RNI that " 0 " produce before all by HLR as fault processing.
Because enroll in notifications pending status sign (RNPF) place value of the MS5 in HLR database is set to " 1 ", so HLR sends an error message to the VLR2 that carries out the second enroll in notifications return results (RNRR).As a result, in VLR2, do not produce the user record of MS5.
In addition, when from HLR to the registration cancellation return results (RCRR) of the MS5 of VLR1 request since MS that the line is busy and so on is former thereby when not carrying out, the registration cancellation return results (RCRR) that VLR1 sends a cancellation refusal parameter that has a MS5 or error message to HLR is (ST17).Therefore, HLR receives the registration cancellation return results (RCRR) of the error message that has cancellation refusal or MS5, and enroll in notifications pending status sign (RNPF) place value is changed into " 0 ".Then, HLR sends first enroll in notifications return results (RNRR) message (ST19) of a MS5 to VLR2.As a result, in VLR2, do not produce the user record of MS5.
Even VLR2 request enroll in notifications (RN) overlaps among the same MS, HLR only handles significant enroll in notifications and calls (RNI) message.Therefore, HLR and VLR2 always can correctly keep the positional information of a MS.
Fig. 6 is one and is used to prevent that HLR from the operational flowchart of Management flag mistake taking place.
In Fig. 6, when making the enroll in notifications pending status sign (RNPF) that is stored in the HLR database remain " 1 " (ST21) owing to mistake.And move to from previous service area other new district under the situation at MS6, by sensing MS6, VLR2 calls (RNI) message to first enroll in notifications that HLR sends a MS6.At this moment, the enroll in notifications pending status sign (RNPF) of current database is set to " 1 ".Therefore, HLR compares up-to-date enroll in notifications time and the current time of MS6, still is provided with place value mistakenly so that determine to carry out enroll in notifications (RN).After comparison, if do not surpass the predetermined constant time (for example this time is set to 6 seconds in the present embodiment), HLR determines that enroll in notifications (RN) operating and keep enroll in notifications pending status sign (RNPF), and the enroll in notifications that produces is just now called (RNI) is treated to mistake.Otherwise if surpassed the predetermined constant time, HLR determines that flag management is wrong, enroll in notifications pending status sign (RNPF) is made zero, and the enroll in notifications that has normally just produced is called (RNI) (ST23).Then, HLR upgrades the positional information of MS6, and the position before storing in database.At this moment, VLR1 has the user record of a MS6.Therefore, HLR is before finishing up to enroll in notifications (RN) operation, and enroll in notifications pending status sign (RNPF) place value in the HLR HLR database is set to " 1 ".And HLR sends registration cancellation return results (RCRR) message (ST25) of MS6 to VLR1.Here, be set under the situation of " 1 " at enroll in notifications pending status sign (RNPF), change into " 0 " before in enroll in notifications pending status sign (RNPF) value, the enroll in notifications that all are extra is called (RNI) message as fault processing.
But, there is such situation, VLR2 calls (RNI) message (ST26) because specific reasons sends one second enroll in notifications to HLR.Because the enroll in notifications pending status sign (RNPF) in database is set to " 1 ", enroll in notifications (RN) message of HLR request for the second time is as fault processing (ST27), and the second enroll in notifications return results (RNRR) that sends the error message with MS6 to VLR2 subsequently (ST28).Therefore, in VLR2, do not generate the user record of a MS6.
In addition, since MS that the line is busy and so on is former thereby make the registration cancellation of MS6 call (RCI) when being rejected, VLR1 sends registration cancellation return results (RCRR) message (ST29) of a MS6 to HLR.(RCI) called in the registration cancellation of MS6 to be asked to VLR1 from HLR.Therefore, under the situation of registration cancellation return results (RCRR) message that receives MS6, HLR changes into " 0 " to enroll in notifications pending status sign (RNPF) place value, so that notify current enroll in notifications (RN) to finish.HLR sends first enroll in notifications return results (RNRR) message (ST31) of a MS6 to VLR2.As a result, in VLR2, do not produce the user record of a MS6.
Fig. 7 is a flow chart according to another embodiment of the invention.It shows when overlapping about same mobile subscriber's enroll in notifications (RN) program and call processing program how to prevent that same mobile subscriber is retained among the plural VLR.
Under MS7 moved to situation in other new service area, the VLR2 of new service sensed MS7 and calls (RNI) (ST51) to HLR request enroll in notifications.HLR upgrades the positional information of MS7, and former positional information is stored in the database.VLR1 has the user record of MS7.As a result, before enroll in notifications (RN) was finished, HLR was set to " 1 " to the enroll in notifications pending status sign (RNPF) in the HLR database (ST52).And HLR points out that enroll in notifications (RN) is being operated and cancels return results (RCRR) message (ST53) to the registration of a MS7 of VLR1 transmission.
Have such a case, before the enroll in notifications (RN) of request was normally finished, the location request message of relevant same MS7 sent to HLR (ST54) from another MSC, and wherein this MSC does not ask enroll in notifications (RN).In this case, the customer position information that is stored in the HLR database has been changed to a new service system.Therefore, HLR sends a route requests to new service system, and attempts to receive TLDN (ST55).
But because from enroll in notifications (RN) present of new service system request, VLR2 does not have that corresponding M S7's use the corpse record.Therefore, VLR2 route requests (RR) error message (indicate a Unidentified MIN) conduct from a MS7 to HLR that send is returned mistake (ST56) about route requests (RR) message.
Because after the error message that receives about route requests, current enroll in notifications pending status sign (RNPF) place value is " 1 ", so HLR does not remove the positional information (ST57) of MS7.Then, HLR is to the return results message (ST58) of MSC transmission position requests, call failure.Sending a registration cancellation return results (RCRR) afterwards from VLR1 to HLR, HLR changes into " 0 " with enroll in notifications pending status sign (RNPF) place value, and point out that enroll in notifications (RN) finishes, and send enroll in notifications return results (RNRR) message and subscriber profile information to VLR2, wherein enroll in notifications pending status sign (RNPF) is in HLR database.As a result, in VLR2, produce the user record (ST60) of a MS7.
At this moment, have a kind of situation, the location request message of MS7 sends to HLR from other mobile switching centre (not shown), by it produced same MS7 by the call signal request, shown in the below of Fig. 7 (ST61).In this case, because HLR does not have the positional information of removing about the MS7 in the HLR database in step (ST57), so HLR has the positional information of MS7.Therefore, send route request information so that under the situation of the positional information (ST62) of acquisition MS7 at HLR to VLR2, VLR2 sends route requests return results (RRRR) message (ST63) of a MS7 to HLR.
In addition, under the situation of the service area before MS7 moves to (or move to other service system, present embodiment is that the situation that MS7 moves to former service area is again described), VLR1 sends the enroll in notifications of MS7 and calls (RNI) message (ST65).HLR does not have to remove the customer position information that is stored in the database.Therefore, HLR calls (RCI) message and deletes the user record that VLR2 is stored in the MS7 in the VLR2 database to the registration cancellation that VLR2 sends MS7, and sends corresponding registration cancellation return results (RCRR) message (ST67) to HLR.Therefore, HLR sends enroll in notifications return results (RNRR) message of MS7 to VLR2.As a result, VLR1 produces the user record of a MS7.
Thereby the positional information of current MS7 can correctly remain on HLR and only among the VLR (VLR1 or VLR2).
Fig. 8 shows explanation prevents from how to prevent in the wrong operating process that produces the flag management misoperation under the superimposed situation of the enroll in notifications (RN) of Fig. 7 and call processing program flow chart.
Have such a case, when making HLR enroll in notifications pending status sign (RNPF) remain " 1 " owing to unknown cause, MSC sends the location request message (ST71) of a MS8 to HLR.HLR sends the route request information (ST73) of MS8 to VLR2.But VLR2 does not have the user record of MS8.VLR2 sends route requests return results (RRRR) error message (ST74) of a MS8 to HLR.Enroll in notifications pending status sign (RNPF) place value in the HLR database is " 1 ".Therefore, whether HLR is by having surpassed the predetermined constant time (6 seconds) to the up-to-date enrollment time of MS8 and current time audit by comparison up-to-date enrollment time.After having surpassed the constant time, HLR removes the customer position information (ST75) that is stored in the HLR database, and sends position requests return results (LRRR) message (ST76) of MS8 to MSC.
Here, send to HLR in other MSC (not shown) under the situation of location request message of MS8, HLR sends position requests return results (LRRR) message (ST77) to the MSC that sends location request message, and wherein position requests return results (LRRR) message informing does not have the routing iinformation of MS8.
In addition, under the situation of the service area before MS8 moves to, the VLR1 of respective area sends the enroll in notifications of a MS8 and calls (RNI) message (ST79).And HLR is stored in the customer position information of MS8 in the database and to VLR1 and sends enroll in notifications return results (RNRR) message and do not ask the registration of other VLR to cancel (RC) (ST80).As a result, VLR1 has generated the user record of a MS8.
Fig. 9 is the flow chart of the method for explanation managing subscriber location information.It shows the enroll in notifications pending status sign of finishing among the HLR that has finished in above-mentioned each embodiment (RNPF) and is provided with/makes zero and utilize the pending status sign to be provided with/to make zero to prevent the wrong operation that produces in a VLR.Its explanation: in enroll in notifications (RN) process of a travelling carriage (MS9), HLR and former visitor location register (VLR1) and current accessed person's location register (VLR2) keep correct positional information.Should understand that Fig. 5 extremely each embodiment shown in Figure 8 illustrates following operation.
As shown in Figure 9, move under the situation of other new service area from a service area of front at MS9, corresponding VLR2 senses MS9 (ST91), enroll in notifications pending status sign (RNPF) is set (ST92) and to the enroll in notifications of a MS9 of HLR transmission calls (RNI) message (ST93) for " 1 ".Here, VLR1 has the user record of a MS9, and HLR upgrade the position of MS9 and store M S9 with the front position.
Then, the position that HLR identifies MS9 changes, and therefore sends registration cancellation return results (RCRR) message (ST94) to VLR1, and waits for its answer.Under the situation of answering the position of a mobile switching centre (MSC) request MS9 during the wait state, HLR to VLR2 send a route request information (ST95, ST96).
But owing to the answer that does not receive about current enroll in notifications (RN), VLR2 does not have user record in database.In addition, VLR2 enroll in notifications pending status sign (RNPF) is set to " 1 ".
Therefore, VLR2 also sends " operator sequencing problem mistake " message as the route requests return results (RRRR) of MS9 (ST97) except sending " unidentified MIN mistake " message.Thereby HLR does not remove user profile and sends position requests return results (LRRR) (ST98) to MSC.As a result, HLR can keep a right user information.
Next, as HLR (ST99) when VLR1 receives registration cancellation return results (RCRR) message of MS9, HLR sends enroll in notifications return results (RNRR) message (ST100) that return results (RCRR) is cancelled in this registration to VLR2.In this case, VLR2 produces the user record of a MS9 in database, and enroll in notifications pending status sign (RNPF) is changed into " 0 " (ST101).As a result, VLR2 points out finishing of enroll in notifications, and helps another enroll in notifications (RN) and call treatment normally to carry out.
As mentioned above, when a mobile subscriber when a service area of front moves to a new service area, even single VLR asks the enroll in notifications (RN) (or two VLR ask enroll in notifications (RN) respectively) of single MS overlappingly, HLR also can only keep user's a current location information.
In addition, under the situation that same user's enroll in notifications (RN) and call processing program overlaps, the present invention can correctly keep same user's temporary information in single VLR, and the current location information that correctly keeps the user in HLR.Therefore, can improve the reliability of the call through in the mobile communication system.
The above-mentioned description of a preferred embodiment that provides can make any those of ordinary skill in the art realize or use the present invention.Those skilled in the art can easily carry out various changes to these embodiment, and the rule of definition here needn't just can be applied among other embodiment through creative work.Therefore, the present invention is not limited to the embodiment here, but comprises and the disclosed here consistent maximum magnitude of the principle as new feature.