CN112887960A

CN112887960A - Event monitoring method and device

Info

Publication number: CN112887960A
Application number: CN201911207317.1A
Authority: CN
Inventors: 周晓云
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-11-29
Filing date: 2019-11-29
Publication date: 2021-06-01
Anticipated expiration: 2039-11-29
Also published as: CN112887960B

Abstract

The application discloses an event monitoring method and device, relates to the technical field of communication, and solves the problem that when a terminal device moves across a network system, the current value of relevant parameters monitored by an event cannot be acquired, so that the event monitoring report is inaccurate. The specific scheme is as follows: when the terminal device moves from the first network system to the second network system, the user data management network element sends a first request for requesting a current value of a first parameter of a first event to the first network element, receives the current value of the first parameter from the first network element, sends a second request including the current value of the first parameter to the target mobility management network element, and requests the target mobility management network element to monitor the first event based on the current value of the first parameter.

Description

Event monitoring method and device

Technical Field

The present application relates to the field of wireless communication technologies, and in particular, to an event monitoring method and apparatus.

Background

Currently, in a network architecture in which fourth generation (4th generation, 4G)/fifth generation (5th generation, 5G) service capabilities are interconnected, a Service Capability Server (SCS)/Application Server (AS) may perform event monitoring (event monitoring) on a terminal device, for example: monitoring the location of the terminal device, etc. Before event monitoring, related configuration parameters for event monitoring are configured to the MME/AMF by the SCS/AS, and the MME/AMF monitors the event of the terminal device based on the configuration parameters.

For example, when the terminal device is registered to a 4G network of a 4G/5G service capability interworking network architecture, monitoring configuration related parameters provided by the service provider of the third party are received by the MME, such as: monitoring event types, maximum reporting times and the like, performing event monitoring on the terminal device based on monitoring configuration related parameters, subtracting 1 from the maximum reporting times every time an event is reported, and simultaneously storing the residual reporting times in the MME until the times of reporting the event by the MME reaches the maximum reporting times. When the terminal device registers to the 5G network of the network architecture of the 4G/5G service capability interworking, the AMF receives monitoring configuration related parameters provided by the service provider of the third party, such as: and monitoring the event type, the maximum reporting times and the like, performing event monitoring on the terminal device based on monitoring configuration related parameters, subtracting 1 from the maximum reporting times every time an event is reported, and simultaneously storing the residual reporting times in the AMF until the times of reporting the event by the MME reach the maximum reporting times.

As can be seen from the above, in the process of monitoring the event of the terminal device, the value of the remaining report time is dynamically changed and is stored in the mobility management element registered in the terminal device, such as: MME or AMF. Since the terminal device has mobility, the terminal device can move from the 4G network to the 5G network or from the 5G network to the 4G network in a network architecture in which 4G/5G service capabilities interwork. Taking the example that the terminal device moves from the 4G network to the 5G network, after the terminal device moves to the 5G network, the AMF cannot obtain the current value of the remaining reporting times, but performs event monitoring on the terminal device according to the maximum reporting times (i.e. the initial value of the reporting times) configured by the SCS/AS, so that the total number of the finally reported monitoring event reports is greater than the maximum reporting times, which affects the accuracy of the event reports.

Disclosure of Invention

The application provides an event monitoring method and device, and solves the problem that when a terminal device moves across a network system, the current value of a relevant parameter for event monitoring cannot be acquired, and the accuracy of an event monitoring report is reduced.

In order to achieve the purpose, the technical scheme is as follows:

in a first aspect, the present application provides an event monitoring method, including: when the terminal device moves from a first network system to a second network system, the user data management network element sends a first request for requesting a current value of a first parameter of a first event to the first network element; the user data management network element receives a current value of the first parameter from the first network element, sends a second request including the current value of the first parameter to the target mobility management network element, and requests the target mobility management network element to monitor the first event based on the current value of the first parameter.

Based on the method in the first aspect, when the terminal device moves across the network system, the user data management network element requests the first network element for a current value of the first parameter used for monitoring the first event, and sends the current value of the first parameter acquired from the first network element to the target mobility management network element, so that the target mobility management network element continues to monitor the terminal device for the event based on the current value of the first parameter. Therefore, the event monitoring is carried out on the terminal device by the mobile management network element before the terminal device crosses the network system and the mobile management network element after the terminal device crosses the network system based on the continuous value of the same parameter, the accuracy of the event monitoring report is improved, and the problem that the event monitoring report is inaccurate due to the fact that the mobile management network element in a new network system cannot acquire the current value of the parameter and the event monitoring is carried out on the terminal device again based on the initial value of the parameter after the terminal device crosses the network system in the prior art is solved.

In a second aspect, the present application provides a communication device, which may be a user data management network element or a chip or a system on a chip in the user data management network element, or may be a functional module in the user data management network element for implementing the method according to the first aspect or any possible design of the first aspect. The terminal device may implement the functions performed by the user data management network element in the above aspects or in various possible designs, and the functions may be implemented by executing corresponding software through hardware. The hardware or software comprises one or more modules corresponding to the functions. Such as: the communication device includes: a transmitting unit and a receiving unit.

A sending unit configured to send, to a first network element, a first request for requesting a current value of a first parameter of a first event when the terminal apparatus moves from a first network system to a second network system;

a receiving unit, configured to receive a current value of a first parameter from a first network element;

and the sending unit is further configured to send, to the target mobility management network element, a second request that includes the current value of the first parameter and is used for requesting the target mobility management network element to monitor the first event.

The specific implementation manner of the communication apparatus may refer to the behavior function of the user data management network element in the event monitoring method provided in the first aspect or any one of the possible designs of the first aspect. Based on the communication device in the second aspect, when the terminal device moves across the network system, the communication device requests the first network element for the current value of the first parameter used for monitoring the first event, and sends the current value of the first parameter acquired from the first network element to the target mobility management network element, so that the target mobility management network element continues to monitor the terminal device for the event based on the current value of the first parameter. Therefore, the event monitoring is carried out on the terminal device by the mobile management network element before the terminal device crosses the network system and the mobile management network element after the terminal device crosses the network system based on the continuous value of the same parameter, the accuracy of the event monitoring report is improved, and the problem that the event monitoring report is inaccurate due to the fact that the mobile management network element in a new network system cannot acquire the current value of the parameter and the event monitoring is carried out on the terminal device again based on the initial value of the parameter after the terminal device crosses the network system in the prior art is solved.

In a possible design, in combination with the first aspect or the second aspect, the first parameter includes at least one of a number of reports and a reporting interval. The number of reports may refer to the number of remaining reports, the reporting interval may refer to the remaining reporting interval, and so on.

Based on this possible design, it is possible to obtain the current values of parameters whose parameter values dynamically change as the event monitoring advances in real time as the terminal device moves across the network system, such as: the current values of the report times and/or the report intervals are convenient for the mobile management network elements before and after the network system to carry out event monitoring according to continuous parameter values.

A possible design, combining the first aspect or the second aspect or any possible design of the first aspect or any possible design of the second aspect, where the first network element belongs to a first network system and the target mobility management network element belongs to a second network system.

Based on the possible design, the current value of the first parameter can be obtained from the first network element in the first network system and sent to the target mobility management network element in the second network system, so that after the terminal device moves to the second network system, the target mobility management network element monitors the event of the terminal device according to the current value of the first parameter, and the accuracy of event monitoring is improved.

In a possible design, with reference to the first aspect, the second aspect, or any one of the possible designs of the first aspect, or any one of the possible designs of the second aspect, the first network element is an AMF or a network open function network element, and the target mobility management network element is an MME; or, the first network element is an MME or a network open function network element, and the target mobility management network element is an AMF.

In one possible design, in combination with the first aspect or the second aspect or any one of the possible designs of the first aspect or any one of the possible designs of the second aspect, the first request includes an identification of the terminal device; the identification of the terminal device is from the target mobility management network element.

Based on the possible design, the identifier of the terminal device may be carried in the first request and sent to the first network element, so that the first network element queries a current value of the first parameter of the first event according to the identifier of the terminal device, and sends the current value of the first parameter to the target mobility management network element through the communication device.

In a possible design, with reference to the first aspect or the second aspect or any one of the possible designs of the first aspect or any one of the possible designs of the second aspect, the first request includes a configuration identifier of the first event, and the configuration identifier of the first event is used for the first network element to send the current value of the first parameter according to the configuration identifier of the first event.

Based on the possible design, the configuration identifier of the first event may be carried in the first request and sent to the first network element, so that the first network element queries a current value of a first parameter of the first event according to the configuration identifier of the first event, and sends the current value of the first parameter to the target mobility management network element through the communication device.

In a third aspect, the present application provides a communication device, which may be a user data management network element or a chip or a system on chip in the user data management network element. The communication device may implement the functions performed by the user data management network element in each of the above aspects or possible designs, and the functions may be implemented by hardware, such as: in one possible design, the communication device may include: a processor and a transceiver. The processor is configured to send, through the transceiver, a first request for requesting a current value of a first parameter of a first event to the first network element when the terminal device moves from the first network system to the second network system, receive, through the transceiver, the current value of the first parameter from the first network element, and send, to the target mobility management network element, a second request including the current value of the first parameter and for requesting the target mobility management network element to monitor the first event.

In yet another possible design, the terminal device may further include a memory for storing computer-executable instructions and data necessary for the terminal device. The processor executes the computer executable instructions stored by the memory when the terminal device is operating to cause the terminal device to perform the event monitoring method as set forth in the first aspect or any one of the possible designs of the first aspect.

In a fourth aspect, the present application provides a computer-readable storage medium, which may be a readable non-volatile storage medium, and which stores a computer instruction or a program, which when executed on a computer, enables the computer to perform the event monitoring method according to the first aspect or any one of the above possible designs.

In a fifth aspect, the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the event monitoring method of the first aspect described above or any one of the possible designs of the above aspect.

In a sixth aspect, the present application provides a communication apparatus, which may be a user data management network element or a chip or a system on a chip in a user data management network element, including one or more processors and one or more memories. The one or more memories are coupled to the one or more processors and the one or more memories are configured to store computer program code comprising computer instructions which, when executed by the one or more processors, cause the terminal device to perform the event monitoring method as set forth in the first aspect above or any possible design of the first aspect.

In a seventh aspect, the present application provides a chip system comprising one or more processors and one or more memories; one or more memories coupled to the one or more processors, the one or more memories having stored therein computer program code or computer instructions; the computer program code or computer instructions, when executed by the one or more processors, cause the system-on-chip to perform the event monitoring method as set forth in the first aspect or any possible design of the first aspect.

For technical effects brought by any design manner in the third aspect to the seventh aspect, reference may be made to the technical effects brought by the first aspect or any possible design of the first aspect, and details are not repeated.

In an eighth aspect, the present application provides an event monitoring method, including: when the terminal device moves from the first network system to the second network system, the first network element receives a first request for requesting a current value of a first parameter of a first event from the user data management network element, and transmits the current value of the first parameter to the user data management network element according to the first request.

Based on the method in the eighth aspect, when the terminal device moves across the network system, the first network element sends the current value of the first parameter to the user data management network element under the request of the user data management network element, and the user data management network element sends the current value of the first parameter acquired from the first network element to the target mobility management network element, so that the target mobility management network element continues to monitor the event of the terminal device based on the current value of the first parameter. Therefore, the event monitoring is carried out on the terminal device by the mobile management network element before the terminal device crosses the network system and the mobile management network element after the terminal device crosses the network system based on the continuous value of the same parameter, the accuracy of the event monitoring report is improved, and the problem that the event monitoring report is inaccurate due to the fact that the mobile management network element in a new network system cannot acquire the current value of the parameter and the event monitoring is carried out on the terminal device again based on the initial value of the parameter after the terminal device crosses the network system in the prior art is solved.

In one possible design, with reference to the eighth aspect, the first parameter includes at least one of a number of reports and a report interval. The number of reports may refer to the number of remaining reports, the reporting interval may refer to the remaining reporting interval, and so on.

In a possible design, with reference to the eighth aspect or any one of the possible designs of the eighth aspect, the first network element belongs to a first network system, and the target mobility management network element belongs to a second network system.

Based on the possible design, the first network element in the first network system can send the current value of the first parameter to the target mobility management network element in the second network system, so that the target mobility management network element performs event monitoring on the terminal device according to the current value of the first parameter after the terminal device moves to the second network system, and the accuracy of event monitoring is improved.

In a possible design, with reference to the eighth aspect or any possible design of the eighth aspect, the first network element is an AMF or a network open function network element, and the target mobility management network element is an MME; or, the first network element is an MME or a network open function network element, and the target mobility management network element is an AMF.

In one possible design, in combination with the eighth aspect or any one of the possible designs of the eighth aspect, the first request includes an identification of the terminal device; the identification of the terminal device is from the target mobile management network element; the first network element sending a current value of the first parameter to the user data management network element according to the first request, comprising: and the first network element sends the current value of the first parameter to the user data management network element according to the identifier of the terminal device.

Based on the possible design, the first network element may receive a first request carrying an identifier of the terminal device, query a current value of a first parameter of the first event according to the identifier of the terminal device, and send the current value of the first parameter to the target mobility management network element through the communication device.

In a possible design, with reference to the eighth aspect or any one of the possible designs of the eighth aspect, the first request includes a configuration identifier of the first event; the first network element sending a current value of the first parameter to the user data management network element according to the first request, comprising: and the first network element sends the current value of the first parameter to the user data management network element according to the configuration identifier of the first event.

Based on the possible design, the first network element may receive a first request carrying a configuration identifier of the first event, query a current value of a first parameter of the first event according to the configuration identifier of the first event, and send the current value of the first parameter to the target mobility management network element through the communication device.

In a ninth aspect, the present application provides a communication apparatus, which may be a first network element or a chip or a system on chip in the first network element, and may also be a functional module in the first network element for implementing the method according to any possible design of the eighth aspect or the eighth aspect. The communication apparatus may implement the functions performed by the first network element in the above aspects or possible designs, and the functions may be implemented by hardware executing corresponding software. The hardware or software comprises one or more modules corresponding to the functions. Such as: the communication apparatus may include: a receiving unit, a transmitting unit;

a receiving unit configured to receive a first request for requesting a current value of a first parameter of a first event from a user data management network element when the terminal device moves from the first network system to the second network system;

and a sending unit, configured to send the current value of the first parameter to the user data management network element according to the first request.

Based on the communication device described in the ninth aspect, when the terminal device moves across the network system, the communication device sends the current value of the first parameter to the user data management network element under the request of the user data management network element, and the user data management network element sends the current value of the first parameter acquired from the communication device to the target mobility management network element, so that the target mobility management network element continues to monitor the event of the terminal device based on the current value of the first parameter. Therefore, the event monitoring is carried out on the terminal device by the mobile management network element before the terminal device crosses the network system and the mobile management network element after the terminal device crosses the network system based on the continuous value of the same parameter, the accuracy of the event monitoring report is improved, and the problem that the event monitoring report is inaccurate due to the fact that the mobile management network element in a new network system cannot acquire the current value of the parameter and the event monitoring is carried out on the terminal device again based on the initial value of the parameter after the terminal device crosses the network system in the prior art is solved.

In one possible design, with reference to the ninth aspect, the first parameter includes at least one of a number of reports and a report interval. The number of reports may refer to the number of remaining reports, the reporting interval may refer to the remaining reporting interval, and so on.

In a possible design, with reference to the ninth aspect or any one of the possible designs of the ninth aspect, the first network element belongs to a first network system, and the target mobility management network element belongs to a second network system.

In a possible design, with reference to the ninth aspect or any possible design of the ninth aspect, the first network element is an AMF or a network open function network element, and the target mobility management network element is an MME; or, the first network element is an MME or a network open function network element, and the target mobility management network element is an AMF.

In one possible design, in combination with the ninth aspect or any one of the possible designs of the ninth aspect, the first request includes an identification of the terminal device; the identification of the terminal device is from the target mobile management network element; and a sending unit, configured to send the current value of the first parameter to the user data management network element according to the identifier of the terminal device.

Based on the possible design, the communication device may receive a first request carrying an identifier of the terminal device, query a current value of a first parameter of the first event according to the identifier of the terminal device, and send the current value of the first parameter to the target mobility management network element through the communication device.

In a possible design, with reference to the ninth aspect or any one of the possible designs of the ninth aspect, the first request includes a configuration identification of the first event; and a sending unit, configured to send the current value of the first parameter to the user data management network element according to the configuration identifier of the first event.

Based on the possible design, the communication device may receive a first request carrying a configuration identifier of a first event, query a current value of a first parameter of the first event according to the configuration identifier of the first event, and send the current value of the first parameter to the target mobility management network element through the communication device.

In a tenth aspect, the present application provides a communication apparatus, which may be a first network element or a chip in the first network element or a system on chip. The communication apparatus may implement the functions performed by the first network element in the above aspects or possible designs, and the functions may be implemented by hardware, such as: in one possible design, the communication device may include: a processor and a transceiver. A processor, configured to receive, through the transceiver, a first request for requesting a current value of a first parameter of a first event from the user data management network element when the terminal device moves from the first network system to the second network system, and send the current value of the first parameter to the user data management network element according to the first request. In yet another possible design, the communication device may further include a memory for storing computer-executable instructions and data necessary for the communication device. When the communication device is running, the processor executes the computer-executable instructions stored in the memory to cause the communication device to perform the event monitoring method according to any one of the possible designs of the above-mentioned eighth aspect or eighth aspect.

In an eleventh aspect, the present application provides a computer-readable storage medium, which may be a readable non-volatile storage medium, and which stores computer instructions that, when executed on a computer, enable the computer to perform the event monitoring method according to the eighth aspect or any one of the above possible designs.

In a twelfth aspect, the present application provides a computer program product containing instructions that, when run on a computer, enable the computer to perform the event monitoring method according to the eighth aspect or any one of the above possible designs.

In a thirteenth aspect, the present application provides a communication apparatus, which may be a first network element or a chip or a system on a chip in a first network element, comprising one or more processors and one or more memories. The one or more memories are coupled to the one or more processors and the one or more memories are configured to store computer program code comprising computer instructions that, when executed by the one or more processors, cause the communication device to perform the event monitoring method as set forth in any of the possible designs of the above eighth aspect or the eighth aspect.

In a fourteenth aspect, the present application provides a chip system comprising one or more processors and one or more memories; one or more memories coupled to the one or more processors, the one or more memories having stored therein computer program code or computer instructions; the computer program code or computer instructions, when executed by the one or more processors, cause the system-on-chip to perform the event monitoring method as set forth in any one of the possible designs of the above-mentioned eighth aspect or eighth aspect.

For technical effects brought by any design manner of the ninth aspect to the fourteenth aspect, reference may be made to the seventh aspect or any possible design manner of the seventh aspect, and details are not repeated.

In a thirteenth aspect, the present application provides a communication system comprising a user data management network element as described in any of the second to sixth aspects, a first network element as described in any of the eighth to twelfth aspects, and a target mobility management network element.

Drawings

Fig. 1 is a schematic diagram of a network architecture for interworking 4G/5G service capabilities according to an embodiment of the present application;

FIG. 2 is a flow chart illustrating the configuration of parameters related to event monitoring;

FIG. 3 is a schematic diagram of a prior art event monitoring system;

FIG. 4 is a schematic diagram of a terminal device moving across systems;

fig. 5 is a flowchart of an event monitoring method according to an embodiment of the present application;

fig. 6 is a flowchart of another event monitoring method provided in the embodiment of the present application;

fig. 7 is a flowchart of another event monitoring method provided in the embodiment of the present application;

fig. 8 is a flowchart of another event monitoring method provided in the embodiment of the present application;

fig. 9 is a flowchart of yet another event monitoring method according to an embodiment of the present application;

fig. 10 is a schematic diagram illustrating a communication device 100 according to an embodiment of the present disclosure;

fig. 11 is a schematic diagram illustrating a communication device 110 according to an embodiment of the present disclosure;

fig. 12 is a schematic diagram illustrating a communication device 120 according to an embodiment of the present disclosure;

fig. 13 is a schematic composition diagram of a communication system according to an embodiment of the present application.

Detailed Description

Embodiments of the present application will be described in detail below with reference to the accompanying drawings.

The event monitoring method provided by the embodiment of the application can be applied to the network architecture of 4G/5G service capability intercommunication shown in fig. 1, and can also be applied to the sixth generation (6)^thgeneration, 6G) communication system or other communication system, without limitation. Fig. 1 is an example to explain an event monitoring method provided in the embodiment of the present application.

As shown in fig. 1, the network architecture may include: a terminal device, an evolved universal terrestrial Radio Access Network (E-UTRAN), a next generation Radio Access Network (NG-RAN), a mobile management entity (mobility management entity, MME), an Access and mobility management function (AMF), a Unified Data Management (UDM) + Home Subscriber Server (HSS), a Network open function (NEF) + service capability open function (SCEF) +), a service capability server (service capability server, SCS)/application server (application, AS Application Function (AF) + and the like. Wherein "+" indicates a combination, and the 4G network and the 5G network are shared. In this embodiment, the E-UTRAN and the NG-RAN may be referred to AS access network devices, the MME and the AMF may be referred to AS a mobility management entity, the UDM + HSS may be referred to AS a user data management network element, the NEF + SCEF may be referred to AS a network open function network element, and the SCS/AS + AF may be referred to AS an application server, which will not be described herein in detail. The combined network device may also use other names, which is not limited in this embodiment of the present application.

The terminal device in fig. 1 can access the 4G network through the E-UTRAN and the 5G network through the NG-RAN. The E-UTRAN communicates with the MME over the S1 interface, the MME communicates with the UDM + HSS over the S6a interface, and the MME communicates with the NEF + SCEF over the T6a interface. The NG-RAN communicates with the AMF over an N2 interface, the AMF communicates with the UDM + HSS over a Namf interface, and the AMF communicates with the NEF + SCEF over a Namf interface. The SCS/AS + AF communicates with the NEF + SCEF via an Nnef interface, and the SCS/AS + AF invokes the service capability provided by the NEF + SCEF via an Application Programming Interface (API) interface. It should be noted that the interface name between each network element in fig. 1 is only an example, and the interface name may be other names in a specific implementation, which is not specifically limited in this embodiment of the present application.

Here, the terminal apparatus in fig. 1 may be referred to as a User Equipment (UE), a Mobile Station (MS), a mobile terminal apparatus (MT), or the like. Specifically, the terminal device in fig. 2 may be a mobile phone (mobile phone), a tablet computer, or a computer with a wireless transceiving function, and may also be a Virtual Reality (VR) terminal device, an Augmented Reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in unmanned driving, a wireless terminal device in telemedicine, a wireless terminal device in a smart grid, a wireless terminal device in a smart city (smart city), a smart home, or a vehicle-mounted terminal device.

The E-UTRAN, NG-RAN may be used to provide network access services for the terminal devices. The E-UTRAN and NG-RAN can be specifically as follows: AN Access Point (AP), a base station (nodeB, NB), AN enhanced base station (eNB), a next generation base station (NR nodeB, gNB), a Transmission Reception Point (TRP), a transmission point (transmission point, 5G-AN/5G-RAN node may be AN Access Point (AP), a base station (nodeB, NB), AN enhanced base station (eNB), a next generation base station (NR nodeB, gNB), a Transmission Reception Point (TRP), a Transmission Point (TP), or some other access node, etc.

The AMF and the MME are mainly responsible for the operations of access authentication, mobility management, signaling interaction between functional network elements, and the like of the terminal device, such as: and managing the registration state of the user, the connection state of the user, the user registration and network access, the tracking area updating, the cell switching user authentication, the key safety and the like.

The UDM + HSS may be used to hold data for the terminal device, such as: subscription data of the terminal device, data for event monitoring, and other data.

The NEF + SCEF may be used to provide service capabilities to the third party service provider SCS/AS + AF.

The SCS/AS + AF may provide third party services to the user.

It should be noted that fig. 1 is only an exemplary architecture diagram, and the number of devices included therein is not limited. Furthermore, the communication system may comprise, in addition to the devices shown in fig. 1, other devices, such as: a General Packet Radio System (GPRS) service support node (SGSN) in a 4G network, an authentication service function (AUSF) entity and a Network Slice Selection Function (NSSF) entity in a 5G network, and the like, which are not specifically limited in this embodiment of the present invention. The names of the devices and the links in fig. 1 are not limited, and the devices and the links may be named by other names besides the names shown in fig. 1, without limitation.

In the architecture shown in fig. 1, SCS/AS + AF may configure relevant parameters for event monitoring for the terminal device, such AS: the SCS/AS + AF may send the relevant parameters for event monitoring to the core network device, and the core network device monitors the event of the terminal device according to the relevant parameters for event monitoring and reports the monitoring report to the SCS/AS + AF. The following methods shown in fig. 2 to 4 are used to describe the event monitoring process provided by the prior art, and the methods shown in fig. 5 to 9 are used to describe the event monitoring process provided by the embodiment of the present application. The method embodiments corresponding to fig. 2 to 9 are all applicable to the architecture shown in fig. 1.

Referring to fig. 2, a configuration flow of related parameters for monitoring an existing event, as shown in fig. 2, may include:

step 201: the SCS/AS + AF sends a monitoring request for requesting monitoring of the terminal device to the NEF + SCEF.

The monitoring request may carry one or more parameters such AS SCS/AS + AF identifier, T8 destination address, monitoring type (monitoring type), mobile subscriber international ISDN number (MSISDN) or external identifier (external Id) or external group identifier (external group Id), maximum reporting number (MNR), and the like. It should be noted that, when the monitoring request is for a group of terminal devices, the monitoring request carries an external group identifier; when the monitoring request is directed to a single terminal device, the MSISDN or the external identification of the terminal device is included in the monitoring request. In addition, the monitoring request may also carry the accuracy (accuracy) of the location report, such as cell level (cell level), base station level ((e) NodeB level), tracking area/routing area level (TA/RA level).

Wherein the maximum number of reports may be used to indicate the maximum number of event reports. The maximum reporting times can be configured by SCS/AS + AF according to the needs, without limitation.

It should be noted that, when the monitoring type is location reporting (location reporting), the monitoring request may also carry a Minimum Reporting Interval (MRI). Wherein the minimum reporting interval may be used to indicate a minimum time interval between location reporting indications. Mobility management network elements, such as: after the MME or the AMF acquires the MRI, a timer may be started when sending the location report notification, and an effective duration of the timer is the MRI. And in the validity period of the timer, the mobility management element inhibits the sending of the monitoring event report (such AS a position report notification), and when the timer times out, the mobility management element sends the position report notification obtained last in the validity period of the timer to the SCS/AS + AF. And the mobile management network element sends a position report notice and restarts the timer. MRI ensures that SCS/AS + AF can receive the position update of the terminal device within a certain time, and avoids the impact of signaling load on the network caused by frequent position update in the past.

Step 202: and after receiving the monitoring request, the NEF + SCEF authorizes the monitoring event and distributes the configuration identifier of the monitoring event.

For the authorization of the monitoring event by the NEF + SCEF, reference may be made to the prior art, which is not described herein.

The configuration identifier of the monitoring event may represent the current monitoring event configuration, and the configuration identifier of the monitoring event may be referred to as an SCEF reference identifier (SCEF reference ID) or other names, which is not limited.

Step 203: the NEF + SCEF sends a monitoring request carrying the configuration identity of the monitoring event to the UDM + HSS.

The monitoring request may carry the parameter described in step 201, and may also carry a configuration identifier of the monitoring event.

Further, the NEF + SCEF may also store the parameters and the configuration identifier of the monitoring event in step 201.

Step 204: the UDM + HSS checks the received monitoring request and saves the received parameters after the check is passed.

The process of checking the received monitoring request by the UDM + HSS may refer to the prior art, and is not described in detail herein.

The parameters saved by the UDM + HSS may include the parameters in step 201, such as: SCS/AS + AF identification, T8 destination address, monitoring type, MSISDN or external identification of the terminal device or external group identification (external group Id) MNR, MRI, etc., and may also include configuration identification of the monitoring event.

Taking the current monitoring event as an example of monitoring for the current terminal device, for example, the UDM + HSS may store the configuration identifier of the monitoring event and the parameter in step 201 in a local location; alternatively, the MSISDN of the terminal device is stored locally in association with the other parameters and the configured identifier of the monitoring event in step 201.

Step 205: the UDM + HSS sends a monitoring response to the NEF + SCEF.

Step 206: NEF + SCEF sends a monitoring response to SCS/AS + AF.

The monitoring response may carry a T8 long-term transaction reference ID (TLTRI) or other parameters, without limitation. The TLTRI may be an identifier recognizable by the third party provider (or externally recognizable) for identifying the present event monitoring configuration.

Step 207: the UDM + HSS sends an insert user data request to the mobility management element.

Step 208: and the mobile management network element receives the request for inserting the user data and stores the relevant parameters for monitoring the event.

For example, the mobility management element may store the parameters and the configuration identifier of the monitoring event in step 201.

Step 209: and the mobile management network element sends an insert user data response to the UDM + HSS.

Step 210: the UDM + HSS sends a monitoring answer/monitoring indication to the NEF + SCEF.

Step 211: NEF + SCEF sends a monitoring response/monitoring indication to SCS/AS + AF.

Step 212: SCS/AS + AF sends a monitoring indication response to NEF + SCEF.

Specifically, the detailed process of step 205 to step 212 shown in fig. 2 can refer to the prior art and is not repeated.

Next, the mobility management element may perform event monitoring on the terminal device based on the relevant parameters of event monitoring configured by the SCS/AS + AF, and specifically, the process may be AS shown in fig. 3.

Referring to fig. 3, a conventional event monitoring process is shown. As shown in fig. 3, the process may include:

step 301: and the mobile management network element monitors the events of the terminal device according to the relevant parameters.

Step 302: the mobility management element sends a monitoring indication to the NEF + SCEF.

The monitoring indication may carry a monitoring event report.

Taking the monitoring type as the location report monitoring of the terminal device as an example, if the monitoring request described in fig. 2 carries MRI, the mobility management element starts a timer according to the MRI, and the effective duration of the timer is equal to MRI. Before the timer expires, the mobility management element detects a location change (location change) of the terminal device, generates a monitoring event report, suppresses transmission of the generated monitoring event report notification, and transmits a monitoring instruction carrying the monitoring event report to the NEF + SCEF when the timer expires.

If the monitoring request described in fig. 2 carries the MNR, the MNR is decreased by one when the mobility management element detects that the location of the terminal device changes each time and sends a monitoring instruction carrying a monitoring event report to the NEF + SCEF. And the mobile management network element continues to monitor the terminal device, and continues to send a monitoring instruction to the NEF + SCEF according to the monitoring result until MNR is 0, and stops monitoring the terminal device.

It should be noted that, in addition to carrying the monitoring event report, the monitoring indication may also carry a configuration identifier of the monitoring event, such as: the SCEF reference ID, and other parameters are not limited. If the monitoring request is directed to a group of terminal devices, the monitoring indication may also carry an external identity or MSISDN of the terminal device.

Further, the mobility management element stores the current value (i.e., the number of remaining reports) of the MNR and the current value of the MRI corresponding timer in real time.

Step 303: the NEF + SCEF receives the monitoring instruction carrying the monitoring event report and sends the monitoring instruction to the SCS/AS + AF.

Further, if MNR is locally stored in NEF + SCEF, when NEF + SCEF receives a monitoring instruction carrying a monitoring event report, MNR may be decremented by one, and the current value of MRI may be recorded. And so on until MNR equals 0.

If MRI is locally stored in NEF + SCEF, when the NEF + SCEF receives a monitoring instruction carrying a monitoring event report once, the NEF + SCEF sets a timer, the effective time of the timer is MRI, and the current value of MRI is recorded.

Step 304: SCS/AS + AF sends a monitoring indication response to NEF + SCEF.

When the terminal device is located in the 4G network, the mobile management network element is an MME. When the terminal device is located in the 5G network, the mobility management network element is the AMF.

Specifically, the detailed process of each step shown in fig. 3 can refer to the prior art and is not repeated.

For example, taking the example that the terminal device is registered in the 4G network, the mobility management network element is an MME, and the SCS/AS + AF requests the MME to monitor the location change of the terminal device, if the MNR configured by the SCS/AS + AF to the MME is 10 times and the MRI is 50 seconds(s), the MME may set a timer, generate a monitoring event report when the MME detects the location change of the terminal device within the validity period of the timer, and suppress the sending of the monitoring event report until the timer times out, that is, when the timer reaches 50s, the last detected new event monitoring report is sent to the NEF + SCEF, and at the same time, reduce the MNR by one so that the current value of the MNR is equal to 9, restart the timer, and continue monitoring the terminal device. And so on, and when the current value of the MNR is equal to 0, stopping monitoring the terminal device.

As described above, when the terminal device is monitored for an event, the parameters such as MNR and MRI configured for the event monitoring at this time change in value as the event monitoring progresses. Since the terminal device has mobility, if the terminal device moves from one network system to another network system, for example: and moving from the 4G network to the 5G network, or moving from the 5G network to the 4G network, the mobility management network element in the new network system acquires the relevant parameters for event monitoring from the UDM + HSS, and performs event monitoring on the terminal device based on the acquired parameters. The process can be seen in figure 4.

Fig. 4 shows a flow of monitoring, by a mobility management element, a terminal device based on initial parameters configured by SCS/AS + AF in UDM + HSS when an existing terminal device moves across a network system, AS shown in fig. 4, the process may include:

step 401: the terminal device registers with the first network system.

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

Step 402: the SCS/AS + AF, NEF + SCEF, the user data management network element, and the source mobility management network element interactively execute the parameter configuration flow shown in fig. 2.

When the first network system is a 4G network, the source mobility management network element may be an MME. When the first network system is a 5G network, the source mobile management network element is AMF.

Step 403: the source mobility management element, the user data management element, the NEF + SCEF, and the SCS/AS + AF interact to perform the event monitoring procedure shown in fig. 3.

Step 404: the terminal device moves to the second network system and sends a registration request to the target access network equipment.

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

Step 405: and the target access network equipment sends a registration request to the target mobility management network element.

Step 406: the target mobility management network element sends an identification request to the terminal device.

Step 407: and the terminal device receives the identification request and sends an identification response to the target mobile management network element.

Step 408: and the target mobile management network element receives the identification response and requests the data of the terminal device from the user data management network element.

Step 409: and the user data management network element sends the data of the terminal device to the target mobile management network element, wherein the data of the terminal device comprises relevant parameters for event monitoring.

Step 410: and the target mobile management network element sends a confirmation message to the user data management network element.

Step 411: the target mobility management element monitors an event for the terminal device with reference to the flow shown in fig. 3 based on the relevant parameter of event monitoring acquired from the user data management element.

Specifically, the detailed process of each step shown in fig. 4 can refer to the prior art and is not repeated.

For example, taking the example that the terminal device is registered in the 4G network, the mobility management network element is an MME, and the SCS/AS + AF requests the MME to monitor the location change of the terminal device, if the MNR configured by the SCS/AS + AF to the MME through the user data management network element is 10 times, and the MRI is 50 seconds(s), the MME may set a timer, generate a monitoring event report when the MME detects that the terminal device has a location change within the validity period of the timer, and suppress the sending of the monitoring event report until the timer times out, that is, the timer reaches 50s, sends a new event monitoring report detected last time to the NEF + SCEF, and at the same time, reduces the MNR by one so that the current value of the MNR is equal to 9, and restarts the timer to continue monitoring the terminal device. By analogy, if the terminal device moves from the 4G network to the 5G network when the current value of the MNR is equal to 5 and the duration of the timer corresponding to the MRI is 20s, the AMF obtains the relevant parameters for local event monitoring from the user data management network element: and the MNR is 10 times, the MRI is 50s, the timer duration is reset to be 50s, and the terminal device is monitored for the event again according to the MNR which is 10 times. Therefore, the MME and the AMF report 15 event monitoring reports in total to the SCS/AS + AF, which affects the accuracy of event monitoring.

As can be seen from the methods shown in fig. 3 and 4, the current values of the timers corresponding to the MNR and the MRI are dynamically stored by the MME/AMF. When the UE moves from the 4G network to the 5G network or from the 5G network to the 4G network, the MME/AMF cannot currently acquire the current values of the timers corresponding to the MNR and the MRI from the source mobility management network element, and the UDM + HSS performs event subscription to the MME/AMF according to the relevant parameters of the monitoring event acquired from the NEF + SCEF. This may result in the total number of monitoring event reports reported by the MME/AMF exceeding the MNR or the time interval between monitoring event reports exceeding the MRI. Affecting the accuracy of the event report.

To solve the foregoing technical problem, an embodiment of the present application provides an event monitoring method: when the terminal device moves from one network system to another new network system, the UDM + HSS sends a request for the current value of the relevant parameter for a certain monitoring event to the source mobility management network element or the NEF + SCEF; after receiving the request, the source mobility management network element or the NEF + SCEF returns the current value of the relevant parameter of the monitoring event to the UDM + HSS, the UDM + HSS sends the received current value of the relevant parameter of the monitoring event to the target mobility management network element, and the target mobility management network element monitors the event of the terminal device based on the current value of the relevant parameter of the monitoring event. Therefore, when the terminal device moves across the network system, the target mobility management network element monitors the event according to the current value of the relevant parameter of the monitored event, and the accuracy of event monitoring is improved. Specifically, the detailed process of the process can be described with reference to the embodiments corresponding to fig. 5 to 9.

The following describes an event monitoring method provided in the embodiment of the present application in the embodiments corresponding to fig. 5 to 9, by taking the network architecture shown in fig. 1 as an example. In which, the actions, terms, etc. referred to between the embodiments of the present application can be mutually referred to, without limitation. In the embodiment of the present application, the name of the message exchanged between the devices or the name of the parameter in the message, etc. are only an example, and other names may also be used in the specific implementation, which is not limited.

Fig. 5 is a flowchart of an event monitoring method according to an embodiment of the present application, where the method shown in fig. 5 may be used to solve a problem caused by executing the event monitoring method shown in fig. 4 when a terminal device moves across systems. The methods shown in fig. 4 and 5 are two different schemes, and compared with the method shown in fig. 4, in the method shown in fig. 5, the target mobility management network element may obtain the current value of the relevant parameter for event monitoring, and continue to monitor the terminal device according to the obtained current value of the relevant parameter for event monitoring, so as to improve the accuracy of event monitoring.

Before the method shown in fig. 5 is executed, the flows shown in fig. 2 and fig. 3 are executed in sequence. Such as: before executing the method shown in fig. 5, the terminal device is located in the first network system, and when the SCS/AS + AF determines that event monitoring needs to be performed on the terminal device, the SCS/AS + AF configures, with reference to the flow shown in fig. 2, relevant parameters for performing event monitoring on the terminal device to a network element belonging to the first network system, such AS: the NEF + SCEF, UDM + HSS, the source mobility management element, and the like, and referring to the flow shown in fig. 3, the source mobility management element and the NEF + SCEF perform event monitoring on the terminal device according to the relevant parameters of event monitoring configured by SCS/AS + AF, and the NEF + SCEF/source mobility management element stores the current values of the relevant parameters of event monitoring in real time, so that when the terminal device moves to the second network system, the user data management element obtains the current values of the relevant parameters of event monitoring from the NEF + SCEF/source mobility management element, and sends the current values to the target mobility management element in the second network system.

Specifically, the method shown in fig. 5 may include steps 501 to 505:

step 501: the terminal device moves from the first network system to the second network system.

The terminal device may be any one of the terminal devices in fig. 1.

The first network system and the second network system may be network systems using different communication systems. For example, the first network system may be a 4G network, and the second network system may be a 5G network; alternatively, the first network system may be a 5G network, and the second network system may be a 4G network, without limitation.

Specifically, the execution process of step 501 may refer to the process shown in fig. 4, and is not described in detail.

Step 502: the user data management network element sends a first request to the first network element.

The user data network element may be the UDM + HSS in fig. 1.

The first network element belongs to a first network system, and may be a source mobility management network element or a network open function network element, and the network open function network element may be NEF + SCEF in fig. 1.

It should be noted that, in this embodiment of the application, the target mobility management element and the source mobility management element are relative concepts, the target mobility management element may be a core network device in the second network system, and the source mobility management element may be a core network device in the first network system. When the terminal device moves from the 4G network to the 5G network, the source mobility management network element may be the MME in fig. 1, and the target mobility management network element may be the AMF in fig. 1. When the terminal device moves from the 5G network to the 4G network, the source mobility management network element may be the AMF in fig. 1, and the target mobility management network element may be the MME in fig. 1.

Wherein the first request may be for requesting a current value of a first parameter of the first event. The first request may comprise an identification of the terminal device and/or a configuration identification of the first event. The identification of the terminal device may be used to identify the terminal device, and the identification of the terminal device may be an external identification (external ID) of the terminal device or a mobile subscriber international ISDN number (MSISDN) of the terminal device. The configuration identifier of the first event may be used to identify a relevant configuration of the first event, and the configuration identifier of the first event may be configured by NEF + SCEF.

The first event may be any event of the terminal device, such as: the first event may be a location report (location reporting) of the terminal device, or an reachable state of the terminal device, or the like.

The first parameter of the first event may be used to monitor the first event, and the first parameter of the first event may include the number of reports and the reporting interval. The reporting interval may be the MRI as described in fig. 2 and the number of reports may be the MNR as described in fig. 2.

For example, after receiving the registration request sent by the target mobility management network element, the subscriber data management network element may query locally stored data of the terminal device according to the registration request, where the data of the terminal device may include subscription data of the terminal device and/or related parameters of the terminal device, and if the locally stored data of the terminal device includes the first parameter, the subscriber data management network element sends the first request to the first network element.

For example, if the user data management network element determines that the locally stored relevant parameters for event monitoring include MNR and/or MRI, the user data management network element sends a first request to the first network element.

Step 503: and the first network element receives the first request and sends the current value of the first parameter to the user data management network element according to the first request.

Step 504: the user data management network element receives the current value of the first parameter from the first network element and sends a second request to the target mobility management network element.

Wherein the second request may include a current value of the first parameter, and the second request may be for requesting the target mobility management network element to monitor for the first event. It should be noted that, in addition to including the current value of the first parameter, the user data management network element may use an initial value of the first parameter, such as: the initial value of MNR and the initial value of MRI are sent to the target mobility management element, and may also include some other parameters, which are sent to the target mobility management element without limitation.

Step 505: and the target mobile management network element receives the second request and monitors the first event according to the current value of the first parameter.

For example, referring to fig. 3, the target mobility management network element may monitor the first event according to the current value of the first parameter, and meanwhile, the target mobility management network element may store the current values of the timers corresponding to the MNR and the MRI locally in real time, which is not described in detail.

For example, taking the example that the terminal device is registered in the 4G network, the mobility management network element is an MME, and the SCS/AS + AF requests the MME to monitor the location change of the terminal device, if the MNR configured by the SCS/AS + AF to the MME through the user data management network element is 10 times, and the MRI is 50 seconds(s), the MME may set a timer, generate a monitoring event report when the MME detects that the terminal device has a location change within the validity period of the timer, and suppress the sending of the monitoring event report until the timer times out, that is, the timer reaches 50s, sends a new event monitoring report detected last time to the NEF + SCEF, and at the same time, reduces the MNR by one so that the current value of the MNR is equal to 9, and restarts the timer to continue monitoring the terminal device. And so on, if the current value of the MNR is equal to 5 and the duration of the timer corresponding to MRI is 20s, the terminal device moves from the 4G network to the 5G network, the AMF sends a request to the user data management network element to request to acquire the MNR and MRI, the user data management network element acquires the current value 5 of the MNR and the current duration 20s of the timer corresponding to MRI from the MME or NEF + SCEF, and sends the current value 5 of the MNR and the current duration 20s of the timer corresponding to MRI to the AMF, and the AMF monitors the event of the terminal device according to the MNR being 5 times. Therefore, the MME and the AMF report 10 event monitoring reports to the SCS/AS + AF together, and the accuracy of event monitoring is ensured.

Based on the method shown in fig. 5, when the terminal device moves across the network system, the user data management network element requests the first network element for the current value of the first parameter used for monitoring the first event, and sends the current value of the first parameter acquired from the first network element to the target mobility management network element, so that the target mobility management network element continues to monitor the terminal device for the event based on the current value of the first parameter. Therefore, the event monitoring is carried out on the terminal device by the mobile management network element before the terminal device crosses the network system and the mobile management network element after the terminal device crosses the network system based on the continuous value of the same parameter, the accuracy of the event monitoring report is improved, and the problem that the event monitoring report is inaccurate due to the fact that the mobile management network element in a new network system cannot acquire the current value of the parameter and the event monitoring is carried out on the terminal device again based on the initial value of the parameter after the terminal device crosses the network system in the prior art is solved.

With reference to the method shown in fig. 6, the event monitoring flow shown in fig. 5 is described in detail below by taking an example that the first network system is a 4G network, the second network system is a 5G network, the first network element is an MME, the target mobility management network element is an AMF, the terminal device moves from the 4G network to the 5G network, and the UDM + HSS obtains an MRI current value or a remaining number of reports related to event subscription from the MME, and subscribes to the AMF.

Compared with the method shown in fig. 4, the AMF in the method shown in fig. 6 can acquire the current value of the relevant parameter for event monitoring, and continues to monitor the terminal device according to the acquired current value of the relevant parameter for event monitoring, thereby improving the accuracy of event monitoring.

Before executing the method shown in fig. 6, the terminal device is located in the 4G network, and the flows shown in fig. 2 and fig. 3 need to be executed successively. Such as: before executing the method shown in fig. 6, the terminal device is located in the 4G network, and when the SCS/AS + AF determines that event monitoring needs to be performed on the terminal device, the SCS/AS + AF configures relevant parameters for performing event monitoring on the terminal device to network elements belonging to the 4G network with reference to the flow shown in fig. 2, such AS: the method includes that an MME, the NEF + SCEF, an UDM + HSS, the MME and the NEF + SCEF refer to a flow shown in fig. 3, event monitoring is carried out on a terminal device according to event monitoring related parameters configured by SCS/AS + AF, and the MME stores current values of the event monitoring related parameters in real time, so that when the terminal device moves to a 5G network, a user data management network element obtains the current values of the event monitoring related parameters from the MME and sends the current values to an AMF in the 5G network.

Fig. 6 is a flowchart of an event monitoring method according to an embodiment of the present application, and as shown in fig. 6, the method includes:

step 601 to step 608 are executed.

Step 601 to step 608 are the same as step 401 to step 408 shown in fig. 4, and are not described again.

Step 609: the user data management network element judges that the stored relevant parameters of the event monitoring include a first parameter, such as: MNR and/or MRI, the user data management network element sends a first request to the MME.

The first request may carry an identifier of the terminal device and/or a configuration identifier of the first event, such as: in the 4G system, the configuration identifier of the first event is a corresponding SCEF reference identifier (SCEF reference ID) configured for the monitoring event, and in the 5G system, the configuration identifier of the first event may be a corresponding target notification address or a target notification address and notification association identifier configured for the monitoring event.

Step 610: the MME receives the first request, and returns a current value of the first parameter to the user data management network element according to the first request, such as: the number of remaining reports and/or the current value of the MRI corresponding timer.

Step 611: and the user data management network element receives the current value of the first parameter and sends the current value of the first parameter to the AMF.

Wherein the current value of the first parameter may be carried in the event subscription request.

If the event subscription is directed to a single terminal device, the event subscription request carries the stored subscription information, but the MNR is replaced by the remaining report times, and the MRI is replaced by the current value of the timer corresponding to the MRI. If the event subscription is directed to a group of terminal devices, only sending the residual report times related to the terminal device and/or the current value of the timer corresponding to MRI when the subscription for the group already exists on the AMF; when the AMF does not have a subscription for the group, the user data management network element performs group subscription to the AMF, and carries information related to event subscription, remaining report times related to the terminal device and/or a current value of a timer corresponding to MRI.

Step 612: and the AMF returns a confirmation message to the user data management network element.

Step 613: the AMF monitors the terminal device for a first event based on the current value of the first parameter.

The process shown in fig. 3 may be referred to by the AMF for monitoring the first event of the terminal device based on the current value of the first parameter, which is not described in detail.

Based on the method shown in fig. 6, when the terminal device crosses from the 4G network to the 5G network, the user data management network element obtains, from the MME, a current value of a parameter (for example, a current value of a remaining number of reports or a maximum report interval timer) of a monitoring event subscription corresponding to the terminal device, and provides the current value of the parameter to the AMF, so that the AMF continues to perform event monitoring on the terminal device based on the current value of the parameter, and accuracy and continuity of event monitoring are improved.

In the method shown in fig. 6, the first network element is taken as an MME for example, and a method for monitoring an event when the terminal device moves from a 4G network to a 5G network is described, alternatively, the first network element may also be NEF + SCEF. Next, with reference to the method shown in fig. 7, an event monitoring flow shown in fig. 5 is described with an example that the first network system is a 4G network, the second network system is a 5G network, the first network element is NEF + SCEF, the target mobility management network element is AMF, the terminal device moves from the 4G network to the 5G network, and the UDM + HSS obtains an MRI current value or a remaining number of reports related to event subscription from the NEF + SCEF and subscribes to the AMF.

Fig. 7 may also be used to solve the problem caused by the event monitoring method shown in fig. 4 when the terminal device moves from the 4G network to the 5G network. Fig. 7 is different from the method shown in fig. 6 in that: in the method shown in fig. 6, the user management network element may obtain the current value of the first parameter from the MME, whereas in the method shown in fig. 7, the user data management network element obtains the current value of the first parameter from the NEF + SCEF. And similar to the method shown in fig. 6, before the method shown in fig. 7 is executed, the flows shown in fig. 2 and fig. 3 are executed in sequence, which is not described again.

Fig. 7 is a flowchart of an event monitoring method according to an embodiment of the present application, and as shown in fig. 7, the method includes:

step 701 to step 708 are executed.

The steps 701 to 708 are the same as the steps 401 to 408 shown in fig. 4, and are not described again.

It should be noted that, in step 703, after receiving the monitoring event report sent by the MME, the NEF + SCEF updates the current value of the first parameter and maintains the parameter value of the first parameter. For example, the NEF + SCEF may subtract MNR by 1 and reset the duration of the timer corresponding to MRI as described in step 302, i.e., the same remaining number of reports as the MME and the current value of the timer corresponding to MRI are saved on the NEF + SCEF.

Step 709: the user data management network element judges that the stored relevant parameters of the event monitoring include a first parameter, such as: MNR and/or MRI, the user data managing network element sends a first request to the NEF + SCEF.

The first request may carry an identifier of the terminal device and/or a configuration identifier of the first event, such as: in the 4G system, the configuration identifier of the first event may be a corresponding SCEF reference ID configured for the monitoring event, and in the 5G system, the configuration identifier of the first event may be a corresponding target notification address configured for the monitoring event, or a target notification address and notification association identifier, and the like.

Step 710: the NEF + SCEF receives the first request, and returns the current value of the first parameter to the user data management network element according to the first request, such as: the number of remaining reports and/or the current value of the MRI corresponding timer.

Step 711: and the user data management network element receives the current value of the first parameter and sends the current value of the first parameter to the AMF.

Step 712: and the AMF returns a confirmation message to the user data management network element.

Step 713: the AMF monitors the terminal device for a first event based on the current value of the first parameter.

Based on the method shown in fig. 7, when the terminal device crosses from the 4G network to the 5G network, the user data management network element obtains, from NEF + SCEF, a current value of a parameter (for example, a current value of a remaining number of reports or a maximum report interval timer) of a monitoring event subscription corresponding to the terminal device, and provides the current value of the parameter to the AMF, so that the AMF continues to perform event monitoring on the terminal device based on the current value of the parameter, and accuracy and continuity of event monitoring are improved.

Similarly, when the terminal device moves from the 5G network to the 4G network, the event monitoring process may be implemented with reference to the methods shown in fig. 6 and 7. With reference to fig. 8, the event monitoring flow shown in fig. 5 is described in detail below by taking the first network system as a 5G network, the second network system as a 4G network, the first network element as an AMF, the target mobility management network element as an MME, the terminal device moves from the 5G network to the 4G network, and the UDM + HSS obtains an MRI current value or a remaining number of reports related to an event subscription from the AMF and subscribes to the MME.

The method shown in fig. 8 may be used to solve the problem caused by executing the event monitoring method shown in fig. 4 when the terminal device moves from the 5G network to the 4G network, and the methods shown in fig. 4 and 8 are two completely different solutions, and compared with the method shown in fig. 4, the MME in the method shown in fig. 8 may obtain the current value of the relevant parameter for event monitoring, and continue to monitor the terminal device according to the obtained current value of the relevant parameter for event monitoring, so as to improve the accuracy of event monitoring.

Before executing the method shown in fig. 8, the flows shown in fig. 2 and fig. 3 need to be executed successively. Such as: before executing the method shown in fig. 8, the terminal device is located in the 5G network, and when the SCS/AS + AF determines that event monitoring needs to be performed on the terminal device, the SCS/AS + AF configures relevant parameters for performing event monitoring on the terminal device to network elements belonging to the 5G network with reference to the flow shown in fig. 2, such AS: the method includes that the NEF + SCEF, the UDM + HSS, the AMF and the like refer to a flow shown in fig. 3 by the AMF and the NEF + SCEF, event monitoring is carried out on the terminal device according to relevant parameters of event monitoring configured by the SCS/AS + AF, and the AMF stores current values of the relevant parameters of the event monitoring in real time, so that when the terminal device moves to the 4G network, a user data management network element obtains the current values of the relevant parameters of the event monitoring from the AMF and sends the current values to an MME in the 4G network.

Fig. 8 is a flowchart of an event monitoring method according to an embodiment of the present application, and as shown in fig. 8, the method includes:

steps 801 to 808 are performed.

Steps 801 to 808 are the same as steps 401 to 408 shown in fig. 4, and are not described again.

Step 809: the user data management network element judges that the stored relevant parameters of the event monitoring include a first parameter, such as: MNR and/or MRI, the user data managing network element sends a first request to the AMF.

Step 810: the AMF receives the first request, and returns the current value of the first parameter to the user data management network element according to the first request, such as: the number of remaining reports and/or the current value of the MRI corresponding timer.

Step 811: and the user data management network element receives the current value of the first parameter and sends the current value of the first parameter to the MME.

If the event subscription is directed to a single terminal device, the event subscription request carries the stored subscription information, but the MNR is replaced by the remaining report times, and the MRI is replaced by the current value of the timer corresponding to the MRI. If the event subscription is directed to a group of terminal devices, when the MME has the subscription to the group, only sending the residual report times related to the terminal devices and/or the current value of the timer corresponding to the MRI; when the MME does not have a subscription for the group, the user data management network element performs group subscription to the MME, and carries information related to event subscription and also carries the remaining number of reports related to the terminal device and/or the current value of the timer corresponding to MRI.

Step 812: and the MME returns a confirmation message to the user data management network element.

Step 813: and the MME monitors the terminal device for a first event based on the current value of the first parameter.

The monitoring of the first event performed by the MME on the terminal device based on the current value of the first parameter may refer to the process shown in fig. 3, which is not described in detail.

Based on the method shown in fig. 8, when the terminal device crosses from the 5G network to the 4G network, the user data management network element obtains, from the AMF, a current value of a parameter (for example, a current value of a remaining number of reports or a maximum report interval timer) of a monitoring event subscription corresponding to the terminal device, and provides the current value of the parameter to the MME, so that the MME continues to perform event monitoring on the terminal device based on the current value of the parameter, and accuracy and continuity of event monitoring are improved.

In the method shown in fig. 8, the first network element is taken as an MME for example, and a method for monitoring an event when the terminal device moves from a 5G network to a 4G network is described, alternatively, the first network element may also be NEF + SCEF. Next, referring to fig. 9, an event monitoring flow shown in fig. 5 is described with an example that the first network system is a 5G network, the second network system is a 4G network, the first network element is NEF + SCEF, the target mobility management network element is MME, the terminal device moves from the 5G network to the 4G network, and the UDM + HSS acquires an MRI current value or a remaining number of reports related to event subscription from the NEF + SCEF and subscribes to the MME.

Fig. 9 may also be used to solve the problem caused by the event monitoring method shown in fig. 4 when the mobile terminal moves from the 5G network to the 4G network. Fig. 9 is different from the method shown in fig. 8 in that: in the method shown in fig. 8, the subscriber management network element may obtain the current value of the first parameter from the AMF, and in the method shown in fig. 9, the subscriber data management network element obtains the current value of the first parameter from the NEF + SCEF. And similar to the method shown in fig. 8, before the method shown in fig. 9 is executed, the flows shown in fig. 2 and fig. 3 are executed in sequence, which is not described in detail.

Fig. 9 is a flowchart of an event monitoring method according to an embodiment of the present application, and as shown in fig. 9, the method includes:

steps 901 to 908 are performed.

Step 901 to step 908 are the same as step 401 to step 408 shown in fig. 4, and are not described again.

It should be noted that, in step 903, after receiving the monitoring event report sent by the MME, the NEF + SCEF updates the current value of the first parameter and maintains the parameter value of the first parameter. For example, the NEF + SCEF may subtract MNR by 1 and reset the duration of the timer corresponding to MRI as described in step 302, i.e., the same remaining number of reports as the MME and the current value of the timer corresponding to MRI are saved on the NEF + SCEF.

Step 909: the user data management network element judges that the stored relevant parameters of the event monitoring include a first parameter, such as: MNR and/or MRI, the user data managing network element sends a first request to the NEF + SCEF.

Step 910: the NEF + SCEF receives the first request, and returns the current value of the first parameter to the user data management network element according to the first request, such as: the number of remaining reports and/or the current value of the MRI corresponding timer.

Step 911: and the user data management network element receives the current value of the first parameter and sends the current value of the first parameter to the MME.

Step 912: and the MME returns a confirmation message to the user data management network element.

Step 913: and the MME monitors the terminal device for a first event based on the current value of the first parameter.

Based on the method shown in fig. 9, when the terminal device crosses from the 5G network to the 4G network, the user data management network element obtains, from NEF + SCEF, a current value of a parameter (for example, a current value of a remaining number of reports or a maximum report interval timer) of a monitoring event subscription corresponding to the terminal device, and provides the current value of the parameter to the MME, so that the MME continues to perform event monitoring on the terminal device based on the current value of the parameter, and accuracy and continuity of event monitoring are improved.

The above-mentioned scheme provided by the embodiment of the present application is introduced mainly from the perspective of interaction between network elements. It is to be understood that the user data managing network element, the first network element, the target mobility managing network element, etc. comprise corresponding hardware structures and/or software modules for performing the respective functions in order to implement the above-mentioned functions. Those of skill in the art will readily appreciate that the present application is capable of hardware or a combination of hardware and computer software implementing the various illustrative algorithm steps described in connection with the embodiments disclosed herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiment of the present application, according to the above method example, the functional modules may be divided for the user data management network element, the first network element, and the target mobility management network element, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation.

In the case of integrating two or more functional functions into the same functional module, the devices in the architecture shown in fig. 1 for executing the event monitoring method described above, such as: the user data management network element, the AMF, the MME, and the NEF + SCEF may all adopt the composition structure shown in fig. 10, or include the components shown in fig. 10. Fig. 10 is a schematic diagram illustrating a composition of a communication apparatus 100 according to an embodiment of the present application, for example, the communication apparatus 100 may be a user data management network element or a chip or a system on chip in the user data management network element. As shown in fig. 10, the communication device 100 may include a processor 1001, a transceiver 1002, and a communication link 1003.

Further, the communication device 100 may also include a memory 1004. The processor 1001, the memory 1004, and the transceiver 1002 may be connected via a communication line 1003.

The processor 1001 is a Central Processing Unit (CPU), a general purpose processor Network (NP), a Digital Signal Processor (DSP), a microprocessor, a microcontroller, a Programmable Logic Device (PLD), or any combination thereof. The processor 1001 may also be other devices with processing functions, such as a circuit, a device, or a software module, without limitation.

A transceiver 1002 for communicating with other devices or other communication networks. The other communication network may be an ethernet, a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), or the like. The transceiver 1002 may be a module, a circuit, a transceiver, or any device capable of enabling communication.

A communication line 1003 for transmitting information between the respective components included in the communication apparatus 100.

Memory 1004 is used to store instructions. Wherein the instructions may be a computer program.

The memory 1004 may be a read-only memory (ROM) or other types of static storage devices that can store static information and/or instructions, a Random Access Memory (RAM) or other types of dynamic storage devices that can store information and/or instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), a magnetic disc storage medium or other magnetic storage devices, and the like, without limitation.

It is to be noted that the memory 1004 may exist independently of the processor 1001 or may be integrated with the processor 1001. The memory 1004 may be used to store instructions or program code or some data or the like. The memory 1004 may be located inside the communication device 100 or outside the communication device 100, which is not limited. The processor 1001 is configured to execute the instructions stored in the memory 1004 to implement the event monitoring method provided in the following embodiments of the present application.

In one example, the processor 1001 may include one or more CPUs, such as CPU0 and CPU1 in fig. 10.

As an alternative implementation, the communication device 100 includes multiple processors, and may include the processor 1007 in addition to the processor 1001 in fig. 10, for example.

As an alternative implementation, the communication apparatus 100 further comprises an output device 1005 and an input device 1006. Illustratively, the input device 1006 is a keyboard, mouse, microphone, or joystick-like device, and the output device 1005 is a display screen, speaker (spaker), or like device.

It is noted that the communication apparatus 100 may be a desktop computer, a portable computer, a network server, a mobile phone, a tablet computer, a wireless terminal, an embedded device, a chip system or a device with a similar structure as that in fig. 10. Further, the constituent structure shown in fig. 10 does not constitute a limitation of the terminal device, and the terminal device may include more or less components than those shown in fig. 10, or combine some components, or a different arrangement of components, in addition to the components shown in fig. 10.

In the embodiment of the present application, the chip system may be composed of a chip, and may also include a chip and other discrete devices.

In the case of dividing each functional module according to each function, fig. 11 shows a structure diagram of a communication device 110, where the communication device 110 may be a user data management network element or a chip or a system on chip in the user data management network element, and the communication device 110 may be configured to perform the functions of the user data management network element in the above-described embodiments. The communication device 110 shown in fig. 11 includes: transmitting section 1101 and receiving section 1102.

A sending unit 1101, configured to send, to the first network element, a first request for requesting a current value of a first parameter of a first event when the terminal device moves from the first network system to the second network system. For example, the sending unit 1101 may support the communication apparatus 110 to perform step 502, step 609, step 709, step 809, and step 909.

A receiving unit 1102 is configured to receive a current value of a first parameter from a first network element. For example, the receiving unit 1102 may support the communication device 110 to perform step 504, step 611, step 711, step 811, and step 911.

The sending unit 1101 is further configured to send, to the target mobility management element, a second request that includes the current value of the first parameter and is used to request the target mobility management element to monitor the first event. For example, the sending unit 1101 may support the communication device 110 to perform step 504, step 611, step 711, step 811, and step 911.

The specific implementation manner of the communication device 110 may refer to the behavior function of the user data management network element in the event monitoring method shown in fig. 5 to fig. 9. In addition, the description of the first parameter, the first network element, and the target mobility management element may refer to the description in the foregoing embodiment of the method, and is not repeated herein.

As yet another implementation manner, the transmitting unit 1101 and the receiving unit 1102 in fig. 11 may be replaced by a transceiver or a transceiving unit, and the transceiver or the transceiving unit may integrate functions of the transmitting unit 1101 and the receiving unit 1102. Further, the terminal device 110 shown in fig. 11 may further include a processor and a memory. When the transmitting unit 1101 and the receiving unit 1102 are replaced by transceivers or transceiving units, the communication device 110 according to the embodiment of the present application may be the communication device shown in fig. 10.

Fig. 12 shows a structure diagram of a communication apparatus 120, where the communication apparatus 120 may be a first network element or a chip or a system on chip in the first network element, and the first network element may be a source mobility management network element or NEF + SCEF, and the communication apparatus 120 may be configured to perform the functions of the source mobility management network element or NEF + SCEF involved in the foregoing embodiments. As one implementation manner, the communication device 120 shown in fig. 12 includes: a receiving unit 1201, a transmitting unit 1202;

a receiving unit 1201, configured to receive a first request for requesting a current value of a first parameter of a first event from a user data managing network element when the terminal device moves from the first network system to the second network system.

A sending unit 1202, configured to send the current value of the first parameter to the user data management network element according to the first request.

For example, the receiving unit 1201 and the transmitting unit 1202 may support the communication apparatus 120 to perform step 503, step 610, step 710, step 810, and step 910.

The specific implementation manner of the communication device 120 may refer to the behavior function of the first network element in the event monitoring method shown in fig. 5 to fig. 9. In addition, the description of the first parameter, the first network element, and the target mobility management element may refer to the description in the foregoing embodiment of the method, and is not repeated herein.

As yet another implementable manner, the receiving unit 1201, the transmitting unit 1202 in fig. 12 may be replaced by a transceiver, which may integrate the functions of the receiving unit 1201, the transmitting unit 1202. Further, the terminal device 120 shown in fig. 12 may further include a processor and a memory. When the receiving unit 1201 and the transmitting unit 1202 are replaced by a transceiver or a transmitting/receiving unit, the communication device 120 according to the embodiment of the present application may be the communication device shown in fig. 10.

Fig. 13 is a block diagram of a communication system according to an embodiment of the present application, and as shown in fig. 13, the system may include: a user data management network element 130, a first network element 131, a target mobility management network element, a terminal device, and the like.

Among them, the user data management network element 130 has the function of the communication device 110 shown in fig. 11. The first network element 131 has the function of the communication device 120 shown in fig. 12.

A user data management network element 130 for sending a first request for requesting a current value of a first parameter of a first event to a first network element when the terminal device moves from the first network system to a second network system;

a first network element 131, configured to receive the first request and send a current value of the first parameter to the user data management network element 130;

the user data managing network element 130 is further configured to receive a current value of the first parameter from the first network element, send a second request including the current value of the first parameter to the target mobility managing network element, and request the target mobility managing network element to monitor the first event based on the current value of the first parameter.

Specifically, the specific implementation process of the user data management network element 130 may refer to an execution process of the user data management network element in the event monitoring method shown in fig. 5 to 9, and the specific implementation process of the first network element 131 may refer to an execution process of the source mobility management network element or NEF + SCEF in the event monitoring method shown in fig. 5 to 9.

Based on the system shown in fig. 13, when the terminal device moves across the network system, the user data management network element 130 requests the first network element 131 for the current value of the first parameter used for monitoring the first event, and sends the current value of the first parameter acquired from the first network element 131 to the target mobility management network element, so that the target mobility management network element continues to perform event monitoring on the terminal device based on the current value of the first parameter. Therefore, the event monitoring is carried out on the terminal device by the mobile management network element before the terminal device crosses the network system and the mobile management network element after the terminal device crosses the network system based on the continuous value of the same parameter, the accuracy of the event monitoring report is improved, and the problem that the event monitoring report is inaccurate due to the fact that the mobile management network element in a new network system cannot acquire the current value of the parameter and the event monitoring is carried out on the terminal device again based on the initial value of the parameter after the terminal device crosses the network system in the prior art is solved.

The embodiment of the application also provides a computer readable storage medium. All or part of the processes in the above method embodiments may be performed by relevant hardware instructed by a computer program, which may be stored in the above computer-readable storage medium, and when executed, may include the processes in the above method embodiments. The computer-readable storage medium may be an internal storage unit of the terminal device (including the data sending end and/or the data receiving end) in any of the foregoing embodiments, for example, a hard disk or a memory of the terminal device. The computer readable storage medium may also be an external storage device of the terminal device, such as a plug-in hard disk, a Smart Memory Card (SMC), a Secure Digital (SD) card, a flash memory card (flash card), and the like, which are provided on the terminal device. Further, the computer-readable storage medium may include both an internal storage unit and an external storage device of the terminal apparatus. The computer-readable storage medium stores the computer program and other programs and data required by the terminal device. The above-described computer-readable storage medium may also be used to temporarily store data that has been output or is to be output.

It should be noted that the terms "first" and "second" and the like in the description, claims and drawings of the present application are used for distinguishing different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.

It should be understood that in the present application, "at least one" means one or more, "a plurality" means two or more, "at least two" means two or three and three or more, "and/or" for describing an association relationship of associated objects, meaning that three relationships may exist, for example, "a and/or B" may mean: only A, only B and both A and B are present, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of single item(s) or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.

Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical functional division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another device, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may be one physical unit or a plurality of physical units, that is, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially or partially contributed to by the prior art, or all or part of the technical solutions may be embodied in the form of a software product, where the software product is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for event monitoring, the method comprising:

when the terminal device moves from a first network system to a second network system, the user data management network element sends a first request to the first network element, wherein the first request is used for requesting the current value of a first parameter of a first event;

the user data management network element receiving a current value of the first parameter from the first network element;

and the user data management network element sends a second request to a target mobility management network element, wherein the second request comprises the current value of the first parameter, and the second request is used for requesting the target mobility management network element to monitor the first event.

2. The method of claim 1,

the first parameter includes at least one of a number of reports and a reporting interval.

3. The method according to claim 1 or 2,

the first network element belongs to the first network system, and the target mobility management network element belongs to the second network system;

the first network element is an access and mobility management function network element or a network open function network element, and the target mobility management network element is a mobility management entity; alternatively, the first and second electrodes may be,

the first network element is a mobility management entity or a network open function network element, and the target mobility management network element is an access and mobility management function network element.

4. The method according to any one of claims 1 to 3,

the first request comprises an identity of the terminal device; the identification of the terminal device is from the target mobility management network element.

5. The method according to any one of claims 1 to 3,

the first request includes a configuration identifier of the first event, where the configuration identifier of the first event is used for the first network element to send the current value of the first parameter according to the configuration identifier of the first event.

6. A method for event monitoring, the method comprising:

when the terminal device moves from a first network system to a second network system, the first network element receives a first request from a user data management network element, wherein the first request is used for requesting the current value of a first parameter of a first event;

and the first network element sends the current value of the first parameter to the user data management network element according to the first request.

7. The method of claim 6,

8. The method according to claim 6 or 7,

the first network element belongs to the first network system;

the first network element is an access and mobility management function network element or a network open function network element; or, the first network element is a mobility management entity or a network open function network element.

9. The method according to any of claims 6-8, wherein the first request comprises an identity of the terminal device; the identification of the terminal device is from a target mobile management network element;

the sending, by the first network element, the current value of the first parameter to the user data management network element according to the first request includes: and the first network element sends the current value of the first parameter to the user data management network element according to the identifier of the terminal device.

10. The method according to any of claims 6-8, wherein the first request comprises a configuration identification of the first event; the sending, by the first network element, the current value of the first parameter to the user data management network element according to the first request includes:

and the first network element sends the current value of the first parameter to the user data management network element according to the configuration identifier of the first event.

11. A communication device, characterized in that the communication device is adapted to perform the event monitoring method according to any of claims 1-5.

12. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer instruction or a program which, when run on a computer, causes the computer to perform the event monitoring method according to any one of claims 1 to 5.

13. A communication device, characterized in that it is adapted to perform the event monitoring method according to any of claims 6-10.

14. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer instruction or a program which, when run on a computer, causes the computer to perform the event monitoring method according to any one of claims 6 to 10.

15. A communication system, wherein the communication system is a system in which a first network system and a second network system are interworked, the communication system comprising:

a user data management network element for sending a first request to a first network element when the terminal device moves from the first network system to the second network system, wherein the first request is used for requesting a current value of a first parameter of a first event;

the first network element is configured to receive a first request from the user data management network element, and send a current value of the first parameter to the user data management network element according to the first request;

the user data management network element is further configured to receive a current value of the first parameter from the first network element, and send a second request to a target mobility management network element, where the second request includes the current value of the first parameter, and the second request is used to request the target mobility management network element to monitor the first event.