WO2020169050A1 - 一种监控事件的方法及装置 - Google Patents

一种监控事件的方法及装置 Download PDF

Info

Publication number
WO2020169050A1
WO2020169050A1 PCT/CN2020/075877 CN2020075877W WO2020169050A1 WO 2020169050 A1 WO2020169050 A1 WO 2020169050A1 CN 2020075877 W CN2020075877 W CN 2020075877W WO 2020169050 A1 WO2020169050 A1 WO 2020169050A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobility management
network element
management network
location
timer
Prior art date
Application number
PCT/CN2020/075877
Other languages
English (en)
French (fr)
Inventor
周晓云
阎亚丽
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP20759930.9A priority Critical patent/EP3911010A4/en
Priority to JP2021548611A priority patent/JP7200392B2/ja
Publication of WO2020169050A1 publication Critical patent/WO2020169050A1/zh
Priority to US17/404,218 priority patent/US12028931B2/en
Priority to JP2022204705A priority patent/JP7451667B2/ja

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/08—Mobility data transfer
    • H04W8/12—Mobility data transfer between location registers or mobility servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/029—Location-based management or tracking services
    • 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
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H04W48/04—Access restriction performed under specific conditions based on user or terminal location or mobility data, e.g. moving direction, speed
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/06—De-registration or detaching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H04W64/003—Locating users or terminals or network equipment for network management purposes, e.g. mobility management locating network equipment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/06—Registration at serving network Location Register, VLR or user mobility server
    • H04W8/065—Registration at serving network Location Register, VLR or user mobility server involving selection of the user mobility server
    • 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/08—Mobility data transfer
    • 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
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration

Definitions

  • the present invention relates to the field of wireless communication technology, in particular to a method and device for monitoring events.
  • the 3rd generation partnership project (3GPP) defines a service capability exposure (SCE) architecture that can be applied to 4G and 5G networks.
  • Figure 1 is the architecture diagram of the service capability opening in the 4G network. Based on this architecture, the 3GPP network can safely provide services to third-party service providers' service capability servers/application servers (Services Capability Server/Application Server, SCS/AS) ability.
  • Service Capability Exposure Function (SCEF) is the core network element in this architecture, enabling the 3GPP network to safely provide service capabilities to the third-party service provider SCS/AS.
  • the home subscriber server (Home Subscriber Server, HSS) is the home subscriber subscription server, which stores the subscriber's subscription information.
  • a mobility management entity (Mobility Management Entity, MME) and a GPRS service support node (Serving GPRS Support Node, SGSN) are network elements responsible for mobility management of user equipment (User Equipment, UE).
  • SCS/AS calls the service capabilities provided by SCEF through T8's Application Programming Interface (API) interface.
  • Figure 2 is the architecture diagram of the service capability opening in the 5G network.
  • the 5G system is based on the service-oriented architecture.
  • the Network Exposure Function (NEF) has a function similar to SCEF in the 4G network.
  • SCS/AS develops the services and capabilities supported by the 3GPP network.
  • the Nnef interface is a service-based interface displayed by NEF.
  • the Unified Data Management has a function similar to that of the HSS in the 4G network.
  • NEF provides supported business capabilities.
  • the Nudm interface is a service-based interface presented by UDM.
  • the core network access and mobility management function network element (Core Access and Mobility Management Function, AMF) plays the role of the MME in the 4G network.
  • AMF Core Access and Mobility Management Function
  • SCS/AS supports event monitoring of UEs.
  • the UE can be monitored for various events, such as Location Reporting.
  • SCS/AS sends a monitoring request message to SCEF/NEF.
  • the monitoring request message indicates the UE to be monitored and the minimum reporting interval (MRI).
  • the MRI is used to indicate the location reporting instructions. The minimum time interval between. If MRI is provided to MME/SGSN/AMF, MME/SGSN/AMF will monitor the event according to the monitoring event parameters issued by HHS/UDM and start the timer. The value is MRI. Before the timer expires, the timer is running. The running time does not exceed the MRI, MME/SGSN/AMF will suppress the location report notification of the detected UE location. When the timer expires, that is, when the timer runs for the MRI, the MME/SGSN/AMF sends the latest suppressed Location report notification.
  • the new MME/SGSN/AMF to which the UE moves will reset the timer according to the MRI. Therefore, the time interval between the two location report notifications of the UE may exceed the MRI, and it is extreme In this case, the location of the UE changes multiple times, and the time interval between two adjacent location changes does not exceed MRI. At this time, the MME/SGSN/AMF will not send location report notifications, making SCS/AS unable to monitor the UE in time Location update status.
  • the embodiments of the present application provide a method and device for monitoring events, so as to avoid the excessively long time interval between two location report notifications of the existing UE, and to ensure that the SCS/AS can timely monitor the location update status of the UE.
  • a method for monitoring events including the following processes:
  • the first mobility management network element determines a first duration value; sends the first duration value to the second mobility management network element, and the first duration value is the first duration value.
  • the current value of the first timer corresponding to the user equipment UE maintained by a mobility management network element, and the first mobility management network element usually suppresses sending the location report notification of the UE before the first timer expires ;
  • the second mobility management network element receives the first duration value sent by the first mobility management network element, starts the second timer corresponding to the UE maintained by itself, and sets the second timer according to the first duration value.
  • the process of mobility management network element reselection suppose the UE moves from the first mobility management network element to the second mobility management network element, and the first mobility management network element maintains the first timer corresponding to the UE.
  • the current value of is sent to the second mobility management network element as the first duration value, and the second mobility management network element uses the first duration value to set the initial value of the second timer corresponding to the UE maintained by itself, thereby Ensure that the second mobility management network element continues to time based on the timed value of the first mobility management network element, instead of resetting the timer to re-timing.
  • the second mobility management network element determines that the second timer expires, Report the UE's suppressed location report notification, and the time interval between the UE's two location report notifications will not be too long, which can ensure that the SCS/AS can monitor the UE's location update in time.
  • the second mobility management network element may suppress sending a location report notification of the UE.
  • the location report notification of the UE is suppressed, thereby avoiding the impact of the signaling load on the network caused by frequently triggering the location report notification when the location update of the UE occurs frequently.
  • the second mobility management network element may send the suppressed The most recent location report notification among the location report notifications of the UE.
  • the second mobility management network element reports the most recent location report notification among the location report notifications of the suppressed UE, which can ensure that the location information of the UE detected by the SCS/AS is that of the UE. Current location information, and can ensure the accuracy of the UE's location update status monitored by SCS/AS.
  • the first mobility management network element may also receive the minimum report interval sent by the user data management network element, and
  • the minimum reporting interval is the minimum time interval between two or more location report notifications; the first mobility management network element starts the first timer, and sets the first timer according to the minimum reporting interval The initial value of.
  • the first mobility management network element is the mobility management network element before the UE moves. When setting the first timer corresponding to the UE, it may be set according to the minimum report interval sent by the user data management network element.
  • the first mobility management network element may also suppress the location report notification of the UE. Similarly, before the first timer expires, the location report notification of the UE is suppressed, which can avoid the impact of the signaling load on the network caused by frequently triggering the location report notification when the location update of the UE occurs frequently.
  • the first mobility management network element may also send a location report notification of the UE.
  • the first mobility management network element may also send the suppressed And restart the first timer and set an initial value according to the minimum reporting interval.
  • the most recent position report in the position report notification of the suppressed UE is notified, which can ensure that the position information of the UE detected by SCS/AS is the current position information of the UE, and restart and reset
  • the first timer continues to monitor the event, and when the reset first timer expires, it can continue to report the location report notification of the UE.
  • the first mobility management network element may also save all The location information of the UE in the most recent location report notification is used as the location information of the UE that was reported most recently.
  • the first mobility management network element may also send the most recently reported location information of the UE to the second mobility management network element; the second mobility management The network element receives the most recently reported location information of the UE that is sent by the first mobility management network element and saved by the first mobility management network element. By storing and/or sending the location information of the UE last reported, the mobility management network element can learn the location information of the UE last reported.
  • the second mobility management network element may also confirm that the current location information of the UE is different from the location information of the UE reported last time, and then send the UE suppressed Before the notification of the location report.
  • the first mobility management network element may also confirm that the current location information of the UE is different from the location information of the UE reported last time, the first mobility management network element sends the UE again The suppressed location is reported before notification.
  • the mobility management network element When the timer expires, when the mobility management network element confirms that the current location information of the UE is different from the location information of the most recently reported UE, it sends the UE's suppressed location report notification to ensure that SCS/AS can learn the UE's information in time. Location update status.
  • the second mobility management network element when the second mobility management network element expires in the second timer, and the current location information of the UE is the same as the location information of the UE reported last time , It is also possible not to send the location report notification of the UE.
  • the UE may not be sent Location report notification.
  • the mobility management network element When the timer expires, when the mobility management network element confirms that the current location information of the UE is the same as the location information of the last reported UE, if it does not send the location report notification of the UE, it is avoided that the current location information of the UE is compared with the latest location information. When the reported location information of the UE is the same, the same meaningless location report notification is sent to the SCS/AS, thereby saving network resources.
  • the second mobility management network element confirms that the current location information of the UE is different from the current location of the UE reported last time. At the same time, it can also generate the location report notification that the UE is suppressed.
  • the first mobility management network element Before the first timer expires, when the first mobility management network element confirms that the current location information of the UE is different from the current location of the UE reported last time, it may also generate the UE Suppressed location report notification.
  • the mobility management network element Before the timer expires, when the current location information of the UE is different from the current location of the UE reported last time, the mobility management network element generates a location report notification of the UE, which can ensure that SCS/AS can learn the location update of the UE in time In the case, when the current location information of the UE is the same as the current location of the UE reported last time, suppressing the generation of the location report notification of the UE can also save the processing resources of the mobility management network element.
  • the second mobility management network element may also receive a minimum reporting interval sent by the user data management network element, where the minimum reporting interval is the minimum time interval between two or more location report notifications When the second timer expires, the second mobility management network element restarts the second timer, and sets the initial value of the second timer according to the minimum reporting interval.
  • the second mobility management network element can also start and restart the second timer to continue monitoring the event according to the minimum reporting interval sent by the user data management network element.
  • the timer expires, the UE can continue to report the location report notification.
  • the second mobility management network element may also save all The location information of the UE in the most recent location report notification is used as the location information of the UE that was reported most recently.
  • the second mobility management network element or the first mobility management network element is any one of MME, SGSN, and AMF.
  • a device for monitoring events has the function of realizing the behavior of the mobility management network element in the foregoing method, and includes means for executing the steps or functions described in the foregoing method.
  • the steps or functions can be realized by software, or by hardware (such as a circuit), or by a combination of hardware and software.
  • the mobility management network element includes a first mobility management network element and/or a second mobility management network element.
  • the foregoing device includes one or more processors and communication units.
  • the one or more processors are configured to support the device to perform corresponding functions of the mobility management network element in the above method.
  • the device may further include one or more memories, where the memory is used for coupling with the processor and stores necessary program instructions and/or data for the device.
  • the one or more memories may be integrated with the processor, or may be provided separately from the processor. This application is not limited.
  • the above device includes a transceiver, a processor, and a memory.
  • the processor is used to control the transceiver or the input/output circuit to send and receive signals
  • the memory is used to store a computer program
  • the processor is used to run the computer program in the memory so that the device executes the first aspect or any one of the first aspect The method that the mobility management network element completes in the possible implementation mode.
  • the foregoing device includes one or more processors and communication units.
  • the one or more processors are configured to support the device to perform corresponding functions of the mobility management network element in the above method.
  • the device may further include one or more memories, where the memories are configured to be coupled with the processor and store program instructions and/or data necessary for the mobility management network element.
  • the one or more memories may be integrated with the processor, or may be provided separately from the processor. This application is not limited.
  • the device may be located in a mobility management network element, or may be a mobility management network element.
  • the above device includes a transceiver, a processor, and a memory.
  • the processor is used to control the transceiver or the input/output circuit to send and receive signals
  • the memory is used to store a computer program
  • the processor is used to run the computer program in the memory, so that the device executes the first aspect or any one of the first aspect.
  • the method for completing the mobility management network element In the implementation mode, the method for completing the mobility management network element.
  • a computer-readable storage medium for storing a computer program, and the computer program includes instructions for executing the method in the first aspect or any one of the possible implementation manners of the first aspect.
  • a computer program product includes: computer program code, which when the computer program code runs on a computer, causes the computer to execute any one of the first aspect or the first aspect. The method in the possible implementation mode.
  • Figure 1 is an architecture diagram of service capability opening in a 4G network
  • Figure 2 is an architecture diagram of service capability opening in a 5G network
  • Figure 3 is a schematic diagram of a configuration flow of monitoring events in a 4G network
  • Figure 4 is a schematic diagram of a monitoring event reporting process in a 4G network
  • Figure 5 is a schematic diagram of a configuration flow of monitoring events in a 5G network
  • Figure 6 is a schematic diagram of a monitoring event reporting process in a 5G network
  • FIG. 7 is a schematic diagram of a method for monitoring events applicable in an embodiment of this application.
  • FIG. 8 is a schematic diagram of a method for monitoring events applicable in an embodiment of this application.
  • FIG. 9 is a schematic diagram of a monitoring event reporting process in a 4G network applicable in an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of a monitoring event reporting process in a 4G network applicable in an embodiment of the present invention.
  • FIG. 11 is a schematic diagram of a monitoring event reporting process in a 5G network applicable in an embodiment of the present invention.
  • FIG. 12 is a schematic diagram of a monitoring event reporting process in a 5G network applicable in an embodiment of the present invention.
  • FIG. 13 is a structural diagram of a device for monitoring events applicable in an embodiment of this application.
  • the technical solutions of the embodiments of the present application can be applied to various communication systems, such as the fourth generation (4th Generation, 4G), the 4G system includes the long term evolution (LTE) system, and the worldwide interconnection for microwave access (worldwide interoperability).
  • 4G fourth generation
  • LTE long term evolution
  • WiMAX microwave access
  • 5G future 5th Generation
  • NR new-generation radio access technology
  • 6G systems future communication systems, such as 6G systems.
  • the term "exemplary” is used to indicate an example, illustration, or illustration. Any embodiment or design solution described as an "example” in this application should not be construed as being more preferable or advantageous than other embodiments or design solutions. Rather, the term example is used to present the concept in a concrete way.
  • UE User Equipment
  • Mobility management network element the network element responsible for the mobility management of the UE.
  • the mobility management network element includes a mobility management entity (Mobility Management Entity, MME) and a GPRS service support node (Serving GPRS Support Node).
  • MME mobility management entity
  • GPRS service support node Serving GPRS Support Node
  • SGSN mobility management network elements
  • core network access and mobility management function network elements Core Access and Mobility Management Function, AMF).
  • the mobility management network element maintains a corresponding timer for the UE, suppresses sending the location report notification of the corresponding UE before the timer expires, and sends the location report notification of the corresponding UE when the timer expires. Includes the current location information of the UE.
  • the user data management network element is responsible for the management of user data and the minimum reporting interval sent to the mobility management network element.
  • the minimum reporting interval is the minimum time interval between two or more location report notifications.
  • the user data management network element in the middle includes the Home Subscriber Server (HSS), and the user data management network element in the 5G network includes a unified data management node (Unified Data Management, UDM).
  • HSS Home Subscriber Server
  • UDM Unified Data Management
  • the "and/or” in this application describes the association relationship of the associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone. This situation.
  • the character "/" generally indicates that the associated objects are in an "or” relationship.
  • the multiple involved in this application refers to two or more.
  • the service capability server sends an event monitoring request through the open function network element, and the open function network element sends an event monitoring request to the user data management network element after processing.
  • the user data management network element sends an event monitoring request to the mobility management network element after processing, and the mobility management network element processes and monitors the UE, and reports the monitored event report notification to the service capability server through the open function network element.
  • the purpose of event monitoring of the UE by the service capability server is achieved.
  • service capability servers include service capability servers/application servers (Services Capability Server/Application Server, SCS/AS).
  • the open function network elements in the 4G network include service capability exposure function network elements (SCEF), and the open function network elements in the 5G network include network exposure function network elements (Network Exposure Function, NEF).
  • SCEF service capability exposure function network elements
  • NEF Network Exposure Function
  • FIG. 6 is a monitoring event reporting process based on the monitoring event configuration process shown in FIG. 5.
  • the configuration process includes:
  • Step 301 SCS/AS sends a monitoring request message to SCEF.
  • the monitoring request message carries the SCS/AS identifier, T8 destination address, monitoring type (Monitoring Type), and mobile subscriber International ISDN/PSTN number (Mobile Subscriber International ISDN/PSTN number, MSISDN) or external identifier (External Id) or External group ID (External Group Id).
  • the Monitoring Type is configured as Location Reporting.
  • the Monitoring request message also carries the minimum reporting interval (Minimum Reporting Interval, MRI).
  • MRI is used for Indicates the minimum time interval between two or more location report notifications.
  • the MME/SGSN sends a location report notification, the timer is started and the value is MRI. Before the timer expires (that is, when the timer is running), at least one location report notification is suppressed, and the location report notification reported by the MME/SGSN is carried The latest suppressed location report notification, and the timer is restarted for timing.
  • the location information of the UE included in the latest suppressed location report notification can be considered as the current location information of the UE.
  • the MRI setting ensures SCS/
  • the AS can receive the location information of the UE within a certain period of time, determine the location update of the UE, and avoid the impact of the signaling load on the network caused by the frequent location update of the UE triggering the location report notification.
  • the monitoring request message can also carry the accuracy of the UE's location information carried in the location report notification (Accuracy), such as cell level, base station level ((e)NodeB Level), tracking area/routing area level (TA/RA level).
  • Acuracy such as cell level, base station level ((e)NodeB Level), tracking area/routing area level (TA/RA level).
  • the monitoring request message carries the External Group Id. If the monitoring event configuration request is for a single UE, the monitoring request message carries the MSISDN Or External Id.
  • Step 302 The SCEF saves the parameters carried in the received monitoring request message.
  • the SCEF authorizes the configuration request according to the stored local policy. After the authorization is successful, the SCEF assigns the SCEF Reference ID.
  • Step 303 SCEF sends a monitoring request message to HSS.
  • the monitoring request message carries External Id or External Group Id, SCEF identifier, SCEF Reference ID, and Monitoring Type.
  • the Monitoring Type is Location Reporting
  • the monitoring request message also carries MRI.
  • SCEF is mapped to the corresponding internal accuracy (Internal Accuracy) according to the stored operator policy, or when there is no corresponding Internal Accuracy, SCEF configures Internal Accuracy according to the operator policy.
  • Step 304 The HSS checks the received monitoring request message, and after the check is passed, the HSS saves the parameters carried in the received monitoring request message.
  • the HSS determines whether the received monitoring request message carries the External Group Id or the External ID, and determines the group member UE corresponding to the External Group Id or the UE corresponding to the External ID.
  • Step 305 HSS returns a monitoring response to SCEF.
  • the returned monitoring response contains at least the SCEF Reference Id and the acceptance instruction.
  • Step 306 The SCEF returns a monitoring response to the SCS/AS.
  • the monitoring response carries at least a T8 long-term transaction reference identifier TLTRI (T8 Long Term Transaction Reference ID) and an acceptance instruction.
  • TLTRI T8 Long Term Transaction Reference ID
  • the HSS performs steps 307 to 309 for the external Id or MSISDN carried, and if the monitoring request message received by the HSS carries the External Group Id , The HSS performs step 307 to step 309 for each group member UE in the External Group Id carried.
  • Step 307 The HSS sends a user subscription data insertion request message to the MME/SGSN for a group member UE or a UE.
  • the user subscription data insertion request message carries the monitoring type, SCEF identifier, SCEF Reference ID, and Internal Accuracy in the message.
  • the external identifier or MSISDN of the UE, when the Monitoring Type is Location Reporting, the request message for inserting user subscription data also carries MRI.
  • Step 308 The MME/SGSN saves the parameters carried in the received user subscription data insertion request message, and performs corresponding processing.
  • Step 309 The MME/SGSN sends an insert user subscription data response message to the HSS, carrying the above acceptance instruction.
  • the MME/SGSN also carries a monitoring event report in the insert user subscription data response message.
  • the Monitoring Type is Location Reporting
  • the monitoring event report includes at least a location report notification.
  • Step 310 The HSS returns a monitoring response message or a monitoring instruction message to the SCEF.
  • the response message for inserting user subscription data received by the HSS carries a monitoring event report
  • the monitoring response message or monitoring indication message returned by the HSS to the SCEF contains at least the SCEF Reference ID
  • the monitoring event report and monitoring event report correspond to the external identifier or MSISDN of the UE.
  • the monitoring response message or monitoring instruction message from HSS to SCEF contains at least the SCEF Reference ID, acceptance indication and monitoring event report.
  • HSS may aggregate multiple monitoring event reports from MME/SGSN, and then send them to SCEF in one message.
  • Step 311 The SCEF sends a monitoring response message or a monitoring instruction message to the SCS/AS.
  • the monitoring response message or monitoring indication message received by SCEF carries a monitoring event report
  • the monitoring response message or monitoring indication message sent by SCEF to SCS/AS contains at least TLTRI
  • the monitoring event report and monitoring event report correspond to the external group ID or MSISDN of the UE. If the monitoring event request is for a single UE, the monitoring response message or monitoring indication message sent by SCEF to SCS/AS contains at least TLTRI and acceptance indication And monitor event reports.
  • the monitoring response message or monitoring indication message returned by the HSS carries multiple monitoring event reports
  • the monitoring response message or monitoring indication message sent by SCEF to SCS/AS carries TLTRI, (monitoring event report, corresponding to the external group of the UE). ID or MSISDN) correspondence list.
  • Step 312 SCS/AS returns a monitoring indication response message to SCEF.
  • SCS/AS returns a monitoring indication response message for each group member UE.
  • the monitoring event reporting process based on the configuration process of Figure 3 is shown in Figure 4 for details.
  • the monitoring event reporting process includes:
  • Step 401 The MME/SGSN performs event detection according to the parameters of the monitoring event issued in FIG. 3, and starts a timer according to the MRI.
  • the MME/SGSN detects the change in the location of the UE according to Internal Accuracy.
  • the MME/SGSN Before the timer expires, the MME/SGSN suppresses the event report notification corresponding to the detected event, such as Location Change.
  • Step 402 When the timer expires and the MME/SGSN saves at least one suppressed event report notification, the MME/SGSN sends a monitoring indication message to the SCEF, and the monitoring indication message carries at least the SCEF Reference ID and the monitoring event report.
  • the monitoring event report carried in the monitoring indication message is the latest event report notification in the suppressed event report notification list, that is, the event report notification carrying the latest location information of the UE.
  • the monitoring indication information also carries an external identifier or MSISDN.
  • Step 403 The SCEF sends a monitoring indication message to the SCS/AS, and the monitoring indication message carries at least TLTRI and a monitoring event report.
  • the monitoring indication message will at least carry TLTRI, (monitoring event report, corresponding to the external identity of the UE or MSISDN) corresponding List of relations.
  • the monitoring indication information also carries an external identifier or MSISDN.
  • Step 404 SCS/AS returns a monitoring indication response message to SCEF.
  • Figure 5 shows the configuration process of event subscription based on monitoring events in the 5G network.
  • the configuration process includes:
  • Step 501 The SCS/AS sends a Nnef_EventExposure_Subscribe request message to the NEF, that is, a subscription request message.
  • the subscription request message may be equivalent to the monitoring request message shown in FIG. 3 for understanding.
  • the subscription request message carries at least the SCS/AS event notification endpoint, the monitoring event identifier (EventId(s)), the External GroupId or the general public subscription identifier GPSI (Generic Public Subscription Identifier) or the instructions of all UEs. If the subscription is requested The indicated monitoring event includes a location report, and the subscription request message also carries an MRI.
  • the subscription request message carries the External Group Id; if the subscription request is for a single UE, the subscription request message carries GPSI; if the subscription request is for all UEs, the subscription request message carries all UE's instructions.
  • Event Id(s) includes Cell_Change, TAI_Change, CN_Node_Change, etc.
  • Step 502 NEF saves the parameters carried in the received subscription request message. NEF authorizes the configuration request according to the saved local policy.
  • Step 503 NEF sends a Nudm_EventExposure_Subscribe Request message to UDM, and the subscription request message carries External Group Id or GPSI, Event Id(s), NEF event notification endpoint, and MRI.
  • Step 504 UDM checks the monitoring event subscription request message. After the check is passed, UDM saves the parameters carried in the received subscription request message. UDM determines the Internal Group ID corresponding to the External Group ID, and the subscription permanent identifier SUPI (Subscription Permanent Identifier) corresponding to GPSI.
  • SUPI Subscribe Permanent Identifier
  • UDM determines that the subscription request is for a group of UEs
  • UDM performs step 505 with each AMF registered with group members. If UDM determines that the subscription request is for all UEs, UDM performs step 505 with all AMFs. If UDM determines that the subscription request is for a single For the UE, the AMF registered by the UDM with the UE performs step 505.
  • Step 505 The UDM sends a Namf_EventExposure_Subscribe Request message to the AMF.
  • the subscription request message carries the NEF event notification endpoint, Event Id(s), Internal Group Id or SUPI or all UE indications.
  • Step 506 UDM creates an event subscription context according to the subscription request.
  • Step 507 The AMF returns a Namf_EventExposure_Subscribe Response message to the UDM, and the subscription response message carries at least the AMF subscription association identifier and acceptance instruction.
  • Step 508 The UDM creates an event subscription context, and the UDM sends a Ndum_EventExposure_Subscribe Response message to the NEF.
  • the subscription response message carries the UDM subscription association identifier and acceptance indication.
  • Step 509 NEF creates an event subscription context, NEF sends a Nnef_EventExposure_Subscribe Response message to SCS/AS, and the subscription response message carries the NEF subscription association identifier and acceptance indication.
  • the event subscription process includes:
  • Step 601 The AMF performs event detection according to the parameters of the subscription event issued in FIG. 5, and starts a timer according to the MRI.
  • AMF detects location changes according to EventId(s), and detects the corresponding event, namely LocationChange.
  • the AMF suppresses the time report notification corresponding to the detected time, such as Location Change.
  • Step 602 When the timer expires and the AMF saves at least one suppressed event report notification, the AMF sends a Namf_EventExposure_Notify Request message to the NEF.
  • the notification request message carries the SCEF Reference ID and the monitoring event report.
  • the monitoring event report is the latest event report notification in the suppressed event report notification list, that is, the event report notification that carries the latest location information of the UE, such as Cell Id, TAI, etc.
  • the message also carries GPSI.
  • Step 603 NEF returns a confirmation message Nnef_EventExposure_Notify Response, that is, a notification response message.
  • Step 604 NEF sends a Nnef_EventExposure_Notify Request message to SCS/AS, and the notification request message carries the SCS/AS event notification endpoint and monitoring event report.
  • the message sent by NEF to SCS/AS also carries GPSI.
  • Step 605 SCS/AS returns a confirmation message Nnef_EventExposure_Notify Response to NEF, that is, a notification response message.
  • the first mobility management network element maintains the first mobility management network element corresponding to the UE.
  • the current value of a timer is sent to the second mobility management network element as the first duration value, and the second mobility management network element uses the first duration value to set the initial value of the second timer corresponding to the UE maintained by itself Value, so as to ensure that when the second mobility management network element uses the second timer for timing, it continues to time based on the timing of the first mobility management network element, instead of resetting the timer to re-timing.
  • the mobility management network element determines that the second timer expires, it reports the UE's suppressed location report notification, and the time interval between the UE's two location report notifications will not be too long, so that SCS/AS can monitor the UE location in time Update situation.
  • the specific process of monitoring events is described in detail in the following embodiments. First, referring to the process of monitoring events shown in Figure 7, the process includes:
  • Step 701 During the reselection process of the mobility management network element, the first mobility management network element determines a first duration value.
  • the first duration value is the current value of the first timer corresponding to the UE maintained by the first mobility management network element, and the first mobility management network element is before the expiration of the first timer Suppress sending the location report notification of the UE. If the UE moves from the first mobility management network element to the second mobility management network element during the mobility management network element reselection process, in order to monitor the event, before the UE mobility management network element reselection, the first A mobility management network element needs to obtain the monitoring event configuration according to the configuration process shown in Figure 3 or Figure 5 above.
  • the second mobility management network element sends a context request message to the first mobility management network element. If the first mobility management network element receives the context request message sent by the second mobility management network element, it is determined that the UE has reselected the mobility management network element.
  • the first mobility management network element determines that the UE has undergone a renewal of the mobility management network element, it determines the current value of the first timer corresponding to the UE maintained by itself as the first duration value, which can indicate the first duration value.
  • the first mobility management network element may set the first timer corresponding to the UE maintained by itself. This process may be described in the configuration process shown in FIG. 3 or FIG. 5. In the realization.
  • the user data management network element sends the minimum reporting interval MRI, which is the minimum time interval between two or more location report notifications.
  • the sexual management network element receives the MRI, starts the first timer corresponding to the UE, and sets the initial value of the first timer according to the MRI.
  • the initial value of the first timer is set to 0, and the timing threshold is MRI.
  • the initial value of the first timer set is the MRI.
  • the current value of the first timer corresponding to the UE maintained by the mobility management network element itself can be represented by the current maximum reporting interval (CMRI), as maintained by the first mobility management network element itself.
  • the current value of the first timer corresponding to the UE is the first duration value, which can be represented by CMRI1.
  • the first mobility management network element suppresses sending the location report notification of the UE before the first timer corresponding to the UE maintained by itself expires, and sends the suppressed location report notification of the UE when the first timer expires.
  • the first mobility management network element can arbitrarily choose to perform the location report notification of the UE that is suppressed.
  • the reported location report notification of the UE may also send the latest location report notification among the location report notifications of the suppressed UE.
  • the first mobility management network element when the first mobility management network element sends the UE's suppressed location report notification, it restarts the first timer and sets the initial value of the restarted first timer according to MRI.
  • Step 702 The first mobility management network element sends the first duration value to the second mobility management network element.
  • the first mobility management network element may directly send the determined first duration value to the second mobility management network element.
  • the first mobility management network element may carry the determined first duration value in the context response message and send it to the second mobility management Network element.
  • Step 703 The second mobility management network element receives the first duration value sent by the first mobility management network element.
  • the second mobility management network element receives the first duration value directly sent by the first mobility management network element.
  • the second mobility management network element receives the context response message that carries the first duration value and is sent by the first mobility management network element.
  • Step 704 The second mobility management network element starts the second timer corresponding to the UE maintained by the second mobility management network element, and sets the initial value of the second timer according to the first duration value.
  • the second mobility management network element In order to implement the reporting of monitoring events so that the SCS/AS can detect the location information of the UE, the second mobility management network element needs to start the second timer corresponding to the UE maintained by itself for timing.
  • the second mobility management network element When the second mobility management network element starts the second timer corresponding to the UE, it sets the initial value of the second timer according to the received first duration value.
  • the received first duration value is set as the timed initial value of the second timer.
  • the received first duration value is set as the initial value when the second timer counts down.
  • Step 705 The second mobility management network element sends a suppressed location report notification of the UE when the second timer expires.
  • the second mobility management network element refrains from sending the location report information of the UE.
  • the second mobility management network element can arbitrarily select and report from the location report notification of the suppressed UE.
  • the location report notification of the UE may also send the most recent location report notification among the location report notifications of the suppressed UE.
  • the most recent location report notification in the location report notification of the suppressed UE is the latest location report notification in the location report notification of the suppressed UE.
  • the location information of the UE in the latest location report notification can be considered as the current UE Location information.
  • the second mobility management network element resets the second timer corresponding to the UE that it maintains when the second timer expires.
  • the user data management network element sends the minimum report interval MRI, which is the minimum time interval between two or more location report notifications, and the second mobility management network element receives the MRI, and the second timer expires. From time to time, restart the second timer corresponding to the UE, and set the initial value of the second timer according to the MRI.
  • MRI minimum time interval between two or more location report notifications
  • the second mobility management network element receives the MRI, and the second timer expires. From time to time, restart the second timer corresponding to the UE, and set the initial value of the second timer according to the MRI.
  • the initial value of the second timer is set to 0, and the timing threshold is MRI.
  • the initial value of the set second timer is the MRI.
  • the aforementioned first mobility management network element or second mobility management network element is any one of MME, SGSN, and AMF. It should be noted that the first mobility management network element and the second mobility management network element may be mobility management network elements under the same network type, such as the first mobility management network element and the second mobility management network element Both are mobility management network elements under the 4G network, or both are mobility management network elements under the 5G network, the first mobility management network element and the second mobility management network element can also be under different network types
  • the mobility management network element for example, the first mobility management network element is a mobility management network element under a 4G network, and the second mobility management network element is a mobility management network element under a 5G network.
  • the UE undergoes an inter MME/SGSN/AMF movement before the timer expires, and returns to the original MME/SGSN/AMF, that is, during the mobility management network element reselection process, the UE moves from the first The mobility management network element moves to the second mobility management network element. Before the timer expires, the UE moves from the second mobility management network element back to the original first mobility management network element. The location information of the UE reported by the network element for the last time notification has been cleared. At this time, when the timer expires, the first mobility management network element will re-report the location report notification of the UE.
  • the continuously reported location report notification of the UE is the UE If the location information is the same, it is meaningless for the SCS/AS to detect the location update situation of the UE. Instead, signaling is increased and network resources are wasted.
  • the method for monitoring events proposed in this application can also report the location information of the UE last time and the current location information of the detected UE. When they are consistent, the UE location report notification is not reported, thereby saving network resources.
  • the process includes:
  • Step 801 The first mobility management network element sends the most recently reported UE location information to the second mobility management network element.
  • the first timer corresponding to the UE maintained by the first mobility management network element expires, it can send the location report notification that the UE is suppressed, and specifically it can send the location report of the suppressed UE.
  • the most recent location report notification in the notification is the most recent location report notification in the notification.
  • the first mobility management network element sends the most recent position report notification among the location report notifications of the suppressed UE, the first mobility management network element saves the most recent position report after sending the most recent position report notification
  • the location information of the UE in the notification is used as the location of the UE reported last time.
  • the location information of the most recently reported UE is stored in the first mobility management network element, which facilitates the first mobility management network element to send the location information of the most recently reported UE to the second mobility management network element.
  • the first mobility management network element decides whether to report the location report notification of the UE.
  • the most recently reported UE location information saved by the first mobility management network element may be sent to the first mobility management network element when the UE moves from another mobility management network element to the first mobility management network element.
  • the location information of the UE reported last time, among which other mobility management network elements may include the second mobility management network element, which may be set when the first timer before the first timer expires, the first mobility management The location information of the UE in the location report notification sent by the network element.
  • the first mobility management network element When the first mobility management network element has timed out on the first timer corresponding to the UE maintained by the first mobility management network element, the first mobility management network element confirms that the current location information of the UE is different from the stored location information of the most recently reported UE, and sends The UE's suppressed location report notification.
  • the first timer corresponding to the UE maintained by the first mobility management network element expires, it is confirmed that the current location of the UE is the same as the stored location information of the most recently reported UE. , Does not send the UE's location report notification.
  • the first mobility management network element confirms that the current location information of the UE is different from the stored location information of the last reported UE, it generates a location report notification that the UE is suppressed.
  • a mobility management network element confirms that the current location information of the UE is the same as the stored location information of the last reported UE, it does not generate a location report notification that the UE is suppressed.
  • the first mobility management network element sends the location information of the UE in the most recent location report notification as the most recently reported location information of the UE.
  • the first mobility management network element may directly send the most recently reported location information of the UE to the second mobility management network element.
  • the first mobility management network element may carry the most recently reported UE location information in the context response message and send it to the second mobility management network element. Mobility management network element.
  • Step 802 The second mobility management network element receives the most recently reported UE location information sent by the first mobility management network element.
  • the second mobility management network element receives the most recently reported location information of the UE directly sent by the first mobility management network element.
  • the second mobility management network element receives a context response message sent by the first mobility management network element that carries the location information of the UE that was reported last time.
  • Step 803 When the second timer expires, the second mobility management network element confirms that the current location information of the UE is different from the location information of the UE reported last time, and sends a location report notification that the UE is suppressed.
  • the mobility management network element can confirm the location information of the UE within its management range, when the second timer expires, in order to ensure that the SCS/AS can detect the location update of the UE in time, the second mobility management network element Confirm that the current location and information of the UE are different from the location information of the UE reported last time, and send the UE's suppressed location report notification.
  • the second mobility management network element sends the most recent location report notification among the location report notifications of the suppressed UE, the second mobility management network element saves the most recent location after sending the latest location report notification
  • the location information of the UE in the report notification is used as the location information of the UE reported last time.
  • the second mobility management network element does not send when the second timer expires and the current location information of the UE is the same as the location information of the UE reported last time.
  • the location report notification of the UE does not send when the second timer expires and the current location information of the UE is the same as the location information of the UE reported last time.
  • the second mobility management network element may continue to save the location information sent by the first mobility management network element as the location information of the UE last reported.
  • the second mobility management network element confirms that the current location information of the UE is different from the stored location information of the UE last reported, it generates a location report notification that the UE is suppressed. 2.
  • the mobility management network element confirms that the current location information of the UE is the same as the stored location information of the last reported UE, it does not generate a location report notification that the UE is suppressed.
  • the second timer is a timer set according to the first duration value sent by the first mobility management network element
  • the most recently reported location information of the UE stored by the second mobility management network element is the first mobility management network
  • the location information of the UE sent by the element if the second timer is a timer reset by the second mobility management network element after sending the location report notification of the UE, the last reported UE saved by the second mobility management network element
  • the location of is the location information of the UE in the location report notification of the UE sent by the second mobility management network element.
  • Embodiment 1 When this application is applied to a 4G network, it is assumed that when the UE moves from MME/SGSN1 to MME/SGSN2, referring to the monitoring event report process shown in Figure 9, the monitoring event report process includes:
  • Step 901 MME/SGSN1 performs monitoring event configuration according to the configuration process shown in FIG. 3 above.
  • Step 902 The UE moves to the area managed by the MME/SGSN2, and the MME/SGSN2 receives a Tracking Area Update (TAU)/Routing Area Update (RAU) request from the UE.
  • TAU Tracking Area Update
  • RAU Radio Access Area Update
  • Step 903 MME/SGSN2 sends a context request to MME/SGSN1.
  • Step 904 MME/SGSN1 returns a context response message to MME/SGSN2.
  • the context response message carries the SCEF identifier, the SCEF Reference ID, and the current value CMRI1 of the first timer corresponding to the UE. If MME/SGSN1 has sent a location report notification to SCEF, the context response message also includes the location information Last Location Info in the last location report notification.
  • the location information Last Location Info in the last location report notification includes Cell Id, (e)NodeB Id, or TAI, etc.
  • Step 905 MME/SGSN2 returns a confirmation message to MME/SGSN1.
  • Step 906 MME/SGSN2 sends a location update request to HSS.
  • Step 907 HSS sends a location cancellation request to MME/SGSN1.
  • Step 908 MME/SGSN1 returns a response message to the HSS, that is, cancels the location confirmation message.
  • Step 909 HSS returns a location update confirmation message to MME/SGSN2.
  • the updated location confirmation message carries monitoring event configuration information, including at least Monitoring type, SCEF ID, SCEF Reference ID, MRI, Internal Accuracy, external ID or MSISDN.
  • Step 910 MME/SGSN2 performs event detection.
  • MME/SGSN2 performs event monitoring according to the monitoring event parameters carried in the updated location confirmation message issued in step 909, and at the same time starts the second timer corresponding to the UE and sets the initial value of the second timer according to CMRI1.
  • MME/SGSN2 monitors events based on Internal Accuracy and detects location changes.
  • the MME/SGSN2 Before the second timer expires, the MME/SGSN2 suppresses the event report notification corresponding to the detected event (ie, Location Change).
  • Step 911 When the second timer expires and the MME/SGSN2 saves at least one suppressed event report notification, the MME/SGSN2 sends a monitoring instruction to the SCEF.
  • the monitoring instruction carries the SCEF Reference ID and the location report notification.
  • the monitoring event report is the latest event report notification in the suppressed event report notification list, that is, the latest event report notification includes the latest location information of the UE, that is, the current location information of the UE.
  • MME/SGSN2 determines whether a Location Change has occurred according to Last Location Info and the current location information of the UE. If the Last Location Info is different from the current location information of the UE, MME/SGSN2 confirms that a Location Change has occurred, otherwise MME/SGSN2 confirms that no Location Change has occurred.
  • MME/SGSN2 sets the second timer according to CMRI1, for MME/SGSN2, Last Location Info must be different from the UE’s current location information, that is, at this time CellId, (e)NodeBId or TAI/ RAI must have changed. Therefore, in this scenario, when the second timer expires, MME/SGSN2 must send a location report notification.
  • Step 912 SCEF sends a monitoring instruction to SCS/AS.
  • the monitoring instruction carries at least TLTRI and location report notification.
  • the monitoring indication also includes the external identifier or MSISDN.
  • the process of reporting the location report notification of the UE is not performed, assuming that the UE moves from MME/SGSN1 When arriving at MME/SGSN2 and moving from MME/SGSN2 to MME/SGSN1, see the monitoring event report process shown in Figure 10 for details.
  • the process specifically includes:
  • step 1001 to step 1010 is the same as that of step 901 to step 910 shown in FIG. 9 above, and will not be repeated here.
  • Step 1011 The UE moves to the area managed by the MME/SGSN1, and the MME/SGSN1 receives the TAU/RAU request from the UE.
  • Step 1012 MME/SGSN1 sends a context request message to MME/SGSN2.
  • Step 1013 MME/SGSN2 returns a context response message to MME/SGSN1.
  • the context response message carries the SCEF identifier, the SCEF Reference ID, and the current value CMRI2 of the second timer corresponding to the UE.
  • the Last Location Info included in the context response message is the location information in the last monitoring event report reported by MME/SGSN2; otherwise, if MME/SGSN2 receives it from MME/SGSN1 To Last Location Info, the Last Location Info included in the context response message is the Last Location Info sent by MME/SGSN1.
  • Step 1014 MME/SGSN1 returns a confirmation message to MME/SGSN2.
  • Step 1015 MME/SGSN1 sends a location update request to HSS.
  • Step 1016 HSS sends a location cancellation request to MME/SGSN2.
  • Step 1017 MME/SGSN2 returns a response message to the HSS, that is, cancels the location confirmation message.
  • Step 1018 HSS returns a location update location confirmation message to MME/SGSN1.
  • the updated location confirmation message carries monitoring event configuration information, including at least Monitoring type, SCEF ID, SCEF Reference ID, MRI, Internal Accuracy, external ID, or MSISDN.
  • Step 1019 MME/SGSN1 performs event detection.
  • the event monitoring is performed according to the monitoring event parameters carried in the update location confirmation message issued in step 1018, and at the same time, the first timer corresponding to the UE is started and the initial value of the first timer is set according to CMRI2.
  • MME/SGSN1 performs event monitoring based on Internal Accuracy and detects location changes.
  • the MME/SGSN1 suppresses the event report notification corresponding to the detected event (ie, Location Change).
  • Step 1020 When the first timer expires and the MME/SGSN1 saves at least one suppressed event report notification, the MME/SGSN1 sends a monitoring instruction to the SCEF.
  • the monitoring indication carries the SCEF Reference ID, which is the location report notification.
  • the monitoring event report is the latest event report notification in the suppressed event report notification list, that is, the latest event report notification includes the latest location information of the UE, that is, the current location information of the UE.
  • MME/SGSN1 If MME/SGSN1 receives Last Location Info from MME/SGSN2, MME/SGSN1 judges whether a Location Change has occurred according to Last Location Info and the current location of the UE.
  • Last Location Info may carry the location information previously reported by MME/SGSN1 to SCEF, and the UE’s current location information and Last location Info information may be the same, so in this case When the first timer expires, MME/SGSN1 does not send the UE's location report notification.
  • Last Location Info carries the location information reported by MME/SGSN2 to SCEF, the UE’s current location information and Last location Info information are not the same. Therefore, in this case, when the first timer expires, MME/SGSN1 sends UE's location report notification.
  • Step 1021 The SCEF sends a monitoring instruction to the SCS/AS.
  • At least TLTRI and location report notification are carried in the monitoring instruction.
  • the monitoring request is for a group of UEs, it also includes the external identity or MSISDN.
  • Embodiment 2 When this application is applied to a 5G network, it is assumed that when the UE moves from AMF1 to AMF2, referring to the monitoring event reporting process shown in Figure 11, the monitoring time reporting process includes:
  • Step 1101 AMF1 performs monitoring event subscription according to the configuration process shown in FIG. 5 above.
  • Step 1102 The UE moves to the area managed by AMF2, and AMF2 receives the Registration Area update request from the UE, that is, the RAU update request.
  • Step 1103 AMF2 sends a context request message, such as Namf_Communication_UEContextTransfer message, to AMF1.
  • a context request message such as Namf_Communication_UEContextTransfer message
  • Step 1104 AMF 1 returns a context response message to AMF 2, such as Namf_Communication_UEContextTransfer Response message.
  • the context response message carries the context of the event subscription, and the context of the event subscription includes at least Internal Group Id, Event Id(s), NEF event notification endpoint, MRI and the current value of the first timer corresponding to the UE CMRI1. If AMF1 sends a location report to NEF, the context response message also reports the location information Last Location Info in the last monitoring event report.
  • Step 1105 AMF 2 returns a context confirmation message, such as Namf_Communication_RegistrationCompleteNotify message, to AMF 1.
  • a context confirmation message such as Namf_Communication_RegistrationCompleteNotify message
  • Step 1106 AMF2 sends a registration request such as a Nudm_UECM_Registration message to UDM, and UDM returns a response message, or AMF2 sends a request for obtaining UE subscription information such as a Nudm_SDM_GET message to UDM, and UDM returns a response message, or AMF2 sends UDM a notification request for subscription data change Such as Nudm_SDM_Subsribed message, UDM returns a response message.
  • a registration request such as a Nudm_UECM_Registration message
  • AMF2 sends a request for obtaining UE subscription information such as a Nudm_SDM_GET message to UDM, and UDM returns a response message
  • AMF2 sends UDM a notification request for subscription data change
  • UDM returns a response message.
  • Step 1107 UDM sends a deregistration request such as Nudm_UECM_DeregistrationNotify message to AMF1, and AMF1 returns a response message.
  • AMF1 sends to UDM a subscription request to cancel the notification of subscription data change, such as a Nudm_SDM_Unsubsribe message, and UDM returns a response message.
  • Step 1108 AMF2 performs event detection, for example, performs event monitoring according to the event subscription parameters carried in the context response message obtained in step 1104, and starts a second timer corresponding to the UE and sets the initial value of the second timer according to CMRI1.
  • MME/SGSN2 monitors events based on Event ID and detects location changes.
  • the AMF 2 Before the second timer expires, the AMF 2 suppresses the event report notification corresponding to the detected event (ie, Location Change).
  • Step 1109 When the second timer expires and AMF 2 saves at least one suppressed event report notification, AMF 2 sends a monitoring indication to NEF, such as Namf_EventExposure_Notify Request message, and NEF returns a response message, such as Namf_EventExposure_Notify Response message.
  • NEF such as Namf_EventExposure_Notify Request message
  • the monitoring instructions carry NEF event notification endpoints and monitoring event reports.
  • the monitoring event report is the latest event report notification in the suppressed event report notification list, that is, the latest event report notification includes the latest location information of the UE, that is, the current location information of the UE.
  • AMF 2 determines whether a Location Change has occurred based on Last Location Info and the current location information of the UE.
  • AMF 2 sets the second timer according to CMRI1, for AMF 2, Last Location Info must be different from the UE's current location information, that is, at this time, the Cell Id, NgNodeB Id or RAI must have changed, so In this scenario, when the second timer expires, AMF 2 will definitely send an event report notification.
  • Step 1110 NEF sends a monitoring instruction to SCS/AS, such as Namf_EventExposure_Notify Request message, and SCS/AS returns a response message, such as Namf_EventExposure_Notify Response message.
  • SCS/AS sends a monitoring instruction to SCS/AS, such as Namf_EventExposure_Notify Request message
  • SCS/AS returns a response message, such as Namf_EventExposure_Notify Response message.
  • the monitoring instruction carries at least the SCS/AS event notification endpoint and the location report notification.
  • GPSI is also included.
  • step 1201 to step 1208 is the same as step 1101 to step 1108 shown in FIG. 11, and the details are not repeated here.
  • Step 1209 The UE moves to the area managed by AMF1, and AMF1 receives the Registration Area update request from the UE, that is, the RAU update request.
  • Step 1210 AMF1 sends a context request message to AMF2, such as Namf_Communication_UEContextTransfer message.
  • Step 1211 AMF 2 returns a context response message to AMF 1, such as Namf_Communication_UEContextTransfer Response message.
  • the context query response message carries the context of the event subscription, where the context of the event subscription includes at least Internal Group Id, Event Id(s), NEF event notification endpoint, MRI, and the current value of the second timer CMRI2 corresponding to the UE.
  • the Last Location Info included in the context response message is the location information in the last monitoring event report of AMF2; otherwise, if AMF2 receives Last Location Info from AMF1, the context response The Last Location Info included in the message is the Last Location Info sent by AMF1.
  • Step 1212 AMF 1 returns a context confirmation message to AMF 2, such as Namf_Communication_RegistrationCompleteNotify message.
  • Step 1213 AMF1 sends a registration request such as a Nudm_UECM_Registration message to UDM, and UDM returns a response message, or AMF1 sends a request for obtaining UE subscription information such as a Nudm_SDM_GET message to UDM, and UDM returns a response message, or AMF1 sends a notification request for subscription data change to UDM Such as Nudm_SDM_Subsribed message, UDM returns a response message.
  • a registration request such as a Nudm_UECM_Registration message
  • AMF1 sends a request for obtaining UE subscription information such as a Nudm_SDM_GET message to UDM, and UDM returns a response message
  • AMF1 sends a notification request for subscription data change to UDM Such as Nudm_SDM_Subsribed message, UDM returns a response message.
  • Step 1214 UDM sends a deregistration request such as Nudm_UECM_DeregistrationNotify message to AMF2, and AMF2 returns a response message, or AMF2 sends a subscription request for canceling subscription data change notification such as Nudm_SDM_Unsubsribe message to UDM, and UDM returns a response message.
  • a deregistration request such as Nudm_UECM_DeregistrationNotify message
  • AMF2 returns a response message
  • AMF2 sends a subscription request for canceling subscription data change notification such as Nudm_SDM_Unsubsribe message to UDM, and UDM returns a response message.
  • Step 1215 AMF1 performs event detection according to the event subscription parameters carried in the context response message obtained in step 1211, starts the first timer corresponding to the UE, and sets the initial value of the first timer according to CMRI2.
  • AMF performs event detection based on Event ID and detects location changes.
  • the AMF1 Before the first timer expires, the AMF1 suppresses the event report notification corresponding to the detected event (ie, Location Change).
  • Step 1216 When the timer expires and AMF 1 saves at least one suppressed event report notification, AMF 1 sends a monitoring indication to NEF, such as Namf_EventExposure_Notify Request message, and NEF returns a response message, such as Namf_EventExposure_Notify Response message.
  • NEF such as Namf_EventExposure_Notify Request message
  • the monitoring instructions carry NEF event notification endpoints and monitoring event reports.
  • the monitoring event report is the latest event report notification in the suppressed event report notification list, that is, the latest event report notification includes the latest location information of the UE, that is, the current location information of the UE.
  • AMF1 determines whether a Location Change has occurred according to Last Location Info and the current location information of the UE.
  • the Last Location Info may be the location information that AMF 1 previously reported to the SCEF. Therefore, the UE’s current location information and Last location Info information may be the same. Therefore, in this case, when When the first timer expires, AMF 1 does not send the UE's location report notification.
  • Last Location Info carries the location information reported by AMF2 to NEF, the current location information of the UE is different from the Last Location Info information. Therefore, in this case, when the first timer expires, AMF1 sends the UE's location report notification .
  • Step 1217 NEF sends a monitoring instruction to the SCS/AS, such as Namf_EventExposure_Notify Request message, and NEF returns a response message, such as Namf_EventExposure_Notify Response message.
  • a monitoring instruction such as Namf_EventExposure_Notify Request message
  • NEF returns a response message, such as Namf_EventExposure_Notify Response message.
  • the monitoring instruction carries at least the SCS/AS event notification endpoint and the location report notification.
  • GPSI is also included.
  • the process of the UE moving from the MME/SGSN of the 4G network to the AMF of the 5G network is similar, and will not be repeated.
  • the method for monitoring events in the embodiments of the present application is described in detail above with reference to FIGS. 7 to 12. Based on the same inventive concept as the above method for monitoring events, as shown in FIG. 13, an embodiment of the present application also provides a method for monitoring events.
  • the apparatus 1300 may be used to implement the method described in the above method embodiment applied to a mobility management network element. For details, refer to the description in the above method embodiment, where the mobility management network element includes a first mobility management network element or a second mobility management network element. 2.
  • Mobility management network element The apparatus 1300 may be in a mobility management network element or a mobility management network element.
  • the apparatus 1300 includes one or more processors 1301.
  • the processor 1301 may be a general-purpose processor or a special-purpose processor. For example, it can be a baseband processor or a central processing unit.
  • the baseband processor can be used to process communication protocols and communication data
  • the central processor can be used to control communication devices (such as base stations, terminals, or chips, etc.), execute software programs, and process software program data.
  • the communication device may include a transceiving unit to implement signal input (reception) and output (transmission).
  • the transceiver unit may be a transceiver, a radio frequency chip, or the like.
  • the apparatus 1300 includes one or more processors 1301, and the one or more processors 1301 can implement the method for mobility management network elements in the above-mentioned embodiment.
  • processor 1301 may also implement other functions in addition to implementing the methods in the above-mentioned embodiments.
  • the processor 1301 may execute instructions to cause the apparatus 1300 to execute the method described in the foregoing method embodiment.
  • the instructions may be stored in whole or in part in the processor, such as instruction 1303, or may be stored in whole or in part in the memory 1302 coupled with the processor, such as instruction 1304, or through instructions 1303 and 1304.
  • the apparatus 1300 executes the method described in the foregoing method embodiment.
  • the communication device 1300 may also include a circuit, and the circuit may implement the function of the mobility management network element in the foregoing method embodiment.
  • the device 1300 may include one or more memories 1302, on which instructions 1304 are stored, and the instructions may be executed on the processor, so that the device 1300 executes the above method The method described in the examples.
  • data may also be stored in the memory.
  • the optional processor may also store instructions and/or data.
  • the one or more memories 1302 may store the corresponding relationship described in the foregoing embodiment, or related parameters or tables involved in the foregoing embodiment.
  • the processor and memory can be provided separately or integrated together.
  • the device 1300 may further include a transceiver unit 1305 and an antenna 1306.
  • the processor 1301 may be called a processing unit, and controls a device (terminal or base station).
  • the transceiver unit 1305 may be called a transceiver, a transceiver circuit, or a transceiver, etc., and is used to implement the transceiver function of the device through the antenna 1306.
  • the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the aforementioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC application specific integrated circuit
  • FPGA ready-made programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • Synchlink DRAM SLDRAM
  • DR RAM Direct Rambus RAM
  • the embodiment of the present application also provides a computer-readable medium on which a computer program is stored.
  • the computer program is executed by a computer, the method for monitoring events described in any of the above-mentioned method embodiments applied to a mobility management network element is implemented .
  • the embodiment of the present application also provides a computer program product that, when executed by a computer, implements the method of monitoring events described in any of the above-mentioned method embodiments applied to a mobility management network element.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a high-density digital video disc (Digital Video Disc, DVD)), or a semiconductor medium (for example, a solid state disk (Solid State Disk, SSD)) etc.
  • An embodiment of the present application also provides a processing device, including a processor and an interface; the processor is configured to execute the method for monitoring events described in any of the above-mentioned method embodiments applied to a mobility management network element.
  • the foregoing processing device may be a chip, and the processor may be implemented by hardware or software.
  • the processor When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software, At this time, the processor may be a general-purpose processor, which is implemented by reading the software code stored in the memory, and the memory may be integrated in the processor, may be located outside the processor, and exist independently.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or integrated. To another system, or some features can be ignored, or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may also be electrical, mechanical or other forms of connection.
  • the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments of the present application.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • Computer-readable media include computer storage media and communication media, where communication media includes any media that facilitates the transfer of computer programs from one place to another.
  • the storage medium may be any available medium that can be accessed by a computer.
  • computer readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or can be used to carry or store instructions or data structures
  • Any connection can suitably become a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave
  • coaxial cable , Fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, wireless and microwave are included in the fixing of the media.
  • Disk and disc include compact discs (CD), laser discs, optical discs, digital versatile discs (DVD), floppy discs and Blu-ray discs. Disks usually copy data magnetically, while discs The laser is used to optically copy data. The above combination should also be included in the protection scope of the computer-readable medium.

Landscapes

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

Abstract

本申请提供一种监控事件的方法及装置，用以保证业务能力服务器SCS/应用服务器AS能够及时监控到用户设备UE的位置更新情况，该监控事件的方法为：在移动性管理网元重选过程中，第二移动性管理网元接收第一移动性管理网元发送的第一时长值，所述第一时长值是所述第一移动性管理网元维护的UE对应的第一定时器的当前值，所述第一移动性管理网元在所述第一定时器计时超时前抑制发送所述UE的位置报告通知；所述第二移动性管理网元启动自身维护的所述UE对应的第二定时器，并根据所述第一时长值，设置所述第二定时器的初始值；所述第二移动性管理网元在所述第二定时器计时超时时，发送所述UE被抑制的位置报告通知。

Description

一种监控事件的方法及装置
相关申请的交叉引用
本申请要求在2019年02月19日提交中国专利局、申请号为201910124749.X、申请名称为“一种监控事件的方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及无线通信技术领域，尤其涉及一种监控事件的方法及装置。
背景技术
第三代合作伙伴项目(3rd generation partnership project，3GPP)定义了能够应用于4G和5G网络的业务能力开放(service capability exposure，SCE)架构。图1为4G网络中的业务能力开放的架构图，基于该架构，3GPP网络能够安全地向第三方的业务提供者业务能力服务器/应用服务器(Services Capability Server/Application Server，SCS/AS)提供业务能力。业务能力开放功能网元(Service Capability Exposure Function，SCEF)为该架构中的核心网元，使得3GPP网络能够安全地向第三方的业务提供者SCS/AS提供业务能力。家乡用户服务器(Home Subscriber Server，HSS)为归属用户签约服务器，保存用户的签约信息。移动性管理实体(Mobility Management Entity，MME)和GPRS服务支持节点(Serving GPRS Support Node，SGSN)为负责对用户设备(User Equipment，UE)进行移动性管理的网元。SCS/AS通过T8的应用程序编程接口(Application Programming Interface，API)接口调用SCEF提供的业务能力。图2为5G网络中的业务能力开放的架构图，5G系统是基于服务化的架构，网络开放功能网元(Network Exposure Function，NEF)起到与4G网络中SCEF类似的功能，通过Nnef接口向SCS/AS开发3GPP网络支持的业务和能力，其中Nnef接口为NEF展现的基于服务的接口，统一数据管理节点(Unified Data Management，UDM)起到与4G网络中HSS类似的功能，通过Nudm接口向NEF提供支持的业务能力，其中Nudm接口为UDM展现的基于服务的接口，核心网接入和移动性管理功能网元(Core Access and Mobility Management Function，AMF)起到与4G网络中MME的功能，通过Namf接口向NEF提供支持的业务和能力，其中Namf接口为AMF展现的基于服务的接口。
在上述业务能力开放的架构下，支持SCS/AS对于UE的事件监控(Event Monitoring)。可以对UE进行多种事件的监控，例如位置报告Location Reporting等。
在位置报告事件的监控中，SCS/AS向SCEF/NEF发送监控请求消息，监控请求消息指示了待监控的UE以及最小报告间隔(Minimum Reporting Interval，MRI)，该MRI用于指示位置报告指示之间的最小时间间隔。如果MRI提供给了MME/SGSN/AMF，MME/SGSN/AMF根据HHS/UDM下发的监控事件参数进行事件监控，并启动定时器，取值为MRI，在定时器过期前，即定时器正在运行的时间未超过MRI，MME/SGSN/AMF将检测到的UE位置的位置报告通知抑制，当定时器过期时，即定时器运行的时间达到MRI时，MME/SGSN/AMF发送最新被抑制的位置报告通知。
UE发生了inter MME/SGSN/AMF的移动时，UE移动到的新的MME/SGSN/AMF会 根据MRI重新设置定时器，因此可能导致UE两次位置报告通知的时间间隔超过MRI，并且在极端情况下，UE多次发生位置改变，并且相邻两次位置改变的时间间隔均不超过MRI，此时MME/SGSN/AMF一直不会发送位置报告通知，使得SCS/AS无法及时监控到UE的位置更新情况。
发明内容
本申请实施例提供一种监控事件的方法及装置，从而避免现有UE两次位置报告通知的时间间隔过长，保证SCS/AS能够及时监控到UE的位置更新情况。
第一方面，提供了一种监控事件的方法，包括如下过程：
在移动性管理网元重选过程中，第一移动性管理网元确定第一时长值；向第二移动性管理网元发送所述第一时长值，所述第一时长值为所述第一移动性管理网元维护的用户设备UE对应的第一定时器的当前值，所述第一移动性管理网元通常在所述第一定时器计时超时前抑制发送所述UE的位置报告通知；
第二移动性管理网元接收第一移动性管理网元发送的第一时长值，启动自身维护的所述UE对应的第二定时器，并根据所述第一时长值，设置所述第二定时器的初始值；所述第二移动性管理网元在所述第二定时器计时超时时，发送所述UE被抑制的位置报告通知。
在移动性管理网元重选过程中，假设UE从第一移动性管理网元移动到了第二移动性管理网元，第一移动性管理网元将自身维护的该UE对应的第一定时器的当前值作为第一时长值发送给第二移动性管理网元，该第二移动性管理网元将该第一时长值，设置自身维护的该UE对应的第二定时器的初始值，从而保证第二移动性管理网元在第一移动性管理网元已计时的基础上继续进行计时，而非重新设置定时器重新计时，当第二移动性管理网元确定第二定时器超时时，将该UE被抑制的位置报告通知进行上报，UE两次位置报告通知的时间间隔不会过长，可以保证SCS/AS能够及时监控到UE的位置更新情况。
在一种可能的实现中，在所述第二定时器计时超时前，所述第二移动性管理网元可以抑制发送所述UE的位置报告通知。在第二定时器计时超时前，UE的位置报告通知被抑制，从而可以避免UE的位置更新频繁发生时，如果频繁触发位置报告通知导致的信令负荷对网络的冲击。
在一种可能的实现中，当在所述第二定时器计时超时时，若至少存在一个被抑制的所述UE的位置报告通知，则所述第二移动性管理网元可以发送被抑制的所述UE的位置报告通知中最近的一个位置报告通知。第二移动性管理网元在第二定时器计时超时时，将被抑制的UE的位置报告通知中最近的一个位置报告通知进行上报，可以保证SCS/AS检测到的UE的位置信息为UE的当前位置信息，并且可以保证SCS/AS监控到的UE的位置更新情况的准确性。
在一种可能的实现中，在所述第一移动性管理网元确定第一时长值之前，所述第一移动性管理网元还可以接收用户数据管理网元发送的最小报告间隔，所述最小报告间隔为两个或多个位置报告通知之间的最小时间间隔；所述第一移动性管理网元启动所述第一定时器，并根据所述最小报告间隔设置所述第一定时器的初始值。第一移动性管理网元作为UE移动前的移动性管理网元，在设置UE对应的第一定时器时，可以是根据用户数据管理网元发送的最小报告间隔进行设置。
在一种可能的实现中，在所述第一定时器计时超时前，所述第一移动性管理网元还可 以抑制所述UE的位置报告通知。同样地，在第一定时器计时超时前，UE的位置报告通知被抑制，可以避免UE的位置更新频繁发生时，如果频繁触发位置报告通知导致的信令负荷对网络的冲击。
在一种可能的实现中，在所述第一定时器计时超时时，所述第一移动性管理网元还可以发送所述UE的位置报告通知。
在一种可能的实现中，当所述第一定时器计时超时时，若至少存在一个被抑制的所述UE的位置报告通知，则所述第一移动性管理网元还可以发送被抑制的所述UE的位置报告通知中最近的一个位置报告通知，并重启所述第一定时器且根据所述最小报告间隔设置初始值。
在第一定时器计时超时时，将被抑制的UE的位置报告通知中最近的一个位置报告通知，可以保证SCS/AS检测到的UE的位置信息为UE的当前位置信息，并且重启并重新设置第一定时器继续进行事件的监控，在重新设置的第一定时器计时超时时，能够继续进行UE的位置报告通知的上报。
在一种可能的实现中，所述第一移动性管理网元发送被抑制的所述UE的位置报告通知中最近的一个位置报告通知之后，所述第一移动性管理网元还可以保存所述最近的一个位置报告通知中的所述UE的位置信息作为最近一次报告的所述UE的位置信息。
在一种可能的实现中，所述第一移动性管理网元还可以向所述第二移动性管理网元发送所述最近一次报告的所述UE的位置信息；所述第二移动性管理网元接收所述第一移动性管理网元发送的所述第一移动性管理网元保存的最近一次报告的所述UE的位置信息。通过将最近一次报告的UE的位置信息进行保存和/或发送，移动性管理网元可以获知到最近一次报告UE的位置信息。
在一种可能的实现中，所述第二移动性管理网元还可以确认所述UE的当前位置信息与所述最近一次报告的所述UE的位置信息不同时，再发送所述UE被抑制的位置报告通知之前。或者所述第一移动性管理网元还可以确认所述UE的当前位置信息与所述最近一次报告的所述UE的位置信息不同时，所述第一移动性管理网元再发送所述UE被抑制的位置报告通知之前。
在定时器计时超时时，移动性管理网元确认UE的当前位置信息与最近一次报告的UE的位置信息不同时，发送UE被抑制的位置报告通知，可以保证SCS/AS能够及时获知到UE的位置更新情况。
在一种可能的实现中，所述第二移动性管理网元在所述第二定时器计时超时时，且所述UE的当前位置信息与所述最近一次报告的所述UE的位置信息相同，还可以不发送所述UE的位置报告通知。
所述第一移动性管理网元在所述第一定时器计时超时时，且所述UE的当前位置信息与所述最近一次报告的所述UE的位置信息相同，还可以不发送所述UE的位置报告通知。
在定时器计时超时时，移动性管理网元确认UE的当前位置信息与最近一次报告的UE的位置信息相同时，如果不发送UE的位置报告通知，避免了在UE的当前位置信息与最近一次报告的UE的位置信息相同时，向SCS/AS发送相同的没有意义的位置报告通知，从而可以节省网络资源。
在一种可能的实现中，在所述第二定时器计时超时前，所述第二移动性管理网元确认所述UE的当前位置信息与所述最近一次报告的所述UE的当前位置不同时，还可以生成 所述UE被抑制的位置报告通知。
在所述第一定时器计时超时前，所述第一移动性管理网元确认所述UE的当前位置信息与所述最近一次报告的所述UE的当前位置不同时，还可以生成所述UE被抑制的位置报告通知。
在定时器计时超时前，移动性管理网元在UE的当前位置信息与最近一次报告的UE的当前位置不同时，生成UE的位置报告通知，能够保证SCS/AS能够及时获知到UE的位置更新情况，在UE的当前位置信息与最近一次报告的UE的当前位置相同时，抑制UE的位置报告通知的生成，还可以节省移动性管理网元的处理资源。
在一种可能的实现中，所述第二移动性管理网元还可以接收用户数据管理网元发送最小报告间隔，所述最小报告间隔为两个或多个位置报告通知之间的最小时间间隔；在所述第二定时器计时超时时，所述第二移动性管理网元重启所述第二定时器，并根据所述最小报告间隔，设置所述第二定时器的初始值。
在第二定时器超时时，第二移动性管理网元还可以根据用户数据管理网元发送的最小报告间隔，启动并重启第二定时器继续进行事件的监控，在重新设置的第二定时器计时超时时，能够继续进行UE的位置报告通知的上报。
在一种可能的实现中，所述第二移动性管理网元发送被抑制的所述UE的位置报告通知中最近的一个位置报告通知之后，所述第二移动性管理网元还可以保存所述最近的一个位置报告通知中的所述UE的位置信息作为最近一次报告的所述UE的位置信息。
在一种可能的实现中，所述第二移动性管理网元或第一移动性管理网元为MME、SGSN、及AMF中的任意一种。
第二方面，提供了一种监控事件的装置。本申请提供的装置具有实现上述方法方面移动性管理网元行为的功能，其包括用于执行上述方法方面所描述的步骤或功能相对应的部件(means)。所述步骤或功能可以通过软件实现，或硬件(如电路)实现，或者通过硬件和软件结合来实现。其中移动性管理网元包括第一移动性管理网元和/或第二移动性管理网元。
在一种可能的设计中，上述装置包括一个或多个处理器和通信单元。所述一个或多个处理器被配置为支持所述装置执行上述方法中移动性管理网元相应的功能。
可选的，所述装置还可以包括一个或多个存储器，所述存储器用于与处理器耦合，其保存装置必要的程序指令和/或数据。所述一个或多个存储器可以和处理器集成在一起，也可以与处理器分离设置。本申请并不限定。
另一个可能的设计中，上述装置，包括收发器、处理器和存储器。该处理器用于控制收发器或输入/输出电路收发信号，该存储器用于存储计算机程序，该处理器用于运行该存储器中的计算机程序，使得该装置执行第一方面或第一方面中任一种可能实现方式中移动性管理网元完成的方法。
在一种可能的设计中，上述装置包括一个或多个处理器和通信单元。所述一个或多个处理器被配置为支持所述装置执行上述方法中移动性管理网元相应的功能。
可选的，所述装置还可以包括一个或多个存储器，所述存储器用于与处理器耦合，其保存移动性管理网元必要的程序指令和/或数据。所述一个或多个存储器可以和处理器集成在一起，也可以与处理器分离设置。本申请并不限定。
所述装置可以位于移动性管理网元中，或为移动性管理网元。
另一个可能的设计中，上述装置，包括收发器、处理器和存储器。该处理器用于控制收发器或输入/输出电路收发信号，该存储器用于存储计算机程序，该处理器用于运行存储器中的计算机程序，使得该装置执行第一方面或第一方面中任一种可能实现方式中移动性管理网元完成的方法。
第三方面，提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序包括用于执行第一方面或第一方面中任一种可能实现方式中的方法的指令。
第四方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述第一方面或第一方面中任一种可能实现方式中的方法。
附图说明
图1为一种4G网络中的业务能力开放的架构图；
图2为一种5G网络中的业务能力开放的架构图；
图3为一种4G网络中监控事件的配置流程示意图；
图4为一种4G网络中的监控事件报告流程示意图；
图5为一种5G网络中监控事件的配置流程示意图；
图6为一种5G网络中的监控事件报告流程示意图；
图7为本申请实施例中适用的一种监控事件的方法示意图；
图8为本申请实施例中适用的一种监控事件的方法示意图；
图9为本发明实施例中适用的一种4G网络中监控事件报告流程示意图；
图10为本发明实施例中适用的一种4G网络中监控事件报告流程示意图；
图11为本发明实施例中适用的一种5G网络中监控事件报告流程示意图；
图12为本发明实施例中适用的一种5G网络中监控事件报告流程示意图；
图13为本申请实施例中适用的一种监控事件的装置结构图。
具体实施方式
下面将结合附图对本发明作进一步地详细描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：第四代(4th Generation，4G)，4G系统包括系统长期演进(long term evolution，LTE)系统，全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统，未来的第五代(5th Generation，5G)系统，如新一代无线接入技术(new radio access technology，NR)，及未来的通信系统，如6G系统等。
本申请将围绕可包括多个设备、组件、模块等的系统来呈现各个方面、实施例或特征。应当理解和明白的是，各个系统可以包括另外的设备、组件、模块等，并且/或者可以并不包括结合附图讨论的所有设备、组件、模块等。此外，还可以使用这些方案的组合。
另外，在本申请实施例中，“示例的”一词用于表示作例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用示例的一词旨在以具体方式呈现概念。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的 技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
以下对本申请实施例的部分用语进行解释说明，以便于本领域技术人员理解。
1)、用户设备(User Equipment，UE)，能够连接到互联网中的电子设备。
2)、移动性管理网元，负责对UE进行移动性管理的网元，在4G网络中移动性管理网元包括移动性管理实体(Mobility Management Entity，MME)和GPRS服务支持节点(Serving GPRS Support Node，SGSN)，在5G网络中移动性管理网元包括核心网接入和移动性管理功能网元(Core Access and Mobility Management Function，AMF)。
3)、定时器，移动性管理网元为UE维护有对应的定时器，在定时器超时前抑制发送对应UE的位置报告通知，在定时器超期时发送对应UE的位置报告通知，位置报告通知中包括UE当前的位置信息。
4)、用户数据管理网元，负责对用户数据进行管理，以及向移动性管理网元发送最小报告间隔，最小报告间隔为两个或多个位置报告通知之间的最小时间间隔，在4G网络中用户数据管理网元包括家乡用户服务器(Home Subscriber Server，HSS)，在5G网络中用户数据管理网元包括统一数据管理节点(Unified Data Management，UDM)。
本申请中的“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
本申请中所涉及的多个，是指两个或两个以上。
另外，需要理解的是，在本申请的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。
为了便于理解本申请实施例，首先先对本申请使用的应用场景进行说明，业务能力服务器通过开放功能网元发送事件监控请求，开放功能网元进行处理后向用户数据管理网元发送事件监控请求，用户数据管理网元进行处理后向移动性管理网元发送事件监控请求，移动性管理网元进行处理并对UE进行监控，将监控到的事件报告通知通过开放功能网元上报给业务能力服务器，进而达到业务能力服务器对UE进行事件监控的目的。
在4G和5G网络中业务能力服务器包括业务能力服务器/应用服务器(Services Capability Server/Application Server，SCS/AS)。在4G网络中开放功能网元包括业务能力开放功能网元(Service Capability Exposure Function，SCEF)，在5G网络中开放功能网元包括网络开放功能网元(Network Exposure Function，NEF)。
为了便于理解本申请实施例，继续以图3所示的监控事件的配置流程示意图，及图4所示的配置后的监控事件报告流程示意图为例，详细说明本申请在4G网络下的应用场景，并以图5所示的监控事件的配置流程示意图，及图6所示的配置后的监控事件报告流程示意图为例，详细说明本申请在5G网络下的应用场景，其中图3和图4所示的流程基于图1所示的架构实现，图4为基于图3所示的监控事件的配置流程后的监控事件报告流程，图5和图6所示的流程基于图2所示的架构实现，图6为基于图5所示的监控事件的配置流程后的监控事件报告流程。
首先参见图3所示的4G网络中监控事件的配置过程，该配置过程包括：
步骤301：SCS/AS向SCEF发送监控请求消息。
该监控请求消息中携带有SCS/AS标识、T8目的地址、监控类型(Monitoring Type)、及移动用户国际ISDN/PSTN号码(Mobile Subscriber International ISDN/PSTN number，MSISDN)或外部标识(External Id)或外部组标识(External Group Id)。
如果SCS/AS请求监控UE的位置信息，则该Monitoring Type被配置为Location Reporting，当Monitoring Type为Location Reporting时，监控请求消息中还携带有最小报告间隔(Minimum Reporting Interval，MRI)，MRI用于指示两个或多个位置报告通知之间的最小时间间隔。MME/SGSN发送位置报告通知时，启动定时器，取值为MRI，在定时器超期前(即定时器运行时)，至少有一个位置报告通知被抑制，MME/SGSN上报的位置报告通知中携带最新的被抑制的位置报告通知，同时重新启动定时器进行计时，该最新的被抑制的位置报告通知中包括的UE的位置信息可以认为是UE当前的位置信息，该MRI的设置保证了SCS/AS能够在一定时间内收到UE的位置信息，确定UE的位置更新，又避免了UE频繁的位置更新均触发位置报告通知时导致的信令负荷对网络的冲击。
如果该Monitoring Type被配置为Location Reporting，监控请求消息中还可以携带有位置报告通知中携带的UE的位置信息的精度(Accuracy)，具体如小区级别(Cell level)，基站级别((e)NodeB Level)，跟踪区/路由区级别(TA/RA level)。
若监控事件配置请求针对的是一组UE，即针对一组UE进行事件监控时，该监控请求消息中携带External Group Id，若监控事件配置请求针对的单个UE，则该监控请求消息中携带MSISDN或External Id。
步骤302：SCEF将接收到的监控请求消息中携带的参数进行保存。SCEF根据保存的本地策略对配置请求进行授权，在授权成功后，SCEF分配SCEF Reference ID。
步骤303：SCEF向HSS发送监控请求消息。
该监控请求消息中携带External Id或External Group Id、SCEF标识、SCEF Reference ID及Monitoring Type，当Monitoring Type为Location Reporting时，该监控请求消息中还携带有MRI。
若SCS/AS提供了Accuracy，则SCEF根据保存的运营商策略映射到对应的内部精度(Internal Accuracy)，或者在没有对应的Internal Accuracy时，SCEF根据运营商策略配置Internal Accuracy。
步骤304：HSS检查接收到的监控请求消息，在检查通过后，HSS将接收到的监控请求消息中携带的参数进行保存。HSS确定接收到的监控请求消息携带的是External Group Id还是External ID，并确定External Group Id对应的组成员UE或者是确定External ID对应的UE。
步骤305：HSS向SCEF返回监控应答。
若HSS确定接收到的监控请求消息中携带的是External Group Id，则返回的监控应答中至少携带有SCEF Reference Id和接受指示。
步骤306：SCEF向SCS/AS返回监控应答，该监控应答中至少携带有T8长期事务参考标识TLTRI(T8 Long Term Transaction Reference ID)和接受指示。
若HSS接收到的监控请求消息中携带的是External Id或MSISDN，则HSS针对携带的该一个External Id或MSISDN执行步骤307至步骤309，若HSS接收到的监控请求消息中携带的是External Group Id，HSS针对携带的该External Group Id中的每一个组成员UE执行步骤307至步骤309。
步骤307：HSS为一个组成员UE或一个UE向MME/SGSN发送插入用户签约数据请求消息，该插入用户签约数据请求消息中携带有消息中携带Monitoring type，SCEF标识、SCEF Reference ID、Internal Accuracy，UE的外部标识或MSISDN，当Monitoring Type为Location Reporting时，该插入用户签约数据请求消息中还携带有MRI。
步骤308：MME/SGSN将接收到的插入用户签约数据请求消息中携带的参数进行保存，并进行相应的处理。
步骤309：MME/SGSN向HSS发送插入用户签约数据应答消息，携带上述接受指示。
若MME/SGSN保存有已有请求的监控事件，则MME/SGSN在该插入用户签约数据应答消息中还携带有监控事件报告，当Monitoring Type为Location Reporting时，监控事件报告至少包括位置报告通知。
步骤310：HSS向SCEF返回监控应答消息或监控指示消息。
若HSS接收到的插入用户签约数据应答消息中携带有监控事件报告，若监控事件请求是针对一组UE的，则HSS向SCEF返回的监控应答消息或监控指示消息中至少携带有SCEF Reference ID、监控事件报告和监控事件报告对应UE的外部标识或MSISDN，若监控事件请求是针对单个UE的，则HSS向SCEF的监控应答消息或监控指示消息中至少携带有SCEF Reference ID、接受指示和监控事件报告。
HSS可能会汇聚多个来自MME/SGSN的监控事件报告，然后在一条消息发送给SCEF。
步骤311：SCEF向SCS/AS发送监控应答消息或监控指示消息。
若SCEF接收到的监控应答消息或监控指示消息中携带了监控事件报告，若监控事件请求是针对一组UE的，则SCEF向SCS/AS发送的监控应答消息或监控指示消息中至少携带有TLTRI、监控事件报告和监控事件报告对应UE的外部组标识或MSISDN，若监控事件请求是针对单个UE的，则SCEF向SCS/AS发送的监控应答消息或监控指示消息中至少携带有TLTRI、接受指示和监控事件报告。
若HSS返回的监控应答消息或监控指示消息中携带了多个监控事件报告，则SCEF向SCS/AS发送的监控应答消息或监控指示消息中携带有TLTRI、(监控事件报告，对应UE的外部组标识或MSISDN)对应关系的列表。
步骤312：SCS/AS向SCEF返回监控指示应答消息。
若监控事件请求是针对一组UE的，SCS/AS针对每个组成员UE返回监控指示应答消息。
基于图3的配置流程的监控事件报告流程具体参见图4，该监控事件报告过程包括：
步骤401：MME/SGSN根据图3下发的监控事件的参数进行事件检测，并根据MRI启动定时器。
MME/SGSN根据Internal Accuracy检测UE位置的改变。
在定时器过期前，MME/SGSN抑制检测到事件相应的事件报告通知，如Location Change。
步骤402：当定时器超期时，并且MME/SGSN保存了至少一个被抑制的事件报告通知，MME/SGSN将监控指示消息发送给SCEF，该监控指示消息中至少携带SCEF Reference ID和监控事件报告。该监控指示消息中携带的监控事件报告为被抑制的事件报告通知列表中最新的事件报告通知，即携带有UE最新的位置信息的事件报告通知。
若监控请求针对一组UE，监控指示信息中还携带有外部标识或MSISDN。
步骤403：SCEF向SCS/AS发送监控指示消息，该监控指示消息中至少携带TLTRI和监控事件报告。
如果SCEF将汇聚的多个来自MME/SGSN的事件报告通知放在一条消息中发送给SCS/AS，则监控指示消息中至少携带有TLTRI、(监控事件报告，对应UE的外部标识或MSISDN)对应关系的列表。
若监控请求针对一组UE，监控指示信息中还携带有外部标识或MSISDN。
步骤404：SCS/AS向SCEF返回监控指示应答消息。
图5为基于5G网络中监控事件的配置过程即事件订阅的配置过程，该配置过程包括：
步骤501：SCS/AS向NEF发送Nnef_EventExposure_Subscribe request消息即订阅请求消息。
该订阅请求消息可以等同于上述图3所示的监控请求消息进行理解。
该订阅请求消息中至少携带有SCS/AS事件通知端点、监控事件标识(Event Id(s))、External Group Id或通用公共签约标识GPSI(Generic Public Subscription Identifier)或所有UE的指示，若订阅请求指示的监控事件包括位置报告，该订阅请求消息中还携带有MRI。
若订阅请求针对一组UE，则该订阅请求消息中携带External Group Id，若订阅请求针对单个UE，则该订阅请求消息中携带GPSI，若订阅请求针对所有UE，则该订阅请求消息中携带所有UE的指示。
Event Id(s)包括Cell_Change，TAI_Change，CN_Node_Change等。
步骤502：NEF将接收到的订阅请求消息中携带的参数进行保存。NEF根据保存的本地策略对配置请求进行授权。
步骤503：NEF向UDM发送Nudm_EventExposure_Subscribe Request消息，该订阅请求消息中携带External Group Id或GPSI，Event Id(s)、NEF事件通知端点、MRI。
步骤504：UDM检查监控事件订阅请求消息。检查通过后，UDM将接收到的订阅请求消息中携带的参数进行保存。UDM确定External Group ID对应的Internal Group ID，GPSI对应的签约永久标识SUPI(Subscription Permanent Identifier)。
若UDM确定订阅请求针对一组UE，则UDM向每一个有组成员注册的AMF执行步骤505，若UDM确定订阅请求针对所有UE，则UDM向所有AMF执行步骤505，若UDM确定订阅请求针对单个UE，UDM向该UE注册的AMF执行步骤505。
步骤505：UDM向AMF发送Namf_EventExposure_Subscribe Request消息，该订阅请求消息中携带NEF事件通知端点、Event Id(s)、Internal Group Id或SUPI或所有UE的指示。
步骤506：UDM根据订阅请求，创建事件订阅上下文。
步骤507：AMF向UDM返回Namf_EventExposure_Subscribe Response消息，该订阅应答消息中至少携带AMF订阅关联标识和接受指示。
步骤508：UDM创建事件订阅上下文，UDM向NEF发送Ndum_EventExposure_Subscribe Response消息，该订阅应答消息中携带UDM订阅关联标识和接受指示。
步骤509：NEF创建事件订阅上下文，NEF向SCS/AS发送Nnef_EventExposure__Subscribe Response消息，该订阅应答消息中携带NEF订阅关联标识和接受指示。
基于图5的配置流程的事件订阅流程具体参见图6，该事件订阅过程包括：
步骤601：AMF根据图5下发的订阅事件的参数进行事件检测，并根据MRI启动定时器。
AMF根据Event Id(s)检测位置改变，并检测到相应的事件，即Location Change。
在定时器过期前，AMF抑制检测到时间相应的时间报告通知，如Location Change。
步骤602：当定时器超期时，并且AMF保存了至少一个被抑制的事件报告通知，AMF向NEF发送Namf_EventExposure_Notify Request消息，该通知请求消息中携带SCEF Reference ID和监控事件报告。其中监控事件报告为被抑制的事件报告通知列表中最新的事件报告通知，即携带有UE最新的位置信息的事件报告通知，如Cell Id，TAI等。
若监控请求针对一组UE，该消息中还携带有GPSI。
步骤603：NEF返回确认消息Nnef_EventExposure_Notify Response，即通知响应消息。
步骤604：NEF向SCS/AS发送Nnef_EventExposure_Notify Request消息，该通知请求消息中携带SCS/AS事件通知端点、监控事件报告。
若NEF接收到的消息中包括GPSI，则NEF向SCS/AS发送的消息中还携带GPSI。
步骤605：SCS/AS向NEF返回确认消息Nnef_EventExposure_Notify Response，即通知响应消息。
基于上述对现有技术事件监控流程的描述，UE发生了inter MME/SGSN/AMF的移动时，UE移动到的新的MME/SGSN/AMF会根据MRI重新设置定时器，因此可能导致UE两次位置报告通知的时间间隔超过MRI，并且在极端情况下，UE多次发生位置改变，并且相邻两次位置改变的时间间隔均不超过MRI，此时MME/SGSN/AMF一直不会发送位置报告通知，使得SCS/AS无法及时监控到UE的位置更新情况。鉴于此，为了保证SCS/AS能够及时监控到UE的位置更新情况，本申请提出了一种监控事件的方法来避免UE两次位置报告通知的时间间隔过长。
具体地，在移动性管理网元重选过程中，若UE从第一移动性管理网元移动到了第二移动性管理网元，第一移动性管理网元将自身维护的该UE对应的第一定时器的当前值作为第一时长值发送给第二移动性管理网元，该第二移动性管理网元将该第一时长值，设置自身维护的该UE对应的第二定时器的初始值，从而保证第二移动性管理网元在采用第二定时器计时时，是在第一移动性管理网元已计时的基础上继续进行计时，而非重新设置定时器重新计时，当第二移动性管理网元确定第二定时器超时时，将该UE被抑制的位置报告通知进行上报，UE两次位置报告通知的时间间隔不会过长，使得SCS/AS能够及时监控到UE的位置更新情况。以下述实施例详细说明监控事件的具体过程，首先参见图7所示的监控事件的过程，该过程包括：
步骤701：在移动性管理网元重选过程中，第一移动性管理网元确定第一时长值。
其中，所述第一时长值为所述第一移动性管理网元维护的UE对应的第一定时器的当前值，所述第一移动性管理网元在所述第一定时器计时超时前抑制发送所述UE的位置报告通知。如果在移动性管理网元重选过程中，UE从第一移动性管理网元移动到了第二移动性管理网元，为了实现事件的监控，在UE发生移动性管理网元重选之前，第一移动性管理网元需要按照上述图3或图5所示的配置流程获取监控事件配置。
实例的，当UE从第一移动性管理网元管理的区域移动到了第二移动性管理网元的区域时，第二移动性管理网元向第一移动性管理网元发送上下文请求消息。第一移动性管理 网元如果接收到第二移动性管理网元发送的上下文请求消息，确定UE发生了移动性管理网元的重选。
第一移动性管理网元如果确定UE发生了移动性管理网元的重新，将自身维护的UE对应的第一定时器的当前值确定为第一时长值，该第一时长值能够表明第一移动性管理网元维护的UE对应的第一定时器的已计时时长(对应以下正计时)或是最小时间间隔的剩余时长值(对应以下倒计时)。
因此可选地，第一移动性管理网元在确定第一时长值之前，可以对自身维护的UE对应的第一定时器进行设置，该过程可以在上述图3或图5所示的配置流程中实现。
第一移动性管理网元在设置UE对应的第一定时器时，用户数据管理网元发送最小报告间隔MRI，该MRI为两个或多个位置报告通知之间的最小时间间隔，第一移动性管理网元接收该MRI，启动UE对应的第一定时器，并根据该MRI设置第一定时器的初始值。
一种示例，第一移动性管理网元维护的定时器如果为正计时，则设置的第一定时器的初始值为0，计时门限值为MRI。
另一种示例，第一移动性管理网元维护的定时器如果为倒计时，则设置的第一定时器的初始值为该MRI。
具体地，移动性管理网元自身维护的UE对应的第一定时器的当前取值可以用当前最大报告间隔(Current Maximum Report Interval，CMRI)来表示，如第一移动性管理网元自身维护的UE对应的第一定时器的当前值即第一时长值，可以用CMRI1来表示。
第一移动性管理网元在自身维护的UE对应的第一定时器计时超时前抑制发送该UE的位置报告通知，在该第一定时器计时超时时，发送该UE被抑制的位置报告通知。
具体地，如果在第一定时器计时超时时，若至少存在一个被抑制的该UE的位置报告通知，第一移动性管理网元可以在被抑制的该UE的位置报告通知中，任意选取进行上报的UE的位置报告通知，也可以发送被抑制的UE的位置报告通知中最新一个位置报告通知。
可选地，第一移动性管理网元发送UE被抑制的位置报告通知时，并重启第一定时器且根据MRI设置该重启的第一定时器的初始值。
步骤702：第一移动性管理网元向第二移动性管理网元发送所述第一时长值。
一种示例，第一移动性管理网元可以将确定的第一时长值直接发送给第二移动性管理网元。
另一种示例，如果接收到第二移动性管理网元发送的上下文请求消息，第一移动性管理网元可以将确定的第一时长值携带在上下文应答消息中，发送给第二移动性管理网元。
步骤703：第二移动性管理网元接收第一移动性管理网元发送的所述第一时长值。
一种示例，第二移动性管理网元接收第一移动性管理网元直接发送的第一时长值。
另一种示例，第二移动性管理网元接收第一移动性管理网元发送的携带有第一时长值的上下文应答消息。
步骤704：第二移动性管理网元启动自身维护的所述UE对应的第二定时器，并根据所述第一时长值，设置所述第二定时器的初始值。
为了实现监控事件的上报以使SCS/AS能够检测到UE的位置信息，第二移动性管理网元需要启动自身维护的该UE对应的第二定时器进行计时。
第二移动性管理网元在启动UE对应的第二定时器时，根据接收到的第一时长值，对 该第二定时器的初始值进行设置。
一种示例，第二移动性管理网元维护的定时器如果为正计时，则将接收到的第一时长值设置为第二定时器的已计时的初始值。
另一种示例，第二移动性管理网元维护的定时器如果为倒计时，则将接收到的第一时长值设置为第二定时器的倒计时进行计时时的初始值。
步骤705：第二移动性管理网元在所述第二定时器计时超时时，发送所述UE被抑制的位置报告通知。
可选地，在第二定时器计时超时前，第二移动性管理网元抑制发送UE的位置报告信息。
可选地，当在第二定时器计时超时时，若至少存在一个被抑制的UE的位置报告通知，第二移动性管理网元可以在被抑制的UE的位置报告通知中，任意选取进行上报的UE的位置报告通知，也可以发送在被抑制的UE的位置报告通知中最近的一个位置报告通知。
被抑制的UE的位置报告通知中最近的一个位置报告通知，即为被抑制的UE的位置报告通知中最新的位置报告通知，该最近的一个位置报告通知中UE的位置信息可以认为是UE当前的位置信息。
可选地，第二移动性管理网元在该第二定时器计时超时时，对自身维护的UE对应的第二定时器进行重新设置。
具体地，用户数据管理网元发送最小报告间隔MRI，该MRI为两个或多个位置报告通知之间的最小时间间隔，第二移动性管理网元接收该MRI，在第二定时器计时超时时，重启UE对应的第二定时器，并根据该MRI设置第二定时器的初始值。
一种示例，第二移动性管理网元维护的定时器如果为正计时，则设置的第二定时器的初始值为0，计时门限值为MRI。
另一种示例，第二移动性管理网元维护的定时器如果为倒计时，则设置的第二定时器的初始值为该MRI。
上述第一移动性管理网元或第二移动性管理网元为MME、SGSN、及AMF中的任意一种。需要注意的是，第一移动性管理网元和第二移动性管理网元可以为处于同一网络类型下的移动性管理网元，如第一移动性管理网元和第二移动性管理网元均为处于4G网络下的移动性管理网元，或均为处于5G网络下的移动性管理网元，第一移动性管理网元和第二移动性管理网元也可以处于不同网络类型下的移动性管理网元，如第一移动性管理网元为处于4G网络下的移动性管理网元，第二移动性管理网元为处于5G网络下的移动性管理网元。
此外，若在定时器过期前，UE发生了inter MME/SGSN/AMF的移动，并且又回到了最初的MME/SGSN/AMF，即在移动性管理网元重选过程中，UE从第一移动性管理网元移动到了第二移动性管理网元，在定时器过期前，UE又从第二移动性管理网元移动回了最初的第一移动性管理网元，由于最初第一移动性管理网元上报的最后一次时间通知的UE的位置信息已经清空，此时在定时器过期时，第一移动性管理网元会重新上报UE的位置报告通知，连续上报的UE的位置报告通知中UE的位置信息一致的，对SCS/AS检测UE的位置更新情况来说是没有意义的，反而增加了信令，浪费了网络资源。鉴于此，在保证SCS/AS能够及时监控到UE的位置更新情况的基础上，本申请提出的监控事件的方法中还能够在最后一次上报的UE的位置信息与检测到的UE的当前位置信息一致时，不进行UE 的位置报告通知的上报，从而节省了网络资源。具体参见图8所示的监控事件的过程，该过程包括：
步骤801：第一移动性管理网元向第二移动性管理网元发送最近一次报告的UE的位置信息。
根据上述图7的描述，可知第一移动性管理网元在自身维护的UE对应的第一定时器计时超时时，可以发送UE被抑制的位置报告通知，具体可以发送被抑制的UE的位置报告通知中最近的一个位置报告通知。
如果第一移动性管理网元发送被抑制的UE的位置报告通知中最近的一个位置报告通知，第一移动性管理网元在发送该最近的一个位置报告通知之后，保存该最近的一个位置报告通知中UE的位置信息作为最近一次报告的UE的位置。
第一移动性管理网元中保存最近一次报告的UE的位置信息，方便了第一移动性管理网元向第二移动性管理网元发送该最近一次报告的UE的位置信息，也方便了如果在定时器过期前，UE又移动回第一移动性管理网元时，第一移动性管理网元决定是否上报UE的位置报告通知。
因此，第一移动性管理网元保存的最近一次报告的UE的位置信息可能是UE从其他移动性管理网元移动到第一移动性管理网元时，向第一移动性管理网元发送的最近一次报告的UE的位置信息，其中其他移动性管理网元可以包括第二移动性管理网元，可能是设置此次第一定时器之前的第一定时器计时超时时，第一移动性管理网元发送的位置报告通知中UE的位置信息。
在第一移动性管理网元在自身维护的UE对应的第一定时器计时超时时，第一移动性管理网元确认UE的当前位置信息与保存的最近一次报告的UE的位置信息不同，发送UE被抑制的位置报告通知。
可选地，为了节省网络资源，在第一移动性管理网元在自身维护的UE对应的第一定时器计时超时时，且确认UE的当前位置与保存的最近一次报告的UE的位置信息相同，不发送UE的位置报告通知。
可选地，在第一定时器计时超时前，第一移动性管理网元确认UE的当前位置信息与保存的最近一次报告的UE的位置信息不同时，生成UE被抑制的位置报告通知，第一移动性管理网元确认UE的当前位置信息与保存的最近一次报告的UE的位置信息相同时，不生成UE被抑制的位置报告通知。
第一移动性管理网元将发送的最近的一个位置报告通知中的UE的位置信息，作为最近一次报告的UE的位置信息进行发送。
一种示例，第一移动性管理网元可以将该最近一次报告的UE的位置信息直接发送给第二移动性管理网元。
另一种示例，如果接收到第二移动性管理网元发送的上下文请求消息，第一移动性管理网元可以将该最近一次报告的UE的位置信息携带在上下文应答消息中，发送给第二移动性管理网元。
步骤802：第二移动性管理网元接收第一移动性管理网元发送的最近一次报告的UE的位置信息。
一种示例，第二移动性管理网元接收第一移动性管理网元直接发送的最近一次报告的UE的位置信息。
另一种示例，第二移动性管理网元接收第一移动性管理网元发送的携带有最近一次报告的UE的位置信息的上下文应答消息。
步骤803：当在所述第二定时器计时超时时，第二移动性管理网元确认UE的当前位置信息与最近一次报告的UE的位置信息不同，发送UE被抑制的位置报告通知。
由于移动性管理网元能够确认自身管理的范围内的UE的位置信息，因此在第二定时器计时超时时，为了保证SCS/AS能够及时检测UE的位置更新情况，第二移动性管理网元确认UE的当前位置与信息与最近一次报告的UE的位置信息不同，发送UE被抑制的位置报告通知。
如果第二移动性管理网元发送了被抑制的UE的位置报告通知中最近的一个位置报告通知，第二移动性管理网元在发送该最近的一个位置报告通知之后，保存该最近的一个位置报告通知中的UE的位置信息作为最近一次报告的UE的位置信息。
此外，为了节省网络资源，第二移动性管理网元在所述第二定时器计时超时时，且所述UE的当前位置信息与所述最近一次报告的所述UE的位置信息相同，不发送所述UE的位置报告通知。
如果第二移动性管理网元不发送UE的位置报告通知，第二移动性管理网元可以继续将第一移动性管理网元发送的位置信息作为最近一次报告的UE的位置信息保存。
可选地，在第二定时器计时超时前，第二移动性管理网元确认UE的当前位置信息与保存的最近一次报告的UE的位置信息不同时，生成UE被抑制的位置报告通知，第二移动性管理网元确认UE的当前位置信息与保存的最近一次报告的UE的位置信息相同时，不生成UE被抑制的位置报告通知。
如果该第二定时器为根据第一移动性管理网元发送的第一时长值设置的定时器，第二移动性管理网元保存的最近一次报告的UE的位置信息为第一移动性管理网元发送的UE的位置信息，如果该第二定时器为第二移动性管理网元在发送UE的位置报告通知后重新设置的定时器，第二移动性管理网元保存的最近一次报告的UE的位置为第二移动性管理网元发送的UE的位置报告通知中的UE的位置信息。
下面以两个具体的实施例对本申请监控时间的过程进行说明。
实施例一，本申请应用在4G网络时，假设UE从MME/SGSN1移动到MME/SGSN2场景下时，参见图9所示的监控事件报告的流程，监控事件报告的过程包括：
步骤901：MME/SGSN1按照上述图3所示的配置流程进行监控事件配置。
步骤902：UE移动到MME/SGSN2管理的区域，MME/SGSN2接收到来自UE的跟踪区更新(Tracking Area Update，TAU)/路由区更新(Routing Area Update，RAU)请求。
步骤903：MME/SGSN2向MME/SGSN1发送上下文请求。
步骤904：MME/SGSN1向MME/SGSN2返回上下文应答消息。
该上下文应答消息中携带SCEF标识、SCEF Reference ID和UE对应的第一定时器当前的取值CMRI1。若MME/SGSN1向SCEF发送过位置报告通知，该上下文应答消息中还包括最后一次位置报告通知中的位置信息Last Location Info。
该最后一次位置报告通知中的位置信息Last Location Info包括Cell Id，(e)NodeB Id，或TAI等。
步骤905：MME/SGSN2向MME/SGSN1返回确认消息。
步骤906：MME/SGSN2向HSS发送位置更新请求。
步骤907：HSS向MME/SGSN1发送取消位置请求。
步骤908：MME/SGSN1向HSS返回应答消息即取消位置确认消息。
步骤909：HSS向MME/SGSN2返回更新位置确认消息。
该更新位置确认消息中携带有监控事件配置信息，至少包括Monitoring type，SCEF标识、SCEF Reference ID、MRI、Internal Accuracy，外部标识或MSISDN。
步骤910：MME/SGSN2进行事件检测。
具体地，MME/SGSN2根据步骤909下发的更新位置确认消息中携带的监控事件参数进行事件监控，且同时启动UE对应的第二定时器并根据CMRI1设置该第二定时器的初始值。
MME/SGSN2根据Internal Accuracy进行事件监控，检测位置改变。
在该第二定期器过期前，MME/SGSN2抑制检测到的事件(即Location Change)相应的事件报告通知。
步骤911：当该第二定期器超期时，并且MME/SGSN2保存了至少一个被抑制的事件报告通知，则MME/SGSN2向SCEF发送监控指示。
该监控指示携带SCEF Reference ID及位置报告通知。
若监控请求针对一组UE，则还包括外部标识或MSISDN。其中监控事件报告为被抑制的事件报告通知列表中最新的事件报告通知，即该最新的事件报告通知中包括UE最新的位置信息，也就是UE当前的位置信息。
若MME/SGSN2从MME/SGSN1接收到了Last Location Info，则MME/SGSN2根据Last Location Info与UE当前的位置信息来判断是否发生了Location Change。若Last Location Info与UE当前的位置信息不同，MME/SGSN2确认发生了Location Change，否则MME/SGSN2确认未发生Location Change。
由于MME/SGSN2根据CMRI1设置了第二定时器，则对于MME/SGSN2来说，Last Location Info与UE当前的位置信息必然是不同的，也就是此时Cell Id，(e)NodeB Id或TAI/RAI一定发生了变化，因此在该场景下，当第二定时器计时超期时，MME/SGSN2一定会发送位置报告通知。
步骤912：SCEF向SCS/AS发送监控指示。
该监控指示中至少携带TLTRI及位置报告通知。
若监控请求针对一组UE，则该监控指示中还包括外部标识或MSISDN。
为了便于理解本申请中移动性管理网元在最后一次上报的UE的位置信息与检测到的UE的当前位置信息一致时，不进行UE的位置报告通知的上报的过程，假设UE从MME/SGSN1移动到MME/SGSN2，而又从MME/SGSN2移动到MME/SGSN1场景下时，具体可以参见图10所示的监控事件报告的流程，该过程具体包括：
步骤1001～步骤1010的实现过程同上述图9所示的步骤901～步骤910，这里不再重复赘述。
步骤1011：UE移动到MME/SGSN1管理的区域，MME/SGSN1接收到来自UE的TAU/RAU请求。
步骤1012：MME/SGSN1向MME/SGSN2发送上下文请求消息。
步骤1013：MME/SGSN2向MME/SGSN1返回上下文应答消息。
该上下文应答消息中携带SCEF标识、SCEF Reference ID和UE对应的第二定时器当 前的取值CMRI2。
若MME/SGSN2向SCEF发送过位置报告通知，该上下文应答消息中包括的Last Location Info为MME/SGSN2上报的最后一次监控事件报告中的位置信息；否则，若MME/SGSN2从MME/SGSN1中接收到Last Location Info，该上下文应答消息中包括的Last Location Info为MME/SGSN1发送的Last Location Info。
步骤1014：MME/SGSN1向MME/SGSN2返回确认消息。
步骤1015：MME/SGSN1向HSS发送位置更新请求。
步骤1016：HSS向MME/SGSN2发送取消位置请求。
步骤1017：MME/SGSN2向HSS返回应答消息即取消位置确认消息。
步骤1018：HSS向MME/SGSN1返回位置更新位置确认消息。
该更新位置确认消息中携带监控事件配置信息，至少包括Monitoring type，SCEF标识、SCEF Reference ID、MRI、Internal Accuracy，外部标识或MSISDN。
步骤1019：MME/SGSN1进行事件检测。
根据步骤1018下发的更新位置确认消息中携带的监控事件参数进行事件监控，且同时启动UE对应第一定时器并根据CMRI2设置该第一定时器的初始值。
MME/SGSN1根据Internal Accuracy进行事件监控，检测位置改变。
在该第一定期器过期前，MME/SGSN1抑制检测到的事件(即Location Change)相应的事件报告通知。
步骤1020：当该第一定期器超期时，并且MME/SGSN1保存了至少一个被抑制的事件报告通知，则MME/SGSN1向SCEF发送监控指示。
该监控指示携带SCEF Reference ID即位置报告通知。
若监控请求针对一组UE，则还包括外部标识或MSISDN。其中监控事件报告为被抑制的事件报告通知列表中最新的事件报告通知，即该最新的事件报告通知中包括UE最新的位置信息，也就是UE当前的位置信息。
若MME/SGSN1从MME/SGSN2接收到了Last Location Info，则MME/SGSN1根据Last Location Info与UE当前的位置来判断是否发生了Location Change。
由于UE从MME/SGSN2又移动回MME1/SGSN1，Last Location Info携带的可能是MME/SGSN1之前向SCEF报告的位置信息，UE当前的位置信息和Last location Info信息可能相同，因此在这种情况下，当该第一定时器超期时，MME/SGSN1不发送UE的位置报告通知。
如果Last Location Info携带的是MME/SGSN2向SCEF报告的位置信息，UE当前的位置信息和Last location Info信息不相同，因此在这种情况下，当该第一定时器超期时，MME/SGSN1发送UE的位置报告通知。
步骤1021：SCEF向SCS/AS发送监控指示。
该监控指示中至少携带TLTRI及位置报告通知。
若监控请求针对一组UE，则还包括外部标识或MSISDN。
实施例二，本申请应用在5G网络时，假设UE从AMF1移动到AMF2场景下时，参见图11所示的监控事件报告的流程，监控时间报告的过程包括：
步骤1101：AMF1按照上述图5所示的配置流程进行监控事件的订阅。
步骤1102：UE移动到AMF2管理的区域，AMF2接收到来自UE的Registration Area 更新请求，即RAU更新请求。
步骤1103：AMF2向AMF1发送上下文请求消息，如Namf_Communication_UEContextTransfer消息。
步骤1104：AMF 1向AMF 2返回上下文应答消息，如Namf_Communication_UEContextTransfer Response消息。
该上下文应答消息中携带事件订阅的上下文，该事件订阅的上下文至少包括Internal Group Id，Event Id(s)、NEF事件通知端点、MRI和UE对应的第一定时器当前的取值CMRI1。若AMF1向NEF发送过位置报告，该上下文应答消息中还报告最后一次监控事件报告中的位置信息Last Location Info。
步骤1105：AMF 2向AMF 1返回上下文确认消息，如Namf_Communication_RegistrationCompleteNotify消息。
步骤1106：AMF2向UDM发送注册请求如Nudm_UECM_Registration消息，UDM返回应答消息，或AMF2向UDM发送获取UE的签约信息请求如Nudm_SDM_GET消息，UDM返回应答消息，或AMF2向UDM发送订阅签约数据改变的通知请求如Nudm_SDM_Subsribed消息，UDM返回应答消息。
步骤1107：UDM向AMF1发送去注册请求如Nudm_UECM_DeregistrationNotify消息，AMF1返回应答消息。
AMF1向UDM发送取消签约数据改变的通知的订阅请求如Nudm_SDM_Unsubsribe消息，UDM返回应答消息。
步骤1108：AMF2进行事件检测，如根据步骤1104获取的上下文应答消息中携带的事件订阅的参数进行事件监控，且启动UE对应的第二定时器并根据CMRI1设置第二定时器的初始值。
MME/SGSN2根据Event ID进行事件监控，检测位置改变。
在该第二定期器过期前，AMF 2抑制检测到的事件(即Location Change)相应的事件报告通知。
步骤1109：当该第二定期器超期时，并且AMF 2保存了至少一个被抑制的事件报告通知，则AMF 2向NEF发送监控指示，如Namf_EventExposure_Notify Request消息，NEF返回应答消息，如Namf_EventExposure_Notify Reponse消息。
该监控指示中携带NEF事件通知端点、监控事件报告。
若监控请求针对一组UE，则还包括GPSI。其中监控事件报告为被抑制的事件报告通知列表中最新的事件报告通知，即该最新的事件报告通知中包括UE最新的位置信息，也就是UE当前的位置信息。
若AMF 2从AMF 1接收到了Last Location Info，则AMF 2根据Last Location Info与UE当前的位置信息来判断是否发生了Location Change。
由于AMF 2根据CMRI1设置了第二定时器，则对于AMF 2来说，Last Location Info与UE当前的位置信息必然是不同的，也就是此时Cell Id，NgNodeB Id或RAI一定发生了变化，所以在该场景下，当第二定时器计时超期时，AMF 2一定会发送事件报告的通知。
步骤1110：NEF向SCS/AS发送监控指示，如Namf_EventExposure_Notify Request消息，SCS/AS返回应答消息，如Namf_EventExposure_Notify Reponse消息。
该监控指示中至少携带SCS/AS事件通知端点及位置报告通知。
若监控请求针对一组UE，则还包括GPSI。
为了便于理解本申请中移动性管理网元在最后一次上报的UE的位置信息与检测到的UE的当前位置信息一致时，不进行UE的位置报告通知的上报的过程，假设UE从AMF1移动到AMF2，而又从AMF2移动到AMF1场景下时，具体可以参见图12所示的监控事件报告的流程，该过程具体包括：
步骤1201～步骤1208的实现过程同上述图11所示的步骤1101～步骤1108，这里不再重复赘述。
步骤1209：UE移动到AMF1管理的区域，AMF1接收到来自UE的Registration Area更新请求，即RAU更新请求。
步骤1210：AMF1向AMF2发送上下文请求消息，如Namf_Communication_UEContextTransfer消息。
步骤1211：AMF 2向AMF 1返回上下文应答消息，如Namf_Communication_UEContextTransfer Response消息。
该上下文问应答消息中携带事件订阅的上下文，其中该事件订阅的上下文至少包括Internal Group Id，Event Id(s)、NEF事件通知端点、MRI和UE对应的第二定时器当前的取值CMRI2。
若AMF2向NEF发送过监控事件报告，该上下文应答消息中包括的Last Location Info为AMF2最后一次监控事件报告中的位置信息；否则，若AMF2从AMF1中接收到Last Location Info，则，该上下文应答消息中包括的Last Location Info为AMF1发送的Last Location Info。
步骤1212：AMF 1向AMF 2返回上下文确认消息，如Namf_Communication_RegistrationCompleteNotify消息。
步骤1213：AMF1向UDM发送注册请求如Nudm_UECM_Registration消息，UDM返回应答消息，或AMF1向UDM发送获取UE的签约信息请求如Nudm_SDM_GET消息，UDM返回应答消息，或AMF1向UDM发送订阅签约数据改变的通知请求如Nudm_SDM_Subsribed消息，UDM返回应答消息。
步骤1214：UDM向AMF2发送去注册请求如Nudm_UECM_DeregistrationNotify消息，AMF2返回应答消息，或AMF2向UDM发送取消签约数据改变的通知的订阅请求如Nudm_SDM_Unsubsribe消息，UDM返回应答消息。
步骤1215：AMF1根据步骤1211获取的上下文应答消息中携带的事件订阅的参数进行事件检测，且启动UE对应的第一定时器并根据CMRI2设置第一定时器的初始值。
AMF根据Event ID进行事件检测，检测位置改变。
在该第一定期器过期前，AMF1抑制检测到的事件(即Location Change)相应的事件报告通知。
步骤1216：当该定期器超期时，并且AMF 1保存了至少一个被抑制的事件报告通知，则AMF 1向NEF发送监控指示，如Namf_EventExposure_Notify Request消息，NEF返回应答消息，如Namf_EventExposure_Notify Reponse消息。
该监控指示中携带NEF事件通知端点、监控事件报告。
若监控请求针对一组UE，则还包括GPSI。其中监控事件报告为被抑制的事件报告通知列表中最新的事件报告通知，即该最新的事件报告通知中包括UE最新的位置信息，也 就是UE当前的位置信息。
若AMF1从AMF 2接收到了Last Location Info，则AMF 1根据Last Location Info与UE当前的位置信息来判断是否发生了Location Change。
由于UE从AMF 2又移动回AMF 1，Last Location Info携带的可能是AMF 1之前向SCEF报告的位置信息，因此UE当前的位置信息和Last location Info信息可能相同，因此在这种情况下，当该第一定时器超期时，AMF 1不发送UE的位置报告通知。
如果Last Location Info携带的是AMF2向NEF报告的位置信息，UE当前的位置信息和Last Location Info信息不同，因此在这种情况下，当该第一定时器超期时，AMF1发送UE的位置报告通知。
步骤1217：NEF向SCS/AS发送监控指示，如Namf_EventExposure_Notify Request消息，NEF返回应答消息，如Namf_EventExposure_Notify Reponse消息。
该监控指示中至少携带SCS/AS事件通知端点及位置报告通知。
若监控请求针对一组UE，则还包括GPSI。
UE从4G网络的MME/SGSN移动到5G网络的AMF的流程类似，不再赘述。
以上结合图7至图12详细说明了本申请实施例的监控事件的方法，基于与上述监控事件的方法的同一发明构思，如图13所示，本申请实施例还提供了一种监控事件的装置1300的结构示意图。装置1300可用于实现上述应用于移动性管理网元的方法实施例中描述的方法，可以参见上述方法实施例中的说明，其中所述移动性管理网元包括第一移动性管理网元或第二移动性管理网元。所述装置1300可以处于移动性管理网元中或为移动性管理网元。
所述装置1300包括一个或多个处理器1301。所述处理器1301可以是通用处理器或者专用处理器等。例如可以是基带处理器、或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、终端、或芯片等)进行控制，执行软件程序，处理软件程序的数据。所述通信装置可以包括收发单元，用以实现信号的输入(接收)和输出(发送)。例如，所述收发单元可以为收发器，射频芯片等。
所述装置1300包括一个或多个所述处理器1301，所述一个或多个处理器1301可实现上述所示的实施例中移动性管理网元的方法。
可选的，处理器1301除了实现上述所示的实施例的方法，还可以实现其他功能。
可选的，一种设计中，处理器1301可以执行指令，使得所述装置1300执行上述方法实施例中描述的方法。所述指令可以全部或部分存储在所述处理器内，如指令1303，也可以全部或部分存储在与所述处理器耦合的存储器1302中，如指令1304，也可以通过指令1303和1304共同使得装置1300执行上述方法实施例中描述的方法。
在又一种可能的设计中，通信装置1300也可以包括电路，所述电路可以实现前述方法实施例中移动性管理网元的功能。
在又一种可能的设计中所述装置1300中可以包括一个或多个存储器1302，其上存有指令1304，所述指令可在所述处理器上被运行，使得所述装置1300执行上述方法实施例中描述的方法。可选的，所述存储器中还可以存储有数据。可选的处理器中也可以存储指令和/或数据。例如，所述一个或多个存储器1302可以存储上述实施例中所描述的对应关 系，或者上述实施例中所涉及的相关的参数或表格等。所述处理器和存储器可以单独设置，也可以集成在一起。
在又一种可能的设计中，所述装置1300还可以包括收发单元1305以及天线1306。所述处理器1301可以称为处理单元，对装置(终端或者基站)进行控制。所述收发单元1305可以称为收发机、收发电路、或者收发器等，用于通过天线1306实现装置的收发功能。
应注意，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读介质，其上存储有计算机程序，该计算机程序被计算机执行时实现上述应用于移动性管理网元的任一方法实施例所述的监控事件的方法。
本申请实施例还提供了一种计算机程序产品，该计算机程序产品被计算机执行时实现上述应用于移动性管理网元的任一方法实施例所述的监控事件的方法。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、 计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(Digital Video Disc，DVD))、或者半导体介质(例如，固态硬盘(Solid State Disk，SSD))等。
本申请实施例还提供了一种处理装置，包括处理器和接口；所述处理器，用于执行上述应用于移动性管理网元的任一方法实施例所述的监控事件的方法。
应理解，上述处理装置可以是一个芯片，所述处理器可以通过硬件来实现也可以通过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，改存储器可以集成在处理器中，可以位于所述处理器之外，独立存在。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或通信连接，也可以是电的，机械的或其它的形式连接。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本申请可以用硬件实现，或固件实现，或它们的组合方式来实现。当使用软件实现时，可以将上述功能存储在计算机可读介质中或作为计算机可读介质上的一个或多个指令或代码进行传输。计算 机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是计算机能够存取的任何可用介质。以此为例但不限于：计算机可读介质可以包括RAM、ROM、EEPROM、CD-ROM或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。此外。任何连接可以适当的成为计算机可读介质。例如，如果软件是使用同轴电缆、光纤光缆、双绞线、数字用户线(DSL)或者诸如红外线、无线电和微波之类的无线技术从网站、服务器或者其他远程源传输的，那么同轴电缆、光纤光缆、双绞线、DSL或者诸如红外线、无线和微波之类的无线技术包括在所属介质的定影中。如本申请所使用的，盘(Disk)和碟(disc)包括压缩光碟(CD)、激光碟、光碟、数字通用光碟(DVD)、软盘和蓝光光碟，其中盘通常磁性的复制数据，而碟则用激光来光学的复制数据。上面的组合也应当包括在计算机可读介质的保护范围之内。
总之，以上所述仅为本申请技术方案的较佳实施例而已，并非用于限定本申请的保护范围。凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (24)

  1. 一种监控事件的方法，其特征在于，包括：
    在移动性管理网元重选过程中，第二移动性管理网元接收第一移动性管理网元发送的第一时长值，所述第一时长值是所述第一移动性管理网元维护的用户设备UE对应的第一定时器的当前值，所述第一移动性管理网元在所述第一定时器计时超时前抑制发送所述UE的位置报告通知；
    所述第二移动性管理网元启动自身维护的所述UE对应的第二定时器，并根据所述第一时长值，设置所述第二定时器的初始值；
    所述第二移动性管理网元在所述第二定时器计时超时时，发送所述UE被抑制的位置报告通知。
  2. 如权利要求1所述的方法，其特征在于，还包括：
    在所述第二定时器计时超时前，所述第二移动性管理网元抑制发送所述UE的位置报告通知。
  3. 如权利要求2所述的方法，其特征在于，还包括：
    当在所述第二定时器计时超时时，若至少存在一个被抑制的所述UE的位置报告通知，则所述第二移动性管理网元发送被抑制的所述UE的位置报告通知中最近的一个位置报告通知。
  4. 如权利要求1～3任一所述的方法，其特征在于，还包括：
    所述第二移动性管理网元接收所述第一移动性管理网元发送的所述第一移动性管理网元保存的最近一次报告的所述UE的位置信息。
  5. 如权利要求4所述的方法，其特征在于，所述第二移动性管理网元发送所述UE被抑制的位置报告通知之前，还包括：
    所述第二移动性管理网元确认所述UE的当前位置信息与所述最近一次报告的所述UE的位置信息不同。
  6. 如权利要求4所述的方法，其特征在于，还包括：
    所述第二移动性管理网元在所述第二定时器计时超时时，且所述UE的当前位置信息与所述最近一次报告的所述UE的位置信息相同，不发送所述UE的位置报告通知。
  7. 如权利要求4所述的方法，其特征在于，还包括：
    在所述第二定时器计时超时前，所述第二移动性管理网元确认所述UE的当前位置信息与所述最近一次报告的所述UE的当前位置不同时，生成所述UE被抑制的位置报告通知。
  8. 如权利要求1-7任一项所述的方法，其特征在于，还包括：
    所述第二移动性管理网元接收用户数据管理网元发送最小报告间隔，所述最小报告间隔为两个或多个位置报告通知之间的最小时间间隔；
    在所述第二定时器计时超时时，所述第二移动性管理网元重启所述第二定时器，并根据所述最小报告间隔，设置所述第二定时器的初始值。
  9. 如权利要求4所述的方法，其特征在于，还包括：
    所述第二移动性管理网元发送被抑制的所述UE的位置报告通知中最近的一个位置报告通知之后，所述第二移动性管理网元保存所述最近的一个位置报告通知中的所述UE的 位置信息作为最近一次报告的所述UE的位置信息。
  10. 如权利要求1-9任一项所述的方法，其特征在于，所述第二移动性管理网元或第一移动性管理网元为移动性管理实体MME、GPRS服务支持节点SGSN、及接入和移动性管理功能网元AMF中的任意一种。
  11. 一种监控事件的方法，其特征在于，包括：
    在移动性管理网元重选过程中，第一移动性管理网元确定第一时长值，所述第一时长值为所述第一移动性管理网元维护的用户设备UE对应的第一定时器的当前值，所述第一移动性管理网元在所述第一定时器计时超时前抑制发送所述UE的位置报告通知；
    所述第一移动性管理网元向第二移动性管理网元发送所述第一时长值。
  12. 如权利要求11所述的方法，其特征在于，在所述第一移动性管理网元确定第一时长值之前，还包括：
    所述第一移动性管理网元接收用户数据管理网元发送的最小报告间隔，所述最小报告间隔为两个或多个位置报告通知之间的最小时间间隔；
    所述第一移动性管理网元启动所述第一定时器，并根据所述最小报告间隔设置所述第一定时器的初始值。
  13. 如权利要求11或12所述的方法，其特征在于，在所述第一定时器计时超时时，所述第一移动性管理网元发送所述UE的位置报告通知。
  14. 如权利要求12所述的方法，其特征在于，还包括：
    当所述第一定时器计时超时时，若至少存在一个被抑制的所述UE的位置报告通知，则所述第一移动性管理网元发送被抑制的所述UE的位置报告通知中最近的一个位置报告通知，并重启所述第一定时器且根据所述最小报告间隔设置初始值。
  15. 如权利要求14所述的方法，其特征在于，还包括：
    所述第一移动性管理网元发送被抑制的所述UE的位置报告通知中最近的一个位置报告通知之后，所述第一移动性管理网元保存所述最近的一个位置报告通知中的所述UE的位置信息作为最近一次报告的所述UE的位置信息。
  16. 如权利要求14或15所述的方法，其特征在于，所述第一移动性管理网元向所述第二移动性管理网元发送所述最近一次报告的所述UE的位置信息。
  17. 如权利要求15所述的方法，其特征在于，所述第一移动性管理网元发送所述UE被抑制的位置报告通知之前，还包括：
    所述第一移动性管理网元确认所述UE的当前位置信息与所述最近一次报告的所述UE的位置信息不同。
  18. 如权利要求15所述的方法，其特征在于，还包括：
    所述第一移动性管理网元在所述第一定时器计时超时时，且所述UE的当前位置信息与所述最近一次报告的所述UE的位置信息相同，不发送所述UE的位置报告通知。
  19. 如权利要求15所述的方法，其特征在于，还包括：
    在所述第一定时器计时超时前，所述第一移动性管理网元确认所述UE的当前位置信息与所述最近一次报告的所述UE的当前位置不同时，生成所述UE被抑制的位置报告通知。
  20. 如权利要求11-19任一项所述的方法，其特征在于，所述第一移动性管理网元或第二移动性管理网元为移动性管理实体MME、GPRS服务支持节点SGSN、及接入和移动 性管理功能网元AMF中的任意一种。
  21. 一种监控事件的装置，其特征在于，包括处理器和存储器，所述处理器与所述存储器耦合；
    存储器，用于存储计算机程序；
    处理器，用于执行所述存储器中存储的计算机程序，以使得所述装置执行如权利要求1-20中任一项所述的方法。
  22. 一种计算机可读存储介质，其特征在于，包括程序或指令，当所述程序或指令在计算机上运行时，如权利要求1-20中任意一项所述的方法被执行。
  23. 一种计算机程序产品，其特征在于，包括程序或指令，当所述程序或指令在计算机上运行时，如权利要求1-20中任意一项所述的方法被执行。
  24. 一种芯片，其特征在于，所述芯片与存储器耦合，用于读取并执行所述存储器中存储的程序指令，以执行权利要求1-20中任意一项所述的方法。
PCT/CN2020/075877 2019-02-19 2020-02-19 一种监控事件的方法及装置 WO2020169050A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP20759930.9A EP3911010A4 (en) 2019-02-19 2020-02-19 EVENT MONITORING METHOD AND DEVICE
JP2021548611A JP7200392B2 (ja) 2019-02-19 2020-02-19 イベント監視方法および装置
US17/404,218 US12028931B2 (en) 2019-02-19 2021-08-17 Event monitoring method and apparatus
JP2022204705A JP7451667B2 (ja) 2019-02-19 2022-12-21 イベント監視方法および装置

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910124749.XA CN111586583B (zh) 2019-02-19 2019-02-19 一种监控事件的方法及装置
CN201910124749.X 2019-02-19

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/404,218 Continuation US12028931B2 (en) 2019-02-19 2021-08-17 Event monitoring method and apparatus

Publications (1)

Publication Number Publication Date
WO2020169050A1 true WO2020169050A1 (zh) 2020-08-27

Family

ID=72110764

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/075877 WO2020169050A1 (zh) 2019-02-19 2020-02-19 一种监控事件的方法及装置

Country Status (5)

Country Link
US (1) US12028931B2 (zh)
EP (1) EP3911010A4 (zh)
JP (2) JP7200392B2 (zh)
CN (2) CN114501333A (zh)
WO (1) WO2020169050A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4250786A4 (en) * 2020-12-31 2024-01-17 Huawei Technologies Co., Ltd. EVENT MANAGEMENT METHOD AND APPARATUS

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020029670A1 (en) * 2018-08-10 2020-02-13 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatuses for exposure of monitoring event
WO2020221297A1 (en) * 2019-04-30 2020-11-05 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatuses for configuration of monitoring for terminal device
EP4327577A1 (en) * 2021-04-20 2024-02-28 Telefonaktiebolaget LM Ericsson (publ) Methods, network function nodes and computer readable media for event report management
WO2023051772A1 (en) * 2021-09-30 2023-04-06 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for event reporting

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101500287A (zh) * 2009-03-13 2009-08-05 中兴通讯股份有限公司 一种小区重选实现方法、装置以及用户终端
CN101595752A (zh) * 2006-10-02 2009-12-02 沃达方集团有限公司 电信系统中的移动性管理
US20110105153A1 (en) * 2008-03-26 2011-05-05 Telefonaktiebolaget L M Ericsson (Publ) Avoiding excessive signaling during wireless terminal toggling
CN104604289A (zh) * 2012-08-31 2015-05-06 苹果公司 在无线通信中从当前小区到更高优先级小区的快速重选

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101810023B (zh) * 2007-09-26 2014-12-10 日本电气株式会社 无线通信系统和方法
CN101646248B (zh) * 2008-08-07 2011-11-02 华为技术有限公司 封闭用户组信息处理方法、接入控制方法及系统和设备
US9955393B2 (en) * 2014-05-08 2018-04-24 Interdigital Patent Holdings, Inc. Methods and apparatus for selection of dedicated core network
US9930516B2 (en) * 2015-05-15 2018-03-27 Samsung Electronics Co., Ltd. UE monitoring configuration method and apparatus
US10200905B2 (en) * 2016-07-18 2019-02-05 At&T Mobility Ii Llc Method and apparatus for modification of a reporting interval via a network
US11405863B2 (en) * 2016-10-05 2022-08-02 Qualcomm Incorporated Systems and methods to enable combined periodic and triggered location of a mobile device
JP7132950B2 (ja) * 2017-02-13 2022-09-07 マイクロソフト テクノロジー ライセンシング，エルエルシー 共有ｒａｎでのリソース制御

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101595752A (zh) * 2006-10-02 2009-12-02 沃达方集团有限公司 电信系统中的移动性管理
US20110105153A1 (en) * 2008-03-26 2011-05-05 Telefonaktiebolaget L M Ericsson (Publ) Avoiding excessive signaling during wireless terminal toggling
CN101500287A (zh) * 2009-03-13 2009-08-05 中兴通讯股份有限公司 一种小区重选实现方法、装置以及用户终端
CN104604289A (zh) * 2012-08-31 2015-05-06 苹果公司 在无线通信中从当前小区到更高优先级小区的快速重选

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI; HISILICON: "Correction to the Location Reporting with Minimum Reporting Interval", 3GPP DRAFT; S2-1901855, 1 March 2019 (2019-03-01), Santa Cruz - Tenerife , Spain, pages 1 - 2, XP051597534 *
HUAWEI; HISILICON: "Correction to the Location Reporting with Minimum Reporting Interval", 3GPP DRAFT; S2-1901856, 1 March 2019 (2019-03-01), Santa Cruz - Tenerife, Spain, pages 1 - 2, XP051597535 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4250786A4 (en) * 2020-12-31 2024-01-17 Huawei Technologies Co., Ltd. EVENT MANAGEMENT METHOD AND APPARATUS

Also Published As

Publication number Publication date
US12028931B2 (en) 2024-07-02
JP7451667B2 (ja) 2024-03-18
US20210377721A1 (en) 2021-12-02
JP2022521224A (ja) 2022-04-06
CN111586583A (zh) 2020-08-25
CN114501333A (zh) 2022-05-13
JP7200392B2 (ja) 2023-01-06
CN111586583B (zh) 2022-01-14
EP3911010A4 (en) 2022-03-23
JP2023052012A (ja) 2023-04-11
EP3911010A1 (en) 2021-11-17

Similar Documents

Publication Publication Date Title
WO2020169050A1 (zh) 一种监控事件的方法及装置
CN110268760B (zh) 支持接入控制和移动性管理的方法和装置
US11425538B2 (en) Event monitoring method and apparatus
CN106686561B (zh) 支持移动终接短消息递送的方法和装置
US20210022101A1 (en) Event Subscription Method, Apparatus, and System
TW201640937A (zh) 使用延伸drx系統增強
US9942845B2 (en) Terminating service restriction for user equipments having power saving mode
US20180004582A1 (en) Timers in stateless architecture
US10694350B2 (en) Support of mobile-terminated application services in a mobile system
US20240155316A1 (en) Method and apparatus for event monitoring
JP2018061191A (ja) 制御装置、ページング方法、及びプログラム
BR112020008191A2 (pt) Método e dispositivo de monitoramento, e método e dispositivo de exclusão de registro
US20200336866A1 (en) Method, device, and system for optimizing short message signaling
JP2018074522A (ja) ゲートウェイ装置、移動管理装置、基地局、通信方法、制御方法、ページング方法、及びプログラム
EP2564656B1 (en) Method and apparatuses for receiving a mobility management entity name
JP7376166B2 (ja) 第１のｃｎノード、第１のｃｎノードにおいて実行される方法、及びｕｅにおいて実行される方法
WO2020147717A1 (zh) 配置监控事件的方法、通信装置和通信系统
KR102484158B1 (ko) 서비스 활성화 및 비활성화의 방법, 장치, 컴퓨터 저장 매체
EP4124129A1 (en) Quota in network slices
WO2019196773A1 (zh) 一种事件监控方法及装置
WO2020029670A1 (en) Methods and apparatuses for exposure of monitoring event
WO2014180405A1 (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: 20759930

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021548611

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020759930

Country of ref document: EP

Effective date: 20210813