[go: up one dir, main page]

WO2011120453A2 - 用于接收或发送短消息的方法和装置 - Google Patents

用于接收或发送短消息的方法和装置 Download PDF

Info

Publication number
WO2011120453A2
WO2011120453A2 PCT/CN2011/073614 CN2011073614W WO2011120453A2 WO 2011120453 A2 WO2011120453 A2 WO 2011120453A2 CN 2011073614 W CN2011073614 W CN 2011073614W WO 2011120453 A2 WO2011120453 A2 WO 2011120453A2
Authority
WO
WIPO (PCT)
Prior art keywords
message
user equipment
vlr
msc
short message
Prior art date
Application number
PCT/CN2011/073614
Other languages
English (en)
French (fr)
Other versions
WO2011120453A3 (zh
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
Priority to EP16177794.1A priority Critical patent/EP3139675A1/en
Priority to HUE11762027A priority patent/HUE031002T2/en
Priority to ES11762027.8T priority patent/ES2607958T3/es
Priority to EP11762027.8A priority patent/EP2680625B1/en
Priority to CN201180000846XA priority patent/CN102217338B/zh
Priority to PCT/CN2011/073614 priority patent/WO2011120453A2/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to JP2014506720A priority patent/JP5792890B2/ja
Publication of WO2011120453A2 publication Critical patent/WO2011120453A2/zh
Publication of WO2011120453A3 publication Critical patent/WO2011120453A3/zh
Priority to US14/065,523 priority patent/US9179275B2/en
Priority to US14/861,799 priority patent/US9420439B2/en
Priority to US15/228,632 priority patent/US9713114B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/06—De-registration or detaching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
    • 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
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/06—Registration at serving network Location Register, VLR or user mobility server

Definitions

  • the present invention relates to the field of communications, and more particularly to a method and apparatus for receiving or transmitting short messages in the field of communications. Background technique
  • Evolved Packet System is an Evolved Universal Mobile Telecommunication System Territorial Access Network (E-UTRAN) and an evolved packet core network. (Evolved Packet Core Network, called "EPC").
  • EPC Evolved Packet Core Network
  • CS Circuit Switched
  • SMS Short Message Service
  • MME Management Entity
  • MSC/VLR Mobile Switched Network
  • UE User Equipment
  • CS Fallback The architecture and processing method can be called "CS Fallback” (CSFB).
  • the processing method of the short message service is different from that of other CS services (such as voice, CS supplementary service, etc.), that is, the short message service does not need to fall back to the 2G/3G network, but directly in the EPS network.
  • the short message transfer between the UE and the MSC/VLR is completed by the MME, and thus is generally also referred to as a technique of "SMS over SGs".
  • SMS Session In the prior art, a user-initiated SMS over SGs (Mobile Originating SMS, called "MO SMS”) processing flow can implement short message transmission, and the SMS over SGs (Mobile Terminated SMS) received by the user is called "MT".
  • the SMS processing process enables the receipt of short messages.
  • the MSC/VLR fails, for example, the board is reset, or the MSC/VLR recovers from the fault, the user equipment is in an abnormal state, for example, the context of the user equipment is lost in the MSC/VLR. MSC/VLR cannot handle this user's short
  • the MSC/VLR may indicate that the MME current process fails, and then the MME marks the UE in the context of the MME, and waits for the UE to subsequently initiate the tracking area update procedure, instructing the UE to re-initiate the registration to the MSC/VLR. .
  • the time when the UE can initiate the tracking area update process is uncertain. In general, it takes at least several hours. During this time, the user cannot send a short message, that is, the short message cannot be sent.
  • the MSC/VLR fails, for example, the board is reset, or the MSC/VLR recovers from the fault, the user equipment is in an abnormal state, for example, the context of the user equipment is lost in the MSC/VLR.
  • the MSC/VLR can still receive the short message sent by the SMS-Gateway Mobile Switching Center (SMS-GMSC), and further sends a paging message to the MME, the MME.
  • SMS-GMSC SMS-Gateway Mobile Switching Center
  • a service request message is then sent to the MSC/VLR to instruct the MSC/VLR to begin sending short messages.
  • the MSC/VLR ignores the service request message sent by the MME, so that the short message cannot be sent to the UE, that is, the short message is not received.
  • the MSC/VLR ignores the paging response sent by the MME, that is, the above-mentioned service request message, and the MSC/VLR considers that the paging fails, thereby repeatedly paging, resulting in waste of network resources.
  • an embodiment of the present invention provides a method and apparatus for receiving or transmitting a short message, which can implement receiving or transmitting a short message when the user equipment is in an abnormal state due to a failure of the MSC/VLR.
  • an embodiment of the present invention provides a method for receiving or sending a short message, the method comprising: receiving a first message sent by a mobile switching center MSC/visiting location register VLR; determining, according to the first message, that the user equipment is located An abnormal state is sent to the user equipment, where the second message is used to indicate that the user equipment initiates attachment to the MSC/VLR.
  • an embodiment of the present invention provides an apparatus for receiving or transmitting a short message, where the apparatus includes: a receiving module, configured to receive a first message sent by a mobile switching center MSC/visiting location register VLR; The module is configured to determine, according to the first message, that the user equipment is in an abnormal state; the sending module is configured to send a second message to the user equipment, where the second message is used to indicate that the user equipment initiates attaching to the MSC/VLR.
  • an embodiment of the present invention provides an apparatus for receiving or sending a short message, where
  • the device includes: a receiving module, configured to receive a second message sent by the mobility management device, where the second message is used to indicate that the device initiates attaching to the mobile switching center MSC/visiting location register VLR; and the first sending module is configured to The second message sends a third message to the mobility management device to initiate attachment to the MSC/VLR.
  • the method and apparatus for receiving or sending a short message provided by the embodiment of the present invention can be established on the MSC/VLR by sending information indicating that the user equipment initiates attachment to the MSC/VLR to the user equipment.
  • the context of the user equipment can solve the problem that the short message cannot be received or sent when the user equipment is in an abnormal state due to the failure of the MSC/VLR, etc., thereby enabling short message reception or transmission, and improving the network. Self-recovery, saving network resources and improving user experience.
  • FIG. 1 is a schematic flow chart of a method for receiving or transmitting a short message according to an embodiment of the present invention.
  • FIG. 2 is a schematic flow chart of a method for receiving a short message according to an embodiment of the present invention.
  • FIG. 3 is a schematic flow chart of a method for receiving a short message according to another embodiment of the present invention.
  • FIG. 4 is a schematic flow chart of a method for receiving or transmitting a short message according to another embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of a method for transmitting a short message according to an embodiment of the present invention.
  • 6 is a schematic flow chart of a method for receiving a short message according to still another embodiment of the present invention.
  • FIG. 7 is a schematic flow chart of a method for transmitting a short message according to still another embodiment of the present invention.
  • Figure 8 is a schematic block diagram of an apparatus for receiving or transmitting a short message in accordance with an embodiment of the present invention.
  • 9A and 9B are diagrams for receiving or transmitting a short message according to another embodiment of the present invention. Schematic block diagram.
  • Figure 10 is a schematic block diagram of an apparatus for receiving or transmitting a short message in accordance with still another embodiment of the present invention.
  • Figure 11 is a schematic block diagram of an apparatus for receiving or transmitting a short message in accordance with still another embodiment of the present invention. detailed description
  • FIG. 1 shows a schematic flow diagram of a method 100 for receiving or transmitting a short message in accordance with an embodiment of the present invention. As shown in FIG. 1, the method 100 includes:
  • S120 Determine, according to the first message, that the user equipment is in an abnormal state.
  • the MSC/VLR fails, for example, the board is reset, or the MSC/VLR recovers from the fault, the user equipment is in an abnormal state.
  • the context of the user equipment in the MSC/VLR is lost, and the MSC/VLR cannot process the user.
  • the short message at this time, the MSC/VLR will instruct the mobile management device that the current process fails. Therefore, when the mobile management device receives the first message sent by the MSC/VLR, and determines that the user equipment is in an abnormal state according to the first message, the mobility management device sends a second message to the user equipment, where the second message is used to indicate the The user equipment initiates attachment to the MSC/VLR so that the user equipment can normally receive or send short messages.
  • the method for receiving or sending a short message in the embodiment of the present invention enables the context of the user equipment to be established on the MSC/VLR by sending information indicating that the user equipment initiates attachment to the MSC/VLR to the user equipment. It can solve the problem that the short message cannot be received or sent when the user equipment is in an abnormal state due to the failure of the MSC/VLR, etc., thereby enabling short message reception or transmission, and improving the self-recovery capability of the network, saving network resources and Improve the user experience.
  • the user equipment is in an abnormal state, including a board reset, User context loss and other situations that affect the normal reception or transmission of short messages
  • the MSC/VLR can detect that the UE has no context in the MSC/VLR, or has no legal context (eg, the context is not acknowledged by the wireless network, ie MSC/VLR)
  • the "Confirmed by Radio Contact” flag is set to False in the context of the UE; or the Home Location Register ("HLR”) is not confirmed, or there is no SGs connection of the UE.
  • HLR Home Location Register
  • the embodiment of the present invention mainly uses the MSC/VLR without the context of the UE, or the SGs connection with no legal context or the absence of the UE as an example to illustrate that the user equipment is in an abnormal state, but the embodiment of the present invention is not limited thereto.
  • the mobility management device may include a mobility management entity MME.
  • a method according to an embodiment of the present invention may include a method for receiving a short message and a method for transmitting a short message, which will be separately described below.
  • FIG. 2 shows a schematic flowchart of a method 200 for receiving a short message according to an embodiment of the present invention. As shown in FIG. 2, the method 200 includes:
  • the mobility management device receives a first paging (Paging) message sent by the MSC/VLR, where the first paging message carries an International Mobile Subscriber Identification Number ("IMSI") of the UE.
  • IMSI International Mobile Subscriber Identification Number
  • the service type carried by the first paging message is a short message.
  • the MSC/VLR is unable to process the short message service for the UE, for example, the user equipment is in an abnormal state due to the failure of the MSC/VLR, for example, the context of the UE is lost, or the SGs connection established for the UE in the MSC/VLR is released.
  • the MSC/VLR performs the IMSI paging process, that is, the first paging message does not carry the UE location area identifier (Location Area Identity, the tube is called "LAI”) and/or the temporary identification code. (Temporary Mobile Subscriber Identity, the tube is called "TMSI”) and other information.
  • LAI Location Area Identity
  • TMSI Temporal Mobile Subscriber Identity
  • the mobility management device determines, according to the first paging message, that the user equipment is in an abnormal state. Specifically, the mobility management device may determine that the user equipment is abnormal according to the location area identifier LAI or TMSI that does not carry the user equipment in the first paging message, or according to the first paging information that does not carry the LAI and the TMSI. Status, such as the absence of the context of the UE, or the SGs connection is released, and so on.
  • the mobility management device determines that the user equipment is in an idle state.
  • the mobility management device sends a second paging message to the user equipment, where the second paging message is used to indicate that the user equipment initiates attachment to the MSC/VLR.
  • the paging type and/or the paging cause value of the second paging message may be used to indicate that the user equipment initiates attachment to the MSC/VLR.
  • the paging type of the second paging message may be set to IMSI Detach, IMSI Attach or IMSI re-attach.
  • the paging cause value of the second paging message may be a paging cause value corresponding to the paging type, for example, CS service is not allowed, and IMSI is unknown. Or invalid context (Invalid Context) and so on.
  • another paging type and/or a paging cause value may be set for the second paging message to indicate that the user equipment initiates attachment to the MSC/VLR.
  • the user equipment identifier in the second paging message may be a temporary identifier S-TMSI (S-Temporary Mobile Subscriber Identity) allocated by the EPS network to the UE, and the S-TMSI may be used by the MME according to the IMSI of the UE, from the MME. Obtained in the context of the UE in the presence, the core domain indication in the second paging message may be set to PS or cs.
  • S-TMSI S-Temporary Mobile Subscriber Identity
  • the second paging message may include a specific combination of the user equipment identifier and the core network domain identifier, where the specific combination of the user equipment identifier and the core network domain identifier is used to indicate that the user equipment initiates to the MSC/ Adhesion of the VLR.
  • the second paging message may include a specific combination of the user equipment identifier being the IMSI and the core network identifier being the CS.
  • the second paging message may include a specific combination of the user equipment identifier being IMSI and the core domain identifier being PS.
  • FIG. 3 shows a schematic flow diagram of a method 300 for receiving a short message in accordance with another embodiment of the present invention. As shown in FIG. 3, the method 300 includes:
  • S310 Receive a first paging message sent by the MSC/VLR.
  • S320 Determine, according to the first paging message that the LAI and/or the TMSI are not included, determining that the user equipment is in an abnormal state;
  • S310 and S320 in method 300 are the same as S210 and S220 in method 200, in order to Clean, no longer repeat here.
  • the mobility management device determines that the user equipment is in an idle state, sends a paging message to the user equipment, and the user equipment performs service request processing in response to the paging message, and migrates the user equipment to the connected state.
  • the above processing is an existing standard processing method, and details are not described herein again.
  • the mobility management device when the user equipment is in the connected state, the mobility management device sends a second message to the user equipment, where the second message is used to indicate that the user equipment initiates attachment to the MSC/VLR.
  • the second message is used to indicate that the user equipment initiates attachment to the MSC/VLR.
  • the type of the second message and/or the cause value included may be used to indicate that the user equipment initiates attachment to the MSC/VLR.
  • the second message is a Detach Request message
  • the separation type of the separation request message and/or the cause value included is used to indicate that the user equipment initiates to the MSC/VLR.
  • Attachment Specifically, the separation type of the separation request message may be set to IMSI Detach, IMSI Attach, or IMSI re-attach, and the separation cause value of the separation request message may be The reason value corresponding to the separation type, for example, can be set to CS Service is not allowed, IMSI is unknown, or invalid context (Invalid Context).
  • CS Service is not allowed
  • IMSI is unknown
  • invalid context Invalid Context
  • the second message is a circuit switched CS Service Notification message, the CS service notification message including information indicating that the user equipment initiates attachment to the MSC/VLR.
  • the type of the CS service notification message and/or the reason value included is used to indicate that the user equipment initiates attachment to the MSC/VLR.
  • the CS service notification message carries a cell (ie, a type of message and/or a cause value) indicating that the UE needs to initiate attachment to the MSC/VLR, and the type of the CS service notification message is set, for example, to: IMSI separation ( IMSI Detach), IMSI Attach, IMSI re-attach, etc.
  • the reason value of the CS service notification message may be a cause value corresponding to the type, for example, the CS service may be unavailable ( CS Service is not allowed ), IMSI is not (IMSSI is unknown), or invalid context (Invalid Context).
  • the second message is a Notification message
  • the notification message carries information indicating that the user equipment initiates attachment to the MSC/VLR.
  • the type and/or inclusion of the notification message The cause value is used to indicate that the user equipment initiates attachment to the MSC/VLR.
  • the notification message carries a cell (ie, the type and/or cause value of the message) indicating that the UE needs to initiate attachment to the MSC/VLR.
  • the cell may be set to one of the following types: IMSI Detach, IMSI Attach, or IMSI re-attach, and the cause value of the cell may be corresponding to the type.
  • the cause value can be set, for example, to CS Service is not allowed, IMSI is unknown, or invalid context (Invalid Context).
  • the method for receiving or sending a short message in the embodiment of the present invention enables the context of the user equipment to be established on the MSC/VLR by sending information indicating that the user equipment initiates attachment to the MSC/VLR to the user equipment. It can solve the problem that the short message cannot be received or sent when the user equipment is in an abnormal state due to the failure of the MSC/VLR, etc., thereby enabling short message reception or transmission, and improving the self-recovery capability of the network, saving network resources and Improve the user experience.
  • the first message sent by the MSC/VLR received by the mobility management device may be a release request message.
  • the method includes: determining, according to the cause value of the release request message, that the user equipment is in an abnormal state.
  • the MSC/VLR when the MSC/VLR loses the context of the UE due to a failure or the like, or the UE has no legal context in the MSC/VLR, or the SGs connection of the UE is released, the MSC/VLR sends a release request to the MME.
  • the cause value of the release request message indicates the IMSI agnostic ("IMSI Unknown") of the user equipment; when the MSC/VLR fails, the SGs connection established for the UE in the MSC/VLR is released, that is, When the SGs connection is in the SGs-Null state, the cause value of the release request message sent by the MSC/VLR to the MME indicates the IMSI detached for non-EPS services.
  • IMSI Unknown the MSC/VLR fails
  • the mobility management device sends a second message to the user equipment, where the second message is used to indicate that the user equipment initiates attachment to the MSC/VLR, so that the user equipment sends and receives short messages.
  • the type of the second message and/or the cause value included may be used to indicate that the user equipment initiates attachment to the MSC/VLR.
  • the second message is a Detach Request message, a CS Service Notification message, or a Notification message.
  • the type of the second message may be IMSI Detach (IMSI Detach), IMSI Attachment IMSI Attach or IMSI re-attachment.
  • the reason value of the second message may be a cause value corresponding to the type, for example, CS Service is not allowed, IMSI is unknown, or invalid context (Invalid Context) Wait.
  • the method for receiving or sending a short message in the embodiment of the present invention enables the context of the user equipment to be established on the MSC/VLR by sending information indicating that the user equipment initiates attachment to the MSC/VLR to the user equipment. It can solve the problem that the short message cannot be received or sent when the user equipment is in an abnormal state due to the failure of the MSC/VLR, etc., thereby enabling short message reception or transmission, and improving the self-recovery capability of the network, saving network resources and Improve the user experience.
  • the method for receiving or sending a short message according to an embodiment of the present invention is described in detail above from the perspective of a mobility management device, and the following is provided for receiving according to an embodiment of the present invention from the perspective of a user equipment. Or a method of sending a short message is described in detail.
  • the method 400 includes:
  • S410 Receive a second message sent by the mobility management device, where the second message is used to indicate that the user equipment initiates attachment to the MSC/VLR.
  • the MSC/VLR fails, for example, the board is reset, or the MSC/VLR recovers from the fault, the user equipment is in an abnormal state. For example, the context of the user equipment is lost in the MSC/VLR, and the MSC/VLR cannot process the user.
  • the short message at this time, the MSC/VLR will instruct the mobile management device that the current process fails.
  • the mobility management device sends a second message to the user equipment for instructing the user equipment to initiate the attach to the MSC/VLR, and the user equipment receives the second message. Thereafter, a third message is sent to the mobility management device to initiate attachment to the MSC/VLR, thereby facilitating the user equipment to receive or send the short message normally.
  • the method for receiving or sending a short message provided by the embodiment of the present invention enables the context of the user equipment to be established on the MSC/VLR by sending information indicating that the user equipment initiates attachment to the MSC/VLR to the user equipment. This can solve the problem that the short message cannot be received or sent when the user equipment is in an abnormal state due to a failure of the MSC/VLR or the like.
  • the receiving or sending of short messages can improve the self-recovery ability of the network, save network resources and improve user experience.
  • the second message may be a second paging message, a separation request message,
  • the CS service notification message or the notification message may be used to indicate that the user equipment initiates attachment to the MSC/VLR, which will be separately described below.
  • the third message is a tracking area update request message or an attach request message. That is, the user equipment may send a tracking area update request message or an attach request message to the mobility management device according to the second message, so that the user equipment can re-register on the MSC/VLR, and establish the context of the user equipment on the MSC/VLR. Thereby, it is possible to facilitate the user equipment to normally receive or send a short message.
  • a method according to an embodiment of the present invention may include a method of receiving a short message and a method of transmitting a short message, which will be separately described below.
  • the MSC/VLR may send an IMSI paging message to the mobile management device, so that the mobile management device knows that the user equipment is in an abnormal state and cannot receive the short message normally.
  • the mobility management device sends a second message to the user equipment as a second paging message, where the second paging message indicates that the user equipment initiates attachment to the MSC/VLR, the user equipment According to the second paging message, a tracking area update request message or an attach request message may be sent to the mobility management device, thereby facilitating receiving the short message.
  • the user equipment sends a Tracking Area Update Request message or an Attach Request message to the mobility management device according to the paging type or the paging cause value of the second paging message.
  • the type of the tracking area update request message may be a joint tracking area/location area update ( Combined TA/LA Update, where the tracking area Tracking Area cartridge is called "TA", the location area Location Area cartridge is called "LA”) or periodic. Track TA Update.
  • the type of the attach request message may be a Combined EPS/IMSI Attach.
  • the user equipment when the user equipment receives the second paging message whose paging type is IMSI Detach, IMSI Attach, or IMSI re-attach, or when the user equipment receives the homing
  • the reason value is the second paging message of the cause value corresponding to the paging type, for example, CS Service is not allowed, IMSI is unknown, or invalid context (Invalid) Context ), etc.
  • user equipment can Sending a tracking area update request message or an attach request message to the mobility management device.
  • the user equipment may send a tracking area update request message or an attach request message to the mobile management device according to the specific combination of the user equipment identifier and the core network domain identifier in the second paging message.
  • the user equipment sends a tracking area update to the mobile management device according to the specific combination of the user equipment identifier and the core network identifier in the second paging message, which is a specific combination of the international mobile subscriber identity IMSI and the circuit switched CS.
  • the request message or the attach request message may be a joint tracking area/location area update or a periodic tracking area update, and the type of the attach request message may be a combined EPS/IMSI Attach.
  • the user equipment sends an Attach Request message to the mobility management device according to the specific combination of the user equipment identifier and the core network domain identifier in the second paging message, which is a specific combination of the IMSI and the packet switched PS.
  • the type of the attach request message is Joint EPS/IMSI Attach.
  • the mobility management device When the mobility management device receives the IMSI paging message sent by the MSC/VLR, indicating that the user equipment is in an abnormal state and affects the reception of the short message, if the user equipment is in the connected state or migrates from the idle state to the connected state, then the mobility management device The user equipment sends a second message, which is used to indicate that the user equipment initiates attachment to the MSC/VLR.
  • the mobility management device When the user equipment is in an abnormal state and affects the sending of the short message, the mobility management device receives the first message that may be a release request message sent by the MSC/VLR. After the mobile device determines that the user equipment is in an abnormal state according to the cause value of the release request message, the mobile device may send a second message to the user equipment to indicate that the user equipment initiates attachment to the MSC/VLR.
  • the type of the second message and/or the cause value included may be used to indicate that the user equipment initiates attachment to the MSC/VLR.
  • the second message is a detach request message, an CS service notification message, or a notification message.
  • the method 500 for sending a short message may further include:
  • the user equipment sends a fourth message to the mobility management device in response to the second message.
  • the fourth message can be a Detach Accept message.
  • the method 500 may further include: S540. Send a pause indication to a short message protocol stack or an application on the user equipment, where the pause indication is used to indicate that the short message is sent.
  • the method 500 may further include:
  • the user equipment After the user equipment receives the Tracking Area Accept message or the Attach Accept message sent by the mobility management device and responds to the Tracking Area Update Request message or the Attach Request message, the user equipment sends the Tracking Area Accept message or the Attach Accept message to the user equipment.
  • the short message protocol stack or application sends a resend indication to resend the short message.
  • S510 and S520 in the method 500 are the same as S410 and S420 in the method 400, and are not described herein for the sake of cleaning.
  • the method for receiving or sending a short message enables the context of the user equipment to be established on the MSC/VLR by sending information indicating that the user equipment initiates attachment to the MSC/VLR to the user equipment. This can solve the problem that the short message cannot be received or sent when the user equipment is in an abnormal state due to the failure of the MSC/VLR, etc., thereby enabling short message reception or transmission, and improving the self-recovery capability of the network and saving network resources. And improve the user experience.
  • the method for receiving or transmitting a short message will be specifically described below by taking a short message in the EPS network as an example.
  • FIG. 6 shows a schematic flow diagram of a method 600 for receiving a short message, which is directed to a scenario in which a user equipment receives a short message, ie, an MT SMS scenario, in accordance with an embodiment of the present invention.
  • the method 600 includes:
  • SMS Center Sends a short message to SMS-GMSCo
  • the SMS-GMSC performs a routing information query process, and acquires an MSC attached to the current UE from a Home Location Register ("HLR")/Home Subscriber Server (“HSS"). VLR. 5603.
  • the SMS-GMSC forwards the short message to the MSC/VLR to which the UE is attached.
  • the MSC/VLR when the user equipment is in an abnormal state, and the short message service cannot be processed for the UE, for example, the MSC/VLR fails to cause the context of the UE to be lost, or the SGs connection established for the UE in the MSC/VLR is released, that is, in the SGs.
  • the MSC/VLR performs the IMSI paging process, that is, sends a paging message to the MME, the paging message carries the IMSI of the UE, does not carry the location area identifier LAI of the UE, and the service type of the paging message is short. Message.
  • the MSC/VLR can immediately send a short message to the SC through the SMS-GMSC, and after receiving the feedback response, the SC executes S607.
  • the MSC/VLR can also buffer the short message so that the cached short message can be sent immediately after the UE attaches to the MSC/VLR.
  • the UE is currently in an idle state, and the MME sends a paging message to the Evolved Node B (the "eNB"), where the paging message carries the identifier of the UE and the CN Domain.
  • the eNB Evolved Node B
  • the paging message sent by the eNB to the UE in step 606 does not include the information indicating that the UE initiates the attachment to the MSC/VLR, and the steps are performed. S610.
  • the paging message may indicate that the UE initiates attachment to the MSC/VLR or to the MME and the MSC/VLR:
  • the foregoing paging message includes an indication that the UE is required to initiate the attachment to the MSC/VLR, and the attachment indication may be specifically represented by a specific paging cause value or a paging type, and the value may be specifically set to the following types. : "IMSI Detach" (IMSI Attach) or "IMSI re-attach", etc., the paging cause value can be set to the cause value corresponding to the type, for example, it can be set to CS service. Not available (CS Service is not allowed), IMSI is unknown, or invalid context (Invalid Context), etc.
  • the user identifier in the paging message may be a temporary identifier assigned by the EPS network to the UE.
  • the S-TMSI, the core domain indication may be set to PS or CS, where the temporary identifier S-TMSI may be obtained by the MME according to the IMSI of the UE from the context of the UE in the MME.
  • the above paging message indicates that the UE initiates by using a specific UE identity and a core domain indication
  • the attachment of the MSC/VLR, for example, the user identifier in the paging message is received by the MME in S604.
  • IMSI the core domain indication is set to CS.
  • the user identifier in the paging message is the IMSI received by the MME in S604, to indicate that the UE initiates a joint attach procedure to the MME and the MSC/VLR, and the core network
  • the domain indication can be set to PS.
  • the eNB sends a paging message to the UE according to the received paging message from the MME.
  • the paging message carries the identity of the UE provided by S605, the core network domain identifier, and an indication indicating that the UE initiates the attachment.
  • the short message center SC when the short message center SC cannot successfully send a short message, for example, the sending timer expires, or receives a short message sending failure indication sent by the MSC/VLR, and sends a terminal reachability notification request to the SMS-GMSC (UE Reachability Notification Request) ) message, cache the short message.
  • SMS-GMSC UE Reachability Notification Request
  • the SMS-GMSC sends a UE Reachability Notification Request message to the HLR/HSS.
  • the HLR/HSS sends a UE Reachability Notification Request message to the MSC/VLR.
  • the MSC/VLR can set a notification request identifier.
  • the UE performs a service request (Service Request) process, establishes a signaling connection, and turns the user into a connected state. , the flow proceeds to S611.
  • Service Request Service Request
  • the UE does not perform S610, that is, the UE does not perform the service request procedure, and the flow proceeds to S613.
  • the UE sends a notification request message to instruct the UE to initiate attachment to the MSC/VLR.
  • the foregoing notification request message that the UE initiates the attachment to the MSC/VLR may specifically include the following implementation manners:
  • the notification request message may be a Detach Request message, and the Detach Type in the Separation Request message or the Cause value in the Separation Request message is set to indicate that the UE needs to initiate to the MSC/VLR. Attachment.
  • the separation type can be set to the following types: "IMSI Detach”, "IMSI Attach” or "IMSI Re-attach”, etc., and the separation cause value can be set to be separated from the separation type.
  • the corresponding cause value of the type for example, can be set to CS Service is not allowed, IMSI is unknown, or invalid context (Invalid Context).
  • the notification request message may be a CS Service Notification message carrying a cell indicating the UE needs to initiate attachment to the MSC/VLR (ie, the type and/or cause value of the message)
  • the message type can be set to the following types: "IMSI Detach", "IMSI Attach” or "IMSI Re-attach", etc.
  • the reason value of the message It can be set to a reason value corresponding to the type, for example, it can be set to CS Service is not allowed, IMSI is unknown, or invalid context (Invalid Context).
  • the notification request message may be a notification message carrying a cell indicating the UE needs to initiate attachment to the MSC/VLR (i.e., the type and/or cause value of the message).
  • the notification indicator (Notification Indicator) cell in the notification message can be set to one of the following types: "IMSI Detach", "IMSI Attach” or "IMSI Re-attach” (IMSI re-attach) ), etc.
  • the notification indicates that the cause value of the cell can be set to a reason value corresponding to the type, for example, CS Service is not allowed, IMSI is unknown (IMSI is unknown) , or invalid context ( Invalid Context ) and so on.
  • the UE may send, to the MME, a notification response message that responds to the notification request message, where the notification response message is, for example, a Detach Accept message.
  • the UE initiates a tracking area update process or an attach procedure according to the indication received in S606 or S611.
  • the UE initiates a tracking area update process or an attach procedure, and sends a Tracking Area Update Request message to the MME, and the update type is a joint tracking area/location area update (Combined TA/LA). Update) or Periodic TA Update, the type of attach request message can be Combined EPS/IMSI Attach:
  • the UE receives an indication that the UE initiates an attach to the MSC/VLR, such as "IMSI separation"
  • IMSI Detach IMSI Detach
  • IMSI Attach IMSI Attach
  • IMSI Re-attach IMSI Re-attach
  • the UE receives a combination of a specific UE identity and a core domain indication, for example, the identity of the UE is IMSI, and the core domain indication is CS.
  • the UE When one of the following conditions is met, the UE initiates an attach procedure, and sends an Attach Request message to the MME, and the attachment type is Combined EPS/IMSI Attach:
  • the UE receives a combination of a specific UE identity and a core domain indication, for example, the identity of the UE is IMSI, and the core domain indication is PS.
  • the MME initiates registration with the MSC/VLR, and sends a Location Update Request message to the MSC/VLR.
  • the MSC/VLR establishes a context of the UE, and allocates a temporary identifier (temporary) to the UE.
  • TMSI Mobile Subscriber Identity
  • the MME sends a Tracking Area Accept message or an Attach Accept message to the UE.
  • the UE may send a Tracking Area Complete message or an Attach Complete message to the MME.
  • the MME After receiving the completion message sent by the UE, the MME sends a TMSI Reallocation Complete message to the MSC/VLR.
  • the MSC/VLR may directly execute S625, and after receiving the service request message of S626, perform S627 to send a short message to the UE; S625 and S626 are omitted, and S627 is directly executed to send a short message to the UE. This processing can also be performed immediately after S615.
  • the MSC/VLR sets the notification request identifier in S609, the MSC/VLR sends a UE Activity Notification (UE Activity Notification) message to the HLR/HSS.
  • UE Activity Notification UE Activity Notification
  • HLR/HSS sends a terminal activation notification to the SMS-GMSC (UE Activity
  • the SMS-GMSC sends a UE Activity Notification message to the short message center SC.
  • the short message center SC resends the buffered short message to the SMS-GMSC.
  • the SMS-GMSC queries the HLR/HSS for the MSC/VLR to which the current UE is attached.
  • the SMS-GMSC forwards the short message to the MSC/VLR to which the UE is attached. 5625.
  • the MSC/VLR sends a Paging message to the MME, carrying the IMSI of the UE, and the location area identifier (LAI) of the user equipment, and the service type is a short message.
  • LAI location area identifier
  • the MME needs to perform a standard paging procedure, and after receiving the paging message, the UE initiates a service request (Service Request) process, and converts the UE into Connection state. For the sake of cleanliness, we will not repeat them here.
  • Service Request Service Request
  • the MME sends a Service Request message to the MSC/VLR.
  • the MSC/VLR encapsulates the short message in a Downlink Unitdata message and sends the message to the MME. The message is sent to the UE.
  • the UE encapsulates the short message acknowledgement message in an uplink NAS delivery message and sends the message to the MME.
  • the MME encapsulates the short message acknowledgement message in an uplink data delivery (Uplink Unitdata) message and sends the message to the MSC/VLR.
  • Uplink Unitdata Uplink Unitdata
  • the UE encapsulates the short message delivery report in the uplink NAS delivery message and sends the message to the MME.
  • the MME encapsulates the foregoing short message delivery report in an Uplink Unitdata message and sends the message to the MSC/VLR.
  • the MSC/VLR sends a short message delivery report to the SMS-GMSC.
  • the SMS-GMSC sends a short message delivery report to the SC.
  • the MSC/VLR sends the short message delivery report (Enhanced Report) to the MME in a Downlink Unitdata message.
  • the MME sends the short message delivery report (Entry report) to the UE in a Downlink NAS Transport message.
  • the MSC/VLR sends a Release Request message to the MME.
  • the method for receiving or sending a short message provided by the embodiment of the present invention enables the context of the user equipment to be established on the MSC/VLR by sending information indicating that the user equipment initiates attachment to the MSC/VLR to the user equipment. This can solve the problem that the short message cannot be received or sent when the user equipment is in an abnormal state due to a failure of the MSC/VLR or the like.
  • the receiving or sending of short messages can improve the self-recovery ability of the network, save network resources and improve user experience.
  • FIG. 7 is a schematic flow diagram of a method 700 for transmitting a short message, which is a scenario for a user equipment to send a short message, ie, a MO SMS scenario, in accordance with an embodiment of the present invention. As shown in Figure 7, the method 700 includes:
  • the UE When the UE needs to send a short message, if the UE is in an idle state, the UE performs a service request (Service Request) process. That is, the UE sends a Service Request message to the MME, establishes a signaling connection, and turns the UE into a connected state. If the UE is currently in the connected state, the flow proceeds directly to S702.
  • Service Request Service Request
  • the UE encapsulates the short message that needs to be sent in an uplink non-access layer (Non-Access).
  • Non-Access an uplink non-access layer
  • the Stratum called the "NAS" transport (Uplink NAS Transport) message, is sent to the MME.
  • NAS Uplink NAS Transport
  • the MME encapsulates the received short message in an uplink data delivery (Uplink Unitdata) message and sends the short message to the MSC/VLR.
  • Uplink Unitdata Uplink Unitdata
  • the user equipment in the MSC/VLR is in an abnormal state, and the short message service cannot be processed for the UE. For example, if the MSC/VLR fails, the context of the UE is lost, or the SGs connection established for the UE in the MSC/VLR is released. That is, in the SGs-Null state, etc., the MSC/VLR sends a Release Request message to the MME, indicating that the IMSI of the user equipment is unknown ("IMSI Unknown") or the IMSI of the user equipment is separated ("IMSI detached for non" -EPS services” ).
  • IMSI Unknown the IMSI of the user equipment is unknown
  • IMSI detached for non -EPS services
  • the SGs are the names of the interfaces between the MME and the MSC/VLR.
  • the SGs connection is a channel established between the MME and the MSC/VLR for the UE.
  • the MME and the MSC/VLR maintain the state of the SGs connection.
  • the MME sends a notification request message to the UE according to the indication received in S704, to indicate that the UE initiates attachment to the MSC/VLR.
  • the foregoing notification request message that the UE initiates the attachment to the MSC/VLR may specifically include the following implementation manners:
  • the notification request message may be a Detach Request message, and the Detach Type in the Separation Request message or the Cause value in the Separation Request message is set to indicate that the UE needs to initiate to the MSC/VLR. Attachment.
  • the separation type can be set to the following types: "IMSI Detach”, "IMSI” Attachment (IMSI Attach) or "IMSI re-attach”, etc.
  • the separation cause value can be set to the cause value corresponding to the separation type, for example, CS service is not available (CS Service is not allowed) ), IMSI is unknown (IMSI is unknown), or invalid context (Invalid Context).
  • the notification request message may be a CS Service Notification message carrying a cell indicating the UE needs to initiate attachment to the MSC/VLR (ie, the type and/or cause value of the message)
  • the message type can be set to the following types: "IMSI Detach", "IMSI Attach” or "IMSI Re-attach", etc.
  • the reason value of the message It can be set to a reason value corresponding to the type, for example, it can be set to CS Service is not allowed, IMSI is unknown, or invalid context (Invalid Context).
  • the notification request message may be a notification message carrying a cell indicating the UE needs to initiate attachment to the MSC/VLR (i.e., the type and/or cause value of the message).
  • the notification indicator (Notification Indicator) cell in the notification message can be set to one of the following types: "IMSI Detach", "IMSI Attach” or "IMSI Re-attach” (IMSI re-attach) ), etc.
  • the notification indicates that the cause value of the cell can be set to a reason value corresponding to the type, for example, CS Service is not allowed, IMSI is unknown (IMSI is unknown) , or invalid context ( Invalid Context ) and so on.
  • the UE may send, to the MME, a notification response message that responds to the notification request message, where the notification response message is, for example, a Detach Accept message or the like.
  • the UE initiates a tracking area update process or an attach process according to an indication sent by the S705 to the MSC/VLR, such as "IMSI Attach”, “IMSI Detach”, etc.
  • the MME sends a Tracking Area Update Request (TAU Request) message or an Attach Request message.
  • the type of the tracking area update request message may be a combined tracking area/location area update (Compound TA/LA Update) or a periodic tracking area update (Periodic TA Update); the type of the attach request message is a joint update (Combined
  • the UE may also instruct the short message protocol stack/application to suspend short message transmission before, after or at the same time as initiating the tracking area update procedure.
  • the MME initiates registration to the MSC/VLR, and sends a location update to the MSC/VLR. Request Update Request.
  • the MSC/VLR establishes a context of the UE, allocates a TMSI to the UE, and sends a Location Update Accept message to the MME.
  • the MME sends a Tracking Area Accept message or an Attach Accept message to the UE.
  • the UE may send a Tracking Area Complete message or an Attach Complete message to the MME.
  • the UE may notify the short message protocol stack/application on the UE to resend the short message.
  • the MME After receiving the completion message in S711, the MME sends a TMSI Reallocation Complete message to the MSC/VLR.
  • the UE encapsulates the short message to be sent in an Up NAS transport message and sends the message to the MME.
  • the MME encapsulates the received short message in an Uplink Unitdata message and sends the message to the MSC/VLR.
  • the MSC/VLR sends the received short message to the SMS-IWMSC.
  • the SMS-IWMSC sends the received short message to the short message center SC.
  • Short Message Center The SC sends a short message delivery report (send report) to the SMS-IWMSC.
  • the SMS-IWMSC sends a short message delivery report to the MSC/VLR.
  • the MSC/VLR sends a short message acknowledgement message to the MME.
  • the MME sends a short message confirmation message to the UE.
  • the MSC/VLR After the MSC/VLR receives the short message delivery report of the S718, the MSC/VLR encapsulates the received short message delivery report in a Downlink Unitdata message and sends the message to the MME.
  • the MME encapsulates the short message delivery report in a Downlink NAS Transport message and sends the message to the UE.
  • the UE acknowledges receipt of the short message delivery report, and encapsulates the confirmation result in an Uplink NAS Transport message and sends the result to the MME.
  • MSC/VLR C S725 The MSC/VLR sends a Release Request message to the MME, and ends the short message sending process.
  • the method for receiving or sending a short message enables the context of the user equipment to be established on the MSC/VLR by sending information indicating that the user equipment initiates attachment to the MSC/VLR to the user equipment. This can solve the problem that the short message cannot be received or sent when the user equipment is in an abnormal state due to the failure of the MSC/VLR, etc., thereby enabling short message reception or transmission, and improving the self-recovery capability of the network and saving network resources. And improve the user experience.
  • FIG. 8 shows a schematic block diagram of an apparatus 800 for receiving or transmitting a short message, in accordance with an embodiment of the present invention.
  • the apparatus 800 includes:
  • the receiving module 810 is configured to receive a first message sent by the MSC/VLR.
  • the first determining module 820 is configured to determine, according to the first message, that the user equipment is in an abnormal state; the sending module 830 is configured to send a second message to the user equipment, where the second message is used to indicate that the user equipment initiates to the MSC/ Adhesion of the VLR.
  • the apparatus for receiving or sending a short message provided by the embodiment of the present invention enables the establishment of the context of the user equipment on the MSC/VLR by sending information indicating that the user equipment initiates attachment to the MSC/VLR to the user equipment. This can solve the problem that the short message cannot be received or sent when the user equipment is in an abnormal state due to the failure of the MSC/VLR, etc., thereby enabling short message reception or transmission, and improving the self-recovery capability of the network and saving network resources. And improve the user experience.
  • the apparatus 800 for receiving or sending a short message further includes:
  • a second determining module 840 configured to: when the first message is the first paging message, determine that the user equipment is in an idle state,
  • the sending module 830 is specifically configured to send a second paging message to the user equipment, where the second paging The message indicates that the user equipment initiates attachment to the MSC/VLR.
  • the device 800 further includes:
  • the third determining module 850 is configured to determine that the user equipment is in a connected state before the first message is a first paging message, and the sending module sends the second paging message.
  • the apparatus 800 for transmitting a short message may correspond to the mobility management apparatus in the embodiment of the present invention, and the above and other operations and/or functions of the respective modules in the apparatus 800 are respectively implemented in order to implement FIG. 1 to FIG.
  • the corresponding processes of the respective methods 100 to 300 in 3 are not described here.
  • the apparatus for receiving or sending a short message in the embodiment of the present invention enables the context of the user equipment to be established on the MSC/VLR by transmitting information indicating that the user equipment initiates attachment to the MSC/VLR to the user equipment, thereby It can solve the problem that the short message cannot be received or sent when the user equipment is in an abnormal state due to the failure of the MSC/VLR, etc., thereby enabling short message reception or transmission, and improving the self-recovery capability of the network, saving network resources and Improve the user experience.
  • Figure 10 shows a schematic block diagram of an apparatus 900 for receiving or transmitting short messages in accordance with an embodiment of the present invention.
  • the apparatus 900 includes:
  • the receiving module 910 is configured to receive a second message sent by the mobility management device, where the second message is used to indicate that the device initiates attachment to the mobile switching center MSC/visiting location register VLR; and the first sending module 920 is configured to: The second message sends a third message to the mobility management device to initiate attachment to the MSC/VLR.
  • the apparatus for receiving or sending a short message in the embodiment of the present invention enables the context of the user equipment to be established on the MSC/VLR by transmitting information indicating that the user equipment initiates attachment to the MSC/VLR to the user equipment, thereby It can solve the problem that the short message cannot be received or sent when the user equipment is in an abnormal state due to the failure of the MSC/VLR, etc., thereby enabling short message reception or transmission, and improving the self-recovery capability of the network, saving network resources and Improve the user experience.
  • the apparatus 900 for receiving or sending a short message further includes:
  • the second sending module 930 is configured to send, after the receiving module receives the second message, a fourth message that responds to the second message to the mobile management device.
  • the apparatus 900 further includes:
  • the third sending module 940 is configured to send a pause indication to the short message protocol stack or the application on the device, where the pause indication is used to indicate that the short message is sent.
  • the apparatus 900 further includes:
  • the fourth sending module 950 is configured to: after receiving the message sent by the mobility management device and responding to the third message, send a retransmission indication to the short message protocol stack or the application on the device, where the retransmission indication is used The instruction to restart the sending of the short message.
  • the apparatus 900 for receiving or transmitting a short message may correspond to the user equipment in the embodiment of the present invention, and the above-described and other operations and/or functions of the respective modules in the apparatus 900 are respectively implemented in order to implement FIG. 4 to The corresponding processes of the respective methods 400 to 500 in FIG. 5 are not described herein.
  • the apparatus for receiving or sending a short message in the embodiment of the present invention enables the context of the user equipment to be established on the MSC/VLR by transmitting information indicating that the user equipment initiates attachment to the MSC/VLR to the user equipment, thereby It can solve the problem that the short message cannot be received or sent when the user equipment is in an abnormal state due to the failure of the MSC/VLR, etc., thereby enabling short message reception or transmission, and improving the self-recovery capability of the network, saving network resources and Improve the user experience.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not executed.
  • the coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interface, device or unit, or an electrical, mechanical or other form of connection.
  • the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present invention.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the technical solution of the present invention contributes in essence or to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium.
  • a number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like, which can store program codes. .

Landscapes

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

Abstract

本发明公开了一种用于接收或发送短消息的方法和装置。该方法包括：接收移动交换中心/拜访位置寄存器（MSC/VLR）发送的第一消息（S110）；根据该第一消息确定用户设备处于异常状态（S120）；向该用户设备发送第二消息，该第二消息用于指示该用户设备发起到该MSC/VLR的附着（S130）。该装置包括接收模块、第一确定模块和发送模块。采用本发明，通过向用户设备发送指示该用户设备发起到MSC/VLR的附着的信息，能够在MSC/VLR上建立该用户设备的上下文，由此能够解决当由于MSC/VLR发生故障导致用户设备处于异常状态时无法接收或发送短消息的问题，从而能够实现短消息的接收或发送，并能够提高网络的自我恢复能力，提高用户体验。

Description

用于接收或发送短消息的方法和装置 技术领域
本发明涉及通信领域， 尤其涉及通信领域中用于接收或发送短消息的方 法和装置。 背景技术
演进分组系统（Evolved Packet System, 筒称为 "EPS" ) 由演进通用移 动通信系统陆地无线接入网 ( Evolved Universal Mobile Telecommunication System Territorial Access Network, 筒称为 "E-UTRAN" )和演进分组核心网 ( Evolved Packet Core Network, 筒称为 "EPC" )组成。 为了在 EPS中支持 电路交换（Circuit Switched, 筒称为 "CS" )业务， 例如 CS语音和 CS短消 息（Short Message Service, 筒称为 "SMS" )等， 在 EPS的移动性管理实体 ( Mobility Management Entity, 筒称为 "MME" )和电路交换域网络（ Circuit Switched Network ) 的移动交换中心 /拜访位置寄存器（ Mobile Switch Center /Visitor Location Register, 筒称为 "MSC/VLR" )之间部署了 SGs接口， 从 而使得用户设备 ( User Equipment, 筒称为 "UE" ) 能在 EPS网络发起和接 收 CS业务， 并通过 E-UTRAN回到电路域 (例如 2G/3G网络） 完成 CS业 务， 其网络架构和处理方法可以称为 "电路域回落" （CS Fallback, 筒称为 "CSFB" )。
在上述 CSFB中， 短消息业务的处理方式和其他 CS业务（例如语音， CS补充业务等） 的处理方式不同， 即短消息业务不需要回落到 2G/3G网络 中进行， 而是直接在 EPS网络中通过 MME完成 UE和 MSC/VLR之间的短 消息传递， 因此一般也称之为通过 "SGs传递短消息 （SMS over SGs )" 的 技术。 现有技术中用户发起的 SMS over SGs ( Mobile Originating SMS , 筒称 为 "MO SMS" )处理流程， 能够实现短消息的发送， 用户接收到的 SMS over SGs ( Mobile Terminated SMS, 筒称为 "MT SMS" )处理流程， 能够实现短 消息的接收。
在 MO SMS流程中， 当由于 MSC/VLR发生故障， 例如单板复位， 或者 MSC/VLR 从故障中恢复等原因， 导致用户设备处于异常状态， 例如 MSC/VLR中该用户设备的上下文丟失， 该 MSC/VLR无法处理该用户的短 消息， 此时， 该 MSC/VLR会指示 MME当前流程失败， 于是 MME在 UE 在 MME中的上下文中进行标记，并且等待 UE后续发起跟踪区更新流程时， 指示 UE重新发起到 MSC/VLR的注册。 而 UE何时才能发起跟踪区更新流 程是不确定的， 一般情况下至少需要好几个小时， 在这段时间以内用户无法 发送短消息， 即不能够实现短消息的发送。
在 MT SMS流程中， 当由于 MSC/VLR发生故障， 例如单板复位， 或者 MSC/VLR 从故障中恢复等原因， 导致用户设备处于异常状态， 例如 MSC/VLR中该用户设备的上下文丟失， 此时， 该 MSC/VLR仍然能够收到 短消息 -网关移动交换中心 （ SMS-Gateway Mobile Switching Center , 筒称为 "SMS-GMSC" )发送的短消息， 并进而向 MME发送寻呼消息， 该 MME 会进而向该 MSC/VLR发送服务请求消息， 以指示该 MSC/VLR开始发送短 消息。 但是， 由于该 MSC/VLR中上述 UE的用户设备上下文丟失， 因此该 MSC/VLR会忽略 MME发送的服务请求消息，从而无法将短消息发送给 UE , 即不能够实现短消息的接收。 而由于该 MSC/VLR忽略了 MME发送的寻呼 响应， 即上述的服务请求消息， 该 MSC/VLR会认为该次寻呼失败， 从而重 复进行寻呼， 导致了网络资源的浪费。 发明内容
为此， 本发明实施例提供了一种用于接收或发送短消息的方法和装置， 能够在由于 MSC/VLR发生故障等原因导致用户设备处于异常状态时， 实现 短消息的接收或发送。
一方面， 本发明实施例提供了一种用于接收或发送短消息的方法， 该方 法包括： 接收移动交换中心 MSC/拜访位置寄存器 VLR发送的第一消息； 根 据该第一消息确定用户设备处于异常状态； 向该用户设备发送第二消息， 该 第二消息用于指示该用户设备发起到该 MSC/VLR的附着。
另一方面， 本发明实施例提供了一种用于接收或发送短消息的装置， 该 装置包括： 接收模块， 用于接收移动交换中心 MSC/拜访位置寄存器 VLR发 送的第一消息； 第一确定模块， 用于根据该第一消息确定用户设备处于异常 状态； 发送模块， 用于向该用户设备发送第二消息， 该第二消息用于指示该 用户设备发起到该 MSC/VLR的附着。
再一方面， 本发明实施例提供了一种用于接收或发送短消息的装置， 该 装置包括： 接收模块， 用于接收移动管理设备发送的第二消息， 该第二消息 用于指示该装置发起到移动交换中心 MSC/拜访位置寄存器 VLR的附着；第 一发送模块， 用于根据该第二消息， 向该移动管理设备发送第三消息， 以发 起到该 MSC/VLR的附着。
基于上述技术方案， 本发明实施例提供的用于接收或发送短消息的方法 和装置， 通过向用户设备发送指示该用户设备发起到 MSC/VLR的附着的信 息， 使得能够在 MSC/VLR上建立该用户设备的上下文， 由此能够解决当由 于 MSC/VLR发生故障等原因导致用户设备处于异常状态时无法接收或发送 短消息的问题， 从而能够实现短消息的接收或发送， 并能够提高网络的自我 恢复能力， 节省网络资源以及提高用户体验。 附图说明
为了更清楚地说明本发明实施例的技术方案， 下面将对本发明实施例中 所需要使用的附图作筒单地介绍， 显而易见地， 下面所描述的附图仅仅是本 发明的一些实施例， 对于本领域普通技术人员来讲， 在不付出创造性劳动的 前提下， 还可以根据这些附图获得其他的附图。
图 1是根据本发明实施例的用于接收或发送短消息的方法的示意性流程 图。
图 2是根据本发明实施例的用于接收短消息的方法的示意性流程图。 图 3 是根据本发明另一实施例的用于接收短消息的方法的示意性流程 图。
图 4是根据本发明另一实施例的用于接收或发送短消息的方法的示意性 流程图。
图 5是根据本发明实施例的用于发送短消息的方法的示意性流程图。 图 6 是根据本发明再一实施例的用于接收短消息的方法的示意性流程 图。
图 7 是根据本发明再一实施例的用于发送短消息的方法的示意性流程 图。
图 8 是根据本发明实施例的用于接收或发送短消息的装置的示意性框 图。
图 9A和 9B是根据本发明另一实施例的用于接收或发送短消息的装置 的示意性框图。
图 10是根据本发明再一实施例的用于接收或发送短消息的装置的示意 性框图。
图 11是根据本发明再一实施例的用于接收或发送短消息的装置的示意 性框图。 具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行 清楚、 完整地描述， 显然， 所描述的实施例是本发明的一部分实施例， 而不 是全部实施例。 基于本发明中的实施例， 本领域普通技术人员在没有做出创 造性劳动的前提下所获得的所有其他实施例， 都应属于本发明保护的范围。
图 1示出了根据本发明实施例的用于接收或发送短消息的方法 100的示 意性流程图。 如图 1所示， 该方法 100包括：
S110, 接收 MSC/VLR发送的第一消息；
S120, 根据该第一消息确定用户设备处于异常状态；
S130, 向该用户设备发送第二消息， 该第二消息用于指示该用户设备发 起到该 MSC/VLR的附着。
当 MSC/VLR发生故障， 例如单板复位， 或者 MSC/VLR从故障中恢复 等原因， 导致用户设备处于异常状态， 例如 MSC/VLR中的该用户设备的上 下文丟失， MSC/VLR无法处理该用户的短消息， 此时， 该 MSC/VLR会指 示移动管理设备当前流程失败。 因此， 当移动管理设备接收到 MSC/VLR发 送的第一消息， 并根据该第一消息确定用户设备处于异常状态时， 移动管理 设备向用户设备发送第二消息， 该第二消息用于指示该用户设备发起到该 MSC/VLR的附着， 以便于该用户设备能够正常地接收或发送短消息。
本发明实施例的用于接收或发送短消息的方法，通过向用户设备发送指 示该用户设备发起到 MSC/VLR的附着的信息， 使得能够在 MSC/VLR上建 立该用户设备的上下文， 由此能够解决当由于 MSC/VLR发生故障等原因导 致用户设备处于异常状态时无法接收或发送短消息的问题，从而能够实现短 消息的接收或发送， 并能够提高网络的自我恢复能力， 节省网络资源以及提 高用户体验。
应理解， 在本发明实施例中， 用户设备处于异常状态包括单板复位、 用 户上下文丟失以及影响短消息正常接收或发送的其他情况， 例如 MSC/VLR 可以检测到 UE在 MSC/VLR中没有上下文， 或者没有合法的上下文（例如 该上下文未经无线网络确认， 即 MSC/VLR中该 UE的上下文中 "Confirmed by Radio Contact" 标记被设置为 False; 或者未经归属位置寄存器（Home Location Register, 筒称为 "HLR" )确认等）， 或者不存在该 UE的 SGs连接 等。 本发明实施例主要以 MSC/VLR中没有该 UE的上下文， 或者没有合法 的上下文或者不存在该 UE的 SGs连接为例说明用户设备处于异常状态，但 是本发明实施例并不限于此。 还应理解， 在本发明实施例中， 移动管理设备 可以包括移动性管理实体 MME。
在本发明实施例中，根据本发明实施例的方法可以包括用于接收短消息 的方法和用于发送短消息的方法， 下面将分别进行描述。
当用户设备处于异常状态而影响短消息的接收时，移动管理设备接收到 的 MSC/VLR发送的第一消息可以为第一寻呼消息， 此时， 根据本发明实施 例的用于接收短消息的方法如图 2和 3所示。 图 2示出了根据本发明实施例 的用于接收短消息的方法 200的示意性流程图， 如图 2所示， 该方法 200包 括：
在 S210中， 移动管理设备接收 MSC/VLR发送的第一寻呼（ Paging )消 息， 该第一寻呼消息携带 UE 的国际移动用户识别码（International Mobile Subscriber Identification Number , 筒称为 "IMSI" ), 该第一寻呼消息携带的 业务类型为短消息。 由于 MSC/VLR无法为该 UE处理短消息业务， 例如由 于 MSC/VLR发生故障等原因导致用户设备处于异常状态， 例如该 UE的上 下文丟失， 或者 MSC/VLR 中为该 UE 建立的 SGs 连接被释放， 即处于 SGs-Null状态， 此时 MSC/VLR执行 IMSI寻呼处理， 即该第一寻呼消息不 携带 UE位置区标识 ( Location Area Identity, 筒称为 "LAI" )和 /或临时识 别码（Temporary Mobile Subscriber Identity, 筒称为 "TMSI" )等信息。
在 S220中， 移动管理设备根据该第一寻呼消息确定用户设备处于异常 状态。 具体地， 移动管理设备可以根据该第一寻呼消息中未携带用户设备的 位置区标识 LAI或 TMSI,或者根据该第一寻呼信息中未携带 LAI和 TMSI, 由此确定该用户设备处于异常状态， 例如不存在该 UE的上下文， 或者 SGs 连接被释放等。
在 S230中， 移动管理设备确定该用户设备处于空闲态。 在 S240中， 在用户设备处于空闲态时， 移动管理设备向该用户设备发 送第二寻呼消息， 该第二寻呼消息用于指示该用户设备发起到该 MSC/VLR 的附着。
在本发明实施例中，该第二寻呼消息的寻呼类型和 /或寻呼原因值可以用 于指示该用户设备发起到该 MSC/VLR的附着。 可选地， 该第二寻呼消息的 寻呼类型可以设置为 IMSI分离 （IMSI Detach )、 IMSI附着 （ IMSI Attach ) 或者 IMSI重新附着 （IMSI re-attach )等。 该第二寻呼消息的寻呼原因值可 以为与该寻呼类型相应的寻呼原因值， 例如可以设置为 CS业务不可用 （CS Service is not allowed ), IMSI不可 口 ( IMSI is unknown ), 或者无效的上下文 ( Invalid Context )等。 应理解， 在本发明实施例的教导下， 还可以为该第二 寻呼消息设置其它的寻呼类型和 /或寻呼原因值，用于指示该用户设备发起到 该 MSC/VLR的附着， 这些都应该落入本发明的保护范围内。
此时，该第二寻呼消息中的用户设备标识可以是 EPS网络为 UE分配的 临时标识 S-TMSI ( S-Temporary Mobile Subscriber Identity ), 该 S-TMSI可以 由 MME根据 UE的 IMSI, 从 MME中存在的 UE的上下文中获取， 该第二 寻呼消息中的核心网域指示可以设置为 PS或者 cs。
在本发明实施例中， 该第二寻呼消息可以包括用户设备标识和核心网域 标识的特定组合， 该用户设备标识和核心网域标识的特定组合用于指示该用 户设备发起到该 MSC/VLR的附着。 可选地， 当 MME中存在 UE的上下文 时， 该第二寻呼消息可以包括用户设备标识为 IMSI和核心网域标识为 CS 的特定组合。 可选地， 当 MME中没有 UE的合法上下文时， 该第二寻呼消 息可以包括用户设备标识为 IMSI和核心网域标识为 PS的特定组合。
图 3示出了根据本发明另一实施例的用于接收短消息的方法 300的示意 性流程图。 如图 3所示， 该方法 300包括：
S310, 接收 MSC/VLR发送的第一寻呼消息；
S320,根据该第一寻呼消息未包括 LAI和 /或 TMSI, 确定用户设备处于 异常状态；
S330, 确定该用户设备处于连接态；
S340, 向该用户设备发送第二消息， 该第二消息用于指示该用户设备发 起到该 MSC/VLR的附着。
方法 300中的 S310和 S320与方法 200中的 S210和 S220相同，为了筒 洁， 在此不再赘述。
在 S330中， 移动管理设备确定该用户设备处于空闲态， 向用户设备发 送寻呼消息， 用户设备执行服务请求处理以响应该寻呼消息， 并将用户设备 迁移到连接态。 上述处理是现有的标准处理方法， 在此不再赘述。
在 S340中， 在用户设备处于连接态时， 移动管理设备向用户设备发送 第二消息， 该第二消息用于指示该用户设备发起到该 MSC/VLR的附着。 具 体地，该第二消息的类型和 /或包括的原因值可以用于指示该用户设备发起到 该 MSC/VLR的附着。
在本发明实施例中， 可选地， 该第二消息为分离请求（ Detach Request ) 消息，该分离请求消息的分离类型和 /或包括的原因值用于指示该用户设备发 起到该 MSC/VLR的附着。 具体地， 该分离请求消息的分离类型可以设置为 IMSI分离（ IMSI Detach )、 IMSI附着（ IMSI Attach )或者 IMSI重新附着（ IMSI re-attach )等， 该分离请求消息的分离原因值可以为与该分离类型相应的原 因值， 例如可以设置为 CS业务不可用 （ CS Service is not allowed ), IMSI不 可知（ IMSI is unknown ), 或者无效的上下文（ Invalid Context )等。 应理解， 本发明实施例仅以上述三种分离类型为例进行说明， 本发明不应限于此。 在 本发明实施例的教导下，还可以为该分离请求消息设置其它的类型和 /或原因 值， 用于指示该用户设备发起到该 MSC/VLR的附着， 这些都应该落入本发 明的保护范围内。
可选地， 该第二消息为电路交换 CS业务通知 （ CS Service Notification ) 消息， 该 CS业务通知消息包括指示该用户设备发起到该 MSC/VLR的附着 的信息。该 CS业务通知消息的类型和 /或包括的原因值用于指示该用户设备 发起到该 MSC/VLR的附着。 具体地， 该 CS业务通知消息中携带指示 UE 需要发起到 MSC/VLR的附着的信元（即， 消息的类型和 /或原因值）， 该 CS 业务通知消息的类型例如设置为： IMSI分离（IMSI Detach )、IMSI附着（IMSI Attach ), IMSI重新附着（IMSI re-attach )等， 该 CS业务通知消息包括的原 因值可以为与该类型相应的原因值， 例如可以设置为 CS 业务不可用 （CS Service is not allowed ), IMSI不可 口 ( IMSI is unknown ), 或者无效的上下文 ( Invalid Context )等。
可选地， 该第二消息为通知（Notification ) 消息， 该通知消息携带指示 该用户设备发起到该 MSC/VLR的附着的信息。该通知消息的类型和 /或包括 的原因值用于指示该用户设备发起到该 MSC/VLR的附着。 具体地， 该通知 消息中携带指示 UE需要发起到 MSC/VLR的附着的信元（即， 消息的类型 和 /或原因值）。 例如， 该信元可以设置为以下类型之一： IMSI 分离 （IMSI Detach )、 IMSI附着 （ IMSI Attach )或者 IMSI重新附着 （ IMSI re-attach ), 该信元的原因值可以为与该类型相应的原因值， 例如可以设置为 CS业务不 可用 ( CS Service is not allowed ), IMSI不可知 ( IMSI is unknown ), 或者无 效的上下文 ( Invalid Context )等。
本发明实施例的用于接收或发送短消息的方法，通过向用户设备发送指 示该用户设备发起到 MSC/VLR的附着的信息， 使得能够在 MSC/VLR上建 立该用户设备的上下文， 由此能够解决当由于 MSC/VLR发生故障等原因导 致用户设备处于异常状态时无法接收或发送短消息的问题，从而能够实现短 消息的接收或发送， 并能够提高网络的自我恢复能力， 节省网络资源以及提 高用户体验。
当用户设备处于异常状态而影响短消息的发送时，移动管理设备接收到 的 MSC/VLR发送的第一消息可以为释放请求消息。
此时， 如图 1所示， 在 S120中， 根据该第一消息确定用户设备处于异 常状态， 包括： 根据该释放请求消息的原因值确定用户设备处于异常状态。
具体地， 例如， 当 MSC/VLR由于发生故障等原因导致该 UE的上下文 丟失或 UE在 MSC/VLR中没有合法的上下文， 或者该 UE的 SGs连接释放 时， 该 MSC/VLR向 MME发送释放请求（Release Request ) 消息， 该释放 请求消息的原因值指示该用户设备的 IMSI不可知（ "IMSI Unknown" ); 当 MSC/VLR发生故障导致 MSC/VLR中为该 UE建立的 SGs连接被释放， 即 SGs连接处于 SGs-Null状态时， 该 MSC/VLR向 MME发送的释放请求消息 的原因值指示该用户设备的 IMSI 分离 （ "IMSI detached for non-EPS services" )。
在 S130中， 移动管理设备向用户设备发送第二消息， 该第二消息用于 指示该用户设备发起到该 MSC/VLR的附着，以便于该用户设备收发短消息。 可选地，该第二消息的类型和 /或包括的原因值可以用于指示该用户设备发起 到该 MSC/VLR的附着。 可选地， 该第二消息为分离请求（ Detach Request ) 消息、 CS业务通知（ CS Service Notification ) 消息或通知（ Notification ) 消 息。 可选地， 该第二消息的类型可以为 IMSI分离 （IMSI Detach )、 IMSI附 着 （IMSI Attach )或者 IMSI重新附着 （ IMSI re- attach )等。 该第二消息的 原因值可以为与该类型相应的原因值， 例如可以设置为 CS业务不可用 （CS Service is not allowed ), IMSI不可 口 ( IMSI is unknown ), 或者无效的上下文 ( Invalid Context )等。
本发明实施例的用于接收或发送短消息的方法，通过向用户设备发送指 示该用户设备发起到 MSC/VLR的附着的信息， 使得能够在 MSC/VLR上建 立该用户设备的上下文， 由此能够解决当由于 MSC/VLR发生故障等原因导 致用户设备处于异常状态时无法接收或发送短消息的问题，从而能够实现短 消息的接收或发送， 并能够提高网络的自我恢复能力， 节省网络资源以及提 高用户体验。
上文中从移动管理设备的角度，对根据本发明实施例提供的用于接收或 发送短消息的方法进行了详细描述， 下面将从用户设备的角度， 对根据本发 明实施例提供的用于接收或发送短消息的方法进行详细描述。
图 4示出了根据本发明另一实施例的用于发送短消息的方法 400的示意 性流程图。 如图 4所示， 该方法 400包括：
S410, 接收移动管理设备发送的第二消息， 该第二消息用于指示用户设 备发起到 MSC/ VLR的附着；
S420, 根据该第二消息向该移动管理设备发送第三消息， 以发起到该 MSC/VLR的附着。
当由于 MSC/VLR发生故障， 例如单板复位， 或者 MSC/VLR从故障中 恢复等原因， 导致用户设备处于异常状态， 例如 MSC/VLR中该用户设备的 上下文丟失， MSC/VLR无法处理该用户的短消息， 此时， 该 MSC/VLR会 指示移动管理设备当前流程失败。 为了能够实现短消息的接收或发送， 根据 本发明实施例， 移动管理设备会向用户设备发送用于指示用户设备发起到 MSC/ VLR的附着的第二消息， 用户设备在接收到该第二消息后， 向该移动 管理设备发送第三消息， 以发起到该 MSC/VLR的附着， 从而便于该用户设 备能够正常地接收或发送短消息。
本发明实施例提供的用于接收或发送短消息的方法，通过向用户设备发 送指示该用户设备发起到 MSC/VLR的附着的信息， 使得能够在 MSC/VLR 上建立该用户设备的上下文， 由此能够解决当由于 MSC/VLR发生故障等原 因导致用户设备处于异常状态时无法接收或发送短消息的问题，从而能够实 现短消息的接收或发送， 并能够提高网络的自我恢复能力， 节省网络资源以 及提高用户体验。
在本发明实施例中， 该第二消息可以为第二寻呼消息、 分离请求消息、
CS 业务通知消息或通知消息， 这些消息都可以用于指示用户设备发起到 MSC/ VLR的附着， 下文中将分情况分别进行描述。
在本发明实施例中， 可选地， 该第三消息为跟踪区更新请求消息或附着 请求消息。 即， 用户设备根据该第二消息， 可以向该移动管理设备发送跟踪 区更新请求消息或附着请求消息， 从而用户设备能够在 MSC/VLR上重新注 册， 在 MSC/VLR上建立该用户设备的上下文， 由此能够便于用户设备正常 地接收或发送短消息。
在本发明实施例中，根据本发明实施例的方法可以包括接收短消息的方 法和发送短消息的方法， 下面将分别进行描述。
当用户设备处于异常状态而影响短消息的接收时， MSC/VLR可以向移 动管理设备发送 IMSI寻呼消息， 使得移动管理设备获知该用户设备处于异 常状态， 而无法正常接收短消息。 此时， 当用户设备处于空闲态时， 移动管 理设备将向用户设备发送为第二寻呼消息的第二消息， 该第二寻呼消息指示 用户设备发起到该 MSC/VLR的附着， 用户设备根据该第二寻呼消息， 可以 向该移动管理设备发送跟踪区更新请求消息或附着请求消息，从而便于接收 短消息。
可选地， 用户设备根据该第二寻呼消息的寻呼类型或寻呼原因值， 向该 移动管理设备发送跟踪区更新请求（Tracking Area Update Request ) 消息或 者附着请求（ Attach Request )消息。 该跟踪区更新请求消息的类型可以为联 合跟踪区 /位置区更新（ Combined TA/LA Update , 其中跟踪区 Tracking Area 筒称为 "TA" , 位置区 Location Area 筒称为 "LA" )或周期性跟踪区更新 ( Periodic TA Update )。 该附着请求消息的类型可以为联合附着 （ Combined EPS/IMSI Attach )。
具体地， 当用户设备接收到寻呼类型为 IMSI分离（ IMSI Detach )、 IMSI 附着 （IMSI Attach )或者 IMSI重新附着 （ IMSI re-attach ) 的第二寻呼消息 时， 或当用户设备接收到寻呼原因值为与该寻呼类型相应的原因值的第二寻 呼消息时， 例如为 CS业务不可用 ( CS Service is not allowed ), IMSI不可知 ( IMSI is unknown ), 或者无效的上下文（ Invalid Context )等， 用户设备可 以向移动管理设备发送跟踪区更新请求消息或附着请求消息。
在本发明实施例中， 用户设备可以根据第二寻呼消息中的用户设备标识 和核心网域标识的特定组合， 向该移动管理设备发送跟踪区更新请求消息或 附着请求消息。
可选地， 用户设备根据该第二寻呼消息中的用户设备标识和核心网域标 识的特定组合为国际移动用户识别码 IMSI和电路交换 CS的特定组合， 向 该移动管理设备发送跟踪区更新请求消息或附着请求消息， 该跟踪区更新请 求消息的类型可以为联合跟踪区 /位置区更新或周期性跟踪区更新，该附着请 求消息的类型可以为联合附着 （ Combined EPS/IMSI Attach )。
可选地， 用户设备根据该第二寻呼消息中的用户设备标识和核心网域标 识的特定组合为 IMSI和分组交换 PS的特定组合，向该移动管理设备发送附 着请求（ Attach Request )消息。该附着请求消息的类型为联合附着（ Combined EPS/IMSI Attach )。
当移动管理设备接收 MSC/VLR发送的 IMSI寻呼消息， 表明用户设备 处于异常状态而影响短消息的接收时，如果用户设备处于连接态或从空闲态 迁移到连接态时， 那么移动管理设备向用户设备发送第二消息， 用于指示用 户设备发起到 MSC/VLR的附着。
当用户设备处于异常状态而影响短消息的发送时，移动管理设备接收到 MSC/VLR发送的可以为释放请求消息的第一消息。 移动管理设备根据该释 放请求消息的原因值确定用户设备处于异常状态后， 可以向用户设备发送第 二消息， 用于指示用户设备发起到 MSC/VLR的附着。
在本发明实施例中，该第二消息的类型和 /或包括的原因值可以用于指示 该用户设备发起到该 MSC/VLR的附着。 可选地， 该第二消息为分离请求消 息、 CS 业务通知消息或通知消息。 对于第二消息的详细描述可以参考上文 描述的方法 100至 300中的相关描述， 为了筒洁， 在此不再赘述。
当用户设备接收到移动管理设备发送的第二消息之后，根据本发明实施 例的用于发送短消息的方法 500还可以包括：
S530,用户设备向该移动管理设备发送对该第二消息进行响应的第四消 息。 例如， 该第四消息可以是分离接受 （Detach Accept ) 消息。
在用户设备向该移动管理设备发送跟踪区更新请求消息或附着请求消 息之前、 之后或同时， 该方法 500还可以包括： S540, 向该用户设备上的短消息协议栈或应用程序发送暂停指示， 该暂 停指示用于指示暂停短消息的发送。
可选地， 该方法 500还可以包括：
S550,在接收到该移动管理设备发送的对该第三消息进行响应的消息之 后， 向该用户设备上的短消息协议栈或应用程序发送重发指示， 该重发指示 用于指示重新开始短消息的发送。
例如，在用户设备接收到移动管理设备发送的对跟踪区更新请求消息或 附着请求消息进行响应的跟踪区更新接受 （ Tracking Area Accept ) 消息或附 着接受 （ Attach Accept ) 消息之后， 向该用户设备上的短消息协议栈或应用 程序发送重发指示， 以重新发送短消息。
该方法 500中的 S510和 S520与方法 400中的 S410和 S420相同，为了 筒洁， 在此不再赘述。
应理解， 上述各过程的序号的大小并不意味着执行顺序的先后， 各过程 的执行顺序应以其功能和内在逻辑确定， 而不应对本发明实施例的实施过程 构成任何限定。
本发明实施例提供的用于接收或发送短消息的方法，通过向用户设备发 送指示该用户设备发起到 MSC/VLR的附着的信息， 使得能够在 MSC/VLR 上建立该用户设备的上下文， 由此能够解决当由于 MSC/VLR发生故障等原 因导致用户设备处于异常状态时无法接收或发送短消息的问题，从而能够实 现短消息的接收或发送， 并能够提高网络的自我恢复能力， 节省网络资源以 及提高用户体验。
下面将以 EPS网络中接收或发送短消息为例，对根据本发明实施例的用 于接收或发送短消息的方法进行具体描述。
图 6示出了根据本发明实施例的用于接收短消息的方法 600的示意性流 程图， 该实施例针对用户设备收到短消息的场景， 即 MT SMS场景。 如图 6 所示， 该方法 600包括：
5601 , 短消息中心 （SMS Center , 筒称为 "SC" ) 将短消息发送给 SMS-GMSCo
5602, SMS-GMSC执行路由信息查询处理， 从归属位置寄存器（ Home Location Register,筒称为 "HLR" )/归属用户服务器（ Home Subscriber Server, 筒称为 "HSS" )获取当前 UE附着的 MSC/VLR。 5603 , SMS-GMSC将该短消息转发给 UE附着的 MSC/VLR。
5604, 当用户设备处于异常状态， 无法为该 UE处理短消息业务时， 例 如 MSC/VLR发生故障导致该 UE的上下文丟失，或者 MSC/VLR中为该 UE 建立的 SGs连接被释放， 即处于 SGs-Null状态等， MSC/VLR执行 IMSI寻 呼处理， 即向 MME发送寻呼消息， 该寻呼消息携带 UE的 IMSI, 不携带 UE的位置区标识 LAI等， 该寻呼消息的业务类型为短消息。
此时， MSC/VLR也可以立即通过 SMS-GMSC向 SC反馈短消息发送失 败， SC收到该反馈响应后， 执行 S607。 MSC/VLR也可以緩存该短消息， 以便等后续该 UE附着到 MSC/VLR后可以立即发送该緩存的短消息。
如果 UE当前处于空闲态，那么流程进行到 S605、 S606,再进行到 S613; 如果 UE当前处于连接态， 则不执行寻呼流程， 那么流程直接进行到 S611。
5605 , UE当前处于空闲态， 此时 MME向演进基站（ Evolved Node B , 筒称为 "eNB" )发送寻呼消息， 该寻呼消息中携带 UE的标识以及核心网域 指示 （CN Domain )。
该寻呼消息中如果没有包括指示 UE发起到 MSC/VLR附着的信息， 则 步骤 606中 eNB发送给 UE的寻呼消息中也不包括指示 UE发起到 MSC/VLR 的附着的信息， 并执行步骤 S610。
根据 MME中记录的 UE上下文信息， 该寻呼消息可以指示 UE发起到 MSC/VLR的附着， 或者到 MME和 MSC/VLR的附着：
1 ) 当 MME中存在 UE的上下文时，
a )上述寻呼消息中包括要求 UE发起到 MSC/VLR的附着的指示， 该附 着指示具体可以通过特定的寻呼原因值或者寻呼类型等信元来表示， 其值具 体可以设置为以下类型： "IMSI分离 （IMSI Detach "IMSI 附着 （IMSI Attach )" 或者 "IMSI重新附着 ( IMSI re-attach )" 等， 寻呼原因值可以设置 为与该类型相应的原因值，例如可以设置为 CS业务不可用（ CS Service is not allowed ), IMSI 不可知 ( IMSI is unknown ), 或者无效的上下文 ( Invalid Context )等。 此时， 该寻呼消息中的用户标识可以是 EPS网络为 UE分配的 临时标识 S-TMSI, 核心网域指示可以设置为 PS或者 CS , 其中该临时标识 S-TMSI可以由 MME根据 UE的 IMSI, 从 UE在 MME中的上下文中获取。
b )上述寻呼消息通过特定的 UE标识和核心网域指示来指示 UE发起到
MSC/VLR的附着，例如该寻呼消息中的用户标识为 MME在 S604中收到的 IMSI, 核心网域指示设置为 CS。
2 )当 MME中没有 UE的合法上下文时， 则上述寻呼消息中的用户标识 为 MME在 S604中收到的 IMSI, 以指示 UE发起到 MME和 MSC/VLR的 联合附着流程， 此时核心网域指示可以设置为 PS。
S606, eNB根据收到的来自 MME的寻呼消息， 向 UE发送寻呼消息。 该寻呼消息中携带 S605提供的 UE的标识、核心网域标识以及指示 UE发起 附着的指示。
5607, 短消息中心 SC无法成功发送短消息时， 例如， 发送定时器超时， 或者收到 MSC/VLR发送的短消息发送失败指示等， 向 SMS-GMSC发送终 端可达通知请求（ UE Reachability Notification Request )消息，緩存该短消息。
5608, SMS-GMSC向 HLR/HSS发送终端可达通知请求（ UE Reachability Notification Request ) 消息。
5609, HLR/HSS向 MSC/VLR发送终端可达通知请求（ UE Reachability Notification Request ) 消息。 MSC/VLR可以设置通知请求标识。
应理解， 上述各过程的序号的大小并不意味着执行顺序的先后， 各过程 的执行顺序应以其功能和内在逻辑确定， 而不应对本发明实施例的实施过程 构成任何限定。 例如， 上述 S607至 S609与之前的 S604至 S606, 以及之后 的 S611至 S615没有时序关系。
5610, 如果 UE在 S606中收到的寻呼消息中没有包括指示 UE发起到 MSC/VLR附着的指示， 则该 UE执行服务请求（ Service Request )流程， 建 立信令连接， 将用户转为连接态， 流程进行到 S611。
如果 UE在 S606中收到的寻呼消息中包括指示 UE发起到 MSC/VLR附 着的指示， 则该 UE不执行 S610, 即该 UE不执行服务请求流程， 流程进行 到 S613。
S611 , UE 当前处于连接态， 此时 MME根据 S604 中收到的指示， 向
UE发送通知请求消息， 以指示 UE发起到 MSC/VLR的附着。
上述指示 UE发起到 MSC/VLR的附着的通知请求消息， 具体可以包括 以下几种实现方式：
1 )该通知请求消息可以为分离请求（ Detach Request ) 消息， 该分离请 求消息中的分离类型 （Detach Type )或者该分离请求消息中的原因 （Cause ) 值设置为指示 UE需要发起到 MSC/VLR的附着。 该分离类型可以设置为以下类型： "IMSI分离 （IMSI Detach )"、 "IMSI 附着 ( IMSI Attach )" 或者 "IMSI重新附着 ( IMSI re-attach )" 等， 该分离原 因值可以设置为与该分离类型相应的原因值， 例如可以设置为 CS业务不可 用 ( CS Service is not allowed ), IMSI不可知（ IMSI is unknown ), 或者无效 的上下文（ Invalid Context )等。
2 )该通知请求消息可以为 CS业务通知（ CS Service Notification )消息， 该 CS业务通知消息中携带指示 UE需要发起到 MSC/VLR的附着的信元（即， 消息的类型和 /或原因值）， 例如该消息类型可以设置为以下类型： "IMSI分 离 ( IMSI Detach )"、 "IMSI附着 ( IMSI Attach )"或者 "IMSI重新附着 ( IMSI re-attach )"等，类似地，该消息的原因值可以设置为与该类型相应的原因值， 例如可以设置为 CS业务不可用 （CS Service is not allowed ), IMSI不可知 ( IMSI is unknown ), 或者无效的上下文 ( Invalid Context )等。
3 )该通知请求消息可以为通知 ( Notification ) 消息， 该通知消息中携 带指示 UE需要发起到 MSC/VLR的附着的信元（即， 消息的类型和 /或原因 值）。 例如可以将该通知消息中的通知指示（ Notification Indicator )信元设置 为以下类型之一： "IMSI分离 （IMSI Detach )"、 "IMSI附着（ IMSI Attach )" 或者 "IMSI重新附着 （ IMSI re-attach )" 等， 类似地， 该通知指示信元的原 因值可以设置为与该类型相应的原因值，例如可以设置为 CS业务不可用（ CS Service is not allowed ), IMSI不可 口 ( IMSI is unknown ), 或者无效的上下文 ( Invalid Context )等。
5612、 UE可以向 MME发送对该通知请求消息进行响应的通知响应消 息， 该通知响应消息例如为分离接受 （ Detach Accept ) 消息等。
5613, UE根据 S606或者 S611中收到的指示， 发起跟踪区更新流程或 者附着流程。
具体地， 当满足以下条件之一时， UE发起跟踪区更新流程或附着流程， 向 MME发送跟踪区更新请求（ Tracking Area Update Request )消息， 更新类 型为联合跟踪区 /位置区更新 （Combined TA/LA Update ) 或者周期性更新 ( Periodic TA Update ), 附着请求消息的类型可以为联合附着 （Combined EPS/IMSI Attach ):
1 ) UE收到了指示 UE发起到 MSC/VLR附着的指示， 例如 "IMSI分离
( IMSI Detach )"、 "IMSI附着（ IMSI Attach )" 或者 "IMSI重新附着（ IMSI re-attach )，， 等。
2 ) UE收到了特定的 UE标识和核心网域指示的组合， 例如 UE的标识 为 IMSI, 核心网域指示为 CS。
当满足以下条件之一时， UE发起附着流程， 向 MME发送附着请求 ( Attach Request )消息， 附着类型为联合附着（ Combined EPS/IMSI Attach ):
1 ) UE收到了特定的 UE标识和核心网域指示的组合， 例如 UE的标识 为 IMSI, 核心网域指示为 PS。
S614, MME发起到 MSC/VLR的注册， 向 MSC/VLR发送位置更新请 求消息 ( Location Update Request )。
S615 , MSC/VLR建立该 UE的上下文，为 UE分配临时识别码（ Temporary
Mobile Subscriber Identity, 筒称为 "TMSI" ), 向 MME发送位置更新接受消 息 ( Location Update Accept )。
S616 , MME向 UE发送跟踪区更新接受（ Tracking Area Accept )消息或 者附着接受 （ Attach Accept ) 消息。
S617 , UE可以向 MME发送跟踪区更新完成（ Tracking Area Complete ) 消息或者附着完成 ( Attach Complete ) 消息。
5618, MME收到 UE发送的完成消息之后， 向 MSC/VLR发送 TMSI 重分配（ TMSI Reallocation Complete ) 消息。
如果 MSC/VLR中緩存了该 UE的短消息 （例如 S604中进行了緩存）， 则 MSC/VLR可以直接执行 S625, 等收到 S626的服务请求消息之后， 执行 S627向 UE发送短消息； 也可以省略 S625和 S626, 直接执行 S627, 向 UE 发送短消息。 该处理也可以在 S615之后立即执行。
5619, 如果在 S609中 MSC/VLR设置了通知请求标识， 则 MSC/VLR 向 HLR/HSS发送终端激活通知（UE Activity Notification ) 消息。
S620 , HLR/HSS 向 SMS-GMSC 发送终端激活通知 （ UE Activity
Notification ) 消息。
5621 , SMS-GMSC向短消息中心 SC发送终端激活通知 （ UE Activity Notification ) 消息。
5622, 短消息中心 SC重新将緩存的短消息发送给 SMS-GMSC。
S623 , SMS-GMSC向 HLR/HSS查询当前 UE附着的 MSC/VLR。
S624, SMS-GMSC将短消息转发给 UE附着的 MSC/VLR。 5625 , MSC/VLR向 MME发送寻呼（ Paging )消息， 携带 UE的 IMSI, 以及该用户设备的位置区标识（LAI )等信息， 业务类型为短消息。
如果 UE在 MME中处于空闲态， 则当 MME收到该寻呼消息之后， 需 要先执行标准的寻呼流程， UE 收到该寻呼消息后发起服务请求 （ Service Request ) 流程， 将 UE转为连接态。 为了筒洁， 此处不再赘述。
5626, MME向 MSC/VLR发送服务请求（ Service Request ) 消息。
5627, MSC/VLR将短消息封装在下行数据传递（Downlink Unitdata ) 消息中发送给 MME。 消息中发送给 UE。
5629, UE将短消息确认消息封装在上行 NAS传递消息中发送给 MME。
5630 , MME 将上述短消息确认消息封装在上行数据传递 （Uplink Unitdata ) 消息中发送给 MSC/VLR。
5631 , UE将短消息传递报告 ( delivery report )封装在上行 NAS传递消 息中发送给 MME。
5632, MME将上述短消息传递报告 ( delivery report )封装在上行数据 传递（ Uplink Unitdata ) 消息中发送给 MSC/VLR。
5633 , MSC/VLR向 SMS-GMSC发送短消息传递才艮告 ( delivery report )。
5634, SMS-GMSC向 SC发送短消息传递报告 ( delivery report )。
S635 , MSC/VLR将短消息传递报告 ( delivery report )确认封装在下行 数据传递（ Downlink Unitdata ) 消息中发送给 MME。
5636, MME将短消息传递报告 ( delivery report )确认封装在下行 NAS 传递（ Downlink NAS Transport ) 消息中发送给 UE。
5637 , MSC/VLR向 MME发送释放请求（ Release Request ) 消息。
应理解， 上述各过程的序号的大小并不意味着执行顺序的先后， 各过程 的执行顺序应以其功能和内在逻辑确定， 而不应对本发明实施例的实施过程 构成任何限定。 例如， S635和 S633没有时序关系。
本发明实施例提供的用于接收或发送短消息的方法，通过向用户设备发 送指示该用户设备发起到 MSC/VLR的附着的信息， 使得能够在 MSC/VLR 上建立该用户设备的上下文， 由此能够解决当由于 MSC/VLR发生故障等原 因导致用户设备处于异常状态时无法接收或发送短消息的问题，从而能够实 现短消息的接收或发送， 并能够提高网络的自我恢复能力， 节省网络资源以 及提高用户体验。
图 7是根据本发明实施例的用于发送短消息的方法 700 的示意性流程 图， 该实施例针对用户设备发送短消息的场景， 即 MO SMS场景。 如图 7 所示， 该方法 700包括：
S701 , 当 UE需要发送短消息时， 如果 UE处于空闲态， 则 UE执行服 务请求（ Service Request )流程。即 UE向 MME发送服务请求（ Service Request ) 消息， 建立信令连接， 将 UE转为连接态。 如果 UE当前处于连接态， 则流 程直接进行到 S702。
S702 , UE 将需要发送的短消息封装在上行非接入层 （ Non-Access
Stratum, 筒称为 "NAS" )传递（Uplink NAS Transport ) 消息中， 发送给 MME。
S703, MME将收到的短消息封装在上行数据传递（Uplink Unitdata )消 息中发送给 MSC/VLR。
S704, MSC/VLR中用户设备处于异常状态， 无法为该 UE处理短消息 业务时，例如 MSC/VLR发生故障导致该 UE的上下文丟失、或者 MSC/VLR 中为该 UE建立的 SGs连接被释放， 即处于 SGs-Null状态等， 该 MSC/VLR 向 MME发送释放请求（ Release Request )消息， 指示该用户设备的 IMSI不 可知（ "IMSI Unknown" )或者该用户设备的 IMSI分离 （ "IMSI detached for non-EPS services" )。
上述 SGs是 MME和 MSC/VLR之间接口的名称， SGs连接是在 MME 和 MSC/VLR之间为 UE建立的一个通道， MME和 MSC/VLR上会分别维护 该 SGs连接的状态。
S705, MME根据 S704中收到的指示， 向 UE发送通知请求消息， 以指 示 UE发起到 MSC/VLR的附着。
上述指示 UE发起到 MSC/VLR的附着的通知请求消息， 具体可以包括 以下几种实现方式：
1 )该通知请求消息可以为分离请求（ Detach Request ) 消息， 该分离请 求消息中的分离类型 （Detach Type )或者该分离请求消息中的原因 （Cause ) 值设置为指示 UE需要发起到 MSC/VLR的附着。
该分离类型可以设置为以下类型： "IMSI分离 （IMSI Detach )"、 "IMSI 附着 ( IMSI Attach )" 或者 "IMSI重新附着 ( IMSI re-attach )" 等， 该分离原 因值可以设置为与该分离类型相应的原因值， 例如可以设置为 CS业务不可 用 ( CS Service is not allowed ), IMSI不可知（ IMSI is unknown ), 或者无效 的上下文（ Invalid Context )等。
2 )该通知请求消息可以为 CS业务通知（ CS Service Notification )消息， 该 CS业务通知消息中携带指示 UE需要发起到 MSC/VLR的附着的信元（即， 消息的类型和 /或原因值）， 例如该消息类型可以设置为以下类型： "IMSI分 离 ( IMSI Detach )"、 "IMSI附着 ( IMSI Attach )"或者 "IMSI重新附着 ( IMSI re-attach )"等，类似地，该消息的原因值可以设置为与该类型相应的原因值， 例如可以设置为 CS业务不可用 （CS Service is not allowed ), IMSI不可知 ( IMSI is unknown ), 或者无效的上下文 ( Invalid Context )等。
3 )该通知请求消息可以为通知 ( Notification ) 消息， 该通知消息中携 带指示 UE需要发起到 MSC/VLR的附着的信元（即， 消息的类型和 /或原因 值）。 例如可以将该通知消息中的通知指示（ Notification Indicator )信元设置 为以下类型之一： "IMSI分离 （IMSI Detach )"、 "IMSI附着（ IMSI Attach )" 或者 "IMSI重新附着 （ IMSI re-attach )" 等， 类似地， 该通知指示信元的原 因值可以设置为与该类型相应的原因值，例如可以设置为 CS业务不可用（ CS Service is not allowed ), IMSI不可 口 ( IMSI is unknown ), 或者无效的上下文 ( Invalid Context )等。
S706, UE可以向 MME发送对该通知请求消息进行响应的通知响应消 息， 该通知响应消息例如为分离接受 （ Detach Accept ) 消息等。
5707, UE根据 S705 中收到的发起到 MSC/VLR的附着的指示， 例如 "IMSI Attach" , "IMSI Detach" 等， 发起跟踪区更新流程或附着流程， 向
MME发送跟踪区更新请求（ Tracking Area Update Request, TAU Request ) 消息或附着请求（ Attach Request )消息。 该跟踪区更新请求消息的类型可以 是联合跟踪区 /位置区更新 ( Combined TA/LA Update ), 或者周期性跟踪区更 新 （Periodic TA Update ); 该附着请求消息的类型为联合更新 （Combined
EPS/IMSI Attach )。
UE在发起跟踪区更新流程之前、 之后或同时， 还可以指示 UE上的短 消息协议栈 /应用程序暂停短消息发送。
5708, MME发起到 MSC/VLR的注册， 向 MSC/VLR发送位置更新请 求消息 ( Location Update Request )。
5709, MSC/VLR建立该 UE的上下文，为该 UE分配 TMSI,并向 MME 发送位置更新接受消息 （ Location Update Accept )。
5710 , MME向 UE发送跟踪区更新接受（ Tracking Area Accept )消息或 者附着接受 （ Attach Accept ) 消息。
5711 , UE可以向 MME发送跟踪区更新完成（ Tracking Area Complete ) 消息或者附着完成 ( Attach Complete ) 消息。
UE在收到 S710的接受消息之后，可以通知 UE上的短消息协议栈 /应用 程序重新发送短消息。
S712, MME收到 S711中的完成消息之后， 向 MSC/VLR发送 TMSI重 分配（ TMSI Reallocation Complete ) 消息。
5713 , UE将需要发送的短消息封装在在上行 NAS传递（Uplink NAS Transport ) 消息中， 发送给 MME。
5714, MME将收到的短消息封装在上行数据传递（ Uplink Unitdata )消 息中发送给 MSC/VLR。
5715, MSC/VLR将收到的短消息发送给 SMS-IWMSC。
5716, SMS-IWMSC将收到的短消息发送给短消息中心 SC。
5717, 短消息中心 SC向 SMS-IWMSC发送短消息传递报告 ( delivery report )。
S718, SMS-IWMSC向 MSC/VLR发送短消息传递才艮告（ delivery report )。
5719, MSC/VLR向 MME发送短消息确认消息。
5720 , MME向 UE发送短消息确认消息。
5721 , MSC/VLR收到 S718的短消息传递报告 ( delivery report )后， 将 所述收到的短消息传递报告封装在下行数据传递（ Downlink Unitdata ) 消息 中发送给 MME。
5722, MME将上述短消息传递报告封装在下行 NAS传递（Downlink NAS Transport ) 消息中发送给 UE。
5723 , UE确认收到该短消息传递报告， 并将确认结果封装在上行 NAS 传递（ Uplink NAS Transport ) 消息中， 发送给 MME。
S724, MME将收到
息中， 发送给 MSC/VLRC S725 , MSC/VLR向 MME发送释放请求（ Release Request )消息， 结束 短消息发送流程。
应理解， 上述各过程的序号的大小并不意味着执行顺序的先后， 各过程 的执行顺序应以其功能和内在逻辑确定， 而不应对本发明实施例的实施过程 构成任何限定。例如， S719和 S714至 S717没有时序关系， S719可以在 S714 之前、 之后或同时发送。
本发明实施例提供的用于接收或发送短消息的方法，通过向用户设备发 送指示该用户设备发起到 MSC/VLR的附着的信息， 使得能够在 MSC/VLR 上建立该用户设备的上下文， 由此能够解决当由于 MSC/VLR发生故障等原 因导致用户设备处于异常状态时无法接收或发送短消息的问题，从而能够实 现短消息的接收或发送， 并能够提高网络的自我恢复能力， 节省网络资源以 及提高用户体验。
下面将结合图 8至 11详细描述根据本发明实施例的用于接收或发送短 消息的装置。
图 8示出了根据本发明实施例提供的用于接收或发送短消息的装置 800 的示意性框图。 如图 8所示， 该装置 800包括：
接收模块 810, 用于接收 MSC/VLR发送的第一消息；
第一确定模块 820, 用于根据该第一消息确定用户设备处于异常状态； 发送模块 830, 用于向该用户设备发送第二消息， 该第二消息用于指示 该用户设备发起到该 MSC/VLR的附着。
本发明实施例提供的用于接收或发送短消息的装置，通过向用户设备发 送指示该用户设备发起到 MSC/VLR的附着的信息， 使得能够在 MSC/VLR 上建立该用户设备的上下文， 由此能够解决当由于 MSC/VLR发生故障等原 因导致用户设备处于异常状态时无法接收或发送短消息的问题，从而能够实 现短消息的接收或发送， 并能够提高网络的自我恢复能力， 节省网络资源以 及提高用户体验。
可选地， 如图 9A所示， 根据本发明实施例的用于接收或发送短消息的 装置 800还包括：
第二确定模块 840, 用于在该第一消息为第一寻呼消息时， 确定该用户 设备处于空闲态，
该发送模块 830具体用于向该用户设备发送第二寻呼消息，该第二寻呼 消息指示该用户设备发起到该 MSC/VLR的附着。
可选地， 如图 9B所示， 该装置 800还包括：
第三确定模块 850, 用于在该第一消息为第一寻呼消息， 且该发送模块 发送该第二寻呼消息之前， 确定该用户设备处于连接态。
根据本发明实施例的用于发送短消息的装置 800可对应于本发明实施例 中的移动管理设备，并且装置 800中的各个模块的上述和其它操作和 /或功能 分别为了实现图 1至图 3中的各个方法 100至 300的相应流程， 为了筒洁， 在此不再赘述。
本发明实施例的用于接收或发送短消息的装置，通过向用户设备发送指 示该用户设备发起到 MSC/VLR的附着的信息， 使得能够在 MSC/VLR上建 立该用户设备的上下文， 由此能够解决当由于 MSC/VLR发生故障等原因导 致用户设备处于异常状态时无法接收或发送短消息的问题，从而能够实现短 消息的接收或发送， 并能够提高网络的自我恢复能力， 节省网络资源以及提 高用户体验。
图 10示出了根据本发明实施例的用于接收或发送短消息的装置 900的 示意性框图。 如图 10所示， 该装置 900包括：
接收模块 910, 用于接收移动管理设备发送的第二消息， 该第二消息用 于指示该装置发起到移动交换中心 MSC/拜访位置寄存器 VLR的附着； 第一发送模块 920, 用于根据该第二消息， 向该移动管理设备发送第三 消息， 以发起到该 MSC/VLR的附着。
本发明实施例的用于接收或发送短消息的装置，通过向用户设备发送指 示该用户设备发起到 MSC/VLR的附着的信息， 使得能够在 MSC/VLR上建 立该用户设备的上下文， 由此能够解决当由于 MSC/VLR发生故障等原因导 致用户设备处于异常状态时无法接收或发送短消息的问题，从而能够实现短 消息的接收或发送， 并能够提高网络的自我恢复能力， 节省网络资源以及提 高用户体验。
可选地， 如图 11 所示， 根据本发明实施例的用于接收或发送短消息的 装置 900还包括：
第二发送模块 930, 用于在该接收模块接收到该第二消息之后， 向该移 动管理设备发送对该第二消息进行响应的第四消息。
可选地， 如图 11所示， 该装置 900还包括： 第三发送模块 940, 用于向该装置上的短消息协议栈或应用程序发送暂 停指示， 该暂停指示用于指示暂停短消息的发送。
可选地， 如图 11所示， 该装置 900还包括：
第四发送模块 950, 用于在接收到该移动管理设备发送的对该第三消息 进行响应的消息之后， 向该装置上的短消息协议栈或应用程序发送重发指 示， 该重发指示用于指示重新开始短消息的发送。
根据本发明实施例的用于接收或发送短消息的装置 900可对应于本发明 实施例中的用户设备，并且装置 900中的各个模块的上述和其它操作和 /或功 能分别为了实现图 4至图 5中的各个方法 400至 500的相应流程，为了筒洁， 在此不再赘述。
本发明实施例的用于接收或发送短消息的装置，通过向用户设备发送指 示该用户设备发起到 MSC/VLR的附着的信息， 使得能够在 MSC/VLR上建 立该用户设备的上下文， 由此能够解决当由于 MSC/VLR发生故障等原因导 致用户设备处于异常状态时无法接收或发送短消息的问题，从而能够实现短 消息的接收或发送， 并能够提高网络的自我恢复能力， 节省网络资源以及提 高用户体验。
本领域普通技术人员可以意识到， 结合本文中所公开的实施例描述的各 示例的单元及算法步骤， 能够以电子硬件、 计算机软件或者二者的结合来实 现， 为了清楚地说明硬件和软件的可互换性， 在上述说明中已经按照功能一 般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执 行， 取决于技术方案的特定应用和设计约束条件。 专业技术人员可以对每个 特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超 出本发明的范围。
所属领域的技术人员可以清楚地了解到， 为了描述的方便和筒洁， 上述 描述的系统、 装置和单元的具体工作过程， 可以参考前述方法实施例中的对 应过程， 在此不再赘述。
在本申请所提供的几个实施例中， 应该理解到， 所揭露的系统、 装置和 方法， 可以通过其它的方式实现。 例如， 以上所描述的装置实施例仅仅是示 意性的， 例如， 所述单元的划分， 仅仅为一种逻辑功能划分， 实际实现时可 以有另外的划分方式， 例如多个单元或组件可以结合或者可以集成到另一个 系统， 或一些特征可以忽略， 或不执行。 另外， 所显示或讨论的相互之间的 耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或 通信连接， 也可以是电的， 机械的或其它的形式连接。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作 为单元显示的部件可以是或者也可以不是物理单元， 即可以位于一个地方， 或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或 者全部单元来实现本发明实施例方案的目的。
另外， 在本发明各个实施例中的各功能单元可以集成在一个处理单元 中， 也可以是各个单元单独物理存在， 也可以是两个或两个以上单元集成在 一个单元中。 上述集成的单元既可以采用硬件的形式实现， 也可以采用软件 功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销 售或使用时， 可以存储在一个计算机可读取存储介质中。 基于这样的理解， 本发明的技术方案本质上或者说对现有技术做出贡献的部分， 或者该技术方 案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在 一个存储介质中， 包括若干指令用以使得一台计算机设备（可以是个人计算 机， 服务器， 或者网络设备等）执行本发明各个实施例所述方法的全部或部 分步骤。 而前述的存储介质包括： U盘、 移动硬盘、 只读存储器（ROM, Read-Only Memory ), 随机存取存储器（RAM, Random Access Memory ), 磁碟或者光盘等各种可以存储程序代码的介质。
以上所述， 仅为本发明的具体实施方式， 但本发明的保护范围并不局限 于此， 任何熟悉本技术领域的技术人员在本发明揭露的技术范围内， 可轻易 想到各种等效的修改或替换， 这些修改或替换都应涵盖在本发明的保护范围 之内。 因此， 本发明的保护范围应以权利要求的保护范围为准。

