CN1859783A

CN1859783A - Call processing method

Info

Publication number: CN1859783A
Application number: CNA2006100344902A
Authority: CN
Inventors: 刘晓彦; 李世前
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2006-03-15
Filing date: 2006-03-15
Publication date: 2006-11-08
Anticipated expiration: 2026-03-15
Also published as: CN100499865C

Abstract

The present invention provides call processing method. It contains Called side user terminal being first call side user terminal calling accessing process, second call side user terminal requesting same called side user terminal route information, called side MSC judging second call side user terminal and first call side user terminal being same call side user terminal, then called side VLR distributing same information to it, otherwise feeding back called side user terminal busy state information to second call side user terminal. Said method effectively solves double assignment temporary local user number or rejecting same call side terminal calling status.

Description

A kind of call processing method

Technical field

The present invention relates to the communications field, the processing method that particularly a kind of call repeatedly sends routing information.

Background technology

In the cordless communication network, when the interoffice customer call takes place, the mobile switching center MSC/VLR of Originating Office sends route requests to attaching position register HLR, HLR finds the MSC/VLR at called subscriber place according to called party data, obtain Temporary Local Directory Number TLDN, the MSC/VLR of Originating Office is according to TLDN, calls out and the MSC/VLR at called subscriber place connects for this, communicates.Concrete workflow is as shown in Figure 1:

Step 101, the calling subscriber makes a call, MSC1/VLR1 finish and BSC1 between assignation information mutual;

In cdma network, MSC1/VLR1 sends the ASS_REQ assignment request message to caller BSC1, finishes assignment, here repeats no more.

Step 102, the MSC1/VLR1 of Originating Office sends LOCREQ message to HLR according to the called number of calling user dials, request called subscriber's information;

LOCREQ is a location request message, and the calling subscriber has wherein carried called party data information by the positional information of this message to HLR request called subscriber.

Step 103, HLR finds the MSC2/VLR2 at called subscriber place according to called party data information, sends ROUTREQ message to MSC2/VLR2;

HLR requires called MS C2/VLR2 to give calling mobile terminal distribution T LDN by route request information ROUTREQ.

Step 104, MSC2/VLR2 returns the routreq response to HLR, has wherein carried TLDN;

Behind the called MS C2/VLR2 distribution T LDN number, return routreq route requests response message to HLR, comprising called TLDN number.

Step 105, HLR returns the locreq response message to MSC1/VLR1, and the TLDN number is sent to caller MSC1/VLR1;

Step 106, MSC1/VLR1 sends IAM to MSC2/VLR2 by relaying (being example with ISUP) routing striking out here;

MSC1/VLR1 receives after the location information response of HLR that by the IAI/IAM initial address message striking out of ISUP, out called number is called TLDN number.

Step 107 and step 108, MSC2/VLR2 is by issuing page message PagingRequest location called subscriber, and BSC2 returns page-response message PagingResponse.

Step 109 and step 110, MSC2/VLR2 issues assignment request Assignment and distributes A mouth circuit and air interface circuit.

Step 111, MSC2/VLR2 sends Address Complete Message ACM to MSC1/VLR1, and the calling subscriber begins to listen ring-back tone;

Step 112, the called subscriber connects, and BSC2 sends Connect to MSC2/VLR2;

Step 113, MSC2/VLR2 sends response message ANM to MSC1/VLR1, and this moment, the calling and called both sides entered conversation.

Above-mentioned is under the normal condition, the handling process that the interoffice user connects, yet in some particular service flow processs or under the unusual situation of HLR, the situation that may exist call subscriber terminal to send routing information more than twice or twice.In present ANSI-41D agreement, for same called subscriber, two ROUTREQ request messages if arrive simultaneously, when the ROUTREQ request message arrives called MS C2/VLR2 for the first time, TLDN is assigned with, called MS among the VLR2 enters " BUSY " state, wait for incoming call, if receive new ROUTREQ request message during this time, MSC2/VLR2 can be with AccessDeniedReason parameter indication user to be in " BUSY " state in the routreq response, and do not distribute the TLDN number, refuse follow-up call flow.

In this handling process, can't handle repeatedly the situation of request route information, the call flow that some are special, when needing a call subscriber terminal to send ROUTREQ request for the second time, flow process according to present protocol definition, this moment, the called subscriber was in the service access process, and directly refusal is called out, and caused this call flow failure.

At the shortcoming in the above-mentioned agreement, relevant manufacturer has proposed the processing mode that a kind of processing repeatedly sends routing information, concrete handling process, as shown in Figure 2:

Step 201～step 205, when first time during customer call, MSC2/VLR2 distributes a TLMN1 to it, and this process is described in front, here no longer repeats.

Step 206, when the user initiates the routing iinformation request again, MSC1/VLR1 sends LOCREQ message to HLR, the request called user information.

The routing iinformation request is because special professional caused, also may cause unusually owing to HLR; Described here user can for the identical user of calling party's first time, also can for the different user of calling party's first time.

Step 207, HLR requires called MS C2/VLR2 to give calling mobile terminal distribution T LDN to sending ROUTREQ message to MSC2/VLR2.

Step 208, MSC2/VLR2 returns the routreq response, is caller MS distribution T LDN2.

Step 209, HLR returns the locreq response message to MSC1/VLR1, gives caller MSC1/VLR1 TLDN2.

Step 210, MSC1/VLR1 sends IAM message according to preset rule to MSC2/VLR2, and wherein Chu Ju called number is called TLDN1 or TLDN2 number.

Step 211～step 217 is set up one and is communicated to connect between MSC1/VLR1 and the MSC2/VLR2, and refusal access request thereafter, and follow-up workflow is consistent with foregoing flow process, here no longer repeats.

Simultaneously, when the local exchange mobile subscriber calls out the intra-office subscribers of local exchange, the flow process of the flow process of some the HLR equipment in the mobile telephone exchange network during still according to station to station call handled, when MSC when such HLR docks, also can occur in the unusual flow process of getting twice routing iinformation in the call; When the situation that between the local subscriber, takes place repeatedly to send routing information, also adopted said method, as shown in Figure 3.

Step 301～step 305, MSC/VLR is according to the number that the calling subscriber dialed, send LOCREQ message to HLR (though the called subscriber at local exchange, HLR still handles according to the flow process of station to station call, to call out Originating Office send send routing information).Originating Office handles according to normal station to station call and has distributed TLDN1.HLR turns back to Originating Office with TLDN1, and indication caller and called belonging in the same MSC/VLR scope.

Step 306～step 307, after MSC/VLR receives the LOCREQ response, MSC detects the TEMLIST packet of taking back, confirm caller and called when same MSC, local exchange MSC can simulated HLR sends route request information ROUTREQ to local exchange, and local exchange MSC/VLR can be calling terminal distribution T LDN2 once more.

Step 308～step 311, follow-up workflow is consistent with foregoing flow process, here no longer repeats.

Though said method has solved the user when repeatedly sending routing information, unaccepted situation, but in above-mentioned handling process, still have problems, when the party A-subscriber calls out called party B-subscriber, for same called subscriber B, when the party A-subscriber called out Incoming for the first time, local exchange had distributed TLDN1, before this calls out access failure, if there is C, D user's incoming call, simultaneously, again sub-distribution TLDN2, TLDN3......, in fact for repeatedly incoming call, for once calling out finally can be successful, and other callings all can be rejected in follow-up flow process.If allow simultaneously to continue distribution T LDN during the user waits for incoming call, distribute two or more TLDN for call simultaneously, may cause TLDN resource and relay resource exhaustion, cause system can't tackle the impact of Bulk Call.

Summary of the invention

At the problem that exists in the such scheme, for make wireless communication system can process user the situation of request route information repeatedly, simultaneously also in order to save the TLDN resource, the present invention proposes a kind of call processing method, preferably resolve the problems referred to above.

The present invention proposes a kind of method of call treatment, terminal called is in the calling access procedure that first call subscriber terminal is initiated, the routing iinformation of the same called user terminal of the second call subscriber terminal request, called MS C judges that second call subscriber terminal and first call subscriber terminal are same call subscriber terminal, and then called VLR is that second call subscriber terminal distributes the routing iinformation identical with first call subscriber terminal; Otherwise, return called user terminal busy condition information to second call subscriber terminal.

In the such scheme, described called VLR returns called user terminal busy condition information indication called user terminal to second calling mobile terminal and is in access state, and refusal is that second call subscriber terminal distributes routing iinformation.

In the such scheme, described called VLR returns called user terminal busy condition information indication called user terminal to second calling mobile terminal and is in talking state, and is that second call subscriber terminal distributes routing iinformation.

In the such scheme, before all operations, at first in the MSC/VLR at called user terminal place, be set to the quantity that second call subscriber terminal distributes routing iinformation.

In the such scheme, described called VLR returns called user terminal busy condition information indication called user terminal to second calling mobile terminal and is in talking state, and is second call subscriber terminal distribution routing iinformation of predetermined amount.

In the such scheme, described called VLR returns called user terminal busy condition information indication called user terminal to second calling mobile terminal and is in talking state, and refusal is that second call subscriber terminal distributes routing iinformation.

In the such scheme, described called MS C judges by comparing the cell of this calling of sign in the route request information whether first call subscriber terminal and second call subscriber terminal are same call subscriber terminal.

In the such scheme, described first call subscriber terminal is fixed terminal or portable terminal, and described second call subscriber terminal is fixed terminal or portable terminal, and described called user terminal is a portable terminal.

In the such scheme, described routing iinformation is Temporary Local Directory Number TLDN.

A kind of call processing method that the present invention proposes, effectively supported in the wireless communication system, the user is the situation of request route information repeatedly, the system that solved is in supporting the call process, repeatedly during request route information, the duplicate allocation Temporary Local Directory Number that occurs or the situation of call failure, by being in the call, during same user's request route information, the mode of distributing identical Temporary Local Directory Number, not only save the Temporary Local Directory Number resource, and do not influenced the normal handling flow process that different calling subscribers dial identical called original normal refusal one side simultaneously.

Description of drawings

Fig. 1 is a normal call flows in cordless communication network;

Fig. 2 is for handling the mode that repeatedly sends routing information under the prior art condition;

Fig. 3 is under the prior art condition, the mode that repeatedly sends routing information between the local subscriber;

Fig. 4 when calling out between the portable terminal, the handling process that repeatedly sends routing information that the present invention proposes;

Between the local subscriber of Fig. 5 for the present invention's proposition, the handling process that repeatedly sends routing information;

When Fig. 6 calls out portable terminal for fixed terminal, the handling process that repeatedly sends routing information.

Embodiment

In order to make purpose of the present invention, technical scheme and advantage more clear, below we will be in conjunction with concrete execution mode, and be described further with reference to accompanying drawing.

In an embodiment, we to define first call subscriber terminal be call subscriber terminal current or that connect with called user terminal; Second call subscriber terminal is meant in first subscriber terminal access process, asks the call subscriber terminal of same called user terminal routing iinformation.

The present invention proposes a kind of call treatment mode, at first call subscriber terminal in access procedure, the routing iinformation of the same called user terminal of the second call subscriber terminal request, called MS C judges that second call subscriber terminal and first call subscriber terminal are same call subscriber terminal, and then called VLR distributes identical routing iinformation for it.

Below we illustrate workflow of the present invention in conjunction with concrete example, as shown in Figure 4, comprise step:

Step 401～step 405, when being the calling of first call subscriber terminal, MSC2/VLR2 is that it distributes routing iinformation TLDN1, this process is described in front, here no longer repeats.

Step 406, second call subscriber terminal is initiated the routing iinformation request, and MSC1/VLR1 sends LOCREQ message to HLR, the request called user information;

Wherein, carried the called user information of representing this calling in the LOCREQ message, as called number etc., HLR can retrieve the stored information of called user terminal according to the information of carrying in this message, and then can find called user terminal present located positional information, find the MSC2/VLR2 at called place.

Step 407, HLR sends routing iinformation request message ROUTREQ to the MSC2/VLR2 at called user terminal place;

Wherein, in the ROUTREQ message, carried the cell that identifies this calling, as call subscriber terminal number CPNSTRG1, BILLID etc.

Step 408, MSC2/VLR2 judges whether second call subscriber terminal and first call subscriber terminal are same user terminal, and returns routreq message;

MSC2 is at same called user terminal, judges that whether call subscriber terminal is that same, concrete step is as follows:

MSC2/VLR2 can store the number NUM1 of first call subscriber terminal that or connecting with called user terminal, when the second call subscriber terminal NUM2 sends route requests, then MSC2/VLR2 judges whether NUM1 is identical with NUM2, if it is identical, then be same calling subscriber, otherwise be different users;

When being same calling subscriber, MSC2/VLR2 returns routreq to HLR, has wherein carried the identical TLDN1 with NUM1.

When being different calling subscriber, then MSC2/VLR2 returns called user terminal busy condition information in routreq message, is used to refer to called user terminal present located state:

The busy condition of called user terminal has two kinds of situations: be in talking state and be in access state.

1, when MSC2/VLR2 judged that called user terminal is in talking state, we can handle accordingly according to setting in advance.

When allowing Call Waiting in the system: MSC2/VLR2 returns called user terminal state information indication called user terminal and is in talking state, and be, request inserts second call subscriber terminal and distributes different TLDN, or, be the different TLDN of second call subscriber terminal distribution of specified quantity.

Above-mentioned MSC2/VLR2 is that second call subscriber terminal of specified quantity distributes among the different TLDN, must certain quantity be set in MSC2/VLR2 at first, indicates VLR2 to carry out the distribution of TLDN.

When not allowing Call Waiting in the system: MSC2/VLR2 returns called user terminal state information indication called user terminal and is in talking state, and refusal is the second call subscriber terminal distribution T LDN, and refusal is called out and inserted.

2, when MSC2/VLR2 judges that called user terminal is in access state, return called user terminal state information indication called user terminal and be in access state, and refuse this calling, be not its distribution T LDN.

In the present embodiment, we are assumed to be same calling subscriber.

Step 409, HLR returns the locreq response message to MSC1/VLR1;

Step 410～step 417 establishes a communications link between MSC1/VLR1 and the MSC2/VLR2, and this flow process is identical with the workflow of prior art, here no longer repeats.

We can see by the foregoing description, in the process that call subscriber terminal repeatedly sends routing information, whether identical by judging call subscriber terminal, determine whether and how to come distribution T LDN, increase the flexibility of distribution T LDN like this, also saved the TLDN resource simultaneously.

Equally, when call subscriber terminal and called user terminal belonged to identical MSC/VLR, the call processing method that the present invention proposes was suitable equally, and concrete workflow as shown in Figure 5.

Step 501～step 505, concrete workflow is identical with step 301～step 305, here repeats no more;

Step 506～step 507, after MSC/VLR received the LOCREQ response, MSC detected the TEMLIST packet of taking back, and confirmed caller and called when same MSC, and local exchange MSC can send route request information ROUTREQ to local exchange by simulated HLR.In this case, local exchange MSC/VLR is judged as same call subscriber terminal, then distributes identical TLDN1 for it.

Step 508～step 511, follow-up workflow is consistent with foregoing flow process, here no longer repeats.

Therefore, when caller and called user terminal belonged to identical MSC/VLR, the method that can adopt the present invention to propose for identical call subscriber terminal distributes identical TLDN, had so just been avoided the waste of TLDN resource equally.

A kind of call processing method that the present invention proposes is equally applicable to the situation that fixed terminal is called out terminal called, and concrete workflow comprises the steps: as shown in Figure 6

Step 601, PSTN initiates the IAI initial address message and arrives, and has wherein carried the called user terminal number;

Step 602, GMSC/VLR carries out number analysis, and sends position request information LOCREQ to the HLR that called user terminal belonged to;

Step 603, HLR sends routing iinformation request message ROUTREQ to the MSC/VLR at called place, has wherein carried called user terminal number and caller fixed terminal number;

Step 604, called MS C2/VLR2 is according to caller fixed terminal number information among the ROUTREQ and called mobile terminal number information, judging does not have user and called mobile terminal to connect, then MSC2/VLR2 sends the routreq response message to HLR, has wherein carried the TLDN1 that MSC2/VLR2 distributes for the caller fixed terminal;

Step 605, HLR returns the locreq response message to GMSC/VLR;

Step 606, the user initiates the routing iinformation request again, and GMSC/VLR sends LOCREQ message to HLR, the request called user information;

Step 607, HLR sends routing iinformation request message ROUTREQ to the MSC/VLR at called place, has wherein carried called user terminal number and caller fixed terminal number;

Step 608, called MS C2/VLR2 is according to caller fixed terminal number information among the ROUTREQ and called mobile terminal number information, judge that first call subscriber terminal or connects with called mobile terminal, then MSC2/VLR2 judges that request inserts user's second call subscriber terminal and whether first call subscriber terminal is same user, and returns the routreq response message to HLR;

When being same user, then MSC2/VLR2 is that second call subscriber terminal distributes identical TLDN1, when being different user, returns the called subscriber busy state information, and concrete operation is identical with step 408, here repeats no more.

Step 609, HLR returns the locreq response message to GMSC/VLR;

Step 610, GMSC/VLR sends the IAI initial address message to called MS C2/VLR2, enters incoming message;

Step 611～step 617 establishes a communications link between GMSC/VLR and the MSC2/VLR2, and this flow process is identical with the workflow of prior art, here no longer repeats.

In the access process of said fixing terminal call portable terminal, GMSC and MSC2 can be same switches.By such scheme as can be known, the same situation of calling out portable terminal with fixed terminal of using of the call processing method of the present invention's proposition.

A kind of call processing method that the present invention proposes, the system that effectively solved is in supporting the call process, repeatedly during request route information, the situation of the duplicate allocation Temporary Local Directory Number that occurs, by being in the call, during same user's request route information, the mode of distributing identical Temporary Local Directory Number has been saved the Temporary Local Directory Number resource.

Above-described specific embodiment; purpose of the present invention, technical scheme and beneficial effect are further described; institute is understood that; the above only is specific embodiments of the invention; be not limited to the present invention; within the spirit and principles in the present invention all, any modification of being made, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.

Claims

1, a kind of method of call treatment, terminal called is in the calling access procedure that first call subscriber terminal is initiated, and the routing iinformation of the same called user terminal of the second call subscriber terminal request is characterized in that,

Called MS C judges that second call subscriber terminal and first call subscriber terminal are same call subscriber terminal, and then called VLR is that second call subscriber terminal distributes the routing iinformation identical with first call subscriber terminal; Otherwise, return called user terminal busy condition information to second call subscriber terminal.

2, the method for a kind of call treatment as claimed in claim 1, it is characterized in that, described called VLR returns called user terminal busy condition information indication called user terminal to second calling mobile terminal and is in access state, and refusal is that second call subscriber terminal distributes routing iinformation.

3, the method for a kind of call treatment as claimed in claim 1, it is characterized in that, described called VLR returns called user terminal busy condition information indication called user terminal to second calling mobile terminal and is in talking state, and is that second call subscriber terminal distributes routing iinformation.

4, the method for a kind of call treatment as claimed in claim 1 is characterized in that, this method comprises that further system in the MSC/VLR at called user terminal place, is set to the quantity that second call subscriber terminal distributes routing iinformation in advance.

5, the method for a kind of call treatment as claimed in claim 4, it is characterized in that, described called VLR returns called user terminal busy condition information indication called user terminal to second calling mobile terminal and is in talking state, and is second call subscriber terminal distribution routing iinformation of predetermined amount.

6, the method for a kind of call treatment as claimed in claim 1, it is characterized in that, described called VLR returns called user terminal busy condition information indication called user terminal to second calling mobile terminal and is in talking state, and refusal is that second call subscriber terminal distributes routing iinformation.

7, as the method for the described a kind of call treatment of claim 1 to 6, it is characterized in that, called MS C judges by comparing the cell of this calling of sign in the route request information whether first call subscriber terminal and second call subscriber terminal are same call subscriber terminal.

8, as the method for any described a kind of call treatment in the claim 7, it is characterized in that, described first call subscriber terminal is fixed terminal or portable terminal, and described second call subscriber terminal is fixed terminal or portable terminal, and described called user terminal is a portable terminal.

As the method for any described a kind of call treatment in the claim 7, it is characterized in that 9, described routing iinformation is Temporary Local Directory Number TLDN.