CN106998572B

CN106998572B - Load balancing method after SBC fault recovery, S-CSCF and UE

Info

Publication number: CN106998572B
Application number: CN201610049263.0A
Authority: CN
Inventors: 孟令希; 李继
Original assignee: China Mobile Communications Group Co Ltd
Current assignee: China Mobile Communications Group Co Ltd
Priority date: 2016-01-25
Filing date: 2016-01-25
Publication date: 2020-05-19
Anticipated expiration: 2036-01-25
Also published as: CN106998572A

Abstract

The invention discloses a load balancing method after SBC fault recovery, an S-CSCF and UE, wherein the method comprises the following steps: after a first SBC in a Session Border Controller (SBC) pool fails and recovers, a serving call session control function (S-CSCF) receives SBC priority information sent by a PGW (PDN gateway), wherein the priority of the first SBC in the SBC priority information is higher than that of a second SBC which is other SBC except the first SBC in the SBC pool; the S-CSCF receives a registration request sent by a second SBC, wherein the registration request carries identification information of User Equipment (UE); and the S-CSCF sends a registration prohibition instruction to the UE according to the SBC priority information.

Description

Load balancing method after SBC fault recovery, S-CSCF and UE

Technical Field

The present invention relates to Voice services (VoLTE, Voice over LTE), and in particular, to a method for load balancing after a Session Border Controller (SBC) fails to recover, a Serving Call Session Control Function (S-CSCF), and a User Equipment (UE).

Background

With the popularization of mobile fourth generation (4G) mobile communication technology, there are two main types of schemes for implementing voice services in a 4G network, namely, providing voice services based on a second generation/third generation (2G/3G) circuit domain and providing VoLTE (Long Term Evolution) based on a 4G packet domain. And the latter will gradually replace the former as the final solution for voice service under 4G network.

Under the VoLTE network, the similar network elements all adopt a Pool (Pool) manner to perform networking, such as SBC Pool and the like. The method divides network devices of the same category into N (integer of N > 1) group resource pools, each group resource pool is provided with M (integer of M > 1) such devices, and the devices in each group resource pool can serve home users in the group resource pool with the same priority (such as random allocation), so as to realize load balance in the group resource pool.

In the SBC Pool networking mode, when a certain SBC in one SBC Pool fails and recovers, the mode of the SBC carrying the service is as shown in fig. 1-1. Before a fault occurs, SBC1, SBC2, and SBC3 all belong to the same SBC Pool, and the load of each SBC within the SBC Pool is substantially balanced, for example, SBC1 is responsible for UE1 and UE5, SBC2 is responsible for UE3 and UE4, and SBC3 is responsible for UE2 and UE 6. When SBC1 fails, as shown in a diagram of fig. 1-1, SBC1 needs to migrate uniformly to SBC2 and SBC3, so that the service of SBC1 needs to be allocated to SBC2 and SBC3 in a balanced manner, so that SBC2 is responsible for UE1, UE3 and UE4, and SBC3 is responsible for UE2, UE5 and UE 6. As shown in b of fig. 1-1, after SBC1 is recovered, when a user equipment (abbreviated as a user) is powered on in a coverage area, the UE may probabilistically access SBC1, and implement SBC1 carrying services after failure recovery.

In a VoLTE network, a load balancing mechanism (i.e., a rewind mechanism) after an existing SBC failure is that, in a longer time period, an on-network user in an original SBC Pool restarts a mobile phone once, and a UE uniformly attaches an IP Multimedia Subsystem network (IMS, IP Multimedia Subsystem) according to an SBC List (List) downloaded from a PGW, thereby realizing load balancing in the SBC Pool. The defects of the prior art are as follows: firstly, in the prior art, the load balance is realized by independently restarting the mobile phone by the user, downloading the SBC List from the PGW again and registering the VoLTE network; the mode using the user's spontaneity as a mechanism has a long period, and if the user does not power off in the SBC Pool, the network will not reach load balancing all the time. Second, because the redundancy in the SBC Pool is limited, if after a SBC failure recovers, the load in the Pool is not quickly balanced, one SBC is under light load, and other SBCs are under heavy load, which easily causes unstable operation of the device with high load, and is difficult to be lower than the reoccurring failure, which is not favorable for the overall operation safety of the network.

Disclosure of Invention

In view of this, embodiments of the present invention provide a load balancing method after SBC failure recovery, an S-CSCF, and a UE to solve at least one problem existing in the prior art, so that load balancing can be achieved through active control of a network side, thereby rapidly achieving load balancing of SBC Pool, and further recovering an original risk-resisting capability of a VoLTE network.

The technical scheme of the embodiment of the invention is realized as follows:

in a first aspect, an embodiment of the present invention provides a load balancing method after SBC fault recovery, where the method includes:

after a first SBC in a Session Border Controller (SBC) pool fails and recovers, a serving call session control function (S-CSCF) receives SBC priority information sent by a PGW (PDN gateway), wherein the priority of the first SBC in the SBC priority information is higher than that of a second SBC which is part or all of other SBCs except the first SBC in the SBC pool;

the S-CSCF receives a registration request sent by a second SBC, wherein the registration request carries identification information of User Equipment (UE);

and the S-CSCF sends a registration prohibition instruction to the UE according to the SBC priority information.

In a second aspect, an embodiment of the present invention provides a method for balancing load after SBC failure recovery, where the method includes:

after a first SBC in a Session Border Controller (SBC) pool fails and the first SBC is recovered, User Equipment (UE) sends a registration request to a second SBC, wherein the second SBC is other SBC except the first SBC in the SBC pool;

and the UE receives a registration prohibition indication sent by the S-CSCF.

In a third aspect, an embodiment of the present invention provides an S-CSCF, where the S-CSCF includes a first receiving unit, a second receiving unit, and a first sending unit, where:

the first receiving unit is used for receiving SBC priority information sent by a PDN gateway after a first SBC in a Session Border Controller (SBC) pool fails and recovers, wherein the priority of the first SBC in the SBC priority information is higher than that of a second SBC, and the second SBC is other SBC except the first SBC in the SBC pool;

the second receiving unit is configured to receive a registration request sent by a second SBC, where the registration request carries identification information of the UE;

and the first sending unit is configured to send a registration prohibition instruction to the UE according to the SBC priority information.

In a fourth aspect, an embodiment of the present invention provides a UE, where the UE includes a fourth transmitting unit and a fourth receiving unit, where:

the fourth sending unit is configured to send a registration request to a second SBC after a first SBC in a session border controller SBC pool fails and the first SBC recovers, where the second SBC is part or all of other SBCs in the SBC pool except the first SBC;

and the fourth receiving unit is used for receiving the registration prohibition indication sent by the S-CSCF.

The embodiment of the invention provides a load balancing method after SBC fault recovery, an S-CSCF and UE, wherein after a first SBC in an SBC pool is in fault and the first SBC is recovered, the S-CSCF receives SBC priority information sent by a PGW, the priority of the first SBC in the SBC priority information is higher than that of a second SBC, and the second SBC is other SBCs except the first SBC in the SBC pool; the S-CSCF receives a registration request sent by a second SBC, wherein the registration request carries identification information of User Equipment (UE); the S-CSCF sends a registration prohibition instruction to the UE according to the SBC priority information; therefore, load balancing can be achieved through active control of the network side, so that load balancing of the SBC Pool can be achieved quickly, and the original risk resistance capability of the VoLTE network is recovered.

Drawings

FIG. 1-1 is a schematic diagram of a related art SBC bearer service;

fig. 1-2 are schematic diagrams illustrating an implementation flow of a load balancing method after SBC fault recovery according to an embodiment of the present invention;

fig. 2 is a schematic flow chart of a first implementation process of the load balancing method after the SBC fault is recovered according to the third embodiment of the present invention;

fig. 3 is a schematic flow chart illustrating an implementation process of the load balancing method after the SBC fault is recovered according to the third embodiment of the present invention;

FIG. 4 is a schematic diagram of a structure of a four S-CSCF in accordance with an embodiment of the present invention;

fig. 5 is a schematic structural diagram of a five-UE configuration according to an embodiment of the present invention.

Detailed Description

The technical solution of the present invention is further elaborated below with reference to the drawings and the specific embodiments.

Example one

In order to solve the problems existing in the foregoing background art, an embodiment of the present invention provides a load balancing method after SBC failure recovery, and fig. 1-2 is a schematic flow chart of an implementation of the load balancing method after SBC failure recovery according to an embodiment of the present invention, and as shown in fig. 1-2, the method includes:

step S101, after a first SBC in an SBC pool fails and the first SBC is recovered, a service call session control function (S-CSCF) receives SBC priority information sent by a PGW;

here, the SBC priority information includes that the priority of a first SBC is higher than that of a second SBC, where the second SBC is another SBC in the SBC pool except the first SBC; the first SBC includes at least one failed and recovered SBC.

Step S102, UE sends a registration request to a second SBC, wherein the second SBC is part or all of other SBCs except the first SBC in the SBC pool;

here, the registration request carries identification information of the UE;

step S103, the second SBC sends a registration request to an interrogating call session control function (I-CSCF);

