WO2011032395A1 - 一种旁路被叫智能的方法及系统 - Google Patents

一种旁路被叫智能的方法及系统 Download PDF

Info

Publication number
WO2011032395A1
WO2011032395A1 PCT/CN2010/073048 CN2010073048W WO2011032395A1 WO 2011032395 A1 WO2011032395 A1 WO 2011032395A1 CN 2010073048 W CN2010073048 W CN 2010073048W WO 2011032395 A1 WO2011032395 A1 WO 2011032395A1
Authority
WO
WIPO (PCT)
Prior art keywords
vmsc
gmsc
called
called smart
bypasses
Prior art date
Application number
PCT/CN2010/073048
Other languages
English (en)
French (fr)
Inventor
陈建红
曹小飞
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to US13/393,301 priority Critical patent/US8660553B2/en
Priority to IN1900DEN2012 priority patent/IN2012DN01900A/en
Publication of WO2011032395A1 publication Critical patent/WO2011032395A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/082—Mobility data transfer for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • H04Q3/0016—Arrangements providing connection between exchanges
    • H04Q3/0025—Provisions for signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • H04Q3/0016—Arrangements providing connection between exchanges
    • H04Q3/0029—Provisions for intelligent networking
    • H04Q3/0045—Provisions for intelligent networking involving hybrid, i.e. a mixture of public and private, or multi-vendor systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/12—Mobility data transfer between location registers or mobility servers

Definitions

  • the present method relates to the field of mobile networks, and particularly relates to a mobile switching center (MSC) and a called party in a CDMA mobile network where a service control point (SCP) of a called user is faulty and a called location request is located.
  • MSC mobile switching center
  • SCP service control point
  • a method and system for intelligent bypassing in the case where the MSC where the current location is located is not the same MSC.
  • the present invention proposes a method for calculating the called bypass SCP, that is, BYPASS SCP, which determines the state or communication status of the SCP before interacting with the SCP. If it is normal, the call is connected. The trigger is triggered to the SCP normally. If it is not normal, the trigger is not triggered and the user is connected as a non-intelligent user. The bills are replenished through the CDRs issued by the MSC to minimize the loss of operators and improve user satisfaction.
  • the smart trigger of the called user triggers two MSCs.
  • the first is the Gateway Mobile Switching Center (GMSC), GMSC.
  • the MSC which has the Service Switch Point (SSP) function) for initiating the called location request, and then the end office - the Visited Mobile Switching Centre (VMSC), which is the current location of the called party.
  • SSP Service Switch Point
  • VMSC Visited Mobile Switching Centre
  • the MSC where it is located.
  • the GMSC may bypass the called smart because the communication with the called SCP is faulty, and the VMSC communicates with the SCP normally without bypassing the called smart, so that the call still fails. Conversely, if the GMSC does not bypass the SCP and the VMSC bypasses the SCP, the call will still fail.
  • FIG. 1 is a schematic diagram of an intelligent network structure of a CDMA mobile network. Under normal circumstances, when the MSC finds that the user is a smart user, it must interact with the SCP when connecting the user.
  • the called smart trigger list is obtained from the Home Location Register (HLR) through registration, qualification indication or qualification request; the called smart trigger list is also obtained in a way, that is, the gateway office uses the location request. Obtain.
  • Figure 2 depicts how the end office VMSC gets the list of called smart triggers:
  • S201 The mobile terminal (MS) initiates a location update request to a base station controller (BSC);
  • BSC base station controller
  • the BSC After receiving the location update request, the BSC sends the request to the MSC where the called party is currently located, that is, the VMSC;
  • the HLR receives the registration request, updates the user information, returns a registration response to the VMSC, and carries the list of called smart triggers.
  • the figure shows that the existing gateway GMSC and the end office VMSC are not the same MSC, and the gateway GMSC determines that the called smart is not required to be bypassed, and the end office VMSC determines that the bypassed called smart is required:
  • the GMSC After receiving the call request, the GMSC sends a location request to the HLR.
  • the HLR After receiving the location request, the HLR queries the user information included in the location request, finds that the user is a smart user, returns a location response to the gateway GMSC, and carries the list of called smart triggers;
  • S305 The gateway GMSC receives the initial terminal trigger response returned by the SCP;
  • S306 The gateway office GMSC sends a location request to the HLR, where the trigger is a location triggering crying.
  • S307 The HLR sends a routing request to the end office VMSC.
  • S308 The end office VMSC returns a routing request response to the HLR.
  • the HLR returns a location request response to the gateway GMSC, where the location request response carries the called routing information;
  • the gateway GMSC sends a call trigger address available trigger to the SCP;
  • S311 The SCP sends a trigger routing address available trigger response to the gateway GMSC;
  • the gateway GMSC After receiving the triggered routing address of the SCP, the gateway GMSC receives the trigger response, and the analysis number obtains the corresponding service MSC route, and sends a call request to the end office VMSC.
  • S313 The end office VMSC receives the call request, and finds that the called party is the local office. The user is an intelligent user, and continues to determine whether it is necessary to bypass the called smart on the VMSC. If the bypass is required, the end office VMSC connects to the called party. After the called party rings, the end office VMSC rings the gateway GMSC.
  • S314 The gateway office GMSC forwards the ringing to the front office;
  • step S315 The called party responds, and the end office VMSC sends a response to the gateway office GMSC; in this step, the response sent by the end office VMSC to the gateway office GMSC is a response corresponding to the call request sent by the gateway office GMSC to the end office VMSC in step S312;
  • S316 The gateway office GMSC forwards the call to the front office, and the main callee enters the call;
  • the SCP sends a message to the GMSC to announce the release of the call because the response trigger is not received for a long time;
  • Step S317 is also that the gateway GMSC and the end office VMSC are not the same MSC, the gateway The GMSC does not bypass the called smart, and the end office VMSC bypasses the called smart, which causes the call to fail. That is, because the SCP called the smart is triggered on the gateway GMSC, the VMSC needs to bypass the called smart and therefore cannot An acknowledgment trigger is returned to the SCP, causing the SCP to release the call due to an unsuccessful response to the response trigger for a long time.
  • S318 The gateway office GMSC sends a release call message to the front office;
  • the gateway GMSC sends a release message to the end office VMSC.
  • the figure shows that the existing gateway GMSC and the end office VMSC are not the same MSC, and the gateway office GMSC determines that the called party intelligence needs to be bypassed, and the end office VMSC determines that the bypass called party intelligence is not required:
  • S401 Sending a call request to the front office gateway GMSC;
  • the GMSC After receiving the call request, the GMSC sends a location request to the HLR.
  • the HLR After receiving the location request, the HLR queries the user information in the location request, finds that the user is a smart user, returns a location response to the gateway GMSC, and carries the called smart trigger list; S404: the gateway GMSC receives the location response, Found that there is a list of called smart triggers, according to the list of called smart triggers (such as whether the corresponding SCP is faulty) to determine the need for bypass intelligence; send a location request to the HLR, wherein the trigger is a position trigger;
  • S405 The HLR sends a routing request to the end office VMSC.
  • S406 The end office VMSC returns a routing request response to the HLR.
  • S407 The HLR returns a location request response to the gateway GMSC, where the location request response carries the called routing information.
  • the gateway office GMSC sends a call request to the end office VMSC;
  • the end office VMSC After receiving the call request, the end office VMSC finds that the called party is the local user and is a smart user, and continues to determine whether the called smart device needs to be bypassed on the VMSC, and finds that the bypass VMSC is connected to the called party, and is called After ringing, the end office VMSC sends a ring to the gateway GMSC;
  • S410 The gateway GMSC forwards the ringing to the front office;
  • S411 The called party responds, and the end office VMSC sends a response to the SCP;
  • S412 The end office VMSC sends a response to the gateway office GMSC;
  • S413 The gateway office GMSC forwards the response to the front office, and the main called party enters the call;
  • step S414 The SCP directly receives the response because it has not received the trigger before, which may be considered as an error, and sends a release indication to the terminal office VMSC; step S414 is that the gateway GMSC and the end office VMSC are not the same MSC, and the gateway office GMSC Bypassing the called smart, and the end office VMSC does not bypass the called smart, causing the call to fail, that is, because the gateway GMSC bypasses the called smart does not trigger the called smart, and the end office VMSC triggers Called smart, the response trigger is returned to the SCP, causing the SCP to receive the response directly without receiving the trigger, and the call is considered to be an error.
  • S415 The end office VMSC sends a release call message to the gateway office GMSC;
  • S416 The gateway office GMSC sends a release message to the front office.
  • the deficiencies in Figure 3 and Figure 4 above are not limited to the primary and backup disasters. They exist in all kinds of MSC disaster tolerance. Currently, the GMSC and the VMSC are not the same MSC. Whether the GMSC and the VMSC bypass the called party. There is no corresponding solution to the problem that the intelligent situation is different and the call fails.
  • the technical problem to be solved by the present invention is to provide a method and system for bypassing called party intelligence to solve the problem that a call failure may occur when a GMSC and a VMSC are not the same MSC.
  • the present invention provides a method for bypassing called party intelligence, which is applied to a case where a gateway office (GMSC) and a terminal office (VMSC) are not the same mobile switching center (MSC), in a call process,
  • GMSC gateway office
  • VMSC terminal office
  • MSC mobile switching center
  • the GMSC sends the information of whether the GMSC bypasses the called smart to the VMSC; the VMSC determines whether the GMSC bypasses the called smart according to whether the GMSC bypasses the called smart information, and determines whether the VMSC bypasses the called smart; When the VMSC determines that the GMSC bypasses the called smart, and the VMSC determines that the VMSC does not bypass the called smart, the VMSC does not trigger the called smart; when the VMSC determines that the GMSC does not bypass the called smart, and the VMSC determines that the VMSC is next to the VMSC When the road is called smart, the VMSC sends a call release to the GMSC, thereby implementing complete bypass of the called smart.
  • the method further includes: when the VMSC determines that the GMSC bypasses the called smart, and the VMSC determines that the VMSC bypasses the called smart, the VMSC bypasses the called smart; when the VMSC determines that the GMSC does not bypass the called smart, and the VMSC determines When the VMSC does not bypass the called smart, the VMSC does not bypass the called smart.
  • the GMSC sends the information of whether or not to bypass the called intelligent information to the VMSC.
  • the GMSC sends the information to the VMSC via the home location register (HLR) in the location request.
  • HLR home location register
  • the step of the GMSC notifying the VMSC whether to bypass the called smart information includes: the GMSC obtaining the called smart trigger list from the HLR; the GMSC analyzing, according to the called smart trigger list, whether the GMSC bypasses the called smart, and Setting the smart bypass identifier according to whether the GMSC bypasses the called smart, and transmitting the smart bypass identifier in the location request to the VMSC via the HLR;
  • the VMSC determines whether the GMSC bypasses the called smart according to whether the GMSC bypasses the information of the called smart, and the VMSC determines whether the GMSC bypasses the called smart according to the received smart bypass identifier.
  • the method further includes: the VMSC does not send a response indication to the SCP, and the VMSC sends a call request response to the GMSC, and the GMSC will The call request response is forwarded to the front office, and the main called party enters the call.
  • the present invention also proposes a system for bypassing called intelligent, which is applied to
  • GMSC gateway office
  • VMSC end office
  • MSC mobile switching center
  • the GMSC is configured to: send a signal indicating whether the GMSC bypasses the called smart to the VMSC;
  • the VMSC is configured to: determine whether the GMSC bypasses the called smart according to whether the GMSC bypasses the called smart information, and determines whether the VMSC bypasses the called smart, when the VMSC determines that the GMSC bypasses the called smart, and determines that the VMSC is not next to When the road is called smart, the VMSC does not trigger the called smart.
  • the VMSC determines that the GMSC does not bypass the called smart, and the VMSC determines that the VMSC bypasses the called smart, the VMSC sends a call release to the GMSC, thereby supporting the complete bypass. Call smart.
  • the VMSC is further configured to: when the VMSC determines that the GMSC bypasses the called smart, and determines that the VMSC bypasses the called smart, the VMSC bypasses the called smart; when the VMSC determines that the GMSC does not bypass the called smart, and determines the VMSC When bypassing the called smart, the VMSC does not bypass the called smart.
  • the system also includes a Home Location Register (HLR): the GMSC is information set to whether the GMSC bypasses the called intelligence is carried in the location request and sent to the VMSC via the HLR.
  • HLR Home Location Register
  • the GMSC is configured to transmit the information of whether the GMSC bypasses the called smart in the location request by the HLR to the VMSC: the GMSC obtains the list of called smart triggers from the HLR; the GMSC is called according to the called The smart trigger list analyzes whether the GMSC bypasses the called smart, sets the smart bypass identifier according to whether the GMSC bypasses the called smart, and carries the smart bypass identifier in the location request and sends the WBR to the VMSC through the HLR;
  • the VMSC is configured to determine whether the GMSC bypasses the called smart according to the received smart bypass identifier.
  • the VMSC is also configured to: When it is determined that the GMSC bypasses the called smart, and the VMSC determines
  • the GMSC is further configured to: forward the call request response to the front office, so that the main called party enters a call state.
  • the present invention also provides an end office visited mobile switching center (VMSC), which is not the same mobile switching center (MSC) as the gateway (GMSC), and the VMSC includes:
  • the information receiving module is configured to: receive information about whether the GMSC bypasses the called smart device; and bypass the called smart instructing module, and set the method to: determine whether the GMSC is bypassed according to whether the GMSC bypasses the called smart information Calling the smart, and judging whether the VMSC bypasses the called smart.
  • the called smart is not triggered; when it is determined that the GMSC is not bypassed
  • the call is released to the GMSC.
  • the bypass called smart indication module is further configured to:
  • the VMSC determines that the GMSC bypasses the called smart, and determines that the VMSC bypasses the called smart, the VMSC bypasses the called smart;
  • the VMSC determines that the GMSC does not bypass the called intelligence and determines that the VMSC does not bypass the called intelligence, the VMSC does not bypass the called intelligence.
  • the bypass called smart indication module is further configured to: when it is determined that the GMSC bypasses the called smart, and the VMSC determines that the VMSC does not bypass the called smart, does not send a response indication to the SCP, and sends a call request response to the GMSC, So that the GMSC forwards the call request response to the front office, so that the main called party enters the call state.
  • the invention provides a method and system for completely bypassing called intelligent, which effectively solves
  • FIG. 1 is a schematic diagram of a CDMA mobile network intelligent network structure
  • FIG. 2 is a schematic diagram of a process for obtaining a list of user called smart triggers in the prior art
  • FIG. 3 is a schematic diagram of an existing called user location request and a current location not in the same MSC
  • the gateway of the gateway is not bypassed but the call flow diagram of the intelligent bypass of the end office
  • Figure 4 is the call flow of the existing gateway user's location request and the gateway bypass smart bypass when the current location is not in the same MSC but the end office is not bypassed.
  • Figure 5 is a call flow diagram of the present invention in the case where the gateway request is not bypassed when the location request and the current location are not in the same MSC, but the end office finds that bypass is required;
  • Figure 6 is the present invention where the location request and the current location are not present. Call flow diagram in the case of intelligent bypass of the gateway at the same MSC.
  • the solution of the present invention is described in detail by taking the shortcomings of the active and standby disaster recovery instances of the existing MSC mentioned in the background.
  • the present invention is directed to the gateway GMSC and the service end office VMSC are not the same MSC, and the gateway GMSC determines that there is no need to bypass the called smart, in order to avoid the situation shown in FIG. 3, that is, the end office bypasses the called smart.
  • the present invention proposes the following solution. Referring to FIG. 5, the steps are as follows:
  • S501 Sending a call request to the front office gateway GMSC;
  • the GMSC After receiving the call request, the GMSC sends a location request to the HLR.
  • the HLR After receiving the location request, the HLR queries the user information in the location request, finds that the user is a smart user, returns a location response to the gateway GMSC, and carries the list of called smart triggers; S504: The gateway GMSC receives the location response, A list of called smart triggers is found. If it is determined according to the list of called smart triggers (for example, whether the corresponding SCP is faulty), it is determined that bypass intelligence is not required. Send an initial terminal trigger to the SCP;
  • S505 The gateway station receives the initial terminal trigger response sent by the SCP.
  • the gateway GMSC sends a location request carrying the smart bypass identifier to the HLR, where the smart bypass identifier indicates that the called smart is not bypassed on the GMSC; wherein the trigger triggers the crying of the initial terminal?
  • the HLR sends a routing request to the end office VMSC, and carries the smart bypass identifier.
  • S508 After receiving the routing request sent by the HLR, the end office VMSC determines, according to the smart bypass identifier in the routing request, that the called smart is not bypassed on the GMSC, and the current VMSC side records that the current GMSC is not bypassed. The called intelligent information is then sent to the HLR loop by the request response; S509: The HLR returns a location request response to the gateway office GMSC, and the location request response carries the called routing information;
  • the gateway GMSC triggers the routing address available trigger to the SCP
  • the gateway GMSC receives the triggered routing address of the SCP and responds with a trigger, and the analysis number obtains the route corresponding to the serving MSC, that is, the route of the VMSC, and then sends a call request to the terminal VMSC;
  • S512 The end office VMSC receives the call request, finds that the called party is the local user and is an intelligent user, and continues to determine whether the called party intelligence needs to be bypassed on the VMSC, and finds that the bypass is required, and the current VMSC recorded by the end office VMSC side is determined. Whether the information of the called smart is bypassed, and it is found that the called smart is not bypassed on the GMSC; S513: the end office VMSC sends a call release to the gateway GMSC; that is, the present invention is directed to the case where the GMSC and the server VMSC are not the same MSC. The GMSC notifies the VMSC whether the GMSC bypasses the called smart.
  • the VMSC When the VMSC performs call connection, if the GMSC does not bypass the called smart, and the VMSC needs to bypass the called smart, the VMSC sends a call release to the GMSC.
  • the VMSC if the VMSC is in the call connection, if it is judged that the GMSC does not bypass the called smart, and the VMSC does not need to bypass the called smart, the called smart is not bypassed on the VMSC, and the normal call can be realized without appearing. Whether the GMSC is inconsistent with the called smart on the VMSC causes the call to fail. Therefore, it will not be described in detail here.
  • S514 The gateway GMSC forwards and releases to the front office, and the called party is released.
  • the gateway GMSC needs to bypass the called smart.
  • the end office does not bypass the called smart, causing the call to fail.
  • the present invention proposes the following solution. Referring to FIG. 6, the steps are as follows:
  • S601 Sending a call request to the front office gateway GMSC;
  • the GMSC After receiving the call request, the GMSC sends a location request to the HLR.
  • the HLR After receiving the location request, the HLR queries the user information in the location request, finds that the user is a smart user, returns a location response to the gateway GMSC, and carries the list of called smart triggers;
  • S604 The gateway GMSC receives the location response, and finds that there is a list of called smart triggers. According to the list of called smart triggers (such as whether the corresponding SCP is faulty), it is determined that the called smart is required to be bypassed; and the HLR is sent with the intelligent bypass identifier. a location request, where the smart bypass identifier indicates that the called smart is bypassed on the GMSC; the trigger is a location trigger; S605: the HLR sends a routing request to the end office VMSC, carrying the smart bypass identifier;
  • the end office VMSC After receiving the routing request sent by the HLR, the end office VMSC determines to bypass the called smart on the GMSC according to the smart bypass identifier in the routing request, and records the current bypassed called smart on the GMSC on the VMSC side. Information, and then respond to the HLR loop by request;
  • the HLR sends a location request response to the gateway GMSC, where the location request response carries the called routing information;
  • the gateway office sends a call request to the end office VMSC according to the called routing information, and the end office VMSC receives the call request and continues to be called;
  • S609 The called party rings, and the end office VMSC sends a ring to the gateway GMSC;
  • S610 The gateway GMSC forwards the ringing to the front office;
  • S611 The called party responds, and the end office VMSC finds that the called party is the local user and is a smart user, and continues to determine whether the called party smart needs to be bypassed on the VMSC, and finds that it is not needed. Road, judge the VMSC Whether the current saved information on the GMSC bypasses the called intelligent, and finds that the called intelligent is bypassed on the GMSC, the SCP is not sent a response indication, and the end office VMSC sends a response to the gateway GMSC; that is, the present invention is directed to the GMSC.
  • the VMSC is notified whether the GMSC bypasses the called intelligent.
  • the VMSC performs call connection, if the GMSC bypasses the called smart, the VMSC does not need to bypass the called party. Intelligent, the VMSC does not trigger the called smart, that is, does not give the SCP a response indication.
  • the VMSC if it is determined that the GMSC bypasses the called smart, and the VMSC needs to bypass the called smart, the VMSC bypasses the called smart, and can implement a normal call without GMSC and VMSC. Whether the situation of the called smart is inconsistent or not causes the call to fail, and therefore will not be described in detail here.
  • S612 The gateway GMSC forwards the response to the front office, and the main called party enters the call;
  • S614 The gateway GMSC sends a release message to the front office, and the call is released.
  • the present invention also provides a system for the case where the gateway GMSC and the end office VMSC are not the same MSC, including the GMSC, the VMSC, the HLR, and the SCP, where:
  • the GMSC is set to: notify the VMSC of whether it bypasses the called smart information.
  • the GMSC is configured to carry the information of whether or not to bypass the called intelligence in the location request and sent to the VMSC via the HLR. Yes, the GMSC can get the list of called smart triggers from the HLR and analyze it.
  • the smart bypass identifier is set according to whether the GMSC bypasses the called intelligent, and the smart bypass identifier is carried in the location request and sent to the VMSC through the HLR, and the VMSC receives the smart bypass identifier.
  • the smart bypass identifier makes a judgment to know whether the GMSC bypasses the information of the called smart.
  • the VMSC is set to: perform call processing according to whether the GMSC bypasses the called smart information:
  • the VMSC determines that the GMSC bypasses the called smart, and the VMSC does not need to bypass the called smart, the VMSC does not trigger the called smart.
  • the VMSC determines that the GMSC does not bypass the called smart, the VMSC needs to be next to it.
  • the VMSC sends a call release to the GMSC; when the VMSC determines that the GMSC bypasses the called smart, and the VMSC needs to bypass the called smart, the VMSC bypasses the called smart; the VMSC determines that the GMSC does not bypass the called party. Intelligent, when the VMSC does not need to bypass the called smart, the VMSC does not bypass the called smart.
  • the VMSC is further configured to: when it is determined that the GMSC bypasses the called smart, the VMSC does not need to bypass the called smart, does not send a response indication to the SCP, sends a call request response to the GMSC, and the GMSC forwards the response to the front office, Realize the call between the main and the called.
  • the present invention also provides an end office visited mobile switching center (VMSC), which is not the same mobile switching center (MSC) as the gateway (GMSC), and the VMSC includes:
  • the information receiving module is configured to: receive information about whether the GMSC bypasses the called smart device; and bypass the called intelligent indicating module, and set the method to: determine whether the GMSC bypasses the called smart device according to whether the GMSC bypasses the called smart information And determining whether the VMSC bypasses the called smart.
  • the called smart is not triggered; when it is determined that the GMSC does not bypass the called smart, And when it is determined that the VMSC bypasses the called smart, the call release is sent to the GMSC.
  • the bypass called intelligent indicator module is also set to:
  • the VMSC determines that the GMSC bypasses the called smart, and determines that the VMSC bypasses the called smart, the VMSC bypasses the called smart;
  • the VMSC determines that the GMSC does not bypass the called intelligence and determines that the VMSC does not bypass the called intelligence, the VMSC does not bypass the called intelligence.
  • the bypass called intelligent indication module is further configured to: when it is determined that the GMSC bypasses the called smart, and the VMSC determines that the VMSC does not bypass the called smart, does not send an acknowledgement indication to the SCP, and sends a call request response to the GMSC, so that The GMSC forwards the call request response to the front office, thereby causing the calling party to enter the call state.
  • the present invention effectively solves the problem that a call failure may be caused when a GMSC and a VMSC are not the same MSC, and is simple and easy to implement.

Description

一种旁路被叫智能的方法及系统
技术领域 本方法涉及移动网络领域，尤其涉及 CDMA移动网络中在被叫用户所在 业务控制点 （Service Control Point, SCP)故障且被叫位置请求所在移动交换 中心 (Mobile Switching Center, MSC)和被叫当前位置所在 MSC不是同一 MSC 的情况下被叫智能旁路的方法及系统。
背景技术
由于智能网元 SCP发生故障， 或 MSC和 SCP之间的通信中断时， 会导 致该 SCP下的用户无法进行呼叫， 从而给运营商造成损失。 为了克服这一问 题， 本领域提出一种计算被叫旁路 SCP的方法， 即 BYPASS SCP, 该方法是 在和 SCP进行交互前判断该 SCP的状态或通信情况， 如果正常， 则本次呼 叫接续正常触发触发器到 SCP, 如果不正常， 则不触发触发器， 将用户作为 非智能用户接续。 通过 MSC 出的话单进行计费补扣， 尽量减少运营商的损 失和提高用户的满意度。
在码分多址（ Code Division Multiple Access, CDMA )移动电信网络中， 被叫用户的智能触发器触发两个 MSC,首先是关口局一一移动交换中心网关 ( Gateway Mobile Switching Center, GMSC ) , GMSC为发起被叫位置请求 的 MSC (兼具业务交换点（ Service Switch Point, SSP )功能）， 然后是端局- ——拜访移动交换中心 （Visited Mobile Switching Centre, VMSC ) , VMSC 为被叫当前位置所在的 MSC。 这样就可能存在所述 GMSC因为与被叫 SCP 通信故障而旁路被叫智能， 而所述 VMSC与 SCP通信正常而不旁路被叫智 能，这样呼叫还是失败。反之，如果所述 GMSC没有旁路 SCP,而所述 VMSC 旁路了 SCP, 那么呼叫也还是会失败。 下面以一个 MSC的主备容灾为例来详细说明由于 GMSC与 VMSC不是 同一 MSC, GMSC与 VMSC上是否旁路被叫智能的情况不同而导致呼叫失 败的具体情景， 当然， 该类问题并不限于是由主备容灾导致的， 在各种方式 的 MSC容灾中均存在。 图 1为 CDMA移动网络的智能网络结构示意图。 正常情况下， MSC发 现用户是智能用户时， 接续用户的呼叫时要与 SCP交互。 被叫智能触发器列 表是通过登记、 资格指示或者资格请求从归属位置寄存器 （Home Location Register, HLR )中获取的； 被叫智能触发器列表还有一种方式获取， 即， 关 口局通过位置请求来获取。 图 2描述了端局 VMSC是如何得到被叫智能触发器列表的流程：
S201 : 移动终端 （Mobile Station, MS ) 向基站控制器 （Base Station Controller, BSC )发起位置更新请求；
S202: BSC 收到位置更新请求后， 将其发送给被叫当前所在的 MSC, 即 VMSC;
S203: VMSC收到 BSC的位置更新请求后， 向 BSC返回位置更新响应；
S204: BSC收到位置更新响应后， 将其发送给 MS;
S205: 如果 VMSC发现需要给 HLR发送登记（终端位置变化大或开机 登记） ， VMSC给 HLR发登记请求；
S206: HLR收到登记请求， 更新用户信息， 给 VMSC返回登记响应， 携带被叫智能触发器列表。
下面参考图 3 ,该图描述现有的关口局 GMSC和端局 VMSC不是同一个 MSC, 关口局 GMSC判断不需要旁路被叫智能， 而端局 VMSC判断需要旁 路被叫智能情况：
S301 : 前方局向关口局 GMSC发送呼叫请求；
S302: GMSC接收到该呼叫请求后， 向 HLR发送位置请求；
S303: HLR接收到该位置请求后， 查询位置请求中包含的用户信息， 发 现用户是智能用户， 给关口局 GMSC返回位置响应， 携带被叫智能触发器列 表； S304: 关口局 GMSC收到位置响应后， 发现有被叫智能触发器列表， 根 据被叫智能触发器列表（比如对应 SCP是否故障）判断不需要旁路被叫智能， 给 SCP发初始终端触发器；
S305: 关口局 GMSC收到 SCP返回的初始终端触发器响应； S306: 关口局 GMSC给 HLR发送位置请求， 其中， 触发器为位置触发 哭.
口 ？
S307: HLR给端局 VMSC发送路由请求； S308: 端局 VMSC给 HLR返回路由请求响应；
S309: HLR给关口局 GMSC返回位置请求响应， 该位置请求响应中携 带被叫路由信息；
S310: 关口局 GMSC向 SCP发送被叫路由地址可用触发器；
S311 : SCP向关口局 GMSC发送触发路由地址可用触发器响应；
S312: 关口局 GMSC收到 SCP的触发路由地址可用触发器响应后， 分 析号码获取到对应服务 MSC路由， 给端局 VMSC发呼叫请求； S313: 端局 VMSC收到呼叫请求， 发现被叫是本局用户且是智能用户， 继续判断是否需要在 VMSC上旁路被叫智能，发现需要旁路， 则端局 VMSC 接续被叫， 被叫振铃后， 端局 VMSC向关口局 GMSC发振铃；
S314: 关口局 GMSC前转振铃给前方局；
S315: 被叫应答， 端局 VMSC给关口局 GMSC发应答； 该步骤中端局 VMSC发送给关口局 GMSC的应答是对应步骤 S312中的 关口局 GMSC发送给端局 VMSC的呼叫请求的应答；
S316: 关口局 GMSC前转将应答前转给前方局， 主被叫进入通话；
S317: SCP由于长时间没有收到应答触发器，给 GMSC发消息指示释放 呼叫；
步骤 S317也正是关口局 GMSC和端局 VMSC不是同一个 MSC, 关口 局 GMSC不旁路被叫智能， 而端局 VMSC旁路被叫智能的情况下导致呼叫 失败的原因， 即由于关口局 GMSC上触发了 SCP被叫智能， 而 VMSC需要 旁路被叫智能因此无法向 SCP返回应答触发器， 从而导致 SCP由于长时间 没有收到应答触发器认为出错而释放呼叫。 S318: 关口局 GMSC给前方局发释放呼叫消息；
S319: 关口局 GMSC给端局 VMSC发释放消息。
接着参见图 4,该图描述现有的关口局 GMSC和端局 VMSC不是同一个 MSC, 关口局 GMSC判断需要旁路被叫智能， 而端局 VMSC判断不需要旁 路被叫智能的情况：
S401 : 前方局向关口局 GMSC发送呼叫请求；
S402: GMSC接收到该呼叫请求后， 向 HLR发送位置请求；
S403: HLR接收到该位置请求后， 查询位置请求中的用户信息， 发现用 户是智能用户， 给关口局 GMSC返回位置响应， 携带被叫智能触发器列表； S404: 关口局 GMSC收到位置响应， 发现有被叫智能触发器列表， 根据 被叫智能触发器列表 (比如对应 SCP是否故障 )判断需要旁路智能； 给 HLR 发送位置请求， 其中， 触发器为位置触发器；
S405: HLR给端局 VMSC发送路由请求；
S406: 端局 VMSC给 HLR返回路由请求响应； S407: HLR给关口局 GMSC返回位置请求响应， 该位置请求响应中携 带被叫路由信息；
S408: 关口局 GMSC给端局 VMSC发送呼叫请求；
S409:端局 VMSC收到呼叫请求后，发现被叫是本局用户且是智能用户， 继续判断是否需要在 VMSC 上旁路被叫智能， 发现不需要旁路， 则端局 VMSC接续被叫， 被叫振铃后， 端局 VMSC给关口局 GMSC发振铃；
S410: 关口局 GMSC前转振铃给前方局； S411 : 被叫应答， 端局 VMSC给 SCP发应答；
S412: 端局 VMSC给关口局 GMSC发应答；
S413: 关口局 GMSC前转应答给前方局， 主被叫进入通话；
S414: SCP由于之前没有收到过触发器而直接收到应答， 可能认为是个 错误， 而给端局 VMSC发释放指示； 步骤 S414正是关口局 GMSC和端局 VMSC不是同一个 MSC, 关口局 GMSC旁路被叫智能，而端局 VMSC不旁路被叫智能的情况下导致呼叫失败 的原因， 即， 由于关口局 GMSC旁路被叫智能不会去触发被叫智能， 而端局 VMSC触发被叫智能， 向 SCP返回了应答触发器， 从而导致 SCP在没有收 到过触发器的情况下直接收到应答， 认为出错而释放呼叫。
S415: 端局 VMSC给关口局 GMSC发释放呼叫消息；
S416: 关口局 GMSC给前方局发释放消息。 上述图 3 和图 4 中的不足并不限于是主备容灾导致的， 在各种方式的 MSC容灾中均存在， 目前对于 GMSC与 VMSC不是同一 MSC, GMSC与 VMSC上是否旁路被叫智能的情况不同而导致呼叫失败的问题， 并无相应的 解决方案。
发明内容 本发明要解决的技术问题是， 提供一种旁路被叫智能的方法及系统， 以 解决 GMSC与 VMSC不是同一 MSC时可能导致呼叫失败的问题。 为解决上述技术问题， 本发明提出一种旁路被叫智能的方法， 应用于关 口局 （GMSC ) 与端局 （VMSC ) 不是同一移动交换中心 （MSC ) 的情况， 在一次呼叫过程中， 所述方法包括：
GMSC将该 GMSC是否旁路被叫智能的信息发送给 VMSC; VMSC根据 GMSC是否旁路被叫智能的信息判断 GMSC是否旁路被叫 智能， 并判断 VMSC是否旁路被叫智能； 以及 当 VMSC判断出 GMSC旁路被叫智能，且且 VMSC判断出 VMSC不旁 路被叫智能时， VMSC不触发被叫智能； 当 VMSC判断出 GMSC不旁路被 叫智能， 且 VMSC判断出 VMSC旁路被叫智能时， VMSC向 GMSC发送呼 叫释放， 从而实现完整旁路被叫智能。 上述方法还包括： 当 VMSC判断出 GMSC旁路被叫智能，且 VMSC判断出 VMSC旁路被 叫智能时， VMSC旁路被叫智能； 当 VMSC判断出 GMSC不旁路被叫智能，且 VMSC判断出 VMSC不旁 路被叫智能时， VMSC不旁路被叫智能。
GMSC将是否旁路被叫智能的信息发送给 VMSC的步骤中， GMSC是将 其是否旁路被叫智能的信息承载于位置请求中经归属位置寄存器（HLR )发 送给 VMSC的。
GMSC将是否旁路被叫智能的信息通知给 VMSC 的步骤包括： GMSC 从 HLR获取到被叫智能触发器列表； GMSC根据所述被叫智能触发器列表 分析出 GMSC是否旁路被叫智能， 并根据 GMSC是否旁路被叫智能设置智 能旁路标识， 并将所述智能旁路标识承载于位置请求中经 HLR 发送给 VMSC;
VMSC根据 GMSC是否旁路被叫智能的信息判断 GMSC是否旁路被叫 智能的步骤中 , VMSC是根据接收到的所述智能旁路标识判断 GMSC是否旁 路被叫智能。 当 VMSC判断出 GMSC旁路被叫智能，且 VMSC判断出 VMSC不旁路 被叫智能时，所述方法还包括： VMSC不向 SCP发应答指示， VMSC向 GMSC 发送呼叫请求应答， 由 GMSC将所述呼叫请求应答前转至前方局， 主被叫进 入通话。
为解决上述技术问题， 本发明还提出一种旁路被叫智能的系统， 应用于 关口局 （GMSC )与端局（VMSC )不是同一移动交换中心（MSC )的情况， 包括 GMSC和 VMSC, 其中：
GMSC设置为： 将所述 GMSC是否旁路被叫智能的信发送给 VMSC;
VMSC设置为： 根据 GMSC是否旁路被叫智能的信息判断 GMSC是否 旁路被叫智能， 并判断 VMSC是否旁路被叫智能， 当 VMSC判断出 GMSC 旁路被叫智能，且判断出 VMSC不旁路被叫智能时， VMSC不触发被叫智能； 当 VMSC判断出 GMSC不旁路被叫智能，且 VMSC判断出 VMSC旁路被叫 智能时， VMSC向 GMSC发送呼叫释放， 从而支持完整旁路被叫智能。 VMSC还设置为： 当 VMSC判断出 GMSC旁路被叫智能， 且判断出 VMSC旁路被叫智能 时， VMSC旁路被叫智能； 当 VMSC判断出 GMSC不旁路被叫智能， 且判断出 VMSC不旁路被叫 智能时， VMSC不旁路被叫智能。 所述系统还包括归属位置寄存器（HLR ) ： 所述 GMSC是设置为将所述 GMSC是否旁路被叫智能的信息承载于位 置请求中经 HLR发送给 VMSC„
GMSC是设置为通过如下方式将所述 GMSC是否旁路被叫智能的信息 承载于位置请求中经 HLR发送给 VMSC:所述 GMSC从 HLR获取到被叫智 能触发器列表； GMSC根据所述被叫智能触发器列表分析出 GMSC是否旁路 被叫智能，根据 GMSC是否旁路被叫智能设置智能旁路标识， 并将所述智能 旁路标识承载于位置请求中经 HLR发送给 VMSC; 以及
VMSC设置为根据接收到的所述智能旁路标识判断 GMSC是否旁路被 叫智能。 VMSC还设置为： 当判断出 GMSC 旁路被叫智能， 且 VMSC 判断出
VMSC不旁路被叫智能时， 不向 SCP发应答指示， 向 GMSC发送呼叫请求 应答； 以及 所述 GMSC还设置为： 将所述呼叫请求应答前转至前方局， 从而使主被 叫进入通话状态。
为解决上述技术问题， 本发明还提出一种端局拜访移动交换中心 ( VMSC ) ,所述 VMSC与关口局（ GMSC )不是同一移动交换中心（ MSC ) , 所述 VMSC包括：
信息接收模块， 其设置为： 接收所述 GMSC是否旁路被叫智能的信息； 以及 旁路被叫智能指示模块， 其设置为： 根据 GMSC是否旁路被叫智能的信 息判断 GMSC是否旁路被叫智能， 并判断所述 VMSC是否旁路被叫智能， 当判断出 GMSC旁路被叫智能， 且判断出 VMSC不旁路被叫智能时， 不触 发被叫智能； 当判断出 GMSC不旁路被叫智能， 且判断出 VMSC旁路被叫 智能时， 向 GMSC发送呼叫释放，
从而支持完整旁路被叫智能。
所述旁路被叫智能指示模块还设置为：
当 VMSC判断出 GMSC旁路被叫智能， 且判断出 VMSC旁路被叫智能 时， VMSC旁路被叫智能；
当 VMSC判断出 GMSC不旁路被叫智能， 且判断出 VMSC不旁路被叫 智能时， VMSC不旁路被叫智能。
所述旁路被叫智能指示模块还设置为： 当判断出 GMSC旁路被叫智能， 且 VMSC判断出 VMSC不旁路被叫智能时，不向 SCP发应答指示，向 GMSC 发送呼叫请求应答， 以使所述 GMSC将所述呼叫请求应答前转至前方局， 从 而使主被叫进入通话状态。
本发明提供的一种完整旁路被叫智能的方法及系统， 有效地解决了
GMSC与 VMSC不是同一 MSC时可能导致呼叫失败的问题， 简单、 易于实 现。 附图概述 图 1是 CDMA移动网络智能网络结构示意图； 图 2是现有技术中获取用户被叫智能触发器列表的流程示意图； 图 3是现有被叫用户位置请求和当前位置不在同一 MSC时的关口局智 能没有旁路但是端局智能旁路的呼叫流程图； 图 4是现有被叫用户位置请求和当前位置不在同一 MSC时的关口局智 能旁路但是端局没有旁路的呼叫流程图； 图 5是本发明在位置请求和当前位置不在同一 MSC时的关口局智能不 旁路但是端局发现需要旁路情况下的呼叫流程图； 图 6是本发明在位置请求和当前位置不在同一 MSC时的关口局智能旁 路情况下的呼叫流程图。
本发明的较佳实施方式 下面将结合附图来详细说明本发明实施方案。 在本发明实施例中以背景技术中提到的现有的 MSC 的主备容灾实例中 存在不足为例， 来详细说明本发明解决方案。 本发明针对关口局 GMSC和服务端局 VMSC不是同一个 MSC, 关口局 GMSC判断不需要旁路被叫智能的情况， 为了避免出现图 3所示的情况， 即 端局旁路被叫智能而导致呼叫失败的情况， 本发明提出如下解决方案， 参见 图 5, 包括步骤：
S501 : 前方局向关口局 GMSC发送呼叫请求；
S502: GMSC接收到该呼叫请求后， 向 HLR发送位置请求；
S503: HLR接收到该位置请求后， 查询位置请求中的用户信息， 发现用 户是智能用户， 给关口局 GMSC返回位置响应， 携带被叫智能触发器列表； S504: 关口局 GMSC收到位置响应， 发现有被叫智能触发器列表， 如果 根据被叫智能触发器列表（比如对应 SCP是否故障）判断出不需要旁路智能， 给 SCP发初始终端触发器；
S505: 关口局 GMSC收到 SCP发送的初始终端触发器响应；
S506: 关口局 GMSC向 HLR发送携带智能旁路标识的位置请求， 该智 能旁路标识指示在 GMSC上不旁路被叫智能； 其中， 触发器为初始终端触发 哭口 '？
S507: HLR给端局 VMSC发路由请求， 携带该智能旁路标识；
S508: 端局 VMSC在接收到 HLR发送来的路由请求后， 根据该路由请 求中的智能旁路标识判断出在 GMSC上不旁路被叫智能， 在该 VMSC侧记 录当前在 GMSC上不旁路被叫智能的信息， 然后向 HLR回路由请求响应； S509: HLR给关口局 GMSC回位置请求响应， 该位置请求响应中携带 被叫路由信息；
S510: 关口局 GMSC触发路由地址可用触发器到 SCP;
S511 : 关口局 GMSC收到 SCP的触发路由地址可用触发器响应， 分析 号码获取到对应服务 MSC路由， 即 VMSC的路由， 然后给端局 VMSC发呼 叫请求；
S512: 端局 VMSC收到呼叫请求， 发现被叫是本局用户且是智能用户， 继续判断在 VMSC 上是否需要旁路被叫智能， 发现需要旁路， 判断该端局 VMSC侧记录的当前在 GMSC上是否旁路被叫智能的信息， 发现在 GMSC 上不旁路被叫智能； S513: 端局 VMSC给关口局 GMSC发呼叫释放； 即， 本发明针对 GMSC和服务端局 VMSC不是同一个 MSC时， GMSC 将 GMSC是否旁路被叫智能的情况通知 VMSC, VMSC在进行呼叫接续时， 如果 GMSC不旁路被叫智能， 而 VMSC上需要旁路被叫智能， 则 VMSC向 GMSC发呼叫释放。 当然， 如果 VMSC在进行呼叫接续时， 如果判断 GMSC 不旁路被叫智能， 而 VMSC上也不需要旁路被叫智能， 则 VMSC上不旁路 被叫智能， 可以实现正常呼叫， 不会出现 GMSC与 VMSC上是否旁路被叫 智能的情况不一致导致呼叫失败的情况， 因此， 这里不再详述。 S514: 关口局 GMSC前转释放给前方局， 呼叫被叫释放。
针对关口局 GMSC和服务端局 VMSC不是同一个 MSC, 关口局 GMSC 需要旁路被叫智能的情况， 为了避免出现图 4所示的情况， 即端局没有旁路 被叫智能的情况导致呼叫失败， 本发明提出如下解决方案， 参见图 6, 包括 步骤：
S601 : 前方局向关口局 GMSC发送呼叫请求；
S602: GMSC接收到该呼叫请求后， 向 HLR发位置请求；
S603: HLR接收到该位置请求后， 查询位置请求中的用户信息， 发现用 户是智能用户， 给关口局 GMSC回位置响应， 携带被叫智能触发器列表；
S604: 关口局 GMSC收到位置响应， 发现有被叫智能触发器列表， 根据 被叫智能触发器列表 (比如对应 SCP是否故障 )判断需要旁路被叫智能； 给 HLR发送携带智能旁路标识的位置请求，该智能旁路标识在此指示在 GMSC 上旁路被叫智能； 触发器为位置触发器； S605: HLR给端局 VMSC发路由请求， 携带该智能旁路标识；
S606: 端局 VMSC在接收到 HLR发送来的路由请求后， 根据该路由请 求中的智能旁路标识判断出在 GMSC上旁路被叫智能， 在 VMSC侧记录当 前在 GMSC上旁路被叫智能的信息， 然后向 HLR回路由请求响应；
S607: HLR给关口局 GMSC回位置请求响应， 该位置请求响应中携带 被叫路由信息；
S608: 关口局 GMSC根据被叫路由信息向端局 VMSC发呼叫请求， 端 局 VMSC收到呼叫请求， 接续被叫；
S609: 被叫振铃， 端局 VMSC给关口局 GMSC发振铃；
S610: 关口局 GMSC前转振铃给前方局； S611 : 被叫应答， 端局 VMSC发现被叫是本局用户且是智能用户， 继续 判断在 VMSC上是否需要旁路被叫智能， 发现不需要旁路， 判断该 VMSC 侧保存的当前在 GMSC上是否旁路被叫智能的信息， 发现在 GMSC上旁路 被叫智能， 则不给 SCP发应答指示， 端局 VMSC给关口局 GMSC发应答； 即， 本发明针对 GMSC和服务端局 VMSC不是同一个 MSC的情况， 是 将 GMSC是否旁路被叫智能的情况通知 VMSC, VMSC在进行呼叫接续时， 如果 GMSC旁路被叫智能， 而 VMSC上不需要旁路被叫智能， 则 VMSC不 触发被叫智能， 即不给 SCP发应答指示。 当然， 如果 VMSC在进行呼叫接 续时， 如果判断出 GMSC旁路被叫智能， 而 VMSC上也需要旁路被叫智能， 则 VMSC旁路被叫智能， 可以实现正常呼叫， 不会出现 GMSC与 VMSC上 是否旁路被叫智能的情况不一致导致呼叫失败的情况， 因此，这里不再详述。 S612: 关口局 GMSC前转应答给前方局， 主被叫进入通话；
S613: 通话结束， 被叫释放呼叫， 端局 VMSC给关口局 GMSC发释放；
S614: 关口局 GMSC给前方局发释放消息， 呼叫释放。
为了实现上述方法， 本发明还提出了一种系统，应用于关口局 GMSC与 端局 VMSC不是同一 MSC的情况， 包括 GMSC、 VMSC, HLR以及 SCP, 其中：
GMSC设置为： 将其是否旁路被叫智能的信息通知给 VMSC。 具体来说， GMSC是设置为将其是否旁路被叫智能的信息承载于位置请 求中经 HLR发送给 VMSC。 可以是， GMSC 在从 HLR 获取到被叫智能触发器列表并以此分析出
GMSC是否旁路被叫智能后，根据 GMSC是否旁路被叫智能设置一智能旁路 标识， 并将该智能旁路标识承载于位置请求中经 HLR发送给 VMSC, 由 VMSC通过对其接收到的该智能旁路标识进行判断从而获知 GMSC是否旁 路被叫智能的信息。 VMSC设置为： 根据 GMSC是否旁路被叫智能的信息进行呼叫处理：
VMSC在判断出 GMSC旁路被叫智能， VMSC不需要旁路被叫智能时， VMSC 不触发被叫智能； 当 VMSC判断出 GMSC不旁路被叫智能， VMSC需要旁 路被叫智能时， VMSC向 GMSC发呼叫释放； VMSC在判断出 GMSC旁路 被叫智能， VMSC需要旁路被叫智能时， VMSC旁路被叫智能； VMSC在判 断出 GMSC不旁路被叫智能， VMSC不需要旁路被叫智能时， VMSC不旁路 被叫智能。 VMSC还设置为：在判断出 GMSC旁路被叫智能， VMSC不需要旁路被 叫智能时， 不向 SCP发应答指示， 向 GMSC发送呼叫请求应答， 由 GMSC 前转该应答至前方局， 以实现主被叫通话。
相应的， 本发明还提供了一种端局拜访移动交换中心 （VMSC ) , 所述 VMSC与关口局（GMSC )不是同一移动交换中心（MSC ) , 所述 VMSC包 括：
信息接收模块， 其设置为： 接收 GMSC是否旁路被叫智能的信息； 以及 旁路被叫智能指示模块， 其设置为： 根据 GMSC是否旁路被叫智能的信 息判断 GMSC是否旁路被叫智能， 并判断 VMSC是否旁路被叫智能， 当判 断出 GMSC旁路被叫智能， 且判断出 VMSC不旁路被叫智能时， 不触发被 叫智能； 当判断出 GMSC不旁路被叫智能， 且判断出 VMSC旁路被叫智能 时， 向 GMSC发送呼叫释放。
旁路被叫智能指示模块还设置为：
当 VMSC判断出 GMSC旁路被叫智能， 且判断出 VMSC旁路被叫智能 时， VMSC旁路被叫智能；
当 VMSC判断出 GMSC不旁路被叫智能， 且判断出 VMSC不旁路被叫 智能时， VMSC不旁路被叫智能。
旁路被叫智能指示模块还设置为： 当判断出 GMSC 旁路被叫智能， 且 VMSC判断出 VMSC不旁路被叫智能时， 不向 SCP发应答指示， 向 GMSC 发送呼叫请求应答， 以使 GMSC将呼叫请求应答前转至前方局，从而使主被 叫进入通话状态。
本发明还可有其他多种实施例，在不背离本发明精神及其实质的情况下 , 变形， 但这些相应的 改变和变形都应属于本发明所附的权利要求的保护范围
工业实用性 本发明有效地解决了 GMSC与 VMSC不是同一 MSC时可能导致呼叫失 败的问题， 简单且易于实现。