Claims

权利要求
1、 一种用于接收或发送短消息的方法， 其特征在于， 包括：
接收移动交换中心 MSC/拜访位置寄存器 VLR发送的第一消息； 根据所述第一消息确定用户设备处于异常状态；
向所述用户设备发送第二消息，所述第二消息用于指示所述用户设备发 起到所述 MSC/VLR的附着。
2、 根据权利要求 1所述的方法， 其特征在于， 所述第一消息为第一寻 呼消息，
所述根据所述第一消息确定所述用户设备处于异常状态， 包括： 根据所述第一寻呼消息未包括所述用户设备的位置区标识 LAI 或临时 识别码 TMSI, 确定所述用户设备处于异常状态。
3、 根据权利要求 2所述的方法， 其特征在于， 所述方法还包括： 确定所述用户设备处于空闲态，
所述向所述用户设备发送第二消息， 包括：
向所述用户设备发送第二寻呼消息， 所述第二寻呼消息指示所述用户设 备发起到所述 MSC/VLR的附着。
4、 根据权利要求 3所述的方法， 其特征在于， 所述第二寻呼消息的寻 呼类型或寻呼原因值用于指示所述用户设备发起到所述 MSC/VLR的附着。
5、 根据权利要求 3所述的方法， 其特征在于， 所述第二寻呼消息包括 用户设备标识和核心网 i或标识的组合 , 所述用户设备标识和核心网 i或标识的 组合用于指示所述用户设备发起到所述 MSC/VLR的附着。
6、 根据权利要求 2所述的方法， 其特征在于， 在所述向用户设备发送 第二消息之前， 所述方法还包括：
确定所述用户设备处于连接态。
7、 根据权利要求 1所述的方法， 其特征在于， 所述第一消息为释放请 求消息，
所述根据所述第一消息确定所述用户设备处于异常状态， 包括： 根据所述释放请求消息的原因值指示的所述用户设备的国际移动用户 识别码 IMSI不可知或者所述用户设备的 IMSI分离，确定所述用户设备处于 异常状态。
8、 根据权利要求 6或 7所述的方法， 其特征在于， 所述第二消息为分 离请求消息， 所述分离请求消息的分离类型或包括的原因值用于指示所述用 户设备发起到所述 MSC/VLR的附着。
9、 根据权利要求 6或 7所述的方法， 其特征在于， 所述第二消息为通 知消息或电路交换 CS业务通知消息， 所述通知消息或所述 CS业务通知消 息包括指示所述用户设备发起到所述 MSC/VLR的附着的信息。
10、 根据权利要求 6或 7所述的方法， 其特征在于， 所述第二消息为通 知消息或 CS业务通知消息， 所述通知消息或所述 CS业务通知消息的类型 或包括的原因值用于指示所述用户设备发起到所述 MSC/VLR的附着。
11、 根据权利要求 1所述的方法， 其特征在于， 在所述向所述用户设备 发送第二消息之后， 所述方法还包括：
所述用户设备向所述用户设备上的短消息协议栈或应用程序发送暂停 指示， 所述暂停指示用于指示暂停短消息的发送。
12、 根据权利要求 11所述的方法， 其特征在于， 所述方法还包括： 在 所述用户设备接收到移动管理设备发送的对第三消息进行响应的消息之后， 所述用户设备向所述用户设备上的短消息协议栈或应用程序发送重发指示， 所述重发指示用于指示重新开始短消息的发送。
13、 一种用于接收或发送短消息的装置， 其特征在于， 包括： 接收模块，用于接收移动交换中心 MSC/拜访位置寄存器 VLR发送的第 一消息；
第一确定模块， 用于根据所述第一消息确定用户设备处于异常状态； 发送模块， 用于向所述用户设备发送第二消息， 所述第二消息用于指示 所述用户设备发起到所述 MSC/VLR的附着。
14、 根据权利要求 13所述的装置， 其特征在于， 所述装置还包括： 第二确定模块， 用于在所述第一消息为第一寻呼消息时， 确定所述用户 设备处于空闲态，
所述发送模块还用于向所述用户设备发送第二寻呼消息， 所述第二寻呼 消息指示所述用户设备发起到所述 MSC/VLR的附着。
15、 根据权利要求 13所述的装置， 其特征在于， 所述装置还包括： 第三确定模块， 用于在所述第一消息为第一寻呼消息， 且所述发送模块 发送所述第二消息之前， 确定所述用户设备处于连接态。
16、 一种用于接收或发送短消息的装置， 其特征在于， 包括： 接收模块， 用于接收移动管理设备发送的第二消息， 所述第二消息用于 指示所述装置发起到移动交换中心 MSC/拜访位置寄存器 VLR的附着； 第一发送模块， 用于根据所述第二消息， 向所述移动管理设备发送第三 消息， 以发起到所述 MSC/VLR的附着。
17、 根据权利要求 16所述的装置， 其特征在于， 所述装置还包括： 第二发送模块， 用于在所述接收模块接收到所述第二消息之后， 向所述 移动管理设备发送对所述第二消息进行响应的第四消息。
18、 根据权利要求 16所述的装置， 其特征在于， 所述装置还包括： 第三发送模块， 用于向所述装置上的短消息协议栈或应用程序发送暂停 指示， 所述暂停指示用于指示暂停短消息的发送。
19、 根据权利要求 18所述的装置， 其特征在于， 所述装置还包括： 第四发送模块， 用于在接收到所述移动管理设备发送的对所述第三消息 进行响应的消息之后， 向所述装置上的短消息协议栈或应用程序发送重发指 示， 所述重发指示用于指示重新开始短消息的发送。
PCT/CN2011/073614 2011-05-03 2011-05-03 用于接收或发送短消息的方法和装置 WO2011120453A2 (zh)

