CN100466829C - Method and system for processing call service, MSC server and HLR - Google Patents

Abstract

The embodiment of the present invention provides a method, system, mobile switching center (MSC) server and home location register (HLR) for processing call services. , the recorded number of times of the current call service is increased by 1; each time the call service is released, the recorded value of the number of times of the current call service is reduced by 1. At the same time, an upper limit value of the allowed number of calling services carried out by a contracted user at the same time is preset in advance, and when the signed user generates a calling service, it is judged whether the recorded number of times of the current calling service is less than the preset upper limit value of the allowed number of calling services. If no, the call service is not performed; if yes, the user is allowed to perform the call service. In this way, the user is prevented from establishing a large number of user connections in a short period of time, and the impact on the interests of the operator is reduced.

Description

Method and system for processing call service, MSC server and HLR

technical field

The invention relates to call technology, in particular to a method and system for processing call services, a Mobile Switching Center (MSC) server and a Home Location Register (HLR).

Background technique

With the continuous development of the communication industry and the continuous improvement of user requirements, more and more types of services have emerged, among which call forwarding and call transfer (CT, Call Transfer) are two relatively common new services.

Call forwarding service users need to pre-set relevant forwarding information through registration, and upload the set relevant forwarding information to the network. Wherein, the forwarding information includes: call forwarding conditions and call forwarding numbers. There are two types of call forwarding: early call forwarding and late call forwarding. Among them, early call forwarding generally includes unconditional forwarding and inter-office forwarding on busy; late call forwarding generally includes intra-office forwarding and no answer forwarding. The CT service does not require users to pre-register, and only needs to enable the CT service authority for the user. In this document, pre-registered users in the call forwarding service and users with CT service rights in the CT service are collectively referred to as subscribers.

When user A calls user B, if user B has registered the forwarding service and set the call forwarding to user C after meeting the forwarding conditions, then the call of user A can be forwarded to user C, thus establishing the user Connection between A and user C.

If user A has the CT service authority and the call is transferred to user C, then, after user A calls user B, when user A dials user C again, the established call will be transferred to third party user C. At this time, user User A can hang up and establish a connection between user B and user C.

In the current call service, since there is no limit to the number of call services performed by subscribers at the same time, it will have some impact on the interests of operators, for example:

1) Assuming that user B is a subscriber who has registered for the call forwarding service, user C's number is a public number such as an Internet (Internet) access code, and user B activates unconditional forwarding to user C. At this time, if user A calls user B, they can access the Internet through call forwarding; if users A1, A2, and A3 call user B, users A1, A2, and A3 can also access the Internet through call forwarding. If users A1, A2, and A3 are illegal users, user B also needs to pay Internet fees for users A1, A2, and A3. In this way, a large amount of fees will be generated in a short period of time. If user B does not honor these fees, it will affect operator's interests.

2) Assuming that user B is a subscriber who has registered for the call forwarding service, when user A calls user B, if user B registers and forwards to user C, user A establishes a connection with user C, and the connection between user A and user B , No connection is established between user B and user C. In this way, if user B activates the forwarding service and registers forwarding to multiple users Cn, he can establish multiple pairs of connections from user An to user Cn without restriction, which will generate relatively large call charges in a short period of time. If these call charges Failure to do so will affect the interests of operators.

3) Assuming that user A has the authority of CT service, when user A calls user B, user A transfers the established connection to user C, so that user B can establish a connection with user C, and user A can transfer different The call of user Bn is transferred to different user Cn, thus establishing unlimited connections between multiple pairs of Bn and Cn, which will generate relatively large call charges in a short period of time. If these call charges cannot be cashed, it will affect the interests of operators.

It can be seen from the existing methods for processing call services that if a subscriber has signed a call service, but the number of call services of the subscriber is not limited, then the user can arbitrarily establish a connection between multiple pairs of users, and in a short time A large call fee will be generated within a short period of time. Once the call fee cannot be cashed, it will affect the interests of the operator.

Contents of the invention

In view of this, the main purpose of the embodiments of the present invention is to provide a method for processing call services, which restricts subscribers of the call services from simultaneously establishing a large number of connections in a short period of time.

The second object of the embodiment of the present invention is to provide an MSC server that restricts the subscribers of the call service from establishing a large number of connections simultaneously in a short period of time.

The third object of the embodiments of the present invention is to provide an HLR that restricts subscribers of the call service from establishing a large number of connections simultaneously in a short period of time.

The fourth object of the embodiments of the present invention is to provide a system for processing call services, which restricts subscribers of call services from establishing a large number of connections simultaneously in a short period of time.

In order to achieve the above-mentioned first purpose, the embodiment of the present invention provides a method for processing call services, which is characterized in that the upper limit of the number of allowable call services is preset; the method also includes the following steps:

Receive call service data, and when the recorded number of current call services of the subscriber is less than the upper limit value of the allowed number of call services, perform call connection processing, and increase the record number of current call services of the contracted user;

When the recorded number of times of the current call service of the subscriber is not less than the upper limit value of the allowable number of call service times, the call service processing is refused. .

In order to achieve the second purpose above, the embodiment of the present invention provides an MSC server, including a setting module, a judging module, a counting module and a calling module;

The setting module is used to set the upper limit value of the number of times that the contracted user is allowed to call the business, and send it to the judging module;

The judging module receives the upper limit of the number of allowed call services from the setting module and the recorded number of current call services of the subscriber from the counting module, and compares the two after receiving the trigger notification sent by the calling module to determine the subscriber Whether the recorded number of times of the current call service is less than the upper limit value of the number of allowed call services, if not, send a rejection notification to the calling module, if yes, send a call notification to the calling module;

The counting module, after receiving the record notification sent by the judgment module, adds 1 to the number of records, and sends the number of records to the judgment module;

The call module, after receiving the call request, sends a routing information request message; after receiving the call service data, sends a trigger notification to the judgment module; after receiving the rejection notification sent by the judgment module, removes the current call service, and receives the After the incoming call notification is sent, the current call service is performed according to the received call service data.

In order to achieve the above third object, the embodiment of the present invention also provides an HLR, the HLR includes: a setting module, a judging module, a counting module, and a sending and receiving module;

The setting module is used to set the upper limit value of the number of calls allowed by the contracted user, and send it to the judgment module;

The judging module receives the upper limit value of the number of allowed call services from the setting module and the recorded number of times of the current call service from the counting module, and compares the two after receiving the trigger notification from the sending and receiving module to determine the current calling number of the subscriber. Whether the recorded number of times of the business is less than the upper limit of the number of calling business times, if not, send a negative notification to the sending and receiving module; if yes, send a confirmation notification to the sending and receiving module, and send a record notification to the counting module;

The counting module, after receiving the record notification sent by the judgment module, adds 1 to the number of records; and sends the number of records to the judgment module;

The sending and receiving module, after receiving the routing request information, sends a trigger notification to the judging module; after receiving the negative notification sent by the judging module, sends a negative reason value; after receiving the confirmation notification sent by the judging module, sends call service data.

In order to achieve the above fourth purpose, the embodiment of the present invention provides a system for processing call services, the system includes: MSC server, and HLR;

The MSC server sets the upper limit of the number of call services, and after receiving the call request, sends a routing information request to the HLR; after receiving the forwarding data sent by the HLR, judges whether the recorded number of times the subscriber’s current call service is less than the allowable number of call services Limit value, if no, remove the current call service; if yes, perform the current call service according to the forwarding data, and add 1 to the number of records; when the call service ends, decrement the number of records by 1;

After receiving the routing information request sent by the MSC server, the HLR sends forwarding data to the MSC server.

In order to achieve the above fourth objective, the embodiment of the present invention also provides a system for processing call services, the system includes: an MSC server, and an HLR;

After receiving the call request, the MSC server sends a routing information request to the HLR; after receiving the forwarding data sent by the HLR, the current call service is performed according to the forwarding data; when receiving the negative cause value sent by the HLR, the current call is removed;

HLR, set the upper limit value of the number of call services; after receiving the routing information request sent by the MSC server, judge whether the record number of current call services of the subscriber is less than the upper limit value of the allowable call service times, if not, send a negative reason value to the MSC server ; If yes, send forwarding data to the MSC server, and add 1 to the number of records.

It can be seen from the above technical solutions that the embodiment of the present invention prevents users from simultaneously establishing a large number of multiple pairs of user connections in a short period of time by limiting the number of ongoing call services initiated by the same subscriber, thereby reducing the impact on the operation influence on business interests.

Description of drawings

Figure 1.a is a schematic structural diagram of the MSC server provided by the embodiment of the present invention;

Figure 1.b is a schematic diagram of the HLR structure provided by the embodiment of the present invention;

FIG. 2 is a flowchart of a method for processing call services provided by an embodiment of the present invention;

FIG. 3 is a flowchart of a method for limiting the number of call services in an early call forwarding service provided by an embodiment of the present invention;

FIG. 4 is a flow chart of a method for limiting the number of call services in the late call forwarding service provided by an embodiment of the present invention;

FIG. 5 is a flowchart of a method for limiting the number of call services in CT services provided by an embodiment of the present invention;

6 is a flowchart of a method for limiting the number of call services in the call forwarding service on the HLR provided by an embodiment of the present invention;

Figure 7.a is a system structure diagram for processing call services provided by an embodiment of the present invention;

Fig. 7.b is another system structure diagram for processing call services provided by the embodiment of the present invention.

Detailed ways

The main idea of the embodiment of the present invention is: preset the upper limit value of the allowed number of call services; receive the call service data, and when the recorded number of current call services of the subscriber is less than the upper limit value of the call service times, perform call processing, and change number of records.

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the present invention will be further described in detail below in conjunction with the accompanying drawings and specific embodiments.

Figure 1.a is a schematic diagram of the MSC server structure for processing call services. As shown in FIG. 1 , the device is mainly composed of a setting module 101 , a judging module 102 , a counting module 103 , and a calling module 104 .

Setting module 101: Set the upper limit value of the number of calls allowed by the subscriber, and send it to the judging module 102.

The upper limit of the number of allowed calls is the number of calls that a subscriber can access simultaneously. The upper limit of the number of calls is generally set by the operator according to actual needs.

Judgment module 102: respectively receive the upper limit value of the number of allowed call services from the setting module 101 and the recorded number of times of the current call service from the counting module 103, after receiving the trigger notification sent by the call module 104, compare the two, and judge Whether the subscriber's current number of calls is less than the upper limit of the number of calls, if not, send a rejection notification to the calling module 104;

Counting module 103: After receiving the recording notification sent by the judging module 102, add 1 to the number of recording times; and send the number of recording times to the judging module 102.

Call module 104: After receiving the call request, send a routing information request message; after receiving the call service data, send a trigger notification to the judgment module 102; after receiving the rejection notification sent by the judgment module 102, remove the current call service; After the call notification sent by the judging module 102, the current call service is performed according to the received call service data.

The call request is generally sent by the base station controller (BSC) to the MSC server when the user is called.

The received call service data refers to: if the call forwarding service is performed, then the call module 104 may receive data such as the forwarding number and location information sent by the HLR; if the CT service is performed, then the call module 104 Received may be the subscriber number to which the transfer is to be made.

Furthermore, when releasing a call service, the call module 104 sends a release notification to the judging module 102;

The judging module 102 sends a decrement notification to the counting module 103 after receiving the release notification sent by the calling module 104;

After the counting module 103 receives the decrement notification from the judging module, it decrements the recording times by 1.

The HLR provided by the embodiment of the present invention is described in detail below. As shown in FIG.

The setting module 101 sets the upper limit of the number of calls allowed by the subscriber, and sends it to the judging module 102 .

The judging module 102 receives respectively the upper limit value of the number of allowed call services from the setting module 101 and the recorded number of times of the current call service from the counting module 103, and compares the two after receiving the trigger notification from the sending and receiving module 105, and judges The recorded times of the current calling service of the subscriber, and compare the two to determine whether the current calling service number of the contracting user is less than the upper limit value of the calling service number of times, if not, send a negative notification to the sending and receiving module 105; if yes, send a confirmation notification to the sending and receiving module 105, and send the record notification to the counting module 103.

The counting module 103 , after receiving the record notification sent by the judging module 102 , adds 1 to the recording times; and sends the recording times to the judging module 102 .

The sending and receiving module 105, after receiving the routing request information, sends a trigger notification to the judging module 102; after receiving the negative notification sent by the judging module 102, sends a negative reason value; after receiving the confirmation notification sent by the judging module 102, sends the call service data.

The negative reason value may be sent to the MSC server, and the MSC server disconnects the call after receiving the negative reason value.

The call service data can be sent to the MSC server, and the MSC server uses the forwarding data to perform the call service after receiving the forwarding data. The call service data is call forwarding service data.

The negative reason value and call service data can be sent out through a routing information confirmation message.

The timing module 106 is used to set a timing time limit, which can be realized by setting a timer. When the timing time limit arrives, send a clearing notice to the counting module 103;

After receiving the reset notification, the counting module 103 clears the recording times.

The timer setting module 106 is used to solve the problem that when the user forwards the call and releases it, there is no process to notify the HLR, and the recorded times of call forwarding are subtracted by 1.

Fig. 2 is a flowchart of a method for processing call services. As shown in Figure 2, the method of the embodiment of the present invention includes the following steps:

Step 201: Preset the upper limit of the number of allowed call services.

The upper limit of the allowed number of call services is the number of call services that a subscriber can access at the same time. The upper limit of the number of call services is generally set by the operator according to actual needs.

Step 202: Receive relevant call service data, and judge whether the recorded number of current call services of the subscriber is less than the upper limit of call service times, if not, perform step 203; if yes, perform step 204.

Receiving relevant call service data means that if the call forwarding service is performed, the MSC server receives data such as the forwarding number and location information sent from the HLR; if the call forwarding service is performed, the MSC server receives the data to be transferred to User number.

Step 203: Reject the call of the call service.

In this step, the method for refusing the call of the call service is: after the MSC server sends a call service times exceeding notification to the base station controller, the MSC server cancels the call.

Step 204: Perform call processing of the call service, and change the number of records.

It can be set here that every time a call service is added, the number of records will be increased by 1.

Furthermore, the method further includes: when releasing a call service, decrementing the number of times recorded in the counting module by 1.

The above process can be completed through the MSC server and the HLR respectively. When the MSC server completes the method of the present invention, it can be used to limit the number of call services in the call forwarding or call transfer service; when the HLR completes the method of the present invention, it can be used to limit the number of call services in the call forwarding service.

In order to make the flow of the above method more clear, the flow of the method for different business pairs is illustrated below with examples.

Taking unconditional forwarding in early call forwarding as an example, the specific method of completing this method through the MSC server is described. Assume that user A calls user B, user B is the called subscriber, and user B forwards the call to user C. Fig. 3 is the flowchart of the method for limiting the number of call services in the early call forwarding service. As shown in Fig. 3, MSC server 1 is the MSC server of called subscriber B; MSC server 2 is the forwarding service provided by called subscriber The MSC server of the user C of the number, its concrete realization comprises the following steps:

Step 301: The MSC server 1 presets the upper limit value of the allowed number of call services.

This step is to pre-set in the MSC server of the called user the upper limit value of the allowable number of call services that allows the user to simultaneously perform call forwarding. The upper limit value of the allowable number of call forwarding is generally determined by the operator according to actual needs. of.

This step can be completed by the setting module 101 in the MSC server.

Step 302: The BSC sends a call request to the MSC server 1.

When user A calls user B, the BSC sends a call request to the MSC server of the called user B, and the MSC responds to the BSC at the same time.

Step 303: the MSC server 1 sends a routing information request message to the HLR.

In this step, the MSC server 1 acquires the location information of the called user B from the HLR through the routing information confirmation message.

In step 302 and step 303, receiving the call request and sending the routing information request message can be completed by the calling module 104 in the MSC server.

Step 304: HLR judges whether the called user subscribes and meets the conditions for triggering forwarding. In this embodiment, called user B is a subscriber and meets the conditions for triggering forwarding. Then HLR returns the forwarding data through the routing information confirmation message to MSC server 1.

In this step, the HLR will return the forwarding data only when the called party is a subscriber and meets the conditions for triggering the forwarding.

The trigger forwarding condition is the forwarding condition registered in advance by the called user. For example: if the user pre-registers unconditional forwarding, as long as there is a call to the subscriber, the forwarding condition is triggered and the call is forwarded directly; if the user pre-registers If a busy call is registered, when the subscriber receives a call and cannot be connected when the call is busy, the forwarding condition is triggered and the call is forwarded.

Receiving the forwarded data in this step can be completed by the calling module 104 in the MSC server.

Step 305: The MSC server 1 judges whether the number of current call service records forwarded by the called user is less than the preset upper limit of the number of allowable call services; if not, execute step 306; if yes, execute step 308.

This step can be completed by the judging module 102 in the MSC server.

Step 306: The MSC server 1 sends a forwarding count exceeding notification to the BSC.

Generally, in this step, the MSC server 1 sends the forwarding times exceeding notification to the calling user by sending a forwarding times exceeding notification tone.

Step 307: The MSC server 1 disconnects the call from the BSC, and ends the procedure.

Step 306 and step 307 can be completed by the calling module 104 in the MSC server.

Step 308: MSC server 1 performs call forwarding, and sends the call to MSC server 2; and MSC server 1 adds 1 to the number of forwarding records of the called user.

Furthermore, after releasing an ongoing forwarding call, the MSC server 1 subtracts 1 from the number of forwarding records of the called user.

In this step, the call forwarding can be completed by the calling module 104 in the MSC server; adding or subtracting 1 to the recorded times can be completed by the counting module 103 in the MSC server.

The following takes late call forwarding as an example to illustrate the specific process of completing the method through the MSC server. Assume that user A calls user B, and user B is the called subscriber, and user B forwards the call to user C. Fig. 4 is the flow chart of the method for limiting the number of call services in the late call forwarding service. As shown in Fig. 4, the MSC server 1 is the MSC server of the called subscriber B; the MSC server 2 is the forwarding number provided by the called subscriber MSC server of user C. Its specific implementation includes the following steps:

Step 401: The MSC server 1 presets the upper limit value of the allowed number of call services.

In this step, the MSC server of the called user pre-sets the upper limit of the number of call forwardings allowed by the user at the same time. The upper limit of the number of allowed call services is generally determined by the operator according to actual needs.

Step 402: The BSC sends a call request to the MSC server 1.

Step 403: the MSC server 1 sends a routing information request message to the HLR.

In this step, the MSC server 1 goes to the HLR to obtain the location information of the called user B through the routing information request message.

Step 404: The HLR returns the routing information of the called user's location through the routing information confirmation message.

In this step, the returned routing information acknowledgment message only includes the routing information of the called user's location, but does not include forwarding data.

Step 405: MSC server 1 performs call connection. If the called user cannot be connected, step 406 is performed; if the called user is connected, the call is directly established between user A and called user B, and the process ends.

Step 406: The MSC server 1 judges whether the user has subscribed for forwarding information. If yes, go to step 407; if not, go to step 411.

Wherein, the judging whether the user has subscribed to the forwarding information is judging whether the called user has pre-registered the call forwarding service and forwarding data. The forwarding data may be a forwarding number.

Step 407: The MSC server 1 sends a forwarding information request message to the HLR, and acquires the forwarding data of the called user from the HLR.

Step 408: The HLR returns the forwarding data of the called subscriber to the MSC server 1 through the forwarding information confirmation message.

Step 409: The MSC server judges whether the recorded times of the current call service forwarded by the called user is less than the preset upper limit value of the allowed number of call services. If no, go to step 410; if yes, go to step 412.

Step 410: the MSC server sends a forwarding count exceeding notification to the BSC.

Generally, in this step, the MSC server 1 sends the forwarding times exceeding notification to the calling user by sending a forwarding times exceeding notification tone.

Step 411: The MSC server 1 disconnects the call from the BSC, and ends the procedure.

The MSC server 1 releases the call from the BSC by sending a call release message.

Step 412: MSC server 1 performs call forwarding, and sends the call to MSC server 2; and MSC server 1 adds 1 to the number of forwarding records of the called user.

Furthermore, after releasing a forwarded call, the MSC service 1 subtracts 1 from the number of forwarded records of the called user.

Through the above two embodiments of early call forwarding and late call forwarding, the method flow of the method for limiting the number of call services in the call forwarding service through the MSC server in the embodiment of the present invention has been described in detail. The method for limiting the number of calls in the CT service through the MSC server is described in detail. User A establishes a call with user B. User A has the CT authority. During the conversation between user A and user B, user A calls user C and transfers the call to user C, so that user B and user C establish a connection. Fig. 5 is a flowchart of a method for limiting the number of call services in CT services. As shown in FIG. 5 , MSC server 1 is the MSC server of subscriber A, and MSC server 2 is the server of user C. Its process includes the following steps:

Step 501: The MSC server 1 presets the upper limit value of the allowed number of call services.

In this step, the MSC server of the user performing call forwarding pre-sets the upper limit value of the number of CTs allowed to be performed by the user at the same time. The upper limit value of the allowed number of call services is generally determined by the operator according to actual needs.

Step 502: BSC sends to MSC server 1 the user number to be transferred to.

When user A is talking with user B and user A dials user C's number, user A's MSC server receives user C's user number from the BSC.

Step 503: MSC server 1 judges whether the user has CT authority, and judges whether the current number of call service records transferred by the subscribed user is less than the preset upper limit value of call service times. If both are yes, then perform step 506; if the user does not have CT authority, then proceed to step 505; if the recorded times of the current call service transferred by the subscriber is not less than the preset allowable call service number upper limit value, then Execute step 504 .

Step 504: The MSC server 1 sends a forwarding count exceeding notification to the BSC.

Step 505: The MSC disconnects the call and ends the process.

The MSC server 1 disconnects the call from the BSC by sending a DISCONNECT message.

Step 506: MSC server 1 performs CT and sends the call to MSC server 2; and MSC server 1 adds 1 to the number of CT records of the called user.

Furthermore, after releasing the call of a CT, the MSC server 1 subtracts 1 from the number of forwarding records of the subscriber.

In addition, the method for limiting the number of call services during the call forwarding process can be implemented on the HLR, and the upper limit of the number of call forwarding times allowed at the same time is set on the HLR, which is counted and controlled by the HLR. However, the HLR can only increase the call forwarding times of the subscribers at present, and cannot decrease the recorded times of call forwarding when the user forwards the calls and releases them. Therefore, a timer is set on the HLR, and the times of forwarding are cleared after a certain time. In this way, if the call forwarding function is implemented on the HLR, the user's call forwarding times can only be limited within a certain period of time.

Taking the unconditional forwarding in early call forwarding as an example, the flow of the method for limiting the number of calls of the call forwarding service on the HLR is described. This flow is within the time limit of the timer. Fig. 6 is a flowchart of a method for limiting the number of call services in the call forwarding service on the HLR. As shown in Figure 6, its specific implementation includes the following steps:

Step 601: Preset the upper limit of the number of allowed call services in the HLR.

This step can be completed by the setting module 101 in the HLR,

Step 602: The BSC sends a call request to the MSC server 1.

When user A calls user B, the BSC sends a call request to the MSC server of the called user B, and the MSC responds to the BSC at the same time.

Step 603: the MSC server 1 sends a routing information request message to the HLR.

In this step, the MSC server 1 obtains the location information of the called user B from the HLR through the routing information request message.

In this step, the receiving of the routing information request message by the HLR can be completed by the sending and receiving module 105 in the HLR.

Step 604: HLR judges whether the called user subscribes and meets the conditions for triggering forwarding. In this embodiment, called user B is a subscriber and meets the conditions for triggering forwarding; HLR determines whether the current call forwarded by the called user Whether the record times of the service is less than the preset upper limit value of the allowed call service times, if yes, go to step 608; if not, go to step 605.

This step can be completed by the judging module 102 in the HLR.

Step 605: The HLR returns a negative cause value to the MSC server 1 by sending routing information confirmation.

This step can be completed by the sending and receiving module 105 in the HLR.

Step 606: The MSC server 1 sends a forwarding count exceeding notification to the BSC.

Step 607: The MSC server 1 disconnects the call from the BSC, and ends the procedure.

Step 608: The HLR returns the forwarding data to the MSC server 1 through a routing information confirmation message.

The forwarded data is the user number of user C.

This step can be completed by the sending and receiving module 105 in the HLR.

Step 609: MSC server 1 forwards the call, and sends the call to MSC server 2; and the HLR adds 1 to the number of forwarding records of the called user.

In this step, adding 1 to the number of forwarding records of the called party can be completed by the counting module 103 in the HLR.

Furthermore, a periodic timer is set, and when the timing time limit is reached, the number of times of recording in the HLR is cleared.

The periodic timer can be implemented by the timing module 106 in the HLR; the clearing of the recording times can be completed by the counting module 103 in the HLR after receiving the clearing notification from the timing module 106 .

The system provided by the embodiment of the present invention is described in detail below, the system can have the following two modes: one, as shown in Figure 7.a, the system includes: MSC server 701 and HLR 702;

The MSC server 701 sets the upper limit value of the call service times, and after receiving the call request, sends a routing information request to the HLR 702; after receiving the forwarding data sent by the HLR 702, judges whether the record times of the current call service of the subscriber is less than the allowed call The upper limit of service times, if no, remove the current call service; if yes, perform the current call service according to the forwarding data, and add 1 to the recorded number of times;

HLR 702, after receiving the routing information request sent by MSC server 701, sends forwarding data to MSC server 701.

After the call service ends, the MSC server 701 is also used to decrease the recording times by 1.

In this case, the implementation manner of the MSC server may be completed by an MSC server provided in an embodiment of the present invention.

Second, as shown in Figure 7.b, the system includes: MSC server 701, and HLR 702;

After receiving the call request, the MSC server 701 sends a routing information request to the HLR 702; after receiving the forwarding data sent by the HLR 702, it performs the current call service according to the forwarding data; when receiving the negative cause value sent by the HLR 702, it removes the current call.

HLR 702 sets the upper limit value of the number of times of call service; after receiving the routing information request sent by the MSC server 701, judges whether the record number of times of the current call service of the subscriber is less than the upper limit value of the number of call service times allowed, if not, sends to the MSC server 701 Negate the reason value; if yes, send the forwarding data to the MSC server 701, and add 1 to the record times.

The negative reason value and call service data may be sent to the MSC server through a routing information request confirmation message.

Furthermore, the system also includes: a timer 703, which sets a regular time limit; when the regular time limit expires, it sends an arrival notification to the HLR 702;

HLR 702, after receiving the time notification, clears the number of records.

Timer 703 is set because there is no process to notify HLR 702 when the call service ends, and HLR 702 cannot subtract 1 from the recording times, so setting timer 703 periodically clears the recording times of HLR 702.

The timer 703 can be set as an independent device, or can be set in the HLR 702. When it is set in the HLR 702, the implementation of the HLR 702 can be completed by an HLR provided in the embodiment of the present invention.

The first case above can be used for both call forwarding service and CT service; when it is a call forwarding service, the call service data is the call forwarding number; when it is a CT service, the call service data The data is the user number to be transferred to.

In the second case above, it is generally only used for the call forwarding service, and the call forwarding data is the call forwarding number.

It can be seen from the above that the embodiments of the present invention limit the number of ongoing call services initiated by the same subscriber, thereby preventing users from simultaneously establishing a large number of user connections in a short period of time, and reducing the impact on the interests of operators.

Claims (14)

1, a kind of method for handling call business, it is characterized in that, presetting allows the upper limit value of number of times of call business; The method also comprises the following steps: Receive call service data, and when the recorded number of current call services of the subscriber is less than the upper limit value of the allowed number of call services, perform call connection processing, and increase the record number of current call services of the contracted user; When the recorded number of times of the current call service of the subscriber is not less than the upper limit value of the allowable number of call service times, the call service processing is refused. 2. The method according to claim 1, wherein the call service is a call forwarding service; the call service data is a call forwarding number; Alternatively, the call service is a call forwarding CT service; the call service data is the number of the user to be transferred. 3. The method according to claim 1, characterized in that, the method further comprises: after the call service ends, reducing the record times of the current call service of the subscriber; or, A timer is set, and when the timer expires, the recorded number of times of the current call service is cleared. 4. The method according to claim 1, characterized in that the operations of receiving call service data, performing call service processing and rejecting call service processing are performed by MSC; Before receiving the call service data, the method further includes: after the MSC receives the call request, sending a routing information request message to the HLR. 5. The method according to claim 4, characterized in that, the upper limit of the allowed number of call services is set in the MSC, and the recorded number of current call services of the subscriber is recorded by the MSC ; After receiving the call service data, the MSC judges whether the recorded number of current call services of the subscriber is less than the upper limit value of the allowable number of call services. 6. The method according to claim 4, characterized in that, the upper limit of the number of allowed call services is set in the HLR, and the recorded number of current call services of the subscriber is recorded by the HLR ; After the HLR receives the routing information request message, it judges whether the recorded number of times of the current call service of the subscriber is less than the upper limit value of the allowed number of call services, and if so, returns the call service data to the MSC; otherwise, sends the call service data to the MSC. The MSC sends a negative reason value to notify the subscriber that the recorded number of current call services is not less than the upper limit value of the allowed number of call services. 7. A mobile switching center MSC server is characterized in that, the MSC server includes a setting module, a judging module, a counting module and a calling module; The setting module is used to set the upper limit value of the number of times that the contracted user is allowed to call the business, and send it to the judging module; The judging module receives the upper limit of the number of allowed call services from the setting module and the recorded number of current call services of the subscriber from the counting module, and compares the two after receiving the trigger notification sent by the calling module to determine the number of subscribers Whether the recorded number of times of the current call service is less than the upper limit value of the allowed number of call services, if not, send a rejection notification to the calling module, if yes, send a call notification to the calling module; The counting module, after receiving the record notification sent by the judgment module, adds 1 to the number of records, and sends the number of records to the judgment module; The call module, after receiving the call request, sends a routing information request message; after receiving the call service data, sends a trigger notification to the judgment module; after receiving the rejection notification sent by the judgment module, removes the current call service, and receives the After the incoming call notification is sent, the current call service is performed according to the received call service data. 8. The server according to claim 7, wherein the calling module is further configured to: send a release notification to the judging module when releasing the calling service; The judging module sends a decrement notification to the counting module after receiving the release notification from the calling module; The counting module, after receiving the decrement notification sent by the judging module, decrements the number of records by 1. 9. A home location register HLR, characterized in that, the HLR includes: a setting module, a judging module, a counting module, and a sending and receiving module; The setting module is used to set the upper limit value of the number of calls allowed by the contracted user, and send it to the judgment module; The judging module receives the upper limit value of the number of allowed call services from the setting module and the recorded number of times of the current call service from the counting module, and compares the two after receiving the trigger notification from the sending and receiving module to determine the current calling number of the subscriber. Whether the recorded number of times of the business is less than the upper limit of the number of calling business times, if not, send a negative notification to the sending and receiving module; if yes, send a confirmation notification to the sending and receiving module, and send a record notification to the counting module; The counting module, after receiving the record notification sent by the judgment module, adds 1 to the number of records; and sends the number of records to the judgment module; The sending and receiving module, after receiving the routing request information, sends a trigger notification to the judging module; after receiving the negative notification sent by the judging module, sends a negative reason value; after receiving the confirmation notification sent by the judging module, sends call service data. 10, the HLR according to claim 9, is characterized in that, described HLR further comprises: timing module, setting timing time limit; When timing time limit arrives, send clearing notice to counting module; The counting module, after receiving the reset notification, clears the number of records. 11. A system for processing call services, characterized in that the system includes: an MSC server and an HLR; The MSC server sets the upper limit of the number of call services, and after receiving the call request, sends a routing information request to the HLR; after receiving the forwarding data sent by the HLR, judges whether the recorded number of times the subscriber’s current call service is less than the allowable number of call services Limit value, if no, remove the current call service; if yes, perform the current call service according to the forwarding data, and add 1 to the number of records; After receiving the routing information request sent by the MSC server, the HLR sends forwarding data to the MSC server. 12. The system according to claim 11, wherein the MSC server reduces the number of records by 1 after the call service ends. 13. A system for processing call services, characterized in that the system includes: an MSC server, and an HLR; After receiving the call request, the MSC server sends a routing information request to the HLR; after receiving the forwarding data sent by the HLR, the current call service is performed according to the forwarding data; when receiving the negative cause value sent by the HLR, the current call is removed; HLR, set the upper limit value of the number of call services; after receiving the routing information request sent by the MSC server, judge whether the record number of current call services of the subscriber is less than the upper limit value of the allowable call service times, if not, send a negative reason value to the MSC server ; If yes, send forwarding data to the MSC server, and add 1 to the number of records. 14. The system according to claim 13, characterized in that, the system further comprises: a timer, which sets a regular time limit; when the regular time limit expires, it sends an arrival notification to the HLR; HLR, after receiving the arrival notification, clears the recorded number of times.

Images