CN100455138C - Method for resharing service after kernal network fault recovery - Google Patents
Method for resharing service after kernal network fault recovery Download PDFInfo
- Publication number
- CN100455138C CN100455138C CNB2006101040891A CN200610104089A CN100455138C CN 100455138 C CN100455138 C CN 100455138C CN B2006101040891 A CNB2006101040891 A CN B2006101040891A CN 200610104089 A CN200610104089 A CN 200610104089A CN 100455138 C CN100455138 C CN 100455138C
- Authority
- CN
- China
- Prior art keywords
- core net
- user
- described user
- nri
- former
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a method for re-sharing the service of a core network after its fault recovery, its core is that: RNC (wireless network controller) obtains NR1 value through calculation according to the initial MPP news, and takes preference to choose the original core network for the described user according to the NRI value; the registering information of the user is sent to the selected core network when it is confirmed to be in a normal state; when the user is registered in the core network, the core network allocates TMSI for the user according the marks of the user, and marks the original core network and the current core network with the contained NRI value. Through this invention, the user can be registered in the original core network after the core network recovers from failure.
Description
Technical field
The present invention relates to the communications field, relate in particular to the professional technology of heavily sharing after the core net fault.
Background technology
The agreement 3GPP TS 23.236 of 3GPP Release5 and 3GPP TS 25.331 have described IU FLEX characteristic.Introduced the notion of pool-area (Chi Qu) in the agreement, a Chi Qu is exactly the set of one or more RNC (RadioNetwork control, radio network controller) service area.Chi Qu is by a plurality of CN (CoreNetwork, core net) node is as MSC (Mobile Switch Center, mobile switching centre) or SGSN (Service GPRS Support Node, Serving GPRS Support Node) form coequally, these CN nodes are shared the traffic in the district of pond; During CN node failure in the Dang Chi district, other CN node can provide service, thereby has increased professional availability.
Fig. 1 has provided a kind of typical IU FLEX networking structure, and this structure comprises MSC-1, MSC-2, MSC-3, HLR (Home Location Register, attaching position register) and RNC.Wherein said MSC-1, MSC-2, MSC-3 belong to same MSC Chi Qu.Following regulation is arranged: all move under the normal situation in system in agreement 3GPP TS 23.236, MSC-1, MSC-2, MSC-3 share the traffic in this pond district jointly, the user who is respectively the location registers success distributes a TMSI (TemporaryMobile Station Identity, temporary mobile subscriber identity), NRI (Network Resource Identifier, the network resource identifier) value that comprises this MSC among the TMSI.Suppose that NRI-1 belongs to MSC-1, NRI-2 belongs to MSC-2, NRI-3 belongs to MSC-3, then at the RNC dypass by the corresponding MSC-1 node of when distribution: NRI-1, the corresponding MSC-2 node of NRI-2, the corresponding MSC-3 node of NRI-3.
When the user A that the location registers success is arranged under the MSC-2 initiates when professional, use TMSI that MSC-2 distributes for this user as user ID, wherein comprise NRI-2 and IDNNS (Non-Access Stratum selection parameter in the territory), described IDNNS derives from TMSI.After RNC received the Initial Direct Transfer (initial direct-sending message) of user A, the value that parses NRI from IDNNS was NRI-2, and the MSC-2 node can reach, and then RNC sends to MSC-2 with described initial direct-sending message.
Suppose that user A is after the success of MSC-2 location registers, MSC-2 breaks down, if initiating location registers, described user A this moment (comprises periodic location update, user's start, perhaps because other reasons causes the Client-initiated location registers), will cause user A to be registered to MSC-1 or MSC-3 gets on.
The prior art one relevant with the present invention provide when user A after MSC-2 location registers success, MSC-2 breaks down, concrete handling process when using TMSI as user's temporary mark when described user A initiates position register request for the first time as shown in Figure 2, comprising:
Step 102, RNC receives the initial direct-sending message that user A sends, wherein NAS (Non-Access Stratum) part is LOCATION UPDATING REQUEST (position updating request) message.The value that parses NRI from TMSI among the IDNNS that RNC derives is NRI-2, so route is pointed to the MSC-2 node, when finding that the MSC-2 node is unreachable, then RNC moves MSC of algorithm selection that normal MSC applied load is shared in the Tong Chi district, here suppose that the MSC that RNC selects is the MSC-3 node, so described message is sent to the MSC-3 node, in described message, uses TMSI to do user ID (distributing to user A's before the MSC-2 fault) equally.
Step 103, MSC-3 finds that the user ID TMSI in the LOCATION UPDATING REQUEST message is not the TMSI that this MSC distributes, then initiate IDENTITY REQUEST (authentication request) message to user A, request IMSI (International Mobile Subscriber Identifier, international mobile subscriber identifier).
User A returns IDENTITY RESPONE after receiving IDENTITY REQUEST message, wherein has the IMSI of user A.
Step 104, after MSC-3 obtains the IMSI of user A, a series of relevant location registers flow processs such as authentication of the UE that is correlated with.
Step 106, obtain the response of VLR as MSC-3 after, send LOCATION UPDATINGACCEPT (position is upgraded and confirmed) and give user A, and in message, carry the TMSI that this VLR distributes for user A, the NRI value that wherein comprises is NRI-3.
User A initiates business in this pond district later on, and using MSC-3 is the TMSI of its distribution, and then RNC carries out Route Selection according to IDNNS, always can choose MSC-3.
Be to select with the algorithm that hypothesis RNC applied load is shared that an available MSC is that MSC-3 is that example describes in the Tong Chi district in the above-mentioned steps 102, an available MSC is MSC-1 in the Tong Chi district if the algorithm that the RNC applied load is shared is selected, after then customer location was registered successfully, MSC-1 can distribute the TMSI of the NRI-1 that comprises this MSC-1 sign for the user.When user A carries out related service later on, preferentially use MSC-1 to derive IDNNS as the TMSI that user A distributes, can choose MSC-1 when RNC carries out the core net Route Selection like this.
The prior art two relevant with the present invention provide when user A after MSC-2 location registers success, MSC-2 breaks down, concrete handling process when using IMSI as user's temporary mark when described user A initiates position register request for the first time comprises the steps:
Step 201, if MSC-2 fault time greater than the one-period location registers time of RNC configuration, then the user A under the Anchor MSC-2 can initiate location registers again.User A initiates position register request for the first time after the MSC-2 fault, use IMSI as user's temporary mark.
Step 202, RNC receives the initial direct-sending message that user A sends, wherein NAS partly is LOCATION UPDATING REQUEST; RNC obtains described user's IMSI from described message, and the V value that calculates according to the IDNNS that derives among the described IMSI of the terminal used of described user; Judging this V value then is to point to the MSC-2 node; When finding that MSC-2 is unreachable, then RNC can select another MSC to initiate the location registers of user A in the Tong Chi district.Here having selected the MSC-3 node with RNC is the explanation that example is carried out follow-up flow process.
Step 203, after MSC-3 receives the LOCATION UPDATING REQ message of user A transmission, the location registers flow process of proceeding to be correlated with.
Step 204, MSC-3 when issuing the LOCATION UPDATING ACCEPT of user A with on distribute for user A new TMSI, wherein include the NRI-3 of MSC-3.
In this pond district, initiate after the user A professional, use MSC-3 be the TMSI of its distribution as user ID, RNC carries out Route Selection according to the IDNNS of the TMSI derivation that described user A uses, and so always can choose MSC-3.
Be to select with the algorithm that hypothesis RNC applied load is shared that an available MSC is that MSC-3 is that example describes in the Tong Chi district in the above-mentioned steps 202, an available MSC is MSC-1 in the Tong Chi district if the algorithm that the RNC applied load is shared is selected, after then customer location is registered successfully, MSC-1 can distribute the TMSI of the NRI-1 that comprises this MSC-1 sign for the user, when user A carries out related service later on, the preferential MSC-1 that uses derives IDNNS as the TMSI that user A distributes, and can choose MSC-1 when RNC carries out the core net Route Selection like this.
By the technical scheme of above-mentioned prior art as can be seen, if certain the CN node failure time in the district of pond is greater than the one-period location registers time of RNC configuration, user under the former fault CN node can initiate location registers again, be distributed to the core net of other the normal operation in this pond district then respectively, if described user is location registers success again in these core net, then these core net distribute a new TMSI can for these users, wherein comprise the NRI that identifies this core net.When later described user carried out related service, IDNNS preferentially derived from newly assigned TMSI, and then RNC can choose the pairing core net of the NRI that comprises among this TMSI by routing function; That is to say that described user's business all is that the MSC by this user registration success bears.After MSC-2 recovered normally, the user in this MSC-2 registration can not come back to Anchor MSC-2 node in the past.Therefore the technological deficiency of prior art existence is after possible causing the MSC-2 that breaks down to recover normal operation, still there is not traffic carrying capacity, that is to say, when the core net that breaks down is recovered normal operation, when the former home subscriber of described fault core net carries out location registers, can not register to described core net.
Summary of the invention
The invention provides a kind of core net node fault and recover the professional method of heavily sharing in back, by the present invention, after the core net node that breaks down recovers normal operation, when the user who belongs to described fault core net carries out location registers, can register to described core net, thereby solved exist in the prior art after the core net node that breaks down recovers normal operation, when the former home subscriber of described fault core net carries out location registers, can not register to the technical problem of described core net.
The present invention is achieved through the following technical solutions:
The invention provides a kind of method of resharing service after kernal network fault recovery, it comprises:
A, radio network controller (RNC) are resolved according to user's initial direct-sending message and are obtained the NRI value, and according to the described original core network of the preferential selection of described NRI value;
B, when confirming selected core net just often, then the registration message with the user sends to selected core net;
C, after described user is registered to described core net, described core net is described user's distribution T MSI according to described user's user ID, and identifies former homing core net of described user and the current core net that service is provided for described user with the NRI value that wherein comprises.
Wherein, before described steps A, comprise:
In RNC, set up the corresponding relation between the core net of the former homing core net place Chi Qu of different NRI values and described user.
Wherein, described steps A specifically comprises:
After A1, RNC receive messages sent by users, and therefrom parse Non-Access Stratum in the territory in and select parameter I DNNS,, then calculate the RNI value of correspondence according to described TMSI when confirming described IDNNS when TMSI derives;
A2, according to the corresponding relation between the core net of different NRI values and the former homing core net place Chi Qu of described user, judge whether described NRI value can match the NRI value of the former homing core net of described user correspondence, if then select the former homing core net of described user; Otherwise, select the principle of corresponding core net to select core net according to the method for load sharing.
Wherein, described steps A also comprises:
When the core net fault of described user's former ownership, then described RNC judges selected former homing core net and currently provides whether the core net of service is same core net for described user, if, then select the principle of corresponding core net to select core net according to the method for load sharing, otherwise, select the core net at the current place of described user.
Wherein, described steps A also comprises:
When the equal fault of core net at described original core network and the current place of described user, then select the principle of corresponding core net to select core net according to the method for load sharing.
Wherein, described method also comprises:
Set up the corresponding relation between different NRI values and the former homing core net of described user in all core net in the district of pond.
Wherein, the user ID of using when described user is registered to described core net is during as TMSI, and described step C specifically comprises:
C1, when the user ID of confirming described user is TMSI, judge then whether described TMSI is that current core net is distributed, if, execution in step C2 then; Otherwise, execution in step C3;
C2, the location registers flow process sign whether needs heavily distribute of storing according to this core net judge whether that needs are that described user redistributes user ID, give described user as if needing, then distribute to comprise the identical TMSI of NRI value that comprises with current TMSI; Otherwise, do not deal with;
C3, derive NRI value, and judge whether described NRI value is the NRI value of described user's former homing core net correspondence, if then be the TMSI that described user's distribution comprises the NRI value of corresponding former homing core net according to described TMSI; If not, then distribute the TMSI of the NRI value that comprises the corresponding current core net that service is provided for described user for described user.
Wherein, described method also comprises:
Set up the corresponding relation of V value and described user's former homing core net in all core net in the district of pond.
Wherein, the user ID of using when described user is registered to described core net is during as IMSI, and described step C specifically comprises:
Derive the V value according to described IMSI, and according to the corresponding relation between V value and described former homing core net, utilize described V value to remove to mate described user's former homing core net,, then distribute the TMSI of the NRI value that comprises corresponding former homing core net for described user if match; Otherwise, distribute the TMSI of the NRI value that comprises the corresponding current core net that service is provided for described user for described user.
Wherein, described core net comprises:
Mobile services switching centre MSC or service universal grouping wireless business supporting node SGSN.
The concrete technical scheme that provides by the invention described above as can be seen, among the present invention, because radio network controller (RNC) calculates NRI value according to user's user ID, and according to the preferential described original core network of selection of described NRI value; And, then register a user to selected core net when confirming selected core net just often; After described user is registered to described core net, described core net is described user's distributing user sign, and the NRI value that will wherein comprise is designated the former ownership NRI of the former homing core net of described user correspondence, therefore by the present invention, after the core net that breaks down in the district of same pond is recovered normal operation, can make the former home subscriber under the described core net be registered to described core net.
Description of drawings
The IU FLEX networking schematic diagram of Fig. 1 for providing in the background technology;
Fig. 2 for the MSC-2 fault that provides in the background technology after, the location registers flow process the when user uses TMSI as user ID;
Fig. 3 is the flow chart of first embodiment provided by the invention.
Embodiment
In the IU FLEX networking, after certain the core net fault recovery in the district of pond, for the former home subscriber that makes this core net location registers again to this core net, the invention provides concrete solution.Before implementing the present invention, need in RNC, set up the corresponding relation between the core net of the former homing core net place Chi Qu of NRI value and described user.Concrete grammar is as follows:
At first according to the regulation in 3GPP TS 23.236 agreements, with the different NRI value of NRI-XY definition, wherein X, Y are respectively positive integers; If n core net arranged in the district of core net pond, as MSC or SGSN, then X ∈ 1,2...n}; Y ∈ 1,2...n}.
The current core net that service is provided for described user of described X indication; Y indicates described original core network.
When X is that { 1, among the 2...n} during fixing value, NRI-XY is corresponding current for described user provides the core net of service, as the NRI value of the SGSN-X node of the MSC-X node of circuit domain or PS (packet domain);
When Y is { 1,2...n} in during fixing value, the MSC-Y that it is circuit domain that NRI-XY corresponds to this user's former homing core net or the SGSN-Y in PS territory, but cause this user at present in current core net success location registers for some reason, and current core net provide service for described user.
When X=Y, NRI-XY promptly is NRI-XX, and it is corresponding current to be exactly described user's former homing core net for described user provides the core net of service.
Then, according to above-mentioned definition, in RNC, set up the corresponding relation between the core net of the former homing core net place Chi Qu of NRI value and described user, for example:
NRI-11 is corresponding current to be MSC-1 for described user provides the core net of service, and described original core network also is MSC-1;
NRI-12 is corresponding current to be MSC-1 for described user provides the core net of service, and described original core network is MSC-2;
NRI-21 is corresponding current to be MSC-2 for described user provides the core net of service, and described original core network is MSC-1;
NRI-22 is corresponding current to be MSC-2 for described user provides the core net of service, and described original core network is MSC-2.
Secondly, also need set up the corresponding relation between different NRI values and the former homing core net of described user in all core net in the district of pond according to the principle of correspondence of above-mentioned NRI value and former homing core net.
For example: dispose at MSC-1: the former homing core net of NRI-11 respective user is MSC-1; The former homing core net of NRI-21 respective user is MSC-1; The former homing core net of NRI-12 respective user is MSC-2; The former homing core net of NRI-22 respective user is MSC-2.
Dispose at MSC-2: the former homing core net of NRI-11 respective user is MSC-1; The former homing core net of NRI-21 respective user is MSC-1; The former homing core net of NRI-12 respective user is MSC-2; The former homing core net of NRI-22 respective user is MSC-2.
In addition, the corresponding relation of configuration V value and described former homing core net in also need all core net in the district of pond.The corresponding relation of V value and former homing core net all core net in the district of pond all are identical.Wherein said V value belongs to the integer in 0 to 999 scope, the former homing core net of the unique corresponding user of one of them V value.
For example, on MSC-1, the former homing core net that V is set is 100 value correspondence is MSC-1.The V value is that the former homing core net of 502 value correspondence is MSC-2; If the V value that this moment, the IMSI by the registered user calculated is 100, then MSC-1 is NRI-11 for the NRI value that the TMSI of this user's distribution should comprise so; If the V value that the IMSI by the registered user calculates is 502, the TMSI that distributes for this user of the MSC-1 NRI value that should comprise is NRI-12 so.
On MSC-2, the former homing core net that V is set is 100 value correspondence is MSC-1.The V value is that the former homing core net of 502 value correspondence is MSC-2; If the V value that this moment, the IMSI by the registered user calculated is 100, then MSC-2 is NRI-21 for the NRI value that the TMSI of this user's distribution should comprise so; If the V value that the IMSI by the registered user calculates is 502, the TMSI that distributes for this user of the MSC-2 NRI value that should comprise is NRI-22 so.
The invention provides first embodiment, the core of this embodiment is: after radio network controller (RNC) receives the IDNNS that carries in the initial direct-sending message of user's transmission, if judge described IDNNS is to derive from TMSI or P-TMSI, then parse the NRI value according to described IDNNS, and according to the described original core network of the preferential selection of described NRI value, next selects the core net of user's current service; And when confirming selected core net just often, then the location update message with the user sends to selected core net; After described core net is received user's location registers message, be described user's distribution T MSI user ID, and identify former homing core net of described user and the current core net that service is provided for described user with the NRI value that wherein comprises.The specific implementation process of described first embodiment comprises as shown in Figure 3:
Step 301, RNC therefrom parses IDNNS after receiving the initial direct-sending message of user's transmission, when confirming described IDNNS from TMSI or P-TMSI derivation, then parses corresponding NRI value according to described IDNNS;
Step 302, according to the corresponding relation between the core net of NRI value and the former homing core net place Chi Qu of described user, judge whether described NRI value can match the NRI value of described user's former homing core net correspondence, if, then execution in step 303, promptly select described user's former homing core net, execution in step 304 then; Otherwise, execution in step 308.
Step 304, judge whether selected core net breaks down, when the core net fault of described user's former ownership, then execution in step 305, be that described RNC judges selected former homing core net and currently provides whether the core net of service is same core net for described user, if then execution in step 308; Otherwise execution in step 306.
Step 306, described RNC selects current for described user provides the core net of service, and execution in step 307 then.
Step 307 is judged whether fault of the described current core net that provides service for described user, and when confirming fault, then execution in step 308; Otherwise, change step 309 over to.
Step 308 selects the principle of corresponding core net to select core net according to the method for load sharing, changes step 309 over to.
Step 309 is registered to selected core net with described user.
Step 310 when described core net receives the message of user when registering, therefrom obtains the employed user ID of user, judges that described user ID is TMSI or IMSI, and when the user ID of confirming described user was TMSI, then execution in step 311; When the user ID of confirming described user was IMSI, then execution in step 312.
Step 311 judges whether described TMSI is that current core net is distributed, if current core net is distributed, then execution in step 313, i.e. the TMSI that distributes described user to use according to the location registers flow process sign whether needs heavily distribute of this core net storage; Otherwise, execution in step 314, promptly derive the NRI value according to described TMSI, and judge whether described NRI value equals the NRI value of described user's former homing core net correspondence, and when confirming to equal, distribute the TMSI of the NRI value (NRI-XY) that comprises corresponding former homing core net simultaneously and the current core net that service is provided for described user for described user; If the two difference, then only distribute the TMSI of the NRI value (NRI-XX) that comprises the corresponding current core net that service is provided for described user for described user.
The specific implementation process of step 313 is as follows:
Judge whether and to give described user for described user redistributes user ID as if needing, then distribute to comprise the identical TMSI of NRI value that comprises with current TMSI; Otherwise, not dealing with, this moment, described user continued to use original TMSI.
Step 312, described core net derives the V value according to described IMSI, and according to the corresponding relation between V value and core net, utilize described V value to remove to mate described user's former homing core net, if match, then distribute the TMSI of the NRI value (NRI-XY) that comprises corresponding former homing core net simultaneously and the current core net that service is provided for described user for described user; Otherwise, be described user's distribution T MSI, and identify former homing core net of described user and the current core net that service is provided for described user with the NRI value that wherein comprises, this moment the former homing core net of described user and current be same core net for described user provides the core net of service, then described NRI value is NRI-XX.
In the step 312, suppose that described core net is MSC-X, after it receives described user's position register request, be IMSI if find the user ID that described user uses, then MSC-X uses algorithm: V=(IMSI div 10) mod 1000, and the result who calculates is the integer that belongs in 0 to 999 scope; Go to mate corresponding core net with described V value then:
If the V value of configuration is the core net that belongs to the current place of described user, as MSC-X or SGSN-X, the MSC-X at the current place of then described user or SGSN-X are that the NRI value that the TMSI of described user's distribution should comprise is NRI-XX;
If the V value of configuration is to belong to described original core network, as MSC-Y or SGSN-Y, the MSC-X at the current place of then described user or SGSN-X are that the NRI value that the TMSI of described user's distribution should comprise is NRI-XY.
If the V value of calculating is not configuration in the core net at the current place of described user, the MSC-X at the current place of then described user or SGSN-X are that the NRI value that the TMSI of described user's distribution should comprise is NRI-XX.
Among above-mentioned first embodiment, also execution in step 305 is not to the process between the step 308, and continue to change over to step 301 this moment after the core net fault of the former ownership of finding described user, after described former homing core network recovery is normal, and execution in step 309.
Among above-mentioned first embodiment, the also process of execution in step 307 and step 308 not, this moment is behind the described user's of discovery former homing core net and the current equal fault of core net that service is provided for described user, change step 301 over to, up to described former homing core net or the current core net that service is provided for described user recover normal after, execution in step 309.
The specific embodiment that provides by the invention described above as can be seen because radio network controller (RNC) calculates NRI value according to user's user ID, and according to the preferential described original core network of selection of described NRI value; And, then the user is re-registered selected core net when confirming selected core net just often; After described user re-registers described core net, described core net is described user's distributing user sign, and the NRI value that will wherein comprise is designated the former ownership NRI of the former homing core net of described user correspondence, therefore by the present invention, after the core net that breaks down in the district of same pond is recovered normal operation, can make the former home subscriber under the described core net re-register described core net.
Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.
Claims (9)
1, a kind of method of resharing service after kernal network fault recovery is characterized in that, comprising:
A, radio network controller (RNC) are resolved according to user's initial direct-sending message and are obtained network resource identifier NRI value, and, preferentially select described original core network according to the corresponding relation between the core net of described NRI value and different NRI value of in RNC, setting up and the former homing core net place Chi Qu of user;
B, when confirming selected core net just often, then the registration message with the user sends to selected core net;
C, after described user is registered to described core net, described core net is that described user distributes temporary mobile subscriber identity TMSI according to described user's user ID, and identifies former homing core net of described user and the current core net that service is provided for described user with the NRI value that wherein comprises.
2, the method for claim 1 is characterized in that, described steps A specifically comprises:
After A1, RNC receive messages sent by users, and therefrom parse Non-Access Stratum in the territory in and select parameter I DNNS,, then calculate the NRI value of correspondence according to described TMSI when confirming described IDNNS when TMSI derives;
A2, according to the corresponding relation between the core net of different NRI values and the former homing core net place Chi Qu of described user, judge whether described NRI value can match the NRI value of the former homing core net of described user correspondence, if then select the former homing core net of described user; Otherwise, select the principle of corresponding core net to select core net according to the method for load sharing.
3, method as claimed in claim 2 is characterized in that, described steps A also comprises:
When the core net fault of described user's former ownership, then described RNC judges selected former homing core net and currently provides whether the core net of service is same core net for described user, if then select the principle of corresponding core net to select core net according to the method for load sharing; Otherwise, select the core net at the current place of described user.
4, method as claimed in claim 3 is characterized in that, described steps A also comprises:
When the equal fault of core net at described original core network and the current place of described user, then select the principle of corresponding core net to select core net according to the method for load sharing.
5, as any described method of claim 1 to 4, it is characterized in that, also comprise:
Set up the corresponding relation between different NRI values and the former homing core net of described user in all core net in the district of pond.
6, method as claimed in claim 5 is characterized in that, the user ID of using when described user is registered to described core net is during as TMSI, and described step C specifically comprises:
C1, when the user ID of confirming described user is TMSI, judge then whether described TMSI is that current core net is distributed, if, execution in step C2 then; Otherwise, execution in step C3;
C2, the location registers flow process sign whether needs heavily distribute of storing according to this core net judge whether that needs are that described user redistributes user ID, give described user as if needing, then distribute to comprise the identical TMSI of NRI value that comprises with current TMSI; Otherwise, do not deal with;
C3, derive the NRI value according to described TMSI, and judge whether described NRI value is the NRI value of described user's former homing core net correspondence, if then distribute the TMSI of the NRI value of the NRI value that comprises corresponding former homing core net and the current core net that service is provided for described user for described user; If not, then only distribute the TMSI of the NRI value that comprises the corresponding current core net that service is provided for described user for described user.
7, as any described method of claim 1 to 4, it is characterized in that, also comprise:
Set up the corresponding relation of V value and described user's former homing core net in all core net in the district of pond.
8, method as claimed in claim 7 is characterized in that, the user ID of using when described user is registered to described core net is during as international mobile subscriber identifier IMSI, and described step C specifically comprises:
C4, derive the V value according to described IMSI, and according to the corresponding relation between V value and described former homing core net, utilize described V value to remove to mate described user's former homing core net, if match, then distribute the TMSI of the NRI value of the NRI value that comprises corresponding former homing core net and the current core net that service is provided for described user for described user; Otherwise, only distribute the TMSI of the NRI value that comprises the corresponding current core net that service is provided for described user for described user.
9, the method for claim 1 is characterized in that, described core net comprises: mobile services switching centre MSC or service universal grouping wireless business supporting node SGSN.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006101040891A CN100455138C (en) | 2006-08-01 | 2006-08-01 | Method for resharing service after kernal network fault recovery |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006101040891A CN100455138C (en) | 2006-08-01 | 2006-08-01 | Method for resharing service after kernal network fault recovery |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1913715A CN1913715A (en) | 2007-02-14 |
| CN100455138C true CN100455138C (en) | 2009-01-21 |
Family
ID=37722444
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2006101040891A Expired - Fee Related CN100455138C (en) | 2006-08-01 | 2006-08-01 | Method for resharing service after kernal network fault recovery |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100455138C (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101448318B (en) * | 2008-12-22 | 2010-08-18 | 华为技术有限公司 | Registration method, boundary proxy device and communication system thereof |
| CN102340793B (en) * | 2010-07-23 | 2015-09-16 | 中兴通讯股份有限公司 | The choosing method of temporary core network, base station and trunked communication system |
| CN102006613B (en) * | 2010-11-19 | 2013-07-03 | 暨南大学 | Dual combined linear discrimination method of mobile core network failure data |
| CN102006614B (en) * | 2010-11-19 | 2013-07-03 | 暨南大学 | Abnormal data linearity judging method of mobile core network |
| JP5223952B2 (en) | 2011-08-12 | 2013-06-26 | 日本電気株式会社 | Mobile communication system, mobile station, switching station, and mobile station location registration method |
| CN102726078B (en) * | 2011-11-09 | 2014-07-09 | 华为技术有限公司 | Method for mobile terminal registration in Pool area and access network entity |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2002082824A2 (en) * | 2001-04-07 | 2002-10-17 | Telefonaktiebolaget Lm Ericsson | Routing a paging response in a mobile radio communications network to a core network node |
| WO2003019958A1 (en) * | 2001-08-24 | 2003-03-06 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and means for redistribution of subscriber information in umts networks where the nodes are arranged in pools |
| WO2003041444A1 (en) * | 2001-11-09 | 2003-05-15 | Simple Products Inc. | System and method for connecting incoming calls to disposable cell phones |
| CN1678123A (en) * | 2004-03-31 | 2005-10-05 | 株式会社Ntt都科摩 | Mobile communication method, mobile station and radio network controller |
| CN1744761A (en) * | 2004-09-04 | 2006-03-08 | 华为技术有限公司 | Method for sharing wireless accessing net by multi operators |
| WO2006071179A1 (en) * | 2004-12-30 | 2006-07-06 | Teliasonera Ab | Method and system for service access control in shared networks |
-
2006
- 2006-08-01 CN CNB2006101040891A patent/CN100455138C/en not_active Expired - Fee Related
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2002082824A2 (en) * | 2001-04-07 | 2002-10-17 | Telefonaktiebolaget Lm Ericsson | Routing a paging response in a mobile radio communications network to a core network node |
| WO2003019958A1 (en) * | 2001-08-24 | 2003-03-06 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and means for redistribution of subscriber information in umts networks where the nodes are arranged in pools |
| WO2003041444A1 (en) * | 2001-11-09 | 2003-05-15 | Simple Products Inc. | System and method for connecting incoming calls to disposable cell phones |
| CN1678123A (en) * | 2004-03-31 | 2005-10-05 | 株式会社Ntt都科摩 | Mobile communication method, mobile station and radio network controller |
| CN1744761A (en) * | 2004-09-04 | 2006-03-08 | 华为技术有限公司 | Method for sharing wireless accessing net by multi operators |
| WO2006071179A1 (en) * | 2004-12-30 | 2006-07-06 | Teliasonera Ab | Method and system for service access control in shared networks |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1913715A (en) | 2007-02-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102355705B (en) | ISR (idle-mode signaling reduction) method and system | |
| KR101073372B1 (en) | Registering a mobile terminal in an area of overlapping cell coverage by first and second networks | |
| US20160007185A1 (en) | Terminal Registration Method, Terminal Discovery Methods, Terminals and Devices | |
| CN101128047B (en) | Method for reallocating core network service | |
| CN103858517A (en) | Communication system, method and apparatus | |
| US20090122743A1 (en) | Method, system and media gateway for realizing mobile switch center pool | |
| CN103179575A (en) | Neighboring device communication method and system, network side device and user equipment | |
| CN100455138C (en) | Method for resharing service after kernal network fault recovery | |
| KR20110137652A (en) | Wireless communication system and method for establishing connection between user equipment and mobility management entity | |
| CN103238345A (en) | Communication method, device and system all based on mobile management entity pool (MME Pool) | |
| CN101483850B (en) | Method and system for network access | |
| CN101330425B (en) | Method for establishing tunnel from SGSN to service gateway | |
| CN100428851C (en) | Method for transferring user inside node pool of core network, and node | |
| CN101018417A (en) | Core network selection method and device in the IMSI paging process | |
| EP1692901B1 (en) | A system, arrangement and a method for handling connection of a mobile station moving in communications systems supporting communication of data | |
| CN101150781B (en) | Called recovery method, device and system for mobile switching center pool | |
| CN100466790C (en) | Method for reducing core network node load | |
| US20190159013A1 (en) | Mobile communication system, mobile station, switching station, and location registration method for mobile station | |
| CN105472530B (en) | Near field communication discovery method, device and system | |
| CN101400038B (en) | Method, apparatus and system for customer service continuity during network fault | |
| CN100576954C (en) | Determine method and device based on the position mobility of idle state customer terminal | |
| CN101267587B (en) | A method, device and system for realizing load reallocation | |
| CN100484060C (en) | Method for selecting terminal kernel network at shared access network | |
| CN100438469C (en) | Method for selecting service core network node | |
| US8983459B2 (en) | Modification of information in a communication network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20090121 Termination date: 20210801 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |