Method and system for realizing service reallocation
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.
1. A method for realizing a service reallocation, wherein a load shunting flag and a shunting proportion corresponding to a core network (CN) node are configured in a radio network controller (RNC), and the method comprises:
acquiring, by the RNC, 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;
selecting the CN node if the CN node has no load shunting flag; and
performing a load shunting according to the configured shunting proportion of the CN if the CN node has the load shunting flag.
2. The method according to claim 1 , wherein when the message of the user received by the RNC is a radio resource control (RRC) connection request message and if a connection establishment reason cell in the RRC connection request message is registration, it is determined that the present service of the user is a registration service.
3. The method according to claim 1 , wherein when the message of the user received by the RNC is an initial direct transfer message of the user and if a non-access stratum (NAS) message in the initial direct transfer message of the user is a location registration request, a routing area update request, or an attachment request, it is determined that the present service of the user is a registration service.
4. The method according to claim 1 , wherein the acquiring the CN node corresponding to the registration service comprises:
acquiring, by the RNC, an intra domain NAS node selector (IDNNS) according to a received circuit domain or packet domain initial direct transfer message of the user; and
selecting a CN node matching with and corresponding to the IDNNS according to the IDNNS.
5. The method according to claim 4 , wherein the acquiring, by the RNC, the IDNNS according to the received circuit domain initial direct transfer message of the user comprises:
deriving the IDNNS of the user from an international mobile subscriber identifier (IMSI) in the circuit domain initial direct transfer message; and
the IDNNS according to the received packet domain initial direct transfer message of the user comprises:
deriving the IDNNS of the user from a temporary mobile subscriber identity (TMSI) or a packet-TMSI (P-TMSI) in the packet domain initial direct transfer message.
6. The method according to claim 4 , further comprising:
selecting the CN node without the load shunting flag if the matching CN node is not acquired according to a value of the resolved IDNNS.
7. The method according to claim 1 , wherein the performing the load shunting according to the configured shunting proportion of the CN specifically comprises:
selecting a CN node without the load shunting flag if the current shunting proportion of the CN node does not reach the configured shunting proportion; and
selecting the CN node if the current shunting proportion of the CN node reaches the configured shunting proportion.
8. The method according to claim 6 , wherein the selecting the CN node without the load shunting flag comprises:
randomly selecting the CN node without the load shunting flag or selecting the CN node without the load shunting flag by a load sharing algorithm.
9. The method according to claim 6 , further comprising:
configuring an operator identifier corresponding to the CN node in the RNC.
10. The method according to claim 9 , wherein the selecting the CN node without the load shunting flag comprises:
randomly selecting or selecting by a load sharing algorithm the CN node without the load shunting flag and having the same operator identifier as the CN node.
11. The method according to claim 1 , further comprising:
configuring a load shunting time period corresponding to the CN node in the RNC, wherein the shunting time period comprises a starting time and an ending time.
12. The method according to claim 11 , wherein each load shunting flag corresponds to one continuous shunting time period or a plurality of discontinuous shunting time periods, and each continuous time period is an integral multiple of a periodical location registration or of a periodical routing area update timer length.
13. The method according to claim 12 , further comprising:
setting the shunting proportion corresponding to each shunting time period.
14. The method according to claim 13 , wherein the performing the load shunting according to the configured shunting proportion of the CN comprises:
performing the load shunting according to the shunting proportion corresponding to the shunting time period in the shunting time period.
15. A system for realizing a service reallocation, comprising a radio network controller (RNC) which communicates with a core network (CN), wherein:
the RNC is configured to configure a load shunting flag and a shunting proportion corresponding to the CN node,
determine whether a service requested by a user is a registration service, and
select the CN according to load relevant information, and perform a load shunting;
wherein when the RNC receives a message of the user and the RNC determines that the service requested by the user is the registration service, the CN node corresponding to the registration service is acquired;
the CN node is selected if the CN node has no load shunting flag; and
the load shunting is performed according to the configured shunting proportion of the CN if the CN node has the load shunting flag.
16. The system according to claim 15 , wherein the RNC determines whether the service requested by the user is the registration service through a condition as follows:
confirming that the present service of the user is the registration service if a connection establishment reason cell in a radio resource control (RRC) connection request message received by the RNC is registration.
17. The system according to claim 15 , wherein the CN node corresponding to the registration service is acquired through the procedures as follows:
the RNC acquiring an intra domain NAS node selector (IDNNS) according to a received circuit domain and/or packet domain initial direct transfer message of the user; and
selecting the CN node matching with and corresponding to the IDNNS according to the IDNNS.
18. The system according to claim 15 , wherein theRNC performs the load shunting according to the configured shunting proportion of the CN,
the RNC selects the CN node without the load shunting flag if the current shunting proportion of the CN node does not reach the configured shunting proportion; and
the RNC selects the CN node if the current shunting proportion of the CN node reaches the configured shunting proportion.
19. The system according to claim 15 , wherein the RNC configures a load shunting time period corresponding to the CN node, each load shunting flag corresponds to one continuous shunting time period or a plurality of discontinuous shunting time periods, and each continuous time period is an integral multiple of a periodical location registration or of a periodical routing area update timer length.