Claims

权 利 要 求 书
1、 一种旁路被叫智能的方法， 应用于关口局（GMSC )与端局（VMSC ) 不是同一移动交换中心 （MSC ) 的情况， 其特征在于， 在一次呼叫过程中， 所述方法包括： GMSC将该 GMSC是否旁路被叫智能的信息发送给 VMSC;
VMSC根据 GMSC是否旁路被叫智能的信息判断 GMSC是否旁路被叫 智能， 并判断 VMSC是否旁路被叫智能； 以及 当 VMSC判断出 GMSC旁路被叫智能，且 VMSC判断出 VMSC不旁路 被叫智能时， VMSC不触发被叫智能； 当 VMSC判断出 GMSC不旁路被叫智能，且 VMSC判断出 VMSC旁路 被叫智能时， VMSC向 GMSC发送呼叫释放， 从而实现完整旁路被叫智能。
2、 如权利要求 1所述的方法， 其中， 所述方法还包括： 当 VMSC判断出 GMSC旁路被叫智能，且 VMSC判断出 VMSC旁路被 叫智能时， VMSC旁路被叫智能； 当 VMSC判断出 GMSC不旁路被叫智能，且 VMSC判断出 VMSC不旁 路被叫智能时， VMSC不旁路被叫智能。
3、 如权利要求 1或 2所述的方法， 其中：
GMSC将是否旁路被叫智能的信息发送给 VMSC的步骤中， GMSC是将 是否旁路被叫智能的信息承载于位置请求中经归属位置寄存器 （HLR )发送 给 VMSC的。
4、 如权利要求 3所述的方法， 其中：
GMSC将是否旁路被叫智能的信息通知给 VMSC 的步骤包括： GMSC 从 HLR获取到被叫智能触发器列表； GMSC根据所述被叫智能触发器列表 分析出 GMSC是否旁路被叫智能， 并根据 GMSC是否旁路被叫智能设置智 能旁路标识， 并将所述智能旁路标识承载于位置请求中经 HLR 发送给 VMSC;
VMSC根据 GMSC是否旁路被叫智能的信息判断 GMSC是否旁路被叫 智能的步骤中 , VMSC是根据接收到的所述智能旁路标识判断 GMSC是否旁 路被叫智能。
5、 如权利要求 1所述的方法， 其中： 当 VMSC判断出 GMSC旁路被叫智能，且 VMSC判断出 VMSC不旁路 被叫智能时， 所述方法还包括： VMSC不向业务控制点（SCP )发应答指示， VMSC向 GMSC发送呼叫请求应答， 由 GMSC将所述呼叫请求应答前转至 前方局， 主被叫进入通话。
6、 一种旁路被叫智能的系统， 应用于关口局（GMSC )与端局（VMSC ) 不是同一移动交换中心 （MSC ) 的情况， 包括 GMSC和 VMSC, 其特征在 于：
所述 GMSC设置为： 将所述 GMSC 是否旁路被叫智能的信息发送给
VMSC;
所述 VMSC设置为： 根据 GMSC是否旁路被叫智能的信息判断 GMSC 是否旁路被叫智能， 并判断 VMSC 是否旁路被叫智能， 当 VMSC 判断出 GMSC旁路被叫智能，且判断出 VMSC不旁路被叫智能时， VMSC不触发被 叫智能； 当 VMSC判断出 GMSC不旁路被叫智能， 且 VMSC判断出 VMSC 旁路被叫智能时， VMSC向 GMSC发送呼叫释放，
从而支持完整旁路被叫智能。
7、 如权利要求 6所述的系统， 其中， VMSC还设置为： 当 VMSC判断出 GMSC旁路被叫智能， 且判断出 VMSC旁路被叫智能 时， VMSC旁路被叫智能；
当 VMSC判断出 GMSC不旁路被叫智能， 且判断出 VMSC不旁路被叫 智能时， VMSC不旁路被叫智能。 8、 如权利要求 Ί 所述的系统， 其中， 所述系统还包括归属位置寄存器 ( HLR ) ： 所述 GMSC是设置为将所述 GMSC是否旁路被叫智能的信息承载于位 置请求中经 HLR发送给 VMSC„ 9、 如权利要求 8所述的系统， 其中：
GMSC是设置为通过如下方式将所述 GMSC是否旁路被叫智能的信息 承载于位置请求中经 HLR发送给 VMSC:所述 GMSC从 HLR获取到被叫智 能触发器列表； GMSC根据所述被叫智能触发器列表分析出 GMSC是否旁路 被叫智能，根据 GMSC是否旁路被叫智能设置智能旁路标识， 并将所述智能 旁路标识承载于位置请求中经 HLR发送给 VMSC; 以及
VMSC是设置为根据接收到的所述智能旁路标识判断 GMSC是否旁路 被叫智能。
10、 如权利要求 6所述的系统， 其中：
VMSC还设置为： 当判断出 GMSC 旁路被叫智能， 且 VMSC 判断出 VMSC不旁路被叫智能时， 不向 SCP发应答指示， 向 GMSC发送呼叫请求 应答； 以及
所述 GMSC还设置为： 将所述呼叫请求应答前转至前方局， 从而使主被 叫进入通话状态。
11、一种端局拜访移动交换中心（ VMSC ),所述 VMSC与关口局（ GMSC ) 不是同一移动交换中心 （MSC ) , 所述 VMSC包括： 信息接收模块， 其设置为： 接收所述 GMSC是否旁路被叫智能的信息； 以及
旁路被叫智能指示模块， 其设置为： 根据 GMSC是否旁路被叫智能的信 息判断 GMSC是否旁路被叫智能， 并判断所述 VMSC是否旁路被叫智能， 当判断出 GMSC旁路被叫智能， 且判断出 VMSC不旁路被叫智能时， 不触 发被叫智能； 当判断出 GMSC不旁路被叫智能， 且判断出 VMSC旁路被叫 智能时， 向 GMSC发送呼叫释放， 从而支持完整旁路被叫智能。
12、 如权利要求 11 所述的 VMSC, 其中， 所述旁路被叫智能指示模块 还设置为： 当 VMSC判断出 GMSC旁路被叫智能， 且判断出 VMSC旁路被叫智能 时， VMSC旁路被叫智能；
当 VMSC判断出 GMSC不旁路被叫智能， 且判断出 VMSC不旁路被叫 智能时， VMSC不旁路被叫智能。
13、 如权利要求 11或 12所述的 VMSC, 其中： 所述旁路被叫智能指示模块还设置为： 当判断出 GMSC旁路被叫智能， 且 VMSC判断出 VMSC不旁路被叫智能时，不向 SCP发应答指示，向 GMSC 发送呼叫请求应答， 以使所述 GMSC将所述呼叫请求应答前转至前方局， 从 而使主被叫进入通话状态。
PCT/CN2010/073048 2009-09-16 2010-05-21 一种旁路被叫智能的方法及系统 WO2011032395A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US13/393,301 US8660553B2 (en) 2009-09-16 2010-05-21 Method and system for bypassing called intelligence
IN1900DEN2012 IN2012DN01900A (zh) 2009-09-16 2010-05-21

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2009101718901A CN101697639B (zh) 2009-09-16 2009-09-16 一种完整旁路被叫智能的方法及系统
CN200910171890.1 2009-09-16

