Abstract:
A method and system for realizing service reallocation of core network are provided. The method includes the following steps. A load shunting flag and a shunting proportion corresponding to a core network node are configured in a radio network controller (RNC). When the RNC receives a message of a user and determines that the service requested by the user is a registration service, the core network node corresponding to the registration service is acquired. If the core network node has no load shunting flag, the core network node is selected. If the core network node has the load shunting flag, a load shunting is performed according to the configured shunting proportion of the core network. All the scenes that need the load reallocation can be realized simply and expediently by utilizing the method.

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
       [0001]    This application is a continuation of International Patent Application No. PCT/CN2007/001658, filed May 22, 2007, which claims priority to Chinese Patent Application No. 200610115819.8, filed Aug. 15, 2006, both of which are hereby incorporated by reference in their entirety. 
     
    
     FIELD OF THE INVENTION 
       [0002]    The present invention relates to the field of network communication technique, and more particularly to a method and system for realizing a service reallocation. 
       BACKGROUND 
       [0003]    Recently, in order to solve the problems of network backup and resource sharing, IU FLEX concept is introduced into third generation partnership projects (3GPP) protocol. In other words, a universal terrestrial radio access network (UTRAN) supports an intra domain connection routing function from one radio access network (RAN) node to a plurality of core network (CN) nodes, and allows the RAN node to route the information to different CN nodes in a corresponding circuit switched (CS) domain or a packet switched (PS) domain. 
         [0004]    POOL AREA concept is introduced into the IU FLEX technique, and one pool area is a collection of one or more RAN node service areas. The pool area is composed of a plurality of CN nodes equally, and the CN nodes share the communication amount with one another in the pool area. A mobile switching centre (MSC) collection in the pool area is referred to as an MSC pool. A serving GPRS supporting node (SGSN) collection in the pool area is referred to as an SGSN pool. 
         [0005]    A user equipment (UE) may roam in the pool area without changing the serving CN node. One pool area may serve several parallel CN nodes, and the pool area may separately configure the CS domain and the PS domain. From the perspective of the RAN, the pool area includes all the location areas/routing areas (LA/RA) of the one or more RNCs served by a group of parallel CN nodes, and the group of CN nodes may serve the LA/RA outside the pool area and may also serve other pool areas. The group of CN nodes may be the corresponding MSC pool or SGSN pool. A plurality of CN nodes in one area pool may realize the load balance, and the serving coverage provided by the plurality of CN nodes is much larger than the service area provided by a single CN node, which thus reduces node update, handoff, and relocation among the CNs, thereby reducing the update flow of a home location register (HLR). 
         [0006]    All the CNs in the IU FLEX networking belong to the same operator. In addition, multi-operator CN (MOCN) characteristic is introduced into the 3GPP, the MOCN networking has the CNs of a plurality of operators. The CN of one operator may be the POOL of one CN, CS is the MSC pool, and the PS is the SGSN pool. 
         [0007]    It is known that one RNC is connected to the nodes of a plurality of CNs of the same operator (PLMN) simultaneously in the IU FLEX networking manner, and one RNC is connected to the nodes of a plurality of CNs of different operators (PLMN) simultaneously in the MOCN networking manner, in which each operator may have a plurality of CNs. 
         [0008]      FIG. 1  is a networking diagram of a typical MOCN and IU FLEX. 
         [0009]    Three operators are involved, namely, a CN of operator A, a CN of operator B, and a CN of operator C. The CN refers to the MSC or the SGSN. If the CN of the operator A is the MSC, a collection of MSC-A1, MSC-A2, and MSC-A3 is referred to as the MSC pool. If the CN of the operator A is the SGSN, a collection of SGSN-A1, SGSN-A2, and SGSN-A3 is referred to as the SGSN pool. 
         [0010]    The load of the CN is balanced, the load reallocation after the failure is restored is realized, or the load reallocation after the certain MSC or SGSN exits from or adds to the service is realized through a service load reallocation solution by utilizing the networking structure. The process is realized by cooperating the CN and the RNC. 
         [0011]    The process of the load reallocation of the CS domain is shown in  FIG. 2 . 
         [0012]    It is assumed that the MSC1 is shunted, and O&amp;M respectively set a shunting flag on the RNC and the MSC1. 
         [0013]    1. The UE under the MSC1 initiates an initial direct transfer message, the RNC resolves a network resource identifier (NRI) value in an intra domain non-access stratum (NAS) node selector (IDNNS) after receiving the message, wherein the NAS selects the MSC1 through the IDNNS CN selecting algorithm, and the RNC sends a location registration message in the initial direct transfer message to the MSC1. 
         [0014]    2. The MSC1 receives the location registration message, determines that the UE is the user of this MSC, and performs a subsequent location registration flow. 
         [0015]    3. The CN initiates a flow relating to the security function. 
         [0016]    4. The MSC1 determines that this MSC has a load shunting flag, the location registration message includes a reallocated temporary mobile subscriber identity (TMSI) and unbroadcasted location area information (LAI), and the TMSI includes a null network resource identifier (NULL-NRI). 
         [0017]    5. The UE sends a TMSI reallocation complete message to the MSC1. 
         [0018]    6/7. A flow of releasing the location registration of this time is initiated. 
         [0019]    8. The location registration flow is reinitiated after the UE receives a location registration accept message and finds that the LAI is unbroadcasted. After receiving the initial direct transfer message, the RNC resolves the NRI value (should be NULL-NRI) in the IDNNS, and the RNC selects one MSC without the load shunting flag in the MSC pool by using the NULL-NRI. 
         [0020]    9. The RNC sends the location registration message in the initial direct transfer message to the selected MSC. 
         [0021]    10. The MSC initiates a subsequent normal location registration flow after receiving the location registration flow. 
         [0022]    The process of the load reallocation of the PS domain is shown in  FIG. 3 . 
         [0023]    It is assumed that an SGSN1 is shunted, and O&amp;M respectively set the shunting flag on the RNC and the SGSN1. 
         [0024]    1. A UE under the SGSN1 initiates an initial direct transfer message, and after receiving the initial direct transfer message, the RNC resolves an NRI value in an IDNNS, selects the SGSN1 through the IDNNS CN selecting algorithm, and sends a routing area update (RAU) request message in the initial direct transfer message to the SGSN1. 
         [0025]    2. The SGSN1 receives the RAU Request message, determines that the UE is the user of this MSC, and performs a subsequent RAU flow. 
         [0026]    3. The CN initiates a flow relating to the security function. 
         [0027]    4. The SGSN1 determines that this SGSN has a load shunting flag, and the RAU accept message includes a reallocated packet-TMSI (P-TMSI) and unbroadcasted routing area identity (RAI). A periodic RA update timer is set to a smaller value, and the TMSI includes an NULL-NRI. 
         [0028]    5. The UE sends an RAU complete message to the SGSN1. 
         [0029]    6/7. A flow of releasing the location registration of this time is initiated. 
         [0030]    8. The UE reinitiates the RAU flow after the Periodic RA Update Timer reaches the set time, the RNC resolves the NRI value (should be NULL-NRI) in the IDNNS after receiving the initial direct transfer message, and the RNC selects one SGSN without the load shunting flag in the SGSN pool by using the NULL-NRI. 
         [0031]    9. The RNC sends the RAU request message in the initial direct transfer message to the selected SGSN. 
         [0032]    10. The SGSN continues the subsequent RAU flow after receiving the RAU request message. 
         [0033]    It is known from the above flow that the process of realizing the load reallocation of the CN must be realized through the cooperation of the CN and the RNC in the solution of the prior art, thus having a high complexity. Furthermore, the shunting process is finished by performing the location registration flow twice for the CS domain, and the shunting process is finished by performing the RAU flow twice for the PS domain. Therefore, the performance of the existing network is seriously affected. 
       SUMMARY 
       [0034]    Various embodiments of the present invention provide a method and system for realizing a service reallocation, thereby simply and expediently realizing all the scenes that need the load reallocation under a situation of IU FLEX networking or MOCN networking. 
         [0035]    An embodiment of the present invention provides a method for realizing a service reallocation, wherein a load shunting flag and a shunting proportion corresponding to a CN node are configured in an RNC. The method includes the steps as follows. 
         [0036]    The RNC acquires the CN node corresponding to a registration service when the RNC receives a message of a user and determines that a service requested by the user is the registration service. 
         [0037]    The CN node is selected if the CN node has no the load shunting flag. 
         [0038]    A load shunting is performed according to the configured shunting proportion of the CN if the CN node has the load shunting flag. 
         [0039]    An embodiment of the present invention provides a system for realizing a service reallocation, which includes a configuring unit, a determining unit, and a load processing unit. 
         [0040]    The configuring unit is disposed on an RNC, and is adapted to configure a load shunting flag and a shunting proportion corresponding to a CN node. 
         [0041]    The determining unit is adapted to determine whether a service requested by a user is a registration service. 
         [0042]    The load processing unit is adapted to select the CN according to load relevant information, and perform a load shunting. 
         [0043]    When the RNC receives a message of the user, and the determining unit determines that the service requested by the user is the registration service, the CN node corresponding to the registration service is acquired. 
         [0044]    The CN node is selected if the CN node has no the load shunting flag. 
         [0045]    The load shunting is performed according to the configured shunting proportion of the CN if the CN node has the load shunting flag. 
         [0046]    It may be known from the technical solution of the present invention that for the IU FLEX networking manner, it is only necessary to complementarily introduce the radio access including a Node B in the RNC and configure the load shunting flag and the shunting proportion corresponding to the CN node in the RNC, and thus the RNC is able to independently finish the load reallocation process of the CN. For the MOCN networking manner, it is only necessary to increase a network operator identifier corresponding to each CN node on the basis of the configuration information, and thus the RNC is able to independently finish the load reallocation process of the CN. During the particular implementation, the RNC differentiates the type of the service to be performed by the user according to a radio resource control (RRC) connection request, and separately processes the CS domain CN service and the PS domain CN service, or the RNC resolves an NAS part in an initial direct transfer message, and identifies LU of the CS, ATTACH of the PS, and the initial direct transfer of the RAU message, so as to separately process the CS domain CN service and the PS domain CN service without mutual effects. In the method of independently finishing the reallocation of the CN by the RNC, it is not necessary to modify other network elements, and interface protocols are not affected either. Therefore, the implementation is simple and expedient. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0047]      FIG. 1  is a schematic view of typical MOCN and Iu Flex networking; 
           [0048]      FIG. 2  is a flow chart of a conventional load reallocation of a CS domain; 
           [0049]      FIG. 3  is a flow chart of a conventional load reallocation of a PS domain; 
           [0050]      FIG. 4  is a flow chart of a method according to a first embodiment of the present invention; 
           [0051]      FIG. 5  is a flow chart of a method according to a second embodiment of the present invention; and 
           [0052]      FIG. 6  is a flow chart of a method according to a third embodiment of the present invention. 
       
    
    
     DETAILED DESCRIPTION 
       [0053]    In order to have a better understanding of above solutions of the present invention, a detailed description is given below with embodiments and accompanying drawings. 
         [0054]    Referring to  FIG. 4 , a flow chart of a method according to a first embodiment of the present invention is shown. This embodiment is directed to an IU FLEX networking manner, that is, a RNC is connected to a plurality CNs of the same operator, for a CS domain, the CN is an MSC, and for a PS domain, the CN is an SGSN. 
         [0055]    The flow includes the steps as follows. 
         [0056]    In Step  401 , a load shunting flag and a shunting proportion corresponding to a CN node are configured in the RNC. 
         [0057]    In the embodiment of the present invention, the RNC independently finishes the load reallocation of the CN, and it is necessary to configure the CN node which needs a load shunting and configure the corresponding load shunting flag and shunting proportion thereof in the RNC. The CN nodes of the CS domain and the PS domain are respectively configured by the MSC and the SGSN, and thus the shunting of the MSC and the SGSN is in the RNC. The RNC differentiates the service type to be performed by the user according to an RRC connection request to separately process the CS domain CN service and the PS domain CN service without mutual effects. 
         [0058]    In addition, the RNC resolves an NAS part in the initial direct transfer message, identifies LU of the CS, ATTACH of the PS, and the initial direct transfer of the RAU message to separately process the CS domain CN service and the PS domain CN service without mutual effects. 
         [0059]    In addition, in order to reduce the effect on the existing network service during the process of the service reallocation of the CN and ensure that the process of the service reallocation of the CN is performed in the reasonable time, a load shunting time period corresponding to the CN node is configured in the RNC, and the shunting time period includes a starting time and an ending time. The time period from the starting time to the ending time may be a continuous time period or a plurality of discontinuous time periods. Each continuous time period is an integral multiple of a periodical location registration period or of a periodical routing area update timer length. The periodical LU/RAU (location update/routing area update) time may serve as one unit, and the load shunting proportion may be respectively set in each unit. The load shunting flag, the starting time and the ending time of the load reallocation, and the shunting proportion may be respectively set in each CN node which needs the load shunting. At the same moment, the load shunting flags of all the CNs in the pool area cannot be set at the same time, so as to reduce the impact of the shunting process on the existing network. 
         [0060]    For the newly increased CN or the CN restoring from the failure, it is necessary to reallocate the users in the pool area, and at this time, the total shunting proportion or the user number of a certain CN is evaluated according to the capacity of each CN in the current pool area. The load shunting flag, the starting time and the ending time of the load reallocation, and the shunting proportion of other CNs in the pool area are respectively set according to the above evaluation result. 
         [0061]    If the certain CN starts to exit from the service, the load shunting flag, the starting time and the ending time of the load reallocation, and the shunting proportion corresponding to the CN node are set in the RNC. A smaller shunting proportion may be set in a first periodical RAU time or a periodical LU time during the network exiting, the shunting portion is gradually increased in the subsequent cycles, and the registration initial normal message with the shunting portion being 100% is shunted in the last several cycles. In this manner, the CN may quickly exit from the service with the minimum effect on the existing network. 
         [0062]    In Step  402 , the RNC receives an RRC connection request message of the user. 
         [0063]    In Step  403 , it is determined whether the present service of the user is the registration. If the present service of the user is not the registration, Step  404  is performed; otherwise, Step  405  is performed. 
         [0064]    The RNC may confirm whether the present service of the user is the registration through a connection establishment reason cell in the RRC request message. The connection establishment reason is a mandatory cell in the RRC connection request message. 
         [0065]    In Step  404 , the process is performed according to the protocol related to 3GPP. 
         [0066]    If receiving the initial direct transfer message, the RNC selects one CN node according to the IDNNS, and sends the initial UE message to the CN node. 
         [0067]    In Step  405 , the RNC receives the initial direct transfer message of the user. 
         [0068]    In Step  406 , it is determined whether the CN node corresponding to the registration service exists according to the received initial direct transfer information. If the CN node corresponding to the registration service does not exist, Step  407  is performed; otherwise, Step  408  is performed. 
         [0069]    After receiving the initial direct transfer message of the user, the RNC knows whether the message comes from the CS domain or the PS domain according to domain flag information in the initial direct transfer message. 
         [0070]    If the initial direct transfer message comes from the CS domain, the IDNNS is derived from the IMSI information carried in the message, the configuration information in the RNC is searched according to a value of the derived IDNNS, and the CN node MSC matching with the value of the IDNNS is acquired. 
         [0071]    If the initial direct transfer message comes from the PS domain, the IDNNS is derived from the TMSI or the P-TMSI information carried in the message, the configuration information in the RNC is searched according to a value NRI of the derived IDNNS, and the CN node SGSN matching with the value NRI of the IDNNS is acquired. 
         [0072]    It should be noted that after one RRC connection request, the user may merely initiate the initial direct transfer message of the CS domain, may also merely initiate the initial direct transfer message of the PS domain, and may also initiate the initial direct transfer messages of the CS domain and the PS domain at the same time. If the user initiates the initial direct transfer messages of the CS domain and the PS domain at the same time, the RNC respectively processes the messages of the CS domain and the PS domain, and performs the shunting process separately. 
         [0073]    In Step  407 , the CN node without the load shunting flag is selected if the CN node matching the user IDNNS does not exist. 
         [0074]    In Step  408 , it is further determined whether the acquired matching CN node has the shunting flag. If the acquired matching CN node has no the shunting flag, Step  409  is performed; otherwise, Step  410  is performed. 
         [0075]    In Step  409 , the CN node is selected. 
         [0076]    In Step  410 , the load shunting is performed according to the configured shunting proportion of the CN. 
         [0077]    As above mentioned, when the shunting flag corresponding to the CN node is configured in the RNC, it is necessary to configure the shunting proportion of the CN node with the shunting flag. Further, the corresponding shunting time period may also be configured. Therefore, when the matched CN node acquired according to the value of the IDNNS has the shunting flag, the load shunting is performed according to the configuration information. 
         [0078]    During particular implementation, if the current shunting proportion of the CN node does not reach the configured shunting proportion, the CN node without the load shunting flag is selected, and if the current shunting proportion of the CN node reaches the configured shunting proportion, the CN node is selected. 
         [0079]    For example, in a certain shunting time period, ten registration services match the same CN node with the shunting flag, the shunting proportion corresponding to the CN node is 10:1, and the shunting is performed on one registration service in the time period. That is to say, another CN node without the load shunting flag is selected for the registration service, and the CN node with the shunting flag is selected for the rest nine registration services. 
         [0080]    In Steps  407  and  410 , if it is necessary to select the CN node without the load shunting flag, the CN node without the load shunting flag may be randomly selected or selected by a load sharing algorithm, and the message of the user is sent to the selected CN node. The load sharing algorithm may be the existing load sharing algorithm or any other load sharing algorithms. 
         [0081]    Referring to  FIG. 5 , a flow chart of the method according to a second embodiment of the present invention is shown. 
         [0082]    Similarly, this embodiment is directed to an IU FLEX networking manner, that is, one RNC is connected to a plurality of CNs of the same operator, for a CS domain, the CN is an MSC, and for a PS domain, the CN is an SGSN. 
         [0083]    The flow includes the steps as follows. 
         [0084]    In Step  501 , a load shunting flag and a shunting proportion corresponding to a CN node are configured in the RNC. 
         [0085]    The configuration information in the RNC is the same as that of Step  401  in the embodiment of  FIG. 4 , so it is not repeated here. 
         [0086]    In Step  502 , the RNC receives an initial direct transfer message of the user. 
         [0087]    In Step  503 , it is determined whether the present service of the user is the registration. If the present service of the user is not the registration, Step  504  is performed; otherwise, Step  505  is performed. 
         [0088]    The RNC may confirm whether the present service of the user is the registration by resolving the NAS information in the initial direct transfer message. For the initial direct transfer message of the circuit domain, if the NAS is the location registration request, it represents that the service of this time is the registration service. For the initial direct transfer message of the packet domain, if the NAS is the routing area update request or the attachment request, it represents that the service of this time is the registration service. 
         [0089]    In Step  504 , the process is performed according to the protocol related to 3GPP. 
         [0090]    If receiving the initial direct transfer message, the RNC selects one CN node according to the IDNNS, and sends the initial UE message to the CN node. 
         [0091]    In Step  505 , it is determined whether the CN node corresponding to the registration service exists according to the received initial direct transfer information. If the CN node corresponding to the registration service does not exist, Step  506  is performed; otherwise, Step  507  is performed. 
         [0092]    The RNC knows the message comes from the CS domain or the PS domain according to domain flag information in the initial direct transfer message after receiving the initial direct transfer message of the user. 
         [0093]    If the initial direct transfer message comes from the CS domain, the IDNNS is derived from the IMSI information carried in the message, the configuration information in the RNC is searched according to a value of the derived IDNNS, and the CN node MSC matching with the value of the IDNNS is acquired. 
         [0094]    If the initial direct transfer message comes from the PS domain, the IDNNS is derived from the TMSI or the P-TMSI information carried in the message, the configuration information in the RNC is searched according to a value NRI of the derived IDNNS, and the CN node SGSN matching with the value NRI of the IDNNS is acquired. 
         [0095]    In Step  506 , the CN node without the load shunting flag is selected if the CN node matching with the user IDNNS does not exist. 
         [0096]    In Step  507 , it is further determined whether the acquired matching CN node has the shunting flag. If the acquired matching CN node has no the shunting flag, Step  508  is performed; otherwise, Step  509  is performed. 
         [0097]    In Step  508 , the CN node is selected. 
         [0098]    In Step  509 , the load shunting is performed according to the configured shunting proportion of the CN. 
         [0099]    The solution of the present invention is not only applicable to the load shunting of the CN under the IU FLEX networking manner, but also applicable to the load shunting of the CN under the MOCN networking manner. 
         [0100]    Referring to  FIG. 6 , a flow chart of the method according to a third embodiment of the present invention is shown. 
         [0101]    This embodiment is directed to the MOCN networking manner, that is, one RNC is connected to a plurality of CNs of different operators at the same time, for the CS domain, the CN is an MSC, and for the PS domain, the CN is an SGSN. 
         [0102]    In Step  601 , a load shunting flag, a shunting proportion, and an operator identifier corresponding to a CN node are configured in the RNC. 
         [0103]    As compared with Step  401  in the first embodiment of  FIG. 4 , not only the load shunting flag and the shunting proportion corresponding to the CN node are configured in the RNC, but also the operator identifier corresponding to the CN node is configured. 
         [0104]    For the MOCN networking manner, one RNC is connected to a plurality of CNs of different operators at the same time, and thus when the load reallocation of the CN is performed, and the message of the shunted CN is sent to other CNs, the RNC needs to identify whether the two CNs are of the same operator or of the CN operators having the shared protocol. That is to say, the shunting can only be performed between the CNs of the same operator or the operators having the shared protocol. 
         [0105]    Similarly, the CN nodes of the CS domain and the PS domain are respectively configured by the MSC and the SGSN, and thus the shunting of the MSC and the SGSN is separately processed in the RNC without the mutual effects. 
         [0106]    In addition, in order to reduce the effect on the existing network service for the process of the service reallocation of the CN and ensure that the process of the service reallocation of the CN is performed in the reasonable time, a load shunting time period corresponding to the CN node is configured in the RNC, and the shunting time period includes a starting time and an ending time. The time period from the starting time to the ending time may be a continuous time period or a plurality of discontinuous time periods. The periodical LU/RAU (location update/routing area update) time may serve as one unit, and the load shunting proportion may be respectively set in each unit. The load shunting flag, the starting time and the ending time of the load reallocation, and the shunting proportion may be respectively set in each CN node which needs the load shunting. At the same moment, the load shunting flags of all the CNs in the pool area cannot be set at the same time, so as to reduce the impact of the shunting process on the existing network. 
         [0107]    In Step  602 , the RNC receives an RRC connection request message of the user. 
         [0108]    In Step  603 , it is determined whether the present service of the user is the registration. If the present service of the user is not the registration, Step  604  is performed; otherwise, Step  613  is performed. 
         [0109]    The RNC may confirm whether the present service of the user is the registration through a connection establishment reason cell in the RRC request message. The connection establishment reason is a mandatory cell in the RRC connection request message. 
         [0110]    The RNC may also confirm whether the present service of the user is the registration service through the NAS in the initial direct transfer message of the user. If the NAS is the location registration request for the CS domain, or the routing area update request or the attachment request for the PS domain, it is determined that the present service of the user is the registration service. 
         [0111]    In Step  604 , it is determined whether the load shunting flag is set in the RNC. If the load shunting flag is set in the RNC, Step  605  is performed; otherwise, Step  613  is performed. 
         [0112]    In Step  605 , it is determined whether the load shunting flag respectively exists in the CNs of the CS domain and the PS domain. If the CS domain has the shunting flag, Step  606  is performed, and if the PS domain has the shunting flag, Step  614  is performed. 
         [0113]    In Step  606 , it is determined whether the initial direct transfer message of the CS domain exists. If the initial direct transfer message of the CS domain does not exist, Step  613  is performed; otherwise, Step  607  is performed. 
         [0114]    In Step  607 , the IDNNS is derived from the IMSI. 
         [0115]    In Step  608 , it is determined whether the IDNNS derived from the IMSI matches the CN. If the IDNNS derived from the IMSI does not match the CN, Step  609  is performed; otherwise, Step  610  is performed. 
         [0116]    In Step  609 , the valid CN without the load shunting flag is selected if the value of the IDNNS is invalid or cannot match the CN node. 
         [0117]    In Step  610 , it is further determined whether the acquired matched CN node has the load shunting flag. If the acquired matched CN node has no the load shunting flag, Step  611  is performed; otherwise, Step  612  is performed. 
         [0118]    In Step  611 , the acquired matched CN node without the load shunting flag is selected. 
         [0119]    In Step  612 , the load shunting is performed in the CN pool of the same operator according to the configured shunting proportion of the CN node. 
         [0120]    In Step  613 , the process is performed according to the protocol related to 3GPPl. 
         [0121]    If receiving the initial direct transfer message, the RNC selects one CN node according to the IDNNS, and sends the initial UE message to the CN node. 
         [0122]    In Step  614 , it is determined whether the initial direct transfer message of the PS domain exists. If the initial direct transfer message of the PS domain does not exist, Step  613  is performed; otherwise, Step  615  is performed. 
         [0123]    In Step  615 , the IDNNS is derived from the TMSI or the P-TMSI. 
         [0124]    In Step  616 , it is determined whether the IDNNS derived from the TMSI or the P-TMSI matches the CN. If the IDNNS derived from the TMSI or the P-TMSI does not match the CN, Step  617  is performed; otherwise, Step  618  is performed. 
         [0125]    In Step  617 , if the value of the IDNNS is invalid or cannot match the CN node, the valid CN without the load shunting flag is selected. 
         [0126]    In Step  618 , it is further determined whether the acquired matched CN node has the load shunting flag. If the acquired matched CN node has no the load shunting flag, Step  619  is performed; otherwise, Step  620  is performed. 
         [0127]    In Step  619 , the acquired matched CN node without the load shunting flag is selected. 
         [0128]    In Step  620 , the load shunting is performed in the CN pool of the same operator according to the configured shunting proportion of the CN node. 
         [0129]    In Steps  609  and  617 , if it is necessary to select the CN node without the load shunting flag, the CN node without the load shunting flag may be randomly selected or selected by a load sharing algorithm, and the message of the user is sent to the selected CN node. 
         [0130]    If the user initiates the initial direct transfer messages of the CS domain and the PS domain simultaneously after one RRC connection request, the RNC respectively processes the initial direct transfer messages of the CS domain and the PS domain, and performs the shunting process separately. 
         [0131]    For the LU/RAU/ATTACH during the process that the CN user having been registered in the pool area is shunted to a new CN or the CN restored from the failure, the TMSI/P-TMSI is allocated by the originally registered CN, so the current CN may initiate a de-identification flow, thereby reducing the interaction with the HLR due to a great deal of users changing their CNs. 
         [0132]    It will be apparent to those skilled in the art that various modifications and variations can be made to the structure of the present invention without departing from the scope or spirit of the invention. In view of the foregoing, it is intended that the present invention covers modifications and variations of this invention provided they fall within the scope and sprit of the following claims and their equivalents.