WO2010139225A1 - 一种本地交换的实现方法、移动交换中心和通信系统 - Google Patents

一种本地交换的实现方法、移动交换中心和通信系统 Download PDF

Info

Publication number
WO2010139225A1
WO2010139225A1 PCT/CN2010/072549 CN2010072549W WO2010139225A1 WO 2010139225 A1 WO2010139225 A1 WO 2010139225A1 CN 2010072549 W CN2010072549 W CN 2010072549W WO 2010139225 A1 WO2010139225 A1 WO 2010139225A1
Authority
WO
WIPO (PCT)
Prior art keywords
local exchange
msc
information
switching center
mobile switching
Prior art date
Application number
PCT/CN2010/072549
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 RU2011153729/08A priority Critical patent/RU2487503C1/ru
Publication of WO2010139225A1 publication Critical patent/WO2010139225A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup

Definitions

  • a transmission network is an important component of a wireless communication network. Reducing the occupation of transmission network resources (hereinafter referred to as transmission resources) is beneficial to reducing the cost of network construction and operation.
  • Local exchange is an effective solution for reducing transmission resource occupation. .
  • the local exchange refers to the loopback of the voice link in the BSS for the session in which the calling party and the called party are located in the same base station subsystem (BSS, Base Station Subsystem), that is, the voice data of the user plane does not flow out of the BSS.
  • BSS Base Station Subsystem
  • the local exchange in the base station refers to the fact that the two parties in the same base station are located in the same base station or in the same base station cluster (in the case of cascading base stations), the loopback of the voice link occurs in the corresponding base station.
  • the local exchange in the base station controller means that the two parties in the same base station are located in the same base station controller, but in different base stations (or base station clusters), the voice link loopback occurs in the corresponding base station controller.
  • Abis interface between base station and base station controller
  • Ater interface between base station and base station controller
  • a port BSS and mobile switching center (MSC, Mobile Switch Center)
  • BSS and mobile switching center MSC, Mobile Switch Center
  • the prior art defines a method for implementing local switching in a non-MSC pool (POOL) network, mainly by determining whether the base station controller where the calling party and the called party located in the same MSC belong to the same base station controller, and whether The local exchange condition is started to determine whether to initiate the local exchange. If the primary and the called party belong to the same base station controller and have the condition for starting the local exchange, the MSC sends an indication to the base station controller to initiate the local exchange, and the base station controller performs local establishment. Exchange operation. After receiving the local exchange establishment completion message of the base station controller, the MSC releases the A port circuit resource used by the calling and called user.
  • POOL non-MSC pool
  • the condition for starting local exchange means that no supplementary business occurs.
  • the local exchange In the case of performing operations such as playback or lawful interception, if the local exchange is initiated, supplementary services, playback or lawful interception occur, or the handover occurs so that the base station controller of the calling party and the called party no longer belong to the same In the case of the base station controller, the local exchange needs to be cancelled.
  • the MSC can request the base station controller to cancel the local exchange by sending signaling.
  • the embodiment of the invention provides a local exchange implementation method, a mobile switching center and a communication system, which can implement local exchange under the MSC POOL networking.
  • a method for implementing a local exchange comprising:
  • the first mobile switching center where the first calling party is located acquires the local exchange information of the second calling party sent by the second mobile switching center;
  • the first mobile switching center performs local exchange processing according to the local exchange information of the first calling party and the local exchange information of the second calling party, where the local exchange information of the first calling party or the local exchange information of the second calling party respectively Includes information about the base station controller where the corresponding caller is located.
  • a mobile switching center comprising:
  • An acquiring unit configured to acquire local exchange information of a second calling party sent by the second mobile switching center when the calling parties are respectively in the first mobile switching center and the second mobile switching center;
  • a processing unit configured to perform local exchange processing according to local exchange information of the first calling party and local exchange information of the second calling party, where the first calling party's local exchange information or the second calling party's
  • the local exchange information includes information of the base station controller where the corresponding caller is located, respectively.
  • a communication system comprising: a first mobile switching center and a second mobile switching center; and the first mobile switching center, when the calling parties are respectively in the first mobile switching center and the second mobile switching center, Obtaining local exchange information of the second calling party sent by the second mobile switching center, performing local exchange processing according to local exchange information of the first calling party, and local exchange information of the second calling party, where The local exchange information of the first calling party or the local exchange information of the second calling party respectively includes information of the base station controller where the corresponding calling party is located;
  • the second mobile switching center is configured to send local exchange information of the local party to the first mobile switching center.
  • the embodiment of the present invention adopts the local exchange information of the other party sent by the MSC that receives the call of the opposite party, and then performs local exchange processing according to the local exchange information of the party and the local exchange information of the other party, so that even the calling party is called under the MSC POOL network. They are located on different MSCs.
  • the calling or called party can also know the BSC where the other party is calling, and can initiate the local exchange judgment for local exchange processing.
  • FIG. 1 is a flowchart of a method of a method provided by Embodiment 1 of the present invention
  • Embodiment 2 is a flowchart of a method of a method provided by Embodiment 2 of the present invention.
  • Embodiment 3 is a flow chart of another method of the method provided by Embodiment 2 of the present invention.
  • Embodiment 3 of the present invention is a flowchart of a method of a method provided by Embodiment 3 of the present invention.
  • Embodiment 6 is a flow chart of another method of the method provided by Embodiment 3 of the present invention.
  • FIG. 8 is a schematic structural diagram of a mobile switching center according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a communication system according to an embodiment of the present invention.
  • the technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. example. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.
  • the embodiment of the present invention provides a method for implementing local switching, and also provides a corresponding mobile switching center and communication system. The details are described below separately.
  • the "own side" and “the other party” in the embodiment of the present invention are directed to the call.
  • the calling party is "The party” is called “the other party”.
  • the called party is "the party” and the caller is the "other party.”
  • the mobile switching center of the party is referred to as a first mobile switching center
  • the mobile switching center of the other party is referred to as a second mobile switching center. Therefore, the first and second mobile switching centers may perform mobile switching of the calling party.
  • the center may also be the mobile switching center of the called party.
  • the second mobile switching center is the called party mobile switching center, and when the first mobile switching center is called When the mobile switching center is used, the second mobile switching center is the calling mobile switching center.
  • the plan is as follows:
  • a method for implementing a local exchange includes: when the calling parties are respectively in the first mobile switching center and the second mobile switching center, the first mobile switching center acquires the local exchange information of the second mobile switching center, according to the local exchange of the local The information is exchanged locally with the local exchange information of the second mobile switching center. Since the MSCs of the calling and called parties can exchange information exchanged locally, both parties can fully understand the local exchange information of the other party, so the information can be exchanged according to the complete local exchange information (including the local exchange information of the calling party and the called party). Local exchange processing. As shown in Figure 1, the specific process can be as follows:
  • the first mobile switching center acquires the local exchange information of the other party sent by the second mobile switching center.
  • the mobile device part MAP, Mobile Application Part
  • the local exchange information may include base station controller signaling point information, and may also include local exchange capability information of the other party, and of course, other information required to establish or release the local exchange, such as Call-ID of the call.
  • the A port carries information such as information.
  • the base station controller signaling point information refers to a party call leg (the so-called call leg refers to a party call.
  • the base station controller information may be the base station controller signaling point information of the first mobile switching center or the second mobile switching center in the local caller, and the base station controller signaling point information may be used to determine that the calling party and the called party belong to each other.
  • the BSC is the same BS (:, according to the judgment result, it is determined whether the local exchange needs to be performed.
  • the local exchange capability information refers to whether the call is being monitored, or whether the operation of playing, supplementing, etc. is performed, according to the local exchange capability of the other party. The information can further determine whether the other party can perform local exchange.
  • the Call-ID is used to identify the calling information of the calling party and the called party. After the local switching mobile switching center obtains the other party's Call-ID, the calling party and the other party's Call are obtained.
  • the -ID is provided to the base station controller, so that the base station controller establishes a local exchange according to the Cal 1-ID. Information carrier for use in the present exchange when releasing the local switching a mobile switching center.
  • the calling and called parties perform local exchange information through MAP signaling (that is, bear the local exchange information through the MAP signaling bearer)
  • the address of the MSC that the opposite party calls may be obtained, and then according to the acquired MSC of the other party.
  • MSI International Mobile Subscriber Identity
  • the information is used to associate the call, so that the MSC can perform local exchange processing on the associated call according to the local exchange information of the local party and the local exchange information of the other party during the subsequent execution.
  • the address of the MSC of the local call and the B1SI information of the local call may be sent to the MSC of the opposite party, and then the other party calls.
  • the MSC can send the local exchange information of the other party to the MSC that the party calls according to the address of the MSC that the party is calling.
  • the local exchange information of the other party carries the B1SI information of the local call, so that the MSC of the local party receives the call.
  • the call may be associated according to the nisi information of the local call carried in the received local exchange information, and then the local exchange information of the party and the local exchange information of the other party are further associated.
  • the subsequent call is processed by local exchange.
  • the first mobile switching center performs local exchange processing according to the local exchange information of the local party and the local exchange information of the second mobile switching center of the other party, including processing for establishing a local exchange or processing for releasing the local exchange;
  • the first mobile switching center can continue to judge, that is, according to the local exchange capability information of the party and the local exchange capability information of the other party, it is determined whether both parties have the When the local exchange capability is enabled, when the judgment result is yes, the base station controller is notified to initiate the local exchange, and the mobile gateway is notified to release the local A port resource; if the local exchange information does not include the local exchange capability, in order to ensure the local exchange Properly executed, before the second mobile switching center provides local exchange information to the first mobile switching center, it may first determine whether it has local switching capability, and if so, provide local exchange information to the first mobile switching center, and the first mobile The exchange center is getting the second Local switching center or exchange information before the process
  • the local exchange establishment response message may be sent to the MSC of the other party, so that the MSC that the other party calls may notify the mobile gateway to release the A-port resource of the other party according to the local exchange establishment response message.
  • the calling party and the called party can each judge and start the local exchange, or only one of the parties can judge and start the local exchange, and then notify the other party.
  • the local exchange information of the party and the local exchange capability information of the other party may be used.
  • the mobile gateway applies for the A port resource of the local party. If the A port resource of the party is successfully applied, the local exchange release request is sent to the MSC of the other party, so that the MSC called by the other party requests the mobile gateway to apply for the A port resource of the other party according to the local exchange cancellation request. After receiving the confirmation message indicating that the A-port resource of the other party has been successfully returned by the MSC that has received the call of the other party, the base station controller is notified to cancel the local exchange.
  • the MSC can also notify the base station controller to cancel the local exchange, and then return a confirmation message indicating that the A port resource of the other party has been successfully applied to the MS (:.
  • the local exchange release request may be directly sent to the other party's MSC without applying for the local A port resource, so that the MSC called by the other party cancels the request according to the local exchange.
  • this embodiment adopts the local exchange information of the other party sent by the MSC that receives the call of the other party, and then performs local exchange processing according to the local exchange information of the local party and the local exchange information of the other party, so that even under the MSC POOL network, even
  • the primary and secondary called parties are located on different MSCs, and the MSC where the calling or called party is located can also know the base station controller where the other party's call is located, and can perform local exchange judgment for local exchange processing, and, because the receiving party can receive the other party.
  • the local exchange information of the other party sent by the calling MSC so if the call is monitored on one of the MSCs, or the local exchange is not initiated by the operation of playback, supplementary service, etc., another MSC can also know that it is beneficial for local exchange. Implementation.
  • the local exchange is performed after one party obtains the information of the other party, and in actual implementation, both the calling party and the called party may obtain the information of the other party to perform the judgment, and all the local exchanges are processed, for example, the following Program:
  • the first mobile switching center acquires local exchange information of the second mobile switching center, and the first mobile switching center performs local exchange processing with the local exchange information of the second mobile switching center according to the local exchange information;
  • the second mobile switching center Obtaining local exchange information of the first mobile switching center, and the second mobile switching center performs local exchange processing with the local exchange information of the first mobile switching center according to its local exchange information.
  • the present embodiment will be described in detail by using MAP signaling to exchange local exchange information between MSCs to implement local exchange.
  • the plan is as follows:
  • the primary and secondary MSCs carry local exchange information and transmit them through MAP signaling.
  • One of the MSCs sends the local exchange information of the local party to the opposite MSC using MAP signaling.
  • the other MSC After receiving the local exchange related information, the other MSC saves the received local exchange information of the counterpart MSC, and returns the original to the other party by using MAP signaling.
  • the local exchange information of the party If the local exchange information of one MSC changes during the call, the local exchange information that has changed needs to be sent to the other MSC to ensure that the calling MSC can fully understand the local exchange of the other party in time.
  • the information is such that the calling and called MSCs can perform local exchange processing based on the complete local exchange information, that is, the local exchange information in the two MSCs.
  • the primary and secondary MSCs address each other through the address of the other party's MSC to perform MAP signaling.
  • the method in which the calling and called MSCs respectively obtain the address of the opposite MSC that is, the calling MSC obtains the MSC address of the called MSC, and the called MSC obtains the address of the calling MSC
  • the calling MSC obtains the MSC address of the called MSC
  • the called MSC obtains the address of the calling MSC
  • the primary and secondary MSCs request routing information (SRI, SEND ROUTING).
  • the calling party initiates a call, and the calling MSC sends a routing information request to the HLR to obtain the called routing information, where the routing information request carries the address of the calling MSC and the calling B1SI; the HLR sends a roaming number request to the called MSC to obtain The called roaming number, the roaming number request carries the address of the calling MSC and the calling B1SI information, and the called MSC saves the address of the calling MSC and the calling B1SI information.
  • the called MSC returns a roaming number response to the HLR, it carries the address of the called MSC and the called B1SI information.
  • the HLR returns a routing information response to the calling MSC, the HLR carries the address of the called MSC and the called nisi information, and the calling MSC -A saves the address of the called MSC and the called nisi information.
  • the primary and the called MSC use the top SI to associate the call. That is, after receiving the local exchange information of the other party's MSC, the calling and called MSCs use the top SI of the call in the MSC to associate with the corresponding call. Therefore, the calling and called MSCs also need to obtain the neighboring top SI information separately, which can be implemented by carrying the user's top SI information of the other party's calling leg in the MAP signaling sent to the other party. See the description in 2.
  • the above-mentioned MAP signaling which can be used to transmit local exchange information, can be implemented by modifying existing MAP signaling, for example, extending existing MAP signaling SRI and PRN, etc.
  • the MAP signaling is implemented.
  • the new MAP signaling is taken as an example for description. It is assumed that the newly added MAP signaling is named [MAP LCLS serevice], and the signaling can carry the following information (selected according to different scenarios):
  • Local exchange indication which can be used to carry local exchange capability information.
  • Call-ID corresponding to the call within the local office; Call-ID is used between the MSC and the base station controller to identify a call leg.
  • the A port carries information in the local office; when the base station controller releases the local exchange, it needs to use the A port of the two call legs to carry information.
  • the calling terminal is MS-A
  • the calling MSC is MSC-A
  • the called terminal is MS_B
  • the called MSC is MSC_B.
  • the primary and secondary MSCs that is, MSC-A and MSC-B, pass the SRI, PRN, PRN ack, and SRI ack to transmit the address information of the BiSI and the calling and called MSC of the calling and called users.
  • the specific process can be as follows:
  • A20K MS-A sends a service request (CM Service Req) to MSC-A;
  • MSC-A performs authentication and encryption processing on the MS-A, for example, an Authenticate & Chiper message interaction between the MSC-A and the MS-A;
  • MS-A sends a setup (SETUP) message to the MSC_A, and the MSC-A returns a Call Proceeding message to the MS-A;
  • setup SETUP
  • MSC-A sends a setup request (ADD_REQ) to the mobile gateway, and the mobile gateway returns an establishment response (ADD_REPLY) to the MSC-A;
  • the MSC-A sends an assignment request (ASS_REQ) to the base station controller, and the base station controller sends an assignment command.
  • ASS_REQ assignment request
  • the MSC-A sends a routing information request to the HLR, requesting the routing information of the MS_B, where the routing information request carries the address of the MSC-A and the top S I of the MS-A;
  • the HLR sends a roaming number request to the MSC-B to obtain the called roaming number, where the roaming number request is carried.
  • MSC_B stores the address of the MSC-A and the top SI information of the MS-A.
  • the roaming number response carries the address of the MSC-B and the B1SI information of the MS-B.
  • the HLR returns a routing information response to the MSC-A, the routing information response carries the address of the MSC-B and the top SI information of the MS_B, and the MSC-A saves the address of the MSC-B and the top SI information of the MS-B;
  • MSC-A sends a setup request to the mobile gateway again, and the mobile gateway returns a setup response to the MSC-A;
  • A21 K passes the interaction and addressing in steps A206 to A208, and the MSC-A and the MSC-B according to the respective saved counterparts
  • the top SI information is used for call association.
  • the MSC-A sends an initial address message (IAM) to the MSC-B.
  • IAM initial address message
  • the MSC-B sends a page (Page) to the base station controller, and the base station controller sends a page to the MS-B, MS-B.
  • B may return a paging response to the base station controller, and after receiving the paging response (Page rsp), the base station controller may send a paging response to the MSC-B;
  • the MSC-B performs authentication and encryption processing on the MS-B. For example, the Authenticate & Chiper message is exchanged between the MSC-B and the MS_B. Meanwhile, the MSC-B sends a setup request to the mobile gateway, and the mobile gateway can return a setup response. MSC-B; MSC-B sends a setup message to MS-B, MS_B returns Call Confirmation (Cal l Confrimed) to MSC-B;
  • the MSC-B sends a setup request to the mobile gateway again, and the mobile gateway can return a setup response to the MSC-B;
  • MSC-B sends an assignment request to the base station controller, the base station controller sends an assignment command to the MS-B, the MS-B returns the assignment to the base station controller, and the base station controller returns the assignment response to the MSC-B;
  • MS-B may send a ringing message (ALERT) to MSC_B, MSC-B sends an address completion message (ACM) to MSC-A, MSC-A sends a ringing message to MS-A, and thereafter, MS-B sends a connection.
  • ACM address completion message
  • MS-B sends a connection.
  • CONNECT to MSC_B, MSC-B can return connection confirmation (C0N ECT_ACK) to MS_B, MSC-B sends response message (ANM) to MSC_A, MSC-A sends a connection message to MS-A, MS-A can return connection
  • the confirmation message is sent to the MSC-A; At this point, the call setup of the MS-A and the MS-B is completed.
  • the MSC-B sends a local exchange information request (LCLS info Req) to the MSC_A according to the address of the MSC-A.
  • the MAP signaling used to transmit the local exchange information carries the base station controller signaling point information where the MS-B is located.
  • the local exchange capability information of the MSC-B and may also carry the Cal l-ID of the MS-B;
  • MSC-A determines whether the local exchange start condition is available, if yes, initiate local exchange, that is, step A218;
  • determining whether the two-party calls belong to the same base station controller according to the base station controller signaling point information where the MS-A is located and the base station controller signaling point information where the MS-B is located;
  • the base station controller where the MS-A is located is notified to initiate the local exchange (step A218), and the mobile gateway is notified to release the A-port resource of the MS-A (step A219); If there is no ability to initiate local exchange, it is indicated in the local exchange information confirmation message (LCLS info Cnf) returned to MSC-B. The local exchange is not allowed. After the MSC-B receives the local exchange information confirmation message, if the local exchange information confirmation message indicates that the local exchange is not allowed, the local exchange will not be initiated.
  • the local exchange information confirmation message indicates that the local exchange is not allowed
  • the MSC-A If the MSC-A does not activate the local exchange restriction, but the MS-A and the MS-B do not belong to the same base station controller, the MSC-B directly returns a local exchange information confirmation message, and carries the MS-A base station controller letter. Order information and the corresponding Call-ID.
  • both MS-A and MS-B belong to the same base station controller, specifically belong to the same base station controller, and both MSC-A and MSC-B have the capability of starting local exchange, and thus, MSC -A after receiving the local exchange information request sent by the MSC-B, start the local exchange, that is, step A218 is performed;
  • the MSC-A sends a local exchange command (LOCAL SWITCH COMMAND) to the base station controller to initiate local exchange, and the base station controller returns a local exchange complete message (LOCAL SWITCH COMP) to the MSC_A, and the MSC-A returns a local exchange information acknowledgement message to the MSC.
  • the local exchange information confirmation message carries the base station controller signaling point information of the MS-A and the corresponding Call-ID, and indicates that the local exchange has been started;
  • the MSC-A if the base station controller initiates the local exchange failure, the MSC-A returns the local exchange information acknowledgement message to the MSC-B, and the local exchange information acknowledgement message carries the base station controller signaling point information where the MS-A is located. , and indicates that the local exchange did not start.
  • MSC-A sends a delete request (SUB_REQ) to the mobile gateway to release the A-port resource of the MS-A; the mobile gateway can return a delete response (SUB_REPLY) to the MSC-A;
  • the MSC-B After receiving the local exchange information confirmation message, the MSC-B sends a deletion request to the mobile gateway to release the A-port resource of the MS-B after the MSC-A returns the local exchange information confirmation message.
  • the gateway may return a delete response to the MSC-B; if the local exchange information acknowledgement message indicates that the local exchange has not been initiated, then no action is taken.
  • the local exchange is established. It should be noted that there is no need to maintain a MAP connection between the primary and the called MSCs, that is, between the MSC-A and the MSC-B. In addition, after the local exchange is initiated, the relay resources between the MSC-A and the MSC-B are not released. Because if it is released, the local exchange that has already been established cannot be released later.
  • the local exchange information request may also be initiated by the MSC-A first, and the implementation manner is similar to that previously described by the MSC-B, that is, after the MSC-B receives the local exchange information request sent by the MSC-A, the MSC- B determines whether the two-party call belongs to the same base station controller according to the base station controller signaling point information where the MS-A is located and the base station controller signaling point information where the MS-B is located; if it is the same base station controller, according to the present
  • the local exchange capability information of the party and the local exchange capability information of the other party determine that both parties have the ability to initiate local exchange (for example, the same called codec is the same, the called BSC supports local exchange, the called user is not monitored, etc.), and the MS is notified.
  • the MSC-B may also return a local exchange information acknowledgement message to the MSC-A, where the local exchange information acknowledgement message carries the MS-B base station control.
  • the signaling point information and the corresponding Cal l-ID and indicate that the local exchange has been started; if it is determined that the local office does not have the capability to initiate the local exchange, the local exchange information confirmation message returned to the MSC-A indicates that the local exchange is not allowed.
  • the MSC-A does not initiate the local exchange if the local exchange information confirmation message indicates that the local exchange is not allowed.
  • the MSC-A directly returns a local exchange information acknowledgement message, and the base station controller letter carrying the MS-B Order information and the corresponding Cal l-ID.
  • the primary and the called MSCs may each determine and initiate the local exchange.
  • the MSC-A may return a local exchange information acknowledgement message to the MSC-B.
  • the MSC-A and the MSC-B determine whether their local exchange start conditions are respectively available, and if so, the MSC-A and the MSC -B initiates local exchange respectively, that is, on the one hand, the MSC-A notifies the base station controller where the MS-A is located to initiate local exchange, and notifies the mobile gateway to release the A-port resource of the MS-A; on the other hand, the MSC-B also notifies the MS- The base station controller where B is located initiates the local exchange, and notifies the mobile gateway to release the A port resource of the MS-B.
  • the MSC-A and the MSC-B can update the local exchange capability information of the call through the local exchange information request and the local exchange information confirmation message, that is, when the local exchange capability information of the call changes, the MSC-A Dynamic interaction with MSC-B.
  • the MSC-A needs to notify the MSC-B that the call no longer has the local switching capability; if the subsequent interception is cancelled or the supplementary service ends, the MSC-A needs to notify the MSC-B that the call has the local switching capability.
  • the local exchange will not be initiated even if the primary and called users belong to the same base station controller.
  • the MSC-A When the MSC-A needs to cancel the local exchange, the MSC-A applies for the A-port resource to the mobile gateway according to the local exchange information of the two parties. If the A-port resource is successfully applied, the local exchange information request is sent to the MSC-B. Notifying the MSC-B and requesting to cancel the local exchange; after receiving the local exchange information request, the MSC-B applies for the A port resource to the mobile gateway, and if it can apply for the A port resource, returns a local exchange information confirmation message to the MSC-A. And the local exchange information confirmation message carries the corresponding A port resource. After receiving the local exchange information confirmation message of the MSC-B, the MSC-A instructs the base station controller to cancel the local exchange.
  • the MSC-A After the local exchange is released, the MSC-A passes the MSC-A again. Local exchange information request notification The MSC-B local exchange has been released. It should be noted that if the MSC-A requires the base station controller to cancel the local exchange failure, the MSC-A also requests the MSC-B to exchange the information through the local exchange, so that the MSC-A and the MSC-B release the already-requested A-port resources.
  • the MSC-A requires the base station controller to cancel the local exchange
  • the MSCs of both parties that is, the MSC-A and the MSC-B, respectively, request the base station controller to release the local. exchange.
  • it can be as follows:
  • the MSC-A When the MSC-A needs to cancel the local exchange, the MSC-A applies for the A-port resource to the mobile gateway according to the local exchange information of the two parties. If the A-port resource is successfully applied, the local exchange information request is sent to the MSC-B. Notifying the MSC-B and requesting to cancel the local exchange; after receiving the local exchange information request, the MSC-B applies to the mobile gateway for the A-port resource, and returns a local exchange information confirmation message to the MSC-A, where the local exchange information confirms the message.
  • the base station controller is not required to carry the A-port resource information, and the base station controller is instructed to release the local exchange, and the local exchange confirmation message is returned to inform the MSC-A that the local exchange has been cancelled. After receiving the local exchange confirmation message, the MSC-A instructs the base station controller to release the local exchange. .
  • the MSC-A can also directly request the MSC-B to cancel the local exchange.
  • the MSC-B applies for the A-port resource to the mobile gateway. If the MSC-B applies for the A-port resource successfully, the MSC-B returns a local exchange confirmation message. After the MSC-A receives the local exchange confirmation message, the MSC-A applies for the A port resource to the mobile gateway. If the MSC-A application A port resource is unsuccessful, the local exchange is not cancelled; if the MSC-A applies If the MSC-B requests the A port resource to be unsuccessful, it will return a reject message to the MSC-A. After receiving the reject message, the MSC-A will not release the local exchange. MSC-A will perform different processing for different reasons for starting the local exchange. For example, if supplementary service is to be performed, MSC-A refuses to supplement the service; if it is to perform lawful interception, the call can be released. Or not listening.
  • the local exchange is not established during the call, but after the handover, the base station controllers of the calling and called parties belong to the same base station controller, and both parties have the ability to initiate local exchange. Then, local exchange needs to be established at this time. That is to say, when one user switches to the base station controller where another user is located, and the local exchange establishment condition is already available, a local exchange needs to be established.
  • B201 BSC1 sends a request handover message (Handover Required) to MSC-A
  • MSC-A sends a setup request to the mobile gateway, and the mobile gateway can return a setup response to the MSC-A
  • request handover message Handover Required
  • the MSC-A sends a handover request (Handover Request) to the BSC2, where the handover request carries a local exchange indication (LS ind), for example, instructing the BSC2 to initiate local exchange or release the local exchange, and the like;
  • LS ind local exchange indication
  • the MSC-A can determine whether the MSC-B has the capability of starting local exchange according to information related to interaction between the MSC-A and the MSC-B during the call setup phase and the call process, such as the local exchange capability information of the MSC-B. If yes, when the MSC-A sends a handover request to the BSC2, it may instruct the BSC2 to initiate a local exchange in the handover request, and carry the Cal l-ID of the switched call; if not, the handover request is sent to the BSC2. In the message, it does not indicate that the local exchange is initiated;
  • the BSC2 may return a handover request acknowledgement message (Handover Request ack) to the MSC_A, where the handover request acknowledgement message carries local exchange confirmation information (LS ack);
  • MSC-A sends a handover command (Handover Command) to BSC1;
  • B204 BSC2 sends a Handover Detect message to the MSC_A, and sends a Handover Complete to the MSC-A;
  • MSC-A sends a clear command (CI ear Command) to BSC1, and BSC1 returns a clear complete message (Clear
  • the MSC-A sends a local exchange information request to the MSC-B to initiate a local exchange, where the local exchange information request carries the base station controller signaling point information of the calling party, the corresponding Cal l-ID, and the local exchange has been started.
  • the MSC-B may return a local exchange information confirmation message to the MSC-A. Thereafter, if there is a condition for initiating the local exchange, the MSC-A notifies the base station controller where the MS-A is located to initiate the local exchange, and notifies the mobile gateway to release.
  • the A-port resource of the MS_A; at this time, the MSC-B also notifies the base station controller where the MS-B is located to initiate the local exchange, and notifies the mobile gateway to release the A-port resource of the MS-B.
  • the MSC-B also notifies the base station controller where the MS-B is located to initiate the local exchange, and notifies the mobile gateway to release the A-port resource of the MS-B.
  • the source base station controller is different from the MSC to which the target base station controller belongs.
  • the calling user has an inter-office base station controller handover
  • the source MSC is MSC-A
  • the source BSC is BSC 1
  • the target MSC is MSC-A'
  • the target BSC is BSC2
  • the called MSC is MSC-B
  • the called BSC is BSC2, as shown in Figure 4.
  • the specific process is as follows:
  • the MSC-A After the C20K MSC-A receives the handover request, if the MSC-A determines that the local exchange can be initiated, for example, the MSC-A determines that both parties have the ability to initiate the local exchange according to the local exchange capability information of the local party and the local exchange capability information of the opposite party.
  • the handover request sent to the MSC-A' carries an indication indicating that the local exchange is initiated, so that after the handover is completed, the MSC-A' notifies the mobile gateway to release the A-port resource and the notification according to the indication that the local exchange is initiated.
  • the base station controller initiates a local exchange, and the MSC-A' returns a handover response indicating that the local exchange is successfully started to the MSC-A; wherein, the handover request sent to the MSC-A' may be a MAP Prepare Handover Req;
  • MSC-A' sends a handover request to the BSC2, where the handover request carries a local exchange indication, such as instructing the BSC2 to initiate local exchange or de-local exchange, and the like, and the Cal l-IDBSC2 carrying the handover call can return a handover request confirmation.
  • the message is sent to the MSC-A', where the handover request acknowledgement message carries the local exchange confirmation information;
  • MSC-A' sends a handover request acknowledgement message to the MSC-A, and the handover request acknowledgement message carries local exchange confirmation information; wherein the handover request acknowledgement message may also be a MAP Prepare Handover Resp;
  • the MSCA notifies the mobile gateway to release the corresponding A-port bearer, and the MSC-A and/or MSC-B notifies the base station controller to initiate the local exchange, and the process between the MSC-A and the MSC-B is the same as the user.
  • the flow when the base station controller in the intra-office is switched for example, the MSC-A sends a local exchange information request to the MSC-B, the MSC-B returns a local exchange information confirmation message to the MSC-A, and the MSC-B notifies the mobile gateway to release A.
  • the specific resources refer to the previous embodiment, and details are not described herein again.
  • MSC-A determines whether local exchange can be initiated
  • the MSC-A shall send the local exchange information to the MSC-A', for example, to inform the MSC-A' of the local exchange capability of the call, and the base station control where the MSC-B is located.
  • the signaling point information and the Cal l-ID are such that the target mobile switching center performs local exchange processing according to the local exchange information of the party and the local exchange information of the other party.
  • the MSCA also notifies the MSCA'.
  • the MSC-A' After receiving the handover request, the MSC-A' first sends a local exchange information request to inquire whether the MSC-A can initiate a local exchange.
  • the local exchange information request carries the handover target BSC information. If the MSC-A determines that the local exchange can be initiated, The MSC-A' returns an indication that the local exchange is allowed to be started, and the MSC-A' continues the subsequent handover and initiates the local exchange operation. For details, refer to the previous embodiment.
  • the MSC-A' needs to know that the MSC-A has started. Local exchange. The MSC-A needs to pass the MSC-A's local exchange information to the MSC-B.
  • the MSC-A' determines whether the local exchange can be initiated. That is, after receiving the handover request, the MSC-A' determines whether the local exchange can be initiated. If it can be started, the local exchange is started in the handover process, and the handover is completed. After that, MSC-A' informs MSC-A that local exchange has been initiated, and MSC-A needs to deliver MSC-A's local exchange information to MSC-B.
  • the MSC where the call is located shall notify the other MSC of the new base station controller information.
  • the MSC-A receives the handover request, and when the handover request is received, it is determined that the local exchange cancellation request is sent to the MSC-B, for example, the local exchange information request is sent to the MSC-B. After receiving the MSC-B, the MSC-B may The local exchange release request determines whether the local exchange can be cancelled. If the local exchange cannot be released, the message indicating the rejection is returned to the MSC-A. After receiving the message indicating rejection, the MSC-A rejects the handover; if it can be released, it applies to the mobile gateway.
  • a port resource and returns an acknowledgment message indicating that the A port resource is successfully applied to the MSC-A, for example, returning a local exchange information confirmation message to the MSC-A, where the local exchange information confirmation message carries the MSC-B to apply to the mobile gateway.
  • the MSC-A applies for the A-port resource to the mobile gateway, notifies the base station controller to cancel the local exchange, and performs subsequent handover processing, and carries the local handover in the handover command sent to the source BSC.
  • the indication of the exchange, and the information of the A port resource applied by the MSC-B notify the MSC-B local exchange after the handover is completed. Has been lifted.
  • the MSC-A can also send a local exchange information request to the MSC-B after requesting the A-port resource from the MGW, that is, the MSC-A applies for the A-port resource to the mobile gateway, and sends the local exchange if the A-port resource is successfully applied. Information is requested to MSC-B.
  • the MSCs of both parties may instruct the BSC to cancel the local exchange.
  • the MSC-A receives the handover request, and determines that the local exchange release request is sent to the MSC-B according to the received handover request, for example, sending a local exchange information request to the MSC-B, after receiving the MSC-B, according to the The local exchange information request determines whether the local exchange is allowed to be released, and if not, returns a message indicating rejection to the MSC-A. After receiving the message indicating rejection, the MSC-A rejects the handover; if it can be released, applies to the mobile gateway.
  • the MSC-A After the handover is completed, the MSC-A sends a notification that the local exchange has been cancelled to the MSC-B, and the MSC-B deactivates the local exchange according to the notification that the local exchange has been cancelled, and returns an acknowledgement message.
  • the MSC-A can also send a local exchange information request to the MSC-B after requesting the A-port resource from the MGW, that is, the MSC-A applies for the A-port resource to the mobile gateway, and sends the local exchange if the A-port resource is successfully applied. Information is requested to MSC-B.
  • the interaction between the MSC-A and the MSC-B is the same as the intra-office handover. The details are not described here. In this case, the MSC-A' Before making the handover, you must first obtain the license of MSC-A and MSC-B.
  • the embodiment uses the MAP signaling to perform local exchange of information between the MSCs, so that the MSC can perform local exchange processing according to the complete local exchange information (local exchange information between the local party and the other party), so that Under the MSC POOL network, even if the primary and secondary called parties are located on different MSCs, the MSC where the calling party is located can know the base station controller where the other party is located, and can initiate the local exchange judgment for local exchange processing.
  • the local exchange information between the MSCs can be transmitted through the MAP signaling, if the call is monitored on one of the MSCs, or the operation of the playback, supplementary service, etc. cannot be started, the other MSC can also be activated. It can be known that it is advantageous for the implementation of local exchange.
  • the MAP signaling is used to transmit the local exchange information between the MSCs, and there is no need to make too many changes to the MSC, which is advantageous for implementation.
  • the primary and the called MSC exchange information through the relay signaling.
  • One of the MSCs uses the relay signaling to send the local exchange information of the local party to the other MSC, including the base station controller signaling point information and/or local exchange capability information of the local call leg.
  • the other MSC After receiving the local exchange related information, the other MSC saves the received local exchange information of the counterpart MSC, and returns the local exchange information of the local party to the other party by using relay signaling. If the local exchange information of one MSC changes during the call, the local exchange information that has changed needs to be sent to the other MSC to ensure that the calling MSC can fully understand the local exchange of the other party in time.
  • the information is such that the calling and called MSCs can perform local exchange processing based on the complete local exchange information, that is, the local exchange information in the two MSCs.
  • the relay signaling mentioned above which can be used to transmit local exchange information, can use the relay signaling type as: Bearer Independent Call Control Protocol (BICC), or Session Initiation Protocol (BIC). SIP, Session Initiation Protocol), or the integrated service digital network user part
  • BICC Bearer Independent Call Control Protocol
  • BIC Session Initiation Protocol
  • SIP Session Initiation Protocol
  • Session Initiation Protocol Session Initiation Protocol
  • ISUP Integrated Services Digital Network User Part
  • relay signaling etc., by extending existing relay signaling, for example: It is possible to extend the information request (INR, Information Request) and information (INF, Information) of the existing BICC message, and also extend the INR and INF of the existing ISUP message;
  • SIP signaling may use SIP-I signaling.
  • INFO Information, Information
  • 200 OK a response message
  • local exchange information is transmitted between the calling and called MSCs.
  • the extended INR and INF can carry the following information:
  • the base station controller signaling point information where the calling party is located in the local office.
  • LCLS establishment request LCLS establishment permission; LCLS establishment rejection; LCLS release request; LCLS release permission; LCLS release rejection; LCLS prohibition indication; LCLS permission indication; LCLS establishment indication; LCLS release indication;
  • a Call-ID corresponding to the call within this office.
  • a Call-ID is used between the MSC and the base station controller to identify a call leg.
  • the A port in the bureau carries information.
  • the base station controller releases the local exchange, it needs to use the A port of the two call legs to carry information.
  • Local exchange of information For example, the LCLS Request, LCLS information of the new BICC message is added. (It should be noted that the signaling name here is only an example. It should be understood that other signaling names may also be used); or the new ISUP message LCLS Request may be added. , LCLS information, and more.
  • the SIP signaling can use the SIP-I signaling.
  • the INF0 can be used to carry the LCLS Request of the newly added ISUP message.
  • the LC 0 information of the newly added ISUP message can be carried by using 200 0K, thereby realizing the calling and calling The MSC exchanges local exchange information.
  • extended SIP signaling will be taken as an example for description.
  • the calling terminal is MS-A
  • the calling MSC is MSC-A
  • the called terminal is MS_B
  • the called MSC is MSC_B.
  • the primary and secondary MSCs ie, MSC-A and MSC-B, transmit the local interaction information of the two parties through extended SIP signaling.
  • the INF0 can be used to carry the INR of the extended ISUP message, using 200 0K.
  • the INF carrying the extended ISUP message As shown in Figure 5, the specific process can be as follows:
  • A30K MS-A sends a service request (CM Service Req) to MSC-A; A302.
  • the MSC-A performs authentication and encryption processing on the MS-A. For example, the interaction between the MSC-A and the MS-A is performed by the Authent i cat e&Chiper message;
  • the MS-A sends a setup (SETUP) message to the MSC_A, and the MSC-A returns a call progress message (Cal l Proceeding) to the MS-A;
  • SETUP setup
  • Cal l Proceeding call progress message
  • the MSC-A sends a setup request (ADD_REQ) to the mobile gateway, and the mobile gateway returns to establish a response.
  • ADD_REQ setup request
  • the MSC-A sends an assignment request (ASS_REQ) to the base station controller, and the base station controller sends an assignment command (ASS_CMD) to the MS-A, and the MS-A returns the assignment completion (ASS_C0MP) to the base station controller, the base station controller. Return the assignment response (ASS_RSP) to MSC-A;
  • the MSC-A sends a routing information request to the HLR to request routing information of the MS_B.
  • the HLR sends a roaming number request to the MSC-B to obtain the called roaming number.
  • MSC-B returns a roaming number response to the HLR
  • the HLR returns a routing information response to the MSC-A
  • MSC-A sends a setup request to the mobile gateway again, and the mobile gateway returns a setup response to the MSC-A;
  • A31 K MSC-A sends an initial address message (IAM) to the MSC_B, and the MSC-B sends a page (Page) to the base station to control
  • the base station controller sends a paging to the MS-B, and the MS-B can return a paging response to the base station controller.
  • the base station controller can send a paging response to the MSC-B. ;
  • the MSC-B performs authentication and encryption processing on the MS-B. For example, the Authenticate & Chiper message is exchanged between the MSC-B and the MS_B. Meanwhile, the MSC-B sends a setup request to the mobile gateway, and the mobile gateway can return a setup response. MSC-B; MSC-B sends a setup message to MS-B, MS_B returns call confirmation (Cal l Confrimed) to MSC-B;
  • the MSC-B sends a setup request to the mobile gateway again, and the mobile gateway may return a setup response to the MSC-B.
  • MSC-B sends an assignment request to the base station controller, the base station controller sends an assignment command to the MS-B, the MS-B returns the assignment to the base station controller, and the base station controller returns the assignment response to the MSC-B;
  • MS-B may send a ringing message (ALERT) to MSC_B, MSC-B sends an address completion message (ACM) to MSC-A, MSC-A sends a ringing message to MS-A, and thereafter, MS-B sends a connection.
  • MSC_B can return connection confirmation (C0N ECT_ACK) to MS_B
  • MSC-B sends response message (ANM) to MSC_A
  • MSC-A sends a connection message to MS-A
  • MS-A can return connection
  • the confirmation message is sent to the MSC-A; At this point, the call setup of the MS-A and the MS-B is completed.
  • the MSC-B sends an INF0 [INR] message to the MSC_A, where the INF0 [INR] message carries the base station controller signaling point information of the MS_B and the local exchange capability information of the MSC-B, and can also carry the MS-B Call -ID;
  • MSC-A determines whether the local exchange start condition is available, if yes, initiates local exchange, that is, step A318 is performed;
  • determining whether the two-party calls belong to the same base station controller according to the base station controller signaling point information where the MS-A is located and the base station controller signaling point information where the MS-B is located;
  • the base station controller where the MS-A is located is notified to initiate the local exchange (step A318), and the mobile gateway is notified to release the A-port resource of the MS-A (step A319); If there is no ability to initiate local exchange, then the local exchange is not allowed in the 200 0K [INF] message returned to MSC-B. If MSC-B receives the 200 0K[INF] message, if the 200 0K[INF] If the message indicates that local exchange is not allowed, local exchange will not be initiated.
  • the MSC-A does not activate the local exchange restriction, but the MS-A and the MS-B do not belong to the same base station controller, the MSC-B directly returns a 200 0K [INF] message carrying the base station controller signaling of the MS_A. Point information and the corresponding Call-ID.
  • both MS-A and MS-B belong to the same base station controller, specifically belong to the same base station controller, and both MSC-A and MSC-B have the capability of starting local exchange, and thus, MSC -A after receiving the 200 0K [INF] message sent by the MSC-B, start the local exchange, that is, perform step A318;
  • MSC-A sends a local exchange command (LOCAL SWITCH COMMAND) to the base station controller to initiate local exchange, the base station controller returns a local exchange complete message (LOCAL SWITCH C0MP) to MSC_A, and MSC-A returns a 200 OK [INF] message to MSC-B, the 200 0K [INF] message carries the base station controller signaling point information of the MS_A and the corresponding Call-ID, and indicates that the local exchange has been started;
  • the MSC-A if the base station controller initiates the local exchange failure, the MSC-A returns the 200 0K [INF] message to the MSC-B, and carries the base station controller signaling where the MS-A is located in the 200 0K [INF] message. Point the message and indicate that the local exchange did not start.
  • MSC-A sends a delete request (SUB_REQ) to the mobile gateway to release the A-port resource of the MS-A; the mobile gateway may return a delete response (SUB_REPLY) to the MSC-A; After receiving the 200 0K [INF] message, the MSC-B sends a delete request to the mobile gateway to release the A port resource of the MS-B. The mobile gateway may return a delete response to the MSC-B; if the 200 0K[INF] message indicates that the local exchange has not been initiated, then no action is taken.
  • the local exchange is established. It should be noted that there is no need to maintain a MAP connection between the primary and the called MSCs, that is, between the MSC-A and the MSC-B. In addition, after the local exchange is initiated, the relay resources between the MSC-A and the MSC-B are not released. Because if it is released, the local exchange that has already been established cannot be released later.
  • the INF0 [INR] message may also be initiated by the MSC-A first, and the implementation is similar to that previously described by the MSC-B, that is, after the MSC-B receives the INF0 [INR] message sent by the MSC-A,
  • the MSC-B determines whether the two-party call belongs to the same base station controller according to the base station controller signaling point information where the MS_A is located and the base station controller signaling point information where the MS-B is located; if it is the same base station controller, according to the present
  • the local exchange capability information of the party and the local exchange capability information of the other party determine that both parties have the ability to initiate local exchange (for example, the main called codec is the same, the called party
  • the base station controller that informs the MS-B initiates the local exchange, and notifies the mobile gateway to release the A port resource of the MS-B.
  • the MSC-B can also return 200.
  • the 200 0K [INF] message carries the base station controller signaling point information of the MS-B and the corresponding Call-ID, and indicates that the local exchange has been started; if it is determined that the local office does not have the start
  • the MSC-A directly returns a 200 0K [INF] message, and the base station controller carrying the MS-B Signaling point information and corresponding Call_ID.
  • the primary and the called MSCs may each determine and initiate the local exchange.
  • MSC-A may return a 200 OK [INF] message to MSC-B, and then MSC-A and MSC-B determine whether their local exchange start conditions are respectively available, and if so, MSC-A The MSC-B initiates the local exchange with the MSC-B.
  • the MSC-A notifies the base station controller where the MS-A is located to initiate the local exchange, and notifies the mobile gateway to release the A-port resource of the MS-A;
  • the base station controller where the MS-B is located initiates the local exchange, and notifies the mobile gateway to release the A port resource of the MS-B.
  • the MSC0 and the MSC-B can update the local exchange capability information of the call through the INF0 [INR] message and the 200 0K [INF] message, that is, when the local exchange capability information of the call changes, the MSC Dynamic interaction between -A and MSC-B.
  • the MS-A and the MS-B are not in the same base station controller and the local exchange is not initiated, but there is no other local exchange restriction, during the call, if the MS-A user is monitored or occurs For supplementary service, MSC-A needs to notify MSC-B that the call no longer has local switching capability; After the interception or supplementary service ends, the MSC-A needs to notify the MSC-B that the call has the local exchange capability.
  • the local exchange will not be initiated even if the primary and called users belong to the same base station controller.
  • the MSC-A needs to cancel the local exchange when the MSC-A needs to cancel the local exchange
  • the MSC-A applies for the A-port resource to the mobile gateway according to the local exchange information of the two parties, if the A-port resource is successfully applied, the INF0[INR] is sent to the MSC-B.
  • the message informs the MSC-B and requests to cancel the local exchange; after receiving the INF0 [INR] message, the MSC-B applies for the A port resource to the mobile gateway, and if it can apply for the A port resource, returns 200 0K to the MSC-A.
  • the MSC-A instructs the base station controller to cancel the local exchange, after the local exchange is released. MSC-A then informs MSC-B that the local exchange has been released through the INF0 [INR] message. It should be noted that if the MSC-A requests the base station controller to cancel the local exchange failure, the MSC-A also informs the MSC-B through the INF0 [INR] message, so that the MSC-A and the MSC-B release the applied A-port resources. .
  • the MSC-A requires the base station controller to cancel the local exchange
  • the MSCs of both parties that is, the MSC-A and the MSC-B, respectively, request the base station controller to release the local. exchange.
  • it can be as follows:
  • the MSC-A needs to cancel the local exchange when the MSC-A needs to cancel the local exchange, if the MSC-A applies for the A-port resource to the mobile gateway according to the local exchange information of the two parties, if the A-port resource is successfully applied, the INF0[INR] is sent to the MSC-B.
  • the message informs the MSC-B and requests to cancel the local exchange; after receiving the INF0 [INR] message, the MSC-B applies to the mobile gateway for the A port resource, and returns a 200 0K [INF] message to the MSC-A, the 200 0K
  • the [INF] message does not need to carry the A port resource information, and indicates that the base station controller releases the local exchange, and returns a 200 0K [INF] message to inform the MSC-A that the local exchange has been released, and the MSC-A receives the 200 0K [INF] message. After that, the base station controller is instructed to release the local exchange.
  • the MSC-A can also directly request the MSC-B to cancel the local exchange.
  • the MSC-B applies for the A-port resource to the mobile gateway. If the MSC-B applies for the A-port resource successfully, the MSC-B returns a local exchange confirmation message.
  • the MSC-A receives the local exchange confirmation message, the MSC-A applies for the A port resource to the mobile gateway. If the MSC-A application A port resource is unsuccessful, the local exchange is not cancelled; if the MSC-A applies If successful, the base station controller is instructed to cancel the local exchange; if the MSC-B applies for the A port resource is unsuccessful, the MSC-A returns a rejection. After receiving the reject message, MSC-A will not release the local exchange. MSC-A will perform different processing for different reasons for starting the local exchange. For example, if supplementary service is to be performed, MSC-A refuses to supplement the service; if it is to perform lawful interception, the call can be released. Or not listening.
  • (III) Scenario 3 Establish local exchange during handover The local exchange is not established during the call, but after the handover, the base station controllers of the calling and called parties belong to the same base station controller, and both parties have the ability to initiate local exchange. Then, local exchange needs to be established at this time. That is to say, when one user switches to the base station controller where another user is located, and the local exchange establishment condition is already available, a local exchange needs to be established.
  • B30K BSC1 sends a request handover message (Handover Required) to MSC-A, MSC-A sends a setup request to the mobile gateway, and the mobile gateway can return a setup response to the MSC-A;
  • the MSC-A sends a handover request (Handover Request) to the BSC2, where the handover request carries a local exchange indication (LS ind), for example, instructing the BSC2 to initiate local exchange or release the local exchange, and the like;
  • LS ind local exchange indication
  • the MSC-A can determine whether the MSC-B has the capability of starting local exchange according to information related to interaction between the MSC-A and the MSC-B during the call setup phase and the call process, such as the local exchange capability information of the MSC-B. If yes, when the MSC-A sends a handover request to the BSC2, it may instruct the BSC2 to initiate a local exchange in the handover request, and carry the Call-ID of the switched call; if not, the handover request message sent to the BSC2 , does not instruct to initiate local exchange;
  • the BSC2 may return a handover request acknowledgement message (Handover Request ack) to the MSC-A, where the handover request acknowledgement message carries local exchange confirmation information (LS ack);
  • MSC-A sends a handover command (Handover Command) to BSC1;
  • B304 BSC2 sends a Handover Detect message to the MSC_A, and sends a Handover Complete to the MSC-A;
  • MSC-A sends a clear command (CI ear Command) to BSC1, and BSC1 returns a clear complete message (Clear
  • the MSC-A sends an INFO [INR] message to the MSC-B to initiate a local exchange.
  • the INFO [INR] message carries the base station controller signaling point information of the calling party, the corresponding Call-ID, and the local exchange.
  • the indication of the start; the MSC-B may return a 200 0K [INF] message to the MSC-A.
  • the MSC-A notifies the base station controller where the MS-A is located to initiate the local exchange and notifies the mobile
  • the gateway releases the A port resource of MS-A;
  • the MSC-B also informs the base station controller where the MS-B is located to initiate the local exchange, and notifies the mobile gateway to release the A port resource of the MS-B.
  • the source base station controller is different from the MSC to which the target base station controller belongs.
  • the calling user has an inter-office base station controller handover
  • the source MSC is MSC-A
  • the source BSC is BSC 1
  • the target MSC is MSC_A
  • the target BSC is BSC2
  • the called MSC is MSC-B
  • the BSC is BSC2, as shown in Figure 7, the specific process is as follows:
  • the MSC-A determines that the local exchange can be initiated, for example, the MSC-A determines that both parties have the ability to initiate the local exchange according to the local exchange capability information of the local party and the local exchange capability information of the other party.
  • the handover request sent to the MSC-A' carries an indication indicating that the local exchange is initiated, so that after the handover is completed, the MSC-A' notifies the mobile gateway to release the A-port resource of the local party and notify the base station to control according to the indication that the local exchange is initiated.
  • the device initiates the local exchange, and the MSC-A' returns a handover response indicating that the local exchange is successfully started to the MSC-A; wherein, the handover request sent to the MSC-A' may be a MAP Prepare Handover Req;
  • MSC-A' sends a handover request to the BSC2, where the handover request carries a local exchange indication, such as instructing the BSC2 to initiate a local exchange or a local exchange, etc., and the Cal l-IDBSC2 carrying the handover call can return a handover request confirmation.
  • the message is sent to the MSC-A', where the handover request acknowledgement message carries the local exchange confirmation information;
  • MSC-A' sends a handover request acknowledgement message to the MSC-A, and the handover request acknowledgement message carries the local exchange acknowledgement information; wherein the handover request acknowledgement message may also be a MAP Prepare Handover Resp;
  • the MSCA After the handover is completed, the MSCA notifies the mobile gateway to release the corresponding A-port bearer, and the MSC-A and/or MSC-B notifies the base station controller to initiate the local exchange, and the process between the MSC-A and the MSC-B is the same as the user.
  • the A port resource is released, and the specific guest is referred to the foregoing embodiment, and details are not described herein again.
  • MSC-A determines whether local exchange can be initiated
  • the MSC-A shall send the local exchange information to the MSC-A', for example, to inform the MSC-A' of the local exchange capability of the call, and the base station control where the MSC-B is located.
  • the signaling point information and the Cal l-ID are such that the target mobile switching center performs local exchange processing according to the local exchange information of the party and the local exchange information of the other party.
  • the MSCA also notifies the MSCA'.
  • the MSC-A' After receiving the handover request, the MSC-A' first sends an INF0 [INR] message to inquire whether the MSC-A can initiate the local exchange.
  • the INF0 [INR] message carries the handover target BSC information, and if the MSC-A determines that the local exchange can be initiated, Then, the MSC-A' returns an indication that the local exchange is allowed to be started, and the MSC-A' continues the subsequent handover and initiates the local exchange operation. For details, refer to the previous embodiment.
  • the MSC-A' should notify the MSC-A. A local exchange has been initiated. The MSC-A needs to pass the MSC-A's local exchange information to the MSC-B.
  • the MSC-A' determines whether the local exchange can be initiated. That is, after receiving the handover request, the MSC-A' determines whether the local exchange can be initiated. If it can be started, the local exchange is started in the handover process, and the handover is completed. After that, MSC-A' informs MSC-A that local exchange has been initiated, and MSC-A needs to deliver MSC-A's local exchange information to MSC-B.
  • the MSC where the call is located shall notify the other MSC of the new base station controller information.
  • the MSC-A receives the handover request, and if it needs to cancel the local exchange according to the received handover request, sends a local exchange release request to the MSC-B, for example, sends an INF0 [INR] message to the MSC-B, and after receiving the MSC-B, the MSC-B can
  • the local exchange release request determines whether the local exchange can be released, and if not, returns a message indicating rejection to the MSC-A, and after receiving the message indicating rejection, the MSC-A rejects the handover; if it can be released, the mobile gateway is removed.
  • the MSC-A applies for the A-port resource to the mobile gateway, notifies the base station controller to cancel the local exchange, and performs subsequent handover processing, and carries the release command in the handover command sent to the source BSC.
  • the MSC-A may also send an INFO [INR] message to the MSC-B after requesting the A port resource from the MGW, that is, the MSC-A applies for the A port resource to the mobile gateway, and sends the INFO if the A port resource is successfully applied. [INR] message to MSC_B.
  • MSC-A instructs the base station controller to cancel the local exchange
  • MSCs of both parties such as MSC-A and MSC-B, may instruct the BSC to cancel the local exchange. as follows:
  • the MSC-A receives the handover request, and determines that the local exchange release request is sent to the MSC-B according to the received handover request, for example, sending an INF0 [INR] message to the MSC-B, and after receiving the MSC-B, according to the MSC-B, The INF0 [INR] message determines whether the local exchange is allowed to be released, and if it cannot be released, returns a message indicating rejection to the MSC-A.
  • the MSC-A After receiving the message indicating rejection, the MSC-A rejects the handover; if it can be released, moves to the mobile The gateway applies for the A port resource, and returns the local exchange release permission indication to the MSC-A (without the requested A port resource information), and the MSC-A performs the subsequent handover process according to the local exchange release permission indication, including applying to the mobile gateway for the A port. Resources, and notifying the base station controller to release the local exchange.
  • the MSC-A sends a notification to the MSC-B that the local exchange has been released, and the MSC-B deactivates the local exchange based on the notification that the local exchange has been released, and returns a 200 OK [INF] message.
  • the MSC-A may also send an INFO [INR] message to the MSC-B after requesting the A port resource from the MGW, that is, the MSC-A applies for the A port resource to the mobile gateway, and sends the INFO if the A port resource is successfully applied. [INR] message to MSC_B.
  • the interaction between the MSC-A and the MSC-B is the same as the intra-office handover. The details are not described here. In this case, the MSC-A' Before making the handover, you must first obtain the license of MSC-A and MSC-B.
  • the embodiment uses the relay signaling to perform local exchange of information between the MSCs, so that the MSC can perform local exchange processing according to the complete local exchange information (local exchange information between the local party and the other party).
  • the MSC POOL networking even if the primary and the called parties are located on different MSCs, the MSC where the calling party is located can know the base station controller where the other party is located, and can initiate the local exchange judgment for local exchange. Processing, and, since the local exchange information between the MSCs can be transmitted through the relay signaling, if the call is monitored on one of the MSCs, or the operation of the playback, supplementary service, etc.
  • the MSC can also learn that it is beneficial to the implementation of local exchange. Further, the relay signaling is used to transmit the local exchange information between the MSCs. Compared with the local exchange information between the MSCs and the MAP signaling, although the MSC needs to be modified more, the HLR is not needed. Making changes (using MAP signaling to communicate local exchange information between MSCs requires changes to the MSC and HLR).
  • the embodiment of the present invention further provides a mobile switching center, that is, an MSC.
  • the MSC includes an obtaining unit 401 and a processing unit 402.
  • the obtaining unit 401 is configured to acquire local exchange information of the other party sent by the MSC that the other party calls; for example, when the calling parties are respectively in the first mobile switching center and the second mobile switching center, the first mobile switching center acquires the second mobile switching center.
  • the locally exchanged information of the second calling party that is sent may be obtained by using the MAP signaling or the relay signaling to obtain the local exchange information of the other party sent by the MSC that the other party calls, where the local exchange information may include information of the base station controller, such as a base station.
  • the controller signaling point information may also include information such as local switching capability information, and of course, other information required to establish and release local exchange, such as Call-ID and A-port bearer information of the call.
  • the base station controller signaling point information refers to the base station controller where one of the calling legs is located, and the local switching capability information refers to whether the call is being monitored, or whether the operation of playing, supplementary, or the like is being performed.
  • the processing unit 402 is configured to perform local exchange processing according to the local exchange information of the local party and the local exchange information of the other party acquired by the obtaining unit 401, that is, according to local exchange information of the first calling party, and the second calling party
  • the local exchange information is processed by a local exchange, where the local exchange information of the first caller or the local exchange information of the second caller respectively includes information of a base station controller where the corresponding caller is located.
  • the processing unit 402 may include a first determining subunit 4021 and a notification subunit.
  • the first determining sub-unit 4021 is configured to determine, according to the local exchange information of the local party and the local exchange information of the other party acquired by the obtaining unit 401, whether the two-party call belongs to the same base station controller, that is, according to the base station controller information of the first calling party. And the base station controller information of the second calling party acquired by the obtaining unit 401 determines whether the two party calls belong to the same base station controller;
  • the notification sub-unit 4023 is configured to notify the base station controller to initiate local exchange when the first determining sub-unit 4021 determines that the two-party calls belong to the same base station controller, and notify the mobile gateway to release the A-port resource of the local party, that is, the first calling party. A port resource.
  • the processing unit 402 may further include a second determining sub-unit 4022;
  • the second determining sub-unit 4022 is configured to determine, according to the local exchange information of the local party and the local exchange information of the other party (second calling party) acquired by the obtaining unit 401, that is, the local exchange information of the second calling party, whether both parties have the start Local exchange capability;
  • the obtaining unit 401 is further configured to acquire, when the local exchange information of the first calling party or the local exchange information of the second calling party further includes the local switching capability information of the corresponding calling party, respectively Local exchange capability information;
  • the notification sub-unit 4023 is configured to notify the base station controller to start local when the first determining sub-unit 4021 determines that the two-party calls belong to the same base station controller, and the second determining sub-unit 4022 determines that both parties have the capability to initiate local switching. Exchange, and notify the mobile gateway to release the A port resource of the local party, that is, the A port resource of the first calling party.
  • the processing unit 402 may further include a first sending subunit 4024;
  • the first sending subunit 4024 is configured to send a local exchange setup response message to the MSC of the opposite party, such as the second mobile switching center, so that the MSC that the opposite party calls, such as the second mobile switching center, notifies the mobile gateway to release the other party according to the local exchange establishment response message.
  • the A port resource is the A port resource of the second call.
  • the processing unit 402 may further include an application subunit 4025;
  • the application sub-unit 4025 is configured to apply for the local port A resource to the mobile gateway according to the local exchange information of the local party and the local exchange information of the other party acquired by the obtaining unit 401, for example, according to the local exchange information and the acquiring unit of the first calling party. Obtaining the local exchange information of the second calling party to apply for the A port resource of the party to the mobile gateway;
  • the first sending sub-unit 4024 is further configured to send, after the application sub-unit 4025 applies for the A-port resource of the local party, the local exchange release request to the MSC of the opposite party, such as the second mobile switching center, so that the MSC that the other party calls is The second mobile switching center applies for the A-port resource of the other party, that is, the A-port resource of the second calling party, according to the local exchange cancellation request;
  • the notification sub-unit 4023 is further configured to notify the base station controller to cancel the local exchange after receiving an acknowledgment message indicating that the A-port resource of the other party (second calling party) is successfully returned by the MSC that has received the other party's call.
  • the processing unit 402 may further include a switching processing sub-unit 4026;
  • the handover processing sub-unit 4026 is configured to: when the second determining sub-unit 4022 determines that both parties have the capability of starting the local exchange, the handover request sent to the target MSC carries an indication indicating that the local exchange is initiated, so that after the handover is completed, the target MSC Instructing the mobile gateway to release the local port A resource according to the indication that the local exchange is initiated, and notifying the base station controller to initiate the local exchange, and then receiving the handover response returned by the target mobile switching center indicating that the local exchange is successfully started.
  • the processing unit 402 can also be the second sending subunit 4027;
  • the second sending sub-unit 4027 is configured to separately send the local exchange information of the local party and the local exchange information of the other party acquired by the obtaining unit 401 to the target MSC (that is, the local exchange information of the local party and the local exchange information of the other party may not be sent at the same time) ), so that the target MSC performs local exchange processing according to the local exchange information of the party and the local exchange information of the other party.
  • the acquiring unit 401 of the MSC in this embodiment can obtain the local exchange information of the other party sent by the MSC that the other party calls, and then the local exchange information is processed by the processing unit 402 according to the local exchange information of the local party and the local exchange information of the other party. Therefore, under the MSC POOL network, even if the primary and secondary called parties are located on different MSCs, the MSC where the calling party is located can know the base station controller where the other party is located, and can initiate the local exchange judgment for local exchange.
  • the obtaining unit 401 can acquire the local exchange information of the other party sent by the counterpart MSC, if the call is monitored on one of the MSCs, or the operation of playing, supplementing, etc. is performed, the local exchange cannot be initiated, and the other The MSC can also learn that it is beneficial to the implementation of local exchange.
  • the embodiment of the present invention further provides a communication system, including any MSC provided by the embodiment of the present invention.
  • the communication system may specifically include a first mobile switching center (first MSC). 501 and a second mobile switching center (second MSC) 502;
  • the first mobile switching center 501 is configured to acquire local exchange information of the second calling party sent by the second mobile switching center 502 when the calling party is in the first mobile switching center 501 and the second mobile switching center 502, respectively, according to the The local exchange information of the first calling party and the local exchange information of the second calling party are locally exchanged, wherein the local exchange information of the first calling party or the local exchange information of the second calling party respectively includes corresponding Information of the base station controller where the calling party is located;
  • the second mobile switching center 502 is configured to send the local exchange information of the other party to the first mobile switching center 501.
  • the second mobile switching center 502 is further configured to send the local exchange information of the second calling party to the first mobile switching center 501 by using MAP signaling or relay signaling.
  • the local exchange information may include information of the base station controller, such as the base station controller signaling point information, and may also include information such as local exchange capability information, and of course, other information needed to establish and release the local exchange.
  • the Cal l-ID and the A port carry information of the call.
  • the base station controller signaling point information refers to the base station controller where the one call leg is located, and the local exchange capability information refers to whether the call is being monitored, or whether the call is being played or supplemented.
  • the MSC in the communication system of this embodiment can obtain the local exchange information of the other party sent by the MSC that the other party calls, and then perform local exchange processing according to the local exchange information of the local party and the local exchange information of the other party, so that the MSC is in the MSC.
  • the MSC where the calling party is located can know the base station controller where the other party is located, and can initiate the local exchange judgment for local exchange processing, and , because the MSC can obtain the local exchange information sent by the other party's MSC, so if the call is in its When one of the MSCs is monitored, or performs operations such as playback, supplementary services, etc., but cannot initiate local exchange, another MSC can also know that it is advantageous for the implementation of local exchange.
  • the local exchange information between the MSCs may be transmitted through the MAP signaling or the relay signaling.
  • the MAP signaling is used to transmit the local between the MSCs.
  • both the MSC and the HLR need to be modified, but there are fewer changes to the MSC.
  • relay signaling is used to transfer local exchange information between MSCs, only the MSC needs to be modified (no need to modify the HLR), but There are more changes to MSC.
  • it can be selected according to the operator's policy.
  • the program can be stored in a computer readable storage medium.
  • the storage medium can include: Read Only Memory (ROM), Random Access Memory (RAM), disk or optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Description

一种本地交换的实现方法、 移动交换中心和通信系统 本申请要求于 2009年 05月 31日提交中国专利局、申请号为 200910145718. 9、发 明名称为 "一种本地交换的实现方法、 移动交换中心和通信系统"的中国专利申请的优 先权, 其全部内容通过引用结合在本申请中。 技术领域 本发明涉及通信技术领域, 特别涉及一种本地交换的实现方法、 移动交换中心和 通信系统。 背景技术 传输网络是无线通讯网络的重要组成部分,降低对传输网络资源(以下简称传输资 源)的占用, 有利于降低网络建设和运营的成本, 本地交换就是一种有效的降低传输资 源占用的方案。
本地交换指的是对于主叫和被叫位于同一个基站子系统 (BSS, Base Station Subsystem)内的会话,在 BSS内完成语音链路的环回,即用户面的语音数据不流出该 BSS, 从而实现特定接口传输资源的节省的一种技术方案。本地交换可以分为基站(BTS, Base Transceiver Station) 内的本地交换和基站控制器 (BSC, Base Station Controller) 内的本地交换。 其中, 基站内的本地交换, 指的是会话双方位于同一个基站内, 或者 是同一个基站簇内 (对于基站级联的情况) , 语音链路的环回发生在相应的基站中。 而 基站控制器内的本地交换, 则指的是会话双方位于同一基站控制器内, 但在不同的基站 (或基站簇) 内, 语音链路环回发生在相应的基站控制器中。通过建立基站内的本地交 换, 可以实现对 Abis (基站和基站控制器间的接口) 、 Ater (基站和基站控制器间的接 口) 、 以及 A口 (BSS与移动交换中心 (MSC, Mobile Switch Center) 间的接口)传输 资源的节省, 而通过建立基站控制器内的本地交换, 则可以实现对 A口传输资源的节省。
现有技术定义了非 MSC池(POOL) 组网下本地交换的实现方法, 主要是通过 MSC判 断位于同一个 MSC内的主被叫所在的基站控制器是否属于同一个基站控制器, 以及是否 具备启动本地交换的条件来确定是否启动本地交换,若主被叫属于同一个基站控制器且 具备启动本地交换的条件, 则 MSC向基站控制器下发启动本地交换的指示, 基站控制器 执行建立本地交换操作。 MSC收到基站控制器的本地交换建立完成消息后, 释放主被叫 用户使用的 A口电路资源。 其中, 具备启动本地交换的条件指的是没有发生补充业务、 进行放音或合法监听等操作的情况下, 若在启动了本地交换后, 发生补充业务、进行放 音或合法监听等操作,或者发生了切换使得主被叫的基站控制器不再属于同一个基站控 制器的情况, 则需要解除本地交换, 此时 MSC可以通过发送信令要求基站控制器解除本 地交换。
在对现有技术的研究和实践过程中, 本发明的发明人发现, 对于在 MSC POOL组网下 实现本地交换, 现有技术并不存在相关的方案。 发明内容
本发明实施例提供一种本地交换的实现方法、移动交换中心和通信系统,可以在 MSC POOL组网下实现本地交换。
一种本地交换的实现方法, 其特征在于, 包括:
当呼叫双方分别在第一移动交换中心与第二移动交换中心时,第一呼叫方所在的第 一移动交换中心获取第二移动交换中心发送的第二呼叫方的本地交换信息;
第一移动交换中心根据第一呼叫方的本地交换信息,以及第二呼叫方的本地交换信 息进行本地交换的处理, 其中, 第一呼叫方的本地交换信息或第二呼叫方的本地交换信 息分别包括相应呼叫方所在的基站控制器的信息。
一种移动交换中心, 其特征在于, 包括:
获取单元,用于当呼叫双方分别在第一移动交换中心与第二移动交换中心时,获取 第二移动交换中心发送的第二呼叫方的本地交换信息;
处理单元,用于根据第一呼叫方的本地交换信息, 以及所述第二呼叫方的本地交换 信息进行本地交换的处理, 其中, 所述第一呼叫方的本地交换信息或第二呼叫方的本地 交换信息分别包括相应呼叫方所在的基站控制器的信息。
一种通信系统, 其特征在于, 包括第一移动交换中心和第二移动交换中心; 所述第一移动交换中心,用于当呼叫双方分别在第一移动交换中心与第二移动交换 中心时, 获取第二移动交换中心发送的第二呼叫方的本地交换信息, 根据所述第一呼叫 方的本地交换信息, 以及所述第二呼叫方的本地交换信息进行本地交换的处理, 其中, 所述第一呼叫方的本地交换信息或第二呼叫方的本地交换信息分别包括相应呼叫方所 在的基站控制器的信息;
所述第二移动交换中心, 用于发送本方的本地交换信息给第一移动交换中心。 本发明实施例采用接收对方呼叫的 MSC发送的对方的本地交换信息, 然后根据本方 的本地交换信息和对方的本地交换信息进行本地交换的处理, 使得在 MSC POOL组网下, 即使主被叫分别位于不同的 MSC上, 主叫或被叫也可以得知对方呼叫所在的 BSC, 可以进 行启动本地交换的判断以便进行本地交换的处理。 附图说明 图 1是本发明实施例一所提供的方法的方法流程图;
图 2是本发明实施例二所提供的方法的方法流程图;
图 3是本发明实施例二所提供的方法的另一方法流程图;
图 4是本发明实施例二所提供的方法的又一方法流程图;
图 5是本发明实施例三所提供的方法的方法流程图;
图 6是本发明实施例三所提供的方法的另一方法流程图;
图 7是本发明实施例三所提供的方法的又一方法流程图;
图 8是本发明实施例所提供的移动交换中心的结构示意图;
图 9是本发明实施例所提供的通信系统的结构示意图。 具体实施方式 下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整 地描述, 显然, 所描述的实施例仅仅是本发明一部分实施例, 而不是全部的实施例。 基 于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有 其他实施例, 都属于本发明保护的范围。
在 MSC POOL组网下, 由于主被叫可能位于同一基站控制器却分别位于不同的 MSC上, 主被叫所在的 MSC都无法相互得知对方呼叫所在的基站控制器, 因此无法进行启动本地 交换的判断。 而且, 如果呼叫在其中一个 MSC上被监听, 或进行放音、 补充业务等操作 而不能启动本地交换时, 另一个 MSC也无法得知。 为了使得在 MSC POOL组网下可以实现 本地交换, 本发明实施例提供一种本地交换的实现方法, 同时还提供相应的移动交换中 心和通信系统。 以下分别进行详细说明。
实施例一、
本实施例将从移动交换中心, 即 MSC的角度进行描述。 需说明的是, 本发明实施例 所说的 "本方"和 "对方"是针对于呼叫而言的, 例如, 从主叫的角度来说, 主叫就是 "本方" , 被叫就是 "对方" , 从被叫的角度来说, 被叫就是 "本方" , 主叫就是 "对 方"。 本发明实施例中将本方的移动交换中心称为第一移动交换中心, 对方的移动交换 中心称为第二移动交换中心, 因此, 第一、 二移动交换中心可以为主叫方的移动交换中 心, 也可以为被叫方的移动交换中心, 当第一移动交换中心为主叫方移动交换中心时, 第二移动交换中心为被叫方移动交换中心, 当第一移动交换中心为被叫方移动交换中心 时, 第二移动交换中心为主叫方移动交换中心。 方案如下:
一种本地交换的实现方法,包括: 当呼叫双方分别在第一移动交换中心与第二移动 交换中心时, 第一移动交换中心获取第二移动交换中心的本地交换信息, 根据本方的本 地交换信息和第二移动交换中心的本地交换信息进行本地交换的处理。 由于主被叫双方 的 MSC之间可以进行本地交换信息的交互, 可以让双方都可以充分了解对方的本地交换 信息, 所以可以根据完整的本地交换信息(包括主被叫双方的本地交换信息)进行本地 交换的处理。 如图 1所示, 具体流程可以如下:
101、 第一移动交换中心获取第二移动交换中心发送的对方的本地交换信息; 例如, 可以通过移动应用部分 (MAP, Mobile Application Part ) 信令或中继信令 获取对方 MSC发送的对方的本地交换信息, 其中, 本地交换信息可以包括基站控制器信 令点信息, 还可以包括对方的本地交换能力信息, 当然, 还包括建立或解除本地交换所 需使用的其它信息, 例如呼叫的 Call-ID或 A口承载信息等信息。 其中, 基站控制器信令 点信息指的是一方呼叫腿(所谓呼叫腿就是指一方呼叫。 比如, 一个呼叫是由主叫方和 被叫方组成的, 每一方都叫做一个呼叫腿。 )所在的基站控制器信息, 可以是第一移动 交换中心或第二移动交换中心的本局内呼叫方所在的基站控制器信令点信息,根据基站 控制器信令点信息可以来判断主被叫双方所属的 BSC是否是同一个 BS (:,依据判断结果判 定是否需要执行本地交换。 而本地交换能力信息是指呼叫是否被监听, 或是否在进行放 音、 补充业务等操作, 根据对方的本地交换能力信息可以进一步判断对方是否可以进行 本地交换。 Call-ID用于标识主叫方和被叫方的呼叫信息, 执行本地交换的移动交换中 心获得对方的 Call-ID后, 将本方和对方的 Call-ID提供给基站控制器, 使得基站控制器 根据 Cal 1-ID建立本地交换。 A口承载信息用于在执行本地交换的移动交换中心在解除本 地交换的时候使用。
若主被叫双方是通过 MAP信令来进行本地交换信息的提供(即是通过 MAP信令承载来 承载本地交换信息) , 则可以获取对方呼叫的 MSC的地址, 然后根据获取到的对方的 MSC 的地址来进行 MAP信令的寻址,并利用国际移动用户识别码(MSI, International Mobile Subscriber Identity) 信息来进行呼叫的关联, 以便后续执行过程中 MSC可以根据本方 的本地交换信息和对方的本地交换信息对关联后的呼叫进行本地交换的处理。 也就是 说, 在通过 MAP信令获取对方呼叫的 MSC发送的对方的本地交换信息之前, 还可以发送本 方呼叫的 MSC的地址和本方呼叫的 B1SI信息给对方呼叫的 MSC, 然后对方呼叫的 MSC就可 以根据本方呼叫的 MSC的地址发送对方的本地交换信息给本方呼叫的 MSC, 其中, 该对方 的本地交换信息中携带本方呼叫的 B1SI信息, 这样, 本方呼叫的 MSC接收到该对方的本 地交换信息后,就可以根据接收到的对方的本地交换信息中携带的本方呼叫的 nisi信息 对呼叫进行关联,然后根据本方的本地交换信息和对方的本地交换信息再对关联后的呼 叫进行本地交换的处理。
102、 第一移动交换中心根据本方的本地交换信息和作为对方的第二移动交换中心 的本地交换信息进行本地交换的处理,包括关于建立本地交换的处理或关于解除本地交 换的处理等;
例如,若根据本方呼叫的基站控制器信令点信息和对方呼叫的基站控制器信令点信 息确定双方呼叫属于同一个基站控制器, 通知基站控制器启动本地交换, 并通知移动网 关释放本方的 A口资源; 另外, 如果本地交换信息还包括本地交换能力, 第一移动交换 中心还可以继续判断, 即再根据本方的本地交换能力信息和对方的本地交换能力信息确 定双方是否都具备启动本地交换的能力时, 在判断结果为是时, 才通知基站控制器启动 本地交换, 并通知移动网关释放本方的 A口资源; 如果本地交换信息不包括本地交换能 力, 为了保障本地交换的正确执行, 第二移动交换中心在向第一移动交换中心提供本地 交换信息之前, 可以先判断自身是否具备本地交换能力, 如果是, 才向第一移动交换中 心提供本地交换信息,而第一移动交换中心在获取第二移动交换中心的本地交换信息之 前或者处理本地交换之前都可以判断自身是否具备本地交换能力, 如果是, 才执行相应 的操作。当然,也可以直接根据主被叫双方的信令点信息及直接判断是否执行本地交换, 而不用考虑本地交换能力的信息。
其中, 在通知移动网关释放本方的 A口资源之后, 还可以发送本地交换建立响应消 息给对方的 MSC, 以便对方呼叫的 MSC可以根据该本地交换建立响应消息通知移动网关释 放对方的 A口资源。 也就是说, 可以让主被叫双方各自对本地交换进行判断和启动, 也 可以只让其中一方对本地交换进行判断和启动, 然后再通知另一方。
在本地交换建立之后, 若需要对本地交换进行解除时, 例如需要被合法监听, 或进 行放音、 补充业务操作时, 可以根据本方的本地交换信息和对方的本地交换能力信息向 移动网关申请本方的 A口资源, 若申请本方的 A口资源成功, 则发送本地交换解除请求给 对方 MSC, 以便对方呼叫的 MSC根据该本地交换解除请求向移动网关申请对方的 A口资源, 在接收到对方呼叫的 MSC返回的表示成功申请了对方的 A口资源的确认消息后,通知基站 控制器解除本地交换。 需说明的是, 对方 MSC在申请 A口资源成功后, 也可以通知基站控 制器解除本地交换, 然后才返回表示成功申请了对方的 A口资源的确认消息给本方 MS (:。
或者,在本地交换建立之后,若需要对本地交换进行解除时,也可以先不申请本方 的 A口资源, 直接发送本地交换解除请求给对方 MSC, 以便对方呼叫的 MSC根据该本地交 换解除请求向移动网关申请对方的 A口资源,在接收到对方呼叫的 MSC返回的表示成功申 请了对方的 A口资源的确认消息后, 再申请本方的 A口资源, 若申请 A口资源失败, 则不 解除本地交换, 否则, 若申请 A口资源成功, 则通知基站控制器解除本地交换。
由上可知, 本实施例采用接收对方呼叫的 MSC发送的对方的本地交换信息, 然后根 据本方的本地交换信息和对方的本地交换信息进行本地交换的处理, 使得在 MSC POOL组 网下, 即使主被叫分别位于不同的 MSC上, 主叫或被叫所在的 MSC也可以得知对方呼叫所 在的基站控制器, 可以进行启动本地交换的判断以便进行本地交换的处理, 而且, 由于 可以接收对方呼叫的 MSC发送的对方的本地交换信息,所以如果呼叫在其中一个 MSC上被 监听, 或进行放音、 补充业务等操作而不能启动本地交换时, 另一个 MSC也可以得知, 有利于本地交换的实现。
需要说明的是,上述实施例以一方获取另一方的信息进行判断后执行本地交换,而 实际实现时, 也可以主被叫双方都获取对方的信息进行判断, 都对本地交换进行处理, 例如以下方案:
第一移动交换中心获取第二移动交换中心的本地交换信息,第一移动交换中心根据 自身的本地交换信息与所述第二移动交换中心的本地交换信息进行本地交换的处理; 第二移动交换中心获取第一移动交换中心的本地交换信息,第二移动交换中心根据 自身的本地交换信息与所述第一移动交换中心的本地交换信息进行本地交换的处理。
实施例二、
根据实施例一所描述的方法,本实施例将以采用 MAP信令在 MSC之间交换本地交换信 息来实现本地交换为例作详细说明。 方案如下:
1、 主被叫 MSC之间通过 MAP信令携带本地交换信息并传送。
一方 MSC使用 MAP信令向对方 MSC发送本方的本地交换信息。另一方 MSC接收到对方本 地交换相关信息后, 保存接收到的对方 MSC的本地交换信息, 使用 MAP信令向对方返回本 方的本地交换信息。 其中, 若在呼叫过程中, 一方 MSC的本地交换信息发生了变化, 还 需要将发生了变化的本地交换信息发送给另一方 MSC, 以保证主被叫 MSC都能够及时充分 地了解对方的本地交换信息, 以便主被叫 MSC可以根据完整的本地交换信息, 即两个 MSC 内的本地交换信息进行本地交换的处理。
2、主被叫 MSC之间通过对方 MSC的地址来相互进行 MAP信令的寻址。其中,主被叫 MSC 分别获取对方 MSC的地址(即主叫 MSC获取被叫 MSC的 MSC地址, 被叫 MSC获取主叫 MSC的地 址) 的方法可以如下:
呼叫建立过程中, 主被叫 MSC之间通过路由信息请求 (SRI, SEND ROUTING
INFORMATION Request ) 、 漫游号码请求 (PRN, PROVIDE ROAMING NUMBER Request ) 、 漫游号码响应(PRN ack, PROVIDE ROAMING NUMBER Response)、路由信息响应(SRI ack,
SEND ROUTING INFORMATION Response) 来传递主被叫頂 SI信息和主被叫 MSC的地址。
例如, 主叫发起呼叫, 主叫 MSC发送路由信息请求给 HLR以获取被叫路由信息, 该路 由信息请求中携带主叫 MSC的地址和主叫 B1SI ; HLR向被叫 MSC发送漫游号码请求以获取 被叫漫游号码, 该漫游号码请求中携带主叫 MSC的地址和主叫 B1SI信息, 被叫 MSC保存主 叫 MSC的地址和主叫 B1SI信息。 被叫 MSC向 HLR返回漫游号码响应时, 携带被叫 MSC的地址 和被叫 B1SI信息, HLR向主叫 MSC返回取路由信息响应时,携带被叫 MSC的地址和被叫 nisi 信息, 主叫 MSC-A保存被叫 MSC的地址和被叫 nisi信息。
3、主被叫 MSC之间使用頂 SI来关联呼叫。即主被叫 MSC收到对方 MSC的本地交换信息 后, 使用本 MSC内呼叫的頂 SI来关联到相应的呼叫。 因此, 主被叫 MSC还需要分别获取对 方頂 SI信息, 这可以通过在发送给对方的 MAP信令中携带对方呼叫腿的用户頂 SI信息来 实现。 参见 2中的描述。
上面所说的可以用来传送本地交换信息的 MAP信令, 实施时可以通过对现有的 MAP 信令进行改造来实现, 例如扩展现有的 MAP信令 SRI和 PRN等; 也可以通过新增 MAP信令来 实现,在本实施例中,将以新增 MAP信令为例进行说明。假设该新增的 MAP信令命名为 [MAP LCLS serevice] , 且该信令可以携带如下信息 (根据不同的场景选择携带) :
(1) 对方的 si。
(2) 本局内呼叫所在的基站控制器信令点信息。
( 3) 本地交换指示, 可以用承载本地交换能力信息。 例如, 可以包括如下指示类 型: 本地交换(LCLS, Local Call Local Switch)建立请求; LCLS建立允许; LCLS建 立拒绝; LCLS解除请求; LCLS解除允许; LCLS解除拒绝; LCLS禁止指示; LCLS允许指示; LCLS建立指示; LCLS解除指示;
(4)本局内呼叫对应的呼叫标识(Call-ID); MSC和基站控制器之间使用 Call-ID 来标识一个呼叫腿。
( 5)本局内的 A口承载信息; 基站控制器在解除本地交换时, 需要使用两个呼叫腿 的 A口承载信息。
以下将通过几个具体的场景对该方案进行详细说明。为了描述方便, 以下均假设主 叫终端为 MS-A, 主叫 MSC为 MSC-A, 被叫终端为 MS_B, 被叫 MSC为 MSC_B。
(一)场景一: 呼叫建立过程
呼叫建立过程中, 主被叫 MSC, 即 MSC-A和 MSC-B通过 SRI、 PRN、 PRN ack、 SRI ack 来传递主被叫用户的 BiSI和主被叫 MSC的地址信息。 如图 2所示, 具体流程可以如下:
A20K MS-A发送业务请求(CM Service Req)给 MSC-A;
A202、 MSC-A对 MS-A进行鉴权和加密处理, 比如, MSC-A与 MS-A之间进行 Authenticate&Chiper消息的交互;
A203、 MS-A发送建立 (SETUP ) 消息给 MSC_A, MSC-A返回呼叫进行消息 (Call Proceeding)给 MS-A;
A204、 MSC-A向移动网关发送建立请求 (ADD_REQ ) , 移动网关返回建立响应 (ADD—REPLY)给 MSC- A;
A205、 MSC-A发送指配请求 (ASS_REQ) 给基站控制器, 基站控制器发送指配命令
(ASS_CMD)给 MS-A, MS-A返回指配完成 (ASS_C0MP) 给基站控制器, 基站控制器返回 指配响应(ASS_RSP)给 MSC-A;
A206、 MSC-A发送路由信息请求给 HLR, 请求 MS_B的路由信息, 其中, 路由信息请求 中携带 MSC-A的地址和 MS-A的頂 S I;
A207、 HLR向 MSC-B发送漫游号码请求以获取被叫漫游号码,该漫游号码请求中携带
MSC-A的地址和 MS-A的頂 S I信息;
A208、MSC_B保存 MSC-A的地址和 MS-A的頂 SI信息, MSC-B返回漫游号码响应给 HLR时, 该漫游号码响应中携带 MSC-B的地址和 MS-B的 B1SI信息;
A209、 HLR返回路由信息响应给 MSC-A, 该路由信息响应中携带 MSC-B的地址和 MS_B 的頂 SI信息, MSC-A保存 MSC-B的地址和 MS-B的頂 SI信息; A210、 MSC-A再次向移动网关发送建立请求, 移动网关返回建立响应给 MSC-A; A21 K通过在步骤 A206至步骤 A208的交互和寻址, MSC-A和 MSC-B根据各自保存的对 方的頂 SI信息进行呼叫关联, MSC-A发送初始地址消息 (IAM)给 MSC-B, MSC-B发送寻呼 (Page )给基站控制器, 基站控制器发送寻呼给 MS-B, MS-B可以返回寻呼响应给基站控 制器, 基站控制器接收到该寻呼响应 (Page rsp) 后, 可以发送寻呼响应给 MSC-B;
A212、 MSC-B对 MS-B进行鉴权和加密处理, 比如, MSC-B与 MS_B之间进行 Authenticate&Chiper消息的交互; 同时, MSC-B向移动网关发送建立请求, 移动网关可 以返回建立响应给 MSC-B ; MSC-B发送建立消息给 MS-B, MS_B返回呼叫确认 (Cal l Confrimed) 给 MSC-B;
A213、 MSC-B向移动网关再次发送建立请求, 移动网关可以返回建立响应给 MSC-B;
A214、 MSC-B发送指配请求给基站控制器, 基站控制器发送指配命令给 MS-B, MS-B 返回指配完成给基站控制器, 基站控制器返回指配响应给 MSC-B;
A215、 MS-B可以发送振铃消息 (ALERT) 给 MSC_B, MSC-B发送地址完成消息 (ACM) 给 MSC-A, MSC-A发送振铃消息给 MS-A, 此后, MS-B发送连接消息 (CONNECT) 给 MSC_B, MSC-B可以返回连接确认(C0N ECT_ACK)给 MS_B, MSC-B发送应答消息 (ANM)给 MSC_A, MSC-A发送连接消息给 MS-A, MS-A可以返回连接确认消息给 MSC-A; 至此, MS-A与 MS-B的 呼叫建立完成。
A216、 MSC-B根据 MSC-A的地址发送的本地交换信息请求(LCLS info Req)给 MSC_A, 该用来传送本地交换信息的 MAP信令中携带 MS-B所在的基站控制器信令点信息和 MSC-B 的本地交换能力信息, 还可以携带 MS-B的 Cal l-ID;
A217、 MSC-A判断本地交换启动条件是否具备, 若具备, 则启动本地交换, 即执行 步骤 A218;
例如,根据 MS-A所在的基站控制器信令点信息和 MS-B所在的基站控制器信令点信息 确定双方呼叫是否属于同一个基站控制器;
若为同一个基站控制器,则在根据 MSC-A的本地交换能力信息和 MSC-B的本地交换能 力信息确定双方都具备启动本地交换的能力 (比如主被叫编解码相同, 被叫 BSC支持本 地交换, 被叫用户没有被监听等) 时, 通知 MS-A所在的基站控制器启动本地交换(步骤 A218 ) , 并通知移动网关释放 MS-A的 A口资源 (步骤 A219 ) ; 如果确定本局不具备启动 本地交换的能力, 则在返回给 MSC-B的本地交换信息确认消息 (LCLS info Cnf) 中指示 不允许本地交换, MSC-B接收到该本地交换信息确认消息后, 如果该本地交换信息确认 消息中指示不允许本地交换, 则不会启动本地交换。
若 MSC-A虽然没有启动本地交换的限制, 但 MS-A和 MS-B不属于同一个基站控制器, 则直接给 MSC-B返回本地交换信息确认消息, 携带 MS-A的基站控制器信令点信息及相应 的 Call- ID。
在本实施例中,假设 MS-A和 MS-B均属于同一个基站控制器,具体可以属于同一个基 站控制器, 且 MSC-A和 MSC-B都具备启动本地交换的能力, 于是, MSC-A在接收到 MSC-B发 送的本地交换信息请求后, 启动本地交换, 即执行步骤 A218;
A218、 MSC-A发送本地交换命令 (LOCAL SWITCH COMMAND) 给基站控制器以启动本 地交换, 基站控制器返回本地交换完成消息 (LOCAL SWITCH COMP) 给 MSC_A, MSC-A返 回本地交换信息确认消息给 MSC-B, 该本地交换信息确认消息中携带 MS-A的基站控制器 信令点信息及相应的 Call-ID, 并指示本地交换已经启动;
需说明的是,如果基站控制器启动本地交换失败,则 MSC-A向 MSC-B返回本地交换信 息确认消息时, 在本地交换信息确认消息中携带 MS-A所在的基站控制器信令点信息, 并 指示本地交换没有启动。
A219、 MSC-A发送删除请求 (SUB_REQ) 给移动网关, 以释放 MS-A的 A口资源; 移动 网关可以返回删除响应 (SUB_REPLY) 给 MSC-A;
A220、 MSC-B接收到 MSC-A返回本地交换信息确认消息后,如果本地交换信息确认消 息中指示本地交换已经启动, 则发送删除请求给移动网关, 以释放 MS-B的 A口资源; 移 动网关可以返回删除响应给 MSC-B; 如果本地交换信息确认消息中指示本地交换没有启 动, 则不动作。
至此, 本地交换建立完成。 需说明的是, 主被叫 MSC之间, 即 MSC-A和 MSC-B之间不 需要保持 MAP连接; 另外, 本地交换启动后, MSC-A与 MSC-B之间的中继资源不释放, 因 为如果释放了, 后续就无法对该已经建立的本地交换进行解除了。
当然, 本地交换信息请求也可以由 MSC-A首先发起, 实现方式与前面所描述的由 MSC-B首先发起的类似, 即 MSC-B接收到 MSC-A发送的本地交换信息请求后, MSC-B根据 MS-A所在的基站控制器信令点信息和 MS-B所在的基站控制器信令点信息确定双方呼叫 是否属于同一个基站控制器; 若为同一个基站控制器, 则在根据本方的本地交换能力信 息和对方的本地交换能力信息确定双方都具备启动本地交换的能力(比如主被叫编解码 相同, 被叫 BSC支持本地交换, 被叫用户没有被监听等) 时, 通知 MS-B所在的基站控制 器启动本地交换, 并通知移动网关释放 MS-B的 A口资源, 此外, MSC-B还可以返回本地交 换信息确认消息给 MSC-A, 该本地交换信息确认消息中携带 MS-B的基站控制器信令点信 息及相应的 Cal l-ID, 并指示本地交换已经启动; 如果确定本局不具备启动本地交换的 能力, 则在返回给 MSC-A的本地交换信息确认消息中指示不允许本地交换, MSC-A接收到 该本地交换信息确认消息后, 如果该本地交换信息确认消息中指示不允许本地交换, 则 不会启动本地交换。 若 MSC-B虽然没有启动本地交换的限制, 但 MS-A和 MS-B不属于同一 个基站控制器, 则直接给 MSC-A返回本地交换信息确认消息, 携带 MS-B的基站控制器信 令点信息及相应的 Cal l-ID。
另外, 需说明的是, 除了上面所描述的让一方 MSC判断和启动本地交换之外, 也可 以由主被叫 MSC各自判断和启动本地交换。例如, 在步骤 A216之后, MSC-A可以返回本地 交换信息确认消息给 MSC-B然后, MSC-A和 MSC-B分别判断自身的本地交换启动条件是否 具备, 若具备, 则 MSC-A和 MSC-B分别启动本地交换, 即一方面, MSC-A通知 MS-A所在的 基站控制器启动本地交换, 并通知移动网关释放 MS-A的 A口资源; 另一方面 MSC-B也通知 MS-B所在的基站控制器启动本地交换, 并通知移动网关释放 MS-B的 A口资源。
在呼叫过程中, MSC-A与 MSC-B之间可以通过本地交换信息请求和本地交换信息确认 消息来更新呼叫的本地交换能力信息,即当呼叫的本地交换能力信息发生变化时, MSC-A 与 MSC-B之间要动态地进行交互。 比如, 在呼叫发起时, 由于 MS-A与 MS-B不在同一个基 站控制器而没有启动本地交换, 但没有其他本地交换的限制, 在呼叫进行中, 如果 MS-A 的用户被监听或发生补充业务, 则 MSC-A需要通知 MSC-B该呼叫不再具备本地交换能力; 如果后续监听解除或补充业务结束,则 MSC-A需要通知 MSC-B该呼叫又具备了本地交换能 力。 当一个呼叫不具备本地交换能力时, 即使主被叫用户属于同一个基站控制器, 也不 会启动本地交换。
(二)场景二: 在本地交换建立后, MSC要求解除本地交换
MSC-A发生补充业务等操作需要解除本地交换时, MSC-A根据两方的本地交换信息 向移动网关申请 A口资源, 若申请 A口资源成功, 则向 MSC-B发送本地交换信息请求, 通 知 MSC-B并要求解除本地交换; MSC-B收到该本地交换信息请求后, 向移动网关申请 A口 资源, 如可以申请到 A口资源, 则向 MSC-A返回本地交换信息确认消息, 并在该本地交换 信息确认消息中携带相应的 A口资源, MSC-A收到 MSC-B的本地交换信息确认消息后, 指 示基站控制器解除本地交换, 本地交换解除后, MSC-A再通过本地交换信息请求告知 MSC-B本地交换已解除。需说明的是,若 MSC-A要求基站控制器解除本地交换失败, MSC-A 也要通过本地交换信息请求知会 MSC-B, 以便 MSC-A和 MSC-B释放已经申请的 A口资源。
当然,除了上面所描述的由一方的 MSC, 比如由 MSC-A要求基站控制器解除本地交换 之外, 也可以由双方的 MSC, 即由 MSC-A和 MSC-B分别要求基站控制器解除本地交换。 例 如, 可以如下:
MSC-A发生补充业务等操作需要解除本地交换时, MSC-A根据两方的本地交换信息 向移动网关申请 A口资源, 若申请 A口资源成功, 则向 MSC-B发送本地交换信息请求, 通 知 MSC-B并要求解除本地交换; MSC-B收到该本地交换信息请求后, 向移动网关申请到 A 口资源, 并向 MSC-A返回本地交换信息确认消息, 该本地交换信息确认消息中不需携带 A 口资源信息, 同时指示基站控制器解除本地交换, 并返回本地交换确认消息告知 MSC-A 本地交换已解除, MSC-A收到本地交换确认消息后, 指示基站控制器解除本地交换。
当然, MSC-A也可以直接向 MSC-B请求解除本地交换, MSC-B接收到该请求后, 向移 动网关申请 A口资源, 若 MSC-B申请 A口资源成功, 则返回本地交换确认消息告知 MSC-A, MSC-A接收到该本地交换确认消息后, MSC-A向移动网关申请 A口资源, 若 MSC-A申请 A口 资源不成功, 则不解除本地交换; 若 MSC-A申请成功, 则指示基站控制器解除本地交换; 若 MSC-B申请 A口资源不成功, 则会向 MSC-A返回拒绝消息, MSC-A收到拒绝消息后, 不 再解除本地交换。 其中, 对于不同的启动解除本地交换的原因, MSC-A将会做不同的处 理, 比如, 如果是要进行补充业务, 则 MSC-A拒绝补充业务; 如果是要进行合法监听, 则可以释放呼叫或者不进行监听。
(三)场景三: 切换过程中建立本地交换
在呼叫过程中没有建立本地交换,但是经过切换之后,主被叫双方所在的基站控制 器属于同一个基站控制器, 且双方都具备启动本地交换的能力, 那么, 此时需要建立本 地交换。也就是说, 一个用户切换到另一用户所在基站控制器, 且本地交换建立条件都 已具备时, 需要建立本地交换。
下面将举例说明局间呼叫流程中,如果一方发生基站控制器间的切换,本地交换的 建立方法。 其中, 基站控制器间的切换包括两种, 一种为局内的基站控制器间的切换, 另一种为局间的基站控制器间的切换。假设切换前的基站控制器为源基站控制器, 切换 后的基站控制器为目标基站控制器, 源基站控制器为 BSC1 , 目标基站控制器为 BSC2; 首先, 描述在局间呼叫流程中, 主叫发生局内的基站控制器间切换的场景, 如图 3 所示, 具体流程如下: B201、 BSC1发送请求切换消息 (Handover Required)给 MSC-A, MSC-A发送建立请 求给移动网关, 移动网关可以返回建立响应给 MSC-A;
B202、 MSC-A发送切换请求(Handover Request )给 BSC2, 该切换请求中携带本地 交换指示(LS ind) , 比如指示 BSC2启动本地交换或解除本地交换等等;
例如, MSC-A可以根据在呼叫建立阶段和呼叫过程中 MSC-A与 MSC-B之间交互的相关 信息,比如 MSC-B的本地交换能力信息判断 MSC-B是否具备启动本地交换的能力,若具备, 则 MSC-A发送切换请求给 BSC2时, 可以在该切换请求中指示 BSC2启动本地交换, 并携带 切换后的呼叫的 Cal l-ID; 若不具备, 则在发给 BSC2的切换请求消息中, 不会指示启动 本地交换;
BSC2可以返回切换请求确认消息 (Handover Request ack)给 MSC_A, 该切换请求 确认消息中携带本地交换确认信息 (LS ack) ;
B203、 MSC-A发送切换命令(Handover Command)给 BSC1 ;
B204、 BSC2发送发现切换消息 (Handover Detect ) 给 MSC_A, 以及发送切换完成 (Handover Complete )给 MSC-A;
B205、 MSC-A发送清除命令(CI ear Command)给 BSC1, BSC1返回清除完成消息(Clear
Complete )给 MSC- A;
B206、 MSC-A发送本地交换信息请求给 MSC-B, 以启动本地交换,该本地交换信息请 求携带主叫所在的基站控制器信令点信息、 相应的 Cal l-ID、 以及本地交换已经启动的 指示; MSC-B可以返回本地交换信息确认消息给 MSC-A, 此后, 若具备启动本地交换的条 件, 则 MSC-A通知 MS-A所在的基站控制器启动本地交换, 并通知移动网关释放 MS_A的 A口 资源; 此时, MSC-B也通知 MS-B所在的基站控制器启动本地交换, 并通知移动网关释放 MS-B的 A口资源。解除本地交换的方法具体可参见场景一中的相关描述, 在此不再赘述。
下面描述在局间呼叫流程中,用户发生局间的基站控制器切换的场景,即源基站控 制器与目标基站控制器所属的 MSC不同。在此假设主叫用户发生局间的基站控制器切换, 源 MSC为 MSC-A,源 BSC为 BSC 1, 目标 MSC为 MSC-A' , 目标 BSC为 BSC2,被叫的 MSC为 MSC-B, 被叫的 BSC为 BSC2, 则如图 4所示, 具体流程如下:
C20K MSC-A接收到切换请求后, 若 MSC-A判断可以启动本地交换, 比如 MSC-A根据 本方的本地交换能力信息和对方的本地交换能力信息确定双方都具备启动本地交换的 能力, 则在发送给 MSC-A' 的切换请求中携带表示启动本地交换的指示, 以便切换完成 后, MSC-A' 根据该表示启动本地交换的指示通知移动网关释放本方的 A口资源以及通知 基站控制器启动本地交换, MSC-A' 返回的表示本地交换成功启动的切换响应给 MSC-A; 其中, 发送给 MSC-A' 的切换请求可以是准备切换请求(MAP Prepare Handover Req) ;
C202、 MSC-A' 发送切换请求给 BSC2, 该切换请求中携带本地交换指示, 比如指示 BSC2启动本地交换或解除本地交换等等, 以及携带切换后的呼叫的 Cal l-IDBSC2可以返 回切换请求确认消息给 MSC-A' , 该切换请求确认消息中携带本地交换确认信息;
C203、 MSC-A' 发送切换请求确认消息给 MSC-A,该切换请求确认消息中携带本地交 换确认信息;其中,该切换请求确认消息也可以是准备切换响应(MAP Prepare Handover Resp) ;
C204、 切换完成后, MSCA, 自行通知移动网关释放相应的 A口承载, 由 MSC-A和 /或 MSC-B通知基站控制器启动本地交换, MSC-A与 MSC-B之间的流程同用户发生局内的基站 控制器切换时的流程, 例如, MSC-A发送本地交换信息请求给 MSC-B, MSC-B返回本地交 换信息确认消息给 MSC-A, 并且, MSC-B通知移动网关释放 A口资源等等, 具体客参见前 面实施例, 在此不再赘述。
当然, 除了上面所描述的由 MSC-A判断是否可以启动本地交换之外, 也可以由 MSC-A' 来进行判断, 如下:
在局间切换完成后,无论是否启动了本地交换, MSC-A都要给 MSC-A' 发送本地交换 信息, 例如通知 MSC-A' 本呼叫的本地交换能力, 以及 MSC-B所在的基站控制器信令点信 息和 Cal l-ID, 以便目标移动交换中心根据本方的本地交换信息和对方的本地交换信息 进行本地交换的处理。另外,在后续呼叫过程中,若该呼叫的本地交换能力信息或 MSC-B 所在的基站控制器信令点信息发生变化时, MSCA也都要通知 MSCA' 。
下面再描述局间切换完成后,用户再发生局内切换时,本地交换的检查和启动流程。 即, 如果局间切换后, 主被叫并不在一个基站控制器上而没有启动本地交换, 后续用户 在 MSC-A' 内发生局内跨基站控制器切换, 如果切换到了对方用户所在的基站控制器, 则此时可以启动本地交换。
MSC-A' 收到切换请求后,首先发送本地交换信息请求询问 MSC-A是否可以启动本地 交换, 该本地交换信息请求中携带切换目标 BSC信息, 若 MSC-A判断可以启动本地交换, 则给 MSC-A' 返回允许启动本地交换的指示, MSC-A' 继续进行后续的切换和启动本地交 换操作, 具体可参见前面实施例, 切换完成后, MSC-A' 要知会 MSC-A已经启动了本地交 换。 MSC-A需要向 MSC-B传递 MSC-A' 的本地交换信息。 当然,也可以由 MSC-A' 自行判断是否可以启动本地交换,即 MSC-A' 收到切换请求 后, 自行判断是否可以启动本地交换, 如果可以启动则在切换流程中启动本地交换, 切 换完成后, MSC-A' 通知 MSC-A已经启动了本地交换, MSC-A需要向 MSC-B传递 MSC-A' 的 本地交换信息。
需说明的是, 在 MSC P00L组网下, 呼叫的一方发生跨基站控制器切换后, 即使没有 启动本地交换, 该呼叫所在的 MSC也要向对方 MSC通知新的基站控制器信息。
(四)场景四: 切换过程中解除本地交换
首先,描述在局间呼叫流程中,用户发生局内的基站控制器切换时,本地交换解除 的流程。 如下:
MSC-A接收切换请求, 根据接收到切换请求判断需要解除本地交换时, 发送本地交 换解除请求给 MSC-B, 比如发送本地交换信息请求给 MSC-B, MSC-B接收到后, 可以根据 该本地交换解除请求判断是否可以解除本地交换, 若不能解除, 则向 MSC-A返回表示拒 绝的消息, MSC-A接收到该表示拒绝的消息后, 拒绝切换; 若可以解除, 则向移动网关 申请 A口资源, 并向 MSC-A返回表示成功申请了 A口资源的确认消息, 比如向 MSC-A返回本 地交换信息确认消息, 其中, 该本地交换信息确认消息中携带 MSC-B向移动网关申请的 A 口资源, MSC-A接收到该确认消息后, 向移动网关申请 A口资源, 通知基站控制器解除本 地交换, 并进行后面的切换处理, 在发送给源 BSC的切换命令中携带解除本地交换的指 示, 以及 MSC-B申请的 A口资源信息, 在切换完成后, 通知 MSC-B本地交换已经解除。
当然, MSC-A也可以在向 MGW申请 A口资源后,再向 MSC-B发送本地交换信息请求, 即 MSC-A向移动网关申请 A口资源,若申请 A口资源成功,才发送本地交换信息请求给 MSC-B。
另外,除了上面所描述的只由一方的 MSC, 比如 MSC-A来指示基站控制器解除本地交 换之外, 也可以由双方的 MSC, 比如 MSC-A和 MSC-B各自指示 BSC解除本地交换。 如下:
MSC-A接收切换请求, 根据接收到的切换请求判断需要解除本地交换时, 发送本地 交换解除请求给 MSC-B, 比如发送本地交换信息请求给 MSC-B, MSC-B接收到后, 根据该 本地交换信息请求判断是否允许解除本地交换, 若不能解除, 则向 MSC-A返回表示拒绝 的消息, MSC-A接收到该表示拒绝的消息后, 拒绝切换; 若可以解除, 则向移动网关申 请 A口资源,并返回本地交换解除允许指示给 MSC-A (不携带申请的 A口资源信息), MSC-A 根据本地交换解除允许指示进行后面的切换处理, 包括向移动网关申请 A口资源, 以及 通知基站控制器解除本地交换。 切换完成后, MSC-A发送关于已经解除本地交换的通知 给 MSC-B, MSC-B根据该关于已经解除本地交换的通知解除本地交换, 并返回确认消息。 当然, MSC-A也可以在向 MGW申请 A口资源后,再向 MSC-B发送本地交换信息请求, 即 MSC-A向移动网关申请 A口资源,若申请 A口资源成功,才发送本地交换信息请求给 MSC-B。
如果用户发生局间的基站控制器切换,需要解除本地交换时, MSC-A和 MSC-B之间的 交互和局内切换相同, 在此不在赘述, 需说明的是, 此时, MSC-A' 在进行切换前, 要 先得到 MSC-A和 MSC-B的许可。
由上可知,本实施例采用通过 MAP信令来进行 MSC之间的本地交换信息的交互, 以便 MSC可以根据完整的本地交换信息(本方和对方的本地交换信息)进行本地交换的处理, 使得在 MSC POOL组网下, 即使主被叫分别位于不同的 MSC上, 主被叫所在的 MSC也可以相 互得知对方呼叫所在的基站控制器,可以进行启动本地交换的判断以便进行本地交换的 处理, 而且, 由于可以通过 MAP信令来传递 MSC之间的本地交换信息, 所以如果呼叫在其 中一个 MSC上被监听, 或进行放音、 补充业务等操作而不能启动本地交换时, 另一个 MSC 也可以得知, 有利于本地交换的实现。进一步的, 采用 MAP信令来传递 MSC之间的本地交 换信息, 不需要对 MSC作太多的改动, 有利于实施。
实施例三、
根据实施例一所描述的方法, 本实施例将以采用中继信令在 MSC之间交换本地交换 信息来实现本地交换为例作详细说明。 方案如下:
1、 主被叫 MSC之间通过中继信令来进行本地交换信息的交互。
一方 MSC使用中继信令向对方 MSC发送本方的本地交换信息,包括本方呼叫腿所在的 基站控制器信令点信息和 /或本地交换能力信息等。另一方 MSC接收到对方本地交换相关 信息后, 保存接收到的对方 MSC的本地交换信息, 使用中继信令向对方返回本方的本地 交换信息。 其中, 若在呼叫过程中, 一方 MSC的本地交换信息发生了变化, 还需要将发 生了变化的本地交换信息发送给另一方 MSC, 以保证主被叫 MSC都能够及时充分地了解对 方的本地交换信息, 以便主被叫 MSC可以根据完整的本地交换信息, 即两个 MSC内的本地 交换信息进行本地交换的处理。
2、上面所说的可以用来传送本地交换信息的中继信令,可以使用中继信令类型为: 与承载无关的呼叫控制协议(BICC, Bearer Independent Call Control Protocol ) , 或会话发起协议(SIP, Session Initiation Protocol ) , 或综合业务数字网用户部分
( ISUP, Integrated Services Digital Network User Part ) 等中继信令来实现, 也 可以通过扩展现有的中继信令来实现, 比如: 可以扩展现有的 BICC消息的信息请求(INR, Information Request )和信息(INF, Information) , 也可以扩展现有的 ISUP消息的 INR、 INF;
其中, SIP信令可以使用 SIP-I信令, 另外, 可以使用 INFO (信息, Information) 来携带扩展的 ISUP消息的 INR, 使用 200 0K (一种响应消息)来携带扩展的 ISUP消息的 INF, 从而实现在主被叫 MSC之间来传递本地交换信息。
扩展后的 INR、 INF可以携带如下信息:
( 1 )本局内呼叫方所在的基站控制器信令点信息。
(2)本地交换指示, 可以用来承载第一移动交换中心或第二移动交换中心的本局 内呼叫方的本地交换能力信息。 例如, 可以包括如下指示类型:
LCLS建立请求; LCLS建立允许; LCLS建立拒绝; LCLS解除请求; LCLS解除允许; LCLS 解除拒绝; LCLS禁止指示; LCLS允许指示; LCLS建立指示; LCLS解除指示;
( 3)本局内呼叫对应的 Call-ID。 MSC和基站控制器之间使用 Call-ID来标识一个呼 叫腿。
(4)本局内的 A口承载信息。基站控制器在解除本地交换时, 需要使用两个呼叫腿 的 A口承载信息。另外, 除了上面所说的通过扩展中继信令来实现在主被叫 MSC之间进行 本地交换信息的交互之外, 也可以通过新增中继信令来实现在主被叫 MSC之间进行本地 交换信息的交互。 比如, 新增 BICC消息的 LCLS Request, LCLS information (需说明的 是, 此处的信令名称仅仅是例子, 应当理解的是, 也可以为其它的信令名称) ; 或者新 增 ISUP消息 LCLS Request, LCLS information, 等等。 其中, SIP信令可以使用 SIP-I信 令, 另外, 可以使用 INF0来携带新增的 ISUP消息的 LCLS Request, 可以使用 200 0K来携 带新增的 ISUP消息的 LCLS information, 从而实现在主被叫 MSC之间来传递本地交换信 息。
为了描述方便, 在本发明实施例中, 将以扩展 SIP信令为例进行说明。
以下将通过几个具体的场景对该方案进行详细说明。为了描述方便, 以下均假设主 叫终端为 MS-A, 主叫 MSC为 MSC-A, 被叫终端为 MS_B, 被叫 MSC为 MSC_B。
(一)场景一: 呼叫建立过程
呼叫建立过程中,主被叫 MSC,即 MSC-A和 MSC-B通过扩展的 SIP信令来传递双方的本 地交互信息, 其中, 可以使用 INF0来携带扩展的 ISUP消息的 INR, 使用 200 0K来携带扩 展的 ISUP消息的 INF。 如图 5所示, 具体流程可以如下:
A30K MS-A发送业务请求(CM Service Req)给 MSC-A; A302、 MSC-A对 MS-A进行鉴权和加密处理, 比如, MSC-A与 MS-A之间进行 Authent i cat e&Chiper消息的交互;
A303、 MS-A发送建立 (SETUP ) 消息给 MSC_A, MSC-A返回呼叫进行消息 (Cal l Proceeding)给 MS-A;
A304、 MSC-A向移动网关发送建立请求 (ADD_REQ ) , 移动网关返回建立响应
(ADD—REPLY)给 MSC- A;
A305、 MSC-A发送指配请求 (ASS_REQ) 给基站控制器, 基站控制器发送指配命令 (ASS_CMD )给 MS-A, MS-A返回指配完成 (ASS_C0MP) 给基站控制器, 基站控制器返回 指配响应(ASS_RSP)给 MSC-A;
A306、 MSC-A发送路由信息请求给 HLR, 请求 MS_B的路由信息;
A307、 HLR向 MSC-B发送漫游号码请求以获取被叫漫游号码;
A308、 MSC-B返回漫游号码响应给 HLR;
A309、 HLR返回路由信息响应给 MSC-A;
A310、 MSC-A再次向移动网关发送建立请求, 移动网关返回建立响应给 MSC-A; A31 K MSC-A发送初始地址消息(IAM)给 MSC_B, MSC-B发送寻呼(Page )给基站控 制器, 基站控制器发送寻呼给 MS-B, MS-B可以返回寻呼响应给基站控制器, 基站控制器 接收到该寻呼响应(Page rsp)后, 可以发送寻呼响应给 MSC-B;
A312、 MSC-B对 MS-B进行鉴权和加密处理, 比如, MSC-B与 MS_B之间进行 Authenticate&Chiper消息的交互; 同时, MSC-B向移动网关发送建立请求, 移动网关可 以返回建立响应给 MSC-B ; MSC-B发送建立消息给 MS-B, MS_B返回呼叫确认 (Cal l Confrimed)给 MSC-B;
A313、 MSC-B向移动网关再次发送建立请求, 移动网关可以返回建立响应给 MSC-B;
A314、 MSC-B发送指配请求给基站控制器, 基站控制器发送指配命令给 MS-B, MS-B 返回指配完成给基站控制器, 基站控制器返回指配响应给 MSC-B;
A315、 MS-B可以发送振铃消息 (ALERT)给 MSC_B, MSC-B发送地址完成消息 (ACM) 给 MSC-A, MSC-A发送振铃消息给 MS-A, 此后, MS-B发送连接消息 (CONNECT)给 MSC_B, MSC-B可以返回连接确认(C0N ECT_ACK)给 MS_B, MSC-B发送应答消息(ANM)给 MSC_A, MSC-A发送连接消息给 MS-A, MS-A可以返回连接确认消息给 MSC-A; 至此, MS-A与 MS-B的 呼叫建立完成。 A316、 MSC-B发送 INF0[INR]消息给 MSC_A,该 INF0[INR]消息中携带 MS_B所在的基站 控制器信令点信息和 MSC-B的本地交换能力信息, 还可以携带 MS-B的 Call-ID;
A317、 MSC-A判断本地交换启动条件是否具备, 若具备, 则启动本地交换, 即执行 步骤 A318;
例如,根据 MS-A所在的基站控制器信令点信息和 MS-B所在的基站控制器信令点信息 确定双方呼叫是否属于同一个基站控制器;
若为同一个基站控制器,则在根据 MSC-A的本地交换能力信息和 MSC-B的本地交换能 力信息确定双方都具备启动本地交换的能力 (比如主被叫编解码相同, 被叫 BSC支持本 地交换, 被叫用户没有被监听等) 时, 通知 MS-A所在的基站控制器启动本地交换(步骤 A318 ) , 并通知移动网关释放 MS-A的 A口资源 (步骤 A319) ; 如果确定本局不具备启动 本地交换的能力, 则在返回给 MSC-B的 200 0K[INF]消息中指示不允许本地交换, MSC-B 接收到该 200 0K[INF] 消息后, 如果该 200 0K[INF]消息中指示不允许本地交换, 则不 会启动本地交换。
若 MSC-A虽然没有启动本地交换的限制, 但 MS-A和 MS-B不属于同一个基站控制器, 则直接给 MSC-B返回 200 0K[INF] 消息, 携带 MS_A的基站控制器信令点信息及相应的 Call- ID。
在本实施例中,假设 MS-A和 MS-B均属于同一个基站控制器,具体可以属于同一个基 站控制器, 且 MSC-A和 MSC-B都具备启动本地交换的能力, 于是, MSC-A在接收到 MSC-B发 送的 200 0K[INF] 消息后, 启动本地交换, 即执行步骤 A318;
A318、 MSC-A发送本地交换命令 (LOCAL SWITCH COMMAND) 给基站控制器以启动本 地交换, 基站控制器返回本地交换完成消息 (LOCAL SWITCH C0MP) 给 MSC_A, MSC-A返 回 200 OK [INF]消息给 MSC-B, 该 200 0K[INF]消息中携带 MS_A的基站控制器信令点信息 及相应的 Call-ID, 并指示本地交换已经启动;
需说明的是,如果基站控制器启动本地交换失败,则 MSC-A向 MSC-B返回 200 0K[INF] 消息时, 在 200 0K[INF]消息中携带 MS-A所在的基站控制器信令点信息, 并指示本地交 换没有启动。
A319、 MSC-A发送删除请求 (SUB_REQ) 给移动网关, 以释放 MS-A的 A口资源; 移动 网关可以返回删除响应 (SUB_REPLY) 给 MSC-A; A320、 MSC-B接收到 MSC-A返回 200 0K[INF]消息后, 如果 200 0K[INF]消息中指示本 地交换已经启动, 则发送删除请求给移动网关, 以释放 MS-B的 A口资源; 移动网关可以 返回删除响应给 MSC-B; 如果 200 0K[INF]消息中指示本地交换没有启动, 则不动作。
至此, 本地交换建立完成。 需说明的是, 主被叫 MSC之间, 即 MSC-A和 MSC-B之间不 需要保持 MAP连接; 另外, 本地交换启动后, MSC-A与 MSC-B之间的中继资源不释放, 因 为如果释放了, 后续就无法对该已经建立的本地交换进行解除了。
当然, INF0[INR]消息也可以由 MSC-A首先发起, 实现方式与前面所描述的由 MSC-B 首先发起的类似, 即 MSC-B接收到 MSC-A发送的 INF0[INR]消息后, MSC-B根据 MS_A所在的 基站控制器信令点信息和 MS-B所在的基站控制器信令点信息确定双方呼叫是否属于同 一个基站控制器; 若为同一个基站控制器, 则在根据本方的本地交换能力信息和对方的 本地交换能力信息确定双方都具备启动本地交换的能力(比如主被叫编解码相同, 被叫
BSC支持本地交换, 被叫用户没有被监听等) 时, 通知 MS-B所在的基站控制器启动本地 交换, 并通知移动网关释放 MS-B的 A口资源, 此外, MSC-B还可以返回 200 0K[INF]消息 给 MSC-A, 该 200 0K[INF]消息中携带 MS-B的基站控制器信令点信息及相应的 Call-ID, 并指示本地交换已经启动;如果确定本局不具备启动本地交换的能力,则在返回给 MSC-A 的 200 0K[INF]消息中指示不允许本地交换, MSC-A接收到该 200 0K[INF]消息后, 如果 该 200 0K[INF]消息中指示不允许本地交换, 则不会启动本地交换。 若 MSC-B虽然没有启 动本地交换的限制, 但 MS-A和 MS-B不属于同一个基站控制器, 则直接给 MSC-A返回 200 0K[INF]消息, 携带 MS-B的基站控制器信令点信息及相应的 Call_ID。
另外, 需说明的是, 除了上面所描述的让一方 MSC判断和启动本地交换之外, 也可 以由主被叫 MSC各自判断和启动本地交换。 例如, 在步骤 A316之后, MSC-A可以返回 200 0K[INF]消息给 MSC-B,然后, MSC-A和 MSC-B分别判断自身的本地交换启动条件是否具备, 若具备, 则 MSC-A和 MSC-B分别启动本地交换, 即一方面, MSC-A通知 MS-A所在的基站控 制器启动本地交换, 并通知移动网关释放 MS-A的 A口资源; 另一方面 MSC-B也通知 MS-B所 在的基站控制器启动本地交换, 并通知移动网关释放 MS-B的 A口资源。
在呼叫过程中, MSC-A与 MSC-B之间可以通过 INF0[INR]消息和 200 0K[INF]消息来更 新呼叫的本地交换能力信息, 即当呼叫的本地交换能力信息发生变化时, MSC-A与 MSC-B 之间要动态地进行交互。 比如, 在呼叫发起时, 由于 MS-A与 MS-B不在同一个基站控制器 而没有启动本地交换, 但没有其他本地交换的限制, 在呼叫进行中, 如果 MS-A的用户被 监听或发生补充业务, 则 MSC-A需要通知 MSC-B该呼叫不再具备本地交换能力; 如果后续 监听解除或补充业务结束, 则 MSC-A需要通知 MSC-B该呼叫又具备了本地交换能力。 当一 个呼叫不具备本地交换能力时, 即使主被叫用户属于同一个基站控制器, 也不会启动本 地交换。
(二)场景二: 在本地交换建立后, MSC要求解除本地交换
MSC-A发生补充业务等操作需要解除本地交换时,若 MSC-A根据两方的本地交换信息 向移动网关申请 A口资源, 若申请 A口资源成功, 则向 MSC-B发送 INF0[INR]消息, 通知 MSC-B并要求解除本地交换; MSC-B收到该 INF0[INR]消息后, 向移动网关申请 A口资源, 如可以申请到 A口资源, 则向 MSC-A返回 200 0K[INF]消息, 并在该 200 0K[INF]消息中携 带相应的 A口资源, MSC-A收到 MSC-B的 200 0K[INF]消息后, 指示基站控制器解除本地交 换, 本地交换解除后, MSC-A再通过 INF0[INR]消息告知 MSC-B本地交换已解除。 需说明 的是, 若 MSC-A要求基站控制器解除本地交换失败, MSC-A也要通过 INF0[INR]消息知会 MSC-B, 以便 MSC-A和 MSC-B释放已经申请的 A口资源。
当然,除了上面所描述的由一方的 MSC, 比如由 MSC-A要求基站控制器解除本地交换 之外, 也可以由双方的 MSC, 即由 MSC-A和 MSC-B分别要求基站控制器解除本地交换。 例 如, 可以如下:
MSC-A发生补充业务等操作需要解除本地交换时,若 MSC-A根据两方的本地交换信息 向移动网关申请 A口资源, 若申请 A口资源成功, 则向 MSC-B发送 INF0[INR]消息, 通知 MSC-B并要求解除本地交换; MSC-B收到该 INF0[INR]消息后,向移动网关申请到 A口资源, 并向 MSC-A返回 200 0K[INF]消息, 该 200 0K[INF]消息中不需携带 A口资源信息, 同时指 示基站控制器解除本地交换,并返回 200 0K[INF]消息告知 MSC-A本地交换已解除, MSC-A 收到 200 0K[INF]消息后, 指示基站控制器解除本地交换。
当然, MSC-A也可以直接向 MSC-B请求解除本地交换, MSC-B接收到该请求后, 向移 动网关申请 A口资源, 若 MSC-B申请 A口资源成功, 则返回本地交换确认消息告知 MSC-A, MSC-A接收到该本地交换确认消息后, MSC-A向移动网关申请 A口资源, 若 MSC-A申请 A口 资源不成功, 则不解除本地交换; 若 MSC-A申请成功, 则指示基站控制器解除本地交换; 若 MSC-B申请 A口资源不成功, 则会向 MSC-A返回拒绝。 MSC-A收到拒绝消息后, 不再解 除本地交换。 其中, 对于不同的启动解除本地交换的原因, MSC-A将会做不同的处理, 比如, 如果是要进行补充业务, 则 MSC-A拒绝补充业务; 如果是要进行合法监听, 则可 以释放呼叫或者不进行监听。
(三)场景三: 切换过程中建立本地交换 在呼叫过程中没有建立本地交换,但是经过切换之后,主被叫双方所在的基站控制 器属于同一个基站控制器, 且双方都具备启动本地交换的能力, 那么, 此时需要建立本 地交换。也就是说, 一个用户切换到另一用户所在基站控制器, 且本地交换建立条件都 已具备时, 需要建立本地交换。
下面将举例说明局间呼叫流程中,如果一方发生基站控制器间的切换,本地交换的 建立方法。 其中, 基站控制器间的切换包括两种, 一种为局内的基站控制器间的切换, 另一种为局间的基站控制器间的切换。假设切换前的基站控制器为源基站控制器, 切换 后的基站控制器为目标基站控制器, 源基站控制器为 BSC1 , 目标基站控制器为 BSC2; 首先, 描述在局间呼叫流程中, 主叫发生局内的基站控制器间切换的场景, 如图 6 所示, 具体流程如下:
B30K BSC1发送请求切换消息 (Handover Required)给 MSC-A, MSC-A发送建立请 求给移动网关, 移动网关可以返回建立响应给 MSC-A;
B302、 MSC-A发送切换请求(Handover Request )给 BSC2, 该切换请求中携带本地 交换指示(LS ind) , 比如指示 BSC2启动本地交换或解除本地交换等等;
例如, MSC-A可以根据在呼叫建立阶段和呼叫过程中 MSC-A与 MSC-B之间交互的相关 信息,比如 MSC-B的本地交换能力信息判断 MSC-B是否具备启动本地交换的能力,若具备, 则 MSC-A发送切换请求给 BSC2时, 可以在该切换请求中指示 BSC2启动本地交换, 并携带 切换后的呼叫的 Call-ID; 若不具备, 则在发给 BSC2的切换请求消息中, 不会指示启动 本地交换;
BSC2可以返回切换请求确认消息 (Handover Request ack)给 MSC-A, 该切换请求 确认消息中携带本地交换确认信息 (LS ack) ;
B303、 MSC-A发送切换命令(Handover Command)给 BSC1 ;
B304、 BSC2发送发现切换消息 (Handover Detect ) 给 MSC_A, 以及发送切换完成 (Handover Complete)给 MSC-A;
B305、 MSC-A发送清除命令(CI ear Command)给 BSC1, BSC1返回清除完成消息(Clear
Complete)给 MSC- A;
B306、 MSC-A发送 INFO [INR]消息给 MSC-B, 以启动本地交换,该 INFO [INR]消息携带 主叫所在的基站控制器信令点信息、 相应的 Call-ID、 以及本地交换已经启动的指示; MSC-B可以返回 200 0K[INF]消息给 MSC-A, 此后, 若具备启动本地交换的条件, 则 MSC-A 通知 MS-A所在的基站控制器启动本地交换, 并通知移动网关释放 MS-A的 A口资源; 此时, MSC-B也通知 MS-B所在的基站控制器启动本地交换, 并通知移动网关释放 MS-B的 A口资 源。 建立本地交换的方法具体可参见场景一中的相关描述, 在此不再赘述。
下面描述在局间呼叫流程中,用户发生局间的基站控制器切换的场景,即源基站控 制器与目标基站控制器所属的 MSC不同。在此假设主叫用户发生局间的基站控制器切换, 源 MSC为 MSC-A,源 BSC为 BSC 1, 目标 MSC为 MSC_A, , 目标 BSC为 BSC2,被叫的 MSC为 MSC-B, 被叫的 BSC为 BSC2, 则如图 7所示, 具体流程如下:
C30K MSC-A接收到切换请求后, 若 MSC-A判断可以启动本地交换, 比如 MSC-A根据 本方的本地交换能力信息和对方的本地交换能力信息确定双方都具备启动本地交换的 能力, 则在发送给 MSC-A' 的切换请求中携带表示启动本地交换的指示, 以便切换完成 后, MSC-A' 根据该表示启动本地交换的指示通知移动网关释放本方的 A口资源以及通知 基站控制器启动本地交换, MSC-A' 返回的表示本地交换成功启动的切换响应给 MSC-A; 其中, 发送给 MSC-A' 的切换请求可以是准备切换请求(MAP Prepare Handover Req) ;
C302、 MSC-A' 发送切换请求给 BSC2, 该切换请求中携带本地交换指示, 比如指示 BSC2启动本地交换或解除本地交换等等, 以及携带切换后的呼叫的 Cal l-IDBSC2可以返 回切换请求确认消息给 MSC-A' , 该切换请求确认消息中携带本地交换确认信息;
C303、 MSC-A' 发送切换请求确认消息给 MSC-A,该切换请求确认消息中携带本地交 换确认信息;其中,该切换请求确认消息也可以是准备切换响应(MAP Prepare Handover Resp) ;
C304、 切换完成后, MSCA, 自行通知移动网关释放相应的 A口承载, 由 MSC-A和 /或 MSC-B通知基站控制器启动本地交换, MSC-A与 MSC-B之间的流程同用户发生局内的基站 控制器切换时的流程,例如, MSC-A发送 INF0 [INR]消息给 MSC-B, MSC-B返回 200 0K [INF] 消息给 MSC-A, 并且, MSC-B通知移动网关释放 A口资源等等, 具体客参见前面实施例, 在此不再赘述。
当然, 除了上面所描述的由 MSC-A判断是否可以启动本地交换之外, 也可以由 MSC-A' 来进行判断, 如下:
在局间切换完成后,无论是否启动了本地交换, MSC-A都要给 MSC-A' 发送本地交换 信息, 例如通知 MSC-A' 本呼叫的本地交换能力, 以及 MSC-B所在的基站控制器信令点信 息和 Cal l-ID, 以便目标移动交换中心根据本方的本地交换信息和对方的本地交换信息 进行本地交换的处理。另外,在后续呼叫过程中,若该呼叫的本地交换能力信息或 MSC-B 所在的基站控制器信令点信息发生变化时, MSCA也都要通知 MSCA' 。 下面再描述局间切换完成后,用户再发生局内切换时,本地交换的检查和启动流程。 即, 如果局间切换后, 主被叫并不在一个基站控制器上而没有启动本地交换, 后续用户 在 MSC-A' 内发生局内跨基站控制器切换, 如果切换到了对方用户所在的基站控制器, 则此时可以启动本地交换。
MSC-A' 收到切换请求后, 首先发送 INF0 [INR]消息询问 MSC-A是否可以启动本地交 换, 该 INF0 [INR]消息中携带切换目标 BSC信息, 若 MSC-A判断可以启动本地交换, 则给 MSC-A' 返回允许启动本地交换的指示, MSC-A' 继续进行后续的切换和启动本地交换操 作, 具体可参见前面实施例, 切换完成后, MSC-A' 要知会 MSC-A已经启动了本地交换。 MSC-A需要向 MSC-B传递 MSC-A' 的本地交换信息。
当然,也可以由 MSC-A' 自行判断是否可以启动本地交换,即 MSC-A' 收到切换请求 后, 自行判断是否可以启动本地交换, 如果可以启动则在切换流程中启动本地交换, 切 换完成后, MSC-A' 通知 MSC-A已经启动了本地交换, MSC-A需要向 MSC-B传递 MSC-A' 的 本地交换信息。
需说明的是, 在 MSC P00L组网下, 呼叫的一方发生跨基站控制器切换后, 即使没有 启动本地交换, 该呼叫所在的 MSC也要向对方 MSC通知新的基站控制器信息。
(四)场景四: 切换过程中解除本地交换
首先,描述在局间呼叫流程中,用户发生局内的基站控制器切换时,本地交换解除 的流程。 如下:
MSC-A接收切换请求, 根据接收到切换请求判断需要解除本地交换时, 发送本地交 换解除请求给 MSC-B, 比如发送 INF0 [INR]消息给 MSC-B, MSC-B接收到后, 可以根据该本 地交换解除请求判断是否可以解除本地交换, 若不能解除, 则向 MSC-A返回表示拒绝的 消息, MSC-A接收到该表示拒绝的消息后, 拒绝切换; 若可以解除, 则向移动网关申请 A 口资源, 并向 MSC-A返回表示成功申请了 A口资源的确认消息, 比如向 MSC-A返回本地交 换信息确认消息, 其中, 该本地交换信息确认消息中携带 MSC-B向移动网关申请的 A口资 源, MSC-A接收到该确认消息后, 向移动网关申请 A口资源, 通知基站控制器解除本地交 换, 并进行后面的切换处理, 在发送给源 BSC的切换命令中携带解除本地交换的指示, 以及 MSC-B申请的 A口资源信息, 在切换完成后, 通知 MSC-B本地交换已经解除。
当然, MSC-A也可以在向 MGW申请 A口资源后,再向 MSC-B发送 INFO [ INR]消息,即 MSC-A 向移动网关申请 A口资源, 若申请 A口资源成功, 才发送 INFO [INR]消息给 MSC_B。 另外,除了上面所描述的只由一方的 MSC, 比如 MSC-A来指示基站控制器解除本地交 换之外, 也可以由双方的 MSC, 比如 MSC-A和 MSC-B各自指示 BSC解除本地交换。 如下:
MSC-A接收切换请求, 根据接收到的切换请求判断需要解除本地交换时, 发送本地 交换解除请求给 MSC-B , 比如发送 INF0 [INR]消息给 MSC-B , MSC-B接收到后, 根据该 INF0 [INR]消息判断是否允许解除本地交换, 若不能解除, 则向 MSC-A返回表示拒绝的消 息, MSC-A接收到该表示拒绝的消息后, 拒绝切换; 若可以解除, 则向移动网关申请 A口 资源, 并返回本地交换解除允许指示给 MSC-A (不携带申请的 A口资源信息) , MSC-A根 据本地交换解除允许指示进行后面的切换处理, 包括向移动网关申请 A口资源, 以及通 知基站控制器解除本地交换。 切换完成后, MSC-A发送关于已经解除本地交换的通知给 MSC-B, MSC-B根据该关于已经解除本地交换的通知解除本地交换, 并返回 200 0K [INF] 消息。
当然, MSC-A也可以在向 MGW申请 A口资源后,再向 MSC-B发送 INFO [ INR]消息,即 MSC-A 向移动网关申请 A口资源, 若申请 A口资源成功, 才发送 INFO [INR]消息给 MSC_B。
如果用户发生局间的基站控制器切换,需要解除本地交换时, MSC-A和 MSC-B之间的 交互和局内切换相同, 在此不在赘述, 需说明的是, 此时, MSC-A' 在进行切换前, 要 先得到 MSC-A和 MSC-B的许可。
由上可知, 本实施例采用通过中继信令来进行 MSC之间的本地交换信息的交互, 以 便 MSC可以根据完整的本地交换信息 (本方和对方的本地交换信息)进行本地交换的处 理, 使得在 MSC POOL组网下, 即使主被叫分别位于不同的 MSC上, 主被叫所在的 MSC也可 以相互得知对方呼叫所在的基站控制器,可以进行启动本地交换的判断以便进行本地交 换的处理, 而且, 由于可以通过中继信令来传递 MSC之间的本地交换信息, 所以如果呼 叫在其中一个 MSC上被监听, 或进行放音、 补充业务等操作而不能启动本地交换时, 另 一个 MSC也可以得知, 有利于本地交换的实现。进一步的, 采用中继信令来传递 MSC之间 的本地交换信息, 相对与采用 MAP信令来传递 MSC之间的本地交换信息来说, 虽然需要对 MSC作较多的改动, 但无需对 HLR进行改动(采用 MAP信令来传递 MSC之间的本地交换信息 则需要改动 MSC和 HLR) 。
实施例四、
为了更好地实施以上方法,本发明实施例还相应地提供一种移动交换中心,即 MSC, 如图 8所示, 该 MSC包括获取单元 401和处理单元 402 ; 获取单元 401, 用于获取对方呼叫的 MSC发送的对方的本地交换信息; 例如, 当呼叫 双方分别在第一移动交换中心与第二移动交换中心时,第一移动交换中心获取第二移动 交换中心发送的第二呼叫方的本地交换信息, 具体可以通过 MAP信令或中继信令获取对 方呼叫的 MSC发送的对方的本地交换信息, 其中, 本地交换信息可以包括基站控制器的 信息, 比如基站控制器信令点信息, 还可以包括本地交换能力信息等信息, 当然, 还包 括建立和解除本地交换所需使用的其它信息, 例如呼叫的 Call-ID和 A口承载信息等信 息。 其中, 基站控制器信令点信息指的是一方呼叫腿所在的基站控制器, 而本地交换能 力信息是指呼叫是否被监听, 或是否在进行放音、 补充业务等操作。
处理单元 402,用于根据本方的本地交换信息和获取单元 401获取到的对方的本地交 换信息进行本地交换的处理, 即根据第一呼叫方的本地交换信息, 以及所述第二呼叫方 的本地交换信息进行本地交换的处理, 其中, 所述第一呼叫方的本地交换信息或第二呼 叫方的本地交换信息分别包括相应呼叫方所在的基站控制器的信息。
其中, 如图 8所示, 所述处理单元 402可以包括第一判断子单元 4021和通知子单元
4023;
第一判断子单元 4021, 用于根据本方的本地交换信息和获取单元 401获取到的对方 的本地交换信息判断双方呼叫是否属于同一个基站控制器, 即根据第一呼叫方的基站控 制器信息和获取单元 401获取到的第二呼叫方的基站控制器信息判断双方呼叫是否属于 同一个基站控制器;
通知子单元 4023,用于当第一判断子单元 4021确定双方呼叫属于同一个基站控制器 时, 通知基站控制器启动本地交换, 并通知移动网关释放本方的 A口资源, 即第一呼叫 方的 A口资源。
其中, 如图 8所示, 所述处理单元 402还可以包括第二判断子单元 4022;
第二判断子单元 4022, 用于根据本方的本地交换信息和获取单元 401获取到的对方 (第二呼叫方) 的本地交换信息, 即第二呼叫方的本地交换信息判断双方是否都具备启 动本地交换的能力;
所述获取单元 401, 还用于当第一呼叫方的本地交换信息或第二呼叫方的本地交换 信息还分别包括所述相应呼叫方的本地交换能力信息时,获取所述第二呼叫方的本地交 换能力信息; 所述通知子单元 4023,用于当第一判断子单元 4021确定双方呼叫属于同一个基站控 制器, 且第二判断子单元 4022确定双方都具备启动本地交换的能力时, 通知基站控制器 启动本地交换, 并通知移动网关释放本方的 A口资源, 即第一呼叫方的 A口资源。
如图 8所示, 处理单元 402还可以包括第一发送子单元 4024;
第一发送子单元 4024, 用于发送本地交换建立响应消息给对方呼叫的 MSC如第二移 动交换中心, 以便对方呼叫的 MSC如第二移动交换中心根据该本地交换建立响应消息通 知移动网关释放对方的 A口资源如第二呼叫的 A口资源。
如图 8所示, 处理单元 402还可以包括申请子单元 4025 ;
申请子单元 4025, 用于根据本方的本地交换信息和获取单元 401获取到的对方的本 地交换信息向移动网关申请本方的 A口资源, 比如根据第一呼叫方的本地交换信息和获 取单元获取到的第二呼叫方的本地交换信息向移动网关申请本方的 A口资源;
所述第一发送子单元 4024, 还用于在申请子单元 4025申请本方的 A口资源成功后, 发送本地交换解除请求给对方呼叫的 MSC如第二移动交换中心, 以便对方呼叫的 MSC如第 二移动交换中心根据该本地交换解除请求向移动网关申请对方的 A口资源, 即第二呼叫 方的 A口资源;
所述通知子单元 4023, 还用于在接收到对方呼叫的 MSC返回的表示成功申请了对方 (第二呼叫方) 的 A口资源的确认消息后, 通知基站控制器解除本地交换。
如图 8所示, 处理单元 402还可以包括切换处理子单元 4026 ;
切换处理子单元 4026,用于当第二判断子单元 4022确定双方都具备启动本地交换的 能力时, 在发送给目标 MSC的切换请求中携带表示启动本地交换的指示, 以便切换完成 后, 目标 MSC根据该表示启动本地交换的指示通知移动网关释放本方的 A口资源以及通知 基站控制器启动本地交换, 然后接收目标移动交换中心返回的表示本地交换成功启动的 切换响应。
如图 8所示, 处理单元 402还可以第二发送子单元 4027 ;
第二发送子单元 4027, 用于分别发送本方的本地交换信息和获取单元 401获取到的 对方的本地交换信息给目标 MSC (即本方的本地交换信息和对方的本地交换信息可以不 同时发送) , 以便目标 MSC根据本方的本地交换信息和对方的本地交换信息进行本地交 换的处理。
以上各个单元的具体实施可参见前面实施例, 在此不在赘述。 由上可知, 本实施例的 MSC的获取单元 401可以获取对方呼叫的 MSC发送的对方的本 地交换信息, 然后由处理单元 402根据本方的本地交换信息和对方的本地交换信息进行 本地交换的处理, 使得在 MSC POOL组网下, 即使主被叫分别位于不同的 MSC上, 主被叫 所在的 MSC也可以相互得知对方呼叫所在的基站控制器, 可以进行启动本地交换的判断 以便进行本地交换的处理, 而且, 由于获取单元 401可以获取对方 MSC发送的对方的本地 交换信息, 所以如果呼叫在其中一个 MSC上被监听, 或进行放音、 补充业务等操作而不 能启动本地交换时, 另一个 MSC也可以得知, 有利于本地交换的实现。
实施例五、
相应地,本发明实施例还相应地提供一种通信系统,包括本发明实施例提供的任意 一种 MSC, 如图 9所示, 该通信系统具体可以包括第一移动交换中心(第一 MSC) 501和第 二移动交换中心 (第二 MSC) 502;
第一移动交换中心 501,用于当呼叫双方分别在第一移动交换中心 501与第二移动交 换中心 502时, 获取第二移动交换中心 502发送的第二呼叫方的本地交换信息, 根据所述 第一呼叫方的本地交换信息, 以及所述第二呼叫方的本地交换信息进行本地交换的处 理, 其中, 所述第一呼叫方的本地交换信息或第二呼叫方的本地交换信息分别包括相应 呼叫方所在的基站控制器的信息;
第二移动交换中心 502, 用于发送对方的本地交换信息给第一移动交换中心 501。 所述第二移动交换中心 502,还用于通过 MAP信令或中继信令发送第二呼叫方的本地 交换信息给第一移动交换中心 501。 其中, 本地交换信息除了可以包括基站控制器的信 息, 比如基站控制器信令点信息之外, 还可以包括本地交换能力信息等信息, 当然, 还 包括建立和解除本地交换所需使用的其它信息,例如呼叫的 Cal l-ID和 A口承载信息等信 息。 其中, 基站控制器信令点信息指的是一方呼叫腿所在的基站控制器, 而本地交换能 力信息是指呼叫是否被监听, 或是否在进行放音、 补充业务等操作。
第一移动交换中心 501和第二移动交换中心 502的交互具体可参见前面实施例,在此 不再赘述。
由上可知,本实施例的通信系统中的 MSC可以获取对方呼叫的 MSC发送的对方的本地 交换信息, 然后根据本方的本地交换信息和对方的本地交换信息进行本地交换的处理, 使得在 MSC POOL组网下, 即使主被叫分别位于不同的 MSC上, 主被叫所在的 MSC也可以相 互得知对方呼叫所在的基站控制器,可以进行启动本地交换的判断以便进行本地交换的 处理, 而且, 由于 MSC可以获取对方 MSC发送的对方的本地交换信息, 所以如果呼叫在其 中一个 MSC上被监听, 或进行放音、 补充业务等操作而不能启动本地交换时, 另一个 MSC 也可以得知, 有利于本地交换的实现。 其中, 具体可以通过 MAP信令或中继信令来传递 MSC之间的本地交换信息(详细的实施方式可参见前面实施例二和实施例三) , 采用 MAP 信令来传递 MSC之间的本地交换信息时, 需要对 MSC和 HLR都进行改造, 但对 MSC的改变较 少, 采用中继信令来传递 MSC之间的本地交换信息时, 只需对 MSC进行改造 (无需改造 HLR) , 但对 MSC的改变较多。 至于具体采用哪种方式来传递 MSC之间的本地交换信息, 可以根据运营商的策略来选择。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步骤是可以 通过程序来指令相关的硬件来完成, 该程序可以存储于一计算机可读存储介质中, 存储 介质可以包括: 只读存储器(ROM, Read Only Memory )、 随机存取记忆体(RAM, Random Access Memory ) 、 磁盘或光盘等。
以上对本发明实施例所提供的一种本地交换的实现方法、移动交换中心和通信系统 进行了详细介绍, 本文中应用了具体个例对本发明的原理及实施方式进行了阐述, 以上 实施例的说明只是用于帮助理解本发明的方法及其核心思想; 同时, 对于本领域的一般 技术人员, 依据本发明的思想, 在具体实施方式及应用范围上均会有改变之处, 综上所 述, 本说明书内容不应理解为对本发明的限制。

Claims

权利要求
1、 一种本地交换的实现方法, 其特征在于, 包括:
当呼叫双方分别在第一移动交换中心与第二移动交换中心时,第一呼叫方所在的第 一移动交换中心获取第二移动交换中心发送的第二呼叫方的本地交换信息;
第一移动交换中心根据第一呼叫方的本地交换信息,以及第二呼叫方的本地交换信 息进行本地交换的处理, 其中, 第一呼叫方的本地交换信息或第二呼叫方的本地交换信 息分别包括相应呼叫方所在的基站控制器的信息。
2、根据权利要求 1所述的方法, 其特征在于, 所述第一移动交换中心获取第二移动 交换中心发送的第二呼叫方的本地交换信息包括:
第一移动交换中心获取第二移动交换中心通过移动应用部分 MAP信令或中继信令发 送的第二呼叫方的本地交换信息。
3、根据权利要求 2所述的方法, 其特征在于, 所述第一移动交换中心获取第二移动 交换中心通过 MAP信令发送的第二呼叫方的本地交换信息之前, 还包括:
第一移动交换中心发送本方的地址和本方呼叫的国际移动用户标识码 B1SI给第二 移动交换中心;
所述第一移动交换中心获取第二移动交换中心通过移动应用部分 MAP信令发送的第 二呼叫方的本地交换信息包括:获取第二移动交换中心根据第一移动交换中心的地址发 送的通过 MAP信令承载的第二呼叫方的本地交换信息。
4、 根据权利要求 3所述的方法, 其特征在于, 通过 MAP信令承载本地交换信息为: 扩展现有的 MAP信令的路由信息请求 SRI和漫游号码请求 PRN或者新增 MAP信令来承 载本地交换信息。
5、根据权利要求 2所述的方法, 其特征在于, 所述第一移动交换中心获取第二移动 交换中心通过中继信令发送的第二呼叫方的本地交换信息包括:
通过扩展与承载无关的呼叫控制协议 BICC消息的信息请求 INR或信息 INF信元,或者 扩展综合业务数字网用户部分 ISUP消息的 INR或 INF信元,或者新增中继信令来承载本地 交换信息。
6、根据权利要求 1所述的方法, 其特征在于, 所述第一移动交换中心根据第一呼叫 方的本地交换信息, 以及第二呼叫方的本地交换信息进行本地交换的处理包括: 第一移动交换中心根据本方的基站控制器信息和第二呼叫方的基站控制器信息确 定双方呼叫属于同一个基站控制器时, 通知所述基站控制器启动本地交换, 并通知移动 网关释放本方的 A口资源。
7、根据权利要求 6所述的方法, 其特征在于, 所述基站控制器信息为基站控制器信 令点的信息;
则第一移动交换中心根据本方的基站控制器信令点的信息和第二呼叫方的基站控 制器信令点的信息确定双方呼叫是否属于同一个基站控制器。
8、根据权利要求 1所述的方法, 其特征在于, 所述第一呼叫方的本地交换信息或第 二呼叫方的本地交换信息还分别包括以下任意组合:
相应呼叫方的本地交换能力信息;
相应呼叫方的呼叫标识 Call-ID;
相应呼叫方的 A口承载信息。
9、根据权利要求 8所述的方法, 其特征在于, 当第一呼叫方的本地交换信息或第二 呼叫方的本地交换信息还分别包括所述相应呼叫方的本地交换能力信息时,所述第一移 动交换中心根据第一呼叫方的本地交换信息, 以及所述第二呼叫方的本地交换信息进行 本地交换的处理包括:
第一移动交换中心根据本方的基站控制器信令点信息和第二移动交换中心的基站 控制器信令点信息确定双方呼叫属于同一个基站控制器,且根据自身的本地交换能力信 息和第二呼叫方的本地交换能力信息确定双方都具备启动本地交换的能力时,通知所述 基站控制器启动本地交换, 并通知移动网关释放所述第二呼叫方的 A口资源。
10、 根据权利要求 6或 9所述的方法, 其特征在于, 在通知移动网关释放本方的 A口 资源之后还包括:
发送本地交换建立响应消息给第二移动交换中心,以便第二移动交换中心根据该本 地交换建立响应消息通知移动网关释放本方的 A口资源。
11、 根据权利要求 6或 9所述的方法, 其特征在于, 在本地交换建立之后, 还包括: 第一移动交换中心根据本方的本地交换信息和第二呼叫方的本地交换信息向移动 网关申请本方的 A口资源;
当申请本方的 A口资源成功, 发送本地交换解除请求给第二移动交换中心, 以便第 二移动交换中心根据该本地交换解除请求向移动网关申请第二呼叫方的 A口资源; 在接收到第二移动交换中心返回的表示成功申请了第二呼叫方的 A口资源的确认消 息后, 通知基站控制器解除本地交换。
12、 根据权利要求 6所述的方法, 其特征在于, 所述方法还包括:
第二移动交换中心获取第一移动交换中心发送的第一呼叫方的本地交换信息; 第二移动交换中心根据本方的基站控制器信令点信息和第一呼叫方的基站控制器 信息确定双方呼叫属于同一个基站控制器, 通知所述基站控制器启动本地交换, 并通知 移动网关释放本方的 A口资源。
13、 根据权利要求 12所述的方法, 其特征在于, 在本地交换建立之后, 还包括: 第二移动交换中心根据本方的本地交换信息和第一呼叫方的本地交换信息向移动 网关申请本方的 A口资源;
当申请本方的 A口资源成功, 发送本地交换解除请求给第一移动交换中心, 以便第 一移动交换中心根据该本地交换解除请求向移动网关申请第一呼叫方的 A口资源;
在接收到第一移动交换中心返回的表示成功申请了第一呼叫方的 A口资源的确认消 息后, 通知基站控制器解除本地交换。
14、根据权利要求 6或 9或 12所述的方法,其特征在于,当发生局间切换时,还包括: 第一移动交换中心或第二移动交换中心根据本方的本地交换能力信息和第二呼叫 方的本地交换能力信息确定双方都具备启动本地交换的能力,则在发送给目标移动交换 中心的切换请求中携带表示启动本地交换的指示, 以便切换完成后, 目标移动交换中心 根据该表示启动本地交换的指示通知移动网关释放本方的 A口资源以及通知基站控制器 启动本地交换;
接收目标移动交换中心返回的表示本地交换成功启动的切换响应。
15、 一种移动交换中心, 其特征在于, 包括:
获取单元,用于当呼叫双方分别在第一移动交换中心与第二移动交换中心时,获取 第二移动交换中心发送的第二呼叫方的本地交换信息;
处理单元,用于根据第一呼叫方的本地交换信息, 以及所述第二呼叫方的本地交换 信息进行本地交换的处理, 其中, 所述第一呼叫方的本地交换信息或第二呼叫方的本地 交换信息分别包括相应呼叫方所在的基站控制器的信息。
16、 根据权利要求 15所述的移动交换中心, 其特征在于, 所述处理单元包括: 第一判断子单元,用于根据第一呼叫方的基站控制器信息和所述获取单元获取到的 第二呼叫方的基站控制器信息判断双方呼叫是否属于同一个基站控制器; 通知子单元, 用于当所述第一判断子单元确定双方呼叫属于同一个基站控制器时, 通知基站控制器启动本地交换, 并通知移动网关释放本方的 A口资源。
17、根据权利要求 16所述的移动交换中心, 其特征在于, 所述获取单元, 还用于当 第一呼叫方的本地交换信息或第二呼叫方的本地交换信息还分别包括所述相应呼叫方 的本地交换能力信息时, 获取所述第二呼叫方的本地交换能力信息;
所述处理单元还包括:
第二判断子单元,用于根据本方的本地交换能力信息和所述获取单元获取到的第二 呼叫方的本地交换能力信息判断双方是否都具备启动本地交换的能力;
所述通知子单元,还用于在所述第二判断子单元判断双方都具备启动本地交换的能 力时, 通知基站控制器启动本地交换, 并通知移动网关释放本方的 A口资源。
18、 根据权利要求 16所述的移动交换中心, 其特征在于, 所述处理单元还包括: 第一发送子单元,用于发送本地交换建立响应消息给第二移动交换中心, 以便第二 移动交换中心根据该本地交换建立响应消息通知移动网关释放第二呼叫方的 A口资源。
19、 根据权利要求 17所述的移动交换中心, 其特征在于, 所述处理单元还包括: 申请子单元,用于根据第一呼叫方的本地交换信息和获取单元获取到的第二呼叫方 的本地交换信息向移动网关申请本方的 A口资源;
所述第一发送子单元, 还用于在申请子单元申请本方的 A口资源成功后, 发送本地 交换解除请求给第二移动交换中心, 以便第二移动交换中心根据该本地交换解除请求向 移动网关申请第二呼叫方的 A口资源;
所述通知子单元,还用于在接收到第二移动交换中心返回的表示成功申请了第二呼 叫方的 A口资源的确认消息后, 通知基站控制器解除本地交换。
20、 根据权利要求 19所述的移动交换中心, 其特征在于, 所述处理单元还包括: 切换处理子单元, 用于当第二判断子单元确定双方都具备启动本地交换的能力时, 在发送给目标移动交换中心的切换请求中携带表示启动本地交换的指示, 以便切换完成 后, 目标移动交换中心根据该表示启动本地交换的指示通知移动网关释放本方的 A口资 源以及通知基站控制器启动本地交换, 然后接收目标移动交换中心返回的表示本地交换 成功启动的切换响应。
21、 一种通信系统, 其特征在于, 包括第一移动交换中心和第二移动交换中心; 所述第一移动交换中心,用于当呼叫双方分别在第一移动交换中心与第二移动交换 中心时, 获取第二移动交换中心发送的第二呼叫方的本地交换信息, 根据所述第一呼叫 方的本地交换信息, 以及所述第二呼叫方的本地交换信息进行本地交换的处理, 其中, 所述第一呼叫方的本地交换信息或第二呼叫方的本地交换信息分别包括相应呼叫方所 在的基站控制器的信息;
所述第二移动交换中心, 用于发送本方的本地交换信息给第一移动交换中心。
22、 根据权利要求 21所述的通信系统, 其特征在于,
所述第二移动交换中心, 用于通过移动应用部分 MAP信令或中继信令发送第二呼叫 方的本地交换信息给第一移动交换中心。
PCT/CN2010/072549 2009-05-31 2010-05-10 一种本地交换的实现方法、移动交换中心和通信系统 WO2010139225A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
RU2011153729/08A RU2487503C1 (ru) 2009-05-31 2010-05-10 Способ осуществления переключения на местный прием, центр коммутации мобильной связи и система связи

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910145718.9 2009-05-31
CN2009101457189A CN101902824B (zh) 2009-05-31 2009-05-31 一种本地交换的实现方法、移动交换中心和通信系统

Publications (1)

Publication Number Publication Date
WO2010139225A1 true WO2010139225A1 (zh) 2010-12-09

Family

ID=43227930

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/072549 WO2010139225A1 (zh) 2009-05-31 2010-05-10 一种本地交换的实现方法、移动交换中心和通信系统

Country Status (3)

Country Link
CN (1) CN101902824B (zh)
RU (1) RU2487503C1 (zh)
WO (1) WO2010139225A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101754416B (zh) * 2009-12-31 2012-01-25 华为技术有限公司 局间建立、解除本地交换的方法和移动交换中心
CN102497396B (zh) * 2011-11-30 2015-07-22 华为技术有限公司 通信方法、基站、基站控制器和移动交换中心
CN102780992B (zh) * 2012-06-20 2015-01-28 华为技术有限公司 一种基站云下的本地交换功能的实现方法及装置
CN108156639B (zh) * 2016-12-06 2020-05-08 华为技术有限公司 语音业务在切换后返回长期演进网络的方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006117652A1 (en) * 2005-05-04 2006-11-09 Nokia Corporation Low-cost radio access network enabling local switching
CN101180843A (zh) * 2005-05-25 2008-05-14 艾利森电话股份有限公司 由多媒体核心网络进行呼叫建立的本地交换
CN101185299A (zh) * 2005-05-27 2008-05-21 艾利森电话股份有限公司 无线电接入网中的本地交换

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
SE514264C2 (sv) * 1999-05-07 2001-01-29 Ericsson Telefon Ab L M Ett kommunikationssystem
KR100985706B1 (ko) * 2002-02-02 2010-10-06 데이진 아라미드 비.브이. 내피로성이 높은 멀티필라멘트 아라미드 사
CN1311694C (zh) * 2004-05-10 2007-04-18 华为技术有限公司 公用电话交换网演进系统及其方法
US7717342B2 (en) * 2005-08-26 2010-05-18 Hand Held Products, Inc. Data collection device having dynamic access to multiple wireless networks
CN101272626B (zh) * 2008-04-16 2011-05-18 华为技术有限公司 实现本地交换的方法、装置及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006117652A1 (en) * 2005-05-04 2006-11-09 Nokia Corporation Low-cost radio access network enabling local switching
CN101180843A (zh) * 2005-05-25 2008-05-14 艾利森电话股份有限公司 由多媒体核心网络进行呼叫建立的本地交换
CN101185299A (zh) * 2005-05-27 2008-05-21 艾利森电话股份有限公司 无线电接入网中的本地交换

Also Published As

Publication number Publication date
CN101902824A (zh) 2010-12-01
CN101902824B (zh) 2012-11-07
RU2487503C1 (ru) 2013-07-10

Similar Documents

Publication Publication Date Title
EP2182758B1 (en) Method of handling an inter rat handover in wireless communication system and related communication device
JP5260642B2 (ja) マルチメディア・モバイルネットワークにおいて音声サービスを提供するシステムおよび方法
CA2438621C (en) A communication system comprising a plurality of communication networks
JP3727539B2 (ja) シグナリング方法
WO2014044211A1 (zh) 一种移动通信网络中直连通讯终端会话切换方法及装置
WO2011134151A1 (zh) 一种中止电路交换域返回传统网络呼叫的方法、装置和系统
WO2012051961A1 (zh) 业务处理方法和设备
WO2010139225A1 (zh) 一种本地交换的实现方法、移动交换中心和通信系统
WO2009067912A1 (fr) Procédé et dispositif de commutation pour mettre en œuvre une commutation
WO2014198070A1 (zh) 一种csfb实现方法及设备
KR101263971B1 (ko) 이동국 보안 모드 방법
WO2011017894A1 (zh) 一种本地呼叫本地交换的实现方法和系统
WO2011113207A1 (zh) 用于业务交换的方法以及设备
US7039416B2 (en) Method and apparatus for adapting a number of bearers to a service
WO2011057578A1 (zh) 一种本地呼叫本地交换的实现方法
WO2008011777A1 (fr) Procédé permettant d'identifier un msc avec délai d'attente, procédé d'appel de groupe et équipement associé
WO2010091612A1 (zh) 建立本地交换的方法、核心网设备及基站子系统
WO2011134354A1 (zh) 一种本地交换中实现切换的系统、方法及基站子系统
WO2012065405A1 (zh) 合法终端的判定方法及系统
WO2011079788A1 (zh) 局间建立、解除本地交换的方法和移动交换中心
JP2008527777A (ja) 非同期網と同期網とが混在する移動通信網におけるハンドオーバ方法
WO2010091634A1 (zh) 建立本地交换的方法、设备和系统
KR102304200B1 (ko) 기지국장치 및 단말장치
WO2010115379A1 (zh) 一种切入过程中呼叫建立方法和系统
WO2010102584A1 (zh) 一种基站系统内的呼叫切换方法及移动通信系统

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: 10782929

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 9049/CHENP/2011

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2011153729

Country of ref document: RU

122 Ep: pct application non-entry in european phase

Ref document number: 10782929

Country of ref document: EP

Kind code of ref document: A1