CN106982425A - A kind of methods, devices and systems for realizing MTC event-monitorings - Google Patents

A kind of methods, devices and systems for realizing MTC event-monitorings Download PDF

Info

Publication number
CN106982425A
CN106982425A CN201610035863.1A CN201610035863A CN106982425A CN 106982425 A CN106982425 A CN 106982425A CN 201610035863 A CN201610035863 A CN 201610035863A CN 106982425 A CN106982425 A CN 106982425A
Authority
CN
China
Prior art keywords
isr
message
context
service node
hss
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
CN201610035863.1A
Other languages
Chinese (zh)
Inventor
李志军
谢宝国
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to CN201610035863.1A priority Critical patent/CN106982425A/en
Priority to PCT/CN2017/071611 priority patent/WO2017125026A1/en
Publication of CN106982425A publication Critical patent/CN106982425A/en
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/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

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

The invention discloses the methods, devices and systems that one kind realizes machine type communication (MTC) event-monitoring, including：First service node receives the message from home subscriber data server HSS or second service node；Wherein, the message from HSS includes subscription data download request or location updating is responded, and the message from second service node includes user equipment (UE) context acknowledgement message or UE context response informations or UE context request messages；First service node judges that ISR can not be activated according to the message received, ISR is not activated or ISR deactivations are carried out.Pass through the solution of the present invention, when first service node judges that ISR can not be activated, ISR is not activated or carries out ISR deactivations, during switching so as to follow-up UE between E-UTRAN and UTRAN, avoid the occurrence of the over range because caused by information is asynchronous between E-UTRAN and UTRAN and report MTC events, so as to save network signal, network overhead is reduced.

Description

Method, device and system for monitoring MTC event
Technical Field
The present invention relates to Machine Type Communication (MTC) technologies, and in particular, to a method, an apparatus, and a system for implementing MTC event monitoring.
Background
To support MTC communications and improve the competitiveness of third generation mobile communication systems in the communication field, the third generation partnership project (3GPP, 3)rdGeneration Partnership Project) standard work group enhances an Evolved Packet System (EPS) to meet the communication requirements of MTC. Fig. 1 is a schematic diagram of an architecture for supporting MTC communications by EPS. As shown in fig. 1, the EPS mainly includes an Evolved universal terrestrial Radio Access Network (E-UTRAN) and an Evolved packet core Network (EPC). In addition, the EPC supports user Access from a Universal Terrestrial Radio Access Network (UTRAN).
The E-UTRAN includes enhanced nodeb (enodeb) and Radio Network Controller (RNC).
Wherein, EPC includes: a Home Subscriber data Server (HSS), a Mobility Management unit (MME), a Serving Gateway (S-GW), a Packet data network Gateway (P-GW, PDN Gateway), a Serving General Packet Radio Service (GPRS) Support Node (SGSN), a Policy and Charging Rules Function (PCRF), a Service capability Exposure Function/platform (SCEF). Wherein,
the HSS is a permanent storage place of the user subscription data and is positioned in a home network subscribed by the user.
The MME is responsible for managing signaling from a terminal to a Non-Access Stratum (NAS) of a network, tracking, paging management functions and bearer management in an idle mode of a user, for storing user subscription data in a current network.
The S-GW is a gateway between the EPC and the wireless access system and is responsible for user plane bearing from the terminal to the EPC, data caching in an idle mode of the terminal, a function of initiating a service request at a network side, and functions of lawful interception and packet data routing and forwarding.
The P-GW is a gateway connecting the EPS and an external network, and is responsible for functions such as Internet Protocol (IP) address allocation, a charging function, packet filtering, policy application, and the like of a terminal.
The SGSN is a service support point for the UTRAN user to access the EPC, and is functionally similar to the MME, and is responsible for functions such as location update, paging management, and bearer management of the user.
The PCRF is responsible for providing Policy control and charging rules to the Policy and Charging Enforcement Function (PCEF).
The SCEF is responsible for providing various operator services to third party services, such as: and the MTC terminal monitors the service.
In the MTC service, the MTC terminal monitoring service is a typical and widely applied service. The MTC terminal monitors traffic, that is, performs required MTC event detection and reporting for a specific UE. MTC events can be classified into several classes, such as: the method comprises the following steps of pairing the International Mobile Subscriber Identity (IMSI) of the terminal with the International Mobile Equipment Identity (IMEI), terminal-based change, terminal network state change, terminal communication failure and the like.
In this case, monitoring some MTC events may cause an increase in signaling load, thereby affecting the efficiency of the network, such as detecting a change in the location of a terminal. In order to protect the network, the operator typically requires the third party service to set a Validity Time (Validity Time) and a Maximum Number of Reports (Maximum Number of Reports) when configuring the monitoring of MTC events. The effective time limits the return of the action time of the MTC event monitoring, and the network automatically stops the MTC time monitoring when the effective time is exceeded; the maximum report number defines the number of the MTC event reports reported by the network at most, and when the maximum report number is reached, the network automatically stops the MTC event monitoring.
Since the effective time set by MTC event monitoring may be long (e.g. 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, the network needs to synchronize the remaining number of reports between the SGSN/MME and the HSS when the UE is detached from the network or the SGSN/MME is switched. Otherwise, the SGSN/MME defaults to use the maximum report number in the configuration information of the initial MTC event monitoring as the remaining report number, so that the MTC event report exceeding the range may be reported, increasing the network load.
Since the UE may frequently switch between the UTRAN and the EUTRAN, the 3GPP proposes an Idle Signaling Reduction (ISR) function to reduce the number of Routing Area Update (RAU) and Tracking Area Update (TAU) Signaling when the UE switches between the UTRAN and the EUTRAN in an Idle state.
The existing method for implementing MTC event monitoring roughly includes:
in the process that the UE is attached to the MME (or SGSN), the HSS sends MTC event configuration information to the MME (or SGSN); in the process of switching the UE from the MME to the SGSN (or from the SGSN to the MME), the MME and the SGSN activate ISR, and the HSS sends MTC event configuration information to the SGSN (or the MME).
In the existing method for realizing MTC event monitoring, before handover, the HSS sends MTC event configuration information to the MME (or SGSN), after handover, the HSS also sends MTC event configuration information to the SGSN (or MME), and the maximum report number in the MTC event configuration information is the same, which causes that the remaining report number of the same MTC event between the SGSN and the MME is maintained according to the maximum report number in the MTC event configuration information, and in the process of subsequent handover of the UE between E-UTRAN and UTRAN, because the remaining report numbers on the SGSN and MME are asynchronous, the MTC event cumulatively reported by the SGSN and MME exceeds the maximum report number, thereby causing the maximum report number set in MTC event configuration to fail, wasting network signaling, and increasing network overhead.
Disclosure of Invention
In order to solve the above problems, the present invention provides a method, an apparatus, and a system for implementing MTC event monitoring, which can reduce network overhead.
In order to achieve the above object, the present invention provides a method for monitoring MTC events in machine-type communication, including:
a first service node receives a message from a home subscriber data server (HSS) or a second service node; the message from the HSS comprises a subscription data downloading request or a location updating response, and the message from the second service node comprises a User Equipment (UE) context confirmation message or a UE context response message or a UE context request message;
and the first service node judges that the idle state signaling optimization ISR can not be activated, and does not activate or deactivate the ISR according to the received message.
Optionally, the method further includes:
and the first service node indicates the second service node not to activate the ISR or to deactivate the ISR.
Optionally, the determining, by the first service node according to the received message, that ISR cannot be activated includes:
the first service node judges that the ISR is activated; judging that the received subscription data downloading request from a home subscriber data server (HSS) comprises MTC event configuration information or ISR deactivation indication;
or, the first service node determines that the first service node itself has activated an 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 a maximum number of reports;
or, the first serving node determines that the received UE context acknowledgement message from the second serving node does not include an ISR activation instruction, or includes an ISR deactivation instruction.
Optionally, the determining, by the first service node according to the received message, that ISR cannot be activated includes:
the first serving node determining that the received UE context response message from the second serving node includes the remaining report number of one or more MTC events;
the instructing the second serving node not to activate ISR comprises:
the first serving node sending 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.
Optionally, the determining, by the first service node according to the received message, that ISR cannot be activated includes:
the first service node receives a UE context request message from the second service node and judges that the first service node starts MTC event monitoring;
the instructing the second serving node not to activate ISR comprises:
the first serving node sending a UE context response message to the second serving node; wherein the UE context response message does not include ISR capability information and also includes the remaining report number of one or more MTC events.
Optionally, the determining, by the first service node according to the received message, that ISR cannot be activated includes:
the first service node judges that the ISR is activated; judging that the received location updating response from the HSS comprises MTC event configuration information, or judging that the location updating response comprises an ISR deactivation indication;
the instructing the second service 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.
Optionally, the first serving node is a mobility management unit MME, and the second serving node is a serving gprs support node SGSN;
or, the first serving node is an SGSN, and the second serving node is an MME.
The invention also provides a device for realizing the monitoring of the MTC events, which at least comprises the following components:
a receiving module, configured to receive a message from a home subscriber data server HSS or a second serving node; the message from the HSS comprises a subscription data downloading request or a location updating response, and the message from the second service node comprises a User Equipment (UE) context confirmation message or a UE context response message or a UE context request message;
the judging module is used for judging that the idle state signaling optimization ISR can not be activated according to the received message and sending a notification message to the processing module;
and the processing module is used for receiving the notification message and not activating the ISR or deactivating the ISR.
Optionally, the processing module is further configured to:
and indicating the second service node not to activate the ISR or to deactivate the ISR.
Optionally, the determining module is specifically configured to:
judging that the ISR is activated per se; judging that the received subscription data downloading request from a home subscriber data server (HSS) comprises MTC event configuration information or ISR deactivation indication;
or judging that the ISR is activated, and judging that the received subscription data downloading request from the HSS comprises the MTC event configuration information, wherein the MTC event configuration information comprises the maximum report number;
or, it is determined that the received UE context acknowledgement message from the second serving node does not include an ISR activation instruction, or includes an ISR deactivation instruction;
and sending the notification message to the processing module.
Optionally, the determining module is specifically configured to:
judging that the received UE context response message from the second service node comprises the residual report quantity of one or more MTC events, and sending the notification message to the processing module;
the processing module is specifically configured to:
receiving the notification message, and sending 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.
Optionally, the determining module is specifically configured to:
receiving a UE context request message from the second service node, judging that the MTC event monitoring is started, and sending the notification message to the processing module;
the processing module is specifically configured to:
receiving the notification message, and sending a UE context response message to the second serving node; wherein the UE context response message does not include ISR capability information and also includes the remaining report number of one or more MTC events.
Optionally, the determining module is specifically configured to:
judging that the ISR is activated per se; and, judging that the received location update response from the HSS includes MTC event configuration information, or judging that the location update response includes an ISR deactivation indication, sending the notification message to the processing module;
the processing module is specifically configured to:
receiving the notification message, and resending a UE context confirmation 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 invention also provides a system for realizing the monitoring of the MTC events, which at least comprises the following steps:
a first service node for receiving a message from a home subscriber data server (HSS) or a second service node; the message from the HSS comprises a subscription data downloading request or a location updating response, and the message from the second service node comprises a User Equipment (UE) context confirmation message or a UE context response message or a UE context request message; judging that idle state signaling optimization ISR can not be activated according to the received message, and indicating a second service node to not activate ISR or to deactivate ISR;
and the second service node is used for not activating the ISR or deactivating the ISR under the indication of the first service node.
Optionally, the first service node is specifically configured to:
receiving a subscription data downloading request from the HSS;
judging that the ISR is activated per se; judging that the received subscription data downloading request from a home subscriber data server (HSS) comprises MTC event configuration information or ISR deactivation indication;
or judging that the ISR is activated, and judging that the received subscription data downloading request from the HSS comprises the MTC event configuration information, wherein the MTC event configuration information comprises the maximum report number;
or, it is determined that the received UE context acknowledgement message from the second serving node does not include an ISR activation indication or includes an ISR deactivation indication.
Optionally, the first service node is specifically configured to:
determining that the received UE context response message from the second serving node includes a remaining report number of one or more MTC events; sending 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 second serving node is specifically configured to:
receiving a UE context response message from the device, judging that the UE context response message does not include ISR capability information, or judging that the UE context response message includes the remaining report number of one or more MTC events, and not activating ISR.
Optionally, the second service node is further configured to:
and receiving a location updating response from the HSS, and updating the maximum report quantity of the corresponding MTC event configuration information in the location updating response according to the residual report quantity of the one or more MTC events.
Optionally, the first service node is specifically configured to:
receiving a UE context request message from the second service node, and judging that the MTC event monitoring is started per se; re-sending 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 second serving node is specifically configured to:
receiving a UE context confirmation message from the device, judging that the UE context confirmation message does not comprise an ISR activation instruction, and not activating an ISR; or judging that the UE context confirmation message comprises an ISR deactivation instruction, and performing ISR deactivation.
Compared with the prior art, the technical scheme of the invention comprises the following steps: a first service node receives a message from a home subscriber data server (HSS) or a second service node; the message from the HSS comprises a subscription data downloading request or a location updating response, and the message from the second service node comprises a User Equipment (UE) context confirmation message or a UE context response message or a UE context request message; and the first service node judges that the ISR can not be activated, does not activate or deactivate the ISR according to the received message, and/or indicates the second service node to not activate or deactivate the ISR. According to the scheme of the invention, when the first service node judges that the ISR can not be activated according to the received message, the ISR is not activated or is deactivated, so that the condition that the residual report quantity on the SGSN and the MME is not synchronous is avoided in the subsequent process of switching the UE between the E-UTRAN and the UTRAN, the MTC events which are cumulatively reported by the SGSN and the MME are controlled within the limit of the maximum report quantity, network signaling is saved, and network overhead is reduced.
Drawings
The accompanying drawings in the embodiments of the present invention are described below, and the drawings in the embodiments are provided for further understanding of the present invention, and together with the description serve to explain the present invention without limiting the scope of the present invention.
Fig. 1 is a schematic structural diagram of an existing EPS supporting MTC communications;
FIG. 2 is a flowchart illustrating a method for implementing MTC event monitoring when ISR is not activated in the prior art;
FIG. 3 is a flowchart of a method for implementing MTC event monitoring when ISR is activated in the prior art;
FIG. 4 is a flowchart of a method for implementing MTC event monitoring according to the present invention;
FIG. 5 is a flowchart illustrating a method for implementing MTC event monitoring according to a first embodiment of the invention;
FIG. 6 is a flowchart illustrating a method for implementing MTC event monitoring according to a second embodiment of the present invention;
FIG. 7 is a flowchart illustrating a method for monitoring MTC events according to a third embodiment of the present invention;
FIG. 8 is a flowchart illustrating a method for monitoring MTC events 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 the present invention;
fig. 10 is a schematic structural diagram of a system for implementing MTC event monitoring according to the present invention.
Detailed Description
The following further description of the present invention, in order to facilitate understanding of those skilled in the art, is provided in conjunction with the accompanying drawings and is not intended to limit the scope of the present invention. In the present application, the embodiments and various aspects of the embodiments may be combined with each other without conflict.
Fig. 2 is a flowchart of a conventional method for monitoring MTC events without activating ISRs. As shown in fig. 2, the method includes:
step 200, the UE attaches to the network.
Step 201, when needing to monitor the MTC event for the UE, the SCEF sends a terminal monitoring request to the HSS.
In this step, the SCEF generally sends a terminal monitoring request to the HSS when receiving a management request from a third party Application Server (AS).
In this step, the terminal monitoring request includes one or more MTC event configuration information.
Wherein each MTC event configuration information at least comprises: SCEF identity, SCEF reference ID, MTC event type. The SCEF ID is used to identify different SCEFs, and the SCEF reference ID is used to identify a specific MTC event configuration message next to the SCEF.
The MTC event configuration information may also include restriction information for MTC event monitoring, such as: the time of validity and/or the maximum number of reports, etc.
Step 202, the HSS stores the MTC event configuration information in subscription data of the UE, and sends a subscription data download request to the SGSN/MME.
In this step, if the UE is attached to the SGSN and the MME at the same time, the HSS needs to send a subscription data download request to the SGSN and the MME at the same time.
In this step, the subscription data download request includes MTC event configuration information.
Step 203, the SGSN/MME saves the MTC event configuration information in the subscription data download request, and starts MTC event monitoring according to the MTC event configuration information.
In this step, 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 activates a counter variable for monitoring the MTC event corresponding to the MTC event configuration information: the number of reports remaining. And setting the residual report quantity as the maximum report quantity in the MTC event configuration information at the beginning, and automatically decreasing the residual report quantity after the MTC event is detected and reported each time.
In this step, when the SGSN/MME detects that an 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 downloading response to the HSS.
In this step, the subscription data download response may include MTC event configuration result information and MTC event report.
The MTC event configuration result information indicates whether the SGSN/MME successfully receives the MTC event configuration information.
And if the SGSN/MME detects the MTC event, the subscription data download response comprises an MTC event report. For example, if an MTC event is detected, the subscription data download response includes an MTC event report corresponding to MTC event monitoring.
Step 205, the HSS sends the terminal monitoring response to the SCEF.
In this step, the terminal monitoring response includes MTC event configuration result information returned by the SGSN/MME, and if in step 204 the subscription data download response includes an MTC event report, the terminal monitoring response also includes the MTC event report.
And step 206, the SGSN/MME detects the MTC event afterwards, 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 an MTC event report.
In this step, the monitoring report message includes the generated MTC event report.
In this step, after the SGSN/MME sends the monitoring report request, the remaining number of reports corresponding to the MTC event that occurred is subtracted by one.
Step 208, the UE detaches from the network.
Step 209, the SGSN/MME sends a notification message to the HSS.
In this step, the notification message includes the remaining report number corresponding to each MTC event.
Each MTC event may refer to all MTC events of the UE, or each MTC event reported by the SGSN/MME.
Step 210, the HSS updates the maximum report number in the corresponding MTC event configuration information according to the remaining report number in the notification message.
In this step, if the remaining number of reports corresponding to the MTC event is less than the maximum number of reports corresponding to the MTC event in the MTC event configuration information, the maximum number of reports corresponding to the MTC event is updated according to the remaining number of reports corresponding to the MTC event.
Fig. 3 is a flowchart of a conventional method for implementing MTC event monitoring when ISR is activated. As shown in fig. 3, the method includes:
step 300, the SCEF sends a terminal monitoring request to the HSS.
In this step, it is assumed that the UE is not attached to the network when the SCEF sends the monitoring request to the HSS.
In this step, the terminal monitoring request includes one or more MTC event configuration information.
In this step, the SCEF generally sends a terminal monitoring request to the HSS when receiving a management request from a third party Application Server (AS).
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.
In this step, the terminal monitoring response message includes MTC event configuration result information.
The MTC event configuration result information indicates whether the HSS accepts 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) to the HSS.
Step 304, the HSS sends a location update response to the MME.
In this step, the location update response includes subscription data of the UE, and the subscription data of the UE includes MTC event configuration information.
Step 305, the MME stores the MTC event configuration information in the location update response, and starts MTC event monitoring according to the MTC event configuration information.
Step 306, the MME returns an attach response to the UE.
In this step, the attach response includes a Globally Unique Temporary Identifier (GUTI) for EUTRAN access. In the GUTI, a part of information corresponds to an MME identifier, and an MME can be uniquely identified.
In this step, when the UE receives the attach response, it indicates that the UE has successfully attached to the MME, and the ISR function is not activated at this time.
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.
In this step, the RAU request includes a Temporary identifier indication (TIN) and a Packet Temporary identifier (P-TMSI) generated according to the GUTI, where the P-TMSI is used to identify the Identity of the UE when the UTRAN accesses the UE.
Step 308, the SGSN sends a UE context request message to the MME.
In the step, the SGSN acquires the MME identification according to the TIN in the RAU request and the generated P-TMSI, analyzes the MME address, and generates the UE context request message to the MME according to the analyzed MME address.
Step 309, the MME returns a UE context response message to the SGSN.
In this step, the UE context response message includes ISR capability information (i.e., information indicating whether the MME supports ISR).
Step 310, the SGSN returns a UE context acknowledgement message to the MME.
In this step, when the ISR capability information in the UE context response message indicates that the MME supports ISR and the SGSN itself supports ISR, the UE context acknowledgement message includes information indicating ISR activation.
Thereafter, the SGSN stores the MME identification, and the MME stores the SGSN identification and activates ISR respectively.
Step 311, SGSN sends a location update request to HSS.
In step 312, the HSS sends a location update response to the SGSN.
In this step, 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 MTC event monitoring according to the MTC event configuration information.
Step 314, SGSN returns RAU response to UE.
In this step, the RAU response includes the P-TMSI, ISR activation indication allocated by the SGSN.
Step 315, the UE activates the ISR function.
And step 316, when the SGSN and the MME respectively detect the occurrence of the MTC event, respectively generating an MTC event report, and respectively reporting the MTC event report to the SCEF.
Step 317, UE detach from SGSN and MME.
Step 318, SGSN and MME send notification messages to HSS, respectively.
In this step, the notification message includes the remaining report number 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 number of reports corresponding to each MTC event.
Wherein step 300 and step 301 may occur after step 306 or step 315.
Referring to fig. 4, 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.
In this step, the received message from the HSS may be a subscription data download request or a location update response.
In this step, the received message from the second serving node may be a UE context response message, a UE context acknowledgement message, or a UE context request message.
Step 401, the first service node determines that ISR cannot be activated, does not activate ISR or performs ISR deactivation according to the received message.
Further, the first service node instructs the second service node not to activate ISR or to perform ISR deactivation.
In this step, the determining, by the first service node according to the received message, that ISR cannot be activated includes:
the first service node judges that the ISR is activated; judging that the received subscription data downloading request from the HSS comprises MTC event configuration information or ISR deactivation indication;
the specific way for the first service node to determine whether the first service node itself has activated the ISR may be implemented by using a known technology of a person skilled in the art, and is not used to limit the protection scope of the present invention, and is not described herein again.
Or, the first service node determines that the first service node itself has activated the ISR, and determines that the received subscription data download request from the HSS includes MTC event configuration information, and the MTC event configuration information includes a maximum number of reports;
or, the first serving node determines that the received UE context acknowledgement message from the second serving node does not include an ISR activation indication, or includes an ISR deactivation indication.
Or, the determining, by the first service node according to the received message, that ISR cannot be activated includes:
the first service node judges that the received UE context response message from the second service node comprises the residual report quantity of one or more MTC events, or judges that the UE context response message does not comprise ISR capability information; accordingly, the number of the first and second electrodes,
instructing the second serving node not to activate ISR includes:
a first service node sends a UE context confirmation message to a second service node; wherein, the UE context acknowledgement message does not include an ISR activation indication or includes an ISR deactivation indication.
Or, the determining, by the first service node, that ISR cannot be activated includes:
the first service node receives a UE context request message from a second service node and judges that the first service node starts MTC event monitoring; in response to this, the mobile station is,
instructing the second serving node not to activate ISR includes:
the first service node sends a UE context response message to the second service node; the UE context response message does not include ISR capability information, and also includes the remaining report number of one or more MTC events.
Specifically, how to determine whether the MTC event monitoring is started by itself may be implemented by using a known technology of a person skilled in the art, and is not used to limit the protection scope of the present invention, and details are not described here.
Or, the determining, by the first service node according to the received message, that ISR cannot be activated includes:
the first service node judges that the ISR is activated; judging that the received location updating response from the HSS comprises MTC event configuration information, or judging that the location updating response comprises an ISR deactivation indication; accordingly, the number of the first and second electrodes,
instructing the second serving node to perform ISR deactivation includes:
the first service node sends the UE context confirmation message to the second service node again; wherein the UE context acknowledgement message includes an ISR deactivation indication or does not include an ISR activation indication.
In this step, the first service node is an MME, and the second service node is an SGSN; or the first service node is SGSN and the second service node is MME.
According to the scheme of the invention, when the first service node judges that the ISR can not be activated according to the received message, the ISR is not activated or is deactivated, so that the condition that the residual report quantity on the SGSN and the MME is not synchronous is avoided in the subsequent process of switching the UE between the E-UTRAN and the UTRAN, the MTC events which are cumulatively reported by the SGSN and the MME are controlled within the limit of the maximum report quantity, network signaling is saved, and network overhead is reduced.
The process of the present invention is illustrated in detail by the following specific examples.
First embodiment, referring to fig. 5, the method comprises:
step 500, UE attaches to network, after ISR is activated, UE attaches to SGSN and MME at the same time. For the HSS, this means that the UE is registered to both the SGSN and the MME, while the SGSN and the MME are registered to the HSS.
For example, if the UE is located in the E-UTRAN coverage, initiates an Attach (Attach) request to the MME, and the MME sends a location update request to the HSS, the UE attaches to the MME. When UE moves to URAN coverage after entering IDLE state (IDLE), UE initiates RAU process to SGSN, SGSN activates ISR in interactive process of obtaining UE context from MME, SGSN sends position update request to HSS, then UE attaches to SGSN.
Step 501, when needing to monitor the MTC event for the UE, the SCEF sends a terminal monitoring request to the HSS.
In this step, 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.
In this step, the subscription data download request includes MTC event configuration information.
Further, when the HSS determines that the UE is attached to the SGSN and the MME at the same time and the MTC event configuration information includes the maximum report number, 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 respectively start MTC event monitoring according to the MTC event configuration information.
Step 504, the SGSN and the MME return subscription data download responses to the HSS, respectively.
In this step, the subscription data download response includes MTC event configuration result information, and may also include an MTC event report corresponding to MTC event monitoring.
Step 505, the HSS sends the terminal monitoring response to the SCEF.
In this step, the terminal monitoring response includes MTC event configuration result information and MTC event report returned by SGSN/MME.
Step 506, the SGSN and the MME respectively determine that the ISR itself has been activated, and the subscription data download request includes an ISR deactivation indication, and respectively perform ISR deactivation.
And 507, assuming that the UE resides on the MME at the moment, 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 detach from the MME.
In step 510, the MME sends a notification message to the HSS.
In this step, the notification message includes the remaining report number corresponding to each MTC event.
And step 508, the HSS updates the maximum report number of the corresponding MTC events according to the residual report number.
After that, since ISR is deactivated, and UE resides in MME and detach from MME after ISR is deactivated, when UE is not active on SGSN for a long time, according to the prior art, SGSN starts implicit logout timer, and after the timer expires, UE is implicitly detached from SGSN, and specifically how to implicitly detach may be implemented by using the known technology of those skilled in the art, and is not used to limit the protection scope of the present invention, and is not described here any more. When the SGSN implicitly removes the UE, the SGSN may send a notification message to the HSS, carrying the remaining report number of each MTC calculated by the SGSN. And after the HSS receives the residual report quantity reported by the SGSN, if the residual report quantity is less than the maximum report quantity in the corresponding MTC time configuration information, the HSS uses the residual report quantity to update the maximum report quantity in the corresponding MTC event configuration information.
In a second embodiment, referring to fig. 6, the method comprises:
step 600, UE attaches to the network, and after ISR is activated, the UE attaches to SGSN and MME at the same time.
For example, the UE is located in the E-UTRAN coverage, initiates an Attach request to the MME, the MME sends an ULR to the HSS, and the UE attaches to the MME. When UE moves to URAN coverage after entering IDLE state (IDLE), UE initiates RAU process to SGSN, SGSN activates ISR in interactive process of obtaining UE context from MME, SGSN sends ULR to HSS, then UE attaches to SGSN.
Step 601, when needing to monitor the MTC event to the UE, the SCEF sends a terminal monitoring request to the HSS.
In this step, the terminal monitoring request includes one or more MTC event configuration information.
Step 602, the HSS sends a subscription data download request to the SGSN and the MME at the same time.
In this step, 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 respectively start 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.
In this step, the subscription data download response includes MTC event configuration result information, and may also include an MTC event report corresponding to MTC event monitoring.
Step 605, the HSS sends the terminal monitoring response to the SCEF.
In this step, the terminal monitoring response includes MTC event configuration result information and MTC event report returned by SGSN/MME.
Step 606, the SGSN and the MME respectively determine that ISR needs to be deactivated, and respectively deactivate ISR.
In this step, the step in which the SGSN and the MME respectively determine that ISR deactivation is required includes:
the SGSN and the MME respectively judge that the ISR is activated per se, and the subscription data downloading request comprises MTC event configuration information;
or the SGSN and the MME respectively determine that the ISR is activated, and the subscription data download request includes MTC event configuration information, and the MTC event configuration information includes the maximum number of reports.
Step 607, assuming that the UE resides in the MME, when the MME detects the MTC event, 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 detach from the MME.
In step 610, the MME sends a notification message to the HSS.
In this step, the notification message includes the remaining report number 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 number of reports corresponding to each MTC event.
A third embodiment, see fig. 7, the method comprises:
step 700, the SCEF sends a terminal monitoring request to the HSS.
In this step, it is assumed that the UE is not attached to the network when the SCEF sends the terminal monitoring request to the HSS.
In this step, the terminal monitoring request includes one or more MTC event configuration information.
In this step, the SCEF generally sends a terminal monitoring request to the HSS when receiving a management request from a third party Application Server (AS).
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.
In this step, the location update response includes subscription data of the UE, and the subscription data of the UE includes MTC event configuration information.
Step 705, the MME stores the MTC event configuration information in the location update response, and starts 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, it indicates that the UE has successfully attached to the MME, and at this time, the UE activates the ISR function.
Step 708, when the UE enters IDLE state and enters UTRAN coverage, the UE sends RAU request to SGSN.
In this step, the RAU request includes the TIN and the 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.
In this step, the UE context response message includes the remaining report number corresponding to each MTC event. Since the MME starts MTC event monitoring in the foregoing step, in order to synchronize the remaining report number between the MME and the SGSN, the MME needs to notify the SGSN of the remaining report number.
In this step, the UE context response message may or may not include ISR capability information.
In this step, when the MME determines that MTC event monitoring is started on the MME, the MME may not include 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 acknowledgement message to the MME.
In this step, when the SGSN determines that the UE context response message sent by the MME does not include ISR capability information, or determines that the UE context response message sent by the MME includes the remaining report number of one or more MTC events, the SGSN does not include an ISR activation instruction or an ISR deactivation instruction in the UE context acknowledgement message, and the SGSN does not activate the ISR capability.
In step 712, the SGSN sends a location update request to the HSS.
Step 713, the HSS sends a location update response to the SGSN.
In this step, the location update response includes subscription data of the UE, and the subscription data of the UE includes MTC event configuration information.
Step 714, the SGSN stores the MTC event configuration information in the location update response, updates the maximum report number of the corresponding MTC event configuration information in the location update response sent by the HSS according to the remaining report number of each MTC event in the UE context response message sent by the MME, and starts MTC event monitoring according to the updated MTC event configuration information.
Step 715, the SGSN returns an RAU response to the UE.
In this step, the RAU response includes the SGSN-assigned P-TMSI, but not the ISR activation indication.
Step 716, the UE does not activate ISR function.
Step 717, the SGSN and the MME respectively detect the occurrence of the MTC event and respectively generate the MTC event report.
Step 718, the SGSN and the MME report the MTC event report to the SCEF, respectively.
Step 719, the UE detaches from the SGSN or MME.
Step 720, the SGSN or MME sends the remaining report number corresponding to each MTC event to the HSS.
Step 721, the HSS updates the maximum report number corresponding to each MTC event in the MTC event configuration information according to the remaining report number corresponding to each MTC event.
Fourth embodiment, referring to fig. 8, the method comprises:
step 800, the SCEF sends a terminal monitoring request to the HSS.
In this step, it is assumed that the UE is not attached to the network when the SCEF sends the terminal monitoring request to the HSS.
In this step, the terminal monitoring request includes one or more MTC event configuration information.
In this step, the SCEF generally sends a terminal monitoring request to the HSS when receiving a management request from a third party Application Server (AS).
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.
In step 803, the MME sends a location update request to the HSS.
Step 804, the HSS sends a location update response to the MME.
In this step, the location update response includes subscription data of the UE, and the subscription data of the UE includes MTC event configuration information.
Step 805, the MME stores the MTC event configuration information in the location update response, and starts MTC event monitoring according to the MTC event configuration information.
Step 806, the MME returns an attach response to the UE.
In 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 ISR.
Step 808, when the UE enters IDLE state and enters UTRAN coverage, the UE sends RAU request to SGSN.
In this step, the RAU request includes the TIN and the P-TMSI generated from 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.
In this step, the UE context response message includes ISR capability information.
Step 811, the SGSN returns a UE context acknowledgement message to the MME.
In this step, if the MME supports the ISR function and the SGSN also supports the ISR function, the UE context acknowledgement message includes an ISR activation indication.
And then, the SGSN stores an MME identifier, and the MME stores the SGSN identifier and respectively activates ISR functions.
Step 812, the SGSN sends a location update request to the HSS.
Step 813, HSS sends a location update response to SGSN.
In this step, the location update response includes subscription data of the UE, and the subscription data of the UE includes MTC event configuration information.
In this step, when the HSS determines that the UE is attached to the SGSN and the MME at the same time, 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 MTC event monitoring according to the MTC event configuration information.
Step 815, the SGSN determines that the location update response includes MTC event configuration information, or determines that the location update response includes an ISR deactivation indication, and resends the UE context acknowledgement message to the MME.
In this step, the UE context acknowledgement message includes an ISR deactivation indication or does not include an ISR activation indication. Whether the message carries an ISR deactivation indication or does not carry an ISR activation indication indicates that the SGSN and the MME should not activate ISR, and if ISR is activated, ISR should be deactivated, and if ISR is not activated, ISR is not activated.
Thereafter, the SGSN and MME perform deactivation ISR, respectively.
Step 816, the SGSN returns an RAU response to the UE.
In this step, the RAU response includes the SGSN-assigned P-TMSI, but not the ISR activation indication.
Step 817, the UE does not activate the ISR function.
Step 818, SGSN and MME respectively detect the occurrence of MTC event and generate MTC event report respectively.
Step 819, SGSN and MME report MTC event report to SCEF respectively.
Step 820, the UE detach from the SGSN or MME.
Step 821, SGSN or MME sends the remaining report number corresponding to each MTC event to HSS.
Step 822, the HSS updates the maximum report number in the corresponding MTC event configuration information according to the remaining report number.
Referring to fig. 9, the present invention further provides an apparatus for implementing MTC event monitoring, which at least includes:
a receiving module 900, configured to receive a message from a home subscriber data server HSS or a second serving node; the message from the HSS comprises a subscription data downloading request or a location updating response, and the message from the second service node comprises a User Equipment (UE) context confirmation message or a UE context response message or a UE context request message;
a judging module 901, configured to judge that an idle signaling optimization ISR cannot be activated according to the received message, and send a notification message to the processing module 902;
a processing module 902, configured to receive the notification message, and not activate an ISR or perform ISR deactivation.
In the apparatus of the present invention, the processing module is further configured to: and indicating the second service node not to activate the ISR or to deactivate the ISR.
In the apparatus of the present invention, the determining module 901 is specifically configured to:
judging that the ISR is activated per se; judging that the received subscription data downloading request from a home subscriber data server (HSS) comprises MTC event configuration information or ISR deactivation indication;
or judging that the ISR is activated, and judging that the received subscription data downloading request from the HSS comprises MTC event configuration information, wherein the MTC event configuration information comprises the maximum report number;
or, judging that the received UE context confirmation message from the second service node does not include an ISR activation instruction or includes an ISR deactivation instruction;
a notification message is sent to the processing module 902.
In the apparatus of the present invention, the determining module 901 is specifically configured to:
judging that the received UE context response message from the second serving node includes the remaining report number corresponding to one or more MTC events, and sending a notification message to the processing module 902;
the processing module 902 is specifically configured to:
receiving the notification message, and sending a UE context confirmation message to the second service node; wherein, the UE context acknowledgement message does not include an ISR activation indication or includes an ISR deactivation indication.
In the apparatus of the present invention, the determining module 901 is specifically configured to:
receiving a UE context request message from the second serving node, determining that MTC event monitoring has been started, and sending a notification message to the processing module 901;
the processing module 902 is specifically configured to:
receiving the notification message and sending a UE context response message to the second service node; the UE context response message does not include ISR capability information, and also includes the remaining report number of one or more MTC events.
In the apparatus of the present invention, the determining module 901 is specifically configured to:
judging that the ISR is activated per se; moreover, it is determined that the received location update response from the HSS includes MTC event configuration information, or it is determined that the location update response includes an ISR deactivation indication, and a notification message is sent to the processing module 902;
the processing module 902 is specifically configured to:
receiving the notification message, and sending the UE context confirmation message to the second service node again; wherein the UE context acknowledgement message includes an ISR deactivation indication or does not include an ISR activation indication.
Referring to fig. 10, the present invention further provides a system for implementing MTC event monitoring, which at least includes:
a first service node for receiving a message from a home subscriber data server (HSS) or a second service node; the message from the HSS comprises a subscription data downloading request or a location updating response, and the message from the second service node comprises a User Equipment (UE) context confirmation message or a UE context response message or a UE context request message; judging that idle state signaling optimization ISR can not be activated, and not activating or deactivating the ISR according to the received message, and/or indicating a second service node not to activate or deactivate the ISR;
and the second service node is used for not activating the ISR or deactivating the ISR under the indication of the first service node.
In the system of the present invention, the first service node is specifically configured to:
receiving a subscription data downloading request from the HSS;
judging that the ISR is activated per se; judging that the received subscription data downloading request from a home subscriber data server (HSS) comprises MTC event configuration information or ISR deactivation indication;
or judging that the ISR is activated, and judging that the received subscription data downloading request from the HSS comprises the MTC event configuration information, wherein the MTC event configuration information comprises the maximum report number;
or, it is determined that the received UE context acknowledgement message from the second serving node does not include an ISR activation indication or includes an ISR deactivation indication.
In the system of the present invention, the first service node is specifically configured to:
determining that the received UE context response message from the second serving node includes a remaining report number of one or more MTC events; sending 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 second serving node is specifically configured to:
receiving a UE context response message from the device, judging that the UE context response message does not include ISR capability information, or judging that the UE context response message includes the remaining report number of one or more MTC events, and not activating ISR.
In the system of the present invention, the second service node is further configured to:
and receiving a location updating response from the HSS, and updating the maximum report quantity of the corresponding MTC event configuration information in the location updating response according to the residual report quantity of the one or more MTC events.
In the system of the present invention, the first service node is specifically configured to:
receiving a UE context request message from the second service node, and judging that the MTC event monitoring is started per se; re-sending 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 second serving node is specifically configured to:
receiving a UE context confirmation message from the device, judging that the UE context confirmation message does not comprise an ISR activation instruction, and not activating an ISR; or judging that the UE context confirmation message comprises an ISR deactivation instruction, and performing ISR deactivation.
It should be noted that the above-mentioned embodiments are only for facilitating the understanding of those skilled in the art, and are not intended to limit the scope of the present invention, and any obvious substitutions, modifications, etc. made by those skilled in the art without departing from the inventive concept of the present invention are within the scope of the present invention.

Claims (18)

1. A method for realizing Machine Type Communication (MTC) event monitoring is characterized by comprising the following steps:
a first service node receives a message from a home subscriber data server (HSS) or a second service node; the message from the HSS comprises a subscription data downloading request or a location updating response, and the message from the second service node comprises a User Equipment (UE) context confirmation message or a UE context response message or a UE context request message;
and the first service node judges that the idle state signaling optimization ISR can not be activated, and does not activate or deactivate the ISR according to the received message.
2. The method of claim 1, further comprising:
and the first service node indicates the second service node not to activate the ISR or to deactivate the ISR.
3. The method of claim 1 or 2, wherein the first serving node determining that ISR cannot be activated according to the received message comprises:
the first service node judges that the ISR is activated; judging that the received subscription data downloading request from a home subscriber data server (HSS) comprises MTC event configuration information or ISR deactivation indication;
or, the first service node determines that the first service node itself has activated an 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 a maximum number of reports;
or, the first serving node determines that the received UE context acknowledgement message from the second serving node does not include an ISR activation instruction, or includes an ISR deactivation instruction.
4. The method of claim 2, wherein the first serving node determining that ISR cannot be activated according to the received message comprises:
the first serving node determining that the received UE context response message from the second serving node includes the remaining report number of one or more MTC events;
the instructing the second serving node not to activate ISR comprises:
the first serving node sending 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.
5. The method of claim 2, wherein the first serving node determining that ISR cannot be activated according to the received message comprises:
the first service node receives a UE context request message from the second service node and judges that the first service node starts MTC event monitoring;
the instructing the second serving node not to activate ISR comprises:
the first serving node sending a UE context response message to the second serving node; wherein the UE context response message does not include ISR capability information and also includes the remaining report number of one or more MTC events.
6. The method of claim 2, wherein the first serving node determining that ISR cannot be activated according to the received message comprises:
the first service node judges that the ISR is activated; judging that the received location updating response from the HSS comprises MTC event configuration information, or judging that the location updating response comprises an ISR deactivation indication;
the instructing the second service 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.
7. The method according to any of claims 1 to 6, wherein the first serving node is a Mobility Management Element (MME) and the second serving node is a serving general packet radio service technology support node (SGSN);
or, the first serving node is an SGSN, and the second serving node is an MME.
8. An apparatus for implementing MTC event monitoring in machine-type communication, comprising:
a receiving module, configured to receive a message from a home subscriber data server HSS or a second serving node; the message from the HSS comprises a subscription data downloading request or a location updating response, and the message from the second service node comprises a User Equipment (UE) context confirmation message or a UE context response message or a UE context request message;
the judging module is used for judging that the idle state signaling optimization ISR can not be activated according to the received message and sending a notification message to the processing module;
and the processing module is used for receiving the notification message and not activating the ISR or deactivating the ISR.
9. The apparatus of claim 8, wherein the processing module is further configured to:
and indicating the second service node not to activate the ISR or to deactivate the ISR.
10. The apparatus according to claim 8 or 9, wherein the determining module is specifically configured to:
judging that the ISR is activated per se; judging that the received subscription data downloading request from a home subscriber data server (HSS) comprises MTC event configuration information or ISR deactivation indication;
or judging that the ISR is activated, and judging that the received subscription data downloading request from the HSS comprises the MTC event configuration information, wherein the MTC event configuration information comprises the maximum report number;
or, it is determined that the received UE context acknowledgement message from the second serving node does not include an ISR activation instruction, or includes an ISR deactivation instruction;
and sending the notification message to the processing module.
11. The apparatus according to claim 8 or 9, wherein the determining module is specifically configured to:
judging that the received UE context response message from the second service node comprises the residual report quantity of one or more MTC events, and sending the notification message to the processing module;
the processing module is specifically configured to:
receiving the notification message, and sending 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.
12. The apparatus according to claim 9, wherein the determining module is specifically configured to:
receiving a UE context request message from the second service node, judging that the MTC event monitoring is started, and sending the notification message to the processing module;
the processing module is specifically configured to:
receiving the notification message, and sending a UE context response message to the second serving node; wherein the UE context response message does not include ISR capability information and also includes the remaining report number of one or more MTC events.
13. The apparatus according to claim 9, wherein the determining module is specifically configured to:
judging that the ISR is activated per se; and, judging that the received location update response from the HSS includes MTC event configuration information, or judging that the location update response includes an ISR deactivation indication, sending the notification message to the processing module;
the processing module is specifically configured to:
receiving the notification message, and resending a UE context confirmation 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.
14. A system for realizing MTC event monitoring is characterized by at least comprising:
a first service node for receiving a message from a home subscriber data server (HSS) or a second service node; the message from the HSS comprises a subscription data downloading request or a location updating response, and the message from the second service node comprises a User Equipment (UE) context confirmation message or a UE context response message or a UE context request message; judging that idle state signaling optimization ISR can not be activated according to the received message, and indicating a second service node to not activate ISR or to deactivate ISR;
and the second service node is used for not activating the ISR or deactivating the ISR under the indication of the first service node.
15. The system of claim 14, wherein the first serving node is specifically configured to:
receiving a subscription data downloading request from the HSS;
judging that the ISR is activated per se; judging that the received subscription data downloading request from a home subscriber data server (HSS) comprises MTC event configuration information or ISR deactivation indication;
or judging that the ISR is activated, and judging that the received subscription data downloading request from the HSS comprises the MTC event configuration information, wherein the MTC event configuration information comprises the maximum report number;
or, it is determined that the received UE context acknowledgement message from the second serving node does not include an ISR activation indication or includes an ISR deactivation indication.
16. The system of claim 14, wherein the first serving node is specifically configured to:
determining that the received UE context response message from the second serving node includes a remaining report number of one or more MTC events; sending 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 second serving node is specifically configured to:
receiving a UE context response message from the device, judging that the UE context response message does not include ISR capability information, or judging that the UE context response message includes the remaining report number of one or more MTC events, and not activating ISR.
17. The system of claim 16, wherein the second serving node is further configured to:
and receiving a location updating response from the HSS, and updating the maximum report quantity of the corresponding MTC event configuration information in the location updating response according to the residual report quantity of the one or more MTC events.
18. The system of claim 14, wherein the first serving node is specifically configured to:
receiving a UE context request message from the second service node, and judging that the MTC event monitoring is started per se; re-sending 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 second serving node is specifically configured to:
receiving a UE context confirmation message from the device, judging that the UE context confirmation message does not comprise an ISR activation instruction, and not activating an ISR; or judging that the UE context confirmation message comprises an ISR deactivation instruction, and performing ISR deactivation.
CN201610035863.1A 2016-01-19 2016-01-19 A kind of methods, devices and systems for realizing MTC event-monitorings Pending CN106982425A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201610035863.1A CN106982425A (en) 2016-01-19 2016-01-19 A kind of methods, devices and systems for realizing MTC event-monitorings
PCT/CN2017/071611 WO2017125026A1 (en) 2016-01-19 2017-01-18 Method, device and system for implementing mtc event monitoring, and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610035863.1A CN106982425A (en) 2016-01-19 2016-01-19 A kind of methods, devices and systems for realizing MTC event-monitorings

Publications (1)

Publication Number Publication Date
CN106982425A true CN106982425A (en) 2017-07-25

Family

ID=59340994

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610035863.1A Pending CN106982425A (en) 2016-01-19 2016-01-19 A kind of methods, devices and systems for realizing MTC event-monitorings

Country Status (2)

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

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110831056A (en) * 2018-08-13 2020-02-21 华为技术有限公司 Monitoring event reporting method and device
WO2020135536A1 (en) * 2018-12-29 2020-07-02 华为技术有限公司 Communication method and apparatus
WO2020156460A1 (en) * 2019-02-02 2020-08-06 Telefonaktiebolaget Lm Ericsson (Publ) Methods and nodes for ue-to-ue event monitoring
CN112690015A (en) * 2018-09-14 2021-04-20 瑞典爱立信有限公司 Auditing process for event monitoring

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101572942B (en) * 2008-04-30 2012-04-04 华为技术有限公司 Hidden separation method, system and device
CN101577955B (en) * 2008-07-11 2011-04-20 中兴通讯股份有限公司 Method and system for determining activation of signaling-saving function in idle mode
CN101640933B (en) * 2008-07-31 2012-07-04 华为技术有限公司 Method for paging user equipment, network equipment, user equipment and network system
CN102333294B (en) * 2011-09-23 2014-04-09 电信科学技术研究院 Method and device for renewing terminal reachable state information based on detaching process
US9999020B2 (en) * 2014-01-13 2018-06-12 Lg Electronics Inc. Downlink data transfer method and location update procedure execution method

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110831056A (en) * 2018-08-13 2020-02-21 华为技术有限公司 Monitoring event reporting method and device
CN110831056B (en) * 2018-08-13 2021-11-19 华为技术有限公司 Monitoring event reporting method and device
CN112690015A (en) * 2018-09-14 2021-04-20 瑞典爱立信有限公司 Auditing process for event monitoring
CN112690015B (en) * 2018-09-14 2023-12-29 瑞典爱立信有限公司 Audit process for event monitoring
US11889328B2 (en) 2018-09-14 2024-01-30 Telefonaktiebolaget Lm Ericsson (Publ) Audit process for the monitoring of events
WO2020135536A1 (en) * 2018-12-29 2020-07-02 华为技术有限公司 Communication method and apparatus
WO2020156460A1 (en) * 2019-02-02 2020-08-06 Telefonaktiebolaget Lm Ericsson (Publ) Methods and nodes for ue-to-ue event monitoring

Also Published As

Publication number Publication date
WO2017125026A1 (en) 2017-07-27

Similar Documents

Publication Publication Date Title
KR101339044B1 (en) Handling reachability of mobile device when serving core network node changes
EP2699048B1 (en) Accelerating restoration of communication services upon mobility management node restarting
US9629021B2 (en) Method for controlling service in radio communication system
DK2702793T3 (en) Improvements to completed mobile calls
CN102056140B (en) Method and system for acquiring machine type communication terminal information
EP2583508B1 (en) P-gw/ggsn issued paging requests
CN102413485B (en) A kind of method for supervising of machine terminal, system and machine terminal
EP2385720B1 (en) Overload control in a packet mobile communication system
US11558787B2 (en) Monitoring event management method and apparatus
EP2785125A1 (en) Method and system for determining accessibility of terminal group
EP2706810A2 (en) Service restoration processing method and mobility management network element
KR20130112664A (en) Access control method and apparatus for machine type communication devices with dual priority applications
CN106572505A (en) Communication method, apparatus and terminal
US10966106B2 (en) Method and apparatus for managing a PDN connection in a wireless communication system
WO2017125026A1 (en) Method, device and system for implementing mtc event monitoring, and storage medium
CN102083112A (en) Method, network equipment and user equipment for guaranteeing service connection
EP3214893B1 (en) Data processing method, apparatus, terminal and mobility management entity
CN102625276A (en) Method and system for activating a terminal
CN106982446A (en) A kind of methods, devices and systems for realizing MTC event-monitorings
KR20210114454A (en) UE, core network device, and communication control method
WO2011153899A1 (en) Method and system for processing network element failure

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
WD01 Invention patent application deemed withdrawn after publication

Application publication date: 20170725

WD01 Invention patent application deemed withdrawn after publication