WO2017125026A1 - 实现mtc事件监控的方法、装置和系统、存储介质 - Google Patents

实现mtc事件监控的方法、装置和系统、存储介质 Download PDF

Info

Publication number
WO2017125026A1
WO2017125026A1 PCT/CN2017/071611 CN2017071611W WO2017125026A1 WO 2017125026 A1 WO2017125026 A1 WO 2017125026A1 CN 2017071611 W CN2017071611 W CN 2017071611W WO 2017125026 A1 WO2017125026 A1 WO 2017125026A1
Authority
WO
WIPO (PCT)
Prior art keywords
isr
message
serving node
context
determining
Prior art date
Application number
PCT/CN2017/071611
Other languages
English (en)
French (fr)
Inventor
李志军
谢宝国
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2017125026A1 publication Critical patent/WO2017125026A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities

Definitions

  • the invention relates to a machine type communication (MTC) technology, in particular to a method, a device and a system for realizing monitoring of an MTC event, and a storage medium.
  • MTC machine type communication
  • FIG. 1 is a schematic diagram of the architecture of EPS supporting MTC communication.
  • the EPS mainly includes an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and an Evolved Packet Core (EPC).
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • EPC Evolved Packet Core
  • the EPC also supports users to access from the Universal Terrestrial Radio Access Network (UTRAN).
  • UTRAN Universal Terrestrial Radio Access Network
  • UTRAN Universal Terrestrial Radio Access Network
  • the E-UTRAN includes an enhanced NodeB (eNodeB) and a Radio Network Controller (RNC).
  • eNodeB enhanced NodeB
  • RNC Radio Network Controller
  • the EPC includes: Home Subscriber Server (HSS), Mobility Management Entity (MME), Serving Gateway (S-GW, Serving Gateway), Packet Data Network Gateway (P-GW, PDN). Gateway), General Packet Radio Service (GPRS) Supporting Node (SGSN), Policy and Charging Enforcement Function (PCRF), Service Capability Open Function/ Platform (SCEF, Service Capability Exposure Function). among them,
  • the HSS is a permanent storage location for user subscription data, and is located in the home network to which the user subscribes.
  • the MME is the user's subscription data in the current network storage location, responsible for terminal-to-network non-access stratum (NAS, Non-Access Stratum) signaling management, user idle mode tracking, paging management functions and bearer management.
  • NAS terminal-to-network non-access stratum
  • paging management functions and bearer management.
  • the S-GW is a gateway between the EPC and the wireless access system, and is responsible for the user plane bearer of the terminal to the EPC, the data buffer in the terminal idle mode, the function of initiating a service request by the network side, the lawful eavesdropping, and the packet data routing and forwarding function.
  • the P-GW is a gateway connecting the EPS and the external network, and is responsible for the Internet Protocol (IP) address allocation, charging function, packet filtering, and policy application of the terminal.
  • IP Internet Protocol
  • the SGSN is a service support point for the UTRAN user to access the EPC. It is similar in function to the MME and is responsible for user location update, paging management, and bearer management.
  • the PCRF is responsible for providing policy control and charging rules to the Policy and Charging Enforcement Function (PCEF).
  • PCEF Policy and Charging Enforcement Function
  • SCEF is responsible for providing various types of carrier services to third-party service providers, such as MTC terminal monitoring services.
  • MTC terminal monitoring service is a typical and widely used service.
  • MTC terminal monitoring service that is, performing the required MTC event detection and reporting for a specific UE.
  • MTC events can be classified into several categories, such as: International Mobile Subscriber Identification Number (IMSI), International Mobile Equipment Identity (IMEI), terminal-based changes, and terminal network status changes. , terminal communication failed, and so on.
  • IMSI International Mobile Subscriber Identification Number
  • IMEI International Mobile Equipment Identity
  • terminal-based changes terminal-based changes
  • terminal network status changes terminal communication failed, and so on.
  • the monitoring of certain MTC events may cause an increase in signaling load, which may affect the efficiency of the network, such as detecting changes in the location of the terminal.
  • the operator usually requires the third-party service to set the validity time (Maximum Number of Reports) when configuring the monitoring of the MTC event.
  • the effective time limits the return time of the MTC event monitoring.
  • the network automatically stops the MTC time monitoring.
  • the maximum number of reports defines the maximum number of MTC event reports reported by the network. When the maximum number of reports is reached, the network automatically stops monitoring MTC events.
  • the effective time set by MTC event monitoring may be long (for example, 1 month), during which the UE is not always attached to the network, and the UE may not always be on the same SGSN/MME, so when When the UE detaches from the network or switches the SGSN/MME, the network needs to synchronize the remaining report quantity between the SGSN/MME and the HSS. Otherwise, the SGSN/MME will default to the maximum number of reports in the configuration information monitored by the initial MTC event as the remaining report quantity, thereby reporting the out-of-range MTC event report and increasing the network load.
  • ISR Idle Signaling Reducing
  • the HSS sends MTC event configuration information to the MME (or SGSN); in the process of the UE switching from the MME to the SGSN (or from the SGSN to the MME), the MME and the SGSN activate the ISR, And the HSS sends MTC event configuration information to the SGSN (or MME).
  • the HSS since the HSS sends the MTC event configuration information to the MME (or the SGSN) before the handover, the HSS also sends the MTC event configuration information to the SGSN (or the MME), and the MTC event configuration is configured.
  • the maximum number of reports in the information is the same, which causes the SGSN and the MME to maintain the remaining number of reports of the same MTC event according to the maximum number of reports in the MTC event configuration information, and the subsequent UEs switch between E-UTRAN and UTRAN.
  • the MTC events reported by the SGSN and the MME are likely to exceed the maximum number of reports, which invalidates the maximum number of reports set in the MTC event configuration, wastes network signaling, and increases the network. Overhead.
  • the embodiment of the present invention provides a method, an apparatus, and a system for implementing MTC event monitoring, which can reduce network overhead.
  • the embodiment of the invention provides a method for implementing monitoring of an MTC event, including:
  • the first serving node receives a message from the HSS or the second serving node; wherein the message from the HSS includes a subscription data download request or a location update response, and the message from the second serving node includes a user equipment UE context acknowledgement message or a UE context response Message or UE context request message;
  • the first serving node determines, according to the received message, that the idle state signaling cannot be activated to optimize the ISR, does not activate the ISR, or performs ISR deactivation.
  • the method further includes:
  • the first serving node instructs the second serving node not to activate the ISR or perform ISR deactivation.
  • the first serving node determines, according to the received message, that the ISR cannot be activated, including:
  • the first serving node determines that the ISR has been activated by itself; and determines that the received subscription data download request from the HSS includes MTC event configuration information, or an ISR deactivation indication;
  • the first serving node determines that the ISR has been activated, and determines that the received subscription data download request from the HSS includes the MTC event configuration information, and the MTC event configuration information includes a maximum report.
  • the first serving node determines that the received UE context confirmation message from the second serving node does not include an ISR activation indication, or includes an ISR deactivation indication.
  • the first serving node determines, according to the received message, that the ISR cannot be activated, including:
  • the first serving node determines that the received UE from the second serving node is up and down The number of remaining reports including one or more MTC events in the message response message;
  • the indicating that the second serving node does not activate the ISR includes:
  • the first serving node sends a UE context confirmation message to the second serving node, where the UE context confirmation message does not include an ISR activation indication or includes an ISR deactivation indication.
  • the first serving node determines, according to the received message, that the ISR cannot be activated, including:
  • the indicating that the second serving node does not activate the ISR includes:
  • the first serving node sends a UE context response message to the second serving node, where the UE context response message does not include ISR capability information, and further includes a remaining report quantity of one or more MTC events.
  • the first serving node determines, according to the received message, that the ISR cannot be activated, including:
  • the instructing the second serving node to perform ISR deactivation includes:
  • the first serving node resends a UE context acknowledgement message to the second serving node; wherein the UE context acknowledgement message includes an ISR deactivation indication or does not include an ISR activation indication.
  • the first serving node is an MME
  • the second serving node is a serving general packet radio service technology SGSN;
  • the first serving node is an SGSN
  • the second serving node is an MME
  • the invention also proposes an apparatus for implementing monitoring of an MTC event, comprising:
  • a receiving module configured to receive a message from the HSS or the second serving node; wherein the message from the HSS includes a subscription data download request or a location update response, and the message from the second serving node includes a user equipment UE context confirmation message or a UE context a response message or a UE context request message;
  • the determining module is configured to: according to the received message, determine that the idle state signaling optimization ISR cannot be activated, and send a notification message to the processing module;
  • the processing module is configured to receive the notification message, not to activate the ISR or perform ISR deactivation.
  • processing module is further configured to:
  • the determining module is specifically configured to:
  • the determining module is specifically configured to:
  • the processing module is specifically configured as:
  • the UE context confirmation message does not include an ISR activation indication or includes an ISR deactivation indication.
  • the determining module is specifically configured to:
  • the processing module is specifically configured as:
  • Receiving the notification message sending a UE context response message to the second serving node, where the UE context response message does not include ISR capability information, and further includes a remaining report quantity of one or more MTC events.
  • the determining module is specifically configured to:
  • the processing module is specifically configured as:
  • the UE context acknowledgement message includes an ISR deactivation indication or does not include an ISR activation indication.
  • the embodiment of the invention also provides a system for implementing MTC event monitoring, including:
  • a first serving node configured to receive a message from the HSS or the second serving node; wherein the message from the HSS includes a subscription data download request or a location update response, and the message from the second serving node includes a user equipment UE context confirmation message or a UE context response message or a UE context request message; determining, according to the received message, that the idle state signaling optimization ISR cannot be activated, not activating the ISR or performing ISR deactivation, indicating that the second serving node does not activate the ISR or perform ISR deactivation;
  • a second serving node configured to not activate the ISR or perform an ISR under the direction of the first serving node go activate.
  • the first service node is specifically configured to:
  • the received UE context confirmation message from the second serving node does not include an ISR activation indication, or includes an ISR deactivation indication.
  • the first service node is specifically configured to:
  • the second service node is specifically configured as:
  • the second service node is further configured to:
  • the first service node is specifically configured to:
  • the second service node is specifically configured as:
  • Receiving a UE context confirmation message from the device determining that the UE context confirmation message does not include an ISR activation indication, and not activating the ISR; or determining that the UE context confirmation message includes an ISR deactivation indication, performing an ISR activation.
  • the technical solution of the present invention includes: the first serving node receives a message from the HSS or the second serving node; wherein the message from the HSS includes a subscription data download request or a location update response, and the second service node
  • the message includes a user equipment UE context confirmation message or a UE context response message or a UE context request message; the first serving node determines, according to the received message, that the ISR cannot be activated, does not activate the ISR, or performs ISR deactivation, and/or indicates The second service node does not activate the ISR or performs ISR deactivation.
  • the ISR when the first serving node determines that the ISR cannot be activated according to the received message, the ISR is not activated or the ISR is deactivated, so that the subsequent UE avoids the SGSN during the handover between the E-UTRAN and the UTRAN.
  • the number of remaining reports on the MME is out of synchronization.
  • the MTC events that are reported by the SGSN and the MME are limited to the maximum number of reports, thereby saving network signaling and reducing network overhead.
  • FIG. 1 is a schematic structural diagram of a related art EPS supporting MTC communication
  • FIG. 2 is a flowchart of a method for implementing MTC event monitoring when an ISR is not activated in the related art
  • FIG. 3 is a flowchart of a method for implementing MTC event monitoring when a related art activates an ISR
  • FIG. 4 is a flowchart of a method for implementing monitoring of an MTC event according to an embodiment of the present invention
  • FIG. 5 is a flowchart of a method for implementing monitoring of an MTC event according to a first embodiment of the present invention
  • FIG. 6 is a flowchart of a method for implementing MTC event monitoring according to a second embodiment of the present invention.
  • FIG. 7 is a flowchart of a method for implementing MTC event monitoring according to a third embodiment of the present invention.
  • FIG. 8 is a flowchart of a method for implementing MTC event monitoring according to a fourth embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of an apparatus for implementing MTC event monitoring according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a system for implementing MTC event monitoring according to an embodiment of the present invention.
  • FIG. 2 is a flow chart of a method for implementing MTC event monitoring when an ISR is not activated in the related art. As shown in Figure 2, the method includes:
  • Step 200 The UE is attached to the network.
  • Step 201 When the MTC event monitoring needs to be performed on the UE, the SCEF sends a terminal monitoring request to the HSS.
  • the SCEF generally sends a terminal monitoring request to the HSS upon receiving a management request from a third-party application server (AS).
  • AS third-party application server
  • the terminal monitoring request includes one or more MTC event configuration information.
  • Each MTC event configuration information includes at least: an SCEF identifier, a SCEF reference ID, and an MTC event type.
  • the SCEF identifier is used to identify different SCEFs
  • the SCEF reference ID is used to identify the next specific MTC event configuration information of the SCEF.
  • the MTC event configuration information may also contain restriction information for MTC event monitoring, such as: effective time and/or maximum number of reports.
  • Step 202 The HSS stores the MTC event configuration information in the subscription data of the UE, and sends a subscription data download request to the SGSN/MME.
  • the HSS needs to send the subscription data download request to the SGSN and the MME at the same time.
  • the subscription data download request includes the MTC event configuration information.
  • Step 203 The SGSN/MME saves the MTC event configuration information in the subscription data download request, and starts the MTC event monitoring according to the MTC event configuration information.
  • the SGSN/MME when the SGSN/MME saves the MTC event configuration information, if the MTC event configuration information includes the maximum number of reports, the SGSN/MME monitors the counter variable of the MTC event corresponding to the MTC event configuration information: the remaining report quantity. Initially, the remaining report quantity is set to the maximum number of reports in the MTC event configuration information, and each time an MTC event is detected and reported, the remaining report quantity is automatically decremented.
  • step 204 when the SGSN/MME detects that the MTC event occurs, a corresponding MTC event report is generated, and the MTC event report is included in the subscription data download response of step 204.
  • Step 204 The SGSN/MME returns a subscription data download response to the HSS.
  • the subscription data download response may include an MTC event configuration result information and an MTC event report.
  • the MTC event configuration result information refers to whether the SGSN/MME successfully receives the MTC event configuration information.
  • the subscription data download response includes an MTC event report. For example, if an MTC event is detected, the subscription data download response includes an MTC event report corresponding to the MTC event monitoring.
  • Step 205 The HSS sends a terminal monitoring response to the SCEF.
  • the terminal monitoring response includes the MTC event configuration result information returned by the SGSN/MME. If the subscription data download response includes the MTC event report in step 204, the terminal end The end monitoring response also includes an MTC event report.
  • Step 206 Thereafter, the SGSN/MME detects the MTC event, and generates an MTC event report according to the MTC event.
  • Step 207 The SGSN/MME sends a monitoring report message to the SCEF, and reports the MTC event report.
  • the monitoring report message includes the generated MTC event report.
  • the number of remaining reports corresponding to the generated MTC event is subtracted by one.
  • Step 208 The UE is detached from the network.
  • Step 209 The SGSN/MME sends a notification message to the HSS.
  • the notification message includes the remaining report quantity corresponding to each MTC event.
  • Each of the MTC events may refer to all MTC events of the UE, and may also refer to each MTC event reported by the SGSN/MME for reporting the MTC event.
  • Step 210 The HSS updates the maximum number of reports in the corresponding MTC event configuration information according to the remaining report quantity in the notification message.
  • the maximum number of reports corresponding to the MTC event is updated according to the remaining report quantity corresponding to the MTC event.
  • FIG. 3 is a flow chart of a method for implementing MTC event monitoring when an ISR is activated in the related art. As shown in FIG. 3, the method includes:
  • Step 300 The SCEF sends a terminal monitoring request to the HSS.
  • the UE is not attached to the network when the SCEF sends a monitoring request to the HSS.
  • the terminal monitoring request includes one or more MTC event configuration information.
  • SCEF generally receives management from a third-party application server (AS).
  • AS application server
  • a terminal monitoring request is sent to the HSS.
  • Step 301 The HSS stores the MTC event configuration information in the terminal monitoring request in the subscription data of the UE, and returns a terminal monitoring response message to the SCEF.
  • the terminal monitoring response message includes MTC event configuration result information.
  • the MTC event configuration result information refers to whether the HSS accepts the MTC event configuration information.
  • Step 302 The UE sends an attach request to the MME.
  • Step 303 The MME sends a location update request (ULR, Update Location Request) to the HSS.
  • ULR Update Location Request
  • Step 304 The HSS sends a location update response to the MME.
  • the location update response includes the subscription data of the UE, and the subscription data of the UE includes the MTC event configuration information.
  • Step 305 The MME stores the MTC event configuration information in the location update response, and starts the MTC event monitoring according to the MTC event configuration information.
  • Step 306 The MME returns an attach response to the UE.
  • the attach response includes a Globally Unique Temporary Identity (GUTI) for EUTRAN access.
  • GUI Globally Unique Temporary Identity
  • a part of the information corresponds to the MME identity, and one MME can be uniquely identified.
  • the UE when the UE receives the attach response, the UE has successfully attached to the MME, and the ISR function is not activated.
  • Step 307 After the UE accesses the E-UTRAN, when the UE enters the IDLE state and enters the UTRAN coverage area, the UE sends an RAU request to the SGSN.
  • the RAU request includes a Temporary Identity used (Next), and a Packet Temporary Mobile Subscriber Identity (P-TMSI), and the P-TMSI is used for UTRAN access. Identifies the identity of the UE.
  • P-TMSI Packet Temporary Mobile Subscriber Identity
  • Step 308 The SGSN sends a UE context request message to the MME.
  • the SGSN obtains the MME identity according to the TIN in the RAU request and the generated P-TMSI, parses the MME address, and generates a UE context request message to the MME according to the parsed MME address.
  • Step 309 The MME returns a UE context response message to the SGSN.
  • the UE context response message includes ISR capability information (ie, information indicating whether the MME supports ISR).
  • Step 310 The SGSN returns a UE context confirmation message to the MME.
  • the UE context confirmation message includes information indicating that the ISR is activated.
  • the SGSN stores the MME identity
  • the MME stores the SGSN identity
  • Step 311 The SGSN sends a location update request to the HSS.
  • Step 312 The HSS sends a location update response to the SGSN.
  • the location update response includes subscription data of the UE, and the subscription data includes MTC event configuration information.
  • Step 313 The SGSN stores the MTC event configuration information in the location update response, and starts the MTC event monitoring according to the MTC event configuration information.
  • Step 314 The SGSN returns an RAU response to the UE.
  • the RAU response includes the P-TMSI allocated by the SGSN, and the ISR activation indication.
  • Step 315 The UE activates the ISR function.
  • Step 316 When the SGSN and the MME respectively detect the occurrence of the MTC event, respectively generate an MTC event report, and report the MTC event report to the SCEF respectively.
  • Step 317 The UE detaches from the SGSN and the MME.
  • Step 318 The SGSN and the MME respectively send a notification message to the HSS.
  • the notification message includes the remaining number of reports corresponding to each MTC event.
  • Step 319 The HSS updates the maximum number of reports corresponding to each MTC event in the MTC event configuration information according to the remaining report quantity corresponding to each MTC event.
  • step 300 and step 301 can occur after step 306 or step 315.
  • the present invention provides a method for implementing MTC event monitoring, including:
  • Step 400 The first serving node receives a message from the HSS or the second serving node.
  • the received message from the HSS may be a subscription data download request or a location update response.
  • the received message from the second serving node may be a UE context response message or a UE context acknowledgement message or a UE context request message.
  • Step 401 The first serving node determines, according to the received message, that the ISR cannot be activated, does not activate the ISR, or performs ISR deactivation.
  • the first serving node instructs the second serving node not to activate the ISR or perform ISR deactivation.
  • the first serving node determines, according to the received message, that the ISR cannot be activated, including:
  • the first serving node determines that the ISR is activated by itself; and determines that the received subscription data download request from the HSS includes the MTC event configuration information or the ISR deactivation indication;
  • the specific service node can determine whether the ISR has been activated by using the well-known technology of the present invention, and is not used to limit the scope of protection of the present invention, and details are not described herein again.
  • the first serving node determines that the ISR has been activated, and determines that the received subscription data download request from the HSS includes the MTC event configuration information, and the MTC event configuration information includes the maximum number of reports;
  • the first serving node determines that the received UE context confirmation message from the second serving node does not include an ISR activation indication, or includes an ISR deactivation indication.
  • the first serving node determines, according to the received message, that the ISR cannot be activated, including:
  • the first serving node determines that the received UE context response message from the second serving node includes the remaining report quantity of one or more MTC events, or determines that the UE context response message does not include the ISR capability information; accordingly,
  • Instructing the second serving node not to activate the ISR includes:
  • the first serving node sends a UE context acknowledgement message to the second serving node; wherein the UE context acknowledgement message does not include an ISR activation indication or includes an ISR deactivation indication.
  • the first serving node determines that the ISR cannot be activated, including:
  • Instructing the second serving node not to activate the ISR includes:
  • the first serving node sends a UE context response message to the second serving node; wherein the UE context response message does not include ISR capability information, and further includes a remaining report quantity of one or more MTC events.
  • the first serving node determines, according to the received message, that the ISR cannot be activated, including:
  • the first serving node determines that the ISR is activated by itself; and determines that the received location update response from the HSS includes the MTC event configuration information, or determines that the location update response includes the ISR deactivation indication; accordingly,
  • Instructing the second serving node to perform ISR deactivation includes:
  • the first serving node resends the UE context acknowledgement message to the second serving node; wherein the UE context acknowledgement message includes an ISR deactivation indication or does not include an ISR activation indication.
  • the first serving node is the MME
  • the second serving node is the SGSN, or the first serving node is the SGSN
  • the second serving node is the MME.
  • the ISR when the first serving node determines that the ISR cannot be activated according to the received message, the ISR is not activated or the ISR is deactivated, so that the subsequent UE avoids the SGSN during the handover between the E-UTRAN and the UTRAN.
  • the number of remaining reports on the MME is out of synchronization.
  • the MTC events that are reported by the SGSN and the MME are limited to the maximum number of reports, thereby saving network signaling and reducing network overhead.
  • the method includes:
  • Step 500 The UE is attached to the network, and after the ISR is activated, the UE is attached to the SGSN and the MME at the same time.
  • HSS this means that the UE is simultaneously registered to the SGSN and the MME, while the SGSN and MME are simultaneously registered to the HSS.
  • the UE is located in the E-UTRAN coverage, and initiates an attach request to the MME.
  • the MME sends a location update request to the HSS, and the UE attaches to the MME.
  • the UE After the UE enters the idle state (IDLE) and moves to the URAN coverage, the UE initiates a RAU procedure to the SGSN.
  • the SGSN activates the ISR in the process of acquiring the UE context from the MME, and the SGSN sends a location update request to the HSS, and the UE is also attached. On the SGSN.
  • Step 501 When the MTC event monitoring needs to be performed on the UE, the SCEF sends a terminal monitoring request to the HSS.
  • the terminal monitoring request includes one or more MTC event configuration information.
  • Step 502 The HSS sends a subscription data download request to the SGSN and the MME at the same time.
  • the subscription data download request includes MTC event configuration information.
  • the subscription data download request further includes an ISR deactivation indication.
  • Step 503 The SGSN and the MME respectively store the MTC event configuration information in the subscription data download request, and start the MTC event monitoring according to the MTC event configuration information.
  • Step 504 The SGSN and the MME respectively return a subscription data download response to the HSS.
  • the subscription data download response includes the MTC event configuration result information, and may also include an MTC event report corresponding to the MTC event monitoring.
  • Step 505 The HSS sends a terminal monitoring response to the SCEF.
  • the terminal monitoring response includes the MTC event configuration result information and the MTC event report returned by the SGSN/MME.
  • Step 506 The SGSN and the MME respectively determine that the ISR has been activated, and the subscription data download request includes an ISR deactivation indication, and respectively performs ISR deactivation.
  • Step 507 Assuming that the UE camps on the MME at this time, when the MME detects that the MTC event occurs, the MME generates an MTC event report according to the MTC event.
  • Step 508 The MME sends the generated MTC event report to the SCEF.
  • Step 509 The UE detaches from the MME.
  • step 510 the MME sends a notification message to the HSS.
  • the notification message includes the remaining report quantity corresponding to each MTC event.
  • Step 508 The HSS updates the maximum report quantity of the corresponding MTC event according to the remaining report quantity.
  • the SGSN starts an implicit logout timer, timing After the device expires, the UE is implicitly detached from the SGSN.
  • how to implicitly detach may be implemented by using a well-known technology of the present invention, and is not intended to limit the scope of the present invention, and details are not described herein again.
  • the SGSN may send a notification message to the HSS, carrying the remaining report quantity of each MTC calculated by the SGSN.
  • the HSS After the HSS receives the remaining report quantity reported by the SGSN, if the remaining report quantity is less than the maximum report quantity in the corresponding MTC time configuration information, the HSS uses the remaining report quantity to update the maximum report quantity in the corresponding MTC event configuration information.
  • the method includes:
  • Step 600 The UE is attached to the network, and after the ISR is activated, the UE is attached to the SGSN and the MME at the same time.
  • the UE is located in the E-UTRAN coverage, initiates an Attach request to the MME, and the MME sends an ULR to the HSS, and the UE attaches to the MME.
  • the UE moves to the URAN coverage after entering the idle state (IDLE)
  • the UE initiates a RAU procedure to the SGSN.
  • the SGSN activates the ISR during the interaction process of acquiring the UE context to the MME, and the SGSN sends the ULR to the HSS, and the UE is also attached to the SGSN.
  • Step 601 When the MTC event monitoring needs to be performed on the UE, the SCEF sends a terminal monitoring request to the HSS.
  • the terminal monitoring request includes one or more MTC event configuration information.
  • the subscription data download request includes MTC event configuration information.
  • Step 603 The SGSN and the MME respectively store the MTC event configuration information in the subscription data download request, and start the MTC event monitoring according to the MTC event configuration information.
  • Step 604 The SGSN and the MME respectively return a subscription data download response to the HSS.
  • the subscription data download response includes the MTC event configuration result information, and may also include an MTC event report corresponding to the MTC event monitoring.
  • Step 605 The HSS sends a terminal monitoring response to the SCEF.
  • the terminal monitoring response includes the MTC event configuration result information and the MTC event report returned by the SGSN/MME.
  • Step 606 The SGSN and the MME respectively determine that the ISR needs to be deactivated, and respectively deactivate the ISR.
  • the SGSN and the MME respectively determine that the ISR needs to be deactivated, including:
  • the SGSN and the MME respectively determine that the ISR has been activated, and the subscription data download request is included in the package. Including MTC event configuration information;
  • the SGSN and the MME respectively determine that the ISR is activated, and the subscription data download request includes the MTC event configuration information, and the MTC event configuration information includes the maximum number of reports.
  • Step 607 It is assumed that the UE camps on the MME at this time.
  • the MME detects that the MTC event occurs, the MME generates an MTC event report according to the MTC event.
  • Step 608 The MME sends the generated MTC event report to the SCEF.
  • Step 609 The UE detaches from the MME.
  • step 610 the MME sends a notification message to the HSS.
  • the notification message includes the remaining report quantity corresponding to each MTC event.
  • Step 611 The HSS updates the maximum number of reports corresponding to each MTC event in the MTC event configuration information according to the remaining report quantity corresponding to each MTC event.
  • the method includes:
  • Step 700 The SCEF sends a terminal monitoring request to the HSS.
  • the SCEF sends a terminal monitoring request to the HSS, the UE is not attached to the network.
  • the terminal monitoring request includes one or more MTC event configuration information.
  • the SCEF generally sends a terminal monitoring request to the HSS upon receiving a management request from a third-party application server (AS).
  • AS third-party application server
  • Step 701 The HSS stores the MTC event configuration information in the terminal monitoring request in the subscription data of the UE, and returns a terminal monitoring response to the SCEF.
  • Step 702 The UE sends an attach request to the MME.
  • Step 703 The MME sends a location update request to the HSS.
  • Step 704 The HSS sends a location update response to the MME.
  • the location update response includes the subscription data of the UE, and the subscription data of the UE includes the MTC event configuration information.
  • Step 705 The MME stores the MTC event configuration information in the location update response, and starts the MTC event monitoring according to the MTC event configuration information.
  • Step 706 The MME returns an attach response to the UE.
  • Step 707 When the UE receives the attach response, the UE is successfully attached to the MME, and the UE activates the ISR function.
  • Step 708 When the UE enters the IDLE state and enters the UTRAN coverage area, the UE sends an RAU request to the SGSN.
  • the RAU request includes a TIN, and a P-TMSI for UTRAN access generated according to the GUTI.
  • Step 709 The SGSN sends a UE context request message to the MME.
  • Step 710 The MME returns a UE context response message to the SGSN.
  • the UE context response message includes the remaining number of reports corresponding to each MTC event. Since the MME initiates MTC event monitoring in the foregoing steps, in order to synchronize the remaining report quantity between the MME and the SGSN, the MME needs to notify the SGSN of the remaining report quantity.
  • the UE context response message may include the ISR capability information, or may not include the ISR capability information.
  • the MME may not include the ISR capability information in the UE context response message, even if the current MME supports the ISR function.
  • Step 711 The SGSN returns a UE context confirmation message to the MME.
  • the SGSN determines that the UE context response message sent by the MME does not include the ISR capability information, or determines that the UE context response message sent by the MME includes the remaining report quantity of one or more MTC events, the SGSN is in the UE.
  • the ISR activation indication or the ISR deactivation indication is not included in the context confirmation message, and the SGSN does not activate the ISR capability.
  • Step 712 The SGSN sends a location update request to the HSS.
  • Step 713 The HSS sends a location update response to the SGSN.
  • the location update response includes the subscription data of the UE, and the subscription data of the UE includes the MTC event configuration information.
  • Step 714 The SGSN stores the MTC event configuration information in the location update response, and updates the maximum report of the corresponding MTC event configuration information in the location update response sent by the HSS according to the remaining report quantity of each MTC event in the UE context response message sent by the MME. Quantity, and start MTC event monitoring based on the updated MTC event configuration information.
  • Step 715 The SGSN returns an RAU response to the UE.
  • the RAU response includes the P-TMSI allocated by the SGSN, and does not include the ISR activation indication.
  • Step 716 The UE does not activate the ISR function.
  • Step 717 The SGSN and the MME respectively detect the occurrence of the MTC event, and respectively generate an MTC event report.
  • Step 718 The SGSN and the MME respectively report the MTC event report to the SCEF.
  • Step 719 The UE detaches from the SGSN or the MME.
  • Step 720 The SGSN or the MME sends the remaining report quantity corresponding to each MTC event to the HSS.
  • Step 721 The HSS updates the maximum number of reports corresponding to each MTC event in the MTC event configuration information according to the remaining report quantity corresponding to each MTC event.
  • the method includes:
  • Step 800 The SCEF sends a terminal monitoring request to the HSS.
  • the SCEF sends a terminal monitoring request to the HSS, the UE is not attached to the network.
  • the terminal monitoring request includes one or more MTC event configuration information.
  • SCEF generally receives management from a third-party application server (AS).
  • AS application server
  • a terminal monitoring request is sent to the HSS.
  • Step 801 The HSS stores the MTC event configuration information in the terminal monitoring request in the subscription data of the UE, and returns a terminal monitoring response to the SCEF.
  • Step 802 The UE sends an attach request to the MME.
  • Step 803 The MME sends a location update request to the HSS.
  • Step 804 The HSS sends a location update response to the MME.
  • the location update response includes the subscription data of the UE, and the subscription data of the UE includes the MTC event configuration information.
  • Step 805 The MME stores the MTC event configuration information in the location update response, and starts the MTC event monitoring according to the MTC event configuration information.
  • Step 806 The MME returns an attach response to the UE.
  • Step 807 When the UE receives the attach response, it indicates that the UE has successfully attached to the MME, and the UE does not activate the ISR.
  • Step 808 When the UE enters the IDLE state and enters the UTRAN coverage area, the UE sends an RAU request to the SGSN.
  • the RAU request includes a TIN, and a P-TMSI generated according to the GUTI, which is used for UTRAN access.
  • Step 809 The SGSN sends a UE context request message to the MME.
  • Step 810 The MME returns a UE context response message to the SGSN.
  • the UE context response message includes ISR capability information.
  • Step 811 The SGSN returns a UE context confirmation message to the MME.
  • the UE context confirmation message includes an ISR activation indication.
  • the SGSN stores the MME identity
  • the MME stores the SGSN identity
  • Step 812 The SGSN sends a location update request to the HSS.
  • Step 813 The HSS sends a location update response to the SGSN.
  • the location update response includes the subscription data of the UE, and the subscription data of the UE includes the MTC event configuration information.
  • the location update response may further include an ISR deactivation indication.
  • Step 814 The SGSN stores the MTC event configuration information in the location update response, and starts the MTC event monitoring according to the MTC event configuration information.
  • Step 815 The SGSN determines that the location update response includes the MTC event configuration information, or determines that the location update response includes the ISR deactivation indication, and retransmits the UE context acknowledgement message to the MME.
  • the UE context confirmation message includes an ISR deactivation indication or does not include an ISR activation indication. Regardless of whether the message carries the ISR deactivation indication or does not carry the ISR activation indication, it indicates that the SGSN and the MME should not activate the ISR. If the ISR has been activated, the ISR should be deactivated. If the ISR is not activated, the ISR is no longer activated.
  • the SGSN and the MME perform deactivation of the ISR, respectively.
  • Step 816 The SGSN returns an RAU response to the UE.
  • the RAU response includes the P-TMSI allocated by the SGSN, and does not include the ISR activation indication.
  • Step 817 The UE does not activate the ISR function.
  • Step 818 The SGSN and the MME respectively detect the occurrence of the MTC event, and respectively generate an MTC event report.
  • Step 819 The SGSN and the MME respectively report the MTC event report to the SCEF.
  • Step 820 The UE detaches from the SGSN or the MME.
  • Step 821 The SGSN or the MME sends the remaining reports corresponding to each MTC event to the HSS. the amount.
  • Step 822 The HSS updates the maximum number of reports in the corresponding MTC event configuration information according to the remaining report quantity.
  • the present invention further provides an apparatus for implementing monitoring of an MTC event, including at least:
  • the receiving module 900 is configured to receive a message from the HSS or the second serving node; wherein the message from the HSS includes a subscription data download request or a location update response, and the message from the second serving node includes a user equipment UE context acknowledgement message or UE a context response message or a UE context request message;
  • the determining module 901 is configured to: according to the received message, determine that the idle state signaling optimization ISR cannot be activated, and send a notification message to the processing module 902;
  • the processing module 902 is configured to receive the notification message, not to activate the ISR or perform ISR deactivation.
  • the processing module is further configured to: instruct the second serving node not to activate the ISR or perform the ISR deactivation.
  • the determining module 901 is specifically configured to:
  • the processing module 902 has activated the ISR, and determines that the received subscription data download request from the HSS includes the MTC event configuration information, and the MTC event configuration information includes the maximum number of reports;
  • a notification message is sent to the processing module 902.
  • the determining module 901 is specifically configured to:
  • the processing module 902 is specifically configured to:
  • Receiving the notification message sending a UE context confirmation message to the second serving node; wherein the UE context confirmation message does not include an ISR activation indication or includes an ISR deactivation indication.
  • the determining module 901 is specifically configured to:
  • the processing module 902 is specifically configured to:
  • Receiving the notification message sending a UE context response message to the second serving node; wherein the UE context response message does not include the ISR capability information, and further includes the remaining report quantity of one or more MTC events.
  • the determining module 901 is specifically configured to:
  • the processing module 902 is specifically configured to:
  • the UE context acknowledgement message includes an ISR deactivation indication or does not include an ISR activation indication.
  • modules may be implemented by a processor by executing (in a single thread or multiple threads) executable instructions in a storage medium, by a logic programmable gate array (FPGA), or by a complex programmable logic device (CPLD) implementation.
  • FPGA logic programmable gate array
  • CPLD complex programmable logic device
  • the present invention also provides a system for implementing MTC event monitoring, which at least includes:
  • a first serving node configured to receive a message from the HSS or the second serving node; wherein the message from the HSS includes a subscription data download request or a location update response, and the message from the second serving node includes a user equipment UE context confirmation message or UE context response message or UE The following request message; determining, according to the received message, that the idle state signaling optimization ISR cannot be activated, not activating the ISR or performing ISR deactivation, and/or indicating that the second serving node does not activate the ISR or performing ISR deactivation;
  • the second serving node is configured to not activate the ISR or perform the ISR deactivation under the direction of the first serving node.
  • the first service node is specifically configured as:
  • the received UE context confirmation message from the second serving node does not include an ISR activation indication, or includes an ISR deactivation indication.
  • the first service node is specifically configured as:
  • the second service node is specifically configured as:
  • the second service node is further configured to:
  • the first service node is specifically configured as:
  • the second service node is specifically configured as:
  • Receiving a UE context confirmation message from the device determining that the UE context confirmation message does not include an ISR activation indication, and not activating the ISR; or determining that the UE context confirmation message includes an ISR deactivation indication, performing an ISR activation.
  • the first serving node receives the message from the home user data server or the second serving node; the first serving node determines, according to the received message, that the ISR cannot be activated, does not activate the ISR, or performs ISR deactivation.
  • the first serving node determines that the ISR cannot be activated, the ISR is not activated or the ISR is deactivated, so that the subsequent UE does not have information between the E-UTRAN and the UTRAN during the handover between the E-UTRAN and the UTRAN.
  • Over-range reporting of MTC events caused by synchronization saves network signaling and reduces network overhead.

Abstract

本发明公开了一种实现机器类通信(MTC)事件监控的方法、装置和系统、存储介质，包括：第一服务节点接收到来自归属用户数据服务器HSS或第二服务节点的消息；其中，来自HSS的消息包括签约数据下载请求或位置更新响应，来自第二服务节点的消息包括用户设备UE上下文确认消息或UE上下文响应消息或UE上下文请求消息；第一服务节点根据接收到的消息判断出不能激活ISR，不激活ISR或进行ISR去激活。通过本发明的方案，在第一服务节点判断出不能激活ISR时，不激活ISR或进行ISR去激活，从而后续UE在E-UTRAN和UTRAN之间切换的过程中，避免出现因在E-UTRAN和UTRAN之间信息不同步而引起的超范围上报MTC事件，从而节省了网络信令，减小了网络开销。

Description

实现MTC事件监控的方法、装置和系统、存储介质 技术领域
本发明涉及机器类通信(MTC，Machine Type Communication)技术，尤指一种实现MTC事件监控的方法、装置和系统、存储介质。
背景技术
为了支持MTC通讯，提高第三代移动通信系统在通信领域的竞争力，第三代合作伙伴计划(3GPP，3rd Generation Partnership Project)标准工作组对演进分组域系统(EPS，Evolved Packet System)进行了增强，以满足MTC的通讯需求。图1为EPS支持MTC通讯的架构示意图。如图1所示，EPS主要包括演进的通用陆地无线接入网络(E-UTRAN，Evolved Universal Terrestrial Radio Access Network)和演进的分组核心网(EPC，Evolved Packet Core)。另外，EPC还支持用户从通用陆地无线接入网(UTRAN，Universal Terrestrial Radio Access Network)接入。
其中，E-UTRAN包括增强的NodeB(eNodeB)和无线网络控制器(RNC，Radio Network Controller)。
其中，EPC包括：归属用户数据服务器(HSS，Home Subscriber Server)、移动性管理单元(MME，Mobility Management Entity)、服务网关(S-GW，Serving Gateway)、分组数据网络网关(P-GW，PDN Gateway)、服务通用分组无线服务技术(GPRS，General Packet Radio Service)支持节点(SGSN，Serving GPRS Support Node)、策略与计费规则功能实体(PCRF，Policy and Charging Enforcement Function)、服务能力开放功能/平台(SCEF，Service Capability Exposure Function)。其中，
HSS为用户签约数据的永久存放地点，位于用户签约的归属网。
MME为用户签约数据在当前网络的存放地点，负责终端到网络的非接入层(NAS，Non-Access Stratum)的信令的管理，用户空闲模式下的跟踪、寻呼管理功能和承载管理。
S-GW是EPC到无线接入系统之间的网关，负责终端到EPC的用户面承载、终端空闲模式下的数据缓存、网络侧发起业务请求的功能、合法窃听和分组数据路由和转发功能。
P-GW是连接EPS和外部网络的网关，负责终端的互联网协议(IP，Internet Protocol)地址分配、计费功能、分组包过滤、策略应用等功能。
SGSN是UTRAN用户接入EPC的业务支持点，功能上与MME类似，负责用户的位置更新、寻呼管理和承载管理等功能。
PCRF负责向策略及计费执行功能(PCEF，Policy and Charging Enforcement Function)提供策略控制与计费规则。
SCEF负责向第三方服务商提供各类运营商服务，比如：MTC终端监控业务。
在MTC业务中，MTC终端监控业务是很典型并且应用广泛的一种业务。所谓MTC终端监控业务，即针对特定UE执行所要求的MTC事件探测和报告。MTC事件可分若干类，比如：终端国际移动用户识别码(IMSI，International Mobile Subscriber Identification Number)/移动设备国际身份码(IMEI，International Mobile Equipment Identity)配对情况、终端为主变化、终端网络状态变化、终端通讯失败等等。
其中，对某些MTC事件的监控，可能会造成信令负荷的增加，从而影响网络的效率，比如探测终端位置的变化。运营商为了保护网络，通常要求第三方服务在配置MTC事件的监控时设置有效时间(Validity Time)和最大报告数量(Maximum Number of Reports)。其中，有效时间限定了MTC事件监控的作用时间返回，超出该有效时间，网络自动停止MTC时间监控； 最大报告数量限定了网络最多上报的MTC事件报告的数量，达到该最大报告数量，网络自动停止MTC事件监控。
由于MTC事件监控所设置的有效时间可能很长(比如1个月)，而在其期间，UE并不总是附着在网络中，而且UE也不可能一直在同一个SGSN/MME上，所以当UE从网络去附着，或切换SGSN/MME时，网络需要在SGSN/MME和HSS之间同步剩余报告数量。否则，SGSN/MME将默认以初始MTC事件监控的配置信息中的最大报告数量作为剩余报告数量，从而会上报超出范围的MTC事件报告，增加网络负担。
由于UE可能在UTRAN、EUTRAN之间频繁切换，3GPP提出了空间态信令优化(ISR，Idle Signaling Reducing)的功能，用以降低UE处于空闲态时在UTRAN和EUTRAN之间切换时的路由区更新(RAU，Route Area Update)、跟踪区更新(TAU，Tracking Area Update)信令的数量。
相关技术的实现MTC事件监控的方法大致包括：
UE附着到MME(或SGSN)的过程中，HSS向MME(或SGSN)发送MTC事件配置信息；在UE从MME切换到SGSN(或从SGSN切换到MME)的过程中，MME和SGSN激活ISR，并且HSS向SGSN(或MME)发送MTC事件配置信息。
相关技术的实现MTC事件监控的方法中，由于在切换前，HSS向MME(或SGSN)发送MTC事件配置信息，切换后，HSS也向SGSN(或MME)发送MTC事件配置信息，并且MTC事件配置信息中的最大报告数量相同，导致SGSN和MME之间分别根据MTC事件配置信息中的最大报告数量维护同一个MTC事件的剩余报告数量，后续UE在E-UTRAN和UTRAN之间切换的过程中，由于SGSN、MME上剩余报告数量不同步，容易造成SGSN、MME累计上报的MTC事件超出最大报告数量，从而使得MTC事件配置中所设置的最大报告数量失效，浪费了网络信令，加大了网络开销。
发明内容
为了解决上述问题，本发明实施例提出了一种实现MTC事件监控的方法、装置和系统，能够减小网络开销。
本发明实施例的技术方案是这样实现的：
本发明实施例提出了一种实现MTC事件监控的方法，包括：
第一服务节点接收到来自HSS或第二服务节点的消息；其中，来自HSS的消息包括签约数据下载请求或位置更新响应，来自第二服务节点的消息包括用户设备UE上下文确认消息或UE上下文响应消息或UE上下文请求消息；
第一服务节点根据接收到的消息判断出不能激活空闲态信令优化ISR，不激活ISR或进行ISR去激活。
可选的，该方法还包括：
所述第一服务节点指示第二服务节点不激活ISR或进行ISR去激活。
可选的，所述第一服务节点根据接收到的消息判断出不能激活ISR包括：
所述第一服务节点判断出自身已激活ISR；并且，判断出接收到的来自HSS的签约数据下载请求中包括MTC事件配置信息，或ISR去激活指示；
或者，所述第一服务节点判断出自身已激活ISR，且判断出接收到的来自所述HSS的签约数据下载请求中包括所述MTC事件配置信息，且所述MTC事件配置信息中包括最大报告数量；
或者，所述第一服务节点判断出接收到的来自所述第二服务节点的UE上下文确认消息中不包括ISR激活指示，或包括ISR去激活指示。
可选的，所述第一服务节点根据接收到的消息判断出不能激活ISR包括：
所述第一服务节点判断出接收到的来自所述第二服务节点的UE上下 文响应消息中包括一个或一个以上MTC事件的剩余报告数量；
所述指示第二服务节点不激活ISR包括：
所述第一服务节点向所述第二服务节点发送UE上下文确认消息；其中，所述UE上下文确认消息中不包括ISR激活指示或包括ISR去激活指示。
可选的，所述第一服务节点根据接收到的消息判断出不能激活ISR包括：
所述第一服务节点接收到来自所述第二服务节点的UE上下文请求消息，且判断出自身已启动MTC事件监控；
所述指示第二服务节点不激活ISR包括：
所述第一服务节点向所述第二服务节点发送UE上下文响应消息；其中，所述UE上下文响应消息中不包括ISR能力信息，还包括一个或一个以上MTC事件的剩余报告数量。
可选的，所述第一服务节点根据接收到的消息判断出不能激活ISR包括：
所述第一服务节点判断出自身已激活ISR；并且，判断出接收到的来自HSS的位置更新响应中包括MTC事件配置信息，或判断出所述位置更新响应中包括ISR去激活指示；
所述指示第二服务节点进行ISR去激活包括：
所述第一服务节点重新向所述第二服务节点发送UE上下文确认消息；其中，所述UE上下文确认消息包括ISR去激活指示或不包括ISR激活指示。
可选的，所述第一服务节点为MME，所述第二服务节点为服务通用分组无线服务技术SGSN；
或者，所述第一服务节点为SGSN，所述第二服务节点为MME。
本发明还提出了一种实现MTC事件监控的装置，包括：
接收模块，配置为接收到来自HSS或第二服务节点的消息；其中，来自HSS的消息包括签约数据下载请求或位置更新响应，来自第二服务节点的消息包括用户设备UE上下文确认消息或UE上下文响应消息或UE上下文请求消息；
判断模块，配置为根据接收到的消息判断出不能激活空闲态信令优化ISR，向处理模块发送通知消息；
处理模块，配置为接收到通知消息，不激活ISR或进行ISR去激活。
可选的，所述处理模块还配置为：
指示第二服务节点不激活ISR或进行ISR去激活。
可选的，所述判断模块具体配置为：
判断出处理模块已激活ISR；并且，判断出接收到的来自HSS的签约数据下载请求中包括MTC事件配置信息，或ISR去激活指示；
或者，判断出处理模块已激活ISR，且判断出接收到的来自所述HSS的签约数据下载请求中包括所述MTC事件配置信息，且所述MTC事件配置信息中包括最大报告数量；
或者，判断出接收到的来自所述第二服务节点的UE上下文确认消息中不包括ISR激活指示，或包括ISR去激活指示；
向所述处理模块发送所述通知消息。
可选的，所述判断模块具体配置为：
判断出接收到的来自所述第二服务节点的UE上下文响应消息中包括一个或一个以上MTC事件的剩余报告数量，向所述处理模块发送所述通知消息；
所述处理模块具体配置为：
接收到所述通知消息，向所述第二服务节点发送UE上下文确认消息； 其中，所述UE上下文确认消息中不包括ISR激活指示或包括ISR去激活指示。
可选的，所述判断模块具体配置为：
接收到来自所述第二服务节点的UE上下文请求消息，且判断出处理模块已启动MTC事件监控，向所述处理模块发送所述通知消息；
所述处理模块具体配置为：
接收到所述通知消息，向所述第二服务节点发送UE上下文响应消息；其中，所述UE上下文响应消息中不包括ISR能力信息，还包括一个或一个以上MTC事件的剩余报告数量。
可选的，所述判断模块具体配置为：
判断出处理模块已激活ISR；并且，判断出接收到的来自HSS的位置更新响应中包括MTC事件配置信息，或判断出所述位置更新响应中包括ISR去激活指示，向所述处理模块发送所述通知消息；
所述处理模块具体配置为：
接收到所述通知消息，重新向所述第二服务节点发送UE上下文确认消息；其中，所述UE上下文确认消息包括ISR去激活指示或不包括ISR激活指示。
本发明实施例还提出了一种实现MTC事件监控的系统，包括：
第一服务节点，配置为接收到来自HSS或第二服务节点的消息；其中，来自HSS的消息包括签约数据下载请求或位置更新响应，来自第二服务节点的消息包括用户设备UE上下文确认消息或UE上下文响应消息或UE上下文请求消息；根据接收到的消息判断出不能激活空闲态信令优化ISR，不激活ISR或进行ISR去激活，指示第二服务节点不激活ISR或进行ISR去激活；
第二服务节点，配置为在第一服务节点的指示下不激活ISR或进行ISR 去激活。
可选的，所述第一服务节点具体配置为：
接收到来自所述HSS的签约数据下载请求；
判断出自身已激活ISR；并且，判断出接收到的来自HSS的签约数据下载请求中包括MTC事件配置信息，或ISR去激活指示；
或者，判断出自身已激活ISR，且判断出接收到的来自所述HSS的签约数据下载请求中包括所述MTC事件配置信息，且所述MTC事件配置信息中包括最大报告数量；
或者，判断出接收到的来自所述第二服务节点的UE上下文确认消息中不包括ISR激活指示，或包括ISR去激活指示。
可选的，所述第一服务节点具体配置为：
判断出接收到的来自所述第二服务节点的UE上下文响应消息中包括一个或一个以上MTC事件的剩余报告数量；向所述第二服务节点发送UE上下文确认消息；其中，所述UE上下文确认消息中不包括ISR激活指示或包括ISR去激活指示；
所述第二服务节点具体配置为：
接收到来自所述装置的UE上下文响应消息，判断出所述UE上下文响应消息中不包括ISR能力信息，或判断出所述UE上下文响应消息中包括一个或一个以上MTC事件的剩余报告数量，不激活ISR。
可选的，所述第二服务节点还配置为：
接收到来自所述HSS的位置更新响应，根据所述一个或一个以上MTC事件的剩余报告数量更新所述位置更新响应中对应的MTC事件配置信息的最大报告数量。
可选的，所述第一服务节点具体配置为：
接收到来自所述第二服务节点的UE上下文请求消息，且判断出自身已 启动MTC事件监控；重新向所述第二服务节点发送UE上下文确认消息；其中，所述UE上下文确认消息包括ISR去激活指示或不包括ISR激活指示；
所述第二服务节点具体配置为：
接收到来自所述装置的UE上下文确认消息，判断出所述UE上下文确认消息中不包括ISR激活指示，不激活ISR；或判断出所述UE上下文确认消息中包括ISR去激活指示，进行ISR去激活。
本发明实施例还提供了一种实现MTC事件监控的方法
与相关技术相比，本发明的技术方案包括：第一服务节点接收到来自HSS或第二服务节点的消息；其中，来自HSS的消息包括签约数据下载请求或位置更新响应，来自第二服务节点的消息包括用户设备UE上下文确认消息或UE上下文响应消息或UE上下文请求消息；第一服务节点根据接收到的消息判断出不能激活ISR，不激活ISR或进行ISR去激活，和/或，指示第二服务节点不激活ISR或进行ISR去激活。
通过本发明的方案，在第一服务节点根据接收到的消息判断出不能激活ISR时，不激活ISR或进行ISR去激活，从而后续UE在E-UTRAN和UTRAN之间切换的过程中，避免SGSN、MME上剩余报告数量不同步情况的发生，控制SGSN、MME累计上报的MTC事件在最大报告数量的限定内，从而节省了网络信令，减小了网络开销。
附图说明
下面对本发明实施例中的附图进行说明，实施例中的附图是配置为对本发明的进一步理解，与说明书一起配置为解释本发明，并不构成对本发明保护范围的限制。
图1为相关技术EPS支持MTC通讯的结构示意图；
图2为相关技术未激活ISR时实现MTC事件监控的方法的流程图；
图3为相关技术激活ISR时实现MTC事件监控的方法的流程图；
图4为本发明实施例实现MTC事件监控的方法的流程图；
图5为本发明第一实施例实现MTC事件监控的方法的流程图；
图6为本发明第二实施例实现MTC事件监控的方法的流程图；
图7为本发明第三实施例实现MTC事件监控的方法的流程图；
图8为本发明第四实施例实现MTC事件监控的方法的流程图；
图9为本发明实施例实现MTC事件监控的装置的结构组成示意图；
图10为本发明实施例实现MTC事件监控的系统的结构组成示意图。
具体实施方式
为了便于本领域技术人员的理解，下面结合附图对本发明作进一步的描述，并不能用来限制本发明的保护范围。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的各种方式可以相互组合。
图2为相关技术的未激活ISR时实现MTC事件监控的方法的流程图。如图2所示，该方法包括：
步骤200、UE附着到网络。
步骤201、当需要对UE进行MTC事件监控时，SCEF向HSS发送终端监控请求。
本步骤中，SCEF一般在收到来自第三方应用服务器(AS)的管理请求时，向HSS发送终端监控请求。
本步骤中，终端监控请求包括一个或多个MTC事件配置信息。
其中，每个MTC事件配置信息至少包括：SCEF标识、SCEF参考ID、MTC事件类型。其中，SCEF标识用以识别不同的SCEF，SCEF参考ID用以标识该SCEF下一条具体的MTC事件配置信息。
MTC事件配置信息还可能包含针对MTC事件监控的限制信息，如：有效时间和/或最大报告数量等。
步骤202、HSS将MTC事件配置信息存储在UE的签约数据中，并向SGSN/MME发送签约数据下载请求。
本步骤中，如果UE同时附着到SGSN和MME上，则HSS需要同时向SGSN和MME发送签约数据下载请求。
本步骤中，签约数据下载请求中包括MTC事件配置信息。
步骤203、SGSN/MME保存签约数据下载请求中的MTC事件配置信息，并根据MTC事件配置信息启动MTC事件监控。
本步骤中，SGSN/MME保存MTC事件配置信息时，如果MTC事件配置信息中包括最大报告数量，则SGSN/MME对该MTC事件配置信息对应的MTC事件的监控启用计数器变量：剩余报告数量。在初始时将剩余报告数量设置为MTC事件配置信息中的最大报告数量，每次探测到MTC事件并上报后，将剩余报告数量自动递减。
本步骤中，当SGSN/MME检测到MTC事件发生时，生成对应的MTC事件报告，将MTC事件报告包含在步骤204的签约数据下载响应中。
步骤204、SGSN/MME向HSS返回签约数据下载响应。
本步骤中，签约数据下载响应中可能包括MTC事件配置结果信息、MTC事件报告。
其中，MTC事件配置结果信息是指SGSN/MME是否成功接收MTC事件配置信息。
其中，如果SGSN/MME检测到MTC事件，则签约数据下载响应中包括MTC事件报告。例如，检测到MTC事件，则签约数据下载响应中包括MTC事件监控对应的MTC事件报告。
步骤205、HSS向SCEF发送终端监控响应。
本步骤中，终端监控响应中包括SGSN/MME所返回的MTC事件配置结果信息，如果步骤204中，签约数据下载响应包括MTC事件报告，则终 端监控响应还包括MTC事件报告。
步骤206、此后SGSN/MME检测到MTC事件，根据MTC事件生成MTC事件报告。
步骤207、SGSN/MME向SCEF发送监控报告消息，上报MTC事件报告。
本步骤中，监控报告消息包括生成的MTC事件报告。
本步骤中，SGSN/MME发送监控报告请求后，将发生的MTC事件对应的剩余报告数量减去一。
步骤208、UE从网络去附着。
步骤209、SGSN/MME向HSS发送通知消息。
本步骤中，通知消息中包括各MTC事件对应的剩余报告数量。
其中，各MTC事件可以是指UE的所有MTC事件，也可以是指SGSN/MME上报过MTC事件报告的各MTC事件。
步骤210、HSS根据通知消息中的剩余报告数量更新对应的MTC事件配置信息中的最大报告数量。
本步骤中，如果MTC事件对应的剩余报告数量小于MTC事件配置信息中该MTC事件对应的最大报告数量时，则根据该MTC事件对应的剩余报告数量更新该MTC事件对应的最大报告数量。
图3是相关技术的激活ISR时实现MTC事件监控的方法的流程图。如图3所示，该方法包括：
步骤300、SCEF向HSS发送终端监控请求。
本步骤中，假设SCEF向HSS发送的中的监控请求时，UE并未附着到网络中。
本步骤中，终端监控请求包括一个或多个MTC事件配置信息。
本步骤中，SCEF一般在收到来自第三方应用服务器(AS)的管理请 求时，向HSS发送终端监控请求。
步骤301、HSS将终端监控请求中的MTC事件配置信息存储在UE的签约数据中，并向SCEF返回终端监控响应消息。
本步骤中，终端监控响应消息包括MTC事件配置结果信息。
其中，MTC事件配置结果信息指HSS是否接受MTC事件配置信息。
步骤302、UE向MME发送附着请求。
步骤303、MME向HSS发送位置更新请求(ULR，Update Location Request)。
步骤304、HSS向MME发送位置更新响应。
本步骤中，位置更新响应包括UE的签约数据，UE的签约数据包括MTC事件配置信息。
步骤305、MME存储位置更新响应中的MTC事件配置信息，并根据MTC事件配置信息启动MTC事件监控。
步骤306、MME向UE返回附着响应。
本步骤中，附着响应包括用于EUTRAN接入的全局唯一临时标识(GUTI，Globally Unique Temporary Identity)。在GUTI中，有一部分信息对应着MME标识，可以唯一地标识出一个MME。
本步骤中，UE接收到附着响应时，说明UE已成功附着到MME上，此时ISR功能未激活。
步骤307、UE接入到E-UTRAN后，当UE进入IDLE态，且进入UTRAN覆盖区时，UE向SGSN发送RAU请求。
本步骤中，RAU请求包括临时标识指示(TIN，Temporary Identity used in Next update)，和根据GUTI生成的分组临时标识(P-TMSI，Packet Temporary Mobile Subscriber Identity)，P-TMSI用于UTRAN接入时标识UE的身份。
步骤308、SGSN向MME发送UE上下文请求消息。
本步骤中，SGSN根据RAU请求中的TIN和生成的P-TMSI获取MME标识，解析MME地址，根据解析得到的MME地址向MME发生UE上下文请求消息。
步骤309、MME向SGSN返回UE上下文响应消息。
本步骤中，UE上下文响应消息包括ISR能力信息(即表示MME是否支持ISR的信息)。
步骤310、SGSN向MME返回UE上下文确认消息。
本步骤中，当UE上下文响应消息中的ISR能力信息指示MME支持ISR，且SGSN自身支持ISR时，UE上下文确认消息中包括指示ISR激活的信息。
其后，SGSN存储MME标识，MME存储SGSN标识，并各自激活ISR。
步骤311、SGSN向HSS发送位置更新请求。
步骤312、HSS向SGSN发送位置更新响应。
本步骤中，位置更新响应包括UE的签约数据，签约数据包括MTC事件配置信息。
步骤313、SGSN存储位置更新响应中的MTC事件配置信息，并根据MTC事件配置信息启动MTC事件监控。
步骤314、SGSN向UE返回RAU响应。
本步骤中，RAU响应包括SGSN分配的P-TMSI，ISR激活指示。
步骤315、UE激活ISR功能。
步骤316、当SGSN、MME分别探测到MTC事件的发生时，分别生成MTC事件报告，并分别向SCEF上报MTC事件报告。
步骤317、UE从SGSN、MME去附着。
步骤318、SGSN、MME分别向HSS发送通知消息。
本步骤中，通知消息包括各MTC事件对应的剩余报告数量。
步骤319、HSS根据各MTC事件对应的剩余报告数量更新MTC事件配置信息中各MTC事件对应的最大报告数量。
其中，步骤300和步骤301可以发生在步骤306或步骤315之后。
参见图4，本发明提出了一种实现MTC事件监控的方法，包括：
步骤400、第一服务节点接收到来自HSS或第二服务节点的消息。
本步骤中，接收到的来自HSS的消息可以是签约数据下载请求或位置更新响应。
本步骤中，接收到的来自第二服务节点的消息可以是UE上下文响应消息或UE上下文确认消息或UE上下文请求消息。
步骤401、第一服务节点根据接收到的消息判断出不能激活ISR，不激活ISR或进行ISR去激活。
进一步地，第一服务节点指示第二服务节点不激活ISR或进行ISR去激活。
本步骤中，第一服务节点根据接收到的消息判断出不能激活ISR包括：
第一服务节点判断出自身已激活ISR；并且，判断出接收到的来自HSS的签约数据下载请求中包括MTC事件配置信息，或ISR去激活指示；
其中，第一服务节点具体如何判断自身是否已激活ISR可以采用本领域技术人员的公知技术实现，并不用于限定本发明的保护范围，这里不再赘述。
或者，第一服务节点判断出自身已激活ISR，且判断出接收到的来自HSS的签约数据下载请求中包括MTC事件配置信息，且MTC事件配置信息中包括最大报告数量；
或者，第一服务节点判断出接收到的来自第二服务节点的UE上下文确认消息中不包括ISR激活指示，或包括ISR去激活指示。
或者，第一服务节点根据接收到的消息判断出不能激活ISR包括：
第一服务节点判断出接收到的来自第二服务节点的UE上下文响应消息中包括一个或一个以上MTC事件的剩余报告数量，或者判断出UE上下文响应消息中不包括ISR能力信息；相应地，
指示第二服务节点不激活ISR包括：
第一服务节点向第二服务节点发送UE上下文确认消息；其中，UE上下文确认消息中不包括ISR激活指示或包括ISR去激活指示。
或者，第一服务节点判断出不能激活ISR包括：
第一服务节点接收到来自第二服务节点的UE上下文请求消息，且判断出自身已启动MTC事件监控；响应地，
指示第二服务节点不激活ISR包括：
第一服务节点向所述第二服务节点发送UE上下文响应消息；其中，UE上下文响应消息中不包括ISR能力信息，还包括一个或一个以上MTC事件的剩余报告数量。
其中，具体如何判断自身是否已启动MTC事件监控可以采用本领域技术人员的公知技术实现，并不用于限定本发明的保护范围，这里不再赘述。
或者，第一服务节点根据接收到的消息判断出不能激活ISR包括：
第一服务节点判断出自身已激活ISR；并且，判断出接收到的来自HSS的位置更新响应中包括MTC事件配置信息，或判断出位置更新响应中包括ISR去激活指示；相应地，
指示第二服务节点进行ISR去激活包括：
第一服务节点重新向第二服务节点发送UE上下文确认消息；其中，UE上下文确认消息包括ISR去激活指示或不包括ISR激活指示。
本步骤中，第一服务节点为MME，第二服务节点为SGSN；或者第一服务节点为SGSN，第二服务节点为MME。
通过本发明的方案，在第一服务节点根据接收到的消息判断出不能激活ISR时，不激活ISR或进行ISR去激活，从而后续UE在E-UTRAN和UTRAN之间切换的过程中，避免SGSN、MME上剩余报告数量不同步情况的发生，控制SGSN、MME累计上报的MTC事件在最大报告数量的限定内，从而节省了网络信令，减小了网络开销。
下面通过具体实施例详细说明本发明的方法。
第一实施例，参见图5，该方法包括：
步骤500、UE附着到网络，ISR激活后，UE同时附着到SGSN、MME上。对于HSS而言，这意味着该UE同时注册到SGSN和MME上，而SGSN、MME同时注册到HSS上。
例如，UE位于E-UTRAN覆盖，向MME发起附着(Attach)请求，MME向HSS发送位置更新请求，则UE附着到MME上。当UE进入空闲态(IDLE)后移动到URAN覆盖范围，UE向SGSN发起RAU过程，SGSN在向MME获取UE上下文的交互过程中，激活ISR，SGSN向HSS发送位置更新请求，则UE也附着到SGSN上。
步骤501、当需要对UE进行MTC事件监控时，SCEF向HSS发送终端监控请求。
本步骤中，终端监控请求包括一个或多个MTC事件配置信息。
步骤502、HSS同时向SGSN、MME发送签约数据下载请求。
本步骤中，签约数据下载请求包括MTC事件配置信息。
进一步地，当HSS判断出UE同时附着到SGSN、MME上，且MTC事件配置信息中设置有最大报告数量时，签约数据下载请求还包括ISR去激活指示。
步骤503、SGSN和MME分别存储签约数据下载请求中的MTC事件配置信息，并分别根据MTC事件配置信息启动MTC事件监控。
步骤504、SGSN和MME分别向HSS返回签约数据下载响应。
本步骤中，签约数据下载响应包括MTC事件配置结果信息，还可能包括MTC事件监控对应的MTC事件报告。
步骤505、HSS向SCEF发送终端监控响应。
本步骤中，终端监控响应中包括SGSN/MME所返回的MTC事件配置结果信息、MTC事件报告。
步骤506、SGSN和MME分别判断出自身已激活ISR，且签约数据下载请求中包括ISR去激活指示，分别进行ISR去激活。
步骤507、假设此时UE驻留在MME上，当MME检测到MTC事件发生时，MME根据MTC事件生成MTC事件报告。
步骤508、MME将生成的MTC事件报告发送给SCEF。
步骤509、UE从MME去附着。
步骤510，MME向HSS发送通知消息。
本步骤中，通知消息中包括各MTC事件对应的剩余报告数量。
步骤508、HSS根据剩余报告数量更新对应的MTC事件的最大报告数量。
在其后，由于ISR已去激活，而UE在去激活ISR后驻留在MME并从MME去附着，所以当UE长期不在SGSN上活动时，根据相关技术，SGSN启动隐式注销定时器，定时器超期后将UE从SGSN上隐式去附着，具体如何隐式去附着可以采用本领域技术人员的公知技术实现，并不用于限定本发明的保护范围，这里不再赘述。当SGSN隐式去附着UE后，SGSN可能会向HSS发送通知消息，携带SGSN所计算的各MTC的剩余报告数量。当HSS收到SGSN报告的剩余报告数量后，如果该剩余报告数量小于对应MTC时间配置信息中的最大报告数量，则HSS使用该剩余报告数量更新对应MTC事件配置信息中的最大报告数量。
第二实施例，参见图6，该方法包括：
步骤600、UE附着到网络，ISR激活后，UE同时附着到SGSN、MME上。
例如，UE位于E-UTRAN覆盖，向MME发起Attach请求，MME向HSS发送ULR，则UE附着到MME上。当UE进入空闲态(IDLE)后移动到URAN覆盖范围，UE向SGSN发起RAU过程，SGSN在向MME获取UE上下文的交互过程中，激活ISR，SGSN向HSS发送ULR，则UE也附着到SGSN上。
步骤601、当需要对UE进行MTC事件监控时，SCEF向HSS发送终端监控请求。
本步骤中，终端监控请求包括一个或多个MTC事件配置信息。
步骤602、HSS同时向SGSN、MME发送签约数据下载请求。
本步骤中，签约数据下载请求包括MTC事件配置信息。
步骤603、SGSN和MME分别存储签约数据下载请求中的MTC事件配置信息，并分别根据MTC事件配置信息启动MTC事件监控。
步骤604、SGSN和MME分别向HSS返回签约数据下载响应。
本步骤中，签约数据下载响应包括MTC事件配置结果信息，还可能包括MTC事件监控对应的MTC事件报告。
步骤605、HSS向SCEF发送终端监控响应。
本步骤中，终端监控响应中包括SGSN/MME所返回的MTC事件配置结果信息、MTC事件报告。
步骤606、SGSN和MME分别判断出需要去激活ISR，分别进行去激活ISR。
本步骤中，SGSN和MME分别判断出需要去激活ISR包括：
SGSN和MME分别判断出自身已激活ISR，且签约数据下载请求中包 括MTC事件配置信息；
或者，SGSN和MME分别判断出自身已激活ISR，且签约数据下载请求中包括MTC事件配置信息，且MTC事件配置信息中包括最大报告数量。
步骤607、假设此时UE驻留在MME上，当MME检测到MTC事件发生时，MME根据MTC事件生成MTC事件报告。
步骤608、MME将生成的MTC事件报告发送给SCEF。
步骤609、UE从MME去附着。
步骤610，MME向HSS发送通知消息。
本步骤中，通知消息中包括各MTC事件对应的剩余报告数量。
步骤611、HSS根据各MTC事件对应的剩余报告数量更新MTC事件配置信息中各MTC事件对应的最大报告数量。
第三实施例，参见图7，该方法包括：
步骤700、SCEF向HSS发送终端监控请求。
本步骤中，假设SCEF向HSS发送终端监控请求时，UE并未附着到网络中。
本步骤中，终端监控请求包括一个或多个MTC事件配置信息。
本步骤中，SCEF一般在收到来自第三方应用服务器(AS)的管理请求时，向HSS发送终端监控请求。
步骤701、HSS将终端监控请求中的MTC事件配置信息存储在UE的签约数据中，并向SCEF返回终端监控响应。
步骤702、UE向MME发送附着请求。
步骤703、MME向HSS发送位置更新请求。
步骤704、HSS向MME发送位置更新响应。
本步骤中，位置更新响应包括UE的签约数据，UE的签约数据中包括MTC事件配置信息。
步骤705、MME存储位置更新响应中的MTC事件配置信息，并根据MTC事件配置信息启动MTC事件监控。
步骤706、MME向UE返回附着响应。
步骤707、UE接收到附着响应时，说明UE已成功附着到MME上，此时UE为激活ISR功能。
步骤708、当UE进入IDLE态，且进入UTRAN覆盖区时，UE向SGSN发送RAU请求。
本步骤中，RAU请求包括TIN，和根据GUTI生成的用于UTRAN接入的P-TMSI。
步骤709、SGSN向MME发送UE上下文请求消息。
步骤710、MME向SGSN返回UE上下文响应消息。
本步骤中，UE上下文响应消息包括各MTC事件对应的剩余报告数量。由于在前述步骤中MME启动了MTC事件监控，为了在MME和SGSN间同步剩余报告数量，MME需要向SGSN通知剩余报告数量。
本步骤中，UE上下文响应消息中可以包括ISR能力信息，也可以不包括ISR能力信息。
本步骤中，当MME判断出在MME上启动了MTC事件监控，则MME在UE上下文响应消息中可以不包括ISR能力信息，即使当前MME支持ISR功能。
步骤711、SGSN向MME返回UE上下文确认消息。
本步骤中，当SGSN判断出MME发送的UE上下文响应消息中不包括ISR能力信息，或判断出MME发送的UE上下文响应消息中包括一个或一个以上MTC事件的剩余报告数量时，则SGSN在UE上下文确认消息中不包括ISR激活指示或包括ISR去激活指示，并且SGSN不激活ISR能力。
步骤712、SGSN向HSS发送位置更新请求。
步骤713、HSS向SGSN发送位置更新响应。
本步骤中，位置更新响应包括UE的签约数据，UE的签约数据包括MTC事件配置信息。
步骤714、SGSN存储位置更新响应中的MTC事件配置信息，并根据MME发送的UE上下文响应消息中的各MTC事件的剩余报告数量更新HSS发送的位置更新响应中对应的MTC事件配置信息的最大报告数量，并根据更新后的MTC事件配置信息启动MTC事件监控。
步骤715、SGSN向UE返回RAU响应。
本步骤中，RAU响应包括SGSN分配的P-TMSI，而不包括ISR激活指示。
步骤716、UE不激活ISR功能。
步骤717、SGSN、MME分别探测MTC事件的发生，分别生成MTC事件报告。
步骤718、SGSN和MME分别向SCEF上报MTC事件报告。
步骤719、UE从SGSN或MME去附着。
步骤720、SGSN或MME向HSS发送各MTC事件对应的剩余报告数量。
步骤721、HSS根据各MTC事件对应的剩余报告数量更新MTC事件配置信息中各MTC事件对应的最大报告数量。
第四实施例，参见图8，该方法包括：
步骤800、SCEF向HSS发送终端监控请求。
本步骤中，假设SCEF向HSS发送终端监控请求时，UE并未附着到网络中。
本步骤中，终端监控请求包括一个或多个MTC事件配置信息。
本步骤中，SCEF一般在收到来自第三方应用服务器(AS)的管理请 求时，向HSS发送终端监控请求。
步骤801、HSS将终端监控请求中的MTC事件配置信息存储在UE的签约数据中，并向SCEF返回终端监控响应。
步骤802、UE向MME发送附着请求。
步骤803、MME向HSS发送位置更新请求。
步骤804、HSS向MME发送位置更新响应。
本步骤中，位置更新响应包括UE的签约数据，UE的签约数据中包括MTC事件配置信息。
步骤805、MME存储位置更新响应中的MTC事件配置信息，并根据MTC事件配置信息启动MTC事件监控。
步骤806、MME向UE返回附着响应。
步骤807、UE接收到附着响应时，说明UE已成功附着到MME上，此时UE未激活ISR。
步骤808、当UE进入IDLE态，且进入UTRAN覆盖区时，UE向SGSN发送RAU请求。
本步骤中，RAU请求包括TIN，和根据GUTI生成的P-TMSI，该P-TMSI用于UTRAN接入。
步骤809、SGSN向MME发送UE上下文请求消息。
步骤810、MME向SGSN返回UE上下文响应消息。
本步骤中，UE上下文响应消息包括ISR能力信息。
步骤811、SGSN向MME返回UE上下文确认消息。
本步骤中，如果MME支持ISR功能，且SGSN也支持ISR功能，则UE上下文确认消息包括ISR激活指示。
其后，SGSN存储MME标识，MME存储SGSN标识，并分别激活ISR功能。
步骤812、SGSN向HSS发送位置更新请求。
步骤813、HSS向SGSN发送位置更新响应。
本步骤中，位置更新响应包括UE的签约数据，UE的签约数据包括MTC事件配置信息。
本步骤中，当HSS判断出UE同时附着到SGSN和MME上时，位置更新响应还可以包括ISR去激活指示。
步骤814、SGSN存储位置更新响应中的MTC事件配置信息，并根据MTC事件配置信息启动MTC事件监控。
步骤815、SGSN判断出位置更新响应中包括MTC事件配置信息，或判断出位置更新响应中包括ISR去激活指示，重新向MME发送UE上下文确认消息。
本步骤中，UE上下文确认消息包括ISR去激活指示或不包括ISR激活指示。无论所述消息中是携带ISR去激活指示、还是不携带ISR激活指示，均表明SGSN、MME不应激活ISR，若已激活ISR则应去激活ISR，若未激活ISR则不再激活ISR。
其后，SGSN和MME分别进行去激活ISR。
步骤816、SGSN向UE返回RAU响应。
本步骤中，RAU响应包括SGSN分配的P-TMSI，而不包括ISR激活指示。
步骤817、UE不激活ISR功能。
步骤818、SGSN、MME分别探测MTC事件的发生，分别生成MTC事件报告。
步骤819、SGSN和MME分别向SCEF上报MTC事件报告。
步骤820、UE从SGSN或MME去附着。
步骤821、SGSN或MME向HSS发送各MTC事件对应的剩余报告数 量。
步骤822、HSS根据剩余报告数量更新对应的MTC事件配置信息中的最大报告数量。
参见图9，本发明还提出了一种实现MTC事件监控的装置，至少包括：
接收模块900，配置为接收到来自HSS或第二服务节点的消息；其中，来自HSS的消息包括签约数据下载请求或位置更新响应，来自第二服务节点的消息包括用户设备UE上下文确认消息或UE上下文响应消息或UE上下文请求消息；
判断模块901，配置为根据接收到的消息判断出不能激活空闲态信令优化ISR，向处理模块902发送通知消息；
处理模块902，配置为接收到通知消息，不激活ISR或进行ISR去激活。
本发明的装置中，处理模块还配置为：指示第二服务节点不激活ISR或进行ISR去激活。
本发明的装置中，判断模块901具体配置为：
判断出处理模块902已激活ISR；并且，判断出接收到的来自HSS的签约数据下载请求中包括MTC事件配置信息，或ISR去激活指示；
或者，判断出处理模块902已激活ISR，且判断出接收到的来自HSS的签约数据下载请求中包括MTC事件配置信息，且MTC事件配置信息中包括最大报告数量；
或者，判断出接收到的来自第二服务节点的UE上下文确认消息中不包括ISR激活指示，或包括ISR去激活指示；
向处理模块902发送通知消息。
本发明的装置中，判断模块901具体配置为：
判断出接收到的来自第二服务节点的UE上下文响应消息中包括一个或一个以上MTC事件对应的剩余报告数量，向处理模块902发送通知消息；
处理模块902具体配置为：
接收到通知消息，向第二服务节点发送UE上下文确认消息；其中，UE上下文确认消息中不包括ISR激活指示或包括ISR去激活指示。
本发明的装置中，判断模块901具体配置为：
接收到来自第二服务节点的UE上下文请求消息，且判断出处理模块902已启动MTC事件监控，向处理模块902发送通知消息；
处理模块902具体配置为：
接收到通知消息向第二服务节点发送UE上下文响应消息；其中，UE上下文响应消息中不包括ISR能力信息，还包括一个或一个以上MTC事件的剩余报告数量。
本发明的装置中，判断模块901具体配置为：
判断出处理模块902已激活ISR；并且，判断出接收到的来自HSS的位置更新响应中包括MTC事件配置信息，或判断出位置更新响应中包括ISR去激活指示，向处理模块902发送通知消息；
处理模块902具体配置为：
接收到通知消息，重新向第二服务节点发送UE上下文确认消息；其中，UE上下文确认消息包括ISR去激活指示或不包括ISR激活指示。
实际用于中，上述模块均可由处理器通过执行(以单个线程或多个线程)存储介质中的可执行指令实现，通过逻辑可编程门阵列(FPGA)实现，或通过复杂可编程逻辑器件(CPLD)实现。
参见图10，本发明还提出了一种实现MTC事件监控的系统，至少包括：
第一服务节点，配置为接收到来自HSS或第二服务节点的消息；其中，来自HSS的消息包括签约数据下载请求或位置更新响应，来自第二服务节点的消息包括用户设备UE上下文确认消息或UE上下文响应消息或UE上 下文请求消息；根据接收到的消息判断出不能激活空闲态信令优化ISR，不激活ISR或进行ISR去激活，和/或，指示第二服务节点不激活ISR或进行ISR去激活；
第二服务节点，配置为在第一服务节点的指示下不激活ISR或进行ISR去激活。
本发明的系统中，所述第一服务节点具体配置为：
接收到来自所述HSS的签约数据下载请求；
判断出自身已激活ISR；并且，判断出接收到的来自HSS的签约数据下载请求中包括MTC事件配置信息，或ISR去激活指示；
或者，判断出自身已激活ISR，且判断出接收到的来自所述HSS的签约数据下载请求中包括所述MTC事件配置信息，且所述MTC事件配置信息中包括最大报告数量；
或者，判断出接收到的来自所述第二服务节点的UE上下文确认消息中不包括ISR激活指示，或包括ISR去激活指示。
本发明的系统中s，所述第一服务节点具体配置为：
判断出接收到的来自所述第二服务节点的UE上下文响应消息中包括一个或一个以上MTC事件的剩余报告数量；向所述第二服务节点发送UE上下文确认消息；其中，所述UE上下文确认消息中不包括ISR激活指示或包括ISR去激活指示；
所述第二服务节点具体配置为：
接收到来自所述装置的UE上下文响应消息，判断出所述UE上下文响应消息中不包括ISR能力信息，或判断出所述UE上下文响应消息中包括一个或一个以上MTC事件的剩余报告数量，不激活ISR。
本发明的系统中，所述第二服务节点还配置为：
接收到来自所述HSS的位置更新响应，根据所述一个或一个以上MTC 事件的剩余报告数量更新所述位置更新响应中对应的MTC事件配置信息的最大报告数量。
本发明的系统中，所述第一服务节点具体配置为：
接收到来自所述第二服务节点的UE上下文请求消息，且判断出自身已启动MTC事件监控；重新向所述第二服务节点发送UE上下文确认消息；其中，所述UE上下文确认消息包括ISR去激活指示或不包括ISR激活指示；
所述第二服务节点具体配置为：
接收到来自所述装置的UE上下文确认消息，判断出所述UE上下文确认消息中不包括ISR激活指示，不激活ISR；或判断出所述UE上下文确认消息中包括ISR去激活指示，进行ISR去激活。
需要说明的是，以上所述的实施例仅是为了便于本领域的技术人员理解而已，并不用于限制本发明的保护范围，在不脱离本发明的发明构思的前提下，本领域技术人员对本发明所做出的任何显而易见的替换和改进等均在本发明的保护范围之内。
工业实用性
本发明实施例中，第一服务节点接收到来自归属用户数据服务器或第二服务节点的消息；第一服务节点根据接收到的消息判断出不能激活ISR，不激活ISR或进行ISR去激活。在第一服务节点判断出不能激活ISR时，不激活ISR或进行ISR去激活，从而后续UE在E-UTRAN和UTRAN之间切换的过程中，避免出现因在E-UTRAN和UTRAN之间信息不同步而引起的超范围上报MTC事件，从而节省了网络信令，减小了网络开销。

Claims (19)

  1. 一种实现机器类通信MTC事件监控的方法，包括：
    第一服务节点接收到来自归属用户数据服务器HSS或第二服务节点的消息；其中，来自所述HSS的消息包括签约数据下载请求或位置更新响应，来自所述第二服务节点的消息包括用户设备UE上下文确认消息或UE上下文响应消息或UE上下文请求消息；
    所述第一服务节点根据接收到的消息判断出不能激活空闲态信令优化ISR，不激活ISR或进行ISR去激活。
  2. 根据权利要求1所述的方法，其中，还包括：
    所述第一服务节点指示第二服务节点不激活ISR或进行ISR去激活。
  3. 根据权利要求1或2所述的方法，其中，所述第一服务节点根据接收到的消息判断出不能激活ISR包括：
    所述第一服务节点判断出自身已激活ISR；并且，判断出接收到的来自所述HSS的签约数据下载请求中包括MTC事件配置信息，或ISR去激活指示；
    或者，所述第一服务节点判断出自身已激活ISR，且判断出接收到的来自所述HSS的签约数据下载请求中包括所述MTC事件配置信息，且所述MTC事件配置信息中包括最大报告数量；
    或者，所述第一服务节点判断出接收到的来自所述第二服务节点的UE上下文确认消息中不包括ISR激活指示，或包括ISR去激活指示。
  4. 根据权利要求2所述的方法，其中，所述第一服务节点根据接收到的消息判断出不能激活ISR包括：
    所述第一服务节点判断出接收到的来自所述第二服务节点的UE上下文响应消息中包括一个或一个以上MTC事件的剩余报告数量；
    所述指示第二服务节点不激活ISR包括：
    所述第一服务节点向所述第二服务节点发送UE上下文确认消息；其中，所述UE上下文确认消息中不包括ISR激活指示或包括ISR去激活指示。
  5. 根据权利要求2所述的方法，其中，所述第一服务节点根据接收到的消息判断出不能激活ISR包括：
    所述第一服务节点接收到来自所述第二服务节点的UE上下文请求消息，且判断出自身已启动MTC事件监控；
    所述指示第二服务节点不激活ISR包括：
    所述第一服务节点向所述第二服务节点发送UE上下文响应消息；其中，所述UE上下文响应消息中不包括ISR能力信息，还包括一个或一个以上MTC事件的剩余报告数量。
  6. 根据权利要求2所述的方法，其中，所述第一服务节点根据接收到的消息判断出不能激活ISR包括：
    所述第一服务节点判断出自身已激活ISR；并且，判断出接收到的来自HSS的位置更新响应中包括MTC事件配置信息，或判断出所述位置更新响应中包括ISR去激活指示；
    所述指示第二服务节点进行ISR去激活包括：
    所述第一服务节点重新向所述第二服务节点发送UE上下文确认消息；其中，所述UE上下文确认消息包括ISR去激活指示或不包括ISR激活指示。
  7. 根据权利要求1～6任意一项所述的方法，其中，所述第一服务节点为移动性管理单元MME，所述第二服务节点为服务通用分组无线服务技术支持节点SGSN；
    或者，所述第一服务节点为SGSN，所述第二服务节点为MME。
  8. 一种实现机器类通信MTC事件监控的装置，包括：
    接收模块，配置为接收到来自归属用户数据服务器HSS或第二服务节点的消息；其中，来自所述HSS的消息包括签约数据下载请求或位置更新响应，来自第二服务节点的消息包括用户设备UE上下文确认消息或UE上下文响应消息或UE上下文请求消息；
    判断模块，配置为根据接收到的消息判断出不能激活空闲态信令优化ISR，向处理模块发送通知消息；
    处理模块，配置为接收到通知消息，不激活ISR或进行ISR去激活。
  9. 根据权利要求8所述的装置，其中，所述处理模块还配置为：
    指示第二服务节点不激活ISR或进行ISR去激活。
  10. 根据权利要求8或9所述的装置，其中，所述判断模块具体配置为：
    判断出所述处理模块已激活ISR；并且，判断出接收到的来自所述HSS的签约数据下载请求中包括MTC事件配置信息，或ISR去激活指示；
    或者，判断出所述处理模块已激活ISR，且判断出接收到的来自所述HSS的签约数据下载请求中包括所述MTC事件配置信息，且所述MTC事件配置信息中包括最大报告数量；
    或者，判断出接收到的来自所述第二服务节点的UE上下文确认消息中不包括ISR激活指示，或包括ISR去激活指示；
    向所述处理模块发送所述通知消息。
  11. 根据权利要求8或9所述的装置，其中，所述判断模块具体配置为：
    判断出接收到的来自所述第二服务节点的UE上下文响应消息中包括一个或一个以上MTC事件的剩余报告数量，向所述处理模块发送所述通知消息；
    所述处理模块具体配置为：
    接收到所述通知消息，向所述第二服务节点发送UE上下文确认消息；其中，所述UE上下文确认消息中不包括ISR激活指示或包括ISR去激活指示。
  12. 根据权利要求9所述的装置，其中，所述判断模块具体配置为：
    接收到来自所述第二服务节点的UE上下文请求消息，且判断出所述判断模块已启动MTC事件监控，向所述处理模块发送所述通知消息；
    所述处理模块具体配置为：
    接收到所述通知消息，向所述第二服务节点发送UE上下文响应消息；其中，所述UE上下文响应消息中不包括ISR能力信息，还包括一个或一个以上MTC事件的剩余报告数量。
  13. 根据权利要求9所述的装置，其中，所述判断模块具体配置为：
    判断出所述判断模块已激活ISR；并且，判断出接收到的来自所述HSS的位置更新响应中包括MTC事件配置信息，或判断出所述位置更新响应中包括ISR去激活指示，向所述处理模块发送所述通知消息；
    所述处理模块具体配置为：
    接收到所述通知消息，重新向所述第二服务节点发送UE上下文确认消息；其中，所述UE上下文确认消息包括ISR去激活指示或不包括ISR激活指示。
  14. 一种实现机器类通信MTC事件监控的系统，包括：
    第一服务节点，配置为接收到来自归属用户数据服务器HSS或第二服务节点的消息；其中，来自所述HSS的消息包括签约数据下载请求或位置更新响应，来自第二服务节点的消息包括用户设备UE上下文确认消息或UE上下文响应消息或UE上下文请求消息；根据接收到的消息判断出不能激活空闲态信令优化ISR，不激活ISR或进行ISR去激活，指示第二服务节点不激活ISR或进行ISR去激活；
    第二服务节点，配置为在第一服务节点的指示下不激活ISR或进行ISR去激活。
  15. 根据权利要求14所述的系统，其中，所述第一服务节点具体配置为：
    接收到来自所述HSS的签约数据下载请求；
    判断出自身已激活ISR；并且，判断出接收到的来自归属用户数据服务器HSS的签约数据下载请求中包括MTC事件配置信息，或ISR去激活指示；
    或者，判断出自身已激活ISR，且判断出接收到的来自所述HSS的签约数据下载请求中包括所述MTC事件配置信息，且所述MTC事件配置信息中包括最大报告数量；
    或者，判断出接收到的来自所述第二服务节点的UE上下文确认消息中不包括ISR激活指示，或包括ISR去激活指示。
  16. 根据权利要求14所述的系统，其中，所述第一服务节点具体配置为：
    判断出接收到的来自所述第二服务节点的UE上下文响应消息中包括一个或一个以上MTC事件的剩余报告数量；向所述第二服务节点发送UE上下文确认消息；其中，所述UE上下文确认消息中不包括ISR激活指示或包括ISR去激活指示；
    所述第二服务节点具体配置为：
    接收到来自所述装置的UE上下文响应消息，判断出所述UE上下文响应消息中不包括ISR能力信息，或判断出所述UE上下文响应消息中包括一个或一个以上MTC事件的剩余报告数量，不激活ISR。
  17. 根据权利要求16所述的系统，其中，所述第二服务节点还配置为：
    接收到来自所述HSS的位置更新响应，根据所述一个或一个以上MTC 事件的剩余报告数量更新所述位置更新响应中对应的MTC事件配置信息的最大报告数量。
  18. 根据权利要求14所述的系统，其中，所述第一服务节点具体配置为：
    接收到来自所述第二服务节点的UE上下文请求消息，且判断出自身已启动MTC事件监控；重新向所述第二服务节点发送UE上下文确认消息；其中，所述UE上下文确认消息包括ISR去激活指示或不包括ISR激活指示；
    所述第二服务节点具体配置为：
    接收到来自所述装置的UE上下文确认消息，判断出所述UE上下文确认消息中不包括ISR激活指示，不激活ISR；或判断出所述UE上下文确认消息中包括ISR去激活指示，进行ISR去激活。
  19. 一种存储介质，存储有可执行指令，用于执行权利要求1至7任一项所述的实现机器类通信MTC事件监控的方法。
PCT/CN2017/071611 2016-01-19 2017-01-18 实现mtc事件监控的方法、装置和系统、存储介质 WO2017125026A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610035863.1 2016-01-19
CN201610035863.1A CN106982425A (zh) 2016-01-19 2016-01-19 一种实现mtc事件监控的方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2017125026A1 true WO2017125026A1 (zh) 2017-07-27

Family

ID=59340994

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/071611 WO2017125026A1 (zh) 2016-01-19 2017-01-18 实现mtc事件监控的方法、装置和系统、存储介质

Country Status (2)

Country Link
CN (1) CN106982425A (zh)
WO (1) WO2017125026A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110831056B (zh) * 2018-08-13 2021-11-19 华为技术有限公司 一种监控事件上报方法及装置
CN112690015B (zh) * 2018-09-14 2023-12-29 瑞典爱立信有限公司 用于事件监视的审核过程
CN113873588A (zh) * 2018-12-29 2021-12-31 华为技术有限公司 一种通信方法及装置
EP3918818A4 (en) * 2019-02-02 2022-10-26 Telefonaktiebolaget LM Ericsson (publ.) EU-TO-EU EVENT MONITORING PROCESSES AND NODES

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101572942A (zh) * 2008-04-30 2009-11-04 华为技术有限公司 一种隐分离方法、系统和装置
CN101577955A (zh) * 2008-07-11 2009-11-11 中兴通讯股份有限公司 一种空闲模式下节约信令功能的激活判断方法及系统
CN101640933A (zh) * 2008-07-31 2010-02-03 华为技术有限公司 寻呼用户设备的方法、网络设备、用户设备及网络系统
CN102333294A (zh) * 2011-09-23 2012-01-25 电信科学技术研究院 基于去附着流程更新终端可达状态信息的方法及装置
WO2015105301A1 (ko) * 2014-01-13 2015-07-16 엘지전자 주식회사 다운링크 데이터 전달 방법 및 위치 갱신 절차 수행 방법

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101572942A (zh) * 2008-04-30 2009-11-04 华为技术有限公司 一种隐分离方法、系统和装置
CN101577955A (zh) * 2008-07-11 2009-11-11 中兴通讯股份有限公司 一种空闲模式下节约信令功能的激活判断方法及系统
CN101640933A (zh) * 2008-07-31 2010-02-03 华为技术有限公司 寻呼用户设备的方法、网络设备、用户设备及网络系统
CN102333294A (zh) * 2011-09-23 2012-01-25 电信科学技术研究院 基于去附着流程更新终端可达状态信息的方法及装置
WO2015105301A1 (ko) * 2014-01-13 2015-07-16 엘지전자 주식회사 다운링크 데이터 전달 방법 및 위치 갱신 절차 수행 방법

Also Published As

Publication number Publication date
CN106982425A (zh) 2017-07-25

Similar Documents

Publication Publication Date Title
DK2702793T3 (en) Improvements to completed mobile calls
KR101339044B1 (ko) 서빙 코어 네트워크 노드가 변경될 때의 모바일 장치의 접근성의 처리
KR101489418B1 (ko) 혼잡/과부하 제어 방법 및 장치
US8515465B2 (en) Solution for paging differentiation in communication network
EP2583508B1 (en) P-gw/ggsn issued paging requests
US9143997B2 (en) Service restoration processing method and mobility management network element
KR20200033325A (ko) 무선 디바이스를 위한 서비스 갭 제어
US10827458B2 (en) Paging method, mobile management entity and terminal
US20220294791A1 (en) Methods and nodes for handling overload
EP2385720B1 (en) Overload control in a packet mobile communication system
US11558787B2 (en) Monitoring event management method and apparatus
WO2017125026A1 (zh) 实现mtc事件监控的方法、装置和系统、存储介质
US10327224B2 (en) Efficient handling of paging
US20180007614A1 (en) Mitigation of signalling congestion in cellular networks
WO2018171928A1 (en) Periodic timer synchronization logic for rrc inactive state
US9049614B2 (en) Method and device for handling mobility management context
US20200329370A1 (en) Node and method for managing a packet data network connection
EP3589033A1 (en) Epc enhancement for long drx and power saving state
KR20210114454A (ko) Ue, 코어 네트워크 장치, 및 통신 제어 방법
WO2011153899A1 (zh) 一种网元失败处理的方法和系统

Legal Events

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

Ref document number: 17741057

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17741057

Country of ref document: EP

Kind code of ref document: A1