Publications (1)

Publication Number Publication Date
WO2011032395A1 true WO2011032395A1 (zh) 2011-03-24

Family

ID=42142693

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/073048 WO2011032395A1 (zh) 2009-09-16 2010-05-21 一种旁路被叫智能的方法及系统

Country Status (4)

Country Link
US (1) US8660553B2 (zh)
CN (1) CN101697639B (zh)
IN (1) IN2012DN01900A (zh)
WO (1) WO2011032395A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101697639B (zh) 2009-09-16 2012-01-11 中兴通讯股份有限公司 一种完整旁路被叫智能的方法及系统
CN102158472A (zh) * 2011-02-14 2011-08-17 华为技术有限公司 智能业务故障处理方法及stp
CN105813043A (zh) * 2014-12-31 2016-07-27 中国电信股份有限公司 智能业务旁路方法和装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1449616A (zh) * 2000-06-30 2003-10-15 英特尔公司 灵活快速通信的方法及装置
CN1585450A (zh) * 2004-05-27 2005-02-23 中兴通讯股份有限公司 一种智能预付费用户旁路功能的实现方法
KR20070084755A (ko) * 2006-02-21 2007-08-27 에스케이 텔레콤주식회사 지능망을 이용한 발신 중심의 멀티미디어 링백톤 대체음서비스 제공 방법, 시스템 및 장치
CN101047971A (zh) * 2006-04-06 2007-10-03 华为技术有限公司 当智能用户漫游时在归属地触发智能业务的方法
CN101697639A (zh) * 2009-09-16 2010-04-21 中兴通讯股份有限公司 一种完整旁路被叫智能的方法及系统

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI107109B (fi) * 1998-10-21 2001-05-31 Nokia Networks Oy Digitaalinen tietoliikennejärjestelmä
US6795444B1 (en) * 1999-10-26 2004-09-21 Telefonaktiebolaget L M Ericsson (Publ) System and method for providing wireless telephony over a packet-switched network
US6928277B1 (en) * 2000-04-10 2005-08-09 Telefonaktiebolaget L M Ericsson (Publ) Method for handling global challenge authentication registration, mobile switching center and mobile station therefor
US20070030338A1 (en) * 2005-08-04 2007-02-08 Roamware Inc. Video ringback tone
JP4138808B2 (ja) * 2006-01-10 2008-08-27 株式会社エヌ・ティ・ティ・ドコモ 通信システムおよび通信方法
WO2007087898A1 (en) * 2006-02-01 2007-08-09 Telefonaktiebolaget Lm Ericsson (Publ) Routing media streams from packet switched network to circuit switched network
EP1848241A3 (en) * 2006-04-17 2008-05-21 Roamware, Inc. Method and system using In-Band Approach for providing value added services without using prefix
JP4946422B2 (ja) * 2006-12-22 2012-06-06 日本電気株式会社 通信システム、通信装置、サービス処理装置及びそれらに用いる通信方法
CN101287293B (zh) * 2008-05-28 2011-04-20 中兴通讯股份有限公司 预寻呼方式下漫游重试的方法
US20100093307A1 (en) * 2008-10-15 2010-04-15 Yan Hui System and method of location based services from wireless terminals

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1449616A (zh) * 2000-06-30 2003-10-15 英特尔公司 灵活快速通信的方法及装置
CN1585450A (zh) * 2004-05-27 2005-02-23 中兴通讯股份有限公司 一种智能预付费用户旁路功能的实现方法
KR20070084755A (ko) * 2006-02-21 2007-08-27 에스케이 텔레콤주식회사 지능망을 이용한 발신 중심의 멀티미디어 링백톤 대체음서비스 제공 방법, 시스템 및 장치
CN101047971A (zh) * 2006-04-06 2007-10-03 华为技术有限公司 当智能用户漫游时在归属地触发智能业务的方法
CN101697639A (zh) * 2009-09-16 2010-04-21 中兴通讯股份有限公司 一种完整旁路被叫智能的方法及系统

Also Published As

Publication number Publication date
CN101697639B (zh) 2012-01-11
US20120165000A1 (en) 2012-06-28
US8660553B2 (en) 2014-02-25
IN2012DN01900A (zh) 2015-07-24
CN101697639A (zh) 2010-04-21

Similar Documents

Publication Publication Date Title
KR101654532B1 (ko) 프리페이징 동안의 회선 교환 폴백（ｃｓｆｂ）
KR100365443B1 (ko) 통화접속복구방법을구비한전기통신시스템및그시스템운용방법
JP2001508967A (ja) 移動電気通信網内の緊急呼の設定
US20090036122A1 (en) cdma intelligent network system and its method, device for realizing international roaming service
JPH10501377A (ja) 電気通信システム
WO2011032395A1 (zh) 一种旁路被叫智能的方法及系统
TWI511601B (zh) 藉由地理號碼路由呼叫至有非授權行動存取（ｕｍａ）能力的終端機
CN104105079A (zh) 一种呼叫转移方法及装置
EP2008475B1 (en) A method, apparatus or software for managing a call in a telecommunications network
WO2006079276A1 (fr) Equipement permettant la mise en oeuvre d'un service de notification de messages courts entrants inacheves et procede associe
US7924992B2 (en) Method of ensuring call processing for intelligent user
WO2009046659A1 (fr) Procédé, appareil et système d'acheminement d'un appel vers un numéro international
WO2008095418A1 (fr) Procédé, dispositif et système destinés au traitement d'un échec d'appel
WO2007016824A1 (fr) Procédé pour l’enregistrement libre de zone d’itinérance par un utilisateur avec limitation de mobilité
CN102137362B (zh) 预付费用户的智能改号呼叫方法、系统和相关装置
KR100602567B1 (ko) 이동통신망에서 비정상적으로 종료된 단말기의 상태를문자 메시지로 제공하는 시스템 및 방법
WO2011150793A1 (zh) 一种终呼短消息的漫游重试方法和系统
WO2012083788A1 (zh) 清晰呼叫传输ect业务处理方法、装置及系统
WO2011022989A1 (zh) 灵活振铃群组智能业务的触发方法与装置
KR101261081B1 (ko) 유선 전화망에서 호 제어 서비스 제공 방법 및 시스템
KR100286751B1 (ko) 이동 통신망에서의 착신 가입자 위치에 따른 이동 입 호거부 방법
CN101299872B (zh) 会议通话业务的触发方法及系统
CN107567091A (zh) 位置区更新方法和移动台
JP2001025061A (ja) 移動通信システム及びそれにおける通信方法
KR101058942B1 (ko) 프리 픽스를 이용한 호처리 방법 및 장치

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10816599

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 13393301

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 1900/DELNP/2012

Country of ref document: IN

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10816599

Country of ref document: EP

Kind code of ref document: A1