WO2010051763A1 - 寻呼处理、信息显示方法、装置及*** - Google Patents

寻呼处理、信息显示方法、装置及*** Download PDF

Info

Publication number
WO2010051763A1
WO2010051763A1 PCT/CN2009/074812 CN2009074812W WO2010051763A1 WO 2010051763 A1 WO2010051763 A1 WO 2010051763A1 CN 2009074812 W CN2009074812 W CN 2009074812W WO 2010051763 A1 WO2010051763 A1 WO 2010051763A1
Authority
WO
WIPO (PCT)
Prior art keywords
called party
paging
message
called
user
Prior art date
Application number
PCT/CN2009/074812
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 EP09824418.9A priority Critical patent/EP2346281B1/en
Priority to ES09824418.9T priority patent/ES2567050T3/es
Priority to JP2011534994A priority patent/JP2012508487A/ja
Priority to EP15167144.3A priority patent/EP2934042B1/en
Publication of WO2010051763A1 publication Critical patent/WO2010051763A1/zh
Priority to US13/101,816 priority patent/US9049677B2/en
Priority to US14/710,203 priority patent/US10306517B2/en
Priority to US16/405,514 priority patent/US10757614B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H04W36/00224—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies between packet switched [PS] and circuit switched [CS] network technologies, e.g. circuit switched fallback [CSFB]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/005—Transmission of information for alerting of incoming communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a paging process, an information display method, a device, and a system. Background technique
  • Evolved Universal Mobile Telecommunication System Territorial Radio Access Network E-UTRAN
  • Evolved Packet Core EPC
  • UMTS Evolved Universal Mobile Telecommunication System
  • EPS Evolved Packet System
  • PS Packet Switching
  • the domain data service accesses, and the EPS network coexists with the traditional 2/3G circuit domain network for a period of time. Since most users (User Equipment, UE for short) consider the cost reduction, air interface signaling, and battery consumption reduction, only one wireless access technology can be maintained at the same time.
  • UE can pass the Global System for Mobile Communications (GSM) / Enhanced Data Rate for GSM Evolution (EDGE) wireless access 2/3G access network access circuit domain such as GSM EDGE Radio Access Network (GERAN), UTRAN, Code Division Multiple Access (CDMA) Radio Access Network (CDMA)
  • GSM Global System for Mobile Communications
  • EDGE Enhanced Data Rate for GSM Evolution
  • GERAN GSM EDGE Radio Access Network
  • CDMA Code Division Multiple Access
  • the core network can also access the EPC through E-UTRAN.
  • the MME registered by the UE is associated with the MSC registered by the UE on the circuit domain side, and the interface between the MME and the MSC is in the EPS.
  • the standard is called the SGs interface.
  • the UE accesses the EPC on the E-UTRAN side, and the packet service can be used. If the voice service is required, the UE can switch to the GERAN/UTRAN/CDMA AN side through the CS domain fallback process, and establish a CS call link according to the original CS domain process to perform voice service. This process is called CS domain fallback.
  • the packet bearer of the UE is usually suspended by the network (Suspend). In the suspended state, the network still retains the IP address carried by the packet allocated by the UE, but the packet data cannot be transmitted at this time, that is, the data. The business was interrupted.
  • the voice service of the UE ends, the network can recover the packet of the UE through a Resume process, and the UE can reuse the packet service.
  • the MME is associated with the Mobile Switching Center Server (MSC) on the SGs interface (the SGs interface is established, the UE is currently accessing the EPC through the E-UTRAN).
  • MSC Mobile Switching Center Server
  • IAM Initial Address Message
  • the MME forwards the paging request message to the MME.
  • the MME sends a paging notification message to the UE directly through the signaling connection between the MME and the UE if the UE is currently in the connected state.
  • the UE may display the prompt information to prompt the user of the UE to have a voice call according to the CS domain fallback configuration and the current service state on the UE, and query the user whether to interrupt the current data service. Switch to the circuit domain to answer the voice call.
  • the UE may notify the MME to perform the CS domain fallback process, and switch to the CS domain to establish a CS domain call link for voice service, and the current grouping.
  • the bearer is switched to the UTRAN side and hangs; when the UE obtains the command input by the user to reject the voice call, the UE may send a reject answer message to the MME, and after receiving the reject message, the MME notifies the MSC that the called user rejects the SGs interface. For the voice call, the MSC responds to the calling party according to the paging failure or the UE rejection procedure. At this time, the data service currently being performed by the E-UTRAN-side UE is not affected.
  • the inventor has found that at least the following problems exist in the prior art: After the UE displays the prompt information, the user of the UE needs to confirm whether to interrupt the current data service, answer the voice call, or continue the current data service. , refused to answer the voice call.” Confirmation operation above It is a process of human-computer interaction. The user of the UE may need to wait a few seconds to a dozen seconds or even a longer period of time from seeing the prompt information to making a judgment and sending the confirmation information to the UE in some form. After the MSC sends a paging request message to the MME, it waits for the UE to respond to the paging. Generally, the MSC waits for the paging time to be 10 seconds.
  • the CS domain fallback scheme if the CS domain is waiting for the user.
  • the acknowledgment of the fallback operation causes the MSC to fail to receive the paging response of the UE for a long time.
  • the MSC cannot correctly distinguish whether the UE fails to be paged on the E-UTRAN side, or the UE is successfully paged on the E-UTRAN side, and the UE is waiting for the user.
  • Confirmation which causes the MSC to process according to the paging failure, such as terminating the call flow, or erroneously turning to the 2/3G access network for paging; in the original CS domain, the paging of the called user is successful and established. After the CS domain calls the link, it will return the called ringing message to the calling party.
  • the calling party can hear the connection tone at this time. In normal circumstances, it only takes a few seconds. In the CS domain fallback scheme, waiting During the process of confirming the CS domain fallback operation, the called party may not be able to hear the connection tone for a long time, and mistakenly believe that the network has a fault and actively suspend the call, thus affecting the normal progress of the voice service. Row. Summary of the invention
  • the embodiment of the present invention provides a paging processing, an information display method, a device, and a system, which are used to improve the success rate of a paging initiated by a UE registered by a UE to a UE currently in a connected state on the E-UTRAN side.
  • the embodiment of the invention provides a paging processing method, including:
  • the server returns a paging status message of the called party terminal.
  • An embodiment of the present invention provides an information display method, including:
  • paging notification message where the paging notification message carries a service type identifier; displaying the first prompt information, where the first prompt information is used to indicate whether the user confirms whether to accept the circuit domain fallback process;
  • the embodiment of the invention further provides a mobility management apparatus, including:
  • a first receiving module configured to receive a paging request message sent by a mobile switching center server registered by the called party terminal;
  • a notification module configured to: after the first receiving module receives the paging request message, send a paging notification message to the called party terminal, and send the paging notification message to the mobile terminal when the called party terminal is in a connected state
  • the central server returns a paging status message of the called party terminal.
  • the embodiment of the invention further provides a mobile switching center server, including:
  • a second receiving module configured to receive a paging status message of the called party terminal returned by the mobility management device
  • a processing module configured to: after the second receiving module receives the paging status message, extend the time for waiting for the called party terminal to return the paging response message.
  • the embodiment of the invention further provides a terminal, including:
  • a third receiving module configured to receive a paging notification message, where the paging notification message carries a service type identifier
  • a first display module configured to: after the third receiving module receives the paging notification message, display the first prompt information, where the first prompt information is used to indicate whether the user accepts the circuit domain fallback process; And configured to acquire a first instruction that is input by the user according to the first prompt information;
  • a first execution module configured to trigger execution of a circuit domain fallback process according to the first instruction
  • a second display module configured to display second prompt information according to the service type identifier and the first instruction, the second prompt The information is used to instruct the user to confirm whether the call is connected
  • a second acquiring module configured to acquire a second instruction that is input by the user according to the second prompt information
  • a second execution module configured to return a connection message to the mobile switching center server according to the second instruction, or perform an operation process corresponding to the service type identifier.
  • the embodiment of the invention further provides a paging processing system, comprising a mobile switching center server and a mobility management device, wherein
  • the mobile switching center server is configured to send a paging request message to the mobility management device, and receive a paging status message of the called party terminal returned by the mobility management device, and extend waiting for the called party terminal to return a paging response. The time of the message;
  • the mobility management apparatus is configured to receive a paging request message sent by the mobile switching center server, and send a paging notification message to the called party terminal when the called party terminal is in a connected state, and The mobile switching center server returns a paging status message for the called party terminal.
  • the MME after the MME that is registered by the UE receives the paging request message of the MSC registered by the called UE, the MME sends the called UE to the called UE.
  • the paging message of the CS domain may also return a paging status message to the MSC to indicate to the MSC that the called party UE has received the paging notification message, and the MSC that is registered by the UE is connected to the current E-UTRAN side.
  • FIG. 1 is a schematic flowchart of a paging processing method according to Embodiment 1 of the present invention.
  • FIG. 2 is a schematic flowchart of a paging processing method according to Embodiment 2 of the present invention.
  • FIG. 3 is a schematic flowchart of a paging processing method according to Embodiment 3 of the present invention.
  • FIG. 4 is a schematic flowchart of a paging processing method according to Embodiment 4 of the present invention.
  • FIG. 5 is a schematic flowchart diagram of an information display method according to Embodiment 5 of the present invention.
  • FIG. 6 is a schematic structural diagram of a mobility management apparatus according to Embodiment 6 of the present invention.
  • FIG. 7 is a schematic structural diagram of a mobility management apparatus according to Embodiment 7 of the present invention.
  • FIG. 8 is a schematic structural diagram of a mobile switching center server according to Embodiment 8 of the present invention
  • FIG. 9 is a schematic structural diagram of a terminal according to Embodiment 9 of the present invention
  • FIG. 10 is a schematic structural diagram of a paging processing system according to Embodiment 10 of the present invention. detailed description
  • the UE accesses the CS domain core network through the UTRAN and the UE accesses through the E-UTRAN.
  • the CS domain fallback between EPCs is taken as an example to describe the technical solution of the embodiment of the invention.
  • FIG. 1 is a schematic flowchart of a paging processing method according to Embodiment 1 of the present invention.
  • a called UE currently accesses an EPC through an E-UTRAN, and an MME (called MME) registered by a called UE is associated with The MSC (the called party MSC) registered by the called party UE has been associated with the SGs interface.
  • MME MME registered by a called UE
  • MSC the called party MSC
  • Step 101 The MME receives a paging request message sent by the called party MSC.
  • Step 102 When the called UE is in the connected state, the MME sends a paging notification message to the called UE, and returns a paging status message of the called UE to the called MSC.
  • the MME after receiving the paging request message of the MSC registered by the called UE, if the MME is found to be in the connected state, the MME sends a CS domain paging notification message to the called UE, Returning a paging status message to the MSC to indicate to the MSC that the called party UE has received the paging notification message, thereby preventing the MSC from erroneously determining that it is in E- during the waiting party UE waiting for the user to confirm whether to perform the CS domain fallback procedure.
  • the UTRAN side fails to page the called party UE and the corresponding error processing occurs, the success rate of the call is improved.
  • FIG. 2 is a schematic flowchart of a paging processing method according to Embodiment 2 of the present invention.
  • the called UE currently accesses the EPC through the E-UTRAN, and the MME registered by the called UE and the called UE are registered.
  • the MSC has established an association through the SGs interface. As shown in FIG. 2, this embodiment may include the following steps:
  • Step 201 The MSC registered by the called UE receives the IAM sent by the calling party, and the IAM The message carries the mobile station ISDN number (MSISDN) of the called party UE, and the MSC searches the context of the called party UE according to the MSISDN of the called party UE carried in the IAM message, and obtains the called party UE.
  • MSISDN mobile station ISDN number
  • IMSI International Mobile Subscriber Identity
  • the IAM may also carry the identity information of the calling party UE, for example, the MSISDN of the calling party UE, and the paging request message carries the identification information of the calling party UE correspondingly;
  • Step 202 The MME receives the paging request message, searches the context of the called UE according to the IMSI of the called UE carried in the paging request message, and determines the called UE according to the status recorded in the context of the called UE.
  • the CS domain paging notification message is sent to the called UE through a Non Access Stratum (NAS) message.
  • NAS Non Access Stratum
  • the paging request message sent by the MSC in step 201 carries the identification information of the calling party UE, that is, the MME obtains the identification information of the calling party UE from the MSC, for example, the MSISDN of the calling party UE, this step
  • the medium MME may include the MSISDN of the calling party UE in the CS domain paging notification message;
  • Step 203 The MME returns a paging status message of the called party UE to the MSC, to notify the MSC that the called party UE has received the paging notification message and starts a human-computer interaction procedure.
  • Step 204 The MSC receives the paging status message, extends the time of waiting for the CS domain paging response of the called party UE, and returns the called vibration of the CS domain call link to the MSC registered by the calling party UE according to the preset policy.
  • the ringing message is an address complete message (ACM), so that the MSC registered by the calling party UE forwards the called ringing message to the calling party UE.
  • Step 205 The called party UE receives the CS domain paging
  • the notification message displays the prompt information according to the preset CS domain fallback configuration information to request the user to confirm whether to execute the CS domain fallback process.
  • the called party UE acquires the identification information of the calling party UE from the MME, for example: the calling party UE MSISDN, in this step, the called UE may include the MSISDN of the calling party UE in the prompt information;
  • Step 206 The called party UE acquires an execution command input by the user, that is, interrupts the current data service, The command of the voice service is performed, the UE records the user's selection, and sends a Service Request message to the eNB;
  • Step 207 The eNB receives the service request message, and forwards the service request message to the MME.
  • the called party UE switches to the CS domain, establishes a CS domain call link to answer the call, and switches the current PS bearer to the UTRAN side and suspends.
  • the MSC may also pass other types of identification information that can uniquely identify the called UE, for example: Temporary Mobile Station Identity (TMSI) of the UE in the circuit domain.
  • TMSI Temporary Mobile Station Identity
  • M-TMSI MME Temporary Mobile Station Identity
  • the MSC waits for the called UE to respond to the paging state before the step 204, and the MSC can use the two messages as the legal response to the paging request message sent to the MME:
  • the user of the called party UE selects "Accept" CS domain fallback: The called party UE initiates a service request on the CS domain side, and the MSC receives the service request message received on the CS domain side as a paging response;
  • the user of the called party UE selects "reject" the CS domain to fall back, or does not confirm within the set time (for example, 20 seconds), that is, neither "accept” CS domain fallback nor "reject” CS is selected.
  • the domain fallback The called party UE sends a reject answer message to the MME.
  • the MME notifies the MSC of the called party UE that the user of the called party refuses to answer the call through the SGs interface, and the MSC returns a response to the calling party according to the paging failure or the user rejection.
  • the called UE responds to the CS domain paging. Unless otherwise specified, the user of the called UE selects to "accept" the CS domain to fall back, and the called UE switches to the 2/3G access.
  • the network sends a service request message to the MSC on the side of the CS domain as a CS domain paging response.
  • the MSC in step 204 of the embodiment may return the called ringing message to the calling party according to the preset policy.
  • the preset policy may be that the MSC immediately sends the called ringing message to the MSC registered by the calling UE.
  • the preset policy may also forward the called ringing message to the MSC registered to the calling party UE after the preset time period, for example:
  • the MSC may initiate a 12-second paging waiting timer. If the page waiting timer expires, the called party is still not received.
  • the UE's CS domain paging response the MSC sends a called ringing message to the calling party while continuing to wait for the CS domain paging response of the called party UE.
  • the MSC may stop the paging waiting timer, establish a CS domain call link with the called party UE, and return to the calling party. Call the ringing message.
  • Step 203 of this embodiment can be performed in two ways: one is executed immediately after performing step 202; the other is after step 202 is executed, a timer is started, and the timer is executed after the timer expires.
  • a 10-second wait timer which should be less than the duration of the paging wait wait timer of the MSC and the MSC and the calling party UE registered by the calling party UE usually wait for the called ringing message.
  • the MME sends a paging status message to the MSC when the MME receives a response to the CS domain fallback procedure after the waiting timer expires on the MME.
  • the MSC After receiving the paging status message, the MSC knows that although The CS domain paging response of the called party UE has not been received for a long time, but the called party UE has actually received the CS domain paging notification message, waiting for its user to confirm or is in the process of initiating the CS domain fallback process, the MSC The time for waiting for the CS domain paging response of the called party UE is extended, and the called party ringing message established by the CS domain call link is returned to the calling party according to a preset policy.
  • step 203 of this embodiment may be performed simultaneously with the step of the MME in step 202 sending a CS domain paging notification message to the called party UE, and the same effect can be achieved.
  • the duration of the paging waiting timer (including retransmission) on the MSC depends on the length of time that the MSC waits for the UE to respond to the paging message and the number of paging retransmissions of the MSC. For example, the duration of the MSC waiting for the UE to respond to the paging message is 5 seconds, the number of paging retransmissions of the MSC is 3, and the duration of the paging waiting timer is 15 seconds. If the paging response is not received after the timer expires, the prior art does not receive the paging response returned by the called UE.
  • the MSC will consider that the paging on the E-UTRAN side is unsuccessful and suspends the current call, and returns an error message to the calling party; or considers that the called party UE is not in the E-UTRAN coverage area, and then searches for the UTRAN side.
  • the user of the calling party U E may not hear the connection tone for a long time, it is likely that the network has failed and actively suspends the call.
  • the MSC in this embodiment has already obtained the paging response before receiving the called party UE.
  • the paging status message of the called party UE returned by the MME obtains the CS domain paging request message in advance and has successfully submitted the called party UE in the connected state, but the user of the called party UE may not have confirmed whether to execute the CS domain.
  • the MSC can continue to wait for the paging response of the called party UE instead of terminating the call or turning to the 2/3G access network for paging, and the MSC can send the caller in advance to the calling party when the UE cannot respond to the CS paging request in time. Calling a ringing message prevents the calling user from actively terminating the call and improves the call success rate.
  • the MME may return the paging status to the MSC in addition to sending the CS domain paging notification message to the called UE. a message to indicate to the MSC that the called party UE has received the paging notification message, thereby preventing the MSC from erroneously determining to page the called party on the E-UTRAN side while the called party UE waits for the user to confirm whether to perform the CS domain fallback procedure. If the UE fails and the corresponding error processing occurs, the success rate of the call is improved.
  • the MSC may also return the called ringing message to the calling party according to a certain policy, thereby preventing the user of the calling party UE from erroneously determining that the called party is not responding during the waiting party UE waiting for the user to confirm whether to perform the CS domain falling back process. The end of the call occurs.
  • FIG. 3 is a schematic flowchart of a paging processing method according to Embodiment 3 of the present invention.
  • the called UE currently accesses the EPC through the E-UTRAN, and the MME registered by the called UE and the called UE are registered to buy.
  • the MSC has been associated through the SGs interface. As shown in Figure 3, this embodiment may include the following steps:
  • Step 301 The MSC that is registered by the called UE receives the IAM sent by the calling party, where the IAM message carries the MSISDN of the called UE, and the MSC searches for the called party according to the MSISDN of the called UE carried in the IAM message.
  • the IMS of the called UE is obtained by the MME, and the MME is configured to send a paging request message to the MME that is registered by the called UE.
  • the paging request message carries the IMSI of the called UE.
  • the IAM may also carry the identification information of the calling party UE, for example: the calling party
  • the MSISDN of the UE the paging request message carries the identification information of the calling party UE correspondingly;
  • Step 302 The MME receives the paging request message, and searches for the context of the called UE according to the IMSI of the called UE carried in the paging request message, and records according to the context of the called UE.
  • the state determines that the called party UE is in the connected state, and sends a CS domain paging notification message to the called party UE through the NAS layer message.
  • the paging request message sent by the MSC in step 301 carries the identification information of the calling party UE, that is, the MME obtains the identification information of the calling party UE from the MSC, for example, the MSISDN of the calling party UE, this step
  • the medium MME may include the MSISDN of the calling party UE in the CS domain paging notification message;
  • Step 303 The called UE receives the CS domain paging notification message, and determines to display the prompt information according to the preset CS domain fallback configuration information, to request the user to confirm whether to perform the CS domain fallback process, and returns a waiting indication message to the MME.
  • the MME is notified to start the human-computer interaction program.
  • the called party UE obtains the identification information of the calling party UE from the MME, for example: the calling party UE MSISDN, in this step, the called UE may include the MSISDN of the calling party UE in the prompt information;
  • Step 304 The MME receives the waiting indication message, and returns a paging status message of the called party UE to the MSC, to notify the MSC that the called party UE has received the paging notification message and starts a human-computer interaction procedure.
  • Step 305 The MSC receives the paging status message, extends the time of waiting for the CS domain paging response of the called party UE, and returns the called vibration of the CS domain call link to the MSC registered by the calling party UE according to the preset policy.
  • the ring message is the ACM for the MSC to forward to the calling party UE;
  • Step 306 The called UE receives the CS domain paging notification message, and displays the prompt information according to the preset CS domain fallback configuration information, to request the user to confirm whether to perform the CS domain fallback process.
  • Step 307 The called UE acquires the user The input execution command interrupts the current data service and the voice service command, the UE records the user's selection, and sends a service request message to the eNB.
  • Step 309 The MME receives the service request message and initiates a CS domain fallback process.
  • the called party UE switches to the CS domain, establishes a CS domain call link to answer the call, and switches the current PS bearer to the UTRAN side and suspends.
  • the CS domain fallback configuration information in step 303 of the embodiment may be "always preferentially answering the call", and then the called party UE determines that the prompt information may not be displayed when receiving the CS domain paging notification message.
  • the CS domain fallback process is directly confirmed; the CS domain fallback configuration information may also be "Always request user confirmation", then the called party UE determines to display the prompt message when receiving the CS domain paging notification message, to request the user to confirm whether The CS domain fallback process is performed; the CS domain fallback configuration information may also be "When the UE performs certain unbreakable packet services (online video, games, etc.), requesting user confirmation", then the called party UE is performing an uninterruptible packet.
  • the CS domain fallback configuration information may also be "for the calling party UE on the specific whitelist, Always answer the call first; or always refuse to answer the call to the calling party UE on the specific blacklist; or other caller UEs that are not on the whitelist or on the blacklist, request the user to confirm", then
  • the calling UE receives the CS domain paging notification message triggered by the calling party UE on the specific whitelist, it determines that the prompt information may not be displayed, and directly confirms the execution of the CS domain back.
  • the called party UE when the called party UE receives the CS domain paging notification message triggered by the calling party UE on the specific blacklist, the called party information may not be displayed, but the CS domain fallback process is directly rejected, and the called party UE receives other calling parties.
  • the prompt information is determined to request the user to confirm whether to perform the CS domain fallback process.
  • the called party UE determines to display the prompt information, the called party returns a wait indication message to the MME to notify the MME that the called party UE initiates a human-computer interaction procedure, regardless of whether the user of the called party UE confirms the execution of the CS domain.
  • the fallback process or the rejection of the CS domain fallback process may take a long processing time to respond to the MSC's paging request. If the called party UE determines that the prompt information may not be displayed, the called party UE directly confirms whether to perform the CS domain fallback procedure or rejects the CS domain fallback procedure, and the called UE may not return the waiting indication message to the MME in this step.
  • the CS domain fallback procedure is started. When no waiting indication message of the UE is received, the MME does not return a paging status message of the called party UE to the MSC.
  • the technical solution of the foregoing embodiment does not exclude the called party UE from sending a wait indication message to the MME when determining that the prompt information is not displayed after receiving the CS domain paging request message of the MME.
  • step 304 of this embodiment may be implemented in two ways: one is to immediately return a paging status message of the called party UE to the MSC when the MME receives the waiting indication message; the other is received by the MME.
  • a timer is started, and the paging status message of the called party UE is returned to the MSC after the timer expires, and details are not described herein again.
  • the MME in this embodiment negotiates with the called UE before returning the UE paging status message to the MSC, that is, the MME waits for the waiting indication sent by the called party UE.
  • the message if the MME determines that the called party UE initiates the human-computer interaction procedure to confirm to the user whether to perform the CS domain fallback procedure, the MME returns a paging status message of the called party UE to the MSC to indicate the called party UE's seeking. If the MME determines that the called party UE does not initiate the human-computer interaction procedure to confirm to the user whether to perform the CS domain fallback procedure, the MSC waits for the normal paging response according to the normal procedure, and does not need to be extended. The paging response wait time, or the processing step of responding to the called party in response to the called ringing message in advance.
  • the UE in the connected state of the E-UTRAN may determine whether the prompt information needs to be displayed according to the configuration and the packet service state.
  • the user confirms whether the CS domain fallback process needs to be performed, but introduces a user experience problem. If the UE user confirms the execution of the CS domain fallback process, the user will consider that the call has been received according to the experience of the existing CS domain phone. However, in some supplementary services of the CS domain, the user of the called UE cannot judge whether to answer the call only by the telephone number of the calling party UE, for example, Call Forwarding service, call forwarding (Call Deflection) ) Business, etc.
  • the user A of the calling party UE dials the call to the user B, and the service data of the user B (the forward party) is set to forward the call to the user C, and the prompt information displayed on the UE of the user C is displayed.
  • the calling party information is the phone number of user A.
  • user C may be willing to answer user A's call, but is not willing to answer any user B's forwarded call. If the called user C is required to confirm that the CS domain falls back and must confirm the direct answer to the call, then the called user is deprived.
  • the right to answer is selected according to the forwarding information.
  • the user A of the calling party UE dials the call to the user B.
  • call forwarding service requires intermediate user B to input the telephone number of end user C before selecting "accept" call, and confirm the call forwarding; call forwarding service from user A to user B is An ordinary call, so the MSC cannot determine whether User B will initiate a call steering operation before User B operates. Since the call steering operation must interact between the UE and the MSC, if the user of the called party UE is confirmed to return the CS domain, only the "answer" and "reject" voice call two operation options are provided. The call steering option cannot be provided, and the right to use the call to the service is deprived under the CS domain fallback scheme.
  • FIG. 4 is a schematic flowchart of a paging processing method according to Embodiment 4 of the present invention.
  • the called UE is currently accessing the EPC through the E-UTRAN, and the MME registered by the called UE and the called UE are registered to buy.
  • the MSC has been associated through the SGs interface. As shown in FIG. 4, this embodiment may include the following steps:
  • Step 401 The MSC registered by the called UE receives the IAM sent by the calling party, where the IAM message carries the MSISDN of the called UE, and the MSC searches for the called party according to the MSISDN of the called UE carried in the IAM message.
  • the context of the UE is obtained by the IMSI corresponding to the called UE.
  • the MME sends a paging request message to the MME that is registered by the called UE.
  • the paging request message carries the IMSI of the called UE and the service type identifier.
  • the service type identifier may be a type indicating a normal voice call, and various specific supplementary services, for example, a call forwarding service, etc., noting whether the called user initiates a call forwarding service, as described above, depending on the called user. Operation, at this time the MSC is treated as an ordinary call. Therefore, the service type identifier does not indicate that the call is diverted to the service.
  • the called UE may identify the specific service type indicated by the service type identifier, and determine, according to the configuration information of the service, whether the service type needs to be switched to the CS domain side of the called UE. The prompt message is displayed again to ask the user of the called party UE to confirm whether to answer the call.
  • the service type identifier may also be an identifier indicating whether the prompt information needs to be displayed again.
  • the MSC determines the specific type of the service, the MSC directly indicates whether the called UE needs to switch to the CS domain side.
  • the prompt message is displayed again, so that the user of the called party UE can confirm whether to answer the call, for example: for a normal voice call, generate an identifier indicating that the user does not need to be prompted again; for the call forwarding type service, generate a message indicating that the user needs to be prompted again.
  • logo for a normal voice call, generate an identifier indicating that the user does not need to be prompted again; for the call forwarding type service, generate a message indicating that the user needs to be prompted again.
  • the IAM may also carry the identity information of the calling party UE, for example, the MSISDN of the calling party UE, and the paging request message carries the identification information of the calling party UE correspondingly;
  • Step 402 The MME receives the paging request message, searches the context of the called UE according to the IMSI of the called UE carried in the paging request message, and determines the called UE according to the status recorded in the context of the called UE. When in the connected state, send the message to the called UE through the NAS layer message. Cs domain paging notification message.
  • the MME obtains the identification information of the calling party UE and the service type identifier from the MSC.
  • the MME may include the foregoing related information in the CS domain paging notification message;
  • Step 403 The MME returns a paging status message of the called party UE to the MSC, to notify the MSC that the called party UE has received the paging notification message and starts a human-computer interaction procedure.
  • the MME may immediately return the paging status message of the called party UE to the MSC, and the MME may also negotiate with the called party UE, and then return the called party UE to the MSC according to the waiting indication message returned by the called party UE.
  • the call status message is as described in the foregoing embodiment 2 and the third embodiment, and is not described in this embodiment;
  • Step 404 The MSC receives the paging status message, extends the time of waiting for the CS domain paging response of the called party UE, and returns the called ringing message established by the CS domain call link to the calling party according to the preset policy, that is, ACM. ;
  • Step 405 The called party UE receives the CS domain paging notification message, and displays the first prompt information according to the preset CS domain fallback configuration information and the service type identifier carried in the CS domain paging notification message, to request the user to confirm. Whether the CS domain fallback process is performed, and the content of the first prompt information is determined according to the service type identifier, for example:
  • the first prompt information displayed by the called party UE does not need to be reconfirmed before the call is answered, that is, the prompt information is the requesting user.
  • Confirm whether to answer the call directly for example, "Is there a call from 13XXXXXXXX, whether to interrupt the current XXXX packet service, and directly answer the call?", the operation options provided to its users may include "Accept", "Reject", and may also include "Call steering.”
  • the first prompt information displayed by the called party UE includes content that the user needs to reconfirm before answering the call, that is, the prompt information is the requesting user confirmation.
  • the prompt information is the requesting user confirmation.
  • switch to the CS domain but not directly confirm the call, but need its user to confirm again after switching to the CS domain, for example: "There is 13XXXXXXXXX to call you, the call is forward type Service, you may need to confirm whether to answer the call after receiving the call information, whether to interrupt the current XXXX packet service, receive The call information?
  • the operation option provided to the user may include "accept” and "reject”; step 406, the called party UE acquires the first instruction input by the user according to the first display information, and the UE records the user's selection according to the An instruction sends a service request message to the eNB;
  • Step 407 The eNB receives the service request message, and forwards the service request message to the MME.
  • the called party UE switches to the CS domain and establishes a CS domain call link.
  • Step 409 The called UE displays the second prompt information according to the service type identifier and the first instruction.
  • Step 410 The called party U E acquires a second instruction input by the user according to the second prompt information, and returns a connection message to the MSC according to the second instruction.
  • the user of the called UE UE inputs the first instruction according to the first prompt information.
  • the called party UE may further display the second prompt information after the CS domain call link is established, and the user may confirm again; otherwise, the second prompt information is not required to be displayed.
  • the user is requested to confirm again, then the called party UE can immediately answer the call signaling (Connect) to the MSC after the CS domain call link is established, and the called user can directly start the call.
  • the process of responding to the PS domain in the CS domain fallback and responding to paging and establishing a CS call link on the CS domain side requires a delay of several seconds, during which the user and the calling party of the called UE are called.
  • the CS call link between the users of the UE is not yet connected, and the two parties cannot talk to each other, that is, the called user cannot hear the voice of the calling user, and the called user cannot speak to the calling user.
  • the existing CS domain voice service after the called user presses the "Accept" button, since the previous CS paging link has been established, the call can be basically performed at the same time.
  • the called party UE can play the voice information during the CS domain fallback process, for example: The special sound effect, to remind the user of the called party UE that the call is in progress, no need to try to talk before the end of the sound effect.
  • the called party UE can play different voice information for two types of pages that do not need to be reconfirmed and need to be reconfirmed.
  • the paging request message sent by the MSC to the MME is as simple as possible, generally only the called party is carried.
  • the identification information of the party UE, the identification information of the calling party UE, and the like, and the call information of the call of the CS domain supplementary service, such as the forward party identifier of the call forwarding service, and the handover to the CS domain After that, the called party UE is complete in the call link establishment process, and the call related service information acquired from the MSC is complete.
  • the second prompt information is displayed, the richer information content can be selected, thereby making the called party The user of the UE can more accurately determine whether or not he is willing to answer the call.
  • the user of the called UE can judge whether it is willing to answer the paging according to the displayed forwarding party number; for example, after the handover to CS, the called UE directly follows the original CS with the MSC.
  • the call flow interaction can provide the user of the called party UE with other operation options except the "accept/reject" binary selection, which is consistent with the original CS domain service processing logic to provide the same service capability, for example: call steering Service, the user of the called party UE can select another new number to forward the call to this number.
  • the content and operation options of the first prompt information displayed on the E-UTRAN side are determined according to the service type identifier of the MSC, and the operation option selected by the user for the first prompt information is determined according to the service type identifier of the MSC.
  • Embodiment 5 is a schematic flowchart of an information display method according to Embodiment 5 of the present invention.
  • the called UE currently accesses the EPC through the E-UTRAN, and the MME registered by the called UE and the MSC registered by the called UE are used.
  • the association has been established through the SGs interface.
  • this embodiment may include the following steps:
  • Step 501 The called party UE receives a paging notification message, where the paging notification message carries a service type identifier.
  • the service type identifier may be a type indicating a normal voice call, and various specific supplementary services, for example, a call forwarding service, etc., noting whether the called user initiates a call forwarding service, as described above, depending on the called user. Operation, at this time the MSC is treated as an ordinary call. Therefore, the service type identifier does not indicate that the call is diverted to the service.
  • the called party UE may identify the specific service type represented by the foregoing service type, and according to its own configuration letter. After determining whether the service type needs to be switched to the CS domain side of the called party, the prompt information is displayed again, so that the user of the called party UE can confirm whether to answer the call.
  • the service type identifier may also be an identifier indicating whether the prompt information needs to be displayed again.
  • the MSC determines the specific type of the service, the MSC directly indicates whether the called UE needs to switch to the CS domain side.
  • the prompt message is displayed again, so that the user of the called party UE can confirm whether to answer the call, for example: for a normal voice call, generate an identifier indicating that the user does not need to be prompted again; for the call forwarding type service, generate a message indicating that the user needs to be prompted again.
  • logo for a normal voice call, generate an identifier indicating that the user does not need to be prompted again; for the call forwarding type service, generate a message indicating that the user needs to be prompted again.
  • Step 502 The called party UE displays the first prompt information according to the preset CS domain fallback configuration information and the service type identifier carried in the CS domain paging notification message, where the first prompt information is used to indicate whether the user confirms whether to accept the line.
  • the CS domain falls back to the process, and determines the content of the first prompt information according to the service type identifier, for example:
  • the first prompt information displayed by the called party UE does not need to be reconfirmed before the call is answered, that is, the prompt information is the requesting user.
  • Confirm whether to answer the call directly for example, "Is there a call from 13XXXXXXXX, whether to interrupt the current XXXX packet service, and directly answer the call?", the operation options provided to its users may include "Accept", "Reject", and may also include "Call steering.”
  • the first prompt information displayed by the called party UE includes content that the user needs to reconfirm before answering the call, that is, the prompt information is the requesting user confirmation.
  • the prompt information is the requesting user confirmation.
  • switch to the CS domain but not directly confirm the call, but need its user to confirm again after switching to the CS domain, for example: "There is 13XXXXXXXXX to call you, the call is forward type Service, may require you to receive the call information to confirm whether to answer the call, whether to interrupt the current XXXX packet service, receive the call information? ", the operation options provided to its users may include "accept", "reject”;
  • Step 503 The called UE acquires the first instruction that is input by the user according to the first prompt information.
  • Step 504 The called UE triggers the execution of the circuit domain fallback process according to the first instruction.
  • Step 505 The called UE displays the second prompt information according to the foregoing service type identifier and the first instruction, where the second prompt information is used to indicate that the user confirms whether the call is connected.
  • Step 506 The called party UE acquires a second instruction that is input by the user according to the second prompt information.
  • Step 507 The called party UE returns a connection message to the MSC according to the second instruction, and connects the call. Or the operation process corresponding to the service type identifier is executed.
  • the user of the called UE UE inputs the first instruction according to the first prompt information.
  • the called party UE may further display the second prompt information after the CS domain call link is established, and the user may confirm again; otherwise, the second prompt information is not required to be displayed.
  • the user is requested to confirm again, then the called party UE can immediately answer the call signaling (Connect) to the MSC after the CS domain call link is established, and the called user can directly start the call.
  • the process of responding to the PS domain in the CS domain fallback and responding to paging and establishing a CS call link on the CS domain side requires a delay of several seconds, during which the user and the calling party of the called UE are called.
  • the CS call link between the users of the UE is not yet connected, and the two parties cannot talk to each other, that is, the called user cannot hear the voice of the calling user, and the called user cannot speak to the calling user.
  • the existing CS domain voice service after the called user presses the "Accept" button, since the previous CS paging link has been established, the call can be basically performed at the same time.
  • the called party UE can play the voice information during the CS domain fallback process, for example: The special sound effect, to remind the user of the called party UE that the call is in progress, no need to try to talk before the end of the sound effect.
  • the called party UE can play different voice information for two types of pages that do not need to be reconfirmed and need to be reconfirmed.
  • the paging notification message received by the called UE is sent by the MSC.
  • the paging request message sent by the MME is triggered by the MME, and the paging request message sent by the MME to the MME is as simple as possible, and generally carries only the identification information of the called party UE, the identification information of the calling party UE, and the like, and each There are many special information related to the call of the CS domain supplementary service, such as the forward party identifier of the call forwarding service, and after the handover to the CS domain, the called UE acquires from the MSC in the call link establishment process on the CS domain side.
  • the call related service information is complete, and the second prompt information can be displayed to select a richer information content, so that the user of the called party UE can more accurately determine whether it is willing to answer the call.
  • the user of the called party UE can judge whether it is willing to answer the page according to the displayed forwarding party number; for example, the called party UE directly after switching to CS Interacting with the MSC according to the original CS call flow, the user of the called UE can be provided with other operation options except the "accept/reject" binary selection, which is consistent with the original CS domain service processing logic to provide the same service.
  • Capabilities for example: Call forwarding service, the user of the called party UE can choose another new number to forward the call to this number.
  • the content and operation options of the first prompt information displayed on the E-UTRAN side are determined according to the service type identifier of the MSC, and the operation option selected by the user for the first prompt information is determined according to the service type identifier of the MSC.
  • FIG. 6 is a schematic structural diagram of a mobility management apparatus according to Embodiment 6 of the present invention.
  • the embodiment may include a first receiving module 61 and a notification module 62 connected to each other.
  • the first receiving module 61 receives the paging request message sent by the mobile switching center server that is registered by the called party UE, and the paging request message may carry the identification information of the called UE (for example: the called party UE IMSI), when the called party UE is in the connected state, the notification module 62 sends a paging notification message to the called party UE according to the paging request message received by the first receiving module 61, and returns the called party to the mobile switching center server.
  • a paging status message of the party UE to notify the called party that the UE has received the paging notification message.
  • the mobility management apparatus may be considered as an MME in an EPS.
  • the first receiving module of the MME After receiving the paging request message of the MSC registered by the called UE, the first receiving module of the MME notifies the module that if the called UE is in the connected state, the CS domain paging notification message is sent to the called UE.
  • the paging status message may also be returned to the MSC when the CS domain return accept or reject message returned by the called party UE is not received or waited for a certain period of time to indicate to the MSC that the called party UE has received the paging notification message.
  • the MSC avoids the occurrence of corresponding error processing when the called party UE waits for the user to confirm whether to perform the CS domain fallback procedure, and erroneously determines that the called party UE fails to be paged on the E-UTRAN side, thereby improving the success rate of the call. .
  • FIG. 7 is a schematic structural diagram of a mobility management apparatus according to Embodiment 7 of the present invention. As shown in FIG. 7, compared with the previous embodiment, the embodiment may further include a triggering module 63, which is connected to the notification module 62 for acquiring. A waiting indication message sent by the called party UE to trigger the notification module 62 to move to the The switching center server returns a paging status message of the called party UE.
  • the notification module in this embodiment negotiates with the called UE before returning the UE paging status message to the MSC, that is, the triggering module waits for feedback according to the obtained called UE. Instructing the message, if the triggering module determines that the called party UE initiates the human-computer interaction procedure to confirm to the user whether to perform the CS domain fallback procedure, the triggering module retriggering notification module returns a paging status message of the called party UE to the MSC to indicate that The information about the paging state of the calling UE; if the triggering module determines that the called party UE does not initiate the human-computer interaction procedure to confirm to the user whether to perform the CS domain fallback procedure, the triggering module does not trigger the notification module to return to the MSC.
  • the paging status message of the calling UE then the MSC waits for the normal paging response according to the normal procedure, does not need to extend the paging response waiting time, or performs the processing step of responding to the calling party in advance to respond to the called ringing message. .
  • FIG. 8 is a schematic structural diagram of a mobile switching center server according to Embodiment 8 of the present invention.
  • the embodiment may include a second receiving module 81 and a processing module 82.
  • the second receiving module 81 is configured to receive a paging status message of the called party terminal returned by the mobility management device.
  • the processing module 82 extends the time for waiting for the called party UE to return the paging response message according to the paging status message received by the second receiving module 81.
  • the mobile switching center server provided in this embodiment can be considered as an MSC on the CS domain side.
  • the success rate of the call is improved.
  • the processing module 82 in this embodiment may further return a called ringing message established by the circuit domain call link to the mobile switching center server registered by the calling party UE according to a certain policy.
  • the user of the calling party UE is prevented from happening when the called party UE waits for the user to confirm whether to perform the CS domain fallback procedure and erroneously determines that the called party has no response and ends the call.
  • FIG. 9 is a schematic structural diagram of a terminal according to Embodiment 9 of the present invention.
  • the embodiment may include a third receiving module 91, a first display module 92, a first obtaining module 93, and a first executing module 94.
  • the third receiving module 91 is configured to receive a paging notification message, where the paging notification message carries a service type identifier.
  • the first display module 92 is configured to display the first prompt information after the third receiving module 91 receives the paging notification message, where the first prompt information is used to indicate whether the user accepts the circuit domain fallback process; the first obtaining module 93 is configured to: Acquiring the first instruction that is input by the user according to the first prompt information; the first executing module 94 is configured to trigger the execution of the circuit domain fallback process according to the first instruction; the second display module 95 is configured to identify the first type according to the service type and the first The second prompt information is displayed, and the second prompt information is used to indicate that the user confirms whether the call is connected.
  • the second obtaining module 96 is configured to acquire the second instruction that is input by the user according to the second prompt information. And a method for returning a connection message to the mobile switching center server according to the foregoing second instruction, or performing an operation procedure corresponding to the service type identifier.
  • the content and operation options of the first prompt information displayed on the E-UTRAN side are determined according to the service type identifier of the MSC, and the operation option selected by the user for the first prompt information is determined according to the service type identifier of the MSC.
  • FIG. 10 is a schematic structural diagram of a paging processing system according to Embodiment 10 of the present invention.
  • this embodiment may include a called party UE 1001, a mobile switching center server 1002, and a mobility management device 1003.
  • the called party UE 1001 registers with the mobility management device 1003 and the mobile switching center server 1002, respectively, and receives the paging notification message sent by the mobility management device 1003.
  • the mobile switching center server 1002 sends a paging request message to the mobility management device 1003, where the paging request message may carry the identification information of the called UE (for example: the IMSI of the called UE), and the receiving mobility management device 1003 returns The paging status message of the called party UE, and according to the paging status message, the time for waiting for the called party UE to return the paging response message.
  • the mobility management device 1003 receives the paging request message sent by the mobile switching center server 1002, and when the called party UE 1001 is in the connected state, sends a paging notification message to the called party UE 1001 according to the paging request message, and sends the paging notification message to the mobile switching center.
  • the server 1002 returns a paging status message of the called party UE 1001 to notify the called party UE 1001 that the paging notification message has been received.
  • the mobile switching center server 1002 in this embodiment may be considered as an MSC on the CS domain side, and may be the mobile switching center server provided in Embodiment 8 of the present invention; the mobility management apparatus 1003 may
  • the MME in the EPS can be any mobile management device provided in Embodiment 6 and Embodiment 7.
  • the called UE 1001 can be the terminal provided in Embodiment 9 of the present invention.
  • the MM E may send the CS domain paging notification message to the called party UE.
  • the MSC erroneously determines that the called party UE fails to be paged on the E-UTRAN side and performs corresponding error processing during the waiting for the UE to confirm whether to perform the CS domain fallback procedure, thereby improving the success rate of the call.
  • the called party UE in this embodiment receives the CS domain paging notification message, and can also be used to display the first prompt information, to request the user to confirm whether to execute the CS domain fallback process, and determine the first according to the service type identifier.
  • a prompt message (content and operation option), and acquiring a first instruction input by the user of the called party UE according to the first prompt information, and triggering the mobility management device to perform a CS domain fallback process according to the first instruction.
  • the CS domain paging notification message received by the called party UE may further carry a service type identifier, and further, the called party UE may be further configured to display the second prompt information according to the service type identifier and the first instruction, and Acquiring a second instruction input by the user of the called party UE according to the second prompt information, and returning a connection message to the mobile switching center server according to the second instruction, or performing an operation corresponding to the service represented by the service type identifier Process. If the service type identifier in this embodiment indicates that the supplementary service needs to be re-confirmed after being switched to the CS domain, or the service type identifier indicates the normal service, but the user of the called UE UE inputs the first instruction according to the first prompt information.
  • the called party UE may further display the second prompt information after the CS domain call link is established, and the user may confirm again; otherwise, the second prompt information is not required to be displayed.
  • the user is requested to confirm again, then the called party UE can immediately return a connection message (connect) to the mobile switching center server after the CS domain call link is established to answer the call signaling, that is, directly connect the call, the user of the called party UE You can start the call directly.
  • the content and operation options of the first prompt information displayed on the E-UTRAN side are determined according to the service type identifier of the MSC, and the operation option selected by the user for the first prompt information is determined according to the service type identifier of the MSC.
  • the second prompt information is displayed to allow the user to re-confirm, so that the user experience in the CS domain fallback scheme is consistent with the original CS domain service, and the operation options of the user of the called UE to the CS domain supplementary service are realized.
  • the original CS domain business was consistent.
  • the PS domain and the CS domain may be a combination of various existing PS domain and CS domain systems.
  • the PS domain may be a PS domain of a system such as GPRS, UMTS, EPS, WiMax, or CDMA HRPD.
  • the CS domain may be a CS domain system such as GSM (GERAN), WCDMA (UTRAN), or CDMA 1xRTT.

Landscapes

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

Description

寻呼处理、 信息显示方法、 装置及*** 本申请要求 2008年 11月 07日递交的申请号为 200810225981.4、发明 名称为 "寻呼处理、 信息显示方法、 装置及***" 的中国专利申请的优先权， 其全部内容通过引用结合在本申请中。 技术领域
本发明涉及通信技术领域， 特别涉及一种寻呼处理、 信息显示方法、 装 置及***。 背景技术
演进通用移动通信*** ( Universal Mobile Telecommunication System , 简称 UMTS )陆地无线接入网（ Evolved Universal Mobile Telecommunication System Territorial Radio Access Network, 简称 E-UTRAN )和演进分组核心 网（ Evolved Packet Core ,简称 EPC )构成了演进分组*** ( Evolved Packet System, 简称 EPS )。 由于某些运营商希望在部署 EPS网络后仍然由传统的 2/3G无线接入网和电路（ Circuit Switching , 简称 CS )域核心网提供语音业 务， EPS网络只提供分组（Packet Switching , 简称 PS )域数据业务接入， 在一段时间内 EPS网络与传统 2/3G电路域网络共存。由于大多数终端（ User Equipment, 简称 UE )从降低成本、 空口信令节约、 减少电池消耗等方面考 虑， 在同一时刻只能保持一种无线接入技术下的无线连接， 因此提出了 "电 路域回落" （即 CS Fallback ) 的解决方案， UE可以通过全球移动通信*** ( Global System for Mobile Communications , 简称 GSM ) /增强数据速率的 GSM演进技术 ( Enhanced Data rate for GSM Evolution , 简称 EDGE )无 线接入网 （GSM EDGE Radio Access Network, 简称 GERAN )、 UTRAN、 码分多址（Code Division Multiple Access,简称 CDMA )无线接入网（CDMA Access Network, 简称 CDMAAN )等 2/3G接入网络接入电路域核心网， 还 可以通过 E-UTRAN接入 EPC。 UE在 EPS侧附着以后， UE注册的 MME 与 UE在电路域侧注册的 MSC建立关联， MME与 MSC之间的接口在 EPS 标准中称为 SGs接口。 在 SGs接口关联建立以后， 在没有电路域语音业务 时， UE在 E-UTRAN侧接入 EPC, 可以使用分组业务。 若需要进行语音业 务， UE则可以通过 CS域回落流程切换到 GERAN/UTRAN/CDMA AN侧， 按照原有 CS域流程建立 CS呼叫链路， 进行语音业务， 这个过程就称为 CS 域回落。 在 UE 进行语音业务时， UE 的分组承载通常会被网络挂起 ( Suspend ), 在挂起状态下， 网络仍然保留为 UE分配的分组承载的 IP地 址， 但此时不能传输分组数据， 即数据业务被中断。 当 UE的语音业务结束， 网络可以通过一个恢复（ Resume )流程恢复 UE的分组 载， 此时 UE才能 重新使用分组业务。
以 UE通过 UTRAN接入 CS域核心网为例，当 MME与移动交换中心服 务器（ Mobile Switching Center Server, 简称 MSC )在 SGs接口关联建立 后 （SGs接口建立表示 UE 当前通过 E-UTRAN接入 EPC并通过 EPC在 MSC注册 ),若 MSC接收到一个主叫方对 UE的初始寻址消息（ Initial Address Message, 简称 IAM )后， 则向 MME转发寻呼请求消息。 MME接收到寻呼 请求消息后， 若 UE当前处于连接状态， MME则直接通过 MME与 UE之间 的信令连接向 UE发送寻呼通知消息。 UE接收到该寻呼通知消息后， 根据自 己的 CS域回落配置及 UE上当前的业务状态，可以显示提示信息以向 U E的 用户提示当前有一个语音呼叫， 询问用户是否中断当前的数据业务而切换到 电路域接听该语音呼叫。 当 UE获取到用户输入的中断当前数据业务、 接听 语音呼叫的命令后， 则 UE可以通知 MME执行 CS域回落流程， 以切换到 CS 域建立 CS 域呼叫链路进行语音业务， 并将当前的分组承载切换到 UTRAN 侧并挂起； 当 UE获取到用户输入的拒绝接听语音呼叫的命令， 则 UE可以向 MME发送拒绝接听消息， MME接收到拒绝接听消息后，通过 SGs 接口通知 MSC被叫用户拒绝语音呼叫， MSC按照寻呼失败或者 UE拒绝流 程向主叫方响应， 此时在 E-UTRAN—侧 UE当前正在进行的数据业务不受 影响。
在实现本发明过程中，发明人发现现有技术中至少存在如下问题： 当 UE 显示上述提示信息后， 需要 UE的用户进行确认是 "中断当前数据业务、 接 听语音呼叫"还是 "继续当前数据业务、 拒绝接听语音呼叫"。 上述确认操作 是一个人机交互的过程， UE的用户从看到该提示信息， 到做出判断， 并通过 某种形式向 UE发送确认信息， 可能需要几秒到十几秒， 甚至更长的一段时 间。 而 MSC从向 MME发送寻呼请求消息后， 一直处于等待 UE响应寻呼的 状态， 通常 MSC等待寻呼的时长为 10几秒的时间， 在 CS域回落方案中， 如果由于等待用户对 CS域回落操作的确认而导致 MSC长时间不能收到 UE 的寻呼响应， MSC则无法正确区分是在 E-UTRAN侧寻呼 UE失败， 还是在 E-UTRAN侧寻呼 UE成功， 且 UE正在等待用户的确认， 从而导致 MSC会 按照寻呼失败进行处理，例如终止呼叫流程，或者错误地转向 2/3G接入网进 行寻呼； 在原来 CS域中， 在对被叫用户寻呼成功并且建立了 CS域呼叫链 路后就会向主叫方返回被叫振铃消息， 主叫方此时可以听到接续音， 正常情 况下只需要几秒的时间， 而在 CS域回落方案中， 在等待被叫用户确认 CS 域回落操作的过程中， 主叫方可能由于很长时间听不到接续音， 误认为网络 出现了故障而主动中止本次呼叫， 从而影响了语音业务的正常进行。 发明内容
本发明实施例提供一种寻呼处理、 信息显示方法、 装置及***， 用以提 高 UE注册的 MSC向当前在 E-UTRAN侧处于连接状态的 UE发起寻呼的成 功率。
本发明实施例提供了一种寻呼处理方法， 包括：
接收被叫方终端注册的移动交换中心服务器发送的寻呼请求消息； 当所述被叫方终端处于连接状态时， 向所述被叫方终端发送寻呼通知消 息， 并向所述移动交换中心服务器返回被叫方终端的寻呼状态消息。
本发明实施例提供了一种信息显示方法， 包括：
接收寻呼通知消息， 所述寻呼通知消息中携带有业务类型标识； 显示第一提示信息， 所述第一提示信息用于指示用户确认是否接受电路 域回落流程；
获取所述用户根据所述第一提示信息输入的第一指令；
根据所述第一指令触发执行电路域回落流程；
根据所述业务类型标识和所述第一指令显示第二提示信息， 所述第二提 示信息用于指示所述用户确认是否接通呼叫；
获取所述用户根据所述第二提示信息输入的第二指令；
根据所述第二指令向移动交换中心服务器返回连接消息接通呼叫， 或执 行所述业务类型标识对应的操作流程。
本发明实施例还提供了一种移动管理装置， 包括：
第一接收模块， 用于接收被叫方终端注册的移动交换中心服务器发送的 寻呼请求消息；
通知模块， 用于所述第一接收模块接收到寻呼请求消息后， 当所述被叫 方终端处于连接状态时， 向所述被叫方终端发送寻呼通知消息， 并向所述移 动交换中心服务器返回被叫方终端的寻呼状态消息。
本发明实施例还提供了一种移动交换中心服务器， 包括：
第二接收模块， 用于接收移动管理装置返回的被叫方终端的寻呼状态消 息；
处理模块， 用于所述第二接收模块接收到寻呼状态消息后， 延长等待所 述被叫方终端返回寻呼响应消息的时间。
本发明实施例还提供了一种终端， 包括：
第三接收模块， 用于接收寻呼通知消息， 所述寻呼通知消息中携带有业 务类型标识；
第一显示模块， 用于所述第三接收模块接收到寻呼通知消息后， 显示第 一提示信息，所述第一提示信息用于指示用户确认是否接受电路域回落流程； 第一获取模块， 用于获取所述用户根据所述第一提示信息输入的第一指 令；
第一执行模块， 用于根据所述第一指令触发执行电路域回落流程； 第二显示模块， 用于根据所述业务类型标识和所述第一指令显示第二提 示信息， 所述第二提示信息用于指示所述用户确认是否接通呼叫；
第二获取模块， 用于获取所述用户根据所述第二提示信息输入的第二指 令；
第二执行模块， 用于根据所述第二指令向移动交换中心服务器返回连接 消息接通呼叫， 或执行所述业务类型标识对应的操作流程。 本发明实施例又提供了一种寻呼处理***， 包括移动交换中心服务器和 移动管理装置， 其中
所述移动交换中心服务器用于向所述移动管理装置发送寻呼请求消息， 以及接收所述移动管理装置返回的被叫方终端的寻呼状态消息， 并延长等待 被叫方终端返回寻呼响应消息的时间；
所述移动管理装置用于接收所述移动交换中心服务器发送的寻呼请求消 息， 当所述被叫方终端处于连接状态时， 向所述被叫方终端发送寻呼通知消 息， 并向所述移动交换中心服务器返回被叫方终端的寻呼状态消息。
由上述技术方案可知， 本发明实施例通过 UE注册的 MME在接收到被 叫方 UE注册的 MSC的寻呼请求消息之后，如果发现被叫方 UE处于连接状 态， 则 MME向被叫方 UE发送 CS域寻呼通知消息的， 还可以向 MSC返回 寻呼状态消息， 以向 MSC指示被叫方 UE 已经收到寻呼通知消息， 提高了 UE注册的 MSC向当前在 E-UTRAN侧处于连接状态的 UE发起寻呼的成功 率。 附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案， 下面将对实 施例或现有技术描述中所需要使用的附图作简单地介绍， 显而易见地， 下面 描述中的附图仅仅是本发明的一些实施例， 对于本领域普通技术人员来讲， 在不付出创造性劳动的前提下， 还可以根据这些附图获得其他的附图。
图 1为本发明实施例一提供的寻呼处理方法的流程示意图；
图 2为本发明实施例二提供的寻呼处理方法的流程示意图；
图 3为本发明实施例三提供的寻呼处理方法的流程示意图；
图 4为本发明实施例四提供的寻呼处理方法的流程示意图；
图 5为本发明实施例五提供的信息显示方法的流程示意图；
图 6为本发明实施例六提供的移动管理装置的结构示意图；
图 7为本发明实施例七提供的移动管理装置的结构示意图；
图 8为本发明实施例八提供的移动交换中心服务器的结构示意图； 图 9为本发明实施例九提供的终端的结构示意图； 图 10为本发明实施例十提供的寻呼处理***的结构示意图。 具体实施方式
下面将结合本发明实施例中的附图， 对本发明实施例中的技术方案进行 清楚、 完整地描述， 显然， 所描述的实施例仅仅是本发明一部分实施例， 而 不是全部的实施例。 基于本发明中的实施例， 本领域普通技术人员在没有作 出创造性劳动前提下所获得的所有其他实施例 , 都属于本发明保护的范围。
由于 CS域回落方案中不同的目标 CS域***对 CS域回落方案的整体架 构和本发明的思想没有影响， 为了简化描述， 以 UE通过 UTRAN接入 CS 域核心网与 UE通过 E-UTRAN接入 EPC之间的 CS域回落为例描述发明实 施例的技术方案。
图 1 为本发明实施例一提供的寻呼处理方法的流程示意图， 本实施例中 的被叫方 UE当前通过 E-UTRAN接入 EPC,被叫方 UE注册的 MME (被叫 方 MME ) 与被叫方 UE注册的 MSC (被叫方 MSC ) 已经通过 SGs接口建 立关联， 如图 1所示， 本实施例可以包括以下步骤：
步骤 101、 MME接收被叫方 MSC发送的寻呼请求消息；
步骤 102、 当被叫方 UE处于连接状态时， MME向被叫方 UE发送寻呼 通知消息， 并向被叫方 MSC返回被叫方 UE的寻呼状态消息。
本实施例中， MME在接收到被叫方 UE注册的 MSC的寻呼请求消息之 后， 如果发现被叫方 UE处于连接状态， 则 MME除了向被叫方 UE发送 CS 域寻呼通知消息， 还向 MSC返回寻呼状态消息， 以向 MSC指示被叫方 UE 已经收到寻呼通知消息，从而避免了 MSC在被叫方 UE等待用户确认是否执 行 CS域回落流程期间错误地判断为在 E-UTRAN侧寻呼被叫方 UE失败而 进行相应错误处理的情况发生， 提高了呼叫的成功率。
图 2为本发明实施例二提供的寻呼处理方法的流程示意图， 本实施例中 的被叫方 UE当前通过 E-UTRAN接入 EPC, 被叫方 UE注册的 MME与被 叫方 UE注册的 MSC已经通过 SGs接口建立关联， 如图 2所示， 本实施例 可以包括以下步骤：
步骤 201、 被叫方 UE注册的 MSC接收到主叫方发送的 IAM, 该 IAM 消息中携带有被叫方 UE的移动台 ISDN号 ( Mobile Station ISDN号， 简称 MSISDN ), MSC根据 IAM消息中所携带的被叫方 UE的 MSISDN查找被叫 方 UE 的上下文， 得到被叫方 UE对应的国际移动用户标识 （International Mobile Subscriber Identity, 简称 IMSI ),通过 SGs接口向被叫方 UE注册的 MME发送寻呼请求消息， 该寻呼请求消息中携带有被叫方 UE的 IMSI。
其中， 上述 IAM还可能会携带有主叫方 UE的标识信息， 例如： 主叫方 UE的 MSISDN ,则上述寻呼请求消息中会相应地携带有主叫方 UE的标识信 息；
步骤 202、 MME接收到寻呼请求消息， 根据寻呼请求消息中所携带的被 叫方 UE的 IMSI查找被叫方 UE的上下文， 根据被叫方 UE的上下文中记录 的状态判断被叫方 UE处于连接状态时，通过非接入层（ Non Access Stratum , 简称 NAS ) 消息向被叫方 UE发送 CS域寻呼通知消息。
若在步骤 201 中 MSC所发送的寻呼请求消息中携带有主叫方 UE的标 识信息， 即 MME从 MSC获取了主叫方 UE的标识信息， 例如： 主叫方 UE 的 MSISDN , 则本步骤中 MME可以将主叫方 UE的 MSISDN包含在 CS域 寻呼通知消息中；
步骤 203、 MME向 MSC返回被叫方 UE的寻呼状态消息， 以通知 MSC 被叫方 UE已经收到寻呼通知消息并启动了一个人机交互程序；
步骤 204、 MSC接收到寻呼状态消息， 延长等待被叫方 UE的 CS域寻 呼响应的时间，并根据预设策略向主叫方 UE注册的 MSC返回 CS域呼叫链 路建立的被叫振铃消息即地址完成消息（ Address Complete Message , 简称 ACM ), 以供主叫方 UE注册的 MSC向主叫方 UE转发该被叫振铃消息； 步骤 205、 被叫方 UE接收到 CS域寻呼通知消息， 根据预先设置的 CS 域回落配置信息显示提示信息， 以请求用户确认是否执行 CS域回落流程。
若在步骤 202中 MME所发送的 CS域寻呼通知消息中携带有主叫方 UE 的标识信息， 即被叫方 UE从 MME获取了主叫方 UE的标识信息， 例如： 主 叫方 UE的 MSISDN , 则本步骤中被叫方 UE可以在提示信息中包含主叫方 UE的 MSISDN;
步骤 206、 被叫方 UE获取到用户输入的执行命令即中断当前数据业务、 进行语音业务的命令， UE记录用户的选择，并向 eNB发送服务请求（ Service Request ) 消息；
步骤 207、 eNB接收到服务请求消息， 向 MME转发该服务请求消息； 步骤 208、 MME接收到服务请求消息， 发起 CS域回落流程。
至此， 被叫方 UE切换到 CS域， 建立 CS域呼叫链路接听电话， 以及将 当前的 PS承载切换到 UTRAN侧并挂起。
需要说明的是，本实施例步骤 201 中， MSC还可能通过其他能够唯一标 识被叫方 UE的其它类型的标识信息， 例如： 电路域中 UE的临时移动台标 识（ Temporary Mobile Station Identity,简称 TMSI )、 EPS网络中 UE的 MME 临时移动台标识 （ MME Temporary Mobile Station Identity, 简称 M-TMSI ) 等标识， 对此本发明实施例不做限制。
本实施例中 MSC在步骤 204之前一直处于等待被叫方 UE响应寻呼的 状态， MSC可以将两种消息作为对其向 MME发出的寻呼请求消息的合法响 应：
a )被叫方 UE的用户选择"接受" CS域回落： 被叫方 UE在 CS域一侧发 起服务请求， MSC将在 CS域一侧收到的服务请求消息作为寻呼响应；
b )被叫方 UE的用户选择"拒绝" CS域回落， 或者在设定的时间内 （例 如 20秒）没有进行确认，即既没有选择 "接受 "CS域回落，也没有选择"拒绝" CS 域回落： 被叫方 UE向 MME发送拒绝接听消息， MME通过 SGs接口通知 MSC被叫方 UE的用户拒绝接听电话， MSC按照寻呼失败或者用户拒接向 主叫方返回响应。
本发明实施例中被叫方 UE响应 CS域寻呼， 如无特殊说明， 是指正常 情况下被叫方 UE的用户选择"接受" CS域回落， 被叫方 UE切换到 2/3G接 入网， 在 CS域一侧向 MSC发送服务请求消息作为 CS域寻呼应答的情况。
本实施例步骤 204中 MSC接收到寻呼状态消息之后， 可以根据预设策 略向主叫方返回被叫振铃消息。 其中的预设策略可以为 MSC 立即向主叫方 UE注册的 MSC发送该被叫振铃消息。 预设策略也可以为在预设时间段之后 向主叫方 UE注册的 MSC转发该被叫振铃消息， 例如： MSC可以启动一个 12 秒寻呼等待定时器。 如果寻呼等待定时器超时之后仍然没有收到被叫方 UE的 CS域寻呼应答， MSC则向主叫方发送被叫振铃消息， 同时继续等待 被叫方 UE的 CS域寻呼应答。 如果在寻呼等待定时器超时之前收到了被叫 方 UE的 CS域寻呼应答， MSC则可以停止寻呼等待定时器， 与被叫方 UE 建立 CS域呼叫链路， 向主叫方返回被叫振铃消息。
本实施例步骤 203可以有两种执行方式： 一种为执行步骤 202之后立即 执行； 另一种为执行步骤 202之后， 启动一个定时器， 在该定时器超时之后 再执行。 例如一个 10秒等待定时器， 该定时器时长应该小于 MSC的寻呼等 待定时器和主叫方 UE注册的 MSC和主叫方 UE的用户通常等待被叫振铃消 息的时长。 当 MME上该等待定时器超时之后， 仍然没有收到被叫方 UE接 受或者拒绝 CS域回落流程的响应时， MME才向 MSC发送寻呼状态消息， MSC收到寻呼状态消息后， 知道尽管长时间没有接收到被叫方 UE的 CS域 寻呼响应， 但被叫方 UE实际上已经收到 CS域寻呼通知消息， 正在等待其 用户确认或者正在 CS域回落流程的发起过程中， MSC延长等待被叫方 UE 的 CS域寻呼响应的时间， 并根据预设策略向主叫方返回 CS域呼叫链路建 立的被叫振铃消息。
可替换地，本实施例步骤 203还可以与步骤 202中的 MME向被叫方 UE 发送 CS域寻呼通知消息的步骤同时执行， 能够达到同样效果。
通常情况下， MSC上寻呼等待定时器 (包括重发） 的时长取决于 MSC 等待 UE响应寻呼消息的时长与 MSC的寻呼重发次数，例如： MSC等待 UE 响应寻呼消息的时长为 5秒， MSC的寻呼重发次数为 3次， 则该寻呼等待定 时器的时长则为 15秒，如果定时器超时后仍然没有收到被叫方 UE返回的寻 呼响应，现有技术中 MSC会认为在 E-UTRAN侧寻呼 UE不成功而中止本次 呼叫， 向主叫方返回错误消息； 或者认为被叫方 UE不在 E-UTRAN覆盖区 内， 转而在 UTRAN—侧重新寻呼该被叫方 UE, 而此时被叫方 UE实际上是 在 E-UTRAN 覆盖区内， 上述重新在 UTRAN 侧寻呼被叫方 UE 既增大了 UTRAN侧的无线负荷， 又不可能成功寻呼到该被叫方 UE。 同时由于主叫方 U E的用户可能很长时间听不到接续音，很可能认为网络出现了故障而主动中 止本次呼叫。
本实施例中的 MSC由于在接收到被叫方 UE的寻呼响应之前已经得到了 MME返回的被叫方 UE的寻呼状态消息， 提前获取了 CS域寻呼请求消息已 经成功递交到处于连接态的被叫方 UE,只是被叫方 UE的用户可能还没有确 认是否执行 CS域回落流程或者已经确认是否执行 CS域回落流程， 但相应 的 CS域寻呼响应或拒绝消息还没有到达 MSC。 因此 MSC可以继续等待被 叫方 UE的寻呼响应而不是终止呼叫或者转向 2/3G接入网络进行寻呼，并且 MSC可以在 UE不能及时响应 CS寻呼请求时适时向主叫方提前发送被叫振 铃消息， 避免了主叫用户主动终止呼叫， 提高了通话成功率。
本实施例中， MME在接收到 MSC的寻呼请求消息之后， 如果发现被叫 方 UE处于连接状态， 则除了向被叫方 UE发送 CS域寻呼通知消息，还可以 向 MSC返回寻呼状态消息， 以向 MSC指示被叫方 UE已经收到寻呼通知消 息，从而避免了 MSC在被叫方 UE等待用户确认是否执行 CS域回落流程期 间错误地判断为在 E-UTRAN侧寻呼被叫方 UE失败而进行相应错误处理的 情况发生， 提高了呼叫的成功率。 MSC还可以根据一定的策略向主叫方返回 被叫振铃消息， 从而避免了主叫方 UE的用户在被叫方 UE等待用户确认是 否执行 CS域回落流程期间错误地判断被叫方无响应而结束呼叫的情况发生。
图 3为本发明实施例三提供的寻呼处理方法的流程示意图， 本实施例中 的被叫方 UE当前通过 E-UTRAN接入 EPC, 被叫方 UE注册的 MME与被 叫方 UE注册买的 MSC已经通过 SGs接口建立关联， 如图 3所示， 本实施 例可以包括以下步骤：
步骤 301、 被叫方 UE注册的 MSC接收到主叫方发送的 IAM, 该 IAM 消息中携带有被叫方 UE的 MSISDN , MSC根据 IAM消息中所携带的被叫 方 UE的 MSISDN查找被叫方 UE的上下文， 得到被叫方 UE对应的 IMSI , 通过 SGs接口向被叫方 UE注册的 MME发送寻呼请求消息， 该寻呼请求消 息中携带有被叫方 UE的 IMSI。
其中， 上述 IAM还可能会携带有主叫方 UE的标识信息， 例如： 主叫方
UE的 MSISDN ,则上述寻呼请求消息中会相应地携带有主叫方 UE的标识信 息；
步骤 302、 MME接收到寻呼请求消息， 根据寻呼请求消息中所携带的被 叫方 UE的 IMSI查找被叫方 UE的上下文， 根据被叫方 UE的上下文中记录 的状态判断被叫方 UE处于连接状态时， 通过 NAS层消息向被叫方 UE发送 CS域寻呼通知消息。
若在步骤 301 中 MSC所发送的寻呼请求消息中携带有主叫方 UE的标 识信息， 即 MME从 MSC获取了主叫方 UE的标识信息， 例如： 主叫方 UE 的 MSISDN , 则本步骤中 MME可以将主叫方 UE的 MSISDN包含在 CS域 寻呼通知消息中；
步骤 303、 被叫方 UE接收到 CS域寻呼通知消息， 根据预先设置的 CS 域回落配置信息确定显示提示信息， 以请求用户确认是否执行 CS域回落流 程， 并向 MME返回等待指示消息， 以通知 MME启动了人机交互程序。
若在步骤 302中 MME所发送的 CS域寻呼通知消息中携带有主叫方 UE 的标识信息， 即被叫方 UE从 MME获取了主叫方 UE的标识信息， 例如： 主 叫方 UE的 MSISDN , 则本步骤中被叫方 UE可以在提示信息中包含主叫方 UE的 MSISDN;
步骤 304、 MME接收到等待指示消息， 向 MSC返回被叫方 UE的寻呼 状态消息，以通知 MSC被叫方 UE已经收到寻呼通知消息并启动了一个人机 交互程序；
步骤 305、 MSC接收到寻呼状态消息， 延长等待被叫方 UE的 CS域寻 呼响应的时间，并根据预设策略向主叫方 UE注册的 MSC返回 CS域呼叫链 路建立的被叫振铃消息即 ACM, 以供 MSC向主叫方 UE转发；
步骤 306、 被叫方 UE接收到 CS域寻呼通知消息， 根据预先设置的 CS 域回落配置信息显示提示信息， 以请求用户确认是否执行 CS域回落流程； 步骤 307、 被叫方 UE获取到用户输入的执行命令即中断当前数据业务、 进行语音业务的命令， UE记录用户的选择， 并向 eNB发送服务请求消息； 步骤 308、 eNB接收到服务请求消息， 向 MME转发该服务请求消息； 步骤 309、 MME接收到服务请求消息， 发起 CS域回落流程。
至此， 被叫方 UE切换到 CS域， 建立 CS域呼叫链路接听电话， 以及将 当前的 PS承载切换到 UTRAN侧并挂起。
本实施例步骤 303中 CS域回落配置信息可以为"总是优先接听电话"， 那么被叫方 UE接收到 CS域寻呼通知消息时则确定可以不显示提示信息， 而直接确认执行 CS域回落流程； CS域回落配置信息也可以为"总是请求用 户确认 "，那么被叫方 UE接收到 CS域寻呼通知消息时则确定显示提示信息， 以请求用户确认是否执行 CS域回落流程； CS域回落配置信息还可以为"当 UE进行某些不宜中断的分组业务（在线视频、 游戏等）时， 请求用户确认"， 那么被叫方 UE在进行不可中断的分组业务的过程中接收到 CS域寻呼通知 消息时则确定显示提示信息， 以请求用户确认是否执行 CS域回落流程； CS 域回落配置信息还可以为"对特定白名单上的主叫方 UE,总是优先接听电话； 或者对特定黑名单上的主叫方 UE,总是拒绝接听电话；或者即不在白名单上， 也不在黑名单上的其他主叫方 UE, 请求用户确认"， 那么被叫方 UE接收到 特定白名单上的主叫方 UE触发的 CS域寻呼通知消息时则确定可以不显示 提示信息， 而直接确认执行 CS域回落流程， 被叫方 UE接收到特定黑名单 上的主叫方 UE触发的 CS域寻呼通知消息时则可以不显示提示信息， 而直 接拒绝 CS域回落流程，被叫方 UE接收到其他主叫方 UE触发的 CS域寻呼 通知消息时确定显示提示信息， 以请求用户确认是否执行 CS域回落流程。 当被叫方 UE确定显示提示信息时，被叫方 UE则向 MME返回等待指示消息 的用途是通知 MME被叫方 UE启动了一个人机交互程序，无论被叫方 UE的 用户确认执行 CS域回落流程还是拒绝 CS域回落流程都可能需要较长的处 理时间才能响应 MSC的寻呼请求。若被叫方 UE确定可以不显示提示信息时， 被叫方 UE则直接确认执行 CS域回落流程还是拒绝 CS域回落流程，则本步 骤中被叫方 UE可以不向 MME返回等待指示消息而直接开始 CS域回落流 程，在没有接收到 UE的等待指示消息时， MME不会向 MSC返回被叫方 UE 的寻呼状态消息。
当然上述本实施例的技术方案并不排斥被叫方 UE在收到 MME的 CS域 寻呼请求消息后， 在确定不显示提示信息时， 也会向 MME发送等待指示消 息。
与本发明实施例二类似， 本实施例步骤 304可以有两种执行方式： 一种 为 MME接收到等待指示消息立即向 MSC返回被叫方 UE的寻呼状态消息； 另一种为 MME接收到等待指示消息之后， 启动一个定时器， 在该定时器超 时之后再向 MSC返回被叫方 UE的寻呼状态消息， 此处不再赘述。 与本发明实施例二相比，本实施例中的 MME在向 MSC返回 UE寻呼状 态消息之前， 与被叫方 UE进行了协商， 即 MME根据获取到的被叫方 UE所 反馈的等待指示消息， 若 MME确定被叫方 UE通过启动人机交互程序以向 用户确认是否执行 CS域回落流程之后， MME再向 MSC返回被叫方 UE的 寻呼状态消息， 以指示被叫方 UE的寻呼状态的相关信息； 若 MME确定被 叫方 UE不会启动人机交互程序以向用户确认是否执行 CS域回落流程之后， MSC则按正常的流程等待正常的寻呼响应即可，不需要延长寻呼响应等待时 间， 或者执行提前向主叫方响应被叫振铃消息的处理步骤。
在本发明实施例三中提到当前在 E-UTRAN测处于连接状态的 UE接收 到 MME发送的 CS域寻呼通知消息之后， 可以根据其上的配置和分组业务 状态确定是否需要显示提示信息请用户确认是否需要执行 CS域回落流程， 但这样引入一个用户体验的问题， 假如 UE的用户确认执行 CS域回落流程， 按照现有 CS域电话的经验， 用户会认为已经接听了电话。 但是， 有些 CS 域的补充业务， 被叫方 UE的用户并不能仅凭主叫方 UE的电话号码就判断 是否要接听该电话，例如：呼叫前转（ Call Forwarding )业务、呼叫转向（ Call Deflection )业务等。
在呼叫前转业务中，主叫方 UE的用户 A拨打电话到用户 B,用户 B (前 转方） 的业务数据设置为将呼叫前转至用户 C, 则用户 C的 UE上显示的提 示信息为主叫用户信息即用户 A的电话号码。但是可能用户 C愿意接听用户 A的电话， 但并不愿意接听任何用户 B前转的电话， 如果在请求被叫用户 C 确认 CS域回落时必须确认直接接听该电话， 那么就剥夺了被叫用户在呼叫 前转业务中根据前转方信息选择接听的权利。在呼叫转向业务中，主叫方 UE 的用户 A拨打电话到用户 B, 用户 B在 UE振铃后， 通过在 UE上输入用户 C的 MSISDN将该呼叫前转至用户 C。 呼叫转向与呼叫前转业务的区别是： 呼叫转向业务需要中间用户 B在选择"接受"通话前输入最终用户 C的电话号 码， 并确认执行呼叫转向； 呼叫转向业务从用户 A到达用户 B是是一个普通 的呼叫， 因此 MSC在用户 B操作之前无法判断用户 B是否会发起呼叫转向 操作。 由于呼叫转向操作必须在 UE和 MSC之间进行交互，如果在请被叫方 UE的用户确认 CS域回落时只提供"接听"和"拒绝"该语音呼叫两个操作选项， 不能提供呼叫转向操作选项， 那么在 CS域回落方案下就剥夺了用户使用呼 叫转向业务的权利。
图 4为本发明实施例四提供的寻呼处理方法的流程示意图， 本实施例中 的被叫方 UE当前通过 E-UTRAN接入 EPC, 被叫方 UE注册的 MME与被 叫方 UE注册买的 MSC已经通过 SGs接口建立关联， 如图 4所示， 本实施 例可以包括以下步骤：
步骤 401、 被叫方 UE注册的 MSC接收到主叫方发送的 IAM, 该 IAM 消息中携带有被叫方 UE的 MSISDN , MSC根据 IAM消息中所携带的被叫 方 UE的 MSISDN查找被叫方 UE的上下文， 得到被叫方 UE对应的 IMSI , 通过 SGs接口向被叫方 UE注册的 MME发送寻呼请求消息， 该寻呼请求消 息中携带有被叫方 UE的 IMSI , 以及业务类型标识。
其中的业务类型标识可以是表示普通语音呼叫、 以及各种具体的补充业 务等类型例如： 呼叫前转业务等， 注意如前所述被叫用户是否发起呼叫转向 业务， 完全取决于被叫用户的操作， 此时 MSC之前作为一个普通呼叫处理。 因此该业务类型标识不会表示呼叫转向业务。 在后续的流程中， 被叫方 UE 可以根据上述业务类型标识所表示的具体业务类型， 以及根据自身的配置信 息， 确定对该业务类型是否需要在被叫方 UE切换到 CS域一侧后， 再次显 示提示信息， 以请被叫方 UE的用户确认是否接听电话。
该业务类型标识还可以直接就是一个指示是否需要再次显示提示信息的 标识， 即 MSC对业务的具体类型等相关信息进行判断后， 直接指示是否需 要在被叫方 UE切换到 CS域一侧后，再次显示提示信息， 以请被叫方 UE的 用户确认是否接听电话， 例如： 对普通语音呼叫， 生成一个表示不需再次提 示的标识； 对呼叫前转类型的业务， 生成一个表示需要再次提示的标识。
其中， 上述 IAM还可能会携带有主叫方 UE的标识信息， 例如： 主叫方 UE的 MSISDN ,则上述寻呼请求消息中会相应地携带有主叫方 UE的标识信 息；
步骤 402、 MME接收到寻呼请求消息， 根据寻呼请求消息中所携带的被 叫方 UE的 IMSI查找被叫方 UE的上下文， 根据被叫方 UE的上下文中记录 的状态判断被叫方 UE处于连接状态时， 通过 NAS层消息向被叫方 UE发送 cs域寻呼通知消息。
若在步骤 401 中 MSC所发送的寻呼请求消息中携带有主叫方 UE的标 识信息、 业务类型标识等呼叫的相关信息， 即 MME从 MSC获取了主叫方 UE的标识信息、 业务类型标识等呼叫的相关信息， 则本步骤中 MME可以将 上述相关信息包含在 CS域寻呼通知消息中；
步骤 403、 MME向 MSC返回被叫方 UE的寻呼状态消息， 以通知 MSC 被叫方 UE已经收到寻呼通知消息并启动了一个人机交互程序。
其中， MME可以立即向 MSC返回被叫方 UE的寻呼状态消息， MME 也可以与被叫方 U E协商后，再根据被叫方 U E所返回的等待指示消息向 MSC 返回被叫方 UE的寻呼状态消息， 分别如上述实施例二和实施例三所述， 本 实施例不再赘述；
步骤 404、 MSC接收到寻呼状态消息， 延长等待被叫方 UE的 CS域寻 呼响应的时间， 并根据预设策略向主叫方返回 CS域呼叫链路建立的被叫振 铃消息即 ACM;
步骤 405、 被叫方 UE接收到 CS域寻呼通知消息， 根据预先设置的 CS 域回落配置信息、 以及 CS域寻呼通知消息中所携带的业务类型标识显示第 一提示信息， 以请求用户确认是否执行 CS域回落流程， 并根据该业务类型 标识确定第一提示信息内容， 例如：
当 CS域寻呼通知消息中的业务类型为不需要再次确认时，则被叫方 UE 所显示的第一提示信息中没有在接听通话之前用户还需要再次确认的内容， 即提示信息为请求用户确认是否直接接听呼叫， 例如"有 13XXXXXXXXX给 您的呼叫， 是否中断当前 XXXX分组业务， 直接接听本次呼叫？ "， 提供给其 用户的操作选项可以包括"接受"、 "拒绝"， 还可以包括"呼叫转向"。
当 CS域寻呼通知消息中的业务类型为需要再次确认时， 则被叫方 UE 所显示的第一提示信息中含有在接听通话之前用户还需要再次确认的内容， 即提示信息为请求用户确认是否愿意中断当前分组业务， 切换到 CS域， 但 不是直接确认接听该呼叫， 而是需要其用户在切换到 CS域后再次确认， 例 如： "有 13XXXXXXXXX给您的电话， 该通话为前转类型业务， 可能需要您 接收呼叫信息后确认是否接听该呼叫， 是否中断当前 XXXX分组业务， 接收 该呼叫信息？ ", 提供给其用户的操作选项可以包括 "接受"、 "拒绝"； 步骤 406、 被叫方 UE获取到用户根据第一显示信息所输入的第一指令， UE记录用户的选择， 根据该第一指令向 eNB发送服务请求消息；
步骤 407、 eNB接收到服务请求消息， 向 MME转发该服务请求消息； 步骤 408、 MME接收到服务请求消息， 发起 CS域回落流程。
至此， 被叫方 UE切换到 CS域， 建立 CS域呼叫链路。
步骤 409、 被叫方 UE根据上述业务类型标识和第一指令显示第二提示 信息；
步骤 410、 被叫方 U E获取到用户根据第二提示信息所输入的第二指令， 根据该第二指令向 MSC返回连接消息。
本实施例中的业务类型标识若表示需要切换到 CS域后再次确认是否接 听的补充业务， 或者业务类型标识虽然表示普通业务但被叫方 UE 的用户根 据第一提示信息所输入的第一指令为需要再次确认的业务， 如选择了"呼叫转 向"选项， 那么被叫方 UE在 CS域呼叫链路建立后则可以进一步显示第二提 示信息请用户再次确认； 否则不需要显示第二提示信息请用户再次确认， 那 么被叫方 U E在 CS域呼叫链路建立后则可以立即向 MSC应答接受呼叫信令 ( Connect ), 被叫用户可以直接开始通话。
本实施例中， 由于 CS域回落中 PS域切换和在 CS域一侧响应寻呼、建 立 CS呼叫链路等流程需要几秒的时延， 在这期间被叫方 UE的用户与主叫 方 U E的用户之间的 CS呼叫链路尚未接通， 双方不能相互通话， 也就是说 被叫用户听不到主叫用户的声音， 被叫用户说话主叫用户也无法听到。 而现 有的 CS域语音业务中， 被叫用户按下 "接受 "按键后， 由于此前 CS寻呼链路 已经建好， 基本上同时就能够进行通话。 为了避免被叫用户在等待 CS域回 落流程期间由于听不到主叫用户的声音误以为接听通话失败的情况的发生， 在执行 CS域回落流程期间， 被叫方 UE可以播放声音信息， 例如： 特殊的 声效， 以提示被叫方 UE的用户本次通话正在处理过程中， 在音效结束前不 必尝试通话。 为了进一步给被叫方 UE的用户更清晰的提示， 被叫方 UE对 不需要再次确认和需要再次确认的两种寻呼， 可以播放不同的声音信息。
由于 MSC发送给 MME的寻呼请求消息要求尽量简单，一般只携带被叫 方 UE的标识信息，主叫方 UE的标识信息等通用的呼叫信息， 而各种 CS域 补充业务的呼叫相关的特殊信息很多， 如呼叫前转业务的前转方标识， 而切 换到 CS域后，被叫方 UE在 CS域一侧在呼叫链路建立过程中从 MSC获取 的呼叫相关业务信息是完整的， 在显示第二提示信息则可以选择更加丰富的 信息内容， 从而使得被叫方 UE的用户可以更加准确的判断是否愿意接听该 呼叫。
例如： 对于呼叫前转业务， 被叫方 UE 的用户可以根据显示的前转方号 码判断是否愿意接听该寻呼； 又比如， 在由于切换到 CS后被叫方 UE直接 与 MSC按照原有 CS呼叫流程交互， 可以为被叫方 UE的用户提供除了"接 受 /拒绝"二元选择之外的其它操作选择， 与原来 CS 域业务处理逻辑保持一 致， 以提供相同的业务能力， 例如： 呼叫转向业务， 被叫方 UE的用户可以 选择另一个新号码将呼叫前转到这个号码。
本实施例中根据 MSC的业务类型标识确定在 E-UTRAN侧显示的第一提 示信息的内容和操作选项， 并根据 MSC 的业务类型标识， 以及用户针对第 一次提示信息选择的操作选项确定被叫方 UE切换到 CS域一侧之后是否需 要显示第二提示信息以请用户再次确认， 从而使得 CS域回落方案中用户的 使用体验与原 CS域业务尽量保持一致， 同时实现了被叫方 UE的用户对 CS 域补充业务的操作选项与原来 CS域业务一致。
图 5为本发明实施例五提供的信息显示方法的流程示意图，本实施例中的 被叫方 UE当前通过 E-UTRAN接入 EPC, 被叫方 UE注册的 MME与被叫方 UE 注册的 MSC已经通过 SGs接口建立关联， 如图 5所示， 本实施例可以包括以 下步骤：
步骤 501、 被叫方 UE接收寻呼通知消息， 该寻呼通知消息中携带有业务 类型标识。
其中的业务类型标识可以是表示普通语音呼叫、 以及各种具体的补充业 务等类型例如： 呼叫前转业务等， 注意如前所述被叫用户是否发起呼叫转向 业务， 完全取决于被叫用户的操作， 此时 MSC之前作为一个普通呼叫处理。 因此该业务类型标识不会表示呼叫转向业务。 在后续的流程中， 被叫方 UE 可以根据上述业务类型标识所表示的具体业务类型， 以及根据自身的配置信 息， 确定对该业务类型是否需要在被叫方 UE切换到 CS域一侧后， 再次显 示提示信息， 以请被叫方 UE的用户确认是否接听电话。
该业务类型标识还可以直接就是一个指示是否需要再次显示提示信息的 标识， 即 MSC对业务的具体类型等相关信息进行判断后， 直接指示是否需 要在被叫方 UE切换到 CS域一侧后，再次显示提示信息， 以请被叫方 UE的 用户确认是否接听电话， 例如： 对普通语音呼叫， 生成一个表示不需再次提 示的标识； 对呼叫前转类型的业务， 生成一个表示需要再次提示的标识。
步骤 502、被叫方 UE根据预先设置的 CS域回落配置信息、 以及 CS域 寻呼通知消息中所携带的业务类型标识显示第一提示信息， 该第一提示信息 用于指示用户确认是否接受行 CS域回落流程， 并根据该业务类型标识确定 第一提示信息内容， 例如：
当 CS域寻呼通知消息中的业务类型为不需要再次确认时，则被叫方 UE 所显示的第一提示信息中没有在接听通话之前用户还需要再次确认的内容， 即提示信息为请求用户确认是否直接接听呼叫， 例如"有 13XXXXXXXXX给 您的呼叫， 是否中断当前 XXXX分组业务， 直接接听本次呼叫？ "， 提供给其 用户的操作选项可以包括"接受"、 "拒绝"， 还可以包括"呼叫转向"。
当 CS域寻呼通知消息中的业务类型为需要再次确认时， 则被叫方 UE所 显示的第一提示信息中含有在接听通话之前用户还需要再次确认的内容， 即 提示信息为请求用户确认是否愿意中断当前分组业务， 切换到 CS域， 但不是 直接确认接听该呼叫， 而是需要其用户在切换到 CS域后再次确认， 例如： "有 13XXXXXXXXX给您的电话， 该通话为前转类型业务， 可能需要您接收呼叫 信息后确认是否接听该呼叫， 是否中断当前 XXXX分组业务， 接收该呼叫信 息？ "， 提供给其用户的操作选项可以包括 "接受"、 "拒绝"；
步骤 503、 被叫方 UE获取用户根据第一提示信息输入的第一指令； 步骤 504、 被叫方 UE根据第一指令触发执行电路域回落流程；
步骤 505、 被叫方 UE根据上述业务类型标识和第一指令显示第二提示信 息， 该第二提示信息用于指示用户确认是否接通呼叫；
步骤 506、 被叫方 UE获取用户根据第二提示信息输入的第二指令； 步骤 507、 被叫方 UE根据上述第二指令向 MSC返回连接消息接通呼叫， 或执行所述业务类型标识对应的操作流程。
本实施例中的业务类型标识若表示需要切换到 CS域后再次确认是否接 听的补充业务， 或者业务类型标识虽然表示普通业务但被叫方 UE 的用户根 据第一提示信息所输入的第一指令为需要再次确认的业务， 如选择了"呼叫转 向"选项， 那么被叫方 UE在 CS域呼叫链路建立后则可以进一步显示第二提 示信息请用户再次确认； 否则不需要显示第二提示信息请用户再次确认， 那 么被叫方 U E在 CS域呼叫链路建立后则可以立即向 MSC应答接受呼叫信令 ( Connect ), 被叫用户可以直接开始通话。
本实施例中， 由于 CS域回落中 PS域切换和在 CS域一侧响应寻呼、建 立 CS呼叫链路等流程需要几秒的时延， 在这期间被叫方 UE的用户与主叫 方 UE的用户之间的 CS呼叫链路尚未接通， 双方不能相互通话， 也就是说 被叫用户听不到主叫用户的声音， 被叫用户说话主叫用户也无法听到。 而现 有的 CS域语音业务中， 被叫用户按下 "接受 "按键后， 由于此前 CS寻呼链路 已经建好， 基本上同时就能够进行通话。 为了避免被叫用户在等待 CS域回 落流程期间由于听不到主叫用户的声音误以为接听通话失败的情况的发生， 在执行 CS域回落流程期间， 被叫方 UE可以播放声音信息， 例如： 特殊的 声效， 以提示被叫方 UE的用户本次通话正在处理过程中， 在音效结束前不 必尝试通话。 为了进一步给被叫方 UE的用户更清晰的提示， 被叫方 UE对 不需要再次确认和需要再次确认的两种寻呼， 可以播放不同的声音信息。
本实施例中被叫方 UE 所接收到的寻呼通知消息是由于 MSC 发送给
MME的寻呼请求消息所触发的， 由于 MSC发送给 MME的寻呼请求消息要 求尽量简单， 一般只携带被叫方 UE的标识信息， 主叫方 UE的标识信息等 通用的呼叫信息， 而各种 CS域补充业务的呼叫相关的特殊信息很多， 如呼 叫前转业务的前转方标识， 而切换到 CS域后，被叫方 UE在 CS域一侧在呼 叫链路建立过程中从 MSC 获取的呼叫相关业务信息是完整的， 在显示第二 提示信息则可以选择更加丰富的信息内容， 从而使得被叫方 UE的用户可以 更加准确的判断是否愿意接听该呼叫。
例如： 对于呼叫前转业务， 被叫方 UE 的用户可以根据显示的前转方号 码判断是否愿意接听该寻呼； 又比如， 在由于切换到 CS后被叫方 UE直接 与 MSC按照原有 CS呼叫流程交互， 可以为被叫方 UE的用户提供除了"接 受 /拒绝"二元选择之外的其它操作选择， 与原来 CS 域业务处理逻辑保持一 致， 以提供相同的业务能力， 例如： 呼叫转向业务， 被叫方 UE的用户可以 选择另一个新号码将呼叫前转到这个号码。
本实施例中根据 MSC的业务类型标识确定在 E-UTRAN侧显示的第一提 示信息的内容和操作选项， 并根据 MSC 的业务类型标识， 以及用户针对第 一次提示信息选择的操作选项确定被叫方 UE切换到 CS域一侧之后是否需 要显示第二提示信息以请用户再次确认， 从而使得 CS域回落方案中用户的 使用体验与原 CS域业务尽量保持一致， 同时实现了被叫方 UE的用户对 CS 域补充业务的操作选项与原来 CS域业务一致。
图 6为本发明实施例六提供的移动管理装置的结构示意图， 如图 6所示， 本实施例可以包括相互连接的第一接收模块 61和通知模块 62。 其中， 第一接 收模块 61接收到被叫方 UE注册的移动交换中心服务器发送的寻呼请求消息， 该寻呼请求消息中可以携带有被叫方 UE的标识信息 (例如： 被叫方 UE的 IMSI ), 当所述被叫方 UE处于连接状态时， 通知模块 62根据第一接收模块 61 接收的寻呼请求消息向被叫方 UE发送寻呼通知消息， 并向移动交换中心服务 器返回被叫方 UE的寻呼状态消息， 以通知所述被叫方 UE已接收到所述寻呼 通知消息。
本实施例提供的移动管理装置可以认为是 EPS中的 MME。 MME的第一接 收模块在接收到被叫方 UE注册的 MSC的寻呼请求消息之后，通知模块如果发 现被叫方 UE处于连接状态， 则除了向被叫方 UE发送 CS域寻呼通知消息， 还 可以同时或者等待一定时长仍未收到被叫方 UE返回的 CS域回落接受或拒绝 消息时， 向 MSC返回寻呼状态消息， 以向 MSC指示被叫方 UE已经收到寻呼 通知消息， 从而避免了 MSC在被叫方 UE等待用户确认是否执行 CS域回落流 程期间错误地判断为在 E-UTRAN侧寻呼被叫方 UE失败而进行相应错误处理 的情况发生， 提高了呼叫的成功率。
图 7为本发明实施例七提供的移动管理装置的结构示意图， 如图 7所示， 与上一实施例相比， 本实施例可以进一步包括触发模块 63, 与通知模块 62连 接， 用于获取被叫方 UE发送的等待指示消息， 以触发通知模块 62向所述移动 交换中心服务器返回被叫方 UE的寻呼状态消息。
与上一实施例相比，本实施例中的通知模块在向 MSC返回 UE寻呼状态 消息之前， 与被叫方 UE 进行了协商， 即触发模块根据获取到的被叫方 UE 所反馈的等待指示消息， 若触发模块确定被叫方 UE通过启动人机交互程序 以向用户确认是否执行 CS 域回落流程之后， 触发模块再触发通知模块向 MSC返回被叫方 UE的寻呼状态消息以指示被叫方 UE的寻呼状态的相关信 息； 若触发模块确定被叫方 UE不会启动人机交互程序以向用户确认是否执 行 CS域回落流程之后， 触发模块则不会触发通知模块向 MSC返回被叫方 UE的寻呼状态消息， 那么 MSC则按正常的流程等待正常的寻呼响应即可， 不需要延长寻呼响应等待时间， 或者执行提前向主叫方响应被叫振铃消息的 处理步骤。
图 8为本发明实施例八提供的移动交换中心服务器的结构示意图， 如图 8 所示， 本实施例可以包括第二接收模块 81和处理模块 82。 其中， 第二接收模 块 81用于接收移动管理装置返回的被叫方终端的寻呼状态消息。 处理模块 82 根据第二接收模块 81接收的寻呼状态消息延长等待被叫方 UE返回寻呼响应 消息的时间。
本实施例提供的移动交换中心服务器可以认为是 CS域一侧的 MSC。通过 MSC接收到 MME返回的寻呼状态消息， 从而获取到了被叫方 UE已经收到寻 呼通知消息， 从而避免了 MSC在被叫方 UE等待用户确认是否执行 CS域回落 流程期间错误地判断为在 E-UTRAN侧寻呼被叫方 UE失败而进行相应错误处 理的情况发生， 提高了呼叫的成功率。
进一步地， 本实施例中的处理模块 82 还可以根据一定的策略向主叫方 UE注册的移动交换中心服务器返回电路域呼叫链路建立的被叫振铃消息。， 从而避免了主叫方 UE的用户在被叫方 UE等待用户确认是否执行 CS域回落 流程期间错误地判断被叫方无响应而结束呼叫的情况发生。
图 9为本发明实施例九提供的终端的结构示意图， 如图 9所示， 本实施例 可以包括第三接收模块 91、 第一显示模块 92、 第一获取模块 93、 第一执行模 块 94、 第二显示模块 95、 第二获取模块 96和第二执行模块 97。 其中， 第三接 收模块 91用于接收寻呼通知消息 ,上述寻呼通知消息中携带有业务类型标识； 第一显示模块 92用于第三接收模块 91接收到寻呼通知消息后， 显示第一提示 信息， 上述第一提示信息用于指示用户确认是否接受电路域回落流程； 第一 获取模块 93用于获取上述用户根据上述第一提示信息输入的第一指令； 第一 执行模块 94用于根据上述第一指令触发执行电路域回落流程； 第二显示模块 95用于根据上述业务类型标识和上述第一指令显示第二提示信息， 上述第二 提示信息用于指示上述用户确认是否接通呼叫； 第二获取模块 96用于获取上 述用户根据上述第二提示信息输入的第二指令； 第二执行模块 97用于根据上 述第二指令向移动交换中心服务器返回连接消息接通呼叫， 或执行上述业务 类型标识对应的操作流程。
本实施例中根据 MSC的业务类型标识确定在 E-UTRAN侧显示的第一提 示信息的内容和操作选项， 并根据 MSC 的业务类型标识， 以及用户针对第 一次提示信息选择的操作选项确定被叫方 UE切换到 CS域一侧之后是否需 要显示第二提示信息以请用户再次确认， 从而使得 CS域回落方案中用户的 使用体验与原 CS域业务尽量保持一致， 同时实现了被叫方 UE的用户对 CS 域补充业务的操作选项与原来 CS域业务一致。
图 10为本发明实施例十提供的寻呼处理***的结构示意图， 如图 10所 示， 本实施例可以包括被叫方 UE 1001、 移动交换中心服务器 1002和移动管 理装置 1003。 其中被叫方 UE 1001分别向移动管理装置 1003和移动交换中心 服务器 1002注册， 以及接收移动管理装置 1003发送的寻呼通知消息。 移动交 换中心服务器 1002向移动管理装置 1003发送寻呼请求消息，该寻呼请求消息 中可以携带有被叫方 UE的标识信息（例如： 被叫方 UE的 IMSI ), 以及接收移 动管理装置 1003返回的被叫方 UE的寻呼状态消息，并根据该寻呼状态消息延 长等待被叫方 UE返回寻呼响应消息的时间。移动管理装置 1003接收移动交换 中心服务器 1002发送的寻呼请求消息， 当被叫方 UE 1001处于连接状态时， 根据寻呼请求消息向被叫方 UE 1001发送寻呼通知消息， 并向移动交换中心 服务器 1002返回被叫方 UE 1001的寻呼状态消息， 以通知被叫方 UE 1001已 接收到上述寻呼通知消息。
本实施例中的移动交换中心服务器 1002可以认为是 CS域一侧的 MSC, 可以为本发明实施例八提供的移动交换中心服务器； 移动管理装置 1003可以 认为是 EPS中的 MME, 可以为本发明实施例六和实施例七提供的任一移动管 理装置；被叫方 UE 1001可以为本发明实施例九提供的终端。本实施例中 MM E 在接收到被叫方 UE注册的 MSC的寻呼请求消息之后， 如果发现被叫方 UE处 于连接状态， 则除了向被叫方 UE发送 CS域寻呼通知消息， 还可以同时或者 等待一定时长仍未收到被叫方 UE返回的 CS域回落接受或拒绝消息时， 向 MSC返回寻呼状态消息， 以向 MSC指示被叫方 UE已经收到寻呼通知消息， 从而避免了 MSC在被叫方 UE等待用户确认是否执行 CS域回落流程期间错误 地判断为在 E-UTRAN侧寻呼被叫方 U E失败而进行相应错误处理的情况发 生， 提高了呼叫的成功率。
进一步地， 本实施例中的被叫方 UE接收到 CS域寻呼通知消息， 还可以 用于显示第一提示信息， 以请求用户确认是否执行 CS域回落流程， 并根据该 业务类型标识确定第一提示信息 （内容和操作选项）， 以及获取被叫方 UE的 用户根据第一提示信息所输入的第一指令， 并根据第一指令触发移动管理装 置执行 CS域回落流程。
其中， 被叫方 UE接收到的 CS域寻呼通知消息中还可以携带有业务类型 标识， 进一步地， 被叫方 UE还可以用于根据业务类型标识和第一指令显示第 二提示信息， 以及获取被叫方 U E的用户根据第二提示信息所输入的第二指 令， 并根据第二指令向所述移动交换中心服务器返回连接消息接通呼叫， 或 执行业务类型标识所代表的业务对应的操作流程。 本实施例中的业务类型标 识若表示需要切换到 CS域后再次确认是否接听的补充业务， 或者业务类型标 识虽然表示普通业务但被叫方 U E的用户根据第一提示信息所输入的第一指 令为需要再次确认的业务， 如选择了"呼叫转向"选项， 那么被叫方 UE在 CS域 呼叫链路建立后则可以进一步显示第二提示信息请用户再次确认； 否则不需 要显示第二提示信息请用户再次确认， 那么被叫方 UE在 CS域呼叫链路建立 后则可以立即向移动交换中心服务器返回连接消息（connect )以应答接受呼 叫信令即直接接通呼叫， 被叫方 UE的用户可以直接开始通话。
本实施例中根据 MSC的业务类型标识确定在 E-UTRAN侧显示的第一提 示信息的内容和操作选项， 并根据 MSC 的业务类型标识， 以及用户针对第 一次提示信息选择的操作选项确定被叫方 UE切换到 CS域一侧之后是否需 要显示第二提示信息以请用户再次确认， 从而使得 CS域回落方案中用户的 使用体验与原 CS域业务尽量保持一致， 同时实现了被叫方 UE的用户对 CS 域补充业务的操作选项与原来 CS域业务一致。
上述本发明实施例中 PS域和 CS域可以是现有各种 PS域和 CS域*** 的组合， 例 口： PS域可以为 GPRS、 UMTS, EPS, WiMax、 CDMA HRPD 等***的 PS域， 而 CS域可以为 GSM ( GERAN )、 WCDMA ( UTRAN )、 CDMA 1xRTT等 CS域***。
本领域普通技术人员可以理解： 实现上述方法实施例的全部或部分步骤 可以通过程序指令相关的硬件来完成， 前述的程序可以存储于一计算机可读 取存储介质中， 该程序在执行时， 执行包括上述方法实施例的步骤； 而前述 的存储介质包括： ROM、 RAM, 磁碟或者光盘等各种可以存储程序代码的介 最后应说明的是： 以上实施例仅用以说明本发明的技术方案， 而非对其 限制； 尽管参照前述实施例对本发明进行了详细的说明， 本领域的普通技术 人员应当理解： 其依然可以对前述各实施例所记载的技术方案进行修改， 或 者对其中部分技术特征进行等同替换； 而这些修改或者替换， 并不使相应技 术方案的本质脱离本发明各实施例技术方案的精神和范围。

Claims

权利 要求
1、 一种寻呼处理方法， 其特征在于， 包括：
接收被叫方终端注册的移动交换中心服务器发送的寻呼请求消息； 当所述被叫方终端处于连接状态时， 向所述被叫方终端发送寻呼通知消 息， 并向所述移动交换中心服务器返回被叫方终端的寻呼状态消息。
2、根据权利要求 1所述的方法， 其特征在于， 所述向所述移动交换中心 服务器返回被叫方终端的寻呼状态消息之前还包括： 获取所述被叫方终端发 送的等待指示消息。
3、根据权利要求 2所述的方法， 其特征在于， 所述向所述移动交换中心 服务器返回被叫方终端的寻呼状态消息包括： 根据第一预设策略向所述移动 交换中心服务器返回被叫方终端的寻呼状态消息， 所述第一预设策略为立即 返回或在第一预设时间段之后返回。
4、 根据权利要求 1、 2或 3所述的方法， 其特征在于， 还包括： 所述移 动交换中心服务器接收所述寻呼状态消息后， 延长等待所述被叫方终端返回 寻呼响应消息的时间。
5、 根据权利要求 4所述的方法， 其特征在于， 所述方法还包括： 所述移 动交换中心服务器向主叫方返回电路域呼叫链路建立的被叫振铃消息。
6、根据权利要求 5所述的方法， 其特征在于， 所述移动交换中心服务器 向主叫方返回电路域呼叫链路建立的被叫振铃消息包括： 所述移动交换中心 服务器根据第二预设策略向主叫方返回电路域呼叫链路建立的被叫振铃消 息， 所述第二预设策略为立即返回或在第二预设时间段之后返回。
7、 根据权利要求 1或 2所述的方法， 其特征在于， 还包括：
所述被叫方终端接收所述寻呼通知消息；
所述被叫方终端显示第一提示信息， 所述第一提示信息用于指示所述被 叫方终端的用户确认是否接受电路域回落流程；
所述被叫方终端获取所述用户根据所述第一提示信息输入的第一指令； 所述被叫方终端根据所述第一指令触发执行电路域回落流程。
8、根据权利要求 7所述的方法， 其特征在于， 所述寻呼通知消息中还携 带有业务类型标识， 所述被叫方终端显示第一提示信息具体为： 所述被叫方 终端根据所述业务类型标识显示第一提示信息的内容和第一提示信息的操作 选项。
9、根据权利要求 8所述的方法， 其特征在于， 所述被叫方终端根据所述 第一指令触发执行电路域回落流程之后还包括： 所述被叫方终端向所述移动 交换中心服务器返回连接消息直接接通呼叫。
10、 根据权利要求 7所述的方法， 其特征在于， 所述被叫方终端根据所 述第一指令触发执行电路域回落流程之后还包括：
所述被叫方终端根据所述业务类型标识和所述第一指令显示第二提示信 息， 所述第二提示信息用于指示所述用户确认是否接通呼叫；
所述被叫方终端获取所述用户根据所述第二提示信息输入的第二指令； 所述被叫方终端根据所述第二指令向所述移动交换中心服务器返回连接 消息接通呼叫， 或执行所述业务类型标识对应的操作流程。
11、 一种信息显示方法， 其特征在于， 包括：
接收寻呼通知消息， 所述寻呼通知消息中携带有业务类型标识； 显示第一提示信息， 所述第一提示信息用于指示用户确认是否接受电路 域回落流程；
获取所述用户根据所述第一提示信息输入的第一指令；
根据所述第一指令触发执行电路域回落流程；
根据所述业务类型标识和所述第一指令显示第二提示信息， 所述第二提 示信息用于指示所述用户确认是否接通呼叫；
获取所述用户根据所述第二提示信息输入的第二指令；
根据所述第二指令向移动交换中心服务器返回连接消息接通呼叫， 或执 行所述业务类型标识对应的操作流程。
12、 一种移动管理装置， 其特征在于， 包括：
第一接收模块， 用于接收被叫方终端注册的移动交换中心服务器发送的 寻呼请求消息；
通知模块， 用于所述第一接收模块接收到寻呼请求消息后， 当所述被叫 方终端处于连接状态时， 向所述被叫方终端发送寻呼通知消息， 并向所述移 动交换中心服务器返回被叫方终端的寻呼状态消息。
13、 根据权利要求 12 所述的装置， 其特征在于， 还包括： 指示模块， 用于获取所述被叫方终端发送的等待指示消息；
所述通知模块还用于所述指示模块接收到所述等待指示消息后， 向所述 移动交换中心服务器返回被叫方终端的寻呼状态消息。
14、 一种移动交换中心服务器， 其特征在于， 包括：
第二接收模块， 用于接收移动管理装置返回的被叫方终端的寻呼状态消 息；
处理模块， 用于所述第二接收模块接收到寻呼状态消息后， 延长等待所 述被叫方终端返回寻呼响应消息的时间。
15、 根据权利要求 14 所述的服务器， 其特征在于， 所述处理模块还用 于向主叫方返回电路域呼叫链路建立的被叫振铃消息。
16、 一种终端， 其特征在于， 包括：
第三接收模块， 用于接收寻呼通知消息， 所述寻呼通知消息中携带有业 务类型标识；
第一显示模块， 用于所述第三接收模块接收到寻呼通知消息后， 显示第 一提示信息，所述第一提示信息用于指示用户确认是否接受电路域回落流程； 第一获取模块 , 用于获取所述用户根据所述第一提示信息输入的第一指 令；
第一执行模块， 用于根据所述第一指令触发执行电路域回落流程； 第二显示模块， 用于根据所述业务类型标识和所述第一指令显示第二提 示信息， 所述第二提示信息用于指示所述用户确认是否接通呼叫；
第二获取模块， 用于获取所述用户根据所述第二提示信息输入的第二指 令；
第二执行模块， 用于根据所述第二指令向移动交换中心服务器返回连接 消息接通呼叫， 或执行所述业务类型标识对应的操作流程。
17、 一种寻呼处理***， 其特征在于， 包括移动交换中心服务器和移动 管理装置，
所述移动交换中心服务器用于向所述移动管理装置发送寻呼请求消息， 以及接收所述移动管理装置返回的被叫方终端的寻呼状态消息， 并延长等待 被叫方终端返回寻呼响应消息的时间；
所述移动管理装置用于接收所述移动交换中心服务器发送的寻呼请求消 息， 当所述被叫方终端处于连接状态时， 向所述被叫方终端发送寻呼通知消 息， 并向所述移动交换中心服务器返回被叫方终端的寻呼状态消息。
18、 根据权利要求 17 所述的***， 其特征在于， 所述移动管理装置还 用于获取所述被叫方终端发送的等待指示消息， 向所述移动交换中心服务器 返回被叫方终端的寻呼状态消息。
19、 根据权利要求 17 所述的***， 其特征在于， 所述移动交换中心服 务器还用于向主叫方返回电路域呼叫链路建立的被叫振铃消息。
PCT/CN2009/074812 2008-11-07 2009-11-05 寻呼处理、信息显示方法、装置及*** WO2010051763A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
EP09824418.9A EP2346281B1 (en) 2008-11-07 2009-11-05 Paging processing and information displaying method, apparatus and system
ES09824418.9T ES2567050T3 (es) 2008-11-07 2009-11-05 Método, aparato y sistema de procesamiento y de presentación visual de información de radiomensajería
JP2011534994A JP2012508487A (ja) 2008-11-07 2009-11-05 ページング処理および情報表示の方法、装置およびシステム
EP15167144.3A EP2934042B1 (en) 2008-11-07 2009-11-05 Method, apparatus and system for paging processing and information displaying
US13/101,816 US9049677B2 (en) 2008-11-07 2011-05-05 Method, apparatus and system for paging processing and information displaying
US14/710,203 US10306517B2 (en) 2008-11-07 2015-05-12 Method, apparatus and system for paging processing and information displaying
US16/405,514 US10757614B2 (en) 2008-11-07 2019-05-07 Method, apparatus and system for paging processing and information displaying

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810225981.4 2008-11-07
CN2008102259814A CN101742692B (zh) 2008-11-07 2008-11-07 寻呼处理、信息显示方法、装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/101,816 Continuation US9049677B2 (en) 2008-11-07 2011-05-05 Method, apparatus and system for paging processing and information displaying

Publications (1)

Publication Number Publication Date
WO2010051763A1 true WO2010051763A1 (zh) 2010-05-14

Family

ID=42152504

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/074812 WO2010051763A1 (zh) 2008-11-07 2009-11-05 寻呼处理、信息显示方法、装置及***

Country Status (6)

Country Link
US (3) US9049677B2 (zh)
EP (2) EP2346281B1 (zh)
JP (3) JP2012508487A (zh)
CN (1) CN101742692B (zh)
ES (1) ES2567050T3 (zh)
WO (1) WO2010051763A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102217338A (zh) * 2011-05-03 2011-10-12 华为技术有限公司 用于接收或发送短消息的方法和装置
CN103444255A (zh) * 2011-03-31 2013-12-11 瑞典爱立信有限公司 用于增强过载处理的扩展服务请求中的低优先级指示
WO2015109600A1 (zh) * 2014-01-27 2015-07-30 华为技术有限公司 一种ue以及相关的呼叫响应方法

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101489288B (zh) 2008-01-16 2011-04-20 华为技术有限公司 演进分组网络中电路域业务的处理方法、***及相关设备
CN101742692B (zh) 2008-11-07 2012-07-04 华为技术有限公司 寻呼处理、信息显示方法、装置
WO2012055093A1 (zh) * 2010-10-26 2012-05-03 华为技术有限公司 移动交换中心池中的寻呼处理方法及装置
KR20130035143A (ko) * 2011-09-29 2013-04-08 삼성전자주식회사 로컬 네트워크에서 로컬 엑세스와 음성 통화를 지원하기 위한 방법 및 장치
EP2772093B1 (en) 2011-10-28 2020-02-26 BlackBerry Limited Method and apparatus to handle bearers during circuit switched fallback operation
JP6225904B2 (ja) * 2012-07-20 2017-11-08 日本電気株式会社 移動管理ノード、ページング制御方法、及びプログラム
CN103916920B (zh) * 2012-12-31 2017-04-26 展讯通信（上海）有限公司 处理寻呼的方法及***
WO2014161609A1 (en) * 2013-04-04 2014-10-09 Telefonaktiebolaget L M Ericsson (Publ) Network initiated cs services during ims call
JP5525092B1 (ja) * 2013-04-05 2014-06-18 日本電気株式会社 移動管理装置、通信システム、音声着信制御方法及びプログラム
CN103609168B (zh) * 2013-06-21 2017-04-19 华为技术有限公司 电路域回落csfb的接入方法、移动管理实体和移动交换中心
US9876903B2 (en) * 2013-09-30 2018-01-23 Apple Inc. Apparatus, system, and method for notifying a mobile station of an incoming circuit switched call during a packet switched session
CN104918222B (zh) * 2014-03-12 2018-12-04 ***通信集团北京有限公司 一种播放lte语音业务提示音的方法、设备及***
KR20170016939A (ko) 2014-06-24 2017-02-14 후아웨이 테크놀러지 컴퍼니 리미티드 음성 자원 절감 방법, 장치 및 시스템
KR102294359B1 (ko) * 2014-09-26 2021-08-26 삼성전자주식회사 전자 장치 및 전자 장치에서 알림을 제어하는 방법
CN105722106B (zh) * 2014-12-03 2020-06-09 ***通信集团黑龙江有限公司 一种仿真电路域回落信令接续的监控方法及监控***
CN106255083B (zh) * 2016-10-11 2020-02-14 深圳市万普拉斯科技有限公司 一种终端设备通信控制方法和终端设备
WO2018129672A1 (en) * 2017-01-11 2018-07-19 Qualcomm Incorporated Techniques for broadcasting paging messages in wireless communications
US10278153B2 (en) * 2017-06-02 2019-04-30 Mediatek Inc. Method and apparatus for avoiding circuit-switched call drop in mobile communications
CN112689295B (zh) * 2019-10-18 2023-09-05 ***通信集团辽宁有限公司 寻呼消息的业务识别方法、装置、计算设备及存储介质
CN113810964B (zh) * 2020-06-13 2023-03-10 华为技术有限公司 一种通信方法及设备
CN114071492B (zh) * 2020-07-31 2023-07-25 中国联合网络通信集团有限公司 语音通话质量优化方法、终端及基站
CN113660377B (zh) * 2021-08-23 2022-07-15 珠海格力电器股份有限公司 呼叫处理方法、装置、终端设备、电子设备及存储介质
CN114585086B (zh) * 2022-05-05 2022-08-05 深圳小米通讯技术有限公司 呼叫响应方法、装置、终端设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1941997A (zh) * 2005-09-30 2007-04-04 北京三星通信技术研究有限公司 向高速分组数据网下的用户传送3g1x语音呼叫信息的方法
CN101002490A (zh) * 2004-07-19 2007-07-18 西门子公司 操作便携式通信设备的方法和便携式通信设备
CN101222765A (zh) * 2008-01-24 2008-07-16 中兴通讯股份有限公司 电路域回落的控制方法、***、及装置
CN101243711A (zh) * 2004-08-23 2008-08-13 艾利森电话股份有限公司 在混合网络中寻呼移动站

Family Cites Families (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3786538B2 (ja) 1999-02-19 2006-06-14 富士通株式会社 移動通信システム
CN100387091C (zh) * 2003-09-22 2008-05-07 华为技术有限公司 一种实现快速呼叫建立的方法
CN100440850C (zh) 2003-12-24 2008-12-03 华为技术有限公司 多媒体业务网络地址转换穿越的方法及其***
US20050186971A1 (en) * 2004-02-20 2005-08-25 Telefonaktiebolaget L M Ericsson Method and apparatus for intelligent paging in a wireless communication network
CN1728743A (zh) 2004-07-29 2006-02-01 华为技术有限公司 一种实现遇忙回呼业务的方法
JP4584263B2 (ja) * 2004-10-20 2010-11-17 富士通株式会社 携帯電話端末間のデータ伝送路確立システム
ATE438272T1 (de) * 2005-01-31 2009-08-15 Ericsson Telefon Ab L M Technik zum umschalten zwischen sprach- /multimediamodus in einem drahtlosen kommunikationsnetz
CN100450282C (zh) 2005-04-05 2009-01-07 华为技术有限公司 一种电路交换呼叫连接的切换方法
CN1933655A (zh) * 2005-09-15 2007-03-21 北京三星通信技术研究有限公司 高速分组数据网下的双模终端对1x寻呼的应答方法
CN101009927B (zh) * 2006-01-23 2011-02-16 华为技术有限公司 一种寻呼用户设备的实现方法
CN101022653B (zh) 2006-02-15 2010-12-08 中兴通讯股份有限公司 移动性管理状态转换的控制方法
CN100450306C (zh) 2006-03-24 2009-01-07 华为技术有限公司 一种检查通话状态的方法
CN1878337A (zh) 2006-07-14 2006-12-13 华为技术有限公司 实现呼叫等待业务的方法和***
CN101141794B (zh) 2006-09-08 2011-06-15 华为技术有限公司 用户设备、语音呼叫连续性应用服务器及网络切换方法
CN101179829A (zh) 2006-11-07 2008-05-14 华为技术有限公司 向主叫终端通知被叫接续状态的方法、及终端
EP2104984A4 (en) * 2007-01-15 2012-12-26 Ericsson Telefon Ab L M METHOD AND DEVICE FOR ENHANCED PERFORMANCE IN A WIRELESS ACCESS TIME TIME DIVISION DUPLEX SYSTEM
CN101394340B (zh) 2007-09-19 2012-07-11 华为技术有限公司 数据传输方法、***和装置
CN101394580B (zh) 2007-09-21 2012-01-25 电信科学技术研究院 Eps承载管理的方法、装置、mme及通信***
WO2009056932A2 (en) * 2007-11-01 2009-05-07 Telefonaktiebolaget Lm Ericsson (Publ) Circuit-switched services over sae/lte networks
CN101437219B (zh) 2007-11-12 2011-04-20 华为技术有限公司 一种终端的移动性管理方法及设备
CN101184272A (zh) 2007-11-22 2008-05-21 华为技术有限公司 指示主叫设备被叫设备状态的方法、***及设备
US9247420B2 (en) * 2007-12-12 2016-01-26 Lg Electronics Inc. Method of managing user equipment capabilities
CN101640933B (zh) 2008-07-31 2012-07-04 华为技术有限公司 寻呼用户设备的方法、网络设备、用户设备及网络***
US8243725B2 (en) * 2008-08-13 2012-08-14 Interdigital Patent Holdings, Inc. Maintaining circuit switched continuity in an enhanced universal terrestrial radio access network
JP5282495B2 (ja) * 2008-09-05 2013-09-04 富士通モバイルコミュニケーションズ株式会社 移動無線端末
CN101742692B (zh) 2008-11-07 2012-07-04 华为技术有限公司 寻呼处理、信息显示方法、装置
CN101577942B (zh) 2008-11-07 2011-08-10 中兴通讯股份有限公司 既建立ims媒体链接又建立cs媒体链接的方法
CN101466147B (zh) 2008-12-31 2010-12-22 中国科学院计算技术研究所 一种异构网络的寻呼控制***及其寻呼方法
CN101577892A (zh) 2009-01-14 2009-11-11 中兴通讯股份有限公司 一种避免服务限制影响紧急呼叫连续性的方法
US8515485B2 (en) * 2009-10-20 2013-08-20 Lg Electronics Inc. Provisioning of voice and other CS-domain services

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101002490A (zh) * 2004-07-19 2007-07-18 西门子公司 操作便携式通信设备的方法和便携式通信设备
CN101243711A (zh) * 2004-08-23 2008-08-13 艾利森电话股份有限公司 在混合网络中寻呼移动站
CN1941997A (zh) * 2005-09-30 2007-04-04 北京三星通信技术研究有限公司 向高速分组数据网下的用户传送3g1x语音呼叫信息的方法
CN101222765A (zh) * 2008-01-24 2008-07-16 中兴通讯股份有限公司 电路域回落的控制方法、***、及装置

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103444255A (zh) * 2011-03-31 2013-12-11 瑞典爱立信有限公司 用于增强过载处理的扩展服务请求中的低优先级指示
US9629051B2 (en) 2011-03-31 2017-04-18 Telefonaktiebolaget Lm Ericsson (Publ) Low priority indication in extended service request for enhanced overload handling
CN102217338A (zh) * 2011-05-03 2011-10-12 华为技术有限公司 用于接收或发送短消息的方法和装置
CN102217338B (zh) * 2011-05-03 2013-12-18 华为技术有限公司 用于接收或发送短消息的方法和装置
US9179275B2 (en) 2011-05-03 2015-11-03 Huawei Technologies Co. Ltd. Method and apparatus for receiving or sending short message
US9420439B2 (en) 2011-05-03 2016-08-16 Huawei Technologies Co., Ltd. Method and apparatus for receiving or sending short message
US9713114B2 (en) 2011-05-03 2017-07-18 Huawei Technologies Co., Ltd. Method and apparatus for receiving or sending short message
WO2015109600A1 (zh) * 2014-01-27 2015-07-30 华为技术有限公司 一种ue以及相关的呼叫响应方法

Also Published As

Publication number Publication date
US10306517B2 (en) 2019-05-28
US20190268810A1 (en) 2019-08-29
US9049677B2 (en) 2015-06-02
JP5778746B2 (ja) 2015-09-16
JP2014096818A (ja) 2014-05-22
CN101742692A (zh) 2010-06-16
EP2346281A4 (en) 2012-08-29
JP2015201897A (ja) 2015-11-12
EP2346281A1 (en) 2011-07-20
EP2934042A1 (en) 2015-10-21
EP2346281B1 (en) 2016-01-27
EP2934042B1 (en) 2022-04-13
JP2012508487A (ja) 2012-04-05
US20110207481A1 (en) 2011-08-25
ES2567050T3 (es) 2016-04-19
CN101742692B (zh) 2012-07-04
JP6075578B2 (ja) 2017-02-08
US20150245253A1 (en) 2015-08-27
US10757614B2 (en) 2020-08-25

Similar Documents

Publication Publication Date Title
US10757614B2 (en) Method, apparatus and system for paging processing and information displaying
US10531343B2 (en) Processing circuit switched services in an evolved packet network
CN106686565A (zh) 在无线网络中在用户设备处理ims呼叫和csfb呼叫
WO2009100609A1 (zh) 一种单无线信道语音业务连续性的域切换方法
WO2008028416A1 (fr) Procédé de commande de transfert intercellulaire d'appel et système de communication mettant en oeuvre ce procédé et dispositif utilisateur
CN103841545B (zh) 一种mme池场景能力信息上报的方法及装置
CN102711250B (zh) 寻呼处理、信息显示方法、装置及***
WO2006010344A1 (fr) Procede et systeme permettant a un terminal de recevoir un numero appelant a l'avance
EP4093107A1 (en) Multimedia service processing method, storage medium, chip, and related device
US20130303141A1 (en) Provisioning of voice and other cs-domain services
CN102123469B (zh) 演进分组网络中电路域业务的处理方法及用户设备
WO2011044815A1 (zh) 具有优先级的业务实现方法、MSC/VLR、MME和eNodeB
WO2008006281A1 (fr) Procédé, dispositif et centre de commutation mobile pour informer un utilisateur de l'échec d'un appel
US20120020282A1 (en) Allowing a User to Accept or Deny a Mobile Terminated Call From Another Radio Access Technology
JP2019220898A (ja) 無線通信端末、通信方法、及び通信プログラム
WO2011050650A1 (zh) 视频电话回落的处理方法、装置和***
WO2011088802A1 (zh) 一种实现异***间呼叫控制的方法、装置和***
KR20130131772A (ko) 음성 착신호 성공율 향상을 위한 ｃｓｆｂ 서비스 처리 방법 및 장치

Legal Events

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

Ref document number: 09824418

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2011534994

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 3194/CHENP/2011

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2009824418

Country of ref document: EP