Primary/Secondary Mode and Load-sharing Mode of the OCS Servers
|
OCS server groups operate in primary/secondary mode and the OCS servers in each OCS server group operate in load-sharing mode. If an OCS server in the primary OCS server group fails, the UGW9811 sends the CCR message to an available OCS server in the standby OCS server group that is selected according to the load-sharing policy. If an OCS server is unavailable because the traffic reaches the upper limit, the UGW9811 takes the same actions as it would if the OCS server fails. The load-sharing policies for the OCS servers in the OCS server group are as follows: · Even load sharing When subscribers are activated, all OCS servers in the same group evenly process online charging messages. · IMSI/MSISDN-segment-group-specific load sharing among OCS servers All OCS servers in the same group are bound to an IMSI/MSISDN segment group. When subscribers are activated, the UGW9811 selects OCS servers based on IMSI/MSISDN segments, implementing load sharing among OCS servers. Assume that OCS servers A, B, and C are available, that OCS servers A and B share the traffic of one IMSI/MSISDN segment group. When the subscribers of this IMSI/MSISDN segments group are activated, the traffic is evenly distributed to OCS servers A and B. When the subscribers of other IMSI/MSISDN segment groups are activated, the traffic is distributed to OCS server C. Each OCS server in the OCS server group can be bound only to one IMSI/MSISDN segment group. One IMSI/MSISDN segment group, however, can be bound to multiple OCS servers in an OCS server group. The priorities of the OCS servers that are bound to the same IMSI/MSISDN segment group may be different. The UGW9811 selects one of the OCS servers according to the load-sharing policy for the subscriber of an IMSI/MSISDN segment group when the OCS servers bound to this IMSI/MSISDN segment group have the same priority. The priorities of the IMSI/MSISDN segment groups for the same OCS server group must be different. · Traffic-percentage-specific load sharing among OCS servers Traffic percentage is based on the number of times an OCS server participates in load-sharing. Assume that OCS servers A:B:C are available and that the traffic percentages of these OCS servers are 30%:30%:40% respectively. When 10 online charging subscribers are activated in turn, the order in which the OCS servers are used is ABC, ABC, ABC, and C. That is, OCS servers A:B:C process traffic of 3:3:4 subscribers respectively. The total traffic percentage of all OCS servers in an OCS server group cannot exceed 100%; otherwise, the traffic percentage cannot be configured. Traffic-percentage-specific load sharing and IMSI/MSISDN-segment-group-specific load sharing cannot be implemented at the same time. · If IMSI/MSISDN-segment-group-specific load sharing is configured, traffic-percentage-specific load sharing is not implemented. · The UGW9811 evenly distributes the traffic to the OCS servers if neither IMSI/MSISDN-segment-group-specific load sharing nor traffic-percentage-specific load sharing is configured for the OCS servers in the OCS server group. · If IMSI/MSISDN-segment-group-specific load sharing is configured for some OCS servers in an OCS server group, the traffic of the subscribers that does not belong to the IMSI/MSISDN segment group is evenly distributed to the OCS servers where IMSI/MSISDN-segment-group-specific load sharing is not configured in this OCS server group. · If traffic-percentage-specific load sharing is configured for some OCS servers in an OCS server group but the combined traffic percentage of all the OCS servers in the group is below 100%, the traffic is first load balanced among the OCS servers based on the configured percentages. Then, the remaining traffic is evenly distributed to the OCS servers where traffic-percentage-specific load sharing is not configured in this OCS server group. |

Favorite (0)