Priority Applications (10)

Application Number Priority Date Filing Date Title
HUE11762027A HUE031002T2 (en) 2011-05-03 2011-05-03 A method and means for transmitting short messages from an improved packet switched system to a user equipment
ES11762027.8T ES2607958T3 (es) 2011-05-03 2011-05-03 Método y dispositivo para transmitir un mensaje corto desde un sistema de paquetes evolucionado a un equipo de usuario
EP11762027.8A EP2680625B1 (en) 2011-05-03 2011-05-03 Method and device for transmitting a short message from an evolved packet system to a user equipment
CN201180000846XA CN102217338B (zh) 2011-05-03 2011-05-03 用于接收或发送短消息的方法和装置
PCT/CN2011/073614 WO2011120453A2 (zh) 2011-05-03 2011-05-03 用于接收或发送短消息的方法和装置
EP16177794.1A EP3139675A1 (en) 2011-05-03 2011-05-03 Method and device for transmitting a short message from an evolved packet system to a user equipment
JP2014506720A JP5792890B2 (ja) 2011-05-03 2011-05-03 ショートメッセージを受信または送信するための方法および機器
US14/065,523 US9179275B2 (en) 2011-05-03 2013-10-29 Method and apparatus for receiving or sending short message
US14/861,799 US9420439B2 (en) 2011-05-03 2015-09-22 Method and apparatus for receiving or sending short message
US15/228,632 US9713114B2 (en) 2011-05-03 2016-08-04 Method and apparatus for receiving or sending short message

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/073614 WO2011120453A2 (zh) 2011-05-03 2011-05-03 用于接收或发送短消息的方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/065,523 Continuation US9179275B2 (en) 2011-05-03 2013-10-29 Method and apparatus for receiving or sending short message