here, the I-CSCF forwards the registration request to the S-CSCF.

Step S104, the S-CSCF receives the registration request transmitted by the second SBC and forwarded by the I-CSCF;

and step S105, the S-CSCF sends a registration prohibition instruction to the UE according to the SBC priority information.

Here, in step S105, the sending, by the S-CSCF, the registration prohibition instruction to the UE according to the SBC priority information includes: the S-CSCF determines whether the UE belongs to a subscriber preset by the SBC (which may pre-store the identification information of the preset subscriber of each SBC) with non-highest priority, for example, in fig. 1-1, the recovered SBC1 has the highest priority, and the priorities of SBC2 and SBC3 are lower than the priority of SBC1, so that the S-CSCF needs to determine whether the UE belongs to SBC2 or SBC3, and when the UE belongs to SBC2 or SBC3, the S-CSCF sends a Forbidden to the UE.

If the UE belongs to the network, the S-CSCF sends a registration prohibition instruction to the UE; if not, the execution is carried out according to the normal flow. In this embodiment, since the first SBC is a process after the failure and recovery, the first SBC has the highest priority, the S-CSCF only needs to determine whether the UE belongs to the preset subscriber of the first SBC, and if the UE belongs to the first SBC, the registration request sent by the second SBC is rejected. Because the first SBC is restored, the SBC list (SBC list) is updated again, the S-CSCF rejects the registration request sent by the second SBC, and sends 403 a prohibition to the UE, and then the UE initiates reestablishment of the IMS PDN connection, so that the UE receives the SBC list sent by the PGW, where the SBC list carries SBC priority information; thus, the UE sends a registration request to the SBC with the highest priority according to the SBC priority information.

Here, the registration prohibition indication may include any information that can indicate that the UE is prohibited from registering, for example, the registration prohibition indication may include 403Forbidden, which is commonly used in the related art.

And step S106, the UE receives the register forbidding indication sent by the S-CSCF.

In the embodiment of the present invention, the method further includes:

step S107, the S-CSCF judges whether the UE belongs to a user preset by a second SBC according to the identification information of the UE;

here, the S-CSCF may pre-store an identification information list of a preset user of each SBC, and when the S-CSCF receives a registration request, query the identification information list of the user of the second SBC, and if the identification information of the UE is in the identification information list of the user of the second SBC, determine that the UE belongs to the user preset by the second SBC; and if the identification information of the UE is not in the identification information list of the user of the second SBC, determining that the UE does not belong to the user preset by the second SBC.

Step S108, if the UE does not belong to the user preset by the second SBC, the S-CSCF processes according to a normal processing flow;

here, for example, assuming that the UE is not a subscriber of the second SBC but a subscriber of the third SBC, in other words, the second SBC is a part of SBCs of other SBCs in the SBC pool except the first SBC, the S-CSCF performs the processing according to the normal re-registration procedure or the initial registration procedure; if the second SBC is all SBCs in the SBC pool except the first SBC, the process proceeds to step S109.

Step S109, if the UE belongs to a user preset by a second SBC, the S-CSCF sends a registration prohibition instruction to the UE according to the SBC priority information.

Here, for example, assume that one SBC pool has 5 SBCs, numbered SBC-1, SBC-2, SBC-3, SBC-4, and SBC-5, respectively, wherein the load of these 5 SBCs is approximately equal before SBC-1 fails; at a certain moment, SBC-1 fails, and because SBC-1 fails, the users of the original SBC-1 are balanced to SBC-2 and SBC-3, so that the current load of SBC-2 and SBC-3 is larger; and because the user of SBC-1 is not balanced to SBC-4 and SBC-5, the load change of SBC-4 and SBC-5 before and after the failure of SBC-1 is not large. After a period of time, SBC-1 begins to recover. Continuing here with the assumption that the first SBC is SBC-1, the second SBC including SBC-2 and SBC-3, and the third SBC including SBC-4 and SBC-5; therefore, the load of the second SBC is heavy, and the load needs to be balanced to the first SBC, and the load of the first SBC is light because the first SBC is just recovered; after the load balancing of the embodiment of the present invention, the loads of the first SBC, the second SBC, and the third SBC will be approximately equal.

Here, as can be seen from the above-mentioned step S107 to step S109, the S-CSCF should be able to identify whether the user requested from the SBC belongs to a preset user of the SBC.

In the embodiment of the present invention, the method further includes:

step S110, the S-CSCF acquires the currently registered subscriber volume of the first SBC;

step S111, the S-CSCF judges whether the amount of the currently registered user is larger than a preset threshold value;

step S112, if the currently registered user amount is greater than the preset threshold, the S-CSCF sends an error response to the subsequent UE registered to the first SBC.

As can be seen from the above steps S110 to S112, the S-CSCF may set a balancing threshold for each SBC while starting the load balancing function, and when the statistics of the S-CSCF reaches the threshold, the S-CSCF does not perform the balancing operation any more.

Example two

Based on the first embodiment, an embodiment of the present invention further provides a load balancing method after SBC fault recovery, where the method includes:

step S201, the S-CSCF sends a service task Request (SAR) Request to a Home Subscriber Server (HSS), wherein the SAR Request carries a P-CSCF recovery indication;

step S202, the S-CSCF receives the sent Service Assignment Answer (SAA), and the SAA carries the diameter success indication.

Step S203, HSS sends IDR message to Mobile Management Entity (MME), the said IDR message carries P-CSCF reconstruction Indication (P-CSCF Restoration Indication);

step S204, MME sends a deactivation Bearer Request (deactivation Bearer Request) to UE, wherein the deactivation Bearer Request carries a reactivation instruction (reactivation Request);

step S205, UE receives a deactivation bearer request sent by a mobile management entity MME;

step S206, the UE sends an IMS PDN reestablishment message to the MME according to the reactivation instruction in the bearer deactivation request;

step S207, after the UE and the MME reestablish IMS PDN connection, the UE receives an SBC list sent by the PGW, wherein the SBC list carries SBC priority information;

here, it should be noted that after some conventional processing procedures are performed between the MME and the PGW, the PGW sends an SBC list to the UE, where the SBC list includes SBC priority information.

And step S208, the UE sends a registration request to the SBC with the highest priority according to the SBC priority information.

In the embodiment of the present invention, the SBC priority information includes that the priority of a first SBC is higher than the priority of a second SBC, and correspondingly, the UE sends a registration request to the SBC with the highest priority according to the SBC priority information, where the registration request includes: and the UE sends a registration request to the first SBC according to the SBC priority information.

EXAMPLE III

In order to solve the defects existing in the background art, the embodiment of the invention provides a corresponding solution, which is summarized as follows: after a certain SBC fault is recovered in the SBC Pool, the VoLTE network provides the capability of actively transferring users, namely, users of the SBC with more users in the SBC Pool are transferred to the SBC which is just recovered, so that the integral load balance of the SBC Pool is ensured. The migration action is controllable, the migration process is not suitable to be too long, and the migration cannot generate a signaling storm to impact the network.

In a VoLTE network, a network element S-CSCF connected to an SBC is added with a load balancing device to implement a load balancing Control Function, where CSCF is a Call Session Control Function (Call Session Control Function), and according to the different functions, CSCF is divided into an interrogating Call Session Control Function (I-CSCF, Inquiry CSCF), a Proxy Call Session Control Function (P-CSCF, Proxy CSCF), and a service Call Session Control Function (S-CSCF), and the load balancing Control Function added in S-CSCF has the following characteristics: first, the load balancing function can be manually turned on or off to ensure that the network recovers the normal processing flow after the load balancing is finished. Second, the S-CSCF should be able to identify whether the subscriber requested from the SBC belongs to a pre-defined subscriber. Thirdly, the S-CSCF can set a threshold for balancing, and when the statistics of the S-CSCF reaches the threshold, the S-CSCF does not perform balancing operation any more. Fourthly, after the load balancing switch is turned on, and after the second point is met and the third point threshold is not reached, when the user initiates a request to the network, the S-CSCF needs to reply an error response to the user. Fifthly, after the fourth point is completed, an indication of the user reattaching the network needs to be sent to the HSS. Sixthly, when the S-CSCF receives a request sent from a second point of a certain user and processes another request of the user, the S-CSCF does not process the request of the user according to the fourth point.

Next, a load balancing process of the embodiment of the present invention is introduced, and fig. 2 is a schematic view of a first implementation process of the load balancing method after the third SBC fault is recovered in the embodiment of the present invention, as shown in fig. 2, the process includes:

step S301, calculating the user quantity of the SBC to be balanced according to the actual situation, and taking the user quantity as a balancing threshold; and setting the SBC to which the user belongs as the basis for the user amount statistics.

Step S302, adjust the priority of SBC List in PGW, and adjust the priority of SBC just recovered to the highest.

Step S303, the load balancing switch on the S-CSCF is turned on.

Step S304, when the user registers or re-registers, the S-CSCF replies an error response to the user according to the threshold and the conditions of the home SBC in step S301.

In step S305, the S-CSCF allows the user to re-attach to the network through the HSS and the MME.

In step S306, the user initiates registration to the SBC with the higher priority by acquiring the SBC List in the PGW.

In step S307, the PGW restores the original SBC List configuration.

And step S308, closing the S-CSCF load balancing switch.

Steps S302, S305, S306, and S307 are disclosed flows, and some disclosed flows are multiplexed in the load balancing flow in the embodiment of the present invention.

For example, it is assumed that three SBCs, namely SBC1, SBC2, and SBC3, are originally present in a certain SBC Pool, and the number of subscribers per SBC is 2 ten thousand each. When the SBC1 recovers after failure, the network is re-accessed to take over the service, and at this time, the number of SBC1 users is 0, and the number of SBC2 users and SBC3 users is 3 ten thousand each. The PGW (PDN GateWay, Public Data Network) adjusts the SBC List to increase the priority of SBC1, and the generated SBC List is { SBC1, SBC2, SBC3} or { SBC1, SBC3, SBC2}, so that the restarted or newly accessed UE can prefer the SBC1 in the List to register and randomly issue.

Fig. 3 is a schematic diagram of a second implementation flow of the load balancing method after the SBC fault is recovered according to the third embodiment of the present invention, as shown in fig. 3, the flow includes:

step S311, the UE sends a registration request to SBC2 or SBC 3;

here, the registration request carries at least identification Information (ID) of the UE;

step S312, SBC2 or SBC3 sends the registration request to the I-CSCF, which then forwards the registration request to the S-CSCF;

here, the I-CSCF performs the UAR and UAA interaction procedure with the HSS. Wherein, UAR (User Authorization request) message, UAA is User Authorization Answer (UAA).

Step S313, the S-CSCF sends 403Forbidden to the UE according to the identification information of the UE;

here, the S-CSCF sends 403Forbidden to the UE according to the identity information of the UE, including: the S-CSCF sends 403Forbidden to the I-CSCF, which then forwards 403Forbidden to SBC1, which then SBC1 sends 403Forbidden to the UE.

Here, the S-CSCF finds that SBC2 or SBC3 has a lower priority than SBC1 according to the SBC priority List (sblist), and thus the S-CSCF sends 403Forbidden according to the UE' S identification information to the UE.

Here, the S-CSCF turns on the rewind switch, sets a periodic re-registration request for 1 ten thousand UEs sent from SBC2 and SBC3, and returns to 403Forbidden (403 disabled). The way that the S-CSCF identifies SBC2 and SBC3 is that the SBC-domain parameter in the P-Access-Network-Info header field requested by registration (Register) contains SBC2.010.china mobile.

Step S314, the S-CSCF sends an SAR request to the HSS, wherein the SAR request carries a P-CSCF restationindication;

here, after the S-CSCF replies 403 with a response to the UE, the S-CSCF transmits a SAR request including information such as a P-CSCF Restoration Indication to a Home Subscriber Server (HSS).

Step S315, the S-CSCF receives an SAA response sent by the HSS, where the SAA response carries a Diameter success (Diameter success).

Step S316, HSS sends IDR message to MME, said IDR message carries P-CSCF reply Indication (P-CSCFReservation Indication);

step S317, after receiving the IDR message sent by the HSS, the MME sends a deactivation Bearer Request (deactivation Bearer Request) message to the UE, where the deactivation Bearer Request carries a reactivation (reactivation requested) instruction.

In the above steps S315 to S317, the S-CSCF sets the registration state of the user to unregistered (unregistered) after receiving the SAA. The HSS receives the SAR Request and then sends an IDR (Insert Subscriber Data Request) message to a Mobile Management Entity (MME), wherein the IDR message carries a P-CSCF retrieval Indication. After receiving the IDR message carrying the P-CSCF restoration indication, the MME sends a deactivation Bearer Request (deactivation Bearer Request) message to the UE, where an NAS cause value in the deactivation Bearer Request message indicates "Reactivation (Reactivation)" and the Reactivation is used to instruct the terminal to reestablish the IMS PDN connection.

Step S318, after the UE receives the deactivating Bearer Request message, the UE sends an IMS PDN reestablishment (PDN re-establishment) message to a Mobile Management Entity (MME);

step S319, the UE sends a registration request to SBC 1;

step S320, the UE registers to the standard initial registration procedure on SBC 1.

Here, step S320 is a standard initial registration procedure for registering the UE to SBC1, including:

step S3200, SBC1 forwards the registration request to the I-CSCF;

step S3201, the I-CSCF acquires S-CSCF information from HSS through UAR (User-Authorization-Request) message and forwards the registration Request to S-CSCF according to S-CSCF information;

step S3202, the S-CSCF acquires the authentication information of the user from the HSS through a Multimedia Authentication Request (MAR) message;

step S3203, the S-CSCF requires the UE to authenticate by returning 401 information to the UE;

step S3204, the UE sends the registration request again, carries the authentication information and completes the authentication;

step S3205, the S-CSCF acquires the user subscription data from the HSS through the SAR message;

in step S3206, the S-CSCF returns a 200OK response to the UE, and the registration procedure is ended.

Here, the UE reestablishes the IMS PDN connection. The SBC List is downloaded again, and registration to SBC1 is initiated according to the List { SBC1, SBC2, SBC3} or { SBC1, SBC3, SBC2} above. Therefore, when 1 universal subscriber of SBC2 and SBC3 is re-registered, they are registered to SBC1, so that 2 universal subscribers are respectively loaded on SBCs in the SBC Pool, and load balancing is achieved.

Here, it should be noted that, in general, the S-CSCF receives two types of registration requests, the first type of registration request belongs to an initial registration request, and the second type of registration request belongs to a re-registration. Initial registration refers to the process of authentication and attachment performed when a user first accesses a network; re-registration refers to the process of requiring the user to repeatedly initiate authentication within a specified period after initial registration in order for the network to synchronize with the user.

In the embodiment of the present invention, after receiving a registration request, the S-CSCF determines whether the registration request belongs to a re-registration request, where the manner of determining whether the registration request belongs to the re-registration request is as follows: the user is already registered in the S-CSCF and the registration request is secured, then the registration request is re-registered.

It can be seen from the above embodiments that, in this embodiment, a load balancing device is added in the S-CSCF, so that a load balancing mechanism of the SBC Pool is implemented by controlling through the S-CSCF. The S-CSCF can manually turn on and off the load balancing switch; load balancing conditions may be set; an error response may be sent to the eligible user. Based on the load balancing device, a set of load balancing execution processes is realized: opening an S-CSCF load balancing switch; and returning an error response to the user meeting the condition, and closing the S-CSCF load balancing switch. Compared with the prior art, the embodiment of the invention has the following advantages: in the prior art, a user needs to autonomously restart a mobile phone to realize load balancing in an SBC Pool. In the embodiment, the load balancing switch on the S-CSCF is manually turned on and off, and the network side actively controls the load balancing switch to realize the load balancing. In the prior art, the load balancing period of the SBC Pool is long, which is not favorable for stabilizing the VoLTE network. In the embodiment of the invention, the load balance of the SBC Pool can be quickly realized within a re-registration period (generally about 1 hour), and the original risk resistance capability of the VoLTE network is recovered.

Example four

Based on the foregoing embodiments, embodiments of the present invention provide a serving call session control function (S-CSCF), where each unit included in the S-CSCF and each module included in each unit may be implemented by a processor in the S-CSCF, and may also be implemented by a specific logic circuit; in the course of a particular embodiment, the processor may be a Central Processing Unit (CPU), a Microprocessor (MPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), or the like.

Fig. 4 is a schematic diagram of a structure of a four S-CSCF according to an embodiment of the present invention, and as shown in fig. 4, the S-CSCF400 includes a first receiving unit 401, a second receiving unit 402, and a first sending unit 403, where:

the first receiving unit 401 is configured to receive SBC priority information sent by a PGW (PDN gateway) after a first SBC in an SBC pool fails and recovers the first SBC, where a priority of the first SBC in the SBC priority information is higher than a priority of a second SBC, where the second SBC is another SBC in the SBC pool except the first SBC;

the second receiving unit 402 is configured to receive a registration request sent by a second SBC, where the registration request carries identification information of a user equipment UE;

the first sending unit 403 is configured to send a registration prohibition instruction to the UE according to the SBC priority information.

In this embodiment of the present invention, the S-CSCF further includes a second sending unit and a third receiving unit, where:

the second sending unit is used for sending an SAR request to a home subscriber server HSS, wherein the SAR request carries a P-CSCF recovery indication;

the third receiving unit is configured to receive a sent SAA response, where the SAA response carries a diameter success indication.

In this embodiment of the present invention, the S-CSCF further includes a first determining unit and a returning unit, where:

the first judging unit is configured to judge whether the UE belongs to a user preset by a second SBC according to the identification information of the UE; and if the UE belongs to a user preset by a second SBC, triggering the first sending unit.

In this embodiment of the present invention, the S-CSCF further includes an obtaining unit, a second determining unit, and a third sending unit, where:

the acquiring unit is configured to acquire a currently registered subscriber volume of the first SBC;

the second judging unit is configured to judge whether the currently registered user amount is greater than a preset threshold;

and the third sending unit is configured to send an error response to subsequent UE registered to the first SBC if the current registered user amount is greater than a preset threshold.

Here, it should be noted that: the above description of the S-CSCF embodiment is similar to the above description of the method embodiment, and has similar beneficial effects to the method embodiment, and therefore, the description thereof is omitted. For technical details that are not disclosed in the embodiment of the S-CSCF of the present invention, please refer to the description of the embodiment of the method of the present invention for understanding, and therefore, for brevity, will not be described again.

EXAMPLE five

Based on the foregoing embodiments, the embodiments of the present invention provide a UE, where each unit included in the UE and each module included in each unit may be implemented by a processor in the UE, and may also be implemented by a specific logic circuit; in the course of a particular embodiment, the processor may be a Central Processing Unit (CPU), a Microprocessor (MPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), or the like.

Fig. 5 is a schematic structural diagram of a fifth UE according to an embodiment of the present invention, and as shown in fig. 5, the UE 500 includes a fourth sending unit 501 and a fourth receiving unit 502, where:

the fourth sending unit 501 is configured to send a registration request to a second SBC after a first SBC in a session border controller SBC pool fails and the first SBC recovers, where the second SBC is another SBC in the SBC pool except the first SBC;

the fourth receiving unit 502 is configured to receive a registration barring indication sent by the S-CSCF.

In this embodiment of the present invention, the UE further includes a fifth receiving unit, a fifth transmitting unit, a sixth receiving unit, and a sixth transmitting unit, where:

the fifth receiving unit is configured to receive a bearer deactivation request sent by a mobility management entity MME, where the bearer deactivation request carries a reactivation instruction;

the fifth sending unit is configured to send an IMSPDN reestablishment message to the MME according to the reactivation indication in the bearer deactivation request;

the sixth receiving unit is configured to receive, by the UE, an SBC list sent by the PGW after the IMS PDN connection is reestablished with the MME, where the SBC list carries SBC priority information;

and the sixth sending unit is configured to send a registration request to the SBC with the highest priority according to the SBC priority information.

In the embodiment of the present invention, the SBC priority information includes a priority of the first SBC that is higher than a priority of the second SBC, and correspondingly, the sixth sending unit is configured to send, by the UE, a registration request to the first SBC according to the SBC priority information.

Here, it should be noted that: the above description of the UE embodiment is similar to the above description of the method embodiment, and has similar beneficial effects to the method embodiment, and therefore, the description is omitted here for brevity. For technical details that are not disclosed in the UE embodiment of the present invention, please refer to the description of the method embodiment of the present invention for understanding, and therefore, for brevity, will not be described again.

It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that, in various embodiments of the present invention, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention. The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described device embodiments are merely illustrative, for example, the division of the unit is only a logical functional division, and there may be other division ways in actual implementation, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or units may be electrical, mechanical or other forms.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units; can be located in one place or distributed on a plurality of network units; some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, all the functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be separately regarded as one unit, or two or more units may be integrated into one unit; the integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

Those of ordinary skill in the art will understand that: all or part of the steps for realizing the method embodiments can be completed by hardware related to program instructions, the program can be stored in a computer readable storage medium, and the program executes the steps comprising the method embodiments when executed; and the aforementioned storage medium includes: various media that can store program codes, such as a removable Memory device, a Read Only Memory (ROM), a magnetic disk, or an optical disk.

Alternatively, the integrated unit of the present invention may be stored in a computer-readable storage medium if it is implemented in the form of a software functional module and sold or used as a separate product. Based on such understanding, the technical solutions of the embodiments of the present invention may be essentially implemented or a part contributing to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: a removable storage device, a ROM, a magnetic or optical disk, or other various media that can store program code.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.

Claims

1. A load balancing method after SBC fault recovery is characterized by comprising the following steps:

updating an SBC list after a first SBC in an SBC pool fails and recovers, wherein a service call session control function (S-CSCF) receives SBC priority information sent by a PDN gateway, the SBC priority information is stored in the SBC list, the priority of the first SBC in the SBC priority information is higher than that of a second SBC, and the second SBC is part or all of other SBCs except the first SBC in the SBC pool;

the method comprises the steps that an S-CSCF receives a registration request sent by a second SBC and forwarded by an I-CSCF, wherein the registration request carries identification information of User Equipment (UE);

if the UE belongs to a preset user of the first SBC, the S-CSCF rejects the registration request sent by the second SBC;

and if the UE does not belong to the preset user of the first SBC, the S-CSCF sends a registration prohibition instruction to the UE.

2. The method of claim 1, further comprising:

the method comprises the steps that S-CSCF sends a service task request SAR request to a home subscriber server HSS, wherein the SAR request carries a P-CSCF recovery indication;

and the S-CSCF receives a sent service task response SAA response, and the SAA response carries a diameter success indication.

3. The method according to claim 1 or 2, characterized in that the method further comprises:

the S-CSCF judges whether the UE belongs to a user preset by a second SBC according to the identification information of the UE;

and if the UE belongs to a user preset by a second SBC, the S-CSCF sends a registration prohibition instruction to the UE according to the SBC priority information.

4. The method of claim 3, further comprising:

the S-CSCF acquires the current registered user quantity of the first SBC;

the S-CSCF judges whether the amount of the currently registered user is larger than a preset threshold value;

and if the number of the currently registered users is larger than a preset threshold value, the S-CSCF sends an error response to the subsequent UE registered to the first SBC.

5. A load balancing method after SBC fault recovery is characterized by comprising the following steps:

updating an SBC list after a first SBC in an SBC pool of a session border controller fails and the first SBC is recovered, wherein the SBC list stores SBC priority information, and User Equipment (UE) sends a registration request to a second SBC which is other SBC except the first SBC in the SBC pool;

6. The method of claim 5, further comprising:

the method comprises the steps that UE receives a bearer deactivation request sent by a mobile management entity MME, wherein the bearer deactivation request carries a reactivation instruction;

the UE sends an IMS PDN reestablishment message to a mobile management entity MME according to a reactivation instruction in the bearer deactivation request;

after the UE and the MME reestablish IMS PDN connection, the UE receives a Session Border Controller (SBC) list sent by a PDN gateway, wherein the SBC list carries SBC priority information;

and the UE sends a registration request to the SBC with the highest priority according to the SBC priority information.

7. The method of claim 6, wherein the SBC priority information includes a priority of a first SBC higher than a priority of a second SBC, and correspondingly, the UE sends the registration request to the SBC with the highest priority according to the SBC priority information, including:

and the UE sends a registration request to the first SBC according to the SBC priority information.

8. A serving call session control function, S-CSCF, comprising a first receiving unit, a second receiving unit, and a first sending unit, wherein:

the first receiving unit is used for updating an SBC list and receiving SBC priority information sent by a PDN gateway after a first SBC in an SBC pool fails and recovers, wherein the SBC priority information is stored in the SBC list, the priority of the first SBC in the SBC priority information is higher than that of a second SBC, and the second SBC is part or all of other SBCs except the first SBC in the SBC pool;

the first sending unit is configured to, when the UE belongs to a preset user of the first SBC, reject, by the S-CSCF, the registration request sent by the second SBC; and when the UE does not belong to the preset user of the first SBC, the S-CSCF sends a registration prohibition instruction to the UE.

9. The S-CSCF of claim 8, wherein said S-CSCF further comprises a second sending unit and a third receiving unit, wherein:

the second sending unit is used for sending a service task request SAR request to a home subscriber server HSS, wherein the SAR request carries a P-CSCF recovery indication;

the third receiving unit is configured to receive the sent SAA response, where the service task response SAA response carries a diameter success indication.

10. The S-CSCF of claim 8 or 9, wherein said S-CSCF further comprises a first determining unit and a returning unit, wherein:

11. The S-CSCF of claim 10, wherein the S-CSCF further comprises an obtaining unit, a second determining unit, and a third sending unit, wherein:

12. A User Equipment (UE), comprising a fourth transmitting unit, a fourth receiving unit, a sixth receiving unit and a sixth transmitting unit, wherein:

the fourth sending unit is configured to update the SBC list and send a registration request to a second SBC after a first SBC in the SBC pool fails and the first SBC recovers, where the second SBC is another SBC in the SBC pool except the first SBC;

the fourth receiving unit is configured to receive a registration prohibition indication sent by the S-CSCF;

the sixth receiving unit is configured to, after the connection with the MME reestablishes the IMS PDN, receive, by the UE, a SBC list sent by the PDN gateway, where the SBC list carries SBC priority information and the SBC priority information is stored in the SBC list;

the sixth sending unit is configured to, when the UE belongs to a preset user of the first SBC, reject the registration request sent by the second SBC by the S-CSCF; and when the UE does not belong to the preset user of the first SBC, the S-CSCF sends a registration prohibition instruction to the UE.

13. The UE of claim 12, further comprising a fifth receiving unit and a fifth transmitting unit, wherein:

the fifth sending unit is configured to send an IMSPDN reestablishment message to the MME according to a reactivation indication in the bearer deactivation request.

14. The UE of claim 12, wherein the SBC priority information includes a priority of a first SBC higher than a priority of a second SBC, and wherein the sixth sending unit is configured to send, by the UE, a registration request to the first SBC according to the SBC priority information.