WO2020135653A1

WO2020135653A1 - Event monitoring method, device and system

Info

Publication number: WO2020135653A1
Application number: PCT/CN2019/128956
Authority: WO
Inventors: 宗在峰
Original assignee: 华为技术有限公司
Priority date: 2018-12-27
Filing date: 2019-12-27
Publication date: 2020-07-02
Also published as: CN111385785B; CN111385785A

Abstract

The present application provides an event monitoring method, device and system, for use in continuing to perform event monitoring on a terminal after the terminal is deregistered and re-registered to a network. The method comprises: a data management network element receives a first message from a first mobile management network element, the first message being used for indicating that data of a first terminal is deleted from the first mobile management network element, wherein the first message comprises a first identifier and the remaining times of reporting; the first identifier is used for associating a first event; the first event is an event subscribed for a capability exposure network element by the data management network element; the remaining times of reporting is the remaining times of reporting corresponding to the first event of the first terminal; the data management network element receives a second message of a second mobile management network element, the second message being used for indicating that the first terminal is registered in the second mobile management network element; and the data management network element subscribes the first event from the second mobile management network element, and sends the remaining times of reporting to the second mobile management network element.

Description

Event monitoring method, device and system

This application requires the priority of the Chinese patent application submitted to the State Intellectual Property Office of China on December 27, 2018, with the application number 201811613584.4 and the application name as "an event monitoring method, device and system", the entire content of which is cited by reference Incorporated in this application.

Technical field

This application relates to the field of communication technology, and in particular, to an event monitoring method, device, and system.

Background technique

In the existing event subscription process, the capability open network element sends a request message to the data management network element and subscribes to the data management network element for an event, which is an event for a terminal or a terminal group. If the data management network element judges that it cannot detect the event according to the request message sent by the capability opening network element, it sends another request message to the mobile management network element registered for the terminal or member of the terminal group targeted by the event for After subscribing to the event, the mobile management network element monitors the event of the registered terminal. If the event of the registered terminal is detected, the mobility management network element sends a report of the event of the terminal to the capability opening network element.

During the event monitoring process of the mobile management network element, if the terminal deregisters from the network, the mobile management network element will delete the data of the terminal, and then the terminal re-registers with the network, how to continue the event monitoring of the terminal, the existing There is no corresponding method in technology.

Since the terminal device has mobility, the terminal device can be in a network architecture where 4G/5G service capabilities are interoperable (where there is no direct interface between the 4G mobility management entity MME and the 5G access control and mobility management function AMF), from Move from 4G network to 5G network, or from 5G network to 4G network. There is no corresponding method in the prior art to ensure the accuracy of event monitoring of the terminal.

Summary of the invention

The present application provides an event monitoring method, device, and system, so that after the terminal deregisters and re-registers on the network, it can continue to monitor the terminal event.

In a first aspect, the present application provides an event monitoring method. The method includes: a data management network element receives a first message from a first mobile management network element, where the first message is used to instruct data from a first terminal to Deleted from the first mobile management network element, the first message includes a first identifier and the number of remaining reports, the first identifier is used to associate a first event, wherein the first event is the data management network The element is an event subscribed by the capability opening network element, and the remaining report times are the remaining report times corresponding to the first event of the first terminal; the data management network element receives the second from the second mobile management network element Message, the second message is used to instruct the first terminal to register with the second mobility management network element; the data management network element subscribes to the first event from the second mobility management network element; The second mobile management network element sends the remaining report times.

Specifically, the value of the remaining report times is the value of the maximum report times minus the number of times the first event of the first terminal has been reported. The first identifier may be any one or more of the following: an event notification endpoint for the capability opening network element, an event notification endpoint for the data management network element, and a subscription association identifier assigned by the first mobile management network element. Optionally, the first message also includes the identification of the first terminal.

With the method of the first aspect described above, after the first terminal deregisters from the first mobile management network element, the first mobile management network element sends the remaining report times corresponding to the first event of the first terminal to the data management network element. After the first terminal re-registers with the second mobile management network element, the data management network element provides the remaining number of reports to the second mobile management network element, so that the second mobile management network element can continue to perform the first terminal according to the remaining report times Monitoring of the first event.

At the same time, the method can also avoid the sum of the number of reports of the first mobile management network element and the second mobile management network element, exceeding the maximum number of reports corresponding to the first event of the first terminal, and ensuring the accuracy of event monitoring.

In a first possible design of the first aspect, when the first event is directed to the first terminal, the data management network element subscribes to the first event from the second mobile management network element, and Sending the remaining report times to the second mobility management network element includes: the data management network element sending a first request message to the second mobility management network element, the first request message is used to send Two mobile management network elements subscribe to the first event, and the first request message includes the remaining number of reports.

Specifically, the first request message includes second subscription information of the first event, and the second subscription information of the first event includes an event identifier corresponding to the first event, an identifier of the first terminal, an event notification endpoint of the capability opening network element, and a remaining report frequency.

Through the above first possible design solution, because the first event is directed to the first terminal, the data management network element has not subscribed to the first event from the second mobile management network element before receiving the second message, so the data management network After receiving the second message and learning that the first terminal is registered with the second mobility management network element, the element sends a first request message to the second mobility management network element. Through the first request message, the data management network element not only subscribes to the second mobile management network element for the first event, but also sends the remaining report times corresponding to the first event of the first terminal to the second mobile management network element. In this way, the subsequent second mobile management network element can continue to monitor the first terminal for the first event according to the remaining report times according to the first request message.

In a second possible design of the first aspect, when the first event is directed to the terminal group where the first terminal is located, the data management network element subscribes to the second mobile management network element for the first An event, and sending the remaining report times to the second mobility management network element includes: the data management network element sending a first request message to the second mobility management network element, the first request message is used to Subscribe the second event to the second mobility management network element; the data management network element sends a third message to the second mobility management network element, the third message includes the remaining number of reports, the The first identification and the identification of the first terminal.

Specifically, the first request message includes the second subscription information of the first event, the second subscription information of the first event includes the event identifier corresponding to the first event, the identifier of the terminal group where the first terminal is located, and the event notification of the capability opening network element Endpoint, and maximum number of reports. The identifier of the first terminal in the third message and the identifier of the first identifier are used to indicate the terminal and the event corresponding to the remaining number of reports, respectively.

There are two cases in the second possible design:

In case 1 of the second possible design, the step of the data management network element sending the first request message to the second mobile management network element may be that the data management network element receives the second message of the second mobile management network element Execute before the step. Before the data management network element receives the second message of the second mobile management network element, the second mobile management network element is already serving one or more other terminals of the terminal group where the first terminal is located, so the second mobile management network element The network element has received the first request message from the data management network element. After receiving the second message of the second mobile management network element, the data management network element determines that the first event has been subscribed to the second mobile management network element, and determines that the first event monitoring of the first terminal has not ended according to the remaining number of reports To send a third message to the second mobility management network element.

According to the solution in case 1, after receiving the second message, the data management network element determines that the second mobile management network element has subscribed to the first event, thereby sending a third message to the second network element, and providing the remaining report times to the second Mobile management network element. After receiving the third message, the second mobile management network element subsequently determines that the first terminal and the remaining number of reports are associated with the first event corresponding to the terminal group according to the identifier of the first terminal and the first identifier in the third message. In this way, the second mobility management network element can continue to monitor the first event for the first terminal according to the remaining report times.

In case 2 of the second possible design, the step of the data management network element sending the first request message to the second mobile management network element may be after the data management network element receives the second message of the second mobile management network element Execute after the step. After receiving the second message from the second mobile management network element, the data management network element determines that the first event has not been subscribed to the second mobile management network element, so the first request message and the third message are sent to the second mobile management network element .

According to the solution in the second case, after receiving the second message, the data management network element determines that the second mobile management network element is not subscribed to the first event, thereby subscribing to the second mobile management network element through the first request message, The remaining report times are sent to the second mobile management network element through the third message. Subsequently, after receiving the first request message and the third message, the second mobility management network element determines the first terminal and the first number corresponding to the remaining number of reports of the terminal group according to the identifier of the first terminal and the first identifier in the third message Event correlation. In this way, the second mobility management network element can continue to monitor the first event for the first terminal according to the remaining report times.

In a third possible design of the first aspect, when the first event is directed to a terminal group where the first terminal is located, the data management network element receives the After the second message, it is determined that the first event is not subscribed to the second mobile data management network element, then the data management network element subscribes to the first event from the second mobile management network element, and Sending the remaining report times by the second mobility management network element includes: the data management network element sending a first request message to the second mobility management network element, where the first request message is used to send the second request message to the second The mobile management network element subscribes to the first event, and the first request message includes the remaining report times and the identifier of the first terminal.

Specifically, the first request message includes the second subscription information of the first event, the remaining number of reports, and the identifier of the first terminal. Among them, the second subscription information of the first event includes the event identifier corresponding to the first event, the group identifier of the terminal group where the first terminal is located, the event notification endpoint of the capability open network element, and the maximum number of reports, the identifier of the first terminal and the remaining reports The frequency association is used to indicate the terminal corresponding to the remaining report times.

Through the third possible design solution, after receiving the second message, the data management network element determines that the first event has not been subscribed to the second mobile management network element, so that through the first request message, the second mobile management network The yuan subscribes to the first event, and sends the remaining report times to the second mobile management network element. Subsequently, after receiving the first request message, the second mobility management network element determines that the first terminal and the remaining number of reports are associated with the first event corresponding to the terminal group. In this way, the second mobility management network element can continue to monitor the first event for the first terminal according to the remaining report times.

With reference to the first aspect or any one of the first, second, and three possible designs of the first aspect, in a fourth possible design, the data management network element receives the first message from the first mobile management network element Previously, the method further included: the data management network element subscribing to the first mobile management network element for the first event for the capability opening network element.

With reference to the first aspect or any one of the first, second, third, and four possible designs of the first aspect, in a fifth possible design, the method further includes: a data management network element learning capability open network element Subscribe to the second event; the data management network element determines that the capability opening network element needs to be subscribed to the first event according to the second event.

With reference to the fifth possible design of the first aspect, in a sixth possible design, the method further includes: when the second event is directed to the first terminal, the data management network element receives the first mobile management network element After the first message, the data management network element saves the remaining number of reports in the second event subscription information.

With reference to any one of the fifth possible designs of the first aspect, in a seventh possible design, the method further includes: when the second event is directed to the terminal group where the first terminal is located, the data management network element After receiving the first message from the first mobile management network element, the data management network element saves the remaining number of reports in the context of the first terminal without changing the maximum number of reports in the second event subscription information.

With reference to any one of the first aspect or the first, second, third, fourth, fifth, sixth and seventh possible designs of the first aspect, in the eighth possible design, the method further includes: the data After the management network element receives the first message from the first mobile management network element, the data management network element sends the first identification and the remaining number of reports to the data storage network element for requesting to save The first identifier and the remaining report times.

With reference to the eighth possible design of the first aspect, in a ninth possible design of the first aspect, after the data management network element receives the second message from the second mobility management network element, the The method further includes the data management network element querying the data storage network element for the first identification and the remaining number of reports, the data management network element receiving the first identification from the data storage network element And the number of remaining reports.

Through the eighth and ninth possible design schemes, the data management network element sends the first identification to be saved and the number of remaining reports to the data storage network element, reducing the burden on the data management network element and optimizing the data management network element’s Resource management.

In a second aspect, the present application provides an event monitoring method. The method includes: a first mobile management network element receives a second request message from a data management network element, and the second request message is used to subscribe to a first event, The first event is an event reported to a capability opening network element; the first mobility management network element monitors the first terminal for the first event according to the second request message; the first The mobile management network element deletes the data of the first terminal; the first mobile management network element sends a first message to the data management network element, the first message is used to indicate that the data of the first terminal Deleted in the first mobility management network element, the first message includes a first identifier and the number of remaining reports, the first identifier is used to associate the first event, and the remaining number of reports is the number of the first terminal The number of remaining reports corresponding to the first event.

Specifically, the value of the remaining report times is the value of the maximum report times minus the number of times the first event of the first terminal has been reported. Specifically, the first identifier may be any one or more of the following: an event notification endpoint of the capability opening network element, an event notification endpoint of the data management network element, and a subscription association identifier assigned by the first mobile management network element. Optionally, the first message further includes the identifier of the first terminal.

With the method of the second aspect, after deleting the data of the first terminal, the first mobile management network element sends the remaining report times corresponding to the first event of the first terminal to the data management network element, so that the first terminal After the first mobile management network element has registered and re-registered with the second mobile management network element, the data management network element may provide the remaining number of reports to the second mobile management network element. In this way, the subsequent second mobile management network element may continue to monitor the first terminal for the first event according to the remaining report times.

In a first possible design of the second aspect, the second request message includes the maximum number of reports, and then the first mobility management network element performs the process on the first terminal according to the second request message The monitoring of the first event includes: if the first event of the first terminal is detected, the first mobile management network element reports the first event of the first terminal to the capability open network The first mobile management network element deducts the maximum number of reports from the number of times the first event of the first terminal has been reported to obtain the remaining number of reports.

Specifically, the process of obtaining the value of the remaining report times is: each time the first mobility management network element reports the first event to the capability opening network element, the value of the maximum report times is deducted by one.

In a third aspect, the present application provides an event monitoring method. The method includes: a second mobile management network element sends a second message to a data management network element, where the second message is used to instruct the first terminal to Two mobile management network element registration; the second mobile management network element learns that the data management network element subscribes to the first event, the first event is an event reported to the capability opening network element; obtains the remaining number of reports, where The number of remaining reports is the number of remaining reports corresponding to the first event of the first terminal; the second mobility management network element performs a report on the first terminal according to the first event and the number of remaining reports Describe the monitoring of the first event.

Specifically, the value of the remaining report times is the value of the maximum report times minus the number of times the first event of the first terminal has been reported.

Through the method of the third aspect, the first terminal deregisters and re-registers with the second mobile management network element, and the data management network element provides the remaining number of reports to the second mobile management network element, so that the second mobile management network element can follow this The number of remaining reports continues to monitor the first terminal for the first event.

In a first possible design of the third aspect, the second mobile management network element monitoring the first event of the first terminal according to the first event and the remaining number of reports includes: When the first event of the first terminal is detected, the second mobility management sends a fourth message to the capability open network element, where the fourth message is used to report the first event of the first terminal An event; if the number of reports of the first event of the first terminal reaches the remaining number of reports, the second mobility management network element no longer reports the first terminal’s The first event.

Specifically, each time the second mobility management network element reports the first event to the capability opening network element, the value of the remaining reporting times is deducted by one. When the value of the remaining reporting times is reduced to zero, the second mobility management network element The first event of the first terminal is no longer reported to the capability opening network element.

In a second possible design of the third aspect, the second mobile management network element learning that the data management network element subscribes to the first event, and obtaining the remaining number of reports includes: the second mobile management The network element receives a first request message from the data management network element, the first request message is used to subscribe to the first event from the second mobile management network element, and the first request message includes the remaining The number of reports.

There are two cases in the second possible design:

In case one of the second possible design, when the first event is directed to the first terminal, the second mobile management network element receives the first request message from the data management network element, and the first request message includes the remaining number of reports.

Through the solution in the above case 1, because the first event is directed to the first terminal, before the second mobile management network element sends the second message to the data management network element, the data management network element has not subscribed to the second mobile management network element. In an event, the data management network element receives the second message, learns that the first terminal is registered with the second mobile management network element, and sends a first request message to the second mobile management network element. Through the first request message, the data management network element not only subscribes to the second mobile management network element for the first event, but also sends the remaining report times corresponding to the first event of the first terminal to the second mobile management network element. In this way, the subsequent second mobile management network element can continue to monitor the first terminal for the first event according to the remaining report times according to the first request message.

In case 2 of the second possible design, when the first event is directed to the terminal group where the first terminal is located, the second mobility management network element receives the first from the data management network element A request message, the first request message further includes an identifier of the first terminal.

Specifically, the first request message includes the second subscription of the first event, the identifier of the first terminal, and the remaining number of reports. Wherein, the second subscription information of the first event includes the event identifier corresponding to the first event, the identifier of the terminal group where the first terminal is located, the event notification endpoint of the capability open network element, and the maximum number of reports. Wherein, the identifier of the first terminal is associated with the remaining report times, and is used to indicate the terminal corresponding to the remaining report times.

The second mobile management network element continues to monitor the first terminal according to the remaining report times, but does not affect one or more other terminals of the terminal group served by the second mobile management network element. For example, the first The second mobile management network element monitors the first event of one or more other terminals of the terminal group served by the second mobile management network element according to the maximum number of reports, where the one or more other terminals are managed in the second mobile for the first time The terminal where the NE is registered.

Through the solution of the second case above, because the first event is directed to the terminal group where the first terminal is located, and before the second mobile management network element sends the second message to the data management network element, the data management network element does not manage to the second mobile management The network element has subscribed to the first event, so the data management network element receives the second message, learns that the first terminal is registered with the second mobile management network element, and sends a first request message to the second mobile management network element. Through the first request message, the data management network element not only subscribes to the second mobile management network element for the first event, but also sends the remaining report times corresponding to the first event of the first terminal to the second mobile management network element. In this way, the subsequent second mobile management network element can continue to monitor the first terminal for the first event according to the remaining report times according to the first request message.

In a third possible design of the third aspect, when the first event is for a terminal group where the first terminal is located, the second mobile management network element learns that the data management network element subscribes to the The first event, and obtaining the remaining report times include: the second mobility management network element receives a first request message from the data management network element, and the first request message is used to manage the second mobility The network element subscribes to the first event; the second mobility management network element also receives a third message from the data management network element, the third message includes the remaining number of reports, a first identifier, and the first An identifier of the terminal, the first identifier is used to associate the first event.

In the third possible design of the third aspect, there are two cases:

In case one of the third possible design, before the second mobility management network element sends the second message to the data management network element, the second mobility management network element receives the first request message from the data management network element; the second After the mobile management network element sends the second message to the data management network element, the second mobile management network element receives the third message.

According to the solution in case 1, after receiving the second message, the data management network element determines that the first event has been subscribed to the second mobile management network element, thereby sending a third message to the second mobile management network element, and providing the remaining report times to the first 2. Mobile management network element. After receiving the third message, the second mobility management network element determines that the first terminal and the remaining number of reports are associated with the first event corresponding to the terminal group according to the first identifier in the third message. In this way, the subsequent second mobile management network element can continue to monitor the first event for the first terminal according to the remaining report times.

In case 2 of the third possible design, after the second mobility management network element sends the second message to the data management network element, the second mobility management network element receives the first request message and the third from the data management network element news.

According to the solution of the second scenario, after receiving the second message, the data management network element determines that the second mobile management network element is not subscribed to the first event, so that the second mobile management network element is subscribed to the first event through the first request message, and The remaining report times are sent to the second mobile management network element through the third message. After receiving the first request message and the third message, the second mobility management network element determines, according to the first identifier in the third message, that the first terminal and the remaining number of reports are associated with the first event corresponding to the terminal group. In this way, the subsequent second mobile management network element can continue to monitor the first event for the first terminal according to the remaining report times.

Specifically, in the solutions in case 1 and case 2 above, the first request message includes the second subscription information of the first event, where the second subscription information includes the event identifier of the first event, and the terminal group where the first terminal is located The group ID, the capability opening network element event notification endpoint, and the maximum number of reports. The second mobile management network element continues to monitor the first terminal according to the remaining report times, but does not affect one or more other terminals of the terminal group served by the second mobile management network element, for example, the second mobile The management network element monitors the first event for one or more other terminals of the terminal group served by the second mobile management network element according to the maximum number of reports, where the one or more other terminals are in the second mobile management network element for the first time Registered terminal. .

According to a fourth aspect, the present application provides an event monitoring method, which includes: a data management network element subscribing to a first event from a first mobile management network element; and the data management network element receiving from the first mobile management network A first message of the element, the first message is used to instruct the data of the first terminal to be deleted from the first mobility management network element; the data management network element receives the second message from the second mobility management network element, The second message is used to instruct the first terminal to register with the second mobile management network element; the data management network element subscribes to the first event from the second mobile management network element.

According to the method of the fourth aspect, after the first terminal deregisters from the first mobile management network element and re-registers to the second mobile management network element, the data management network element determines that the second mobile management network element is not sent to the second mobile management network element After subscribing to the first event, the second mobile management network element is subscribed to the first event, so that the second mobile management network element can continue to monitor the first terminal for the first event.

In a fifth aspect, the present application provides an event monitoring method. The method includes: a capability opening network element receiving a fifth message from a second mobility management network element, where the fifth message is used to open the network element to the capability Report a first event of the first terminal, the first event being associated with a second event that the capability opening network element subscribes to the data management network element; the capability opening network element determining the first event of the first terminal The number of reported events reaches or exceeds the maximum number of reports; the capability opening network element sends a first indication to the second mobility management network element, where the first indication is used to indicate that the second mobility management network element no longer reports The first event of the first terminal.

Specifically, the fifth message includes a capability opening network element event notification endpoint. Before the capability opening network element receives the fifth message from the second mobile management network element, the method further includes: the capability opening network element further sends a third message to the data management network element. Request message, the third request message is used to subscribe to the second event. The third request message includes the capability open network element event notification endpoint and the maximum number of reports; the capability open network element is notified of the first event and the first event according to the capability open network element event notification endpoint Subscription correlation of two events, and then learn that the first event is correlated with the second event.

In the scenario described in the fourth aspect, if the second mobility management network element reports the first event of the first terminal according to the maximum report times, it may cause the reports of the first mobility management network element and the second mobility management network element The sum of the number of times exceeds the maximum number of reports corresponding to the first event of the first terminal. Through the method of the fifth aspect, the capability open network element receives the first event of the first terminal reported by the mobile management network element, determines whether the number of reports reaches the maximum number of reports, and promptly informs the mobile management network element that it will no longer report the first terminal’s The first incident avoids the occurrence of reporting errors and guarantees the accuracy of incident monitoring.

In a first possible design of the fifth aspect, the first indication is used to indicate that the second mobility management network element no longer reports the first event of the first terminal. Specifically, the first indication is used to indicate the second mobility management network Yuan stops reporting the first event of the first terminal, or instructs to delete the information subscribed to the first event.

In the above first possible design, when the first event is directed to the first terminal, the first indication is used to instruct the second mobility management network element to stop reporting the first event of the first terminal, or delete the first event subscription Information. When the first event is directed to the terminal group where the first terminal is located, the first indication is used to instruct the second mobility management network element to stop reporting the first event of the first terminal. Optionally, when the first event is directed to the terminal group where the first terminal is located, and the first event of all terminals in the terminal group reaches or exceeds the maximum number of reports, the capability open network element sends the data management network element to delete the first In the request for subscription information of two events, further, the data management network element sends a request to delete the second subscription information of the first event to the second mobile management network element.

With reference to the fifth aspect or the first possible design of the fifth aspect, in a second possible design, the capability opening network element sending the first indication to the second mobility management network element includes: the capability opening network element moves to the second The management network element sends a response message to respond to the fifth message, and the response message includes the first indication.

With reference to the fifth aspect or the first and second possible designs of the fifth aspect, in a third possible design, the capability opening network element also sends a cause value to the second mobility management network element, and the cause value is used to indicate the first The number of reports of the first event of the terminal reaches or exceeds the maximum number of reports.

In a sixth aspect, the present application provides an event monitoring method, which includes:

The second mobility management network element receives a fourth request message from the data management network element. The fourth request message is used to subscribe to the first event. The first event is an event reported to the capability opening network element, where the fourth request message includes the largest Number of reports; the second mobile management network element monitors the first terminal for the first event according to the maximum number of reports; if the first event of the first terminal is detected, the second mobile management network element reports the first event to the capability open network element ; The second mobility management network element receives the first indication from the capability opening network element, which is used to indicate that the first event of the first terminal is no longer reported; the second mobility management network element no longer opens the capability opening network according to the first instruction The meta reports the first event of the first terminal.

Through the method of the sixth aspect, after detecting the first event of the first terminal, the second mobility management network element reports the first event to the capability opening network element. After the capability opening network element receives the first event of the first terminal reported by the second mobility management network element, if it is determined that the number of reports reaches or exceeds the maximum number of reporting times, the capability opening network element can promptly notify the second mobility management network element Report the first event of the first terminal, avoid reporting the number of errors, and ensure the accuracy of event monitoring.

In a first possible design of the sixth aspect, the first indication is used to indicate that the first event of the first terminal is no longer reported may specifically be: the first indication is used to indicate that the first event of the first terminal is stopped to be reported, or Instruction to delete the information of the first event subscription.

In the above first possible design, when the first event is directed to the terminal group where the first terminal is located, the first indication is used to instruct to stop reporting the first event of the first terminal, but the second mobility management network element One or more other terminals of the served terminal group do not affect, for example, the second mobility management network element performs the first event on one or more other terminals of the terminal group served by the second mobility management network element according to the maximum number of reports Monitoring, wherein the one or more other terminals are the terminals registered with the second mobile management network element for the first time.

Optionally, when the first event is directed to the terminal group where the first terminal is located, and the first event of all terminals in the terminal group reaches or exceeds the maximum number of reports, the second mobile management network element receives data from the data management network element The request to delete the second subscription information of the first event deletes the second subscription information of the first event.

With reference to the sixth aspect or the first possible design of the sixth aspect, in a second possible design, the second mobility management network element receiving the first indication from the capability openness network element includes: the second mobility management network element receiving The response message from the capability opening network element is used to respond to the fifth message, and the response message includes the first indication.

With reference to the sixth aspect or the first and second possible designs of the sixth aspect, in a third possible design, the second mobility management network element also receives a cause value from the capability opening network element, and the cause value is used to indicate the The number of reports of the first event of a terminal reaches or exceeds the maximum number of reports.

In a seventh aspect, the present application provides a data management network element that has the function of implementing the method described in the first aspect or the fourth aspect. The function can be realized by hardware, or can also be realized by hardware executing corresponding software. The hardware and software include one or more modules corresponding to the above functions.

With reference to the seventh aspect, in a possible design, the structure of the data management network element includes a processor and a transceiver, and the processor is configured to support the data management network element to perform the above-mentioned first aspect or fourth aspect. In the method described, the transceiver is used to support communication between the data management network element and other devices. The data management network element may further include a memory for coupling with the processor, which stores necessary program instructions and data of the data management network element.

In an eighth aspect, the present application provides a mobility management network element that has the function of implementing the method described in the second aspect, the third aspect, or the sixth aspect. The function can be realized by hardware, or can also be realized by hardware executing corresponding software. The hardware and software include one or more modules corresponding to the above functions.

With reference to the eighth aspect, in a possible design, the structure of the mobile management network element includes a processor and a transceiver, and the processor is configured to support the mobile management network element to perform the second aspect, the third aspect, or the first aspect In the method described in the sixth aspect, the transceiver is used to support communication between the mobile management network element and other devices. The mobile management network element may further include a memory for coupling with the processor, which stores necessary program instructions and data of the data management network element.

In a ninth aspect, the present application provides a capability opening network element that has the function of implementing the method described in the fifth aspect above. The function can be realized by hardware, or can also be realized by hardware executing corresponding software. The hardware and software include one or more modules corresponding to the above functions.

With reference to the ninth aspect, in a possible design, the structure of the capability open network element includes a processor and a transceiver, the processor is configured to support the capability open network element to perform the method described in the fifth aspect, The transceiver is used to support communication between the open network element and other devices. The capability opening network element may further include a memory for coupling with the processor, which stores necessary program instructions and data of the capability opening network element.

In a tenth aspect, the present application provides an apparatus (for example, the apparatus may be a chip system). The apparatus includes a processor, and may execute any one or more of the methods described in the first aspect to the sixth aspect.

With reference to the tenth aspect, in a possible design, the device further includes a memory for storing necessary program instructions and data.

In an eleventh aspect, the present application provides a computer program product, which when run on a computer, enables the computer to perform any one or more of the methods described in the first to sixth aspects.

In a twelfth aspect, the present application provides a computer-readable storage medium having instructions stored therein, which when run on a computer, enables the computer to perform the above-mentioned first to sixth aspects Any one or more of the methods described.

In a thirteenth aspect, the present application provides a communication system including the data management network element related to the first aspect, the data management network element related to the fourth aspect, and the mobile management network element related to the second aspect , And one or more of the mobile management network elements involved in the third aspect.

With reference to the thirteenth aspect, in a possible design, the system further includes data management network elements related to the first aspect, or data management network elements related to the fourth aspect, or mobile related to the second aspect The management network element, or other equipment that the mobile management network element involved in the third aspect interacts with, such as a first terminal, a base station, and so on.

According to a fourteenth aspect, the present application provides a communication system, which includes one or more of the capability opening network element related to the fifth aspect and the mobile management network element related to the sixth aspect.

With reference to the fourteenth aspect, in a possible design, the system further includes other devices that interact with the capability opening network element involved in the fifth aspect, or the mobile management network element involved in the sixth aspect, such as the first Terminals, base stations, etc.

BRIEF DESCRIPTION

FIG. 1 is a schematic diagram of a network architecture provided by an embodiment of this application;

2 is a schematic diagram of a 4G network architecture provided by an embodiment of this application;

3 is a schematic diagram of a 5G network architecture provided by an embodiment of this application;

4 is a communication schematic diagram of an event monitoring method in the prior art;

5 is a flowchart of an event monitoring method provided by an embodiment of this application;

6 is a flowchart of yet another event monitoring method provided by an embodiment of this application;

7 is a flowchart of another event monitoring method provided by an embodiment of the present application;

8 is a flowchart of yet another event monitoring method provided by an embodiment of this application;

9 is a flowchart of another event monitoring method provided by an embodiment of the present application;

10 is a flowchart of yet another event monitoring method provided by an embodiment of this application;

11 is a flowchart of another event monitoring method provided by an embodiment of this application;

12 is a flowchart of another event monitoring method provided by an embodiment of this application;

13 is a flowchart of another event monitoring method provided by an embodiment of this application;

14 is a schematic structural diagram of a communication device according to an embodiment of this application;

14a is a schematic structural diagram of a data management network element according to an embodiment of this application;

14b is a schematic structural diagram of a mobile management network element according to an embodiment of this application;

14c is a schematic structural diagram of a capability opening network element provided by an embodiment of this application;

15 is a schematic structural diagram of another communication device according to an embodiment of the present application.

[Corrected according to Rule 26 06.03.2020]
FIG. 16 is a method for event monitoring in a 4G and 5G interworking scenario provided by an embodiment of this application.

detailed description

In order to make the purpose, technical solutions and advantages of the present application more clear, the technical solutions of the embodiments of the present application will be described below with reference to the drawings. In the description of this application, unless otherwise stated, "/" means that the related objects are in an "or" relationship, for example, A/B can mean A or B; "and/or" in this application only It is an association relationship describing associated objects, which means that there can be three kinds of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist at the same time, and B exists alone. Can be singular or plural. And, in the description of the present application, unless otherwise stated, "plurality" means two or more than two. "One or more" or similar expressions refer to any combination of these items, including any combination of single items or plural items, such as one or more of a, b, and c, can Represents: a, b, c, ab, ac, bc, or abc, where a, b, c can be a single or multiple. In addition, in order to facilitate a clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words “first” and “second” are used to distinguish the same or similar items whose functions and functions are basically the same. Those skilled in the art may understand that the words "first" and "second" do not limit the number and execution order, and the words "first" and "second" do not necessarily mean different.

The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: global mobile communication (global system for mobile communications, GSM) system, code division multiple access (code division multiple access (CDMA) system, broadband code division multiple access) (wideband code division multiple access (WCDMA) system, general packet radio service (general packet radio service, GPRS), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE Time division duplex (time division duplex, TDD), universal mobile communication system (universal mobile telecommunication system, UMTS), global interconnected microwave access (worldwide interoperability for microwave access, WiMAX) communication system, future fifth generation (5th generation, 5G) system or new radio (NR), etc.

FIG. 1 is a network architecture provided by an embodiment of this application. As shown in FIG. 1, the network architecture 10 includes: a first terminal (terminal) 101, a first access network device 102, a second access network device 103, a first mobile management network element 104, and a second mobile Management network element 105, data management network element 106, network capability open network element 107 and application function network element 108. Optionally, the network architecture may further include a data storage network element 109. The first terminal 101 may be connected to the first access network device 102 or the second access network device 103. The first access network device 102 and the second access network device 103 can also be connected to the first mobile management network element 104 and the second mobile management network element 105 respectively, and the first access network device 102 can also be connected to the second The network access device 103 is connected. The first mobility management network element 104 and the second mobility management network element 105 may be connected to the data management network element 106, and the first mobility management network element 104 may also be connected to the second mobility management network element 105. The data management network element 106 may be connected to the network capability open network element 107, and the data management network element 106 may also be connected to the data storage network element 109. The network capability open network element 107 may be connected to the application function network element 108. The first mobility management network element 104 and the second mobility management network element 105 can obtain data from the data management network element 106, such as user subscription data. Further, the data management network element 106 may also obtain data from the data storage network element 109 and send it to the first mobility management network element 104 and the second mobility management network element 105. It should be noted that the functions of the first access network device 102, the second access network device 103, the first mobility management network element 104, and the second mobility management network element 105 in the 3GPP communication system are the same, so the following will not be done Differentiated introduction, collectively referred to as access network equipment and mobile management network elements.

Terminal device (TD) 101, abbreviated as terminal, is a device with wireless transceiver function, which can include various handheld devices with wireless communication function, vehicle-mounted devices, wearable devices, computing devices or connected to a wireless modem Other processing equipment, as well as various forms of terminals, mobile stations (MS), terminals, user equipment (UE), soft terminals, etc. Terminals can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; they can also be deployed on the water surface (such as ships, etc.); they can also be deployed in the air (such as airplanes, balloons, and satellites, etc.). For example, mobile phones, tablets, computers with wireless transceiver functions, virtual reality (VR) terminals, augmented reality (AR) terminals, and wireless in industrial control Terminals, wireless terminals in self-driving (self-driving), wireless terminals in telemedicine (remote), wireless terminals in smart grid (smart grid), wireless terminals in transportation safety (transportation safety), smart cities ( wireless terminals in smart cities, wireless terminals in smart homes, etc.

The access network device 102/103 is a device that provides wireless communication functions for terminals. Access network equipment 102/103 includes but is not limited to: 5G next-generation base stations (gNodeB, gNB), evolved node B (evolved node B, eNB), radio network controller (radio network controller, RNC), nodes B (node B, NB), base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved node B, or home node B, HNB), baseband unit ( baseBand unit (BBU), transmission point (transmitting and receiving point, TRP), transmission point (transmitting point, TP), etc.

The mobile management network element 104/105 is mainly used for terminal registration, mobility management, and tracking area update processes in a mobile network. The mobility management network element 104/105 terminates non-access stratum (NAS) messages, completes registration management, connection management, and reachability management, assigns tracking area lists (TA lists), and mobility Management, etc. In the 3rd generation (3G) communication, the mobile management network element 104/105 may be a GPRS service support node (serving GPRS support node, SGSN). In the 4th generation (4th generation, 4G) communication, mobility management The network element 104/105 may be a mobility management entity (MME). In the 5th generation (5G) communication, the mobility management network element 104/105 may be an access and mobility management function ( access and mobility management function (AMF) network element, in future communications such as 6th generation (6th generation, 6G) communication, the mobility management network element 104/105 can still be an AMF network element, or have another name, this application is for This is not limited.

The data management network element 106 is mainly used to store user data, such as contract information and authentication/authorization information. In 4G, the data management network element 106 may be a home subscriber server (HSS). In 5G, the data management network element 106 may be a unified data management (unified data management, UDM) network element. In 6G, the data management network element 106 may still be a UDM network element, or have another name, which is not limited in this application.

The capability opening network element 107 enables the 3GPP network to safely provide service capabilities to the third-party service provider application function network element 108. In 4G, the network capability open network element 107 may be a service capability open function (service capability, function, SCEF) network element, and in 5G, the network capability open network element 107 may be a network open function (network exposure function, NEF) network. Yuan, in future communications such as 6G, the network capability open network element 107 may still be a NEF network element, or have another name, which is not limited in this application.

The application function network element 108 is mainly used to provide application layer information to the 3GPP network and access network capability open network elements. The application function network element 108 may be a service capability server (service capability server, SCS) network element, or may be an application server (application server, AS) network element.

The data storage network element 109 is mainly used for storing subscription data. In 5G, the data storage network element 109 may be a unified data repository (UDR). In future communications such as 6G, the data storage network element 109 may still be a UDR network element, or have another name. This application No limitation.

FIG. 2 is a 4G network architecture provided by an embodiment of this application. As shown in FIG. 2, the network architecture 20 includes: a first terminal 201, a first eNB 202, a second eNB 203, a first MME 204, a second MME 205, HSS 206, SCEF 207, and SCS/AS 208. The first terminal 201 may be connected to the first eNB 202 or the second eNB 203. The first eNB 202 and the second eNB 203 may also be connected to the first MME 204 and the second MME 205, respectively. The first eNB 202 may also be connected to the second eNB 203. The first MME 204 and the second MME 205 can be connected to the HSS 206, and the first MME 204 can also be connected to the second MME 205. HSS206 can be connected with SCEF207. SCS/AS208 can call the service capabilities provided by SCEF208. The first MME 204 and the second MME 205 can obtain data from the HSS 206, for example, user subscription data.

FIG. 3 is a 5G network architecture provided by the application example. As shown in FIG. 3, the network architecture 30 includes: a first terminal 301, a first gNB302, a second gNB303, a first AMF304, a second AMF305, UDM306, NEF307, and SCS/AS308. Further, the network architecture also includes UDR309. The first terminal 301 may be connected to the first gNB302 or the second gNB303. The first gNB302 and the second gNB303 may also be connected to the first AMF304 and the second AMF305, respectively, and the first gNB302 may also be connected to the second gNB303. The first AMF304 and the second AMF305 may be connected to the UDM306, and the first AMF304 may also be connected to the second AMF305. UDM306 can be connected to NEF307, UDM306 can also be connected to UDR309. NEF307 can be connected with SCS/AS308. The first AMF304 and the second AMF305 can obtain data from the UDM306, for example, user subscription data. Further, UDM306 can also obtain data from UDR309 and send it to the first AMF304 and the second AMF305.

In addition, network elements such as AMF, UDM, UDR, and NEF shown in FIG. 3 can also use a service-based interface for interaction. For example, the service interface provided by AMF is Namf; the service interface provided by UDM is Nudm; the service interface provided by UDR is Nudr; the service interface provided by NEF is Nnef.

It can be understood that the foregoing network element or function may be a network element in a hardware device, or may be a software function running on dedicated hardware, or a virtualized function instantiated on a platform (for example, a cloud platform). The above functions can be divided into one or more services, and further, there may be services that exist independently of network functions. In this application, an instance of the above function, or an instance of a service included in the above function, or a service instance that exists independently of a network function may be called a service instance.

First, the related terms involved in the embodiments of the present application are explained:

Subscribe-notify:

Scenario 1: The service consumer subscribes to a service from the service provider, and the service provider notifies the service consumer of the result of the service. In the embodiment of the present application, the service consumer can subscribe to the service provider to monitor the service of the event. When the service provider detects the event, the service consumer is notified of the event, that is, the service consumer Report the incident.

Scenario 2: The service consumer subscribes to a service for another network element from the service provider (ie, the service consumer requests a service on behalf of another network element from the service provider), and the service provider uses the result of the service Notify another network element. In the embodiment of the present application, the consumer of the service subscribes the service provider for the monitoring event service to the service provider for another network element. When the service provider detects the event, it notifies the other network element of the event, that is, to another A network element reports the incident.

Report: When a service provider detects a monitored event, it reports the event to the service consumer. Specifically, the event report can be sent to the service consumer.

It can be understood that from the service consumer or another network element, the above-mentioned event is a subscription event, while for the service provider, the above-mentioned event is a monitored event, or a reported event, expressed in terms of The difference does not mean that the event is different.

Event ID (Event ID(s)): An event may include one or more sub-events, and the event ID is used to identify sub-events. The event identifier may indicate the type of the sub-event, for example, it may be a protocol data unit (protocol data unit, PDU) session release, the terminal moves outside the area of interest, and so on. When any sub-event is subsequently detected, the service provider reports the event to the service consumer or another network element.

Event reporting target (the target of event reporting): used to indicate the target for the event, that is, to detect whether a monitoring event occurs for the target. The event reporting target can be a specific terminal or a terminal group. When the event reporting target is a terminal, the subscribed event is directed to the terminal, that is, when subsequent detection of any sub-event of the event occurs on the terminal, the service provider reports this to the service consumer or another network element event. When the event reporting target is a terminal group, the subscribed event is directed to the terminal group, that is, subsequent detection of one or more terminals in the terminal group, if a terminal in the terminal group is detected In any sub-event in the event, the service provider reports the event of the terminal to the service consumer or another network element.

Among them, when the event reporting target specifies a specific terminal, the event reporting target includes an identification of the terminal, and the identification of the terminal is an identification that can uniquely indicate the terminal. For example, it can be any one or more of the following: mobile station international ISDN number ( mobile station, international ISDN number (MSISDN), public subscription identifier (generic public subscription identifier, GPSI), international mobile subscriber identifier (international mobile subscriber identifier, IMSI), subscription permanent identifier (SUPI).

When the event reporting target specifies a terminal group, the event reporting target includes an identification of the terminal group. The identification of the terminal group is an identification that can uniquely indicate the terminal group. For example, it can be any one or more of the following: external group identification (external group ID), internal group ID (internal group ID).

It should be noted that during the subscription process, the terminal/terminal group identification form may be converted (for example, from GPSI to SUPI), but it can be understood that no matter how the form changes, as long as the terminal can be identified /The terminal group will be referred to as the terminal identification/terminal group identification later in this application document.

Event reporting information (event reporting): may include event reporting mode (event reporting mode) and/or maximum number of reports (maximum number of reports), where the event reporting mode is a mode for reporting events, for example, the report may reach a maximum The number of reports, the report reaching a maximum duration, etc. In the embodiment of the present application, the event reporting mode is that the report reaches a maximum number of reports, and the maximum number of reports is the maximum number of events to which the report is subscribed. It should be noted that the event report information is applicable to an event subscription, that is, an event report target corresponds to an event report information, for example, the event report target is a terminal group, and the terminal group includes a first terminal, a second terminal and For the third terminal, the event report information corresponding to the first terminal, the second terminal, and the third terminal are the same. For example, the first terminal, the second terminal, and the third terminal respectively correspond to the same maximum report times. The event report information is not related to the number of sub-events. For example, the events subscribed for the first terminal include event 1, event 2, and event 3. The maximum number of reports for the event subscribed for the first terminal is 10, and the event is subsequently detected. When any one sub-event is reported, the event is reported. As long as the event is reported up to 10 times, the first terminal is no longer reported on the event.

Event notification endpoint (event notification): used to indicate the object of event report sending, such as reporting monitored events to the service consumer or another network element, and also used for event reports that the service consumer or another network element will receive Associated with event subscription. Wherein, the event notification endpoint includes a notification target address (a notification target address) and/or a notification correlation ID (notification correlation ID).

Figure 4 is an event monitoring method in the prior art, as shown in Figure 4, specifically including the following steps:

S401: The application function network element sends a message 3 to the capability opening network element, so that the capability opening network element receives the message 3 from the application function network element.

This message 3 is used to subscribe to the third event from the capability open network element, including the event identifier corresponding to the third event, event report target 3, event report information 3, and application function network element event notification endpoint.

The third event may include one or more sub-events, for example, including event 1, event 2, and event 3, etc. Correspondingly, the event identifier corresponding to the third event may include the identifier of event 1, the identifier of event 2, and the event 3 Logo, this application does not limit.

The event report target 3 may include an identification of a terminal or an identification of a terminal group.

The event report information 3 may include the event report mode 3 corresponding to the third event and the maximum number of report times 3.

The application function network element event notification endpoint may be used for the application function network element to associate the received event report with the third event subscription, and for instructing to report the event to the application function network element. Wherein, the application function network element event notification endpoint includes the application target network element notification target address, and/or the application function network element notification association identifier.

S402: The capability opening network element saves the third event subscription information.

The third event subscription information includes an event identifier corresponding to the third event in message 3, event report target 3, event report information 3, and application function network element event notification endpoint.

S403: The capability opening network element sends a message 2 to the data management network element, so that the data management network element receives the message 2 from the capability opening network element.

The message 2 is used to subscribe to the second event from the data management network element, including the event identifier corresponding to the second event, the event reporting target 2, the event reporting information 2, and the capability opening network element event notification endpoint.

The second event is determined according to the third event in S401. For example, it may be the same as the third event, or may include one or more sub-events in the third event. Correspondingly, the event identifier corresponding to the second event may be The event identifier corresponding to the third event is the same, and may include one or more of the event identifiers corresponding to the third event. This application does not limit this. For example, the third event includes Event 1, Event 2, and Event 3, and the second event may include any one or more of Event 1, Event 2, and Event 3.

The event report target 2 is determined according to the event report target 3, and may be the same as the event report target 3. Similarly, the event report target 2 may include an identification of a terminal or an identification of a terminal group. If the event report target 2 includes a terminal, the second event is directed to the terminal, and if an identifier of a terminal group is included, the second event is directed to the terminal group.

The event report information 2 may include the event report mode 2 corresponding to the second event and the maximum number of report times 2. The event report information 2 is determined based on the event report information 3, where the value of the maximum report number 2 is the same as the value of the maximum report number 3.

The capability opening network element event notification endpoint can be used by the capability development network element to associate the received event report with the second event subscription, and to instruct to report the event to the capability opening network element. Specifically, the capability opening network element event notification endpoint may include a notification target address of the capability opening network element, and/or a notification association identifier allocated by the capability opening network element.

S404: The data management network element saves the second event subscription information.

The second event subscription information includes an event identifier corresponding to the second event in message 2, event report target 2, event report information 2, and an event notification endpoint of the capability opening network element.

S405: When the data management network element determines that the sub-event included in the second event cannot be detected by itself, it is determined that the capability opening network element subscribes to the mobile management network element for the first event.

The first event is determined according to the second event in S403, including that the data management network element itself cannot detect the sub-event in the second event. For example, it may be the same as the second event, or may include one or more sub-events in the second event. For example, the second event includes event 1, event 2, and event 3. If the data management network element determines that event 1, event 2, and event 3 cannot be detected, the first event includes event 1, event 2, and event 3, that is, the second event The events are the same; or, if the data management network element determines that event 1 cannot be detected, the first event includes event 1.

S406: The data management network element determines the mobile management network element serving the event report target 2 according to the event report target 2.

If the event reporting target 2 includes an identification of a terminal, the data management network element determines the mobile management network element serving the terminal. For example, if the terminal is the first terminal, the data management network element determines the first mobile management network element serving the first terminal.

If the event report target 2 includes an identifier of a terminal group, the data management network element determines to serve one or more mobile management network elements of the terminal group. For example, the terminal group includes a first terminal, a second terminal and a third terminal. If the first mobile management network element serves the first terminal and the third mobile management network element serves the second terminal and the third terminal, the data management The network element determines the first mobility management network element and the third mobility management network element serving the terminal group.

S407: The data management network element sends message 1 to the mobile management network element determined in S406, so that the mobile management network element receives message 1 from the data management network element.

Message 1 is used to subscribe to the first event, including the event identifier corresponding to the first event, event report target 1, event report information 1, and the event notification endpoint of the capability open network element.

In this step, the first event is determined according to the second event in S403. For a similar description, refer to S405. Correspondingly, the event identifier corresponding to the first event may be the same as the event identifier corresponding to the second event, or may include the second One or more of the event identifiers corresponding to the events. This application does not limit this.

Event report target 1 is determined according to event report target 2. The relationship between event report target 1 and event report target 2 is divided into three situations:

Case 1. The event reporting target 1 is the same as the event reporting target 2: the event reporting target 2 includes the identification of a terminal, and the event reporting target 1 includes the identification of the terminal. Correspondingly, the data management network element sends a message 1 to the mobile management network element serving the terminal for subscribing to the first event for the terminal. For example, if the event reporting target 2 includes the identifier of the first terminal, the data management network element sends a message 1 to the mobile management network element serving the first terminal (for example, the first mobile management network element), and the event reporting target 1 in the message 1 Including the identification of the first terminal.

Case 2. The event report target 1 is the same as the event report target 2: the event report target 2 includes an identification of a terminal group, and the event report target 1 includes the identification of the terminal group. Correspondingly, the data management network element may send messages 1 to mobile management network elements serving one or more terminals in the terminal group, respectively, for subscribing to the first event for the terminal group. For example, the event report target 2 includes an identifier of a terminal group (the terminal group includes a first terminal, a second terminal, and a third terminal), a data management network element to the first mobile management network element serving the first terminal, and a service The third mobile management network element of the second terminal and the third terminal respectively sends a message 1, and the event report target 1 in the message 1 includes the identifier of the terminal group.

Case 3. The event reporting target 1 is determined according to the event reporting target 2, which is different from the event reporting target 2: The event reporting target 2 includes an identification of a terminal group, and the data management network element determines one or more corresponding group members according to the identification of the terminal group Terminal identification, event report target 1 includes the identification of the terminal corresponding to one of the terminal group members. Correspondingly, the data management network element separately sends a message 1 for each terminal in the terminal group to subscribe to the first event for a single group member in the terminal group. For example, the data management network element sends a message 1 to the first mobile management network element serving the first terminal, and the event report target 1 in the message 1 includes the identifier of the first terminal, and sends a message to the second terminal and the third terminal. The third mobility management network element sends two messages 1, and the event report target 1 in the two messages 1 includes the identifier of the second terminal or the identifier of the third terminal, respectively, and is used to subscribe to the first event for the second terminal, respectively And the first event for the third terminal.

It can be understood that, in case 1 and case 3 above, the event report target 1 includes an identification of a terminal, that is, the case where the first event is for a terminal, and in case 2 described above, the event report target 1 includes an identification of a terminal group, that is The first event is for a terminal group.

The event report information 1 may include an event report mode 1 corresponding to the first event and a maximum number of report times 1. The event report information 1 is determined based on the event report information 2, wherein the value of the maximum report number 1 is the same as the value of the maximum report number 2.

It should be noted that the data management network element subscribes to the mobile management network element serving the event reporting target 2 as the first event, and the mobile management network element serving the event reporting target 2 stores the first event subscription information, and is To further distinguish the process of the data management network element subscribing to the first event from different mobile management network elements, the data management network element subscribing the first event to the first mobile management network element is called the first subscription of the first event, and moved to the second The management network element subscribing to the first event is called a second subscription for the first event, and the third mobile management network element is subscribed to the first event for a third subscription called the first event. Understandably, this distinction is taken as an example, It does not constitute a limitation on the embodiments of the present application. For convenience of description, the following uses the first mobile management network element to accept the first subscription of the first event and save the first subscription information of the first event as an example.

In an example, optionally, message 1 further includes data management network element event notification endpoint 1, wherein

The data management network element event notification endpoint 1 may be used for the data management network element to associate the received event report with the first subscription of the first event, and for instructing to report the event to the data management network element. Wherein, the data management network element event notification endpoint 1 includes the notification target address 1 of the data management network element, and/or the notification association identifier 1 assigned by the data management network element.

S408: The first mobile management network element saves the first subscription information of the first event, and monitors the first event of the event report target 1 according to the first subscription information of the first event.

In an example, the first mobile management network element allocates a subscription correlation identifier 1 (subscription correlation ID1) for the first subscription of the first event, and the subscription correlation identifier 1 is used to modify or delete the first subscription of the first event in the future , The first subscription associated with the first event.

Wherein, the first subscription information of the first event includes an event identifier corresponding to the first event in message 1, an event report target 1, event report information 1, and an event notification endpoint of the capability opening network element. Optionally, the first subscription information of the first event further includes a subscription association identifier 1 and/or a data management network element event notification endpoint 1.

When the event subscription is for a terminal group, the maximum number of reports is the maximum number of reports for each terminal of the terminal group, that is, the number of reports of the event for each terminal of the terminal group cannot exceed the maximum number of reports, respectively. Therefore, in an example, when the event reporting target 1 includes an identification of a terminal group, the first mobility management network element also stores the maximum number of reporting times 1 in the context of the terminals monitored in the terminal group, respectively.

Optionally, if the event report information 1 includes the maximum number of reporting times 1, the first mobility management network element reports the first event of the first terminal to the capability opening network element once, and deducts the value of the maximum reporting number of the first terminal 1 1. When the number of reports of the first event of the first terminal reaches or exceeds the maximum number of reports, the first mobility management network element no longer reports the first event of the first terminal. It should be noted that the maximum number of reports 1 is not related to whether the first event includes one or more sub-events. For example, the first event includes event 1 and event 2. The maximum number of reports of the first event for the first terminal is 10. If the number of reports of the first event reaches 10, the first mobile management network element A terminal reports the first event.

In the general method of event monitoring described in FIG. 4, the monitored terminal (the first terminal is taken as an example below) is moved from the mobile management network element serving the terminal (hereinafter the first mobile management network element as Example) After mid-deregistration (including explicit deregistration and implicit deregistration), and re-registration to the second mobile management network element, the second mobile management network element cannot continue to monitor the first terminal for the first event.

To solve this problem, on the basis of the method shown in FIG. 4, an embodiment of the present application provides an event monitoring method, which may be executed after S408, as shown in FIG. 5, and specifically includes the following steps:

S501: The first terminal or the network initiates a de-registration process, and the first terminal de-registers from the network.

Specifically, the first terminal sends a deregistration request message to the network, requesting to deregister from the network, or the network determines to deregister the first terminal (including timeout according to network management configuration or implicit deregistration timer).

S502: The first mobile management network element deletes the data of the first terminal, and sends a first message to the data management network element, so that the data management network element receives the first message from the first mobile management network element.

The first message is used to instruct the data of the first terminal to be deleted from the first mobility management network element. The data of the first terminal includes any one or more of subscription information, subscription data, and mobility management context (MM context).

It should be noted that the first message is used to instruct the data of the first terminal to be deleted from the first mobility management network element, and may also be understood to be used to instruct the first terminal to deregister from the first mobility management network element. The data management network element learns that the first terminal deregisters from the first mobility management network element, or learns that the data of the first terminal is deleted from the first mobility management network element.

S503: After receiving the first message, the data management network element sets a flag that the first terminal is deleted (UE purged).

S504: The first terminal re-registers with the network and sends a registration request to the second mobile management network element, so that the second mobile management network element receives the registration request from the first terminal.

It should be noted that the first mobile management network element and the second mobile management network element may be different mobile management network elements, or may be the same mobile management network element, that is, after the first terminal deregisters, it re-registers to the first A mobile management network element, which is not limited in this embodiment of the present application.

S505: The second mobile management network element sends a second message to the data management network element, so that the data management network element receives the second message from the second mobile management network element.

The second message is used to instruct the first terminal to register with the second mobility management network element, and includes the identifier of the first terminal.

S506: The data management network element sends a first request message to the second mobile management network element for subscribing to the first event.

It should be noted that, since the data management network element still retains the information of the second event subscription, the data management network element determines the first according to the event report target 2 in the second event subscription information and the identifier of the first terminal in the first message. The identifier of a terminal is included in the event report target 2, so the data management network element learns that the event monitoring of the first terminal is needed, and subscribes to the first event from the second mobile management network element.

Among them, the first request message includes the event identifier corresponding to the first event, the event report target 1, the event report information 1, the capability opening network element event notification endpoint, and optionally, the data management network element event notification endpoint 1 or data management Network element event notification endpoint 2.

Wherein, the data management network element event notification endpoint 2 is reallocated by the data management network element to the second mobile management network element, and is used by the data management network element to associate the received event report with the second subscription of the first event, and It is used to instruct to report events to the data management network element. Wherein, the data management network element event notification endpoint 2 may include the notification target address 2 of the data management network element and/or the notification association identifier 2 assigned by the data management network element.

S507: The second mobile management network element stores the second subscription information 1 of the first event, and monitors the first terminal for the first event according to the second subscription information 1 of the first event.

Wherein, the second subscription information 1 of the first event includes the event identifier corresponding to the first event in the first request message, the event report target 1, the event report information 1, and the event notification endpoint of the capability opening network element, optionally, it also includes Data management network element event notification endpoint 1 or data management network element event notification endpoint 2.

S508: When the second mobility management network element detects the first event of the first terminal (eg, event 1), the second mobility management network element notifies the endpoint according to the capability opening network element event, and sends a fifth message to the capability opening network element, so that The capability open network element receives the fifth message from the first mobile management network element. The fifth message is used to report the first event of the first terminal to the capability opening network element, including the identification of event 1 and the capability opening network element event notification endpoint.

It should be noted that the first event monitoring of the first terminal described in S507, specifically reporting the detection of the first event of the first terminal described in S508, reporting the first event of the first terminal, and the deduction The entire process of reducing the maximum number of reports until it is no longer reported. The monitoring of the first event in the following embodiments also includes the above steps, which will not be repeated.

Optionally, if the event report information 1 includes the maximum number of reporting times 1, the second mobile management network element deducts the value of the maximum number of reporting times 1 every time the first event of the first terminal is reported to the capability opening network element. When the number of reports of the first event of the first terminal reaches or exceeds the maximum number of reports, the second mobility management network element no longer reports the first event of the first terminal.

In an example, if the first event is directed to a terminal group, and the first terminal is a member of the terminal group, the fifth message also includes the identifier of the first terminal to indicate the terminal corresponding to the report of the first event If the first event is directed to the first terminal, the identifier of the first terminal may not be included in the fifth message, and the endpoint of the capability opening network element event notification may be associated with the first terminal.

Based on the event monitoring method provided in FIG. 5, after the first terminal deregisters from the first mobile management network element and re-registers to the second mobile management network element, the data management network element can resubscribe to the second mobile management network element An event, so that the second mobile management network element can continue to monitor the first terminal for the first event.

However, if the second mobility management network element in this embodiment monitors the first event of the first terminal according to the maximum report times 1 in the first request message, because the first mobility management network element has The first event of the first terminal is monitored according to the maximum number of reports 1, which may result in the first event reporting times of the first mobile management network element for the first terminal, and the second mobile management network element for the first terminal. Number of first event reports, the sum of the two exceeds the maximum number of reports 1, that is, the number of reports of the first event received by the capability open network element from the first terminal exceeds the value of maximum number of reports 3 (maximum number of reports 1 and maximum number of reports 3) The same, refer to the description of FIG. 4 for details).

To solve this problem, based on the above method, the embodiments of the present application provide an event monitoring method, as shown in FIG. 6, which specifically includes the following steps:

S601: The data management network element sends a second request message to the first mobile management network element, so that the first mobile management network element receives the second request message from the data management network element.

The second request message is used to subscribe to the first event, and the first event is an event reported to the capability open network element.

It is understandable that for the data management network element, the first event is an event that is subscribed to the mobile management network element for the capability opening network element, and for the first mobile management network element, the first event is reporting to the capability opening function event.

Specifically, the second request message includes the maximum number of reports 1, which can be referred to the description in S407.

Further, the second request message further includes an event identifier corresponding to the first event, an event reporting target 1, an event reporting mode 1, and an event notification endpoint of an open capability network element. Optionally, it may also include a data management network element event notification endpoint 1. .

Among them, the event identifier corresponding to the first event, the event reporting target 1, the event reporting mode 1, the capability opening network element event notification endpoint and the data management network element event notification endpoint 1, please refer to the description in S407 for details.

S602: The first mobile management network element monitors the first terminal for the first event according to the second request message.

Specifically, if the first event of the first terminal is detected, the first mobility management network element reports the first event of the first terminal to the capability opening network element. Correspondingly, the first mobile management network element deducts the maximum number of reporting times 1 from the number of times the first event of the first terminal has been reported to obtain the remaining number of reports.

For example, when the first event includes multiple sub-events (for example, event 1, event 2, and event 3), when the first mobile management network element detects any one of the sub-events (for example, event 1 or event 2 or event 3), the first event The first event of the terminal is reported to the capability opening network element. Correspondingly, each time the first mobile management network element reports the first event, the value of the maximum number of reports 1 is deducted by 1, so that the remaining number of reports after deducting the number of reports can be obtained.

S603: The first terminal or the network initiates a de-registration process, and the first terminal de-registers from the network.

For details, refer to the description in S501.

S604: The first mobile management network element deletes the data of the first terminal, and sends a first message to the data management network element, so that the data management network element receives the first message from the first mobile management network element.

The first message is used to indicate that the data of the first terminal is deleted from the first mobile management network element, including the first identifier and the remaining number of reports, where the first identifier is used to associate the first event, and the remaining number of reports is the first terminal's The number of remaining reports corresponding to the first event.

It should be noted that the first message is used to instruct the data of the first terminal to delete the first message from the first mobility management network element, and may also be understood to be used to instruct the first terminal to register from the first mobility management network element, Specifically, the data management network element may learn that the first terminal deregisters from the first mobility management network element, or learn that the data of the first terminal is deleted from the first mobility management network element.

It can be understood that the first identifier is used to associate with the first event, and can also be understood to indicate the first event, that is, after the data management network element receives the first identifier, according to the first identifier, the first message and the first The first subscription of the event/subscription of the second event is associated to determine the first event.

Specifically, the first identifier may be any one or more of the capability opening network element event notification endpoint, the data management network element event notification endpoint 1, and the subscription association identifier 1. It can be understood that the foregoing capability opening network element event notification endpoint can be used by the data management network element to associate the first message with the second event subscription, and the first event is determined according to the second event (for details, refer to the figure 4) Therefore, the capability opening network element event notification endpoint can be used to associate with the first event, and can also be used to indicate the first event. The data management network element event notification endpoint 1 described above can be used for the data management network element to associate the received first message with the first subscription of the first event, so it can be used to associate the first event and can also be used to indicate the first An event. The foregoing subscription association identifier 1 is allocated by the first mobile management network element to the first subscription of the first event, and therefore can be used to associate the first event or to indicate the first event. It should be noted that, in the subsequent related processes, the form of the first identification may be changed, for example, the data management network element replaces the received first identification (eg, data management network element event notification endpoint 1) with another The first identifier of the form (capability open network element event notification endpoint). It can be understood that, no matter how the form changes, as long as the first event can be associated or indicated, the subsequent application documents will be referred to as the first identification.

It should be noted that, in the following 4G network shown in FIG. 9, the first message may be a purge terminal request (purge UE request), and in the following 5G network shown in FIG. 10, the first message may be a deregistration request ( Nudm_UECM_deregistration request), it can be understood that no matter how the name of the message changes, as long as the data management network element can be informed that the data of the first terminal is deleted on the first mobile management network element, this application file can be called the first A message.

S605: After receiving the first message from the first mobile management network element, the data management network element obtains the remaining number of reports.

In one example, the data management network element saves the remaining number of reports, for example, locally or on a data storage network element.

S606: The first terminal re-registers with the network and sends a registration request to the second mobile management network element, so that the second mobile management network element receives the registration request from the first terminal.

The registration request includes the identifier of the first terminal. For details, refer to step 504.

S607: The second mobile management network element sends a second message to the data management network element, so that the data management network element receives the second message from the second mobile management network element.

It should be noted that in the 4G network shown in FIG. 9 below, the second message may be a location update request (update location request), and in the 5G network shown in FIG. 10 below, the second message may be a registration request (Nudm_UECM_registration request)2. It can be understood that no matter how the name of the message changes, as long as the data management network element can learn that the first terminal is registered with the second mobile management network element, this application file can be called the second message.

S608: The data management network element subscribes to the first event from the second mobile management network element.

S609: The data management network element sends the remaining report times to the second mobile management network element, so that the second mobile management network element obtains the remaining report times from the data management network element.

In S608 and S609, the data management network element may both subscribe to the first event from the second mobile management network element and send the remaining number of reports to the second mobile management network element through the first request message. Alternatively, the data management network element may subscribe to the first event from the second mobile management network element through the first request message, and send the remaining report times to the second mobile management network element through the third message.

In a solution in which the data management network element performs S608 and S609 through the first request message and the third message, sending the first request message to the second mobile management network element may be before S607 or after S607.

Specifically, S608 and S609 can be implemented in any of the following four ways:

1. When the first event is directed to the first terminal, after S607, the data management network element performs steps S608 and S609 by sending a first request message to the second mobile management network element.

The first request message is used to subscribe to the first event from the second mobile management network element, including the number of remaining reports.

Specifically, the first request message includes the second subscription information 2 of the first event. The second subscription information 2 of the first event includes the event identifier corresponding to the first event, the event report information 1', the event report target 1 and the capability open network element event notification endpoint, optionally, the data management network element event notification endpoint 2. Among them, the maximum report times 1'in the event report information 1'is replaced by the value of the remaining report times. For convenience of explanation, the "remaining report times" is still used in place of the maximum report times 1'in the future.

In this manner, before receiving the second message, the data management network element subscribes to the first event for the first mobile management network element serving the first terminal, and does not subscribe to the first event for the second mobile management network element. After receiving the second message, the data management network element determines to send the first request message to the second mobile management network element, which is used to both subscribe to the first event from the second mobile management network element and provide the remaining number of reports to the second mobile Management network element.

2. When the first event is directed to the terminal group where the first terminal is located, the data management network element performs step S608 to send the first request message to the second mobile management network element before S607, and after S607, the data management network element performs step S609 to The second mobility management network element sends a third message 1.

The first request message is used to subscribe to the second event from the second mobile management network element, and the third message 1 includes the first identification, the identification of the first terminal, and the remaining number of reports.

Specifically, the first request message includes the second subscription information 3 of the first event, and the second subscription information 3 of the first event includes the event identifier corresponding to the first event, the event report target 1, the event report information 1, and the capability opening network element The event notification endpoint, optionally, also includes the data management network element event notification endpoint 1. The first identifier may be the capability opening network element event notification endpoint, or the data management network element event notification endpoint 1.

In this way, before receiving the second message, the data management network element sends a second mobility management service to one or more other terminals (such as the fourth terminal) in the terminal group except the first terminal After the first request message is subscribed to the first event, the second mobile management network element saves the second subscription information 3 of the first event. After receiving the second message, the data management network element determines that the first event has been subscribed to the second mobile management network element, thereby sending a third message 1 to the second mobile management network element, and providing the remaining number of reports to the second mobile Management network element.

It should be noted that, after receiving the third message, the second mobile management network element not only monitors the first event of the re-registered first terminal, but also targets one or A plurality of other terminals (for example, the fourth terminal, registered with the second mobile management network element for the first time) monitor the first event. And the second mobile management network element monitors the first terminal for the first event according to the remaining report times, and monitors the fourth terminal for the first event according to the maximum report number 1.

3. When the first event is directed to the terminal group where the first terminal is located, after S607, the data management network element performs step S608 to send the first request message to the second mobile management network element, and performs step S609 to the second mobile management network element Send the third message 2.

The first request message is used to subscribe to the first event from the second mobile management network element, and the third message 2 includes the first identification, the identification of the first terminal, and the remaining number of reports.

Specifically, the first request message includes the second subscription information 3 of the first event. The first identifier may be the capability opening network element event notification endpoint, or the data management network element event notification endpoint 1.

In this manner, before receiving the second message, the data management network element has not subscribed to the first event of the terminal group from the second mobile management network element. After receiving the second message, the data management network element determines that the first event has not been subscribed to the second mobile management network element, so it sends a first request message to the second mobile management network element, subscribes to the first event, and also sends a message to the second mobile The management network element sends a third message 2 to provide the remaining number of reports to the second mobile management network element.

4. When the first event is directed to the terminal group where the first terminal is located, after S607, the data management network element performs steps S608 and S609 by sending a first request message to the second mobile management network element.

The first request message is used to subscribe to the first event from the second mobile management network element, including the number of remaining reports and the identification of the first terminal, and also includes second subscription information 3 of the first event.

In this manner, before receiving the second message, the data management network element has not subscribed to the first event of the terminal group from the second mobile management network element. After receiving the second message, the data management network element determines that the first event has not been subscribed to the second mobile management network element, so it sends a first request message to the second mobile management network element, subscribes to the first event, and reports the number of remaining reports Provided to the second mobile management network element.

It should be noted that in the following 4G network shown in FIG. 9, the first request message may be a monitoring request (monitoring request), and in the following 5G network shown in FIG. 10, the first request message may be a subscription request message ( Namf_EventExposure_subscribe request). Further, the first request message may be a subscription request message. It can be understood that no matter how the name of the message changes, as long as the first event can be subscribed to the second mobile management network element, this application file can be called the first request message.

S610: The second mobile management network element monitors the first terminal for the first event according to the first event and the remaining report times.

Wherein, if a first event of the first terminal is detected (for example, event 1), the second mobility management network element sends a fourth message to the capability opening network element, and the fourth message is used to report the first event of the first terminal, including the event The identification and capability of the 1 open network element event notification endpoint. If the number of reports of the first event of the first terminal reaches the remaining number of reports, the second mobility management network element no longer reports the first event of the first terminal to the capability opening network element.

Specifically, corresponding to the four implementation manners of S608 and S609, the second mobile management network element monitors the first event of the first terminal in the following three ways:

1. Method 1 corresponding to S608 and S609

The second mobility management network element monitors the first terminal for the first event according to the remaining report times according to the first request message.

2. Modes 2 and 3 of the four implementations corresponding to S606 and S607

The second mobility management network element determines that the remaining number of reports is associated with the second subscription information 3 of the first event according to the first identifier in the third message, and determines that the remaining number of reports corresponds to the first terminal according to the identifier of the first terminal, Therefore, the second mobile management network element can monitor the first terminal for the first event according to the remaining report times.

3. Method 4 corresponding to S606 and S607

The second mobility management network element determines that the remaining report times are associated with the second subscription information 3 of the first event according to the first request message, and determines that the remaining report times correspond to the first terminal according to the identifier of the first terminal, so the second mobile The management network element can monitor the first terminal for the first event according to the remaining report times.

It should be noted that, in method 2 or 3, if the second mobile management network element also serves one or more other terminals in the terminal group (for example, the fourth terminal, the first registration with the second mobile management network element), The first event can be monitored for other terminals according to the maximum number of reports 1. The basis for monitoring is the maximum number of reports 1, that is, each time the first event is reported, the number of reports of the first event in the context of the fourth terminal is deducted (the initial value of the number of reports is the maximum number of reports).

By the method shown in FIG. 6, after the first terminal deregisters from the first mobile management network element, the first mobile management network element sends the remaining number of reports corresponding to the first event of the first terminal to the data management network element. After the first terminal re-registers with the second mobile management network element, the data management network element provides the remaining number of reports to the second mobile management network element, so that the second mobile management network element can continue to perform An event monitoring.

At the same time, this method can avoid the situation that the sum of the number of first event reports of the first mobile management network element and the second mobile management network element for the first terminal exceeds the maximum number of report times 1, so that the second mobile management network element can One terminal performs correct event monitoring to ensure the accuracy of event monitoring.

The following describes in detail the event monitoring provided in FIG. 6 in conjunction with FIGS. 7-10 of the specific embodiment.

Based on the embodiment shown in FIG. 6, FIG. 7 is an event monitoring method provided by an embodiment of the present application. Specifically, when the event report target 1 includes an identifier of a terminal (such as a first terminal), that is, the first event When targeting the first terminal, the following steps are included:

S701: After receiving the first message from the first mobile management network element, the data management network element obtains the remaining report times.

In one example, the data management network element locally saves the remaining number of reports, or saves it to the data storage network element.

It can be saved in the following three ways:

1. When the second event is directed to the first terminal, the data management network element locally saves the remaining number of reports.

Specifically, the data management network element saves the remaining report times in the second event subscription information. For example, the data management network element sets the value of the maximum report times 2 in the second event subscription information to the value of the remaining report times, and obtains the updated second event subscription information 2, in order to facilitate the explanation of the connection between the steps, Subsequent use of "remaining report times" will replace the maximum report times 2'of the second event subscription information 2. or

The data management network element stores the remaining report times in the context of the first terminal, that is, the data management network element does not change the value of the maximum report times 2 in the second event subscription information, and stores the remaining report times in the context of the first terminal.

2. When the second event is directed to the terminal group where the first terminal is located, the data management network element locally saves the remaining number of reports.

Specifically, the data management network element saves the remaining report times in the context of the first terminal, that is, the data management network element does not change the value of the maximum report number 2 in the second event subscription information, and saves the remaining reports in the context of the first terminal frequency.

3. When the second event is directed to the first terminal or the terminal group where the first terminal is located, the data management network element requests the data storage network element to save the remaining number of reports.

Specifically, the data management network element sends a message 4 to the data storage network element, so that the data storage network element receives the message 4 from the data storage network element, and the message 4 includes the first identifier and the number of remaining reports. The data storage network element saves the remaining number of reports. Wherein, the first identifier may be an event notification endpoint of the capability opening network element.

It should be noted that when the second event is directed to the first terminal, the data management network element may save the second event subscription information to the data storage network element, and the second event is directed to the terminal group where the first terminal is located. After all terminals in the group are deregistered, the data management network element may save the second event subscription information to the data storage network element.

S702: The first terminal re-registers with the network, and sends a registration request to the second mobile management network element. For details, refer to S606, and no further details are provided.

S703: The second mobile management network element sends a second message to the data management network element. For details, refer to S607, and details are not described here.

S704: The data management network element determines that the second mobile management network element needs to be subscribed to the first event.

Specifically, the data management network element determines that the number of remaining reports corresponds to the first terminal according to the first message, and determines that the number of remaining reports is the number of remaining reports of the first event according to the first identifier. After receiving the second message, the data management network element determines, according to the identifier of the first terminal in the second message, that the first event of the first terminal still has the remaining number of reports, that is, the first event of the first terminal has not been monitored At the end, it is determined that the second mobile management network element needs to be subscribed to the first event.

In one example, corresponding to manner 3 in S701, the data management network element queries the data storage network element for the first identifier and the remaining number of reports.

S705: The data management network element sends a first request message to the second mobile management network element, so that the second mobile management network element receives the first request message from the data management network element.

The first request message is used to subscribe to the first event from the second mobile management network element, including the number of remaining reports. For details, reference may be made to the description of method 1 in S608 and S609, and details are not described.

It should be noted that if the data management network element adopts the method 1 in S701 to save the remaining report times, specifically, the remaining report times are saved in the context of the first terminal, and the value of the maximum report times 2 in the second event subscription information is not changed, During the process of the data management network element sending the first request message to the second mobile management network element, the data management network element replaces the value of the maximum number of reporting times 1 with the value of the remaining number of reporting times, obtains the maximum number of reporting times 1', and sets the maximum The report number 1'is sent to the second mobile management network element. For ease of explanation, the maximum number of reports 1'will be replaced with "remaining reports" in the future.

S706: The second mobile management network element monitors the first terminal for the first event according to the remaining report times according to the first request message.

Specifically, if a first event of the first terminal (for example, event 1) is detected, the second mobility management network element reports the detected first event to the capability opening network element. If the number of reports of the first event of the first terminal reaches the remaining number of reports, the second mobility management network element no longer reports the first event of the first terminal. For other similar descriptions, reference may be made to S610.

Through the method shown in FIG. 7, the data management network element receives the second message, learns that the first terminal is registered with the second mobile management network element, and sends the first request message to the second mobile management network element. Through the first request message, the data management network element not only subscribes to the second mobile management network element for the first event, but also sends the remaining report times corresponding to the first event of the first terminal to the second mobile management network element. In this way, the subsequent second mobile management network element can continue to monitor the first terminal for the first event according to the remaining report times according to the first request message.

Based on the embodiment shown in FIG. 6, FIG. 8 is an event monitoring method provided by an embodiment of the present application. Specifically, when the second event targets the terminal group where the first terminal is located, the first event also targets the terminal group Time, including the following steps:

S801: After receiving the first message from the first mobile management network element, the data management network element obtains the remaining number of reports. In an example, the data management network element saves the remaining number of reports, which can be saved in two ways:

1. The data management network element locally saves the remaining report times.

2. The data management network element requests the data storage network element to save the remaining report times, specifically:

Specifically, the data management network element sends a message 4 to the data storage network element, so that the data storage network element receives the message 4 from the data storage network element, and the message 4 includes the first identifier and the number of remaining reports. The data storage network element saves the remaining number of reports. For a similar description, refer to method 3 in S701.

S802: The first terminal re-registers with the network, and sends a registration request to the second mobile management network element. For details, refer to S606, and no further details are provided.

S803: The second mobile management network element sends a second message to the data management network element. For details, refer to S607, and details are not described here.

S804: The data management network element determines that the number of remaining reports and the identifier of the first terminal need to be provided to the second mobile management network element.

For details, reference may be made to the description in S704, and details are not repeated.

In one example, corresponding to manner 2 in S801, the data management network element queries the data storage network element for the first identifier and the remaining number of reports.

S805: The data management network element subscribes to the first event from the second mobile management network element.

S806: The data management network element sends the remaining report times and the first terminal identification to the second mobile management network element, so that the second mobile management network element receives the remaining report times and the first terminal identification from the data management network element.

In S805 and S806, the data management network element may not only subscribe to the first event from the second mobile management network element through the first request message, but also send the remaining report times to the second mobile management network element. Alternatively, the data management network element may subscribe to the first event from the second mobile management network element through the first request message, and send the remaining report times to the second mobile management network element through the third message.

In the scheme in which the data management network element performs S805 and S806 through the first request message and the third message, sending the first request message to the second mobile management network element may be before S803 or after S803.

Specifically, S805 and S806 can be implemented in the following three ways:

1. The data management network element has sent the first request message to the second mobility management network element before S803, and after S803, the data management network element has sent the third message 1 to the second mobility management network element. For details, reference may be made to the description of method 2 in S608 and S609, and details are not described.

2. After S803, the data management network element sends a first request message and a third message 2 to the second mobile management network element. For details, reference may be made to the description of Mode 3 in S608 and S609, and details are not described.

3. After S803, the data management network element sends a first request message to the second mobile management network element. For details, reference may be made to the description of Mode 4 in S608 and S609, and details are not described.

S807: The second mobile management network element monitors the first terminal for the first event according to the first event and the remaining report times.

Wherein, if a first event of the first terminal is detected (for example, event 1), the second mobile management network element sends a fourth message to the capability opening network element. The fourth message is used to report the first event of the first terminal. Refer to the description in S610, without repeating it.

Corresponding to the three methods in S806, the second mobile management network element monitors the first terminal for the first event, which can be specifically implemented by the following two methods:

1. Corresponding to mode 1 and mode 2 in S805 and S806, for details, please refer to the description of mode 2 in S610.

2. Corresponding to mode 3 in S805 and S806, for details, refer to the description of mode 3 in S610.

Through the method shown in FIG. 8, the first terminal deregisters and re-registers with the second mobile management network element. The second mobile management network element receives the remaining number of reports from the data management network element, and the remaining number of reports continues to the first The terminal monitors the first event. At the same time, this method can avoid the situation that the sum of the number of first event reports of the first mobile management network element and the second mobile management network element for the first terminal exceeds the maximum number of report times 1, so that the second mobile management network element can One terminal performs correct event monitoring to ensure the accuracy of event monitoring.

The following describes the event monitoring method provided in FIG. 6 in detail in conjunction with FIGS. 9-10 of the specific embodiment, and FIG. 9 is a schematic diagram of the method of FIG. 6 applied to a 3G or 4G network, and FIG. 10 is the method of FIG. 6 Schematic diagram applied in 5G network.

It can be understood that the MME network element, AMF network element, HSS network element, UDM network element, SCEF network element, NEF network element, SCS network element, and AS network element described in subsequent embodiments are only examples and do not constitute Limitations on the embodiments of the present application. That is, the MME network element and the AMF network element described later in this application can be replaced by the mobile management network element 104/105, the HSS network element and the UDM network element can be replaced by the data management network element 106, the SCEF network element, and the NEF network element All can be replaced by the capability open network element 107, the SCS network element and the AS network element can be replaced by the application function network element 108, the UDR network element can be replaced by the data storage network element 109, and the MME network element is simply referred to as MME, AMF network element Referred to as AMF, HSS network element as HSS, UDM network element as UDM, SCEF network element as SCEF, NEF network element as NEF, SCS network element as SCS, AS network element as AS, UDR network element as For UDR.

Based on the above embodiment, FIG. 9 is an event monitoring method provided by an embodiment of the present application, which is specifically applied to a 3G or 4G network and includes the following steps:

S901: The first MME/SGSN deletes the data of the first terminal, and sends a terminal delete request (purge UE request) to the HSS, so that the HSS receives the terminal delete request from the first MME/SGSN. The terminal deletion request is used to indicate that the data of the first terminal has been deleted from the first MME/SGSN. The terminal deletion request includes the remaining report times, SCEF ID, and SCEF reference ID.

It should be noted that the SCEF ID and/or SCEF Reference ID correspond to the first identifier in step 604, which may specifically be an event notification endpoint of the capability opening network element.

S902: After receiving the request to delete the terminal from the first MME/SGSN, the HSS obtains the remaining report times.

For details, reference may be made to method 1 and method 2 in S701, and details are not described.

S903: The first terminal re-registers with the network, and sends a registration request to the second MME/SGSN, so that the first MME/SGSN receives the registration request from the first terminal. The registration request includes the identification of the first terminal.

S904: The second MME/SGSN sends a location update request (update location request) to the HSS, so that the HSS receives the location update request from the second MME/SGSN. The location update request is used to instruct the first terminal to register with the second MME/SGSN. Wherein, the location update request includes the identifier of the first terminal.

S905: The HSS determines that it is necessary to subscribe to the first event from the second MME/SGSN according to the identifier of the first terminal, SCEF ID, SCEF Reference ID, and the number of remaining reports.

S906: The HSS sends a monitoring request (monitoring request) to the second MME/SGSN, so that the second MME/SGSN receives the monitoring request from the HSS.

The monitoring request is used to subscribe to the first event from the second MME/SGSN, including the event identifier corresponding to the first event, the event report target 1, the SCEF ID and the SCEF reference ID, and also includes the event report information 1'. Among them, the maximum report times 1'in the event report information 1'is replaced with the value of the remaining report times.

S907: The second MME/SGSN monitors the first terminal for the first event according to the monitoring request.

Specifically, if a first event (for example, event 1) is detected, the second MME/SGSN sends a monitoring instruction (monitor, indication, message) to the SCEF. The monitoring instruction is used to report the first event of the first terminal, including the identifier of the event 1 , SCEF reference ID. If the number of reports of the first event of the first terminal reaches the remaining number of reports, the second MME/SGSN deletes the second subscription information of the first event.

By the method shown in FIG. 9, after the first terminal deregisters from the first MME/SGSN, the first MME/SGSN sends the remaining report times corresponding to the first event of the first terminal to the HSS. After the first terminal re-registers with the second MME/SGSN, the HSS provides the remaining number of reports to the second MME/SGSN, so that the second MME/SGSN can continue to monitor the first terminal according to the remaining number of reports.

Based on the above embodiment, FIG. 10 is an event monitoring method provided by an embodiment of the present application, which is specifically applied to a 5G network and includes the following steps:

S1001: The first AMF deletes the data of the first terminal, and sends a deregistration request (Nudm_UECM_deregistration request) to the UDM, so that the UDM receives the deregistration request from the first AMF. The de-registration request is used to indicate that the data of the first terminal has been deleted from the first AMF, including the number of remaining reports and the first identification.

Specifically, the first identifier may be any one of the following: UDM event notification endpoint 1 (corresponding to the data management network element event notification endpoint 1 in S701), NEF event notification endpoint (corresponding to the capability opening event notification endpoint in S701) 1. AMF subscription association identifier (corresponding to subscription association identifier 1 in S701).

S1002: After the UDM receives the de-registration request from the first AMF, the UDM obtains the remaining report times.

In one example, UDM saves the remaining number of reports locally, or saves to UDR. For details, refer to the three methods in S701. In mode 3, UDM sends an update data request (Nudr_DM_update) request to UDR, so that UDR receives the update data request from UDM. The update data request includes the NEF event notification endpoint and the remaining number of reports. UDR saves the remaining report times.

S1003: The first terminal re-registers with the network, and sends a registration request 1 to the second AMF, so that the second AMF receives the registration request 1 from the first terminal. The registration request 1 includes the identification of the first terminal.

S1004, the second AMF sends a registration request (Nudm_UECM_registration request) 2 to the UDM, so that the UDM receives the registration request 2 from the second AMF. Wherein, the registration request 2 includes the identifier of the first terminal.

S1005: The UDM determines, according to the identifier of the first terminal, the first identifier, and the number of remaining reports, that the number of remaining reports and the identifier of the first terminal need to be provided to the second AMF.

In one example, corresponding to Mode 3 in S1002, the data management network element sends a query request (Nudr_DM_query) to the UDR for querying the NEF notification endpoint and the remaining number of reports.

S1006: UDM subscribes to the first event from the second AMF.

S1007: The UDM sends the remaining number of reports and the identifier of the first terminal to the second AMF, so that the second AMF receives the remaining number of reports from the data management network element and the identifier of the first terminal.

In S1006 and S1007, the UDM can subscribe to the first event from the second AMF through the subscription request message (Namf_EventExposure_subscribe request), and send the remaining report times to the second AMF. Alternatively, the data management network element may subscribe to the first event from the second AMF through the subscription request message, and send the remaining report times to the second AMF through the third message.

In the scheme where the UDM executes S1006 and S1007 through the subscription request message and the third message, sending the subscription request message to the second AMF may be before S1004 or after S1004.

Specifically, S1006 and S1007 can be implemented in the following four ways:

1. The first event is directed to the first terminal, and after S1004, the UDM sends a subscription request message to the second AMF.

For details, refer to method 1 in S608 and S609, and details are not described. In this step, the data management network element event notification endpoint 2 can be the UDM event notification endpoint 2.

2. When the first event is directed to the terminal group where the first terminal is located, UDM has sent a subscription request message to the second AMF before S1004, and after S1004, UDM sends a third message 1 to the second AMF.

For details, refer to method 2 in S608 and S609, and details are not described.

3. When the first event is directed to the terminal group where the first terminal is located, the UDM sends a subscription request message and a third message 2 to the second AMF after S1004.

For details, refer to method 3 in S608 and S609, and details are not described herein.

4. When the first event is directed to the terminal group where the first terminal is located, the UDM sends a subscription request message to the second AMF after S1004.

For details, refer to method 4 in S608 and S609, and details are not described herein.

S1008: The second AMF monitors the first terminal according to the first event and the remaining report times.

Wherein, if a first event (for example, event 1) is detected, the second AMF sends an event notification request (Namf_EventExposure_notifyrequest) to the NEF. This monitoring instruction is used to report the first event of the first terminal, including the event 1 identification, NEF event Notify the endpoint. If the number of reports of the first event of the first terminal reaches the remaining number of reports, the second AMF no longer reports the first event of the first terminal.

Specifically, corresponding to the four implementation modes of S1006 and S1007, the second AMF monitors the first event of the first terminal in the following three ways:

1. Method 1 corresponding to S1006 and S1007

For details, refer to method 1 in S610, and details are not described.

2. Modes 2 and 3 of the four implementations corresponding to S1006 and S1007

For details, refer to method 2 in S610, and details are not described.

3. Method 4 corresponding to S1006 and S1007

For details, refer to method 3 in S610, and details are not described.

By the method shown in FIG. 10, after the first terminal deregisters from the first AMF, the first AMF sends the remaining report times corresponding to the first event of the first terminal to the UDM. After the first terminal re-registers with the second AMF, the UDM provides the second AMF with the remaining report times, so that the second AMF can continue to monitor the first terminal for the first event according to the remaining report times.

In the scenario shown in FIG. 5, there is a problem that the capability opening network element receives the first mobile management network element and the second mobile management network element, and the number of reports of the first event for the first terminal exceeds the maximum number of reports 3. To solve this problem, based on the embodiment of FIG. 5, the embodiment of the present application provides an event monitoring method, as shown in FIG. 11, specifically including the following steps:

S1101: The capability opening network element sends a third request message to the data management network element, so that the data management network element receives the third request message from the capability opening network element.

The third request message is used to subscribe to the second event from the data management network element, including the event identifier corresponding to the second event, the event report target 2, the event report information 2, and the capability opening network element event notification endpoint. The event report information 2 includes the maximum Number of reports 2. For details, reference may be made to the description in S403, and details are not repeated.

S1102: The data management network element subscribes to the first event from the first mobile management network element where the first terminal is located. For details, please refer to the description in S407.

S1103: The first terminal deregisters from the network, re-registers into the network, and sends a registration request to the second mobile management network element. For details, please refer to the description in S501-S504.

S1104: The second mobility management network element sends a second message to the data management network element, so that the data management network element receives the second message from the second mobility management network element.

The second message is used to instruct the first terminal to register with the second mobility management network element, and includes the identifier of the first terminal. For details, please refer to the description in S505.

S1105: The data management network element sends a fourth request message to the second mobile management network element, so that the second mobile management network element receives the fourth request message from the data management network element. The fourth request message is used to subscribe to the first event from the second mobile management network element.

The fourth request message includes the event identifier corresponding to the first event, the event report target 1, the event report information 1 and the event notification endpoint of the capability open network element. The event report information 1 includes the maximum number of reporting times 1, wherein the value of the maximum number of reporting times 1 The value of the maximum report times 3 is the same. For details, reference may be made to the description in S407, which will not be repeated.

S1106: The second mobile management network element monitors the first terminal according to the maximum number of reports 1.

Specifically, if the second mobility management network element detects the first event (eg, event 1) of the first terminal, the second mobility management network element sends a fifth message to the capability opening network element. The fifth message is used to report the first event of the first terminal to the capability opening network element. The fifth message includes the capability opening network element event notification endpoint and the identification of event 1.

In one example, the first event is directed to the terminal group where the first terminal is located, and the fifth message includes the identifier of the first terminal.

S1107: After receiving the fifth message of the second mobility management network element, the capability opening network element determines that the number of reports of the first event of the first terminal reaches or exceeds the maximum number of reports 3.

Specifically, the capability opening network element notifies the endpoint according to the capability opening network element event in the fifth message, learns that the first event is associated with the second event subscription, and then learns that the first event is associated with the second event, thereby determining the first terminal’s Whether the number of reports of an event reaches or exceeds the maximum number of reports3.

It should be noted that in the following 4G network shown in FIG. 9, the fifth message may be a monitoring instruction, and in the following 5G network shown in FIG. 10, the fifth message may be an event notification request.

S1108: The capability opening network element sends a first indication to the second mobility management network element, so that the second mobility management network element receives the first indication from the capability opening network element.

The first indication is used to indicate that the second mobility management network element no longer reports the first event of the first terminal.

In one example, the first indication is used to instruct the second mobility management network element to stop reporting the first event of the first terminal, or instruct the second mobility management network element to delete the first event subscription information.

Specifically, when the first event is directed to the first terminal, the first indication is used to instruct the second mobility management network element to stop reporting the first event of the first terminal, or delete the subscription information of the first event.

When the first event is directed to the terminal group where the first terminal is located, the first indication is used to instruct the second mobility management network element to stop reporting the first event of the first terminal.

In one example, the capability opening network element sends the first indication to the second mobility management network element through the response message of the fifth message.

In an example, the capability opening network element also sends a cause value that reaches or exceeds the maximum number of reporting times 3 to the second mobility management network element. For example, the cause value that reaches the maximum number of reporting times 3 can take the value 0, and The cause value can be 1.

S1109: After receiving the first instruction, the second mobility management network element no longer reports the first event of the first terminal.

Specifically, according to the first instruction, the second mobile management network element stops reporting the first event of the first terminal or deletes the first event subscription information.

In one example, when the first event is directed to the terminal group where the first terminal is located, the first indication is used to instruct the second mobility management network element to stop reporting the first event of the first terminal, if the second mobility management network element Monitoring the first event serving one or more other terminals in the terminal group, the second mobile management network element performs one or more other terminals in the terminal group on the second mobile management network element according to the maximum number of reports Monitoring of the first event, where the one or more other terminals are the terminals registered with the second mobile management network element for the first time. .

Through the above example, after receiving the first instruction, the second mobility management network element will not affect the monitoring of the first event of one or more other terminals on the second mobility management network element.

The following S1110-S1112 are optional steps

S1110: When the first event is directed to the terminal group where the first terminal is located, and the number of reports of the first event of the terminal in the terminal group reaches the maximum number of reports, the capability open network element sends the data management network element to delete the second event subscription information , The data management network element receives the request to delete the second event subscription information from the capability opening network element.

Wherein, the request to delete the subscription information of the second event includes an event notification endpoint of the capability opening network element.

S1111: The data management network element sends a request to delete the first event subscription information to the second mobile management network element, so that the second mobile management network element receives the request to delete the first event subscription information from the data management network element.

S1112: The second mobile management network element deletes the first event subscription information.

Through the method shown in FIG. 11, the capability opening network element determines that the number of reports of the first event of the second mobile management network element for the first terminal has reached or exceeded the maximum number of report times 3, and then sends the first to the second mobile management network element An instruction, indicating that the first event of the first terminal is no longer reported, thereby preventing the second mobile management network element from performing event monitoring exceeding the maximum number of reports.

The following describes the event monitoring method in FIG. 11 in detail with reference to FIGS. 12-13 of the specific embodiment, and FIG. 12 is a schematic diagram of the method of FIG. 11 applied to a 3G or 4G network, and FIG. 13 is a diagram of the method of FIG. 11 applied to Schematic diagram of 5G network.

Based on the embodiment shown in FIG. 11, FIG. 12 is an event monitoring method provided by an embodiment of the present application, which is specifically applied to a 3G or 4G network and includes the following steps:

S1201-S1205: refer to S1101-S1105, without repeat

S1206: When the second MME/SGSN detects the first event (eg, event 1) of the first terminal, the second MME/SGSN sends a monitoring instruction to the SCEF, so that the SCEF receives the monitoring instruction from the second MME/SGSN. The monitoring instruction is used to report the first event of the first terminal to SCEF, including the identification of event 1 and the SCEF reference ID.

S1207: SCEF judges that the number of reports of the first event of the first terminal reaches or exceeds the maximum number of reports 3

Specifically, the SCEF learns that the first event is associated with the second event according to the SCEF reference ID in the monitoring instruction, so as to determine whether the first event of the first terminal reaches or exceeds the maximum number of reports3.

S1208: SCEF sends a first indication to the second MME/SGSN, so that the second MME/SGSN receives the first indication from SCEF. The first indication is used to indicate that the first event of the first terminal is no longer reported.

In one example, the first indication is used to instruct the second MME/SGSN to stop reporting the first event of the first terminal, or instruct the second MME/SGSN to delete the first event subscription information.

In one example, the SCEF sends a first indication to the second MME/SGSN through a monitoring indication response message (monitoring indication response).

The monitoring instruction response message may further include a cause value that reaches or exceeds the maximum number of reporting times 3, for example, a cause value that reaches the maximum number of reporting times 3 may take a value of 0, and a cause value that exceeds the maximum number of reporting times may take a value of 1.

S1209: After receiving the first indication, the second MME/SGSN no longer reports the first event of the first terminal.

Through the method shown in FIG. 12, SCEF determines that the number of reports of the first event by the second MME/SGSN for the first terminal has reached or exceeded the maximum number of reports 3, and then sends a first indication to the second MME/SGSN that the indication is no longer The first event of the first terminal is reported, thereby preventing the second MME/SGSN from performing event monitoring exceeding the maximum number of reports.

Based on the embodiment shown in FIG. 11, FIG. 13 is an event monitoring method provided by an embodiment of the present application, which is specifically applied to a 5G network and includes the following steps:

S1301-S1305: refer to S1101-S1105, without repeating

S1306: When the second AMF detects the first event (eg, event 1) of the first terminal, the second AMF sends an event notification request to the NEF, so that the NEF receives the event notification request from the second AMF. The event notification request is used to report the first event to NEF, including the identification of event 1 and the NEF event notification endpoint.

In one example, the first event is directed to the terminal group where the first terminal is located, and the event notification request includes the identifier of the first terminal.

S1307: The NEF judges that the number of reports of the first event of the first terminal reaches or exceeds the maximum number of reports 3.

Specifically, according to the NEF event notification endpoint in the event notification request, the NEF learns that the first event is associated with the second event, so as to determine whether the first event of the first terminal reaches or exceeds the maximum number of reports3.

S1308: The NEF sends the first indication to the second AMF, so that the second AMF receives the first indication from the NEF. The first indication is used to indicate that the first event of the first terminal is no longer reported.

In one example, the first indication is used to instruct the second AMF to stop reporting the first event of the first terminal, or instruct the second AMF to delete the first event subscription information. For details, refer to the description in S1108, and no further details are provided.

In one example, the NEF sends a first indication to the second AMF through an event notification response message (Namf_EventExposure_notify response). The event notification response message may further include a cause value that reaches or exceeds the maximum number of reporting times 3. For example, the cause value that reaches the maximum number of reporting times 3 may take a value of 0, and the cause value that exceeds the maximum number of reporting times may take a value of 1.

S1309: After receiving the first instruction, the second AMF no longer reports the first event of the first terminal.

In an example, the first event is directed to the terminal group where the first terminal is located. For details, reference may be made to the description in S1109, and details are not described herein.

Through the method shown in FIG. 13, the NEF determines that the number of reports of the first event by the second AMF for the first terminal has reached or exceeded the maximum number of reports 3, and then sends a first indication to the second AMF indicating that the first terminal is no longer reported To prevent the second AMF from performing event monitoring that exceeds the maximum number of reports.

The above mainly introduces the solutions provided by the embodiments of the present application from the perspective of interaction between various network elements. It can be understood that the above data management network element, mobility management network element, and capability opening network element include The hardware structure and/or software module corresponding to each function. Those skilled in the art should be easily aware that, in conjunction with the exemplary units and algorithm steps described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed by hardware or computer software driven hardware depends on the specific application of the technical solution and design constraints. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not exceed the scope of this application.

The embodiments of the present application may divide the function modules of the data management network element, the mobile management network element, and the capability open network element according to the above method examples. For example, each function module may be divided corresponding to each function, or two or more than two The functions are integrated in one processing module. The above integrated modules can be implemented in the form of hardware or software function modules. It should be noted that the division of the modules in the embodiments of the present application is schematic, and is only a division of logical functions. In actual implementation, there may be another division manner.

For example, the above-mentioned network element or function may be realized by the communication device of FIG. 14. As shown in FIG. 14, the communication device 1400 may be a data management network element, a mobile management network element, and a capability open network element. The communication device includes a processing module 1401, a sending module 1402, and a receiving module 1403, and optionally, a storage module 1404. The sending module 1402 and the receiving module 1403 may be the same module, for example, a communication module.

The processing module 1401 is used to control the actions of the above network elements, for example, to support the above network elements to execute the methods and steps provided in the embodiments of the present application. The sending module 1402 is configured to support the network element to send information to other network entities. For example, in the embodiment of the present application, the network element sends information to other network entities. The receiving module 1403 is used to support the network element to receive information sent by other network entities. For example, in the embodiment of the present application, the network element receives information sent by other network entities. The storage unit 1403 is used to store the data and codes of the above network elements.

The communication device 1400 may be a data management network element. FIG. 14a shows a schematic structural diagram of a data management network element 1410. The data management network element includes a processing module 1411, a sending module 1412, and a receiving module 1413. Optionally, it also includes Storage module 1414.

The receiving module 1413 is configured to receive the first message from the first mobile management network element. The first message is used to instruct the data of the first terminal to be deleted from the first mobility management network element. The first message includes a first identifier and the number of remaining reports. The first identifier is used to associate with the first event. The remaining number of reports is the first The number of remaining reports corresponding to the first event of a terminal. For details, refer to S604 in FIG. 6.

The receiving module 1413 is also used to receive the second message from the second mobility management network element. The second message is used to instruct the first terminal to register with the second mobility management network element. For details, refer to S607 in FIG. 6.

The processing module 1411 is configured to subscribe the first event to the second mobile management network element through the sending module 1412 and send the remaining report times to the second mobile management network element. For details, refer to S608 and S609 in FIG. 6.

Since the data management network element provided by the embodiment of the present application can be used in the above event monitoring method, for the technical effects it can obtain, reference may be made to the above method embodiment, which will not be repeated here.

Further, the data management network element can also be used to perform the corresponding steps in FIG. 5, 6, 7, 8, 9, 10, or 11, for details, refer to the description in the foregoing method embodiments. E.g:

The receiving module 1413 may be used to execute S502, S505, S703, S803, S901, S904, S1001, S1004, S1101, and S1107. For details, refer to the description in the above steps.

The processing module 1411 may be used to execute S503, S605, S701, S704, S801, S804, S805, S902, S905, S1002, S1005, and S1006. For details, refer to the description in the above steps.

The sending module 1412 may be used to execute S506, S601, S609, S705, S806, S906, S1007, and S1102. For details, refer to the description in the above steps.

The communication device 1400 may also be a mobile management network element. FIG. 14b shows a schematic structural diagram of a mobile management network element 1420. The mobile management network element includes a processing module 1421, a sending module 1422, and a receiving module 1423. The storage module 1424 is included.

In one embodiment, the mobility management network element 1420 may be used to perform the operation of the first mobility management network element in the foregoing method embodiment, specifically:

The receiving module 1423 is configured to receive the second request message from the data management network element. The second request message is used to subscribe to the first event, and the first event is an event reported to the capability open network element. For details, refer to S601 in FIG. 6.

The processing module 1421 is configured to monitor the first terminal for the first event according to the second request message. For details, refer to S602 in FIG. 6.

The processing module 1421 is configured to delete data of the first terminal. For details, refer to S604 in FIG. 6.

The sending module 1422 is configured to send the first message to the data management network element. The first message is used to instruct the data of the first terminal to be deleted from the first mobility management network element. The first message includes a first identifier and the number of remaining reports, where the first identifier is used to associate the first event, and the remaining number of reports is The number of remaining reports corresponding to the first event corresponding to the first terminal. For details, refer to S604 in FIG. 6.

Further, the mobility management network element can also be used to perform the corresponding steps in FIGS. 5, 6, 9, 10, and 11, for details, refer to the description in the foregoing method embodiments. E.g:

The receiving module 1423 can be used to execute S1102. For details, refer to the description in the above steps.

The processing module 1421 can be used to execute S502, S901, and S1001. For details, refer to the description in the above steps.

The sending module 1422 can be used to execute S502, S901, and S1001. For details, refer to the description in the above steps.

In another embodiment, the mobility management network element 1420 may perform the operation of the second mobility management network element in the foregoing method embodiment, specifically:

The sending module 1422 is configured to send a second message to the data management network element. The second message is used to instruct the first terminal to register with the second mobility management network element. For details, refer to S607 in FIG. 6.

The processing module 1421 is configured to learn that the data management network element subscribes to the first event through the receiving module 1423. The first event is an event reported to the capability opening network element. For details, refer to S608 in FIG. 6.

The processing module 1421 is used to obtain the remaining report times through the receiving module 1423, where the remaining report times are the remaining report times corresponding to the first event of the first terminal, and reference may be made to S609 in FIG. 6 for details.

The processing module 1421 is also used to monitor the first terminal for the first event according to the first event and the remaining report times. For details, refer to S610 in FIG. 6.

Further, the mobility management network element may also perform the corresponding steps in FIGS. 5, 6, 7, 8, 9, 10, 11, 12, or 13, for details, reference may be made to the description in the above method embodiments. E.g:

The sending module 1422 can be used to execute S505, S508, S607, S703, S803, S904, S907, S1004, S1008, S1104, S1106, S1206, and S1306. For details, refer to the description in the above steps.

The processing module 1421 can be used to execute S507, S508, S706, S807, S907, S1008, S1106, S1109, S1112, S1209, and S1309. For details, refer to the description in the above steps.

The receiving module 1423 can be used to execute S504, S506, S606, S702, S705, S802, S806, S903, S906, S1003, S1007, S1103, S1105, S1108, S1111, S1208, S1308, for details, please refer to the description in the above steps .

The communication device 1400 may also be a capability opening network element. FIG. 14c shows a schematic structural diagram of a capability opening network element 1430. The capability opening network element includes a processing module 1431, a sending module 1432, and a receiving module 1433. Includes storage module 1434.

The receiving module 1433 is configured to receive a fifth message from the second mobile management network element. The fifth message is used to report the first event of the first terminal to the capability opening network element. The first event and the capability opening network element report to the data management network For the second event correlation of the meta subscription, please refer to S1106 in FIG. 11 for details.

The processing module 1431 is configured to determine that the number of reports of the first event of the first terminal reaches or exceeds the maximum number of reports. For details, refer to S1107 in FIG. 11.

The sending module 1432 is configured to send a first indication to the second mobility management network element. The first indication is used to indicate that the second mobility management network element no longer reports the first event of the first terminal. For details, refer to S1108 in FIG. 11.

Further, the capability opening network element may also perform the corresponding steps in FIG. 5, 6, 9, 10, 11, 12, or 13, for details, reference may be made to the description in the above method embodiments. E.g

The receiving module 1433 can be used to execute S508, S610, S907, S1008, S1106, S1206, and S1306. For details, refer to the description in the above steps.

The processing module 1431 can be used to execute S1107, S1207, and S1307. For details, refer to the description in the above steps.

The sending module 1432 can be used to execute S1101, S1108, S1110, S1208, and S1308. For details, refer to the description in the above steps.

When the above processing units 1401, 1411, 1421, 1431 can be one or more processors, the sending

units

1402, 1412, 1422, 1432 and the receiving

units

1403, 1413, 1423, 1433 are transceivers, and the storage units 1404, 1414, When 1424 and 1434 are memories, the data management network element, mobility management network element, and capability opening network element involved in the embodiments of the present application may have the structure shown in FIG. 15.

Referring to FIG. 15, the communication device 1500 includes a processor 1501, a transceiver 1502, and optionally, a memory 1503 and a bus 1504. The processor 1501, the transceiver 1502, and the memory 1503 are connected through a bus 1504. The processor 1501 may be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or on-site. Programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the present application. The processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, DSP and microprocessor combinations, and so on. The bus 1504 may be a peripheral component interconnection (peripheral component interconnection, PCI for short) bus or an extended industry standard architecture (extended industry standard architecture, EISA for short) bus, or the like. The bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only a thick line is used in FIG. 15, but it does not mean that there is only one bus or one type of bus.

An embodiment of the present application further provides a chip system 1600, which includes at least one processor 1601 and an interface circuit 1602. The processor 1601 and the interface circuit 1602 are connected.

The processor 1601 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1601 or an instruction in the form of software. The aforementioned processor 1601 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware Components. The methods and steps 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 be any conventional processor or the like.

The interface circuit 1602 can complete the sending or receiving of data, instructions or information. The processor 1601 can process the data, instructions or other information received by the interface circuit 1602, and can send the processing completion information through the interface circuit 1602.

Optionally, the chip system further includes a memory 1603. The memory 1603 may include a read-only memory and a random access memory, and provide operation instructions and data to the processor. A portion of the memory 1603 may also include non-volatile random access memory (NVRAM).

Optionally, the memory 1603 stores executable software and software modules or data structures, and the processor 1603 can execute the corresponding operation by calling an operation instruction stored in the memory (the operation instruction can be stored in the operating system).

Optionally, the chip system may be used in the data management network element, the mobile management network element, and the capability open network element involved in the embodiments of the present application. Optionally, the interface circuit 1602 is used to perform the steps of receiving and sending the data management network element, the mobile management network element, and the capability opening network element in the embodiments shown in FIGS. 5 to 13. The processor 1601 is configured to execute the processing steps of the data management network element, the mobile management network element, and the capability opening network element in the embodiments shown in FIGS. 5 to 13. The memory 1603 is used to store data and instructions of the data management network element, the mobile management network element, and the capability open network element in the embodiments shown in FIGS. 5 to 13.

The embodiments of the present application also provide a computer-readable storage medium. The methods described in the above method embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media may include computer storage media and communication media, and may also include any media that can transfer a computer program from one place to another. A storage medium may be any available medium that can be accessed by a computer.

As an optional design, the computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or use instructions or data structures The required program code is stored in the form of and can be accessed by the computer. Also, any connection is properly termed a computer-readable medium. For example, if you use coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared, radio, and microwave) to transmit software from a website, server, or other remote source, then coaxial cable, fiber optic cable , Twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of medium. As used herein, magnetic disks and optical disks include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and blu-ray disks, where magnetic disks usually reproduce data magnetically, while optical disks reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

An embodiment of the present application also provides a computer program product. The methods described in the above method embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If implemented in software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the above computer program instructions are loaded and executed on the computer, all or part of the processes or functions described in the above method embodiments are generated. The above-mentioned computer may be a general-purpose computer, a dedicated computer, a computer network, a network device, user equipment, or other programmable devices.

The above specific embodiments further describe the purpose, technical solutions and beneficial effects of this application in detail. It should be understood that the above are only the specific embodiments of this application and are not intended to limit the scope of protection of this application. On the basis of the technical solutions of this application, any modifications, equivalent replacements, improvements, etc., shall be included in the scope of protection of this application.

For the 4G and 5G interworking scenarios, the number of reports of the first event of the first terminal will also exceed the maximum number of reports of 3. The following is a combination of specific embodiments shown in Fig. 16.

FIG. 16 shows a flow of monitoring the terminal device based on the initial parameters configured by SCS/AS+AF in UDM+HSS when the existing terminal device moves across the network system. Among them, UDM+HSS can be a fusion node, which means that the node combines the functions of UDM and HSS. SCS/AS+AF can also be a fusion node, indicating that the node combines the functions of SCS and AF, or the functions of AS and AF. The specific process includes:

S1701: The terminal device registers with the first network system.

The first network system may be a 4G network or a 5G network.

S1702: SCS/AS+AF, capability open network element (here can be the fusion node NEF+SCEF, which integrates the functions of NEF and SCEF), user data management network element and the first mobile management network element The parameter configuration process shown.

S1703: The terminal device moves to the second network system, and sends a registration request to the second access network device.

It should be noted that when the second network system is a 5G network, that is, when the terminal device moves from the 4G network to the 5G network, the terminal device sends a registration request to the second access network device. When the second network system is a 4G network, that is, the terminal device moves from the 5G network to the 4G network, the terminal device sends a tracking area update request to the second access network device.

S1704: The second access network device sends a registration request to the second mobile management network element.

S1705: The second mobile management network element sends an identification request to the terminal device.

S1706: The terminal device receives the identification request and sends an identification response to the second mobility management network element.

S1707: The second mobile management network element receives the identification response, and requests the data management network element for the data of the terminal device.

S1708: The data management network element sends data of the terminal device to the second mobile management network element, where the data of the terminal device includes relevant parameters for event monitoring, including the event identifier corresponding to the first event, the event report target 1, and event report information 1 and the event notification endpoint of the capability opening network element. The event report information 1 includes the maximum number of reporting times 1, wherein the value of the maximum number of reporting times 1 is the same as the value of the maximum number of reporting times 3. For details, reference may be made to the description in S407, and no further description will be given.

S1709: The second mobile management network element sends a confirmation message to the user data management network element.

S1710: The second mobile management network element monitors the first terminal according to the maximum number of reports 1.

Specifically, if the second mobility management network element detects the first event (eg, event 1) of the first terminal, the second mobility management network element sends an event notification message to the capability opening network element. The message is used to report the first event of the first terminal to the capability opening network element, and the fifth message includes the capability opening network element event notification endpoint and the identification of event 1.

In one example, the first event is directed to the terminal group where the first terminal is located, and the message includes the identifier of the first terminal.

S1711: After receiving the notification message of the second mobility management network element, the capability opening network element determines that the number of reports of the first event of the first terminal reaches or exceeds the maximum number of reports 3.

Specifically, the capability opening network element notifies the endpoint according to the capability opening network element event in the fifth message, learns that the first event is associated with the second event subscription, and then learns that the first event is associated with the second event, thereby determining the first terminal’s Whether the number of reports of an event reaches or exceeds the maximum number of reports 3, where the description of the fifth message can refer to S508.

S1712: The capability opening network element sends a first indication to the second mobility management network element, so that the second mobility management network element receives the first indication from the capability opening network element.

In an example, the capability opening network element also sends a cause value that reaches or exceeds the maximum number of reporting times 3 to the second mobility management network element. For example, the cause value that reaches the maximum number of reporting times 3 can take the value 0, which exceeds the maximum number of reporting times The cause value can be 1.

S1713: After receiving the first instruction, the second mobile management network element no longer reports the first event of the first terminal.

The following S1714-S1716 are optional steps

S1714: When the first event is directed to the terminal group where the first terminal is located, and the number of reports of the first event of the terminal in the terminal group reaches the maximum number of reports, the capability open network element sends the data management network element to delete the second event subscription information , The data management network element receives the request to delete the second event subscription information from the capability opening network element.

S1715: The data management network element sends a request to delete the first event subscription information to the second mobile management network element, so that the second mobile management network element receives the request to delete the first event subscription information from the data management network element.

S1716: The second mobile management network element deletes the first event subscription information. Through the method shown in FIG. 16, the capability opening network element determines that the number of reports of the first event of the first terminal by the second mobile management network element has reached or exceeded the maximum number of report times 3, and then sends the first to the second mobile management network element An instruction, indicating that the first event of the first terminal is no longer reported, thereby preventing the second mobile management network element from performing event monitoring exceeding the maximum number of reports.

Claims

An event monitoring method is characterized by including:

The data management network element receives a first message from the first mobility management network element, where the first message is used to instruct data of the first terminal to be deleted from the first mobility management network element, and the first message includes the first Identifier and the number of remaining reports, the first identifier is used to associate with a first event, wherein the first event is an event that the data management network element subscribes to a capability opening network element, and the remaining number of report times is the first The number of remaining reports corresponding to the first event of a terminal;

The data management network element receives a second message from a second mobility management network element, where the second message is used to instruct the first terminal to register with the second mobility management network element;

The data management network element subscribes to the first event from the second mobility management network element; and sends the remaining number of reports to the second mobility management network element.
The method according to claim 1, wherein when the first event is directed to the first terminal,

The data management network element subscribing to the first event to the second mobile management network element and sending the remaining number of reports to the second mobile management network element include:

The data management network element sends a first request message to the second mobility management network element, the first request message is used to subscribe to the first event from the second mobility management network element, the first request The message includes the remaining number of reports.
The method according to claim 1, wherein when the first event is directed to a terminal group where the first terminal is located,

The data management network element subscribing to the first event to the second mobile management network element and sending the remaining number of reports to the second mobile management network element include:

The data management network element sends a first request message to the second mobility management network element, and the first request message is used to subscribe to the first event from the second mobility management network element;

The data management network element sends a third message to the second mobility management network element, where the third message includes the remaining number of reports, the first identification, and the identification of the first terminal.
The method according to claim 1, wherein when the first event is directed to a terminal group where the first terminal is located, the method further comprises:

After receiving the second message from the second mobile management network element, the data management network element determines that the first event has not been subscribed to the second mobile data management network element;

The data management network element subscribing to the first event to the second mobile management network element and sending the remaining number of reports to the second mobile management network element include:

The data management network element sends a first request message to the second mobility management network element, the first request message is used to subscribe to the first event from the second mobility management network element, the first request The message includes the remaining report times and the identification of the first terminal.
The method according to any one of claims 1-4, wherein after the data management network element receives the first message from the first mobility management network element, the method further comprises:

The data management network element sends the first identification and the remaining number of reports to the data storage network element for requesting to save the first identification and the number of remaining reports.
The method according to claim 5, wherein after the data management network element receives the second message from the second mobile management network element, the method further comprises:

The data management network element queries the data storage network element for the first identifier and the remaining number of reports, and the data management network element receives the first identification and the remaining number from the data storage network element The number of reports.
An event monitoring method is characterized by including:

The first mobility management network element receives a second request message from the data management network element, where the second request message is used to subscribe to the first event, and the first event is an event reported to the capability opening network element;

The first mobility management network element monitors the first event for the first terminal according to the second request message;

The first mobile management network element deletes the data of the first terminal;

The first mobility management network element sends a first message to the data management network element, where the first message is used to instruct the data of the first terminal to be deleted from the first mobility management network element, the first A message includes a first identifier and remaining report times. The first identifier is used to associate the first event. The remaining report times are the remaining report times corresponding to the first event of the first terminal.
The method according to claim 7, wherein the second request message includes a maximum number of reports,

The first mobile management network element monitoring the first event of the first terminal according to the second request message includes:

If the first event of the first terminal is detected, the first mobility management network element reports the first event of the first terminal to the capability opening network element;

Before the first mobility management network element sends the first message to the data management network element, the method further includes: the first mobility management network element deducts the maximum number of reports from the location of the first terminal. The number of times that the first event has been reported, and the remaining number of reports are obtained.
An event monitoring method is characterized by including:

The second mobility management network element sends a second message to the data management network element, where the second message is used to instruct the first terminal to register with the second mobility management network element;

The second mobile management network element learns that the data management network element subscribes to a first event, and the first event is an event reported to the capability opening network element; obtains the remaining number of reports, wherein the remaining number of reports is the The number of remaining reports corresponding to the first event of the first terminal;

The second mobility management network element monitors the first event for the first terminal according to the first event and the remaining report times.
The method according to claim 9, wherein the second mobile management network element monitoring the first event for the first terminal according to the first event and the remaining number of reports includes:

If the first event of the first terminal is detected, the second mobility management sends a fourth message to the capability opening network element, where the fourth message is used to report the First event

If the number of reports of the first event of the first terminal reaches the remaining number of reports, the second mobility management network element no longer reports the first An event.
The method according to claim 9 or 10, wherein the second mobile management network element learning that the data management network element subscribes to the first event, and obtaining the remaining number of reports includes:

The second mobility management network element receives a first request message from the data management network element, the first request message is used to subscribe to the first event from the second mobility management network element, the first The request message includes the remaining number of reports.
The method according to claim 11, wherein when the first event is directed to a terminal group where the first terminal is located, the first request message further includes an identifier of the first terminal.
The method according to claim 9 or 10, wherein when the first event is directed to a terminal group where the first terminal is located,

The second mobile management network element learning that the data management network element subscribes to the first event, and obtaining the remaining report times includes:

The second mobility management network element receives a first request message from the data management network element, where the first request message is used to subscribe to the first event from the second mobility management network element;

The second mobile management network element receives a third message from the data management network element, the third message includes the remaining number of reports, a first identification, and an identification of the first terminal, the first identification Used to correlate the first event.
An event monitoring method is characterized by including:

The capability opening network element receives a fifth message from the second mobility management network element, the fifth message is used to report the first event of the first terminal to the capability opening network element, the first event and the capability opening network element Correlation of the second event subscribed to the data management network element;

The capability opening network element determines that the number of reports of the first event of the first terminal reaches or exceeds the maximum number of reports;

The capability opening network element sends a first indication to the second mobility management network element, where the first indication is used to indicate that the second mobility management network element no longer reports the first event of the first terminal .
The method according to claim 14, wherein when the first event is directed to the first terminal, the first indication is used to instruct the second mobility management network element to stop reporting the first The first event of a terminal, or delete the information subscribed to by the first event.
The method according to claim 14, wherein when the first event is directed to a terminal group where the first terminal is located, the first indication is used to instruct the second mobility management network element to stop The first event of the first terminal is reported.
The method according to claim 16, wherein when the first event is directed to a terminal group where the first terminal is located, and the number of first event reports of terminals in the terminal group reaches the maximum report Times, the capability opening network element sends a request to delete the second event subscription information to the data management network element.
A data management network element, characterized by comprising a processing module, a receiving module and a sending module;

The receiving module is configured to receive a first message from a first mobility management network element, the first message is used to instruct data of a first terminal to be deleted from the first mobility management network element, and the first message It includes a first identifier and the number of remaining reports. The first identifier is used to associate with a first event, where the first event is an event that the data management network element subscribes to a capability opening network element, and the remaining number of reports is The number of remaining reports corresponding to the first event of the first terminal;

The receiving module is further configured to receive a second message from a second mobility management network element, where the second message is used to instruct the first terminal to register with the second mobility management network element;

The processing module is configured to subscribe the first event to the second mobile management network element through the sending module and send the remaining number of reports to the second mobile management network element.
The data management network element according to claim 18, wherein when the first event is directed to the first terminal, the processing module is configured to send the second mobile management network element to the second mobile management element through the sending module Subscribing to the first event and sending the remaining number of reports to the second mobile management network element include:

The processing module is used to send a first request message to the second mobility management network element through the sending module, and the first request message is used to subscribe to the first event from the second mobility management network element, The first request message includes the remaining number of reports.
The data management network element according to claim 18, wherein when the first event is directed to a terminal group where the first terminal is located, the processing module is used to send the second event to the second The mobile management network element subscribing to the first event, and sending the remaining number of reports to the second mobile management network element include:

The processing module is used to send a first request message to the second mobility management network element through the sending module, and the first request message is used to subscribe to the first event from a second mobility management network element; and The sending module sends a third message to the second mobility management network element, where the third message includes the remaining number of reports, the first identifier, and the identifier of the first terminal.
The data management network element according to claim 18, wherein when the first event is directed to a terminal group where the first terminal is located, the receiving module receives all data from the second mobile management network element After describing the second message,

The processing module is further configured to determine that the first event has not been subscribed to the second mobile data management network element;

The processing module for subscribing to the first event to the second mobile management network element through the sending module and sending the remaining number of reports to the second mobile management network element includes:

The processing module is used to send a first request message to the second mobility management network element through the sending module, and the first request message is used to subscribe to the first event from the second mobility management network element, The first request message includes the remaining report times and the identifier of the first terminal.
The data management network element according to any one of claims 18 to 21, wherein after the receiving module receives the first message from the first mobility management network element,

The sending module is further configured to send the first identification and the remaining number of reports to a data storage network element for requesting to save the first identification and the number of remaining reports.
The data management network element according to claim 21, wherein after the receiving module receives the second message from the second mobile management network element,

The processing module is also used to query the data storage network element for the first identifier and the remaining number of reports;

The receiving module is further configured to receive the first identification and the remaining number of reports from the data storage network element.
A mobile management network element is characterized by comprising: a processing module, a receiving module and a sending module;

The receiving module is configured to receive a second request message from a data management network element, the second request message is used to subscribe to a first event, and the first event is an event reported to a capability opening network element;

The processing module is configured to monitor the first event of the first terminal according to the second request message;

The processing module is configured to delete the data of the first terminal;

The sending module is configured to send a first message to the data management network element, where the first message is used to indicate that data of the first terminal is deleted from the mobile management network element, and the first message includes A first identifier and remaining report times. The first identifier is used to associate the first event. The remaining report times are the remaining report times corresponding to the first event of the first terminal.
The mobile management network element according to claim 24, wherein the second request message includes a maximum number of reports,

The processing module for monitoring the first event on the first terminal according to the second request message includes:

If the first event of the first terminal is detected, the processing module is further configured to report the first event of the first terminal to the capability opening network element through the sending module;

The processing module is further configured to deduct the maximum number of reports from the number of times the first event of the first terminal has been reported to obtain the remaining number of reports.
A mobile management network element, characterized by comprising: a processing module, a receiving module and a sending module;

The sending module is configured to send a second message to the data management network element, where the second message is used to instruct the first terminal to register with the mobile management network element;

The processing module is used to learn that the data management network element subscribes to a first event through the receiving module, the first event is an event reported to the capability opening network element; and is used to obtain the remaining report through the receiving module The number of times, wherein the number of remaining reports is the number of remaining reports corresponding to the first event of the first terminal;

The processing module is further used for monitoring the first event on the first terminal according to the first event and the remaining report times.
The mobile management network element according to claim 26, wherein the processing module is configured to monitor the first event for the first terminal according to the first event and the remaining number of reports includes:

If the first event of the first terminal is detected, the processing module is used to send a fourth message to the capability open network element through the sending module, and the fourth message is used to report the The first event of the first terminal;

If the number of reported first events of the first terminal reaches the number of remaining reports, the processing module is no longer used to report the first terminal’s The first event.
The mobile management network element according to claim 26 or 27, wherein the processing module is used to learn that the data management network element is subscribed to the first event through the receiving module and used to receive The module obtaining the remaining report times includes:

The processing module is configured to receive a first request message from the data management network element through the receiving module, and the first request message is used to subscribe to the first event from the second mobile management network element. The first request message includes the remaining report times.
The mobile management network element according to claim 28, wherein when the first event is directed to a terminal group where the first terminal is located, the first request message further includes an identifier of the first terminal.
The mobile management network element according to claim 26 or 27, wherein when the first event is directed to a terminal group where the first terminal is located, the processing module is used to learn the The data management network element subscribing to the first event and acquiring the remaining report times through the receiving module includes:

The processing module is configured to receive a first request message from the data management network element through the receiving module, and the first request message is used to subscribe to the first event from the second mobile management network element;

The processing module is configured to receive a third message from the data management network element through the receiving module, the third message includes the remaining number of reports, a first identifier, and an identifier of the first terminal, the The first identifier is used to indicate the first event.
A capability open network element is characterized by comprising: a processing module, a receiving module and a sending module;

The receiving module is configured to receive a fifth message from the second mobility management network element, and the fifth message is used to report the first event of the first terminal to the capability opening network element, the first event and all Describe the second event correlation that the capability open network element subscribes to the data management network element

The processing module is configured to determine that the number of reports of the first event of the first terminal reaches or exceeds the maximum number of reports;

The sending module is configured to send a first indication to the second mobility management network element, where the first indication is used to indicate that the second mobility management network element no longer reports the first of the first terminal event.
The capability opening network element according to claim 31, wherein when the first event is directed to the first terminal, the first indication is used to instruct the second mobility management network element to stop reporting The first event of the first terminal, or deleting the information subscribed to by the first event.
The capability opening network element according to claim 31, wherein when the first event is directed to a terminal group where the first terminal is located, the first indication is used to instruct the second mobility management The network element stops reporting the first event of the first terminal.
The method according to claim 33, wherein when the first event is directed to a terminal group where the first terminal is located, and the number of first event reports of terminals in the terminal group reaches the maximum report Times, the sending module is also used to send a request to delete the second event subscription information to the data management network element.
A computer-readable storage medium including instructions which, when run on a computer, cause the computer to perform the method according to any one of claims 1 to 17.
An event monitoring system, comprising a data management network element according to any one of claims 18 to 23, a mobile management network element according to any one of claims 24 to 25, and any one of claims 26 to 30 Any one or more of the mobile management network elements described in one item.