Publications (2)

Publication Number Publication Date
WO2011120453A2 true WO2011120453A2 (zh) 2011-10-06
WO2011120453A3 WO2011120453A3 (zh) 2012-04-05

Family

ID=44712667

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/073614 WO2011120453A2 (zh) 2011-05-03 2011-05-03 用于接收或发送短消息的方法和装置

Country Status (7)

Country Link
US (3) US9179275B2 (zh)
EP (2) EP2680625B1 (zh)
JP (1) JP5792890B2 (zh)
CN (1) CN102217338B (zh)
ES (1) ES2607958T3 (zh)
HU (1) HUE031002T2 (zh)
WO (1) WO2011120453A2 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104247472A (zh) * 2012-12-21 2014-12-24 展讯通信（上海）有限公司 补充业务的实现方法、lte网络系统、移动终端

Families Citing this family (47)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011120453A2 (zh) 2011-05-03 2011-10-06 华为技术有限公司 用于接收或发送短消息的方法和装置
WO2013104101A1 (en) * 2012-01-09 2013-07-18 Telefonaktiebolaget L M Ericsson (Publ) Method for allowing a successful first mobile terminated call towards a mobile subscriber initially assigned to a failing core network node
CN103209402B (zh) * 2012-01-17 2018-03-23 中兴通讯股份有限公司 终端组可及性确定方法及系统
CN103716819A (zh) * 2012-09-29 2014-04-09 华为技术有限公司 拜访位置寄存器故障处理方法和移动管理网元
CN102984777A (zh) * 2012-12-06 2013-03-20 中兴通讯股份有限公司 电路域交换网络业务的处理方法、装置及mme
CN104488323B (zh) * 2013-07-01 2019-03-26 华为技术有限公司 一种呼叫处理的方法、设备和移动性管理实体
CN104521256B (zh) * 2013-07-22 2018-09-07 华为技术有限公司 位置更新处理方法及设备
GB2516837B (en) * 2013-07-31 2015-12-09 Ip Access Ltd Network elements, wireless communication system and methods therefor
CN104918292B (zh) * 2014-03-13 2019-04-26 中国移动通信集团江苏有限公司 一种业务控制方法和系统
EP3131361A4 (en) * 2014-04-30 2017-05-03 Huawei Technologies Co. Ltd. Mobility management entity and method for processing downlink circuit switched cs service
CN105744620B (zh) * 2014-12-09 2019-03-26 中国移动通信集团广东有限公司 一种电路域回落的寻呼方法及装置
US9967906B2 (en) 2015-01-07 2018-05-08 Cisco Technology, Inc. Wireless roaming using a distributed store
US9985837B2 (en) 2015-07-23 2018-05-29 Cisco Technology, Inc. Refresh of the binding tables between data-link-layer and network-layer addresses on mobility in a data center environment
JP6182800B2 (ja) * 2015-08-06 2017-08-23 ▲ホア▼▲ウェイ▼技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． ショートメッセージを受信または送信するための方法および機器
CN106714253B (zh) * 2015-11-12 2020-09-25 大唐移动通信设备有限公司 一种电路域回落csfb流程处理方法和装置
WO2017135676A1 (en) * 2016-02-02 2017-08-10 Lg Electronics Inc. Method and apparatus for paging with resume id for suspended user equipment in wireless communication system
WO2017180055A1 (en) * 2016-04-15 2017-10-19 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatus for paging an inactive ue in a wireless network
US10206093B2 (en) * 2016-05-24 2019-02-12 Telefonaktiebolaget L M Ericsson (Publ) Managing devices with SGs interface in VLR
US11696250B2 (en) * 2016-11-09 2023-07-04 Intel Corporation UE and devices for detach handling
US10440723B2 (en) 2017-05-17 2019-10-08 Cisco Technology, Inc. Hierarchical channel assignment in wireless networks
US10555341B2 (en) 2017-07-11 2020-02-04 Cisco Technology, Inc. Wireless contention reduction
US10440031B2 (en) 2017-07-21 2019-10-08 Cisco Technology, Inc. Wireless network steering
US10735981B2 (en) 2017-10-10 2020-08-04 Cisco Technology, Inc. System and method for providing a layer 2 fast re-switch for a wireless controller
US10375667B2 (en) 2017-12-07 2019-08-06 Cisco Technology, Inc. Enhancing indoor positioning using RF multilateration and optical sensing
US11012973B2 (en) * 2018-01-03 2021-05-18 Lg Electronics Inc. Method for receiving, by user equipment, paging signal in wireless communication system and device for performing the method
EP3788837B1 (en) * 2018-05-04 2023-08-23 Telefonaktiebolaget LM Ericsson (publ) Devices and methods for connection establishment in wireless network
US10505718B1 (en) 2018-06-08 2019-12-10 Cisco Technology, Inc. Systems, devices, and techniques for registering user equipment (UE) in wireless networks using a native blockchain platform
US10673618B2 (en) 2018-06-08 2020-06-02 Cisco Technology, Inc. Provisioning network resources in a wireless network using a native blockchain platform
US10873636B2 (en) 2018-07-09 2020-12-22 Cisco Technology, Inc. Session management in a forwarding plane
US10671462B2 (en) 2018-07-24 2020-06-02 Cisco Technology, Inc. System and method for message management across a network
US11252040B2 (en) 2018-07-31 2022-02-15 Cisco Technology, Inc. Advanced network tracing in the data plane
US10735209B2 (en) 2018-08-08 2020-08-04 Cisco Technology, Inc. Bitrate utilization feedback and control in 5G-NSA networks
US10623949B2 (en) 2018-08-08 2020-04-14 Cisco Technology, Inc. Network-initiated recovery from a text message delivery failure
US10284429B1 (en) 2018-08-08 2019-05-07 Cisco Technology, Inc. System and method for sharing subscriber resources in a network environment
US10949557B2 (en) 2018-08-20 2021-03-16 Cisco Technology, Inc. Blockchain-based auditing, instantiation and maintenance of 5G network slices
US10374749B1 (en) 2018-08-22 2019-08-06 Cisco Technology, Inc. Proactive interference avoidance for access points
US10567293B1 (en) 2018-08-23 2020-02-18 Cisco Technology, Inc. Mechanism to coordinate end to end quality of service between network nodes and service provider core
US10230605B1 (en) 2018-09-04 2019-03-12 Cisco Technology, Inc. Scalable distributed end-to-end performance delay measurement for segment routing policies
US10652152B2 (en) 2018-09-04 2020-05-12 Cisco Technology, Inc. Mobile core dynamic tunnel end-point processing
US10779188B2 (en) 2018-09-06 2020-09-15 Cisco Technology, Inc. Uplink bandwidth estimation over broadband cellular networks
US11558288B2 (en) 2018-09-21 2023-01-17 Cisco Technology, Inc. Scalable and programmable mechanism for targeted in-situ OAM implementation in segment routing networks
US10285155B1 (en) 2018-09-24 2019-05-07 Cisco Technology, Inc. Providing user equipment location information indication on user plane
US10601724B1 (en) 2018-11-01 2020-03-24 Cisco Technology, Inc. Scalable network slice based queuing using segment routing flexible algorithm
WO2021163949A1 (en) * 2020-02-20 2021-08-26 Telefonaktiebolaget Lm Ericsson (Publ) Methods, nodes and computer readable medium for solving dual vlr issue
CN111885517B (zh) * 2020-07-20 2021-11-09 中国联合网络通信集团有限公司 一种短信验证码防嗅探方法及装置
MX2023010240A (es) 2021-03-01 2023-11-24 Deciduous Therapeutics Inc Compuestos para activar células t asesinas naturales invariantes y métodos de uso en la eliminación de células senescentes inflamatorias.
CN113068136A (zh) * 2021-03-02 2021-07-02 Oppo广东移动通信有限公司 传输彩信的方法及装置、终端、可读存储介质

Family Cites Families (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3786538B2 (ja) 1999-02-19 2006-06-14 富士通株式会社 移動通信システム
KR100492959B1 (ko) 2002-09-11 2005-06-07 삼성전자주식회사 공중 이동통신망과 연동되는 사설 무선망의 단문 메시지서비스 서버 및 방법
EP1784035A1 (en) 2005-11-07 2007-05-09 Alcatel Lucent A method for connection re-establishment in a mobile communication system
CN100563358C (zh) 2006-05-31 2009-11-25 华为技术有限公司 一种应对移动交换节点故障的系统、设备及方法
EP2069949B1 (en) 2006-09-12 2012-08-22 Alcatel Lucent Delivery of mobile terminated call during inter-vlr location update
US8259673B2 (en) 2007-06-19 2012-09-04 Telefonaktiebolaget L M Ericsson (Publ) System and method for providing voice service in a mobile network with multiple wireless technologies
CN101351040B (zh) * 2007-07-19 2012-05-30 华为技术有限公司 语音呼叫建立方法以及移动管理实体、用户设备
EP2183231B1 (en) * 2007-07-24 2019-02-20 Mobileum, Inc. Testing of roaming transactions
JP4586056B2 (ja) * 2007-10-10 2010-11-24 ノキア コーポレイション 契約を変更する方法及びシステム
ES2692193T3 (es) * 2007-11-01 2018-11-30 Telefonaktiebolaget Lm Ericsson (Publ) Servicios de conmutación de circuito a través de redes SAE/LTE
EP2243309B1 (en) 2007-12-19 2011-08-03 Telefonaktiebolaget L M Ericsson (publ) Inter-domain coordination for mt and mo calls
CN101489288B (zh) * 2008-01-16 2011-04-20 华为技术有限公司 演进分组网络中电路域业务的处理方法、系统及相关设备
CN101499967B (zh) 2008-02-03 2011-07-13 中兴通讯股份有限公司 电路域寻呼实现方法及系统
CN101296518B (zh) 2008-06-16 2013-01-16 中兴通讯股份有限公司 电路域业务寻呼实现方法和装置
CN101577962B (zh) * 2008-07-10 2011-03-16 中兴通讯股份有限公司 一种关联关系更新的实现方法及相应终端
CN101577955B (zh) 2008-07-11 2011-04-20 中兴通讯股份有限公司 一种空闲模式下节约信令功能的激活判断方法及系统
CN101657025B (zh) * 2008-08-21 2013-08-14 华为技术有限公司 一种isr场景下电路交换域业务处理方法及装置
US8023944B2 (en) * 2008-09-29 2011-09-20 Via Telecom, Inc. Apparatus and method for performing attach procedure in mobile communication system
CN101742692B (zh) * 2008-11-07 2012-07-04 华为技术有限公司 寻呼处理、信息显示方法、装置
NZ592796A (en) * 2008-11-11 2013-12-20 Ericsson Telefon Ab L M Methods and apparatuses for user registration in the ims by msc server when using sgs / gs interface
CN101778348B (zh) * 2009-01-09 2012-03-21 华为技术有限公司 一种cs域业务的处理方法、设备及系统
GB2467348A (en) * 2009-01-30 2010-08-04 Nec Corp SMS transport resource control
US8547969B2 (en) * 2009-03-31 2013-10-01 Interdigital Patent Holdings, Inc. Method and apparatus for providing non-packet switched service in a target radio access technology network
WO2011012305A1 (en) * 2009-07-31 2011-02-03 Deutsche Telekom Ag Method and apparatuses for the transmission of a short message in an evolved packet system providing an interworking function
US8493904B2 (en) 2009-09-22 2013-07-23 Samsung Electronics Co., Ltd. Method and apparatus for supporting short messaging service of mobile station during idle mode in wireless communication system
KR101627165B1 (ko) * 2009-09-22 2016-06-14 삼성전자주식회사 무선통신 시스템에서 유휴 모드 단말의 단문 메시지 전송을 지원하기 위한 방법 및 장치
US20110105117A1 (en) 2009-10-29 2011-05-05 Chin Frances M Method And System Of Delivering An SMS Message
CN103281780B (zh) 2010-02-10 2016-04-06 电信科学技术研究院 空闲状态信令优化激活状态下寻呼消息的处理方法及设备
EP2699048B1 (en) * 2010-04-27 2015-01-21 Nec Corporation Accelerating restoration of communication services upon mobility management node restarting
US8948753B2 (en) * 2010-04-30 2015-02-03 Alcatel Lucent Method of providing notification of abnormal conditions during non-access stratum (NAS) message tunneling
WO2011120453A2 (zh) * 2011-05-03 2011-10-06 华为技术有限公司 用于接收或发送短消息的方法和装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
None
See also references of EP2680625A4

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104247472A (zh) * 2012-12-21 2014-12-24 展讯通信（上海）有限公司 补充业务的实现方法、lte网络系统、移动终端
US20150138974A1 (en) * 2012-12-21 2015-05-21 Spreadtrum Communications (Shanghai) Co., Ltd. Supplementary service implementation method, lte network system and mobile terminal
US9084158B2 (en) * 2012-12-21 2015-07-14 Spreadtrum Communications (Shanghai) Co., Ltd. Supplementary service implementation method, LTE network system and mobile terminal
CN104247472B (zh) * 2012-12-21 2018-06-05 展讯通信（上海）有限公司 补充业务的实现方法、lte网络系统、移动终端

Also Published As

Publication number Publication date
HUE031002T2 (en) 2017-06-28
ES2607958T3 (es) 2017-04-04
JP2014519219A (ja) 2014-08-07
EP2680625A2 (en) 2014-01-01
US20160345285A1 (en) 2016-11-24
WO2011120453A3 (zh) 2012-04-05
US9179275B2 (en) 2015-11-03
US9713114B2 (en) 2017-07-18
US9420439B2 (en) 2016-08-16
US20160014576A1 (en) 2016-01-14
JP5792890B2 (ja) 2015-10-14
EP2680625A4 (en) 2014-09-24
CN102217338B (zh) 2013-12-18
US20140051466A1 (en) 2014-02-20
CN102217338A (zh) 2011-10-12
EP3139675A1 (en) 2017-03-08
EP2680625B1 (en) 2016-09-28

Similar Documents

Publication Publication Date Title
WO2011120453A2 (zh) 用于接收或发送短消息的方法和装置
JP6317491B2 (ja) モバイル通信ネットワーク、インフラストラクチャ機器、モバイル通信端末、および方法。
JP6444356B2 (ja) 拡張アイドルモードｄｒｘなどの省電力化機構を使用するユーザ機器のためのモバイル着信ショートメッセージ配信のサポート
WO2011116722A2 (zh) Isr激活场景中移动管理设备故障的处理方法及设备
JP2014522164A (ja) 通信端末及び方法
JP2014522165A (ja) マシンタイプ通信（ｍｔｃ）装置の低減されたモビリティを管理し、ｍｔｃ装置にダウンリンクデータを送信するための移動体通信ネットワーク、インフラ設備及び方法
WO2012106896A1 (zh) 一种语音回落的方法及设备
CN107005792B (zh) 用于支持移动系统中移动终止应用服务的方法及相关实体
WO2013034091A1 (zh) 一种sms业务的处理方法及装置
WO2013113195A1 (zh) 短消息的发送方法及系统
WO2011063762A1 (zh) 保证业务连接的方法、网络设备和用户设备
WO2016029391A1 (zh) 一种接入网节点、核心网节点和寻呼方法
WO2012016546A1 (zh) 一种用户设备的寻呼处理方法及设备
WO2013064065A1 (zh) 应用数据处理方法及装置
US8868114B2 (en) Network entity for mobile communications
WO2010124644A1 (zh) 紧急业务实现方法、系统和网络设备
WO2013063785A1 (zh) 一种建立Gs关联的方法及装置
JP6182800B2 (ja) ショートメッセージを受信または送信するための方法および機器
WO2015085545A1 (zh) 一种ps业务恢复方法、msc/vlr及mme
WO2013065264A1 (ja) 通信装置及びオフライン移行方法
EP4211932A1 (en) Method and mme for handling mobility of a ue
WO2014048142A1 (zh) 拜访位置寄存器故障处理方法和移动管理网元
WO2011017853A1 (zh) 更新关联关系的方法以及分组域网元

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201180000846.X

Country of ref document: CN

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

Ref document number: 11762027

Country of ref document: EP

Kind code of ref document: A2

REEP Request for entry into the european phase

Ref document number: 2011762027

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2011762027

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2014506720

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE