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

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

Info

Publication number
WO2019196773A1
WO2019196773A1 PCT/CN2019/081696 CN2019081696W WO2019196773A1 WO 2019196773 A1 WO2019196773 A1 WO 2019196773A1 CN 2019081696 W CN2019081696 W CN 2019081696W WO 2019196773 A1 WO2019196773 A1 WO 2019196773A1
Authority
WO
WIPO (PCT)
Prior art keywords
monitoring
user group
monitoring event
members
message
Prior art date
Application number
PCT/CN2019/081696
Other languages
English (en)
French (fr)
Inventor
朱奋勤
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN201810349848.3A external-priority patent/CN110366199B/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to KR1020207030612A priority Critical patent/KR102517686B1/ko
Priority to BR112020020432-3A priority patent/BR112020020432A2/pt
Priority to JP2020552193A priority patent/JP7130767B2/ja
Priority to EP19785187.6A priority patent/EP3764680B1/en
Publication of WO2019196773A1 publication Critical patent/WO2019196773A1/zh
Priority to US17/066,914 priority patent/US11425538B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements

Definitions

  • the embodiments of the present invention relate to the field of communications technologies, and in particular, to an event monitoring method and apparatus.
  • SCEF service capability exposure function
  • the NEF provides the 3GPP network-supported services to the SCS/AS through services. ability.
  • the SCS/AS can monitor the event of the user under the framework of the open service capability, and can monitor the user for various events, such as user equipment (UE). Events such as sexuality and dropped calls.
  • UE user equipment
  • the SCEF may receive a monitoring request carrying an external group identifier, and the external group identifier is used to identify a group of members, and the monitoring event is performed on the members in the group.
  • the core network element mobility management entity (MME)/serving GPRS support node (SGSN) sends a monitoring event report to the SCEF for each member of the group after event monitoring.
  • MME mobility management entity
  • SGSN serving GPRS support node
  • the NEF may receive a monitoring request carrying an external group identity.
  • the Access and Mobility Management Function (AMF) sends monitoring to the SCEF after event monitoring for each member of the group. Event report.
  • AMF Access and Mobility Management Function
  • SCEF/NEF retains The monitoring event configuration of this group will result in waste of resources and subsequent policy execution errors.
  • the embodiment of the present invention provides an event monitoring method and device, which is used to implement the service capability opening function or the network opening function to delete the monitoring event configuration of the group after receiving the event report of all members in the group, thereby avoiding waste of resources and subsequent Policy execution error.
  • an event monitoring method is provided, the execution subject of which is an open functional entity.
  • the process of the specific method is as follows: receiving a first message, where the first message is used to configure a monitoring event for a user group, obtaining member information of the user group, and determining all the user groups according to the member information.
  • the member's monitoring event report has been received, and the configuration of the monitoring event for the user group is deleted.
  • the open function entity obtains the member information of the user group, and when receiving the monitoring event report, can determine, according to the member information of the user group, that the monitoring event report of all members in the user group has been received, thereby further deleting the user.
  • the monitoring of the group's monitoring events avoids wasting resources and helps ensure the correct execution of subsequent policies.
  • the open functional entity is a service capability open function SCEF entity, or the open functional entity is a network open function NEF entity.
  • SCEF entity service capability open function SCEF entity
  • NEF entity network open function NEF entity.
  • the member information of the user group may be the number of members included in the user group, and the number of members may be represented by N; the member information of the user group may also be the identifier of each member in the user group, that is, the user The member information of the group is N identifiers.
  • the open function entity can determine, according to the number of members included in the user group, or according to the identifier of the member, how many members have received the monitoring event report, thereby determining whether the monitoring event reports of all members in the user group have been received. .
  • Manner 1 The first message carries the member information of the user group, and obtains the member information of the user group from the first message.
  • Manner 2 Receive member information of the user group sent by the user data management entity, that is, obtain member information of the user group from the user data management entity. In this way, the member information of the user group is carried in the existing signaling, which reduces the overhead of adding new signaling.
  • the first message may also carry a maximum number of reports, which is used to indicate the maximum number of times that a monitoring event report is allowed to be reported for one member, or the maximum number of reports is used to indicate that one member is allowed to be allowed.
  • the maximum number of times a monitoring event reports a monitoring event report, or the maximum number of reports is used to indicate the maximum total number of times that a monitoring event report is allowed to be reported for multiple monitoring events of one member.
  • the maximum number of reports is set for each member of the user group and applies to each member of the user group.
  • the first message may further carry a monitoring duration, where the monitoring duration is used to indicate an absolute time when the monitoring request expires.
  • the monitoring duration is set for each member of the user group and applies to each member of the user group.
  • the open function entity may determine the monitoring event report of the N members. The monitoring event reports for all members of the user group have been received.
  • the open function entity determines that the first message is used to configure a monitoring request for the user group; or And if the first message includes the first maximum number of reports, and the first maximum number of reports is 1, the open function entity determines that the first message is used to configure a monitoring request for the user group.
  • the open functional entity receives each member for each of the N members.
  • the monitoring event report of each of the plurality of monitoring events is reported, it is determined that the monitoring event reports of all users in the member group have been received.
  • the open function entity reports, for each member of the N members, the number of times of the monitored event report reaches the At the second maximum number of reports, it is determined that the monitoring event reports of all members of the member group have been received.
  • the open function entity receives the multiple for each member of the N members.
  • the number of monitoring event reports of each of the monitoring events reaches the second largest number of reports, it is determined that the monitoring event reports of all members of the user group have been received.
  • the foregoing methods are capable of determining that the monitoring event report of the members in the user group is received, thereby further initiating the configuration of deleting the monitoring event for the user group.
  • the open function entity receives a monitoring event report, and determines whether the one monitoring event report is the monitoring of the member.
  • the event report obtains a judgment result, and the judgment result is used to determine whether the monitoring event reports of all members in the user group have been received. In this way, it can help to ensure the accuracy of determining whether the monitoring event report of the members in the user group is received.
  • the open functional entity deletes a configuration of monitoring events for the user group, including at least one of the following operations: the open functional entity deletes a locally stored configuration of monitoring events for the user group Transmitting, by the open function entity, a second message to the user data management entity, the second message being used to instruct the user data management entity to delete a configuration of a monitoring event for the user group; The third-party application entity sends a third message, where the third message is used to instruct the third-party application entity to delete the configuration of the monitoring event for the user group.
  • the user data management entity is a home subscriber server HSS entity, or the unified data management UDM entity.
  • an event monitoring method is provided, the execution subject of which is an open functional entity.
  • the process of the specific method is as follows: receiving a first message, where the first message is used to configure a monitoring event for a user group, obtaining member information of the user group, and determining all the user groups according to the member information. Whether the member's monitoring event report is completed. Optionally, in the case that the determination is completed, the configuration of the monitoring event for the user group is deleted or the monitoring event report is stopped from being sent to the third-party application.
  • the open function entity obtains the member information of the user group, and when receiving the monitoring event report, can determine, according to the member information of the user group, that the monitoring event report of all members in the user group has been received, thereby further deleting the user.
  • the configuration of the monitoring event of the group or the stop sending the monitoring event report to the third-party application avoiding waste of resources, and helping to ensure the correct execution of the subsequent policies.
  • the open functional entity is a service capability open function SCEF entity, or the open functional entity is a network open function NEF entity.
  • SCEF entity service capability open function SCEF entity
  • NEF entity network open function NEF entity.
  • the member information of the user group may be the number of members included in the user group, and the number of members may be represented by N; the member information of the user group may also be the identifier of each member in the user group, that is, the user The member information of the group is N identifiers.
  • the open function entity can determine, according to the number of members included in the user group, or according to the identifier of the member, how many members have received the monitoring event report, thereby determining whether the monitoring event reports of all members in the user group have been received. .
  • Manner 1 The first message carries the member information of the user group, and obtains the member information of the user group from the first message.
  • Manner 2 Receive member information of the user group sent by the user data management entity, that is, obtain member information of the user group from the user data management entity. In this way, the member information of the user group is carried in the existing signaling, which reduces the overhead of adding new signaling.
  • the first message may also carry a maximum number of reports, which is used to indicate the maximum number of times that a monitoring event report is allowed to be reported for one member, or the maximum number of reports is used to indicate that one member is allowed to be allowed.
  • the maximum number of times a monitoring event reports a monitoring event report, or the maximum number of reports is used to indicate the maximum total number of times that a monitoring event report is allowed to be reported for multiple monitoring events of one member.
  • the maximum number of reports is set for each member of the user group and applies to each member of the user group.
  • the first message may further carry a monitoring duration, where the monitoring duration is used to indicate an absolute time when the monitoring request expires.
  • the monitoring duration is set for each member of the user group and applies to each member of the user group.
  • the open function entity may determine the monitoring event report of the N members. The monitoring event report for all members of the user group has been completed.
  • the open function entity determines that the first message is used to configure a monitoring request for the user group; or And if the first message includes the first maximum number of reports, and the first maximum number of reports is 1, the open function entity determines that the first message is used to configure a monitoring request for the user group.
  • the open function entity receives the monitoring event report of each of the plurality of monitoring events for each member of the N members, it is determined that the monitoring event report of all users in the member group has been carry out.
  • the open function entity reports, for each member of the N members, the number of times of the monitored event report reaches the At the second maximum number of reports, it is determined that the monitoring event reports of all members of the member group have been received.
  • the open functional entity is Determining, by each member of the N, the monitoring events of all members of the user group when the number of monitoring event reports of each of the plurality of monitoring events reaches the second maximum number of reports The report has been completed.
  • the foregoing methods are capable of determining that the monitoring event report of the members in the user group has been completed, thereby further initiating the deletion of the configuration of the monitoring event for the user group or stopping the sending of the monitoring event report to the third party application.
  • the open function entity receives a monitoring event report, and determines whether the one monitoring event report is the monitoring of the member.
  • the event report obtains a judgment result, and the judgment result is used to determine whether the monitoring event report of all members in the user group is completed. In this way, it can help to ensure the accuracy of determining whether the monitoring event report of the members in the user group is completed.
  • the open functional entity deletes a configuration of monitoring events for the user group, including at least one of the following operations: the open functional entity deletes a locally stored configuration of monitoring events for the user group.
  • the open function entity sends a second message to the third-party application entity, where the second message is used to instruct the third-party application entity to delete a configuration of a monitoring event for the user group.
  • the open function entity deletes the configuration of the monitoring event for the user group, including: the open function entity sends a third message to the user data management entity, where the third message is used to indicate The user data management entity deletes the configuration of the monitoring event for the user group; or the open function entity sends a fourth message to the user data management entity, where the fourth message is used to indicate that the user data management entity deletes Configuration of monitoring events for one or more members of the user group.
  • the open function entity determines that the monitoring event report of the one or more members has been completed, and the open function entity sends the fourth message to the user data management entity.
  • the user data management entity is a home subscriber server HSS entity, or the unified data management UDM entity.
  • the monitoring event report of the member in the user group is completed, that is, the monitoring event report of the user group is completed; the monitoring event report of all members of the user group is determined, that is, the monitoring event report of the user group is determined to be completed.
  • an event monitoring apparatus having the functionality to implement any of the possible aspects of the first aspect, the second aspect, the first aspect, and any one of the possible aspects of the second aspect.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the device can be a chip or an integrated circuit.
  • the apparatus includes a transceiver for communicating with the other functional entity or network element, and a processor for executing a set of programs, when the program is executed,
  • the apparatus may perform the method described in the first aspect and any of the possible designs of the first aspect above.
  • the apparatus also includes a memory that stores the program executed by the processor.
  • the device is a business capability open function SCEF entity, or is a network open function NEF entity.
  • a chip is provided, the chip being connected to a memory or the chip comprising a memory for reading and executing a software program stored in the memory to implement the first aspect, the second aspect, the first aspect as described above Any of the possible designs and methods described in any of the possible designs of the second aspect.
  • the fifth aspect provides an event monitoring method, where the execution entity of the method is a user data management entity, and the method is specifically: receiving a first request message, where the first request message is used to configure a monitoring event for a user group; Sending a first response message to the open function entity, where the first response message carries member information of the user group.
  • the open function entity can determine, according to the member information of the user group, that the monitoring event report of all members in the user group has been received when receiving the monitoring event report, thereby The configuration of the monitoring event of the user group can be further deleted or the monitoring event report can be sent to the third-party application to avoid waste of resources and help ensure the correct execution of the subsequent policies.
  • the member information of the user group may be the number of members included in the user group, and the number of members may be represented by N; the member information of the user group may also be the identifier of each member in the user group, that is, the user The member information of the group is N identifiers.
  • the open function entity can determine, according to the number of members included in the user group, or according to the identifier of the member, how many members have received the monitoring event report, thereby determining whether the monitoring event reports of all members in the user group have been received. .
  • the user data management entity receives a second request message sent by the open function entity, where the second request message carries information indicating that the configuration of the monitoring event for the user group is deleted, the user The data management entity deletes the configuration of the monitoring event for the user group according to the second request message.
  • the user data management entity receives a fourth request message sent by the open function entity, where the second request message carries one or more indicators for the user data management entity to delete the user group.
  • the configuration of the monitoring event of the member the user data management entity deleting the configuration of the monitoring event for one or more members of the user group according to the fourth request message.
  • the user data management entity is a home subscriber server HSS entity, or the unified data management UDM entity.
  • an event monitoring apparatus having the functionality to implement any of the possible aspects of the third aspect and the third aspect described above.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the device can be a chip or an integrated circuit.
  • the apparatus includes a transceiver for communicating with the other functional entity or network element, and a processor for executing a set of programs, when the program is executed,
  • the apparatus may perform the method described in any of the possible aspects of the second aspect and the second aspect described above.
  • the apparatus also includes a memory that stores the program executed by the processor.
  • the device is an HSS entity or a UDM entity.
  • a chip is provided, the chip being connected to a memory or the chip comprising a memory for reading and executing a software program stored in the memory to implement any of the third aspect and the third aspect as described above Possible methods described in the design.
  • the eighth aspect provides an event monitoring method, where the method is performed by a third-party application entity, where the method is specifically: sending a first message to the open function entity, where the first message is used to configure monitoring for a user group
  • the event the first message carries the member information of the user group.
  • the open function entity can determine, according to the member information of the user group, that the monitoring event report of all members in the user group has been received when receiving the monitoring event report, thereby The configuration of the monitoring event of the user group can be further deleted, the waste of resources is avoided, and the correct execution of the subsequent policies is ensured.
  • the member information of the user group may be the number of members included in the user group, and the number of members may be represented by N; the member information of the user group may also be the identifier of each member in the user group, that is, the user The member information of the group is N identifiers.
  • the open function entity can determine, according to the number of members included in the user group, or according to the identifier of the member, how many members have received the monitoring event report, thereby determining whether the monitoring event reports of all members in the user group have been received. .
  • the third message sent by the open function entity is received, where the third message carries information indicating that the configuration of the monitoring event for the user group is deleted, and the third party application entity is configured according to the third Message, delete the configuration of the monitoring event for the user group.
  • the third-party application entity is an SCS entity or an AS entity.
  • an event monitoring apparatus having a function of implementing any of the possible designs of the fourth aspect and the fourth aspect described above.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the device can be a chip or an integrated circuit.
  • the apparatus includes a transceiver for communicating with the other functional entity or network element, and a processor for executing a set of programs, when the program is executed,
  • the apparatus may perform the method described in any of the possible aspects of the fourth aspect and the fourth aspect above.
  • the apparatus also includes a memory that stores the program executed by the processor.
  • the device is an SCS entity or an AS entity.
  • a chip is provided, the chip being connected to a memory or the chip comprising a memory for reading and executing a software program stored in the memory to implement any of the fourth aspect and the fourth aspect described above Possible methods described in the design.
  • a computer storage medium is provided, stored with a computer program comprising instructions for performing any of the possible in-design methods of the various aspects and aspects described above.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the methods described in any of the above aspects and aspects of any of the possible aspects.
  • FIG. 1 is a structural diagram of service capability opening in an LTE system according to an embodiment of the present application
  • FIG. 2 is a structural diagram of service capability opening in a 5G system according to an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of an event monitoring method in an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of an event monitoring event in an application scenario according to an embodiment of the present application.
  • FIG. 5 is a second schematic flowchart of an event monitoring event in an application scenario according to an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of the event monitoring in the application scenario 2 in the embodiment of the present application.
  • FIG. 7 is a second schematic flowchart of event monitoring under the application scenario 2 in the embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of an event monitoring apparatus according to an embodiment of the present application.
  • FIG. 9 is a second schematic structural diagram of an event monitoring apparatus according to an embodiment of the present application.
  • An embodiment of the present invention provides an event monitoring method and apparatus, which are used to implement: in a group-based event monitoring, when an event report of all members in a group in an SCEF or a 5G system in an LTE system has been received, The configuration of the monitoring events of the group is deleted in time, thereby saving resources and helping to ensure the correct execution of subsequent policies.
  • FIG. 1 it is an architecture diagram of service capability exposure (SCE) in an LTE system, including: SCEF 101, SCS/AS 102, home subscriber server (HSS) 103, MME 104, and SGSN 105.
  • the SCEF 101 is the core network element of the service capability open architecture.
  • the SCEF 101 is used to ensure that the network securely provides service capabilities to third-party service providers to achieve reachability and interoperability between internal and external applications and services.
  • the third-party application obtains the service capability from the SCEF 101 through the SCS/AS 102.
  • the HSS 103 is a home subscriber subscription server and is used to save the subscriber's subscription information.
  • the mobility management network element includes an MME 104 and an SGSN 105 for performing mobility management on the terminal.
  • the SCS/AS 102 invokes the service capabilities provided by the SCEF 101 through the API interface of the T8.
  • FIG. 2 it is an architecture diagram of SCE in a 5G system, including: NEF201, SCS/AS202, UDM203, and AMF204.
  • NEF201 the function of the NEF 201 is similar to the function of the SCEF 101 in the LTE system, and the NEF 201 develops the services and capabilities supported by the 3GPP network to the SCS/AS 202 through the Nnef service.
  • the function of the UDM 203 is similar to the function of the HSS 103 in the LTE system.
  • the UDM 203 provides the supported service capability to the NEF 201 through the Nudm service.
  • the mobility management network element includes the AMF 204.
  • the function of the AMF 204 is similar to the function of the MME 104 in the LTE system, and the AMF 204 passes the Namf service to the NEF 201.
  • FIG. 1 and FIG. 2 are exemplary.
  • the methods provided in the embodiments of the present application are not limited to the two communication systems, and may be applied to more communication systems.
  • the SCS/AS can monitor one or more events for the user.
  • the event may be, for example, UE reachability, connection loss, location, and the like.
  • a user group is called a group.
  • a user group includes one or more members.
  • Members are users, that is, one user group includes one or more users.
  • the configuration of the monitoring event may be group-based, and all members in one group have the same external group identifier.
  • the member information may be: the number of members included in the user group.
  • the number of members is represented by N, and N is a positive integer;
  • the member information may also be an identifier of each member included in the user group, and the identifier is It is also used to distinguish different members. It can also be called member ID or user ID.
  • the external group ID of a member in a group is used to distinguish different user groups.
  • the member ID or user ID is used to distinguish different users (or members). of.
  • the open functional entity may refer to SCEF 101 or NEF 201.
  • the third-party application entity may refer to SCS/AS 102 or SCS/AS 202.
  • the mobility management network element may refer to the MME 104 and the SGSN 105, or may refer to the AMF 204.
  • the user data management entity may refer to the HSS 103 or the UDM 203.
  • the monitoring event report may carry related content of one or more monitoring events.
  • the open function entity distinguishes the monitoring event report of different monitoring events by monitoring the identifier of the event, and distinguishes the monitoring event report of different members by the identification of the member.
  • the specific process of the event monitoring method provided by the embodiment of the present application is as follows, and the execution body of the method is an open function entity.
  • the first message can be a monitoring request.
  • the first message is used to configure a monitoring event for a group of users, or the first message is used to configure a monitoring request for a group of users.
  • the user group includes one or more members, and the monitoring event or monitoring request for a user group is a monitoring event or monitoring request for each member in a user group.
  • the first message may be used to configure the number of monitoring events for a group of users to be one or more.
  • the one or more monitoring events are for each member of the user group.
  • the first group message may carry an external group ID of the user group, and the external group identifier is also used for each member in the user group to distinguish different user groups.
  • a monitoring request may also be referred to as an event subscription, which is used to subscribe to monitoring events for a group of users.
  • the first message may also carry a maximum number of reports, which is used to indicate the maximum number of times the monitoring event report is reported for one member, or the maximum number of reports is used to report a monitoring event report for a monitoring event of one member.
  • the maximum number of times, or the maximum number of reports is used to indicate the maximum total number of times a monitoring event report is reported for multiple monitoring events for a member.
  • the maximum number of reports is set for each member of the user group and applies to each member of the user group. Among them, the maximum number of reports is a positive integer.
  • the first message may also carry a monitoring duration, which is used to indicate the absolute time at which the monitoring request expires.
  • the monitoring duration is set for each member of the user group and applies to each member of the user group.
  • the first message may be used to configure a monitoring request for a user group, and the monitoring request is to report a monitoring event report to each member in the user group, wherein the number of monitoring events is one. And reporting a monitoring event report for the one monitoring event. If the number of monitoring events is multiple, reporting any one of the plurality of monitoring events in the one monitoring request or for each of the plurality of monitoring events A monitoring event reports a monitoring event report.
  • the first message is used to configure a monitoring request for a user group, and the following situations are as follows: (1) the first message includes the maximum number of reports, and the maximum number of reports is 1; (2) the first The maximum number of reports is not included in the message and does not include monitoring duration.
  • the member information of the user group can be obtained by, but not limited to, the following two methods.
  • Manner 1 The first message carries the member information of the user group, and obtains the member information of the user group from the first message.
  • Manner 2 Receive member information of the user group sent by the user data management entity, that is, obtain member information of the user group from the user data management entity.
  • the user data management entity herein may be an HSS entity or a UDM entity.
  • S303 Determine, according to the member information of the user group, that the monitoring event reports of all members of the user group have been received.
  • the open function entity receives the monitoring event report by one or more times, and stores the received monitoring event report locally when receiving the monitoring event report, and according to the received event report and the member information of the user group. Determine whether all members' monitoring event reports have been received (ie, determine if all members' monitoring event reports have been completed).
  • the mobility management network element also reports the monitoring request identifier (SCEF reference identifier or NEF event notification identifier), the identifier of the monitoring event, and the identifier of the member, the identifier of the monitoring request, and the monitoring event, each time the monitoring event report is reported.
  • the identity and the identity of the member are carried in the monitoring event report or carried along with the monitoring event report in a certain type of message, such as a monitoring response message.
  • the open function entity determines the user group, monitoring event, and member to which the monitoring event report belongs according to the identifier of the monitoring request, the identifier of the monitoring event, and the identifier of the member.
  • the member information of the user group can be the number of members included in the user group, and the number of members can be represented by N.
  • the member information of the user group can also be the identifier of each member in the user group, that is, the member information of the user group is N.
  • logo Each time an open function entity receives a monitoring event report, it can determine the user group to which the monitoring event report belongs, the monitoring event, and the member to which it belongs. Based on this, it is determined that the monitoring event reports of all members of the user group have been received, and there are several cases.
  • the first message is used to configure a monitoring request for the user group. In this case, for a monitoring event of one member, only one monitoring event report needs to be received.
  • the first message contains a monitoring event, that is, the first message is used to configure the number of monitoring events for the user group to be one, then:
  • the open function entity when the open function entity receives the N monitoring event reports, it can determine that the monitoring event reports of all members of the user group have been received, wherein N monitoring event reports are received.
  • the members are different from each other, that is, N monitoring events are reported as monitoring event reports of N different members. Since the open functional entity is able to determine which member the monitoring event report belongs to, the open functional entity can determine how many different members have received monitoring event reports.
  • the open function entity compares the identifier of the member associated with the received monitoring event report with the N identifiers, and if the monitoring event reports of the members of the N identifiers have been received, It can be determined that the monitoring event reports of all members of the user group have been received (ie, it is determined that the monitoring event report of all members of the user group has been completed).
  • the first message includes multiple monitoring events, that is, the first message is used to configure multiple monitoring events for the user group, for example, M, then:
  • the open function entity can also determine that the monitoring event reports of all members of the user group have been received when receiving the N monitoring event event reports. If the first message includes multiple monitoring events, that is, the first message is used to configure multiple monitoring events for the user group, for example, M, then each member of the N members receives the monitoring. The event report, or the monitoring event report is received for each of the M monitoring events of each member of the N members, and it is determined that the monitoring event reports of all members of the user group have been received (ie, the user group is determined) The monitoring event report for all members has been completed).
  • the open function entity may also determine that the monitoring event reports of all members of the user group have been received when the monitoring event reports of the members of the N identifiers have been received. Or the open function entity compares the identifier of the member associated with the received monitoring event report with the N identifiers, and compares the identifier of the monitoring event associated with the received monitoring event report with the identifier of the M monitoring events, if the N is for the N When each member of the identified members, the monitoring event report of each monitoring event of the M monitoring events has been received, it is determined that all the monitoring event reports of the members of the user group have been received (ie, all members of the user group are determined) The monitoring event report has been completed).
  • the first message carries the maximum number of reports, and the maximum number of reports is greater than one.
  • the monitoring event report of all members in the user group reaches the maximum number of reports, in order to determine that the monitoring event reports of all members of the user group have been received (ie, it is determined that the monitoring event report of all members of the user group has been completed).
  • the open function entity determines how many different members' monitoring event reports have been received based on the number N or N of the user groups. When the number of received monitoring event reports reaches the maximum number of reports for each member of N members, it is determined that the monitoring event reports of all members of the member group have been received. If the first message includes multiple monitoring events, that is, the first message is used to configure multiple monitoring events for the user group, for example, M, then the event is received for each member of the N members. The number of reports reaches the maximum number of reports, or the number of monitoring events reported for each of the M monitoring events of each member of the N members reaches the maximum number of reports, and the monitoring event reports of all members of the user group are determined. Received (ie, it is determined that the monitoring event report for all members of the user group has been completed).
  • the open function entity deletes the local monitoring event configuration for the user group.
  • the open function entity may further send a message to the third-party application entity, to instruct the third-party application entity to delete the configuration of the monitoring event for the user group.
  • the open function entity may further send a message to the user data management entity to instruct the user data management entity to delete the configuration of the monitoring event for the user group or to instruct the user data management entity to delete one or more of the user group for the user group.
  • the configuration of the member's monitoring event is a message to the third-party application entity, to instruct the third-party application entity to delete the configuration of the monitoring event for the user group.
  • the open function entity may further determine, when each monitoring event report is received, whether the received monitoring event report is a member of the user group.
  • Monitoring event report Specifically, determining whether the member identifier associated with the received monitoring event report is among the N identifiers, and if yes, determining that the received monitoring event report is a monitoring event report of a member of the user group; otherwise, determining the received The monitoring event report is not a monitoring event report for members of this user group. The result of the judgment is used to further determine whether the monitoring event reports of all members in the user group have been received (ie, it is determined that the monitoring event report of all members of the user group has been completed).
  • the open function entity obtains the member information of the user group, and when receiving the monitoring event report, can determine the monitoring of all members in the user group according to the member information of the user group.
  • the event report has been received, so that the configuration of the monitoring event of the user group can be further deleted or the monitoring event report can be sent to the third-party application to avoid waste of resources and help ensure the correct execution of the subsequent policies.
  • the event monitoring method of the present application is further described in detail based on the method provided in the foregoing embodiment and in combination with a specific application scenario.
  • Application scenario 1 LTE system.
  • the open functional entity is SCEF
  • the third-party application entity is SCS/AS
  • the mobility management network element is MME and SGSN
  • the user data management entity is HSS.
  • the SCS/AS sends a first monitoring request message based on the user group configuration to the SCEF, and the SCEF receives the first monitoring request message sent by the SCS/AS.
  • the first monitoring request message is the first message described in the foregoing embodiment, and has the attributes and functions of the first message.
  • the first monitoring request message carries the member information of the user group, and may be, but not limited to, carrying at least one of the following information: an SCS/AS identifier, a T8 destination address, a monitoring type, an external group identifier, and a T8 long-term cross reference identifier (T8Long Term). Transaction Reference ID, TLTRI), maximum number of reports, and/or monitoring duration. The maximum number of reports and/or monitoring duration is applied to each member of the user group. If the first monitoring request message does not carry the maximum number of reports and does not carry the monitoring duration, or the first monitoring request message carries the maximum number of reports, and the value of the maximum number of reports is 1, the first monitoring request message is indicated. Request for one monitoring.
  • the SCEF saves various information carried in the received monitoring request message, and the SCEF authorizes the configured monitoring request according to the local policy. After the authorization is successful, the SCEF allocates the SCEF reference ID and saves the correspondence between the SCEF Reference ID and the TLTRI.
  • the SCEF reference ID is used to identify this monitoring request within the core network, which in turn can determine the user group.
  • the SCEF sends a second monitoring request message to the HSS, where the HSS receives the second monitoring request message sent by the SCEF.
  • the second monitoring request message carries one or more kinds of information carried in the first monitoring request message in S401, and of course, does not need to carry the member information of the user group, for example, can carry an external group identifier, an SCEF identifier, a SCEF reference identifier, and a monitoring Types of.
  • the HSS checks the second monitoring request message. After the check is passed, the HSS saves the information carried in the received second monitoring request message. The HSS determines the members of the group corresponding to the external group identifier.
  • the HSS returns a first monitoring response message to the SCEF, where the SCEF receives the first monitoring response message sent by the HSS.
  • the first monitoring response message is used to confirm the second monitoring request message, and the first monitoring response message may carry the member information of the user group.
  • the first monitoring response message may also carry the SCEF reference identifier and the receiving indication.
  • the SCEF returns a second monitoring response message to the SCS/AS, and the SCS/AS receives the second monitoring response message returned by the SCEF.
  • the second monitoring response message carries the TLTRI and the reception indication.
  • S407 to S409 are executed for each member in the user group.
  • the HSS sends an insert user subscription data request to all MME/SGSNs serving the user group.
  • the insertion user subscription data request carries the monitoring type, SCEF identifier, SCEF reference identifier, maximum number of reports and/or monitoring duration, external identifier or mobile subscriber integrated service digital network/public switched telephone network number (Mobile Subscriber International ISDN/PSTN number) , MSISDN).
  • the MME/SGSN saves the parameters carried in the received request for inserting the user subscription data, and performs corresponding processing.
  • the MME/SGSN sets the number of remaining reports based on the maximum number of reports. For one request monitoring, the MME/SGSN can also set the remaining number of reports to 1.
  • the MME/SGSN sends an insert user subscription data response message to the HHS, and the HHS receives the inserted user subscription data response message sent by the MME/SGSN.
  • the inserted user subscription data response message carries an indication of receipt. If the MME/SGSN has a monitoring event of the current monitoring request, the MME/SGSN carries a monitoring event report in the inserted user subscription data response message. Further, if neither the maximum number of reports nor the duration is monitored in S407, or the remaining number of reports is 1, the MME/SGSN locally deletes the monitoring event configuration for the user group; if the maximum number of reports is carried in S407 If the value is greater than 1, the MME/SGSN decrements the number of remaining reports by one.
  • the HSS sends a first monitoring indication message to the SCEF, and the SCEF receives the first monitoring indication message sent by the HSS.
  • the first monitoring indication message carries an external identifier or an MSISDN corresponding to the SCEF Reference ID, the monitoring event report, and the monitoring event report.
  • the HSS may aggregate multiple monitoring event reports from the MME/SGSN and send them to the SCEF in a monitoring indication message. That is, the monitoring indication message carries a list of SCEF Reference IDs, and correspondences between monitoring event reports, external identifiers, or MSISDNs.
  • the SCEF sends a second monitoring indication message to the SCS/AS, and the SCS/AS receives the second monitoring indication message sent by the SCEF.
  • the second monitoring indication message carries the TLTRI, the monitoring event report, and the external group identifier or MSISDN. If the first monitoring indication message in S410 carries multiple monitoring event reports, the second monitoring indication message carries a list of TLTRIs, and a corresponding relationship between the monitoring event reports, external identifiers, or MSISDNs.
  • the SCS/AS returns a monitoring indication response message to the SCEF, and the SCEF receives the monitoring indication response message returned by the SCS/AS.
  • the MME/SGSN If the first monitoring request message is a monitoring request in S401, and the MME/SGSN has the monitoring event of the current monitoring request in S409, the MME/SGSN carries the monitoring event report in the inserted user subscription data response message, and in S410,
  • the HSS sends a monitoring event report from the MME/SGSN to the SCEF, and the SCEF first determines the user group corresponding to the event report according to the SCEF Reference ID, and then according to the member information of the user group received in S401 or S405 (for example, N identifiers, or The number of members N) determines whether the monitoring event report received by S410 contains the monitoring event report of all members.
  • the monitoring event report of all members is included, it is determined that the monitoring event reports of all members in the user group have been received (ie, it is determined that the monitoring event report of all members in the user group has been completed), and the monitoring event of deleting the user group is initiated. Configuration or stop sending monitoring event reports to SCS/AS. If the first monitoring request message includes multiple monitoring events, that is, the first monitoring request message is used to configure multiple monitoring events for the user group, for example, M, then the monitoring event report received according to S410.
  • the monitoring event report of the user group is completed when the monitoring event report of all members in the user group is completed.
  • the process of determining that the monitoring event reports of all members in the user group have been received is as follows. If the member information is the number of members, the SCEF determines, according to the number of different members (MSISDN or external identifier) associated with the monitoring event report received by the S410, to determine how many members have received the monitoring event report, and has received the When the number of members of the monitoring event report reaches the number of members of the member information, it is determined that the monitoring event reports of all members in the user group have been received.
  • MSISDN or external identifier the number of different members
  • the SCEF compares the identifiers of the different members associated with the monitoring event report received by the S410, and compares the identifiers of the members in the member information to determine how many members have received the monitoring event report. When the ID of the member who has received the monitoring event report has reached all the member IDs in the member information, it is determined that the monitoring event reports of all members in the user group have been received.
  • the SCEF when the SCEF receives the identifier of the member associated with the monitoring event report, determining whether the member of the identifier is a member of the user group according to whether the identifier of the member exists in the identifier of the member of the member information, If yes, continue to determine whether a monitoring event report has been received for all members of the user group.
  • the configuration of deleting the monitoring event of the user group is implemented by S414 to S418.
  • the SCEF sends a third monitoring request message to the HSS, where the HSS receives the third monitoring request message sent by the SCEF.
  • the third monitoring request message carries a SCEF Reference ID and a deletion indication.
  • the deletion indication is used to instruct the HSS to delete the configuration of the monitoring event of the user group.
  • the HSS deletes the configuration of the monitoring event of the user group according to the third monitoring request message.
  • the HSS sends a third monitoring response message to the SCEF, where the SCEF receives the third monitoring response message sent by the HSS.
  • the third monitoring response message is used to confirm the third monitoring request message.
  • the SCEF sends a fourth monitoring request message to the SCS/AS, and the SCS/AS receives the fourth monitoring request message sent by the SCEF.
  • the fourth monitoring request message carries a TLTRI and a deletion indication, and the deletion indication is used to instruct the SCS/AS to delete the configuration of the monitoring event of the user group.
  • the SCS/AS returns a fourth monitoring response message to the SCEF, and the SCEF receives the fourth monitoring response message returned by the SCS/AS.
  • the fourth monitoring response message is used to confirm the fourth monitoring request message.
  • S414 and S417 have no strict execution order, and may be exchanged in order or simultaneously.
  • the MME/SGSN If the MME/SGSN has the monitoring event of the current monitoring request in S409, the MME/SGSN carries the monitoring event report in the inserted user subscription data response message, but the maximum reporting number is greater than 1; or, S409 and S410 are not reported for monitoring. Event report. In both cases, the steps S410 to S418 are omitted.
  • S401 to S409 are processes for configuring a monitoring event of the user group. After S409, subsequent event monitoring can be implemented according to the monitoring process shown in FIG. 5.
  • the SCEF stops transmitting the monitoring event report to the SCS/AS.
  • the specific monitoring process is as follows.
  • the MME/SGSN After receiving the insert user data request message in S407 of FIG. 4, the MME/SGSN obtains information or parameters carried in the inserted user data request message, and performs event monitoring on members in the user group according to the information or parameters.
  • each member of the user group may belong to the same mobility management entity, or may belong to different mobility management entities, and the mobility management entity of the service user group may be one or more.
  • the process performed by each mobility management entity for members within the group of users it serves is the same or similar.
  • the MME/SGSN sends a monitoring indication message to the SCEF when the event of the member in the user group is detected, and the SCEF receives the monitoring indication message sent by the MME/SGSN.
  • the monitoring indication message carries the SCEF Reference ID, the monitoring event report, and the external identifier or MSISDN. If the first monitoring request message in S401 is a monitoring request, the MME/SGSN also locally deletes the configuration of the monitoring event for the user group. If the value of the maximum number of reports included in the first monitoring request message in S401 is greater than 1, the MME/SGSN decrements the number of remaining reports recorded by one. When the remaining number of reports is 0, the MME/SGSN locally deletes the configuration of the monitoring event for the user group.
  • S503 The SCEF sends a monitoring indication message to the SCS/AS, and the SCS/AS receives the monitoring indication message sent by the SCEF.
  • the monitoring indication message carries a TLTRI, a monitoring event report, and an external identifier or MSISDN.
  • the SCEF may aggregate multiple monitoring event reports from the MME/SGSN, and send the multiple monitoring event reports to the SCS/AS in a monitoring indication message.
  • the monitoring indication message is carried in the message.
  • TLTRI a list of correspondences with monitoring event reports, external identities, or MSISDN.
  • S504 The SCS/AS returns a monitoring indication response message to the SCEF, and the SCEF receives the monitoring indication response message returned by the SCS/AS.
  • the monitoring indication response message is used to confirm the monitoring indication message received in S503.
  • the processing of S505 and SCEF may include two types of processing.
  • the first type of processing includes the following situations.
  • the SCEF determines the user group corresponding to the event report according to the SCEF Reference ID received in S502, and determines whether the monitoring event report of all members has been received according to the member information of the user group received in S401 or S405. If the monitoring event report of all members has been received, it is determined that the monitoring event reports of all members of the user group have been received (ie, it is determined that the monitoring event report of all members of the user group has been completed), and the monitoring event of deleting the user group is initiated. Configuration or stop sending monitoring event reports to SCS/AS. The monitoring event report of the user group is completed when the monitoring event report of all members in the user group is completed.
  • the process of determining that the monitoring event reports of all members of the user group have been received is as follows.
  • the process of determining that the monitoring event reports of all members of the user group have been received is as follows: If the member information is the number of members, the SCEF determines, according to the number of different members (MSISDN or external identifier) associated with the monitoring event report received by the S502, how many members have received the monitoring event report, and has received the When the number of members of the monitoring event report reaches the number of members of the member information, it is determined that the monitoring event reports of all members of the user group have been received.
  • MSISDN MSISDN or external identifier
  • the SCEF compares the identifiers of the different members associated with the monitoring event report received by the S502, and compares the identifiers of the members in the member information to determine how many members have received the monitoring event report. When the ID of the member who has received the monitoring event report has reached all the member IDs in the member information, it is determined that the monitoring event reports of all members of the user group have been received.
  • the SCEF receives the identifier of the member associated with the monitoring event report, determining whether the member of the identifier is a member of the user group according to whether the identifier of the member exists in the identifier of the member of the member information, If yes, continue to determine if a monitoring event report has been received for all members of the user group. If the first monitoring request message includes multiple monitoring events, that is, the first monitoring request message is used to configure multiple monitoring events for the user group, for example, M, then the monitoring event report received according to S502. Receiving a monitoring event report for each member of the N members, or receiving a monitoring event report for each of the M monitoring events for each member of the N members, determining the user group All members' monitoring event reports have been received.
  • the SCEF determines that the monitoring event reports of all members of the user group have been received according to the member information of the user group (for example, N identifiers or the number of members N) are as follows. If the member information is the number of members, the SCEF determines the number of monitoring events reported by the member according to the number of different members (MSISDN or external identifier) associated with the monitoring event report received by S502, and determines each of the members. Whether the cumulative number of reports for a member has reached the maximum number of reports.
  • MSISDN number of different members
  • the SCEF compares the identifiers of the different members associated with the monitoring event report received by the S502, and compares the identifiers of the members in the member information to determine how many members have received the monitoring event report. And determine whether the cumulative number of reports for each member has reached the maximum number of reports.
  • the SCEF receives the identifier of the member associated with the monitoring event report, determining whether the member of the identifier is a member of the user group according to whether the identifier of the member exists in the identifier of the member of the member information, If yes, continue to determine whether a monitoring event report has been received for all members of the user group.
  • the first message includes multiple monitoring events, that is, the first message is used to configure multiple monitoring events for the user group, for example, M
  • the event is received for each member of the N members.
  • the number of reports reaches the maximum number of reports, or the number of monitoring events reported for each of the M monitoring events of each member of the N members reaches the maximum number of reports, and the monitoring event reports of all members of the user group are determined. Received.
  • the configuration of deleting the monitoring event of the user group is implemented by S506 to S510. (In the first type of processing, S506 to S510 need only be executed once.)
  • the SCEF sends a monitoring request message to the HSS, and the HSS receives the monitoring request message sent by the SCEF.
  • the monitoring request message carries a SCEF Reference ID and a deletion indication.
  • the deletion indication is used to instruct the HSS to delete the configuration of the monitoring event of the user group.
  • the HSS deletes the configuration of the monitoring event of the user group according to the monitoring request message.
  • the HSS sends a monitoring response message to the SCEF, and the SCEF receives the monitoring response message sent by the HSS.
  • the monitoring response message is used to confirm receipt of the monitoring request message of S506.
  • S509 The SCEF sends a monitoring request message to the SCS/AS, and the SCS/AS receives the monitoring request message sent by the SCEF.
  • the monitoring request message carries a TLTRI and a deletion indication, and the deletion indicates a configuration for instructing the SCS/AS to delete the monitoring event of the user group.
  • S510 The SCS/AS returns a monitoring response message to the SCEF, and the SCEF receives the monitoring response message returned by the SCS/AS.
  • the monitoring response message is used to confirm the monitoring request message of S509.
  • S506 and S509 do not have strict execution order, and may be exchanged in order or simultaneously.
  • S503 and S505 do not have a strict execution order, and they can be exchanged in order or simultaneously.
  • the second type of processing includes the following cases.
  • the SCEF determines the user group corresponding to the event report according to the SCEF Reference ID received in S502, and if it is determined whether the monitoring event report of any member corresponding to the event report is received (that is, whether the monitoring event report is completed), if the receiving is completed, the HSS is requested. Delete the configuration of the member's monitoring event.
  • the SCEF further determines whether the monitoring event report of all members of the user group is received according to the member information of the user group received in S401 or S405 (that is, whether the monitoring event report is completed). If it has been received, execute: delete the configuration of the monitoring event of the local user group and request the SCS/AS to delete the configuration of the monitoring event of the user group or stop sending the event report to the SCS/AS.
  • the HSS can also be sent to the HSS. Sending a message, the message is used to instruct the HSS to delete the configuration of the monitoring event for the user group.
  • the SCEF requests the HSS to delete the configuration of the monitoring event of the member,
  • the SCEF sends a message to the HSS indicating that the configuration of the monitoring event for the user group is deleted is an optional step.
  • the SCEF further determines that the monitoring event configuration deletion request message has been sent to the HSS for all members of the user group, deleting the configuration of the monitoring event of the local user group and requesting the SCS/AS to delete the configuration of the monitoring event of the user group.
  • the monitoring event report of the user group is completed when the monitoring event report of all members in the user group is completed.
  • the process of determining that the monitoring event report of the member corresponding to the event report has been received is as follows:
  • the first monitoring request message in S401 is a monitoring request and the event report of a member received in S502, it is determined that the monitoring event report receiving of the member corresponding to the event report is completed; if the value of the maximum reporting number is greater than 1 and After S502, if the number of event reports of a member received reaches the maximum number of reports, it is determined that the monitoring event report of the member corresponding to the event report is received.
  • the SCEF receives the identifier of the member associated with the monitoring event report, determining whether the member of the identifier is a member of the user group according to whether the identifier of the member exists in the identifier of the member of the member information, If yes, it is judged that the monitoring event report of the corresponding member has been received.
  • the first message includes multiple monitoring events, that is, the first message is used to configure multiple monitoring events for the user group, for example, M
  • the number of event reports received by one member reaches the maximum number of reports
  • the number of monitoring event reports of each of the M monitoring events of one member reaches the maximum number of reports
  • the monitoring event report of the member corresponding to the event report is determined to have been received.
  • the configuration of the monitoring event of the member is deleted by the HSS by S506-S508. (In the second type of processing, S506 to S508 need to be executed multiple times, or even N times.)
  • the SCEF sends a monitoring request message to the HSS, and the HSS receives the monitoring request message sent by the SCEF.
  • the monitoring request message carries a SCEF Reference ID, an external group identifier, a member identifier (ie, an external identifier and/or an MSISDN), and a deletion indication.
  • the deletion indicates a configuration for instructing the HSS to delete the monitoring event of the member corresponding to the member identifier.
  • the HSS deletes the configuration of the monitoring event of the member according to the monitoring request message.
  • the HSS sends a monitoring response message to the SCEF, and the SCEF receives the monitoring response message sent by the HSS.
  • the monitoring response message is used to confirm receipt of the monitoring request message of S506.
  • the SCEF carries multiple member identifiers in the monitoring request message of the S506, and the HSS deletes the configuration of the monitoring event corresponding to the multiple member identifiers.
  • the process of determining that the monitoring event reports for all members of the user group have been received is as follows.
  • the process of determining that the monitoring event reports of all members of the user group have been received is as follows: If the member information is the number of members, the SCEF determines, according to the number of different members (MSISDN or external identifier) associated with the monitoring event report received by the S502, how many members have received the monitoring event report, and has received the When the number of members of the monitoring event report reaches the number of members of the member information, it is determined that the monitoring event reports of all members of the user group have been received.
  • MSISDN MSISDN or external identifier
  • the SCEF compares the identifiers of the different members associated with the monitoring event report received by the S502, and compares the identifiers of the members in the member information to determine how many members have received the monitoring event report. When the ID of the member who has received the monitoring event report has reached all the member IDs in the member information, it is determined that the monitoring event reports of all members of the user group have been received.
  • the SCEF receives the identifier of the member associated with the monitoring event report, determining whether the member of the identifier is a member of the user group according to whether the identifier of the member exists in the identifier of the member of the member information, If yes, continue to determine if a monitoring event report has been received for all members of the user group. If the first monitoring request message includes multiple monitoring events, that is, the first monitoring request message is used to configure multiple monitoring events for the user group, for example, M, then the monitoring event report received according to S502. Receiving a monitoring event report for each member of the N members, or receiving a monitoring event report for each of the M monitoring events for each member of the N members, determining the user group All members' monitoring event reports have been received.
  • the SCEF determines that the monitoring event reports of all members of the user group have been received according to the member information of the user group (for example, N identifiers or the number of members N) are as follows. If the member information is the number of members, the SCEF determines the number of monitoring events reported by the member according to the number of different members (MSISDN or external identifier) associated with the monitoring event report received by S502, and determines each of the members. Whether the cumulative number of reports for a member has reached the maximum number of reports.
  • MSISDN number of different members
  • the SCEF compares the identifiers of the different members associated with the monitoring event report received by the S502, and compares the identifiers of the members in the member information to determine how many members have received the monitoring event report. And determine whether the cumulative number of reports for each member has reached the maximum number of reports.
  • the SCEF receives the identifier of the member associated with the monitoring event report, determining whether the member of the identifier is a member of the user group according to whether the identifier of the member exists in the identifier of the member of the member information, If yes, continue to determine whether a monitoring event report has been received for all members of the user group.
  • the first message includes multiple monitoring events, that is, the first message is used to configure multiple monitoring events for the user group, for example, M
  • the event is received for each member of the N members.
  • the number of reports reaches the maximum number of reports, or the number of monitoring events reported for each of the M monitoring events of each member of the N members reaches the maximum number of reports, and the monitoring event reports of all members of the user group are determined. Received.
  • the configuration of deleting the monitoring event of the user group is implemented by S509 to S510.
  • S509 The SCEF sends a monitoring request message to the SCS/AS, and the SCS/AS receives the monitoring request message sent by the SCEF.
  • the monitoring request message carries a TLTRI and a deletion indication, and the deletion indicates a configuration for instructing the SCS/AS to delete the monitoring event of the user group.
  • S510 The SCS/AS returns a monitoring response message to the SCEF, and the SCEF receives the monitoring response message returned by the SCS/AS.
  • the monitoring response message is used to confirm the monitoring request message of S509.
  • the monitoring request message and the monitoring response message sent by different steps in FIG. 5 are not distinguished. It can be understood that messages of the same name may carry the same content or may be different.
  • the steps shown in S505 to S510 in FIG. 5 are the same, but in fact, according to the above description, different steps can be explained according to the two different types of processing of SCEF in S505, and the detailed description of each step is as described above.
  • the SCEF temporarily does not execute S506 to S510 for some reason, during this period, the SCEF receives the event report for monitoring the event request in step S401, the SCEF stops transmitting the monitoring event report to the SCS/AS.
  • the SCEF can obtain the member information of the user group, and when receiving the monitoring event report, can determine the user group according to the member information of the user group. All members' monitoring event reports have been received, which can further delete the configuration or stop event report of the monitoring events of the user group, avoid resource waste, and help ensure the correct execution of subsequent policies.
  • Application scenario 2 5G system.
  • the open functional entity is NEF
  • the third-party application entity is SCS/AS
  • the mobility management network element is AMF
  • the user data management entity is UDM203.
  • the process of event monitoring in the application scenario 2 is specifically as follows.
  • the SCS/AS sends a Nnef_Event Exposure_Subscribe request message to the NEF, and the NEF receives the NSN_Event Exposure_Subscribe request message from the SCS/AS.
  • the Nnef_EventExposure_Subscribe request message is the first message described in the foregoing embodiment, and has the attributes and functions of the first message.
  • the Nnef_EventExposure_Subscribe request message carries the member information of the user group, and may be, but not limited to, carrying at least one of the following information: an SCS/AS event notification address and an event notification identifier, a monitoring event (Monitoring Event), and an external group identifier (External Group Id). , event reporting mode.
  • the event reporting mode can take the value of the maximum number of reports, periodic reports, or reports to reach the maximum duration. If the event report granularity is that the report reaches the maximum number of times, the Nnef_EventExposure_Subscribe request message also carries the maximum number of reports.
  • the parameter configuration in the monitoring event subscription message applies to every member of the user group. If the event report granularity is the maximum number of reports, the value of the maximum number of reports carried in the Nnef_EventExposure_Subscribe request message is 1, indicating that the Nnef_EventExposure_Subscribe request message is a monitoring request.
  • the subscription of monitoring events can be similar to the configuration of monitoring events in an LTE system.
  • the NEF saves various information carried in the message received by the S601, and the NEF authorizes the monitoring request of the subscription according to the local policy.
  • the NEF sends a monitoring event subscription request message, that is, a Nudm_EventExposure_Subscribe Request message, to the UDM, and the UDM receives the Nudm_EventExposure_Subscribe Request message sent by the NEF.
  • the message carries the External Group Id, Monitoring Event, NEF event notification address, and event notification identifier. It can also carry some optional parameters in the Nnef_EventExposure_Subscribe request message in S601.
  • the NEF event notification address and event notification identifier are used to correlate future event notifications to determine the user group.
  • the UDM checks the Nudm_EventExposure_Subscribe Request message received in S603, and after the check is passed, the UDM saves the parameters carried in the message.
  • the UDM determines the correspondence between the external group identifier and the identity of the user group member.
  • the UDM sends a monitoring event subscription response message (Nudm_Event Exposure_Subscribe Reponse) message to the NEF, and the NEF receives the monitoring event subscription response message sent by the UDM.
  • a monitoring event subscription response message (Nudm_Event Exposure_Subscribe Reponse) message
  • the monitoring event subscription response message carries the member information of the user group.
  • the monitoring event subscription response message also carries the received UDM subscription identifier and the receiving indication.
  • the NEF sends a monitoring event subscription response message (Nnef_Event Exposure_Subscribe Response) to the SCS/AS, and the SCS/AS receives the monitoring event subscription response message sent by the NEF.
  • Nnef_Event Exposure_Subscribe Response a monitoring event subscription response message
  • the message carries an NEF subscription identifier and an indication of receipt.
  • S607 to S611 are executed for each member in the user group.
  • the UDM sends a Subscriber Data Management (SDM) notification request message (Nudm_SDM_Notification Request) to the AMF serving the member, and the AMF receives the SDM notification request message sent by the UDM.
  • SDM Subscriber Data Management
  • the message carries an external identifier or MSISDN, and can also carry the maximum number of reports.
  • the UDM is a member described in S607, and sends a monitoring event subscription request message (Namf_EventExposure_Subscribe Request) to the AMF, and the AMF receives the Namf_EventExposure_Subscribe Request message sent by the UDM.
  • Namf_EventExposure_Subscribe Request a monitoring event subscription request message
  • the message carries the Monitoring Event, the NEF event notification address, and the event notification identifier.
  • the AMF saves the parameters of the received Namf_EventExposure_Subscribe Request message and performs corresponding processing.
  • the process includes setting the number of remaining reports based on the maximum number of reports.
  • the AMF sends an SDM notification response message (Nudm_SDM_Notification Reponse) to the UDM, and the UDM receives the Nudm_SDM_Notification Reponse message sent by the AMF.
  • SDM notification response message Nudm_SDM_Notification Reponse
  • the message carries the received indication.
  • the AMF returns a monitoring event subscription response message (Namf_EventExposure_Subscribe Response) to the UDM, and the UDM receives the Namf_Event Exposure_Subscribe Response message sent by the AMF.
  • Namf_EventExposure_Subscribe Response a monitoring event subscription response message
  • the message carries an AMF subscription identifier and an indication of receipt. If the AMF has a monitoring event report of the monitoring event subscribed to this time, the AMF carries the monitoring event report, the NEF event notification address, and the event notification identifier in the Namf_Event Exposure_Subscribe Response message. Further, if the monitoring event is subscribed to the first monitoring request in S607, the AMF deletes the monitoring event configuration for the user group locally; if the maximum number of reporting times in S607 is greater than 1, the AMF reduces the remaining reporting times. 1.
  • the UDM sends a monitoring event notification request message (Ndum_EventExposure_Notify Request) to the NEF, and the NEF receives the Ndum_EventExposure_Notify Request message sent by the UDM.
  • the NEF returns a Ndum_EventExposure_Notify Response message to the UDM.
  • the Ndum_EventExposure_Notify Reques message carries an external identifier or MSISDN corresponding to the NEF event notification identifier, the monitoring event report, and the monitoring event report.
  • the UDM may aggregate multiple monitoring event reports from the AMF and send them to the NEF in a monitoring event notification request message. That is, the monitoring event notification request message carries a NEF event notification identifier, and monitors a list of correspondences of event reports, external identifiers, or MSISDNs.
  • the NEF sends a monitoring event subscription request message (Nnef_Event Exposure_Notify Request) to the SCS/AS, and the SCS/AS receives the Nnef_EventExposure_Notify Request message sent by the NEF.
  • the SCS/AS returns a monitoring event subscription response message (Nnef_Event Exposure_Notify Response) to the NEF, and the NEF receives the Nnef_EventExposure_Notify Response returned by the SCS/AS.
  • the Nnef_EventExposure_Notify Request message carries an SCS/AS event notification identifier, a monitoring event report, and an external identifier or MSISDN. If the S612 carries a plurality of monitoring event reports, the Nnef_Event Exposure_Notify Request message carries a list of correspondences between the SCS/AS event notification identifier and the monitoring event report, the external identifier, or the MSISDN.
  • the processing of S614 and NEF includes the following cases.
  • the UDM sends a monitoring event report from the AMF to the NEF in S612, and the NEF receives the NEF notification according to the received NEF.
  • the user group corresponding to the determination event report is identified, and according to the member information of the user group received in S601 or S605, it is determined whether the monitoring event report received by S612 includes the monitoring event report of all members.
  • the monitoring event report of all members is included, it is determined that the monitoring event reports of all members in the user group have been received (ie, it is determined that the monitoring event report of all members in the user group has been completed), and the monitoring event of deleting the user group is initiated. Configure or stop sending monitoring event reports to the SCS/AS.
  • the monitoring event report of the user group is completed when the monitoring event report of all members in the user group is completed.
  • the process of determining that the monitoring event reports of all members in the user group have been received is as follows. If the member information is the number of members, the NEF determines, according to the number of different members (MSISDN or external identifier) associated with the monitoring event report received by the S612, how many monitoring events reports have been received, and has received When the number of members of the monitoring event report reaches the number of members of the member information, it is determined that the monitoring event reports of all members in the user group have been received.
  • MSISDN the number of different members
  • the NEF compares the identifiers of the different members associated with the monitoring event report received in S612, and compares the identifiers of the members in the member information to determine how many members have received the monitoring event report. When the ID of the member who has received the monitoring event report has reached all the member IDs in the member information, it is determined that the monitoring event reports of all members in the user group have been received.
  • the NEF receives the identifier of the member associated with the monitoring event report, determining whether the member of the identifier is a member of the user group according to whether the identifier of the member exists in the identifier of the member of the member information, If yes, continue to determine whether a monitoring event report has been received for all members of the user group.
  • the monitoring event subscription request includes multiple monitoring events, that is, the monitoring event subscription request is used to configure multiple monitoring events for the user group, for example, M, then according to the monitoring event report received in S612, For each member of the N members, a monitoring event report is received, or a monitoring event report is received for each of the M monitoring events of each member of the N members, and all members of the user group are determined. The monitoring event reports have been received.
  • the subscription for deleting the monitoring event of the user group is implemented by S615 ⁇ S622.
  • the NEF sends a monitoring event to subscription request (Nudm_EventExposure_Unsubscribe Request) to the UDM, and carries the UDM subscription identifier in the Nudm_EventExposure_Unsubscribe Request message.
  • the UDM receives the Nudm_EventExposure_Unsubscribe Request message sent by the NEF.
  • the UDM sends a monitoring event to a subscription request (Namf_EventExposure_Unsubscribe Request), and the AMF receives the Namf_EventExposure_Unsubscribe Request sent by the UDM.
  • the AMF subscription identifier is carried in the Namf_EventExposure_Unsubscribe Request message.
  • the AMF deletes the monitoring event subscription information corresponding to the AMF subscription identifier.
  • the AMF returns a response message to the UDM.
  • the UDM deletes the monitoring event subscription information corresponding to the UDM subscription identifier, and returns an acknowledgement message to the NEF.
  • the NEF sends a monitoring event notification request message (Nnef_EventExposure_Notifiy Request) to the SCS/AS, and carries the SCS event notification identifier and the deletion indication in the Nnef_EventExposure_Notifiy Request message.
  • the SCS/AS returns a reply message.
  • the SCS/AS sends a monitoring event to a subscription request (Nnef_EventExposure_Unsubscribe Request) to the NEF, and carries an NEF subscription identifier in the Nnef_EventExposure_Unsubscribe Request message.
  • the NEF deletes the event subscription information corresponding to the NEF subscription identifier and returns an acknowledgement message.
  • S615 and S620 do not have strict execution order, and may be exchanged in order or simultaneously.
  • the SCEF receives the monitoring event report for monitoring the event subscription request in step S601, the SCEF stops sending the monitoring event report to the SCS/AS.
  • the specific monitoring process is as follows.
  • the SMF After receiving the Nudm_SDM_Notification Reponse message, the SMF performs event monitoring on the members in the user group according to the parameters carried in the Nudm_SDM_Notification Reponse message.
  • each member of the user group may belong to the same AMF, or may belong to a different AMF, and the AMF of the service user group may be one or more.
  • the process performed by each AMF for members within the user group it serves is the same or similar.
  • the AMF sends a monitoring event notification request message to the NEF, that is, a Namf_EventExposure_Notify Request message, where the Namf_EventExposure_Notify Request message carries an external identifier or an MSISDN corresponding to the NEF event notification address and the identifier, the monitoring event report, and the monitoring event report.
  • the event reporting mode is that the report reaches the maximum number of times and the maximum number of reports is 1, the AMF deletes the monitoring event subscription for the user group locally. If the value of the maximum number of reports is greater than 1, the AMF decrements the number of remaining reports recorded by one. When the remaining number of reports is 0, the AMF locally deletes the configuration of the monitoring event for the user group.
  • the NEF returns an acknowledgement message to the AMF, that is, Namf_EventExposure_Notify Reponse.
  • the AMF receives the Namf_EventExposure_Notify Reponse returned by the NEF.
  • the NEF sends a monitoring event notification request to the SCS/AS, that is, the Nnef_EventExposure_Notify Request, and the Nnef_EventExposure_Notify Request message carries the SCS, the AS event notification identifier, the monitoring event report, and the external identifier or the MSISDN.
  • the NEF may aggregate multiple monitoring event reports from the AMF and send them to the SCS/AS in an Nnef_EventExposure_Notify Request message, where the Nnef_EventExposure_Notify Request message carries the SCS/AS event notification identifier and the monitoring event report, the external identifier, or A list of correspondences of MSISDN.
  • the SCS/AS returns an acknowledgement message to the SCEF, that is, Nnef_EventExposure_Notify Reponse, and the SCEF receives the Nnef_EventExposure_Notify Reponse returned by the SCS/AS.
  • the processing of S706 and NEF includes the following cases.
  • the NEF determines the user group corresponding to the event report according to the event notification identifier received in S602, and determines whether the monitoring event report of all members has been received according to the member information of the user group received in S601 or S605, and if it is determined that all the information has been received,
  • the monitoring event report of the member determines that the monitoring event report of all members of the user group has been received (determined that the monitoring event report of all members of the user group has been completed), initiates the configuration of deleting the monitoring event of the user group or stops the SCS /AS sends a monitoring event report.
  • the monitoring event report of the user group is completed when the monitoring event report of all members in the user group is completed.
  • the process of determining that the monitoring event reports of all members of the user group have been received is as follows.
  • the process of determining that the monitoring event reports of all members of the user group have been received is as follows: If the member information is the number of members, the NEF determines, according to the number of different members (MSISDN or external identifier) associated with the monitoring event report received by the S612, how many monitoring events reports have been received, and the monitoring has been received. When the number of members of the event report reaches the number of members of the member information, it is determined that the monitoring event reports of all members of the user group have been received.
  • the NEF compares the identifiers of the different members associated with the monitoring event report received in S612, and compares the identifiers of the members in the member information to determine how many members have received the monitoring event report. When the ID of the member who has received the monitoring event report has reached all the member IDs in the member information, it is determined that the monitoring event reports of all members of the user group have been received.
  • the NEF receives the identifier of the member associated with the monitoring event report, determining whether the member of the identifier is a member of the user group according to whether the identifier of the member exists in the identifier of the member of the member information, If yes, continue to determine if a monitoring event report has been received for all members of the user group. If the first monitoring request message includes multiple monitoring events, that is, the first monitoring request message is used to configure multiple monitoring events for the user group, for example, M, then the monitoring event report received according to S612 Receiving a monitoring event report for each member of the N members, or receiving a monitoring event report for each of the M monitoring events for each member of the N members, determining the user group All members' monitoring event reports have been received.
  • the NEF determines that the monitoring event reports of all members in the user group have been received according to the member information of the user group (for example, N identifiers or the number of members N) are as follows. If the member information is the number of members, the NEF determines the number of monitoring events reported by the member according to the number of different members (MSISDN or external identifier) associated with the monitoring event report received in S612, and determines each of the members. Whether the cumulative number of reports for a member has reached the maximum number of reports. When the number of members who have received the monitoring event report reaches the number of members of the member information, and the cumulative number of reports for each member reaches the maximum number of reports, it is determined that the monitoring event reports of all members in the user group have been received.
  • MSISDN number of different members
  • the NEF compares the identifiers of the different members associated with the monitoring event report received in S612, and compares the identifiers of the members in the member information to determine how many members have received the monitoring event report. And determine whether the cumulative number of reports for each member has reached the maximum number of reports. When the ID of the member who has received the monitoring event report has reached all the member IDs in the member information, and the cumulative number of reports for each member reaches the maximum number of reports, it is determined that the monitoring event reports of all members in the user group have been received. .
  • the NEF receives the identifier of the member associated with the monitoring event report, determining whether the member of the identifier is a member of the user group according to whether the identifier of the member exists in the identifier of the member of the member information, If yes, continue to determine whether a monitoring event report has been received for all members of the user group.
  • the first message includes multiple monitoring events, that is, the first message is used to configure multiple monitoring events for the user group, for example, M
  • the event is received for each member of the N members.
  • the number of reports reaches the maximum number of reports, or the number of monitoring events reported for each of the M monitoring events of each member of the N members reaches the maximum number of reports, and the monitoring event reports of all members of the user group are determined. Received.
  • the S707-S714 is used to delete the subscription of the monitoring event of the user group.
  • the specific S707-S714 are the same as S615-S622, and the repeated description is not repeated.
  • the SCEF receives the monitoring event report for monitoring the event subscription request in step S601, the SCEF stops sending the monitoring event report to the SCS/AS.
  • the NEF can obtain the member information of the user group, and when receiving the monitoring event report, the NEF can determine the user group according to the member information of the user group. All members' monitoring event reports have been received, which can further delete the configuration of monitoring events of the user group or stop sending monitoring event reports to the SCS/AS, avoiding waste of resources and helping to ensure the correct execution of subsequent policies.
  • the embodiment of the present application further provides an event monitoring apparatus 800, where the event monitoring apparatus 800 includes: a receiving unit 801 and a processing unit 802.
  • the event monitoring device 800 is configured to perform the steps performed by the open function entity in the event monitoring method provided in the foregoing embodiment, specifically:
  • the receiving unit 801 is configured to receive a first message, where the first message is used to configure a monitoring event for a group of users.
  • a processing unit configured to acquire member information of the user group, and configured to determine, according to the member information, that the monitoring event report of all members of the user group has been received, delete the configuration of the monitoring event for the user group, or acquire the user Member information of the group, and used to determine whether the monitoring event report of all members of the user group is completed based on the member information.
  • the receiving unit 801 and the processing unit 802 in the event monitoring device 800 can also be used to perform other steps corresponding to the open function entity in the event monitoring method provided in the foregoing embodiment, and the repeated description is not repeated herein.
  • the event monitoring apparatus 800 is further configured to perform the steps performed by the user data management entity in the event monitoring method provided in the foregoing embodiment, specifically:
  • the receiving unit 801 and the processing unit 802 in the event monitoring apparatus 800 can also be used to perform other steps corresponding to the user data management entity in the event monitoring method provided by the foregoing embodiment, and the repeated description is not repeated herein.
  • the event monitoring device 800 is further configured to perform the steps performed by the third-party application entity in the event monitoring method provided in the foregoing embodiment, specifically:
  • the receiving unit 801 and the processing unit 802 in the event monitoring device 800 can also be used to perform other steps corresponding to the third-party application entity in the event monitoring method provided by the foregoing embodiment, and the repeated description is not repeated herein.
  • the embodiment of the present application further provides an event monitoring device 900, where the network parameter tuning device 900 is configured to execute the event monitoring method, and the event monitoring device 900 includes: The transceiver 901, the processor 902, and the memory 903.
  • Memory 903 is optional.
  • the processor 902 is configured to invoke a set of programs that, when executed, cause the processor 902 to perform the event monitoring method described above.
  • the memory 903 is used to store programs executed by the processor 902.
  • the function module receiving unit 801 in FIG. 8 can be implemented by the transceiver 901, and the processing unit 802 can be implemented by the processor 902.
  • the processor 902 can be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP.
  • CPU central processing unit
  • NP network processor
  • Processor 902 can also further include a hardware chip.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • the PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or any combination thereof.
  • the memory 903 may include a volatile memory such as a random-access memory (RAM); the memory 903 may also include a non-volatile memory such as a flash memory (flash) Memory), hard disk drive (HDD) or solid state drive (SSD); the memory 903 may also include a combination of the above types of memories.
  • RAM random-access memory
  • non-volatile memory such as a flash memory (flash) Memory), hard disk drive (HDD) or solid state drive (SSD); the memory 903 may also include a combination of the above types of memories.
  • the embodiment of the present application further provides a chip, including a processor, for supporting the apparatus to implement an open function entity or a user data management entity in the event monitoring method, Or the functionality involved in a third-party application entity.
  • the chip is coupled to a memory or the chip includes a memory for storing program instructions and data necessary for the device.
  • the embodiment of the present application provides a computer storage medium, where a computer program is stored, and the computer program includes a method for monitoring the event.
  • An embodiment of the present application provides a computer program product comprising instructions that, when run on a computer, cause the computer to perform the event monitoring method described above.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种事件监控方法及装置，用以实现业务能力开放功能或者网络开放功能在接收到组内全部成员的事件报告后删除该组的监控事件配置，从而避免资源的浪费和后续策略执行错误。该方法为：开放功能实体接收第一消息，所述第一消息用于配置针对一个用户组的监控事件，开放功能实体获取所述用户组的成员信息，所述开放功能实体根据所述成员信息，确定所述用户组的所有成员的监控事件报告均已接收完毕，删除针对所述用户组的监控事件的配置。

Description

一种事件监控方法及装置
本申请要求了2018年4月9日提交的、申请号为201810312936.6、发明名称为“一种事件监控方法及装置”的中国申请的优先权，以及2018年4月18日提交的、申请号为201810349848.3、发明名称为“一种事件监控方法及装置”的中国申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，尤其涉及一种事件监控方法及装置。
背景技术
随着移动互联网的发展，运营商需要与第三方应用提供商进行互通，为第三方应用提供商提供的业务进行保障。在长期演进(long term evolution，LTE)通信系统中，业务能力开放功能(service capability exposure function，SCEF)能够使得第三代合作伙伴计划(3 rdgeneration partnership project，3GPP)网络能够安全地向第三方的业务提供者提供业务能力，实现内外部应用和业务的可达和互通。第三方应用通过业务能力服务器(Services Capability Server，SCS)/应用服务器(Application Server，AS)向SCEF获取业务能力。第五代(5th Generation，5G)通信系统是基于服务化的架构，网络开放功能(network exposure function，NEF)具有类似于SCEF的功能，NEF通过服务向第SCS/AS提供3GPP网络支持的业务和能力。不管是在LTE系统还是5G系统中，在业务能力开放的架构下，均能支持SCS/AS对于用户的事件监控，可以对用户进行多种事件的监控，例如用户设备(user equipment，UE)可达性、掉线等事件。
在LTE系统中，通过监控事件配置，SCEF可能收到携带外部组标识的监控请求，外部组标识用于标识一组成员，表征对该组内的成员执行监控事件。核心网网元移动管理实体(mobility management entity，MME)/服务GPRS支持节点(serving GPRS support node，SGSN)针对组内的每一个成员，在事件监测后向SCEF发送监控事件报告。在5G通信系统中，NEF可能收到携带外部组标识的监控请求，接入和移动性管理功能(Access and Mobility Management Function，AMF)针对组内的每一个成员，在事件监测后向SCEF发送监控事件报告。
不管LTE系统中的SCEF还是5G系统中的NEF，都无法获知是否组内所有成员都完成所请求的监控事件报告，若在组内所有成员均完成请求的监控事件报告后，SCEF/NEF仍保留该组的监控事件配置，将会导致资源的浪费以及后续策略执行错误。
发明内容
本申请实施例提供一种事件监控方法及装置，用以实现业务能力开放功能或者网络开放功能在接收到组内全部成员的事件报告后删除该组的监控事件配置，从而避免资源的浪费和后续策略执行错误。
本申请实施例提供的具体技术方案如下：
第一方面，提供一种事件监控方法，该方法的执行主体为开放功能实体。具体方法的流程大致如下：接收第一消息，所述第一消息用于配置针对一个用户组的监控事件，获取所述用户组的成员信息，根据所述成员信息，确定所述用户组的所有成员的监控事件报告均已接收完毕，删除针对所述用户组的监控事件的配置。这样，开放功能实体通过获取用户组的成员信息，在接收到监控事件报告时，能够根据用户组的成员信息判断用户组内的所有成员的监控事件报告均已接收完毕，从而能够进一步删除该用户组的监控事件的配置，避免资源的浪费，以及有助于保证后续策略的正确执行。
可选的，所述开放功能实体为业务能力开放功能SCEF实体，或者，所述开放功能实体为网络开放功能NEF实体。这样，本申请实施例提供的方法能够适应LTE系统和5G系统中。
在一个可能的设计中，用户组的成员信息可以是用户组内包含的成员数量，成员数量可以用N来表示；用户组的成员信息也可以是用户组内每一个成员的标识，即，用户组的成员信息为N个标识。这样，开放功能实体可以根据用户组内包含的成员数量，或根据成员的标识，判断已接收了多少个成员的监控事件报告，从而判断是否用户组内所有的成员的监控事件报告均已接收完毕。
在一个可能的设计中，可以但不限于以下两种方式来获取用户组的成员信息。方式一：第一消息中携带用户组的成员信息，从第一消息中获得用户组的成员信息。方式二：接收用户数据管理实体发送的用户组的成员信息，即，从用户数据管理实体获取用户组的成员信息。这样，使得用户组的成员信息携带在已有的信令中，减少新增信令的开销。
在一个可能的设计中，该第一消息还可能携带最大报告次数，该最大报告次数用于指示允许针对一个成员上报监控事件报告的最大次数，或者，该最大报告次数用于指示允许针对一个成员的一个监控事件上报监控事件报告的最大次数，或者，该最大报告次数用于指示允许针对一个成员的多个监控事件上报监控事件报告的最大总次数。该最大报告次数是针对该用户组内的每一个成员设置的，适用于该用户组内的每一个成员。
可选的，该第一消息还可能携带监控持续时间，该监控持续时间用于指示监控请求过期的绝对时间。该监控持续时间是针对该用户组内的每一个成员设置的，适用于该用户组内的每一个成员。
确定所述用户组的所有成员的监控事件报告均已接收完毕，可能包含以下几种情况：
在一个可能的设计中，若所述第一消息用于配置对所述用户组进行一次监控请求，则所述开放功能实体在接收到N个所述成员的监控事件报告时，就可以确定所述用户组的所有成员的监控事件报告均已接收完毕。
可选的，若所述第一消息中不包括最大报告次数、且不包括持续时间，则所述开放功能实体确定所述第一消息用于配置对所述用户组进行一次监控请求；或者，若所述第一消息中包括第一最大报告次数、且所述第一最大报告次数为1，则所述开放功能实体确定所述第一消息用于配置对所述用户组进行一次监控请求。
在一个可能的设计中，若所述第一消息用于配置针对所述用户组的监控事件的数量为多个，则所述开放功能实体在针对N个所述成员的每一个成员，均接收到所述多个监控事 件中的每一个监控事件的监控事件报告时，确定所述成员组内所有用户的监控事件报告均已接收完毕。
在一个可能的设计中，若所述第一消息中包括第二最大报告次数，则所述开放功能实体针对N个所述成员的每一个成员，接收到的监控事件报告的次数均达到所述第二最大报告次数时，确定所述成员组的所有成员的监控事件报告均已接收完毕。
可选的，若所述第一消息用于配置针对所述用户组的监控事件的数量为多个，则所述开放功能实体在针对N个所述成员的每一个成员，接收到所述多个监控事件中的每一个监控事件的监控事件报告次数均达到第二最大报告次数时，确定所述用户组的所有成员的监控事件报告均已接收完毕。
上述几种方法均能够确定用户组内的成员的监控事件报告接收完毕，从而进一步发起删除针对该用户组的监控事件的配置。在一个可能的设计中，若所述用户组的成员信息包括所述N个标识，则所述开放功能实体每接收到一个监控事件报告，判断所述一个监控事件报告是否为所述成员的监控事件报告，获得判断结果，所述判断结果用于确定所述用户组内所有成员的监控事件报告是否均已接收完毕。这样，能够有助于保证确定用户组内的成员的监控事件报告是否接收完毕的准确性。
在一个可能的设计中，所述开放功能实体删除针对所述用户组的监控事件的配置，包括以下至少一项操作：所述开放功能实体删除本地存储的针对所述用户组的监控事件的配置；所述开放功能实体向用户数据管理实体发送第二消息，所述第二消息用于指示所述用户数据管理实体删除针对所述用户组的监控事件的配置；所述开放功能实体向所述第三方应用实体发送第三消息，所述第三消息用于指示所述第三方应用实体删除针对所述用户组的监控事件的配置。可选的，所述用户数据管理实体为归属用户服务器HSS实体，或者，所述统一数据管理UDM实体。
第二方面，提供一种事件监控方法，该方法的执行主体为开放功能实体。具体方法的流程大致如下：接收第一消息，所述第一消息用于配置针对一个用户组的监控事件，获取所述用户组的成员信息，根据所述成员信息，确定所述用户组的所有成员的监控事件报告是否完成。可选的，在确定完成的情况下，删除针对所述用户组的监控事件的配置或停止向第三方应用发送所述监控事件报告。这样，开放功能实体通过获取用户组的成员信息，在接收到监控事件报告时，能够根据用户组的成员信息判断用户组内的所有成员的监控事件报告均已接收完毕，从而能够进一步删除该用户组的监控事件的配置或停止向第三方应用发送所述监控事件报告，避免资源的浪费，以及有助于保证后续策略的正确执行。
可选的，所述开放功能实体为业务能力开放功能SCEF实体，或者，所述开放功能实体为网络开放功能NEF实体。这样，本申请实施例提供的方法能够适应LTE系统和5G系统中。
在一个可能的设计中，用户组的成员信息可以是用户组内包含的成员数量，成员数量可以用N来表示；用户组的成员信息也可以是用户组内每一个成员的标识，即，用户组的成员信息为N个标识。这样，开放功能实体可以根据用户组内包含的成员数量，或根据成员的标识，判断已接收了多少个成员的监控事件报告，从而判断是否用户组内所有的成员的监控事件报告均已接收完毕。
在一个可能的设计中，可以但不限于以下两种方式来获取用户组的成员信息。方式一：第一消息中携带用户组的成员信息，从第一消息中获得用户组的成员信息。方式二：接收用户数据管理实体发送的用户组的成员信息，即，从用户数据管理实体获取用户组的成员信息。这样，使得用户组的成员信息携带在已有的信令中，减少新增信令的开销。
在一个可能的设计中，该第一消息还可能携带最大报告次数，该最大报告次数用于指示允许针对一个成员上报监控事件报告的最大次数，或者，该最大报告次数用于指示允许针对一个成员的一个监控事件上报监控事件报告的最大次数，或者，该最大报告次数用于指示允许针对一个成员的多个监控事件上报监控事件报告的最大总次数。该最大报告次数是针对该用户组内的每一个成员设置的，适用于该用户组内的每一个成员。
可选的，该第一消息还可能携带监控持续时间，该监控持续时间用于指示监控请求过期的绝对时间。该监控持续时间是针对该用户组内的每一个成员设置的，适用于该用户组内的每一个成员。
确定所述用户组的所有成员的监控事件报告均已完成，可能包含以下几种情况：
在一个可能的设计中，若所述第一消息用于配置对所述用户组进行一次监控请求，则所述开放功能实体在接收到N个所述成员的监控事件报告时，就可以确定所述用户组的所有成员的监控事件报告已完成。
可选的，若所述第一消息中不包括最大报告次数、且不包括持续时间，则所述开放功能实体确定所述第一消息用于配置对所述用户组进行一次监控请求；或者，若所述第一消息中包括第一最大报告次数、且所述第一最大报告次数为1，则所述开放功能实体确定所述第一消息用于配置对所述用户组进行一次监控请求。
在一个可能的设计中，若所述第一消息用于配置对所述用户组进行一次监控请求且所述第一消息用于配置针对所述用户组的监控事件的数量为多个，则所述开放功能实体在针对N个所述成员的每一个成员，均接收到所述多个监控事件中的每一个监控事件的监控事件报告时，确定所述成员组内所有用户的监控事件报告已完成。
在一个可能的设计中，若所述第一消息中包括第二最大报告次数，则所述开放功能实体针对N个所述成员的每一个成员，接收到的监控事件报告的次数均达到所述第二最大报告次数时，确定所述成员组的所有成员的监控事件报告均已接收完毕。
在一个可能的设计中，若所述第一消息中包括第二最大报告次数且所述第一消息用于配置针对所述用户组的监控事件的数量为多个，则所述开放功能实体在针对N个所述成员的每一个成员，接收到所述多个监控事件中的每一个监控事件的监控事件报告次数均达到第二最大报告次数时，确定所述用户组的所有成员的监控事件报告已完成。
上述几种方法均能够确定用户组内的成员的监控事件报告已完成，从而进一步发起删除针对该用户组的监控事件的配置或停止向第三方应用发送所述监控事件报告。
在一个可能的设计中，若所述用户组的成员信息包括所述N个标识，则所述开放功能实体每接收到一个监控事件报告，判断所述一个监控事件报告是否为所述成员的监控事件报告，获得判断结果，所述判断结果用于确定所述用户组内所有成员的监控事件报告是否完成。这样，能够有助于保证确定用户组内的成员的监控事件报告是否完成的准确性。
在一个可能的设计中，所述开放功能实体删除针对所述用户组的监控事件的配置，包 括以下至少一项操作：所述开放功能实体删除本地存储的针对所述用户组的监控事件的配置；所述开放功能实体向所述第三方应用实体发送第二消息，所述第二消息用于指示所述第三方应用实体删除针对所述用户组的监控事件的配置。
在一个可能的设计中，所述开放功能实体删除针对所述用户组的监控事件的配置，包括：所述开放功能实体向用户数据管理实体发送第三消息，所述第三消息用于指示所述用户数据管理实体删除针对所述用户组的监控事件的配置；或者，所述开放功能实体向用户数据管理实体发送第四消息，所述第四消息用于指示所述用户数据管理实体删除针对所述用户组的一个或多个成员的监控事件的配置。
在一个可能的设计中，所述开放功能实体确定所述一个或多个成员的监控事件报告已完成，则所述开放功能实体向所述用户数据管理实体发送所述第四消息。
可选的，所述用户数据管理实体为归属用户服务器HSS实体，或者，所述统一数据管理UDM实体。
上述描述中，用户组内的成员的监控事件报告已完成即为用户组的监控事件报已完成；确定用户组的所有成员的监控事件报告均已完成，即确定用户组的监控事件报告已完成。
第三方面，提供一种事件监控装置，该装置具有实现上述第一方面、第二方面、第一方面的任一种可能的设计和第二方面的任一种可能的设计的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，该装置可以是芯片或者集成电路。
在一个可能的设计中，该装置包括收发器和处理器，该收发器用于该装置与其他功能实体或网元之间进行通信，处理器用于执行一组程序，当程序被执行时，所述装置可以执行上述第一方面和第一方面的任一种可能的设计中所述的方法。
在一个可能的设计中，该装置还包括存储器，该存储器存储有所述处理器执行的所述程序。
在一个可能的设计中，该装置为业务能力开放功能SCEF实体，或者，为网络开放功能NEF实体。
第四方面，提供一种芯片，该芯片与存储器相连或者该芯片包括存储器，用于读取并执行所述存储器中存储的软件程序，以实现如上述第一方面、第二方面、第一方面的任一种可能的设计和第二方面的任一种可能的设计中所述的方法。
第五方面，提供一种事件监控方法，该方法的执行主体为用户数据管理实体，该方法具体为：接收第一请求消息，所述第一请求消息用于配置针对一个用户组的监控事件；向开放功能实体发送第一应答消息，所述第一应答消息中携带用户组的成员信息。这样，通过向开放功能实体发送用户组的成员信息，使得开放功能实体能够在接收到监控事件报告时，根据用户组的成员信息判断用户组内的所有成员的监控事件报告均已接收完毕，从而能够进一步删除该用户组的监控事件的配置或停止向第三方应用发送所述监控事件报告，避免资源的浪费，以及有助于保证后续策略的正确执行。
在一个可能的设计中，用户组的成员信息可以是用户组内包含的成员数量，成员数量可以用N来表示；用户组的成员信息也可以是用户组内每一个成员的标识，即，用户组的 成员信息为N个标识。这样，开放功能实体可以根据用户组内包含的成员数量，或根据成员的标识，判断已接收了多少个成员的监控事件报告，从而判断是否用户组内所有的成员的监控事件报告均已接收完毕。
在一个可能的设计中，用户数据管理实体接收开放功能实体发送的第二请求消息，所述第二请求消息中携带用于指示删除针对所述用户组的监控事件的配置的信息，所述用户数据管理实体根据第二请求消息，删除针对所述用户组的监控事件的配置。
在一个可能的设计中，用户数据管理实体接收开放功能实体发送的第四请求消息，所述第二请求消息中携带用于指示所述用户数据管理实体删除针对所述用户组的一个或多个成员的监控事件的配置，所述用户数据管理实体根据第四请求消息，删除针对所述用户组的一个或多个成员的监控事件的配置。
可选的，所述用户数据管理实体为归属用户服务器HSS实体，或者，所述统一数据管理UDM实体。
第六方面，提供一种事件监控装置，该装置具有实现上述第三方面和第三方面的任一种可能的设计的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，该装置可以是芯片或者集成电路。
在一个可能的设计中，该装置包括收发器和处理器，该收发器用于该装置与其他功能实体或网元之间进行通信，处理器用于执行一组程序，当程序被执行时，所述装置可以执行上述第二方面和第二方面的任一种可能的设计中所述的方法。
在一个可能的设计中，该装置还包括存储器，该存储器存储有所述处理器执行的所述程序。
在一个可能的设计中，该装置为HSS实体或UDM实体。
第七方面，提供一种芯片，该芯片与存储器相连或者该芯片包括存储器，用于读取并执行所述存储器中存储的软件程序，以实现如上述第三方面和第三方面的任一种可能的设计中所述的方法。
第八方面，提供一种事件监控方法，该方法的执行主体为第三方应用实体，该方法具体为：向开放功能实体发送第一消息，所述第一消息用于配置针对一个用户组的监控事件，所述第一消息中携带用户组的成员信息。这样，通过向开放功能实体发送用户组的成员信息，使得开放功能实体能够在接收到监控事件报告时，根据用户组的成员信息判断用户组内的所有成员的监控事件报告均已接收完毕，从而能够进一步删除该用户组的监控事件的配置，避免资源的浪费，以及有助于保证后续策略的正确执行。
在一个可能的设计中，用户组的成员信息可以是用户组内包含的成员数量，成员数量可以用N来表示；用户组的成员信息也可以是用户组内每一个成员的标识，即，用户组的成员信息为N个标识。这样，开放功能实体可以根据用户组内包含的成员数量，或根据成员的标识，判断已接收了多少个成员的监控事件报告，从而判断是否用户组内所有的成员的监控事件报告均已接收完毕。
在一个可能的设计中，接收开放功能实体发送的第三消息，所述第三消息中携带用于指示删除针对所述用户组的监控事件的配置的信息，所述第三方应用实体根据第三消息， 删除针对所述用户组的监控事件的配置。
可选的，所述第三方应用实体为SCS实体或者AS实体。
第九方面，提供一种事件监控装置，该装置具有实现上述第四方面和第四方面的任一种可能的设计的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，该装置可以是芯片或者集成电路。
在一个可能的设计中，该装置包括收发器和处理器，该收发器用于该装置与其他功能实体或网元之间进行通信，处理器用于执行一组程序，当程序被执行时，所述装置可以执行上述第四方面和第四方面的任一种可能的设计中所述的方法。
在一个可能的设计中，该装置还包括存储器，该存储器存储有所述处理器执行的所述程序。
在一个可能的设计中，该装置为SCS实体或AS实体。
第十方面，提供一种芯片，该芯片与存储器相连或者该芯片包括存储器，用于读取并执行所述存储器中存储的软件程序，以实现如上述第四方面和第四方面的任一种可能的设计中所述的方法。
第十一方面，提供一种计算机存储介质，存储有计算机程序，该计算机程序包括用于执行上述各方面和各方面的任一可能的设计中方法的指令。
第十二方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面和各方面的任一可能的设计中所述的方法。
附图说明
图1为本申请实施例中LTE系统中业务能力开放的架构图；
图2为本申请实施例中5G系统中业务能力开放的架构图；
图3为本申请实施例中事件监控方法的流程示意图；
图4为本申请实施例中应用场景一下事件监控的流程示意图之一；
图5为本申请实施例中应用场景一下事件监控的流程示意图之二；
图6为本申请实施例中应用场景二下事件监控的流程示意图之一；
图7为本申请实施例中应用场景二下事件监控的流程示意图之二；
图8为本申请实施例中事件监控装置结构示意图之一；
图9为本申请实施例中事件监控装置结构示意图之二。
具体实施方式
本申请实施例提供一种事件监控方法及装置，用于实现：在基于组的事件监控中，LTE系统中的SCEF或者5G系统中NEF在组内全部成员的事件报告均已接收完毕时，能够及时删除该组的监控事件的配置，从而节省资源以及有助于保证后续策略的正确执行。
以下介绍一下本申请实施例提供的方法可以适用的通信系统架构。
如图1所示，为LTE系统中业务能力开放(service capability exposure，SCE)的架构 图，包括：SCEF101、SCS/AS102、家乡用户服务器(home subscriber server，HSS)103、MME104和SGSN105。在LTE系统中，SCEF101为业务能力开放架构的核心网元，SCEF101用于保证网络安全地向第三方的业务提供者提供业务能力，以实现内外部应用和业务的可达和互通。第三方应用通过SCS/AS102向SCEF101获取业务能力。HSS103为归属用户签约服务器，用于保存用户的签约信息。移动性管理网元包括MME104和SGSN105，用于负责对终端进行移动性管理。SCS/AS102通过T8的API接口调用SCEF101提供的业务能力。
如图2所示，为5G系统中SCE)的架构图，包括：NEF201、SCS/AS202、UDM203和AMF204。在5G系统中，NEF201的功能类似于LTE系统中SCEF101的功能，NEF201通过Nnef服务向SCS/AS202开发3GPP网络支持的业务和能力。UDM203的功能类似于LTE系统中HSS103的功能，UDM203通过Nudm服务向NEF201提供支持的业务能力，移动性管理网元包括AMF204，AMF204的功能类似于LTE系统中MME104的功能，AMF204通过Namf服务向NEF201提供支持的业务和能力。
需要说明的是，图1和图2提供的通信系统架构为示例性的，本申请实施例提供的方法不限于这两种通信系统中，还可以适用于更多的通信系统。
以下对本申请实施例中涉及到的部分用语进行解释说明，以方便本领域技术人员的理解。
1)监控事件
本申请实施例中，基于图1或图2所示的业务能力开放的架构，SCS/AS可以对用户进行一个或多个事件的监控。事件例如可以是，UE可达性、连接丢失、位置等。
2)用户组
用户组或者称为组，一个用户组包括一个或多个成员，成员即用户，也就是说，一个用户组包括一个或多个用户。本申请实施例中，监控事件的配置可以是基于组的，一个组内的所有成员具有相同的外部组标识。
3)用户组的成员信息
关于一个用户组内包含的成员的相关信息。例如，成员信息可以是：用户组内包含的成员数目，本申请中该成员数目用N来表示，N为正整数；成员信息还可以是用户组内包含的每一个成员的标识，该标识是用于区分不同成员的，也可以称为成员标识或用户标识，一个组内的成员的外部组标识用于区分不同用户组的，成员标识或用户标识是用于区分不同的用户(或成员)的。
4)开放功能实体
是指具有能够实现业务开放功能的实体，具有相同或类似于上述SCEF101或NEF201功能的实体。开放功能实体可以是指SCEF101，也可以是指NEF201。
5)第三方应用实体
具有相同或类似于上述SCS/AS102或SCS/AS202功能的实体。第三方应用实体可以是指SCS/AS102，也可以是指SCS/AS202。
6)移动性管理网元
具有相同或类似于上述MME104和SGSN105功能的实体，或AMF204功能的实体。移动性管理网元可以是指MME104和SGSN105，也可以是指AMF204。
7)用户数据管理实体
具有相同或类似于上述HSS103或UDM203功能的实体。用户数据管理实体可以是指HSS103，也可以是指UDM203。
8)监控事件报告
移动性管理网元上报的关于用户组内的成员的监控事件的相关内容。监控事件报告中可能携带一个或多个监控事件的相关内容。开放功能实体通过监控事件的标识来区分不同监控事件的监控事件报告，以及通过成员的标识来区分不同的成员的监控事件报告。
9)和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。本申请中所涉及的多个，是指两个或两个以上。“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。字符“/”一般表示前后关联对象是一种“或”的关系。
下面将结合附图，对本申请实施例提供的事件监控方法进行详细描述。
如图3所示，本申请实施例提供的事件监控方法的具体流程如下所述，该方法的执行主体为开放功能实体。
S301、接收第一消息。
该第一消息可以是监控请求。该第一消息用于配置针对一个用户组的监控事件，或者说，该第一消息用于配置针对一个用户组的监控请求。其中，该用户组包括一个或多个成员，针对一个用户组的监控事件或监控请求，是指针对一个用户组内的每一个成员的监控事件或监控请求。该第一消息用于配置针对一个用户组的监控事件的数量可以是一个或多个。该一个或多个监控事件是针对该用户组内的每一个成员的。该第一消息中可能携带该用户组的外部组标识(external group ID)，该外部组标识也是针对该用户组内的每一个成员的，用于区分不同的用户组。监控请求也可称为事件订阅，该第一消息用于订阅针对一个用户组的监控事件。
该第一消息还可能携带最大报告次数，该最大报告次数用于指示针对一个成员上报监控事件报告的最大次数，或者，该最大报告次数用于指示针对一个成员的一个监控事件上报监控事件报告的最大次数，或者，该最大报告次数用于指示针对一个成员的多个监控事件上报监控事件报告的最大总次数。该最大报告次数是针对该用户组内的每一个成员设置的，适用于该用户组内的每一个成员。其中，最大报告次数为正整数。
该第一消息还可能携带监控持续时间，该监控持续时间用于指示监控请求过期的绝对时间。该监控持续时间是针对该用户组内的每一个成员设置的，适用于该用户组内的每一个成员。
实际应用中，第一消息可以用于配置针对一个用户组的一次监控请求，一次监控请求是指针对用户组内的每一个成员上报一次监控事件报告即可，其中，若监控事件的数量为一个，则针对这一个监控事件上报一次监控事件报告，若监控事件的数量为多个，则针对这一个监控请求中的多个监控事件的任一个监控事件报告一次或针对多个监控事件中的每一个监控事件均上报一次监控事件报告。
具体的，第一消息是用于配置针对一个用户组的一次监控请求的，有以下几种情况：(1) 第一消息中包含最大报告次数、且最大报告次数为1；(2)第一消息中不包含最大报告次数，并且也不包含监控持续时间。
S302、获取用户组的成员信息。
可以但不限于以下两种方式来获取用户组的成员信息。方式一：第一消息中携带用户组的成员信息，从第一消息中获得用户组的成员信息。方式二：接收用户数据管理实体发送的用户组的成员信息，即，从用户数据管理实体获取用户组的成员信息。这里的用户数据管理实体可以为HSS实体或者UDM实体。
S303、根据用户组的成员信息，确定用户组的所有成员的监控事件报告均已接收完毕。
具体的，开放功能实体通过一次或多次接收监控事件报告，每接收到监控事件报告时，将接收到的监控事件报告存储在本地，并根据已接收到的事件报告和用户组的成员信息，判断是否所有成员的监控事件报告均已接收完毕(即判断是否所有成员的监控事件报告已完成)。其中，移动性管理网元在每一次上报监控事件报告时，还上报监控请求的标识(SCEF参考标识或NEF事件通知标识)、监控事件的标识以及成员的标识，监控请求的标识、监控事件的标识和成员的标识携带在监控事件报告中或与监控事件报告一起携带在某类消息中，如监控应答消息。开放功能实体根据监控请求的标识、监控事件的标识和成员的标识，确定监控事件报告所属的用户组、监控事件以及成员。
用户组的成员信息可以是用户组内包含的成员数量，成员数量可以用N来表示；用户组的成员信息也可以是用户组内每一个成员的标识，即，用户组的成员信息为N个标识。开放功能实体每接收到监控事件报告，能够确定该监控事件报告所属的用户组、监控事件以及所属的成员。基于此，确定用户组的所有成员的监控事件报告均已接收完毕，可以有以下几种情况。
第一种情况、
第一消息用于配置对用户组进行一次监控请求。这种情况下，针对一个成员的一个监控事件，只需要接收一次监控事件报告即可。
若第一消息中包含一个监控事件，即第一消息用于配置针对用户组的监控事件的数量为一个，则：
鉴于用户组的成员信息为用户组的数目N，开放功能实体在接收到N个监控事件报告时，就可以确定用户组的所有成员的监控事件报告均已接收完毕，其中，N个监控事件报告所属的成员互不相同，即，N个监控事件报告为N个不同成员的监控事件报告。由于开放功能实体能够确定监控事件报告所属的成员，所以开放功能实体能够确定已接收到多少个不同成员的监控事件报告。
鉴于用户组的成员信息为N个标识，开放功能实体将接收到的监控事件报告关联的成员的标识与该N个标识对比，若该N个标识的成员的监控事件报告均已接收到，则可以确定用户组的所有成员的监控事件报告均已接收完毕(即确定用户组的所有成员的监控事件报告已完成)。
若第一消息中包含多个监控事件，即第一消息用于配置针对用户组的监控事件的数量为多个，例如为M个，则：
鉴于用户组的成员信息为用户组的数目N，开放功能实体也可以在接收到N个监控事 件事件报告时，就可以确定用户组的所有成员的监控事件报告均已接收完毕。若第一消息中包含多个监控事件，即第一消息用于配置针对用户组的监控事件的数量为多个，例如为M个，那么在针对N个成员的每一个成员，都接收到监控事件报告，或针对N个成员的每一个成员的M个监控事件中的每一个监控事件都接收到监控事件报告，则确定用户组的所有成员的监控事件报告均已接收完毕(即确定用户组的所有成员的监控事件报告已完成)。
鉴于用户组的成员信息为N个标识，开放功能实体也可以在该N个标识的成员的监控事件报告均已接收到时，就可以确定用户组的所有成员的监控事件报告均已接收完毕。或者，开放功能实体将接收到的监控事件报告关联的成员的标识与该N个标识对比，将接收到的监控事件报告关联的监控事件的标识与M个监控事件的标识对比，若针对该N个标识的成员中每一个成员，M个监控事件的每一个监控事件的监控事件报告均已接收到时，确定用户组的所有成员的监控事件报告均已接收完毕(即确定用户组的所有成员的监控事件报告已完成)。
第二种情况、
第一消息携带最大报告次数，且最大报告次数大于1。这种情况下，用户组内所有成员的监控事件报告均达到最大报告次数，才能确定用户组的所有成员的监控事件报告均已接收完毕(即确定用户组的所有成员的监控事件报告已完成)。
开放功能实体根据用户组的数目N或者N个标识，来确定已接收到多少个不同成员的监控事件报告。在针对N个成员的每一个成员，接收到的监控事件报告的次数均达到最大报告次数时，确定成员组的所有成员的监控事件报告均已接收完毕。若第一消息中包含多个监控事件，即第一消息用于配置针对用户组的监控事件的数量为多个，例如为M个，那么在针对N个成员的每一个成员，接收到的事件报告的次数达到最大报告次数，或针对N个成员的每一个成员的M个监控事件中的每一个监控事件的监控事件报告的次数达到最大报告次数，确定用户组的所有成员的监控事件报告均已接收完毕(即确定用户组的所有成员的监控事件报告已完成)。
S304、删除用户组的监控事件的配置。
具体的，开放功能实体删除本地的针对用户组的监控事件配置。可选的，开放功能实体还可以向第三方应用实体发送消息，用于指示第三方应用实体删除针对该用户组的监控事件的配置。可选的，开放功能实体还可以向用户数据管理实体发送消息，用于指示用户数据管理实体删除针对该用户组的监控事件的配置或指示用户数据管理实体删除针对该用户组的一个或多个成员的监控事件的配置。
在一个可能的实现方式中，若用户组的成员信息为上述的N个标识，则开放功能实体还可以在每接收到一个监控事件报告时，判断接收到的监控事件报告是否为用户组的成员的监控事件报告。具体的，判断接收到的监控事件报告关联的成员标识是否是上述的N个标识中的，若是，则确定接收到的监控事件报告为用户组的成员的监控事件报告，否则，确定接收到的监控事件报告不是该用户组的成员的监控事件报告。判断结果用于进一步确定该用户组内所有成员的监控事件报告是否均已接收完毕(即确定用户组的所有成员的监控事件报告已完成)。
综上所述，本申请实施例提供的事件监控方法，开放功能实体通过获取用户组的成员 信息，在接收到监控事件报告时，能够根据用户组的成员信息判断用户组内的所有成员的监控事件报告均已接收完毕，从而能够进一步删除该用户组的监控事件的配置或停止向第三方应用发送监控事件报告，避免资源的浪费，以及有助于保证后续策略的正确执行。
下面基于上述实施例提供的方法，结合具体的应用场景，对本申请的事件监控方法做进一步详细的说明。
应用场景一：LTE系统。开放功能实体为SCEF，第三方应用实体为SCS/AS，移动性管理网元为MME和SGSN，用户数据管理实体为HSS。
如图4所示，在应用场景一下事件监控的流程具体如下所述。
S401、SCS/AS向SCEF发送基于用户组配置的第一监控请求消息，SCEF接收SCS/AS发送的第一监控请求消息。
该第一监控请求消息为上述实施例所述的第一消息，具有第一消息的属性和功能。
该第一监控请求消息中携带用户组的成员信息，还可以但不限于携带以下至少一种信息：SCS/AS标识、T8目的地址、监控类型、外部组标识、T8长期交互参考标识(T8Long Term Transaction Reference ID，TLTRI)、最大报告次数和/或监控持续时间。最大报告次数和/或监控持续时间应用于用户组内的每一个成员。若该第一监控请求消息中既不携带最大报告次数也不携带监控持续时间，或者该第一监控请求消息中携带最大报告次数、且最大报告次数的值为1，均表示第一监控请求消息为一次监控请求。
S402、SCEF保存接收到的监控请求消息中携带的各种信息，SCEF根据本地策略对配置的监控请求进行授权。授权成功后，SCEF分配SCEF参考标识(SCEF reference ID)，保存SCEF Reference ID和TLTRI的对应关系。SCEF reference ID用于在核心网内标识这个监控请求，进而可以确定用户组。
S403、SCEF向HSS发送第二监控请求消息，HSS接收SCEF发送的第二监控请求消息。
第二监控请求消息中携带S401中的第一监控请求消息中携带的一种或多种信息，当然不需要携带用户组的成员信息，例如可以携带外部组标识、SCEF标识，SCEF参考标识、监控类型。
S404、HSS检查第二监控请求消息。检查通过后，HSS保存接收到的第二监控请求消息中携带的信息。HSS确定外部组标识对应的组内成员。
S405、HSS向SCEF返回第一监控应答消息，SCEF接收HSS发送的第一监控应答消息。
第一监控应答消息用于确认第二监控请求消息，第一监控应答消息可以携带用户组的成员信息。第一监控应答消息中还可以携带SCEF参考标识和接收指示。
S406、SCEF向SCS/AS返回第二监控应答消息，SCS/AS接收SCEF返回的第二监控应答消息。
第二监控应答消息中携带TLTRI和接收指示。
针对用户组内的每一个成员，执行S407～S409。
S407、HSS向服务这个用户组的所有MME/SGSN发送插入用户签约数据请求。
插入用户签约数据请求中携带监控类型，SCEF标识、SCEF参考标识、最大报告次数 和/或监控持续时间、外部标识或移动用户综合业务数字网/公共交换电话网络号码(Mobile Subscriber International ISDN/PSTN number,MSISDN)。
S408、MME/SGSN保存接收到的插入用户签约数据请求中携带的参数，进行相应的处理。
例如，MME/SGSN根据最大报告次数设置剩余报告次数。对于一次请求监控，MME/SGSN也可以将剩余报告次数为1。
S409、MME/SGSN向HHS发送插入用户签约数据应答消息，HHS接收MME/SGSN发送的插入用户签约数据应答消息。
插入用户签约数据应答消息中携带接收的指示。若MME/SGSN已有本次监控请求的监控事件，则MME/SGSN在插入用户签约数据应答消息中携带监控事件报告。进一步的，若在S407中既不携带最大报告次数也不监控持续时间，或剩余报告次数为1，则MME/SGSN在本地删除针对该用户组的监控事件配置；若在S407中携带最大报告次数取值大于1，则MME/SGSN将剩余报告次数减1。
S410、若在S409中插入用户签约数据应答消息携带了监控事件报告，则HSS向SCEF发送第一监控指示消息，SCEF接收HSS发送的第一监控指示消息。
第一监控指示消息中携带SCEF Reference ID、监控事件报告和监控事件报告对应的外部标识或MSISDN。实际应用中，HSS可能会汇聚多个来自MME/SGSN的监控事件报告，并在一条监控指示消息中发送给SCEF。即在监控指示消息中携带SCEF Reference ID，和监控事件报告、外部标识或MSISDN的对应关系的列表。
S411、SCEF向SCS/AS发送第二监控指示消息，SCS/AS接收SCEF发送的第二监控指示消息。
第二监控指示消息中携带TLTRI、监控事件报告和外部组标识或MSISDN。若S410中第一监控指示消息中携带了多个监控事件报告，则第二监控指示消息中携带TLTRI，和监控事件报告、外部标识或MSISDN的对应关系的列表。
S412、SCS/AS向SCEF返回监控指示应答消息，SCEF接收SCS/AS返回的监控指示应答消息。
S413、SCEF的处理，过程包括以下几种情况。
若在S401中第一监控请求消息为一次监控请求，且S409中MME/SGSN已有本次监控请求的监控事件，MME/SGSN在插入用户签约数据应答消息中携带监控事件报告，且在S410中HSS向SCEF发送了来自MME/SGSN的监控事件报告，则SCEF先根据SCEF Reference ID确定事件报告对应的用户组，再根据S401或S405中接收到的用户组的成员信息(例如N个标识，或者成员数目N)，确定S410接收到的监控事件报告是否包含了所有成员的监控事件报告。若已包含了所有成员的监控事件报告，则确定用户组内所有成员的监控事件报告均已接收完毕(即确定用户组内所有成员的监控事件报告已完成)，发起删除该用户组的监控事件的配置或停止向SCS/AS发送监控事件报告。其中，若第一监控请求消息中包含多个监控事件，即第一监控请求消息用于配置针对用户组的监控事件的数量为多个，例如为M个，那么根据S410接收到的监控事件报告，在针对N个成员的每一个成员，都接收到监控事件报告，或针对N个成员的每一个成员的M个监控事件中的每一个监控事 件都接收到监控事件报告，则确定用户组的所有成员的监控事件报告均已接收完毕(即确定用户组内所有成员的监控事件报告已完成)。用户组内所有成员的监控事件报告已完成即为用户组的监控事件报已完成。
具体的，根据用户组的成员信息，确定用户组内所有成员的监控事件报告均已接收完毕的过程如下。若成员信息为成员数目，则SCEF根据S410接收到的监控事件报告关联的不同的成员的标识(MSISDN或外部标识)的数目，来判断已接收到多少个成员的监控事件报告，在已接收到监控事件报告的成员数目达到成员信息的成员数目时，确定用户组内所有成员的监控事件报告均已接收完毕。若成员信息为各个成员的标识，则SCEF根据S410接收到的监控事件报告关联的不同的成员的标识，与成员信息中的成员的标识比对，来判断已接收到多少个成员的监控事件报告，当已接收到监控事件报告的成员的标识已达到成员信息中的所有成员标识时，确定用户组内所有成员的监控事件报告均已接收完毕。可选的，SCEF接收到监控事件报告关联的成员的标识时，根据该成员的标识是否存在于成员信息的成员的标识中，来判断该标识的成员是否为该用户组内的成员，在判断为是的时候，再继续判断是否已接收到用户组内所有成员的监控事件报告。
通过S414～S418来实现删除该用户组的监控事件的配置。
S414、SCEF向HSS发送第三监控请求消息，HSS接收SCEF发送的第三监控请求消息。
该第三监控请求消息中携带SCEF Reference ID和删除指示。该删除指示用于指示HSS删除该用户组的监控事件的配置。
S415、HSS根据第三监控请求消息，删除该用户组的监控事件的配置。
S416、HSS向SCEF发送第三监控应答消息，SCEF接收HSS发送的第三监控应答消息。
第三监控应答消息用于确认第三监控请求消息。
S417、SCEF向SCS/AS发送第四监控请求消息，SCS/AS接收SCEF发送的第四监控请求消息。
第四监控请求消息中携带TLTRI和删除指示，删除指示用于指示SCS/AS删除该用户组的监控事件的配置。
S418、SCS/AS向SCEF返回第四监控应答消息，SCEF接收SCS/AS返回的第四监控应答消息。
第四监控应答消息用于确认第四监控请求消息。
需要说明的是，S414和S417没有严格的执行顺序，可以交换顺序，也可以同时执行。
若S409中MME/SGSN已有本次监控请求的监控事件，MME/SGSN在插入用户签约数据应答消息中携带监控事件报告，但是最大报告次数的值大于1；或者，S409和S410并未上报监控事件报告。这两种情况下，省略S410～S418的步骤。S401～S409为配置用户组的监控事件的流程，在S409之后，可根据图5所示的监控流程来实现后续事件监控。
此外，若SCEF因为某种原因暂时不执行S414～S418，在此期间，SCEF接收到针对步骤S401监控请求的事件报告，则SCEF停止向SCS/AS发送监控事件报告。
如图5所示，具体的的监控流程如下所述。
S501、MME/SGSN在图4的S407接收到插入用户数据请求消息后，获取该插入用户数据请求消息中携带的信息或参数，根据信息或参数对用户组内的成员进行事件监控。
需要理解的是，用户组的各个成员可能归属于相同的移动管理实体，也可能归属于不同的移动管理实体，服务用户组的移动管理实体可以是一个或多个。每一个移动管理实体针对其服务的用户组内的成员执行的流程是相同或类似的。
S502、MME/SGSN在检测到用户组内成员的事件时，向SCEF发送监控指示消息，SCEF接收MME/SGSN发送的监控指示消息。
监控指示消息中携带SCEF Reference ID、监控事件报告和外部标识或MSISDN。若S401中的第一监控请求消息为一次监控请求，则MME/SGSN还会在本地删除针对该用户组的监控事件的配置。若S401中的第一监控请求消息中包含的最大报告次数的值大于1，则MME/SGSN将记录的剩余报告次数减一。当剩余报告次数为0时，MME/SGSN在本地删除针对该用户组的监控事件的配置。
S503、SCEF向SCS/AS发送监控指示消息，SCS/AS接收SCEF发送的监控指示消息。
该监控指示消息中携带TLTRI、监控事件报告和外部标识或MSISDN。
可选的，SCEF可能会汇聚多个来自MME/SGSN的监控事件报告，并将多个监控事件报告携带与一条监控指示消息中发送给SCS/AS，这种情况下，该监控指示消息中携带TLTRI，与监控事件报告、外部标识或MSISDN的对应关系的列表。
S504、SCS/AS向SCEF返回监控指示应答消息，SCEF接收SCS/AS返回的监控指示应答消息。
该监控指示应答消息用于确认S503中接收的监控指示消息。
S505、SCEF的处理，可以包括两种类型的处理。
第一种类型的处理，过程包括以下几种情况。
SCEF根据S502中接收的SCEF Reference ID确定事件报告对应的用户组，再根据S401或S405中接收到的用户组的成员信息，确定是否已接收到了所有成员的监控事件报告。若已接收到了所有成员的监控事件报告，则确定用户组的所有成员的监控事件报告均已接收完毕(即确定用户组的所有成员的监控事件报告已完成)，发起删除该用户组的监控事件的配置或停止向SCS/AS发送监控事件报告。用户组内所有成员的监控事件报告已完成即为用户组的监控事件报已完成。
具体的，确定用户组的所有成员的监控事件报告均已接收完毕的过程如下。
若在S401中第一监控请求消息为一次监控请求，则根据用户组的成员信息(例如N个标识或成员数目N)，确定用户组的所有成员的监控事件报告均已接收完毕的过程如下：若成员信息为成员数目，则SCEF根据S502接收到的监控事件报告关联的不同的成员的标识(MSISDN或外部标识)的数目，来判断已接收到多少个成员的监控事件报告，在已接收到监控事件报告的成员数目达到成员信息的成员数目时，确定用户组的所有成员的监控事件报告均已接收完毕。若成员信息为各个成员的标识，则SCEF根据S502接收到的监控事件报告关联的不同的成员的标识，与成员信息中的成员的标识比对，来判断已接收到多少个成员的监控事件报告，当已接收到监控事件报告的成员的标识已达到成员信息中的所有成员标识时，确定用户组的所有成员的监控事件报告均已接收完毕。可选的，SCEF接收到 监控事件报告关联的成员的标识时，根据该成员的标识是否存在于成员信息的成员的标识中，来判断该标识的成员是否为该用户组内的成员，在判断为是的时候，再继续判断是否已接收到用户组的所有成员的监控事件报告。其中，若第一监控请求消息中包含多个监控事件，即第一监控请求消息用于配置针对用户组的监控事件的数量为多个，例如为M个，那么根据S502接收到的监控事件报告，在针对N个成员的每一个成员，都接收到监控事件报告，或针对N个成员的每一个成员的M个监控事件中的每一个监控事件都接收到监控事件报告，则确定用户组的所有成员的监控事件报告均已接收完毕。
若最大报告次数的值大于1，则SCEF根据用户组的成员信息(例如N个标识或成员数目N)，确定用户组的所有成员的监控事件报告均已接收完毕的过程如下。若成员信息为成员数目，则SCEF根据S502接收到的监控事件报告关联的不同的成员的标识(MSISDN或外部标识)的数目，来判断已接收到多少个成员的监控事件报告，并判断每一个成员的累计报告次数是否达到最大报告次数。在已接收到监控事件报告的成员数目达到成员信息的成员数目，并且每一个成员的累计报告次数均达到最大报告次数时，确定用户组内所有成员的监控事件报告均已接收完毕。若成员信息为各个成员的标识，则SCEF根据S502接收到的监控事件报告关联的不同的成员的标识，与成员信息中的成员的标识比对，来判断已接收到多少个成员的监控事件报告，并判断每一个成员的累计报告次数是否达到最大报告次数。当已接收到监控事件报告的成员的标识已达到成员信息中的所有成员标识，并且每一个成员的累计报告次数均达到最大报告次数时，确定用户组内所有成员的监控事件报告均已接收完毕。可选的，SCEF接收到监控事件报告关联的成员的标识时，根据该成员的标识是否存在于成员信息的成员的标识中，来判断该标识的成员是否为该用户组内的成员，在判断为是的时候，再继续判断是否已接收到用户组内所有成员的监控事件报告。
若第一消息中包含多个监控事件，即第一消息用于配置针对用户组的监控事件的数量为多个，例如为M个，那么在针对N个成员的每一个成员，接收到的事件报告的次数达到最大报告次数，或针对N个成员的每一个成员的M个监控事件中的每一个监控事件的监控事件报告的次数达到最大报告次数，确定用户组的所有成员的监控事件报告均已接收完毕。
通过S506～S510来实现删除该用户组的监控事件的配置。(在第一种类型的处理中，S506～S510只需执行一次。)
S506、SCEF向HSS发送监控请求消息，HSS接收SCEF发送的监控请求消息。
该监控请求消息中携带SCEF Reference ID和删除指示。该删除指示用于指示HSS删除该用户组的监控事件的配置。
S507、HSS根据监控请求消息，删除该用户组的监控事件的配置。
S508、HSS向SCEF发送监控应答消息，SCEF接收HSS发送的监控应答消息。
监控应答消息用于确认接收到S506的监控请求消息。
S509、SCEF向SCS/AS发送监控请求消息，SCS/AS接收SCEF发送的监控请求消息。
监控请求消息中携带TLTRI和删除指示，删除指示用于指示SCS/AS删除该用户组的监控事件的配置。
S510、SCS/AS向SCEF返回监控应答消息，SCEF接收SCS/AS返回的监控应答消息。
监控应答消息用于确认S509的监控请求消息。
需要说明的是，S506和S509没有严格的执行顺序，可以交换顺序，也可以同时执行。S503和S505没有严格的执行顺序，可以交换顺序，也可以同时执行。
第二种类型的处理过程包括以下几种情况。
SCEF根据S502中接收的SCEF Reference ID确定事件报告对应的用户组，若确定事件报告对应的任一个成员的监控事件报告是否接收完毕(即监控事件报告是否完成)，若已接收完毕，则请求HSS删除该成员的监控事件的配置。SCEF进一步根据S401或S405中接收到的用户组的成员信息，确定用户组的所有成员的监控事件报告是否接收完毕(即监控事件报告是否完成)。若已接收完毕，则执行：删除本地该用户组的监控事件的配置并请求SCS/AS删除该用户组的监控事件的配置或停止向SCS/AS发送事件报告，可选的，还可以向HSS发送消息，该消息用于指示HSS删除针对用户组的监控事件的配置，需要说明的是，由于每确定一个成员的监控事件报告接收完毕，SCEF向HSS请求删除该成员的监控事件的配置，因此这里SCEF向HSS发送指示删除针对用户组的监控事件的配置的消息为可选的步骤。或者，若SCEF进一步确定已向HSS发送了用户组的所有成员的监控事件配置删除的请求消息，则删除本地该用户组的监控事件的配置并请求SCS/AS删除该用户组的监控事件的配置或停止向SCS/AS发送事件报告。用户组内所有成员的监控事件报告已完成即为用户组的监控事件报已完成。
具体的，确定事件报告对应的成员的监控事件报告均已接收完毕的过程如下：
若在S401中第一监控请求消息为一次监控请求且在S502中接收到的一个成员的事件报告，则确定事件报告对应的成员的监控事件报告接收完成；若最大报告次数的值大于1且在S502后，接收到的一个成员的事件报告次数达到最大报告次数，则确定事件报告对应的成员的监控事件报告接收完成。可选的，SCEF接收到监控事件报告关联的成员的标识时，根据该成员的标识是否存在于成员信息的成员的标识中，来判断该标识的成员是否为该用户组内的成员，在判断为是的时候，再判断对应的成员的监控事件报告均已接收完毕。若第一消息中包含多个监控事件，即第一消息用于配置针对用户组的监控事件的数量为多个，例如为M个，那么一个成员接收到的事件报告的次数达到最大报告次数，或一个成员的M个监控事件中的每一个监控事件的监控事件报告的次数达到最大报告次数，确定事件报告对应的成员的监控事件报告均已接收完毕。
类似的，通过S506-S508请求HSS删除成员的监控事件的配置。(在第二种类型的处理中，S506～S508需执行多次，甚至是N次。)
S506、SCEF向HSS发送监控请求消息，HSS接收SCEF发送的监控请求消息。
该监控请求消息中携带SCEF Reference ID、外部组标识、成员标识(即外部标识和/或MSISDN)和删除指示。该删除指示用于指示HSS删除成员标识对应的成员的监控事件的配置。
S507、HSS根据监控请求消息，删除成员的监控事件的配置。
S508、HSS向SCEF发送监控应答消息，SCEF接收HSS发送的监控应答消息。
监控应答消息用于确认接收到S506的监控请求消息。
可选的，SCEF在S506的监控请求消息中携带多个成员标识，HSS删除这多个成员标识对应的监控事件的配置。
确定用户组的所有成员的监控事件报告均已接收完毕的过程如下。
若在S401中第一监控请求消息为一次监控请求，则根据用户组的成员信息(例如N个标识或成员数目N)，确定用户组的所有成员的监控事件报告均已接收完毕的过程如下：若成员信息为成员数目，则SCEF根据S502接收到的监控事件报告关联的不同的成员的标识(MSISDN或外部标识)的数目，来判断已接收到多少个成员的监控事件报告，在已接收到监控事件报告的成员数目达到成员信息的成员数目时，确定用户组的所有成员的监控事件报告均已接收完毕。若成员信息为各个成员的标识，则SCEF根据S502接收到的监控事件报告关联的不同的成员的标识，与成员信息中的成员的标识比对，来判断已接收到多少个成员的监控事件报告，当已接收到监控事件报告的成员的标识已达到成员信息中的所有成员标识时，确定用户组的所有成员的监控事件报告均已接收完毕。可选的，SCEF接收到监控事件报告关联的成员的标识时，根据该成员的标识是否存在于成员信息的成员的标识中，来判断该标识的成员是否为该用户组内的成员，在判断为是的时候，再继续判断是否已接收到用户组的所有成员的监控事件报告。其中，若第一监控请求消息中包含多个监控事件，即第一监控请求消息用于配置针对用户组的监控事件的数量为多个，例如为M个，那么根据S502接收到的监控事件报告，在针对N个成员的每一个成员，都接收到监控事件报告，或针对N个成员的每一个成员的M个监控事件中的每一个监控事件都接收到监控事件报告，则确定用户组的所有成员的监控事件报告均已接收完毕。
若最大报告次数的值大于1，则SCEF根据用户组的成员信息(例如N个标识或成员数目N)，确定用户组的所有成员的监控事件报告均已接收完毕的过程如下。若成员信息为成员数目，则SCEF根据S502接收到的监控事件报告关联的不同的成员的标识(MSISDN或外部标识)的数目，来判断已接收到多少个成员的监控事件报告，并判断每一个成员的累计报告次数是否达到最大报告次数。在已接收到监控事件报告的成员数目达到成员信息的成员数目，并且每一个成员的累计报告次数均达到最大报告次数时，确定用户组内所有成员的监控事件报告均已接收完毕。若成员信息为各个成员的标识，则SCEF根据S502接收到的监控事件报告关联的不同的成员的标识，与成员信息中的成员的标识比对，来判断已接收到多少个成员的监控事件报告，并判断每一个成员的累计报告次数是否达到最大报告次数。当已接收到监控事件报告的成员的标识已达到成员信息中的所有成员标识，并且每一个成员的累计报告次数均达到最大报告次数时，确定用户组内所有成员的监控事件报告均已接收完毕。可选的，SCEF接收到监控事件报告关联的成员的标识时，根据该成员的标识是否存在于成员信息的成员的标识中，来判断该标识的成员是否为该用户组内的成员，在判断为是的时候，再继续判断是否已接收到用户组内所有成员的监控事件报告。
若第一消息中包含多个监控事件，即第一消息用于配置针对用户组的监控事件的数量为多个，例如为M个，那么在针对N个成员的每一个成员，接收到的事件报告的次数达到最大报告次数，或针对N个成员的每一个成员的M个监控事件中的每一个监控事件的监控事件报告的次数达到最大报告次数，确定用户组的所有成员的监控事件报告均已接收完毕。
通过S509～S510来实现删除该用户组的监控事件的配置。
S509、SCEF向SCS/AS发送监控请求消息，SCS/AS接收SCEF发送的监控请求消息。
监控请求消息中携带TLTRI和删除指示，删除指示用于指示SCS/AS删除该用户组的 监控事件的配置。
S510、SCS/AS向SCEF返回监控应答消息，SCEF接收SCS/AS返回的监控应答消息。
监控应答消息用于确认S509的监控请求消息。
图5中不同步骤发送的监控请求消息和监控应答消息并未做区分，可以理解的是，各个相同名称的消息可能携带内容相同也可能不同。图5中S505～S510显示的步骤相同，但是实际上根据上文的描述，可以根据S505中SCEF两种不同类型的处理各步骤可以做不同的解释，具体各步骤的详细介绍如上文所述。
此外，若SCEF因为某种原因暂时不执行S506～S510，在此期间，SCEF接收到针对步骤S401监控事件请求的事件报告，则SCEF停止向SCS/AS发送监控事件报告。
综上所述，通过图4和图5所示的方法，在LTE系统中，SCEF通过获取用户组的成员信息，在接收到监控事件报告时，能够根据用户组的成员信息判断用户组内的所有成员的监控事件报告均已接收完毕，从而能够进一步删除该用户组的监控事件的配置或停止事件报告，避免资源的浪费，以及有助于保证后续策略的正确执行。
应用场景二：5G系统。开放功能实体为NEF，第三方应用实体为SCS/AS，移动性管理网元为AMF，用户数据管理实体为UDM203。
如图6所示，在应用场景二下事件监控的流程具体如下所述。
S601、SCS/AS向NEF发送基于用户组的监控事件订阅请求(Nnef_EventExposure_Subscribe request)消息，NEF接收SCS/AS接收Nnef_EventExposure_Subscribe request消息。该Nnef_EventExposure_Subscribe request消息为上述实施例所述的第一消息，具有第一消息的属性和功能。
该Nnef_EventExposure_Subscribe request消息中携带用户组的成员信息，还可以但不限于携带以下至少一种信息：SCS/AS事件通知地址和事件通知标识、监控事件(Monitoring Event)、外部组标识(External Group Id)、事件报告模式。其中事件报告模式可以取值为报告达到最大次数、周期性报告或报告达到最大持续时间。其中，若事件报告粒度为报告达到最大次数，则该Nnef_EventExposure_Subscribe request消息中还携带最大报告次数。
监控事件订阅消息中的参数配置适用于用户组的每一个成员。若事件报告粒度为报告达到最大次数，该Nnef_EventExposure_Subscribe request消息中携带最大报告次数的值为1，则表示该Nnef_EventExposure_Subscribe request消息为一次监控请求。
在5G系统中，监控事件的订阅可以类似于LTE系统中的监控事件的配置。
S602、NEF保存S601接收到的消息中携带的各种信息，NEF根据本地策略对订阅的监控请求进行授权。
S603、NEF向UDM发送监控事件订阅请求消息，即Nudm_EventExposure_Subscribe Request消息，UDM接收NEF发送的Nudm_EventExposure_Subscribe Request消息。
该消息中携带External Group Id，Monitoring Event、NEF事件通知地址和事件通知标识。还可以携带S601中Nnef_EventExposure_Subscribe request消息中的一些可选参数。NEF事件通知地址和事件通知标识用于关联将来的事件通知，进而确定用户组。
S604、UDM检查S603中接收到的Nudm_EventExposure_Subscribe Request消息，检查通过后，UDM保存消息中携带的参数。UDM确定外部组标识与用户组成员的标识的对应 关系。
S605、UDM向NEF发送监控事件订阅响应消息(Nudm_EventExposure_Subscribe Reponse)消息，NEF接收UDM发送的监控事件订阅响应消息。
可选的，该监控事件订阅响应消息中携带用户组的成员信息。该监控事件订阅响应消息中还携带接收的UDM订阅标识和接收指示。
S606、NEF向SCS/AS发送监控事件订阅响应消息(Nnef_EventExposure_Subscribe Response)，SCS/AS接收NEF发送的监控事件订阅响应消息。
该消息中携带NEF订阅标识和接收指示。
针对用户组内的每一个成员，执行S607～S611。
S607、UDM为用户组内的一个成员向为该成员服务的AMF发送签约数据管理(Subscriber Data Management，SDM)通知请求消息(Nudm_SDM_Notification Request)，AMF接收UDM发送的SDM通知请求消息。
该消息中携带外部标识或MSISDN，还可以携带最大报告次数。
S608、UDM为S607所述的一个成员，向AMF发送监控事件订阅请求消息(Namf_EventExposure_Subscribe Request)，AMF接收UDM发送的Namf_EventExposure_Subscribe Request消息。
该消息中携带Monitoring Event，NEF事件通知地址和事件通知标识。
S609、AMF保存接收到Namf_EventExposure_Subscribe Request消息的参数，进行相应的处理。
处理过程包括：根据最大报告次数设置剩余报告次数。
S610、AMF向UDM发送SDM通知响应消息(Nudm_SDM_Notification Reponse)，UDM接收AMF发送的Nudm_SDM_Notification Reponse消息。
该消息中携带接收的指示。
S611、AMF向UDM返回监控事件订阅响应消息(Namf_EventExposure_Subscribe Response)，UDM接收AMF发送的Namf_EventExposure_Subscribe Response消息。
该消息中携带AMF订阅标识和接收指示。若AMF已有本次订阅的监控事件的监控事件报告，则AMF在Namf_EventExposure_Subscribe Response消息中携带监控事件报告、NEF事件通知地址和事件通知标识。进一步的，若S607中监控事件订阅为第一次监控请求，则AMF在本地删除针对该用户组的监控事件配置；若在S607中携带最大报告次数取值大于1，则AMF将剩余报告次数减1。
若在S611中携带了监控事件报告，则执行后续步骤，否则不执行。
S612、UDM向NEF发送监控事件通知请求消息(Ndum_EventExposure_Notify Request)，NEF接收UDM发送的Ndum_EventExposure_Notify Request消息。NEF向UDM返回Ndum_EventExposure_Notify Response消息。
该Ndum_EventExposure_Notify Reques消息中携带NEF事件通知标识、监控事件报告和监控事件报告对应的外部标识或MSISDN。实际应用中，UDM可能会汇聚多个来自AMF的监控事件报告，并在一条监控事件通知请求消息中发送给NEF。即在监控事件通知请求消息中携带NEF事件通知标识，监控事件报告、外部标识或MSISDN的对应关系的列表。
S613、NEF向SCS/AS发送监控事件订阅请求消息(Nnef_EventExposure_Notify Request)，SCS/AS接收NEF发送的Nnef_EventExposure_Notify Request消息。SCS/AS向NEF返回监控事件订阅应答消息(Nnef_EventExposure_Notify Response)，NEF接收SCS/AS返回的Nnef_EventExposure_Notify Response。
该Nnef_EventExposure_Notify Request消息携带SCS/AS事件通知标识、监控事件报告和外部标识或MSISDN。若S612携带了多个监控事件报告，则该Nnef_EventExposure_Notify Request消息中携带SCS/AS事件通知标识与监控事件报告、外部标识或MSISDN的对应关系的列表。
S614、NEF的处理，过程包括以下几种情况。
若在S601中监控事件订阅请求消息为一次监控请求，且S611中AMF在Namf_EventExposure_Subscribe Response消息中携带监控事件报告，在S612中UDM向NEF发送了来自AMF的监控事件报告，则NEF根据接收的NEF通知标识确定事件报告对应的用户组，再根据S601或S605中接收到的用户组的成员信息，确定S612接收到的监控事件报告是否包含了所有成员的监控事件报告。若包含了所有成员的监控事件报告，则确定用户组内所有成员的监控事件报告均已接收完毕(即确定用户组内所有成员的监控事件报告已完成)，发起删除该用户组的监控事件的配置或停止向SCS/AS发送监控事件报告。用户组内所有成员的监控事件报告已完成即为用户组的监控事件报已完成。
具体的，根据用户组的成员信息(例如N个标识或成员数目N)，确定用户组内所有成员的监控事件报告均已接收完毕的过程如下。若成员信息为成员数目，则NEF根据S612接收到的监控事件报告关联的不同的成员的标识(MSISDN或外部标识)的数目，来判断已接收到多少个成员的监控事件报告，在已接收到监控事件报告的成员数目达到成员信息的成员数目时，确定用户组内所有成员的监控事件报告均已接收完毕。若成员信息为各个成员的标识，则NEF根据S612接收到的监控事件报告关联的不同的成员的标识，与成员信息中的成员的标识比对，来判断已接收到多少个成员的监控事件报告，当已接收到监控事件报告的成员的标识已达到成员信息中的所有成员标识时，确定用户组内所有成员的监控事件报告均已接收完毕。可选的，NEF接收到监控事件报告关联的成员的标识时，根据该成员的标识是否存在于成员信息的成员的标识中，来判断该标识的成员是否为该用户组内的成员，在判断为是的时候，再继续判断是否已接收到用户组内所有成员的监控事件报告。其中，若监控事件订阅请求中包含多个监控事件，即监控事件订阅请求用于配置针对用户组的监控事件的数量为多个，例如为M个，那么根据S612接收到的监控事件报告，在针对N个成员的每一个成员，都接收到监控事件报告，或针对N个成员的每一个成员的M个监控事件中的每一个监控事件都接收到监控事件报告，则确定用户组的所有成员的监控事件报告均已接收完毕。
通过S615～S622来实现删除该用户组的监控事件的订阅。
S615、NEF向UDM发送监控事件去订阅请求(Nudm_EventExposure_Unsubscribe Request)，在Nudm_EventExposure_Unsubscribe Request消息中携带UDM订阅标识。UDM接收NEF发送的Nudm_EventExposure_Unsubscribe Request消息。
S616、UDM向AMF发送监控事件去订阅请求(Namf_EventExposure_Unsubscribe  Request),AMF接收UDM发送的Namf_EventExposure_Unsubscribe Request。
在Namf_EventExposure_Unsubscribe Request消息中携带AMF订阅标识。
S617、AMF删除AMF订阅标识对应的监控事件订阅信息。
S618、AMF向UDM返回应答消息。
S619、UDM删除UDM订阅标识对应的监控事件订阅信息，向NEF返回确认消息。
S620、NEF向SCS/AS发送监控事件通知请求消息(Nnef_EventExposure_Notifiy Request)，在Nnef_EventExposure_Notifiy Request消息中携带SCS事件通知标识和删除指示。SCS/AS返回应答消息。
S621、SCS/AS向NEF发送监控事件去订阅请求(Nnef_EventExposure_Unsubscribe Request)，在Nnef_EventExposure_Unsubscribe Request消息中携带NEF订阅标识。
S622、NEF删除NEF订阅标识对应的事件订阅信息后返回确认消息。
需要说明的是，S615和S620没有严格的执行顺序，可以交换顺序，也可以同时执行。
此外，若NEF因为某种原因暂时不执行S615～S622，在此期间，SCEF接收到针对步骤S601监控事件订阅请求的监控事件报告，则SCEF停止向SCS/AS发送监控事件报告。
若S611中AMF携带了监控事件报告，但是最大报告次数的值大于1；或者，S611中AMF并未上报监控事件报告。则可根据图7所示的监控流程来实现后续事件监控。
如图7所示，具体的的监控流程如下所述。
S701、AMF在图6的S610接收到Nudm_SDM_Notification Reponse消息后，根据Nudm_SDM_Notification Reponse消息携带的参数对用户组内的成员进行事件监控。
需要理解的是，用户组的各个成员可能归属于相同的AMF，也可能归属于不同的AMF，服务用户组的AMF可以是一个或多个。每一个AMF针对其服务的用户组内的成员执行的流程是相同或类似的。
S702、AMF向NEF发送监控事件通知请求消息，即Namf_EventExposure_Notify Request，该Namf_EventExposure_Notify Request消息中携带NEF事件通知地址和标识、监控事件报告和监控事件报告对应的外部标识或MSISDN。若事件报告模式为报告达到最大次数，且最大报告次数为1，则AMF在本地删除针对用户组的监控事件订阅。若最大报告次数的值大于1，则AMF将记录的剩余报告次数减一。当剩余报告次数为0时，AMF在本地删除针对该用户组的监控事件的配置。
S703、NEF向AMF返回确认消息，即Namf_EventExposure_Notify Reponse。AMF接收NEF返回的Namf_EventExposure_Notify Reponse。
S704、NEF向SCS/AS发送监控事件通知请求，即Nnef_EventExposure_Notify Request，Nnef_EventExposure_Notify Request消息中携带SCS、AS事件通知标识、监控事件报告和外部标识或MSISDN。
可选的，NEF可能会汇聚多个来自AMF的监控事件报告，并在一条Nnef_EventExposure_Notify Request消息中发送给SCS/AS，则Nnef_EventExposure_Notify Request消息中携带SCS/AS事件通知标识与监控事件报告、外部标识或MSISDN的对应关系的列表。
S705、SCS/AS向SCEF返回确认消息，即Nnef_EventExposure_Notify Reponse，SCEF 接收SCS/AS返回的Nnef_EventExposure_Notify Reponse。
S706、NEF的处理，过程包括以下几种情况。
NEF根据S602中接收到事件通知标识确定事件报告对应的用户组，再根据S601或S605中接收到的用户组的成员信息，确定是否已接收到了所有成员的监控事件报告，若确定已接收到了所有成员的监控事件报告，则确定用户组的所有成员的监控事件报告均已接收完毕(确定用户组的所有成员的监控事件报告已完成)，发起删除该用户组的监控事件的配置或停止向SCS/AS发送监控事件报告。用户组内所有成员的监控事件报告已完成即为用户组的监控事件报已完成。
具体的，确定用户组的所有成员的监控事件报告均已接收完毕的过程如下。
若在S601中监控事件订阅请求为一次监控请求，则根据用户组的成员信息(例如N个标识或成员数目N)，确定用户组的所有成员的监控事件报告均已接收完毕的过程如下：若成员信息为成员数目，则NEF根据S612接收到的监控事件报告关联的不同的成员的标识(MSISDN或外部标识)的数目，来判断已接收到多少个成员的监控事件报告，在已接收到监控事件报告的成员数目达到成员信息的成员数目时，确定用户组的所有成员的监控事件报告均已接收完毕。若成员信息为各个成员的标识，则NEF根据S612接收到的监控事件报告关联的不同的成员的标识，与成员信息中的成员的标识比对，来判断已接收到多少个成员的监控事件报告，当已接收到监控事件报告的成员的标识已达到成员信息中的所有成员标识时，确定用户组的所有成员的监控事件报告均已接收完毕。可选的，NEF接收到监控事件报告关联的成员的标识时，根据该成员的标识是否存在于成员信息的成员的标识中，来判断该标识的成员是否为该用户组内的成员，在判断为是的时候，再继续判断是否已接收到用户组的所有成员的监控事件报告。其中，若第一监控请求消息中包含多个监控事件，即第一监控请求消息用于配置针对用户组的监控事件的数量为多个，例如为M个，那么根据S612接收到的监控事件报告，在针对N个成员的每一个成员，都接收到监控事件报告，或针对N个成员的每一个成员的M个监控事件中的每一个监控事件都接收到监控事件报告，则确定用户组的所有成员的监控事件报告均已接收完毕。
若最大报告次数的值大于1，则NEF根据用户组的成员信息(例如N个标识或成员数目N)，确定用户组内所有成员的监控事件报告均已接收完毕的过程如下。若成员信息为成员数目，则NEF根据S612接收到的监控事件报告关联的不同的成员的标识(MSISDN或外部标识)的数目，来判断已接收到多少个成员的监控事件报告，并判断每一个成员的累计报告次数是否达到最大报告次数。在已接收到监控事件报告的成员数目达到成员信息的成员数目，并且每一个成员的累计报告次数均达到最大报告次数时，确定用户组内所有成员的监控事件报告均已接收完毕。
若成员信息为各个成员的标识，则NEF根据S612接收到的监控事件报告关联的不同的成员的标识，与成员信息中的成员的标识比对，来判断已接收到多少个成员的监控事件报告，并判断每一个成员的累计报告次数是否达到最大报告次数。当已接收到监控事件报告的成员的标识已达到成员信息中的所有成员标识，并且每一个成员的累计报告次数均达到最大报告次数时，确定用户组内所有成员的监控事件报告均已接收完毕。可选的，NEF接收到监控事件报告关联的成员的标识时，根据该成员的标识是否存在于成员信息的成员的 标识中，来判断该标识的成员是否为该用户组内的成员，在判断为是的时候，再继续判断是否已接收到用户组内所有成员的监控事件报告。
若第一消息中包含多个监控事件，即第一消息用于配置针对用户组的监控事件的数量为多个，例如为M个，那么在针对N个成员的每一个成员，接收到的事件报告的次数达到最大报告次数，或针对N个成员的每一个成员的M个监控事件中的每一个监控事件的监控事件报告的次数达到最大报告次数，确定用户组的所有成员的监控事件报告均已接收完毕。
通过S707～S714来实现删除该用户组的监控事件的订阅，具体的S707～S714与S615～S622相同，重复之处不再赘述。
此外，若NEF因为某种原因暂时不执行S707～S714，在此期间，SCEF接收到针对步骤S601监控事件订阅请求的监控事件报告，则SCEF停止向SCS/AS发送监控事件报告。
综上所述，通过图6和图7所示的方法，在5G系统中，NEF通过获取用户组的成员信息，在接收到监控事件报告时，能够根据用户组的成员信息判断用户组内的所有成员的监控事件报告均已接收完毕，从而能够进一步删除该用户组的监控事件的配置或停止向SCS/AS发送监控事件报告，避免资源的浪费，以及有助于保证后续策略的正确执行。
基于上述实施例提供的事件监控方法，如图8所示，本申请实施例还提供一种事件监控装置800，该事件监控装置800包括：接收单元801和处理单元802。
该事件监控装置800用于执行上述实施例提供的事件监控方法中开放功能实体执行的步骤，具体为：
接收单元801，用于接收第一消息，第一消息用于配置针对一个用户组的监控事件。
处理单元，用于获取用户组的成员信息，以及用于根据成员信息，确定用户组的所有成员的监控事件报告均已接收完毕，删除针对用户组的监控事件的配置；或者，用于获取用户组的成员信息，以及用于根据成员信息，确定用户组的所有成员的监控事件报告是否完成。
事件监控装置800中接收单元801和处理单元802还可用于执行上述实施例提供的事件监控方法中开放功能实体对应的其它步骤，重复之处在此不再赘述。
该事件监控装置800还用于执行上述实施例提供的事件监控方法中用户数据管理实体执行的步骤，具体为：
接收第一请求消息，所述第一请求消息用于配置针对一个用户组的监控事件；向开放功能实体发送第二应答消息，所述第一应答消息中携带用户组的成员信息。
事件监控装置800中接收单元801和处理单元802还可用于执行上述实施例提供的事件监控方法中用户数据管理实体对应的其它步骤，重复之处在此不再赘述。
该事件监控装置800还用于执行上述实施例提供的事件监控方法中第三方应用实体执行的步骤，具体为：
向开放功能实体发送第一消息，第一消息用于配置针对一个用户组的监控事件，第一消息中携带用户组的成员信息。
事件监控装置800中接收单元801和处理单元802还可用于执行上述实施例提供的事件监控方法中第三方应用实体对应的其它步骤，重复之处在此不再赘述。
基于上述实施例提供的事件监控方法，如图9所示，本申请实施例还提供一种事件监 控装置900，该网络参数调优装置900用于执行上述事件监控方法，事件监控装置900包括：收发器901、处理器902和存储器903。存储器903为可选的。处理器902用于调用一组程序，当程序被执行时，使得处理器902执行上述事件监控方法。存储器903用于存储处理器902执行的程序。图8中的功能模块接收单元801可以通过收发器901来实现，处理单元802可以通过处理器902来实现。
处理器902可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合。
处理器902还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic,GAL)或其任意组合。
存储器903可以包括易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)；存储器903也可以包括非易失性存储器(non-volatile memory)，例如快闪存储器(flash memory)，硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)；存储器903还可以包括上述种类的存储器的组合。
为了实现上述图8或图9所述的装置的功能，本申请实施例还提供一种芯片，包括处理器，用于支持该装置实现上述事件监控方法中开放功能实体、或用户数据管理实体、或第三方应用实体所涉及的功能。在一种可能的设计中，该芯片与存储器连接或者该芯片包括存储器，该存储器用于保存该装置必要的程序指令和数据。
本申请实施例提供了一种计算机存储介质，存储有计算机程序，该计算机程序包括用于执行上述事件监控方法。
本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述事件监控方法。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方 框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和修改。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的精神和范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (49)

  1. 一种事件监控方法，其特征在于，包括：
    开放功能实体接收第一消息，所述第一消息用于配置针对一个用户组的监控事件；
    所述开放功能实体获取所述用户组的成员信息；
    所述开放功能实体根据所述成员信息，确定所述用户组的所有成员的监控事件报告均已接收完毕，删除针对所述用户组的监控事件的配置。
  2. 如权利要求1所述的方法，其特征在于，所述开放功能实体获取所述用户组的成员信息，包括：
    所述第一消息中携带所述用户组的成员信息，所述开放功能实体从所述第一消息中获取所述成员信息；或者，
    所述开放功能实体从用户数据管理实体获取所述用户组的成员信息。
  3. 如权利要求1或2所述的方法，其特征在于，所述用户组的成员信息包括：所述用户组的成员的数目N；或者，N个标识，所述标识用于区分所述用户组的不同成员。
  4. 如权利要求3所述的方法，其特征在于，所述开放功能实体根据所述成员信息，确定所述用户组的所有成员的监控事件报告均已接收完毕，包括：
    若所述第一消息用于配置对所述用户组进行一次监控请求，则所述开放功能实体在接收到N个所述成员的监控事件报告时，确定所述用户组的所有成员的监控事件报告均已接收完毕。
  5. 如权利要求4所述的方法，其特征在于，所述开放功能实体根据所述成员信息，确定所述用户组内所有成员的监控事件报告均已接收完毕，包括：
    若所述第一消息用于配置针对所述用户组的监控事件的数量为多个，则所述开放功能实体在针对N个所述成员的每一个成员，均接收到所述多个监控事件中的每一个监控事件的监控事件报告时，确定所述成员组内所有用户的监控事件报告均已接收完毕。
  6. 如权利要求4或5所述的方法，其特征在于，所述方法还包括：
    若所述第一消息中不包括最大报告次数、且不包括持续时间，则所述开放功能实体确定所述第一消息用于配置对所述用户组进行一次监控请求；或者，
    若所述第一消息中包括第一最大报告次数、且所述第一最大报告次数为1，则所述开放功能实体确定所述第一消息用于配置对所述用户组进行一次监控请求。
  7. 如权利要求3所述的方法，其特征在于，所述开放功能实体根据所述成员信息，确定所述用户组内所有成员的监控事件报告均已接收完毕，包括：
    若所述第一消息中包括第二最大报告次数，则所述开放功能实体针对N个所述成员的每一个成员，接收到的监控事件报告的次数均达到所述第二最大报告次数时，确定所述成员组的所有成员的监控事件报告均已接收完毕。
  8. 如权利要求7所述的方法，其特征在于，所述开放功能实体针对N个所述成员的每一个成员，接收到的监控事件报告的次数均达到所述第二最大报告次数时，确定所述成员组内所有成员的监控事件报告均已接收完毕，包括：
    若所述第一消息用于配置针对所述用户组的监控事件的数量为多个，则所述开放功能 实体在针对N个所述成员的每一个成员，接收到所述多个监控事件中的每一个监控事件的监控事件报告次数均达到第二最大报告次数时，确定所述用户组的所有成员的监控事件报告均已接收完毕。
  9. 如权利要求3～8任一项所述的方法，其特征在于，所述方法还包括：
    若所述用户组的成员信息包括所述N个标识，则所述开放功能实体每接收到一个监控事件报告，判断所述一个监控事件报告是否为所述成员的监控事件报告，获得判断结果，所述判断结果用于确定所述用户组内所有成员的监控事件报告是否均已接收完毕。
  10. 如权利要求1～9任一项所述的方法，其特征在于，所述开放功能实体删除针对所述用户组的监控事件的配置，包括以下至少一项：
    所述开放功能实体删除本地存储的针对所述用户组的监控事件的配置；
    所述开放功能实体向用户数据管理实体发送第二消息，所述第二消息用于指示所述用户数据管理实体删除针对所述用户组的监控事件的配置；
    所述开放功能实体向所述第三方应用实体发送第三消息，所述第三消息用于指示所述第三方应用实体删除针对所述用户组的监控事件的配置。
  11. 一种事件监控装置，其特征在于，包括：
    接收单元，用于接收第一消息，所述第一消息用于配置针对一个用户组的监控事件；
    处理单元，用于获取所述用户组的成员信息；
    所述处理单元，用于根据所述成员信息，确定所述用户组的所有成员的监控事件报告均已接收完毕，删除针对所述用户组的监控事件的配置。
  12. 如权利要求11所述的装置，其特征在于，所述处理单元具体用于：
    所述第一消息中携带所述用户组的成员信息，从所述第一消息中获取所述成员信息；或者，
    从用户数据管理实体获取所述用户组的成员信息。
  13. 如权利要求11或12所述的装置，其特征在于，所述用户组的成员信息包括：所述用户组的成员的数目N；或者，N个标识，所述标识用于区分所述用户组的不同成员。
  14. 如权利要求13所述的装置，其特征在于，所述处理单元具体用于：
    若所述第一消息用于配置对所述用户组进行一次监控请求，则在接收到N个所述成员的监控事件报告时，确定所述用户组的所有成员的监控事件报告均已接收完毕。
  15. 如权利要求14所述的装置，其特征在于，所述处理单元具体用于：
    若所述第一消息用于配置针对所述用户组的监控事件的数量为多个，则所述开放功能实体在针对N个所述成员的每一个成员，均接收到所述多个监控事件中的每一个监控事件的监控事件报告时，确定所述成员组内所有用户的监控事件报告均已接收完毕。
  16. 如权利要求14或15所述的装置，其特征在于，所述处理单元还用于：
    若所述第一消息中不包括最大报告次数、且不包括持续时间，则确定所述第一消息用于配置对所述用户组进行一次监控请求；或者，
    若所述第一消息中包括第一最大报告次数、且所述第一最大报告次数为1，则确定所述第一消息用于配置对所述用户组进行一次监控请求。
  17. 如权利要求13所述的装置，其特征在于，所述处理单元具体用于：
    若所述第一消息中包括第二最大报告次数，则针对N个所述成员的每一个成员，接收到的监控事件报告的次数均达到所述第二最大报告次数时，确定所述成员组的所有成员的监控事件报告均已接收完毕。
  18. 如权利要求17所述的装置，其特征在于，所述处理单元具体用于：
    若所述第一消息用于配置针对所述用户组的监控事件的数量为多个，则在针对N个所述成员的每一个成员，接收到所述多个监控事件中的每一个监控事件的监控事件报告次数均达到第二最大报告次数时，确定所述用户组的所有成员的监控事件报告均已接收完毕。
  19. 如权利要求13～18任一项所述的装置，其特征在于，所述处理单元还用于：
    若所述用户组的成员信息包括所述N个标识，则每接收到一个监控事件报告，判断所述一个监控事件报告是否为所述成员的监控事件报告，获得判断结果，所述判断结果用于确定所述用户组内所有成员的监控事件报告是否均已接收完毕。
  20. 如权利要求11～19任一项所述的装置，其特征在于，所述处理单元在删除针对所述用户组的监控事件的配置时，具体执行以下至少一项操作：
    删除本地存储的针对所述用户组的监控事件的配置；
    向用户数据管理实体发送第二消息，所述第二消息用于指示所述用户数据管理实体删除针对所述用户组的监控事件的配置；
    向所述第三方应用实体发送第三消息，所述第三消息用于指示所述第三方应用实体删除针对所述用户组的监控事件的配置。
  21. 一种事件监控方法，其特征在于，包括：
    开放功能实体接收第一消息，所述第一消息用于配置针对一个用户组的监控事件；
    所述开放功能实体获取所述用户组的成员信息；
    所述开放功能实体根据所述成员信息确定所述用户组的所有成员的监控事件报告是否完成。
  22. 如权利要求21所述的方法，其特征在于，所述开放功能实体获取所述用户组的成员信息，包括：
    所述第一消息中携带所述用户组的成员信息，所述开放功能实体从所述第一消息中获取所述成员信息；或者，
    所述开放功能实体从用户数据管理实体获取所述用户组的成员信息。
  23. 如权利要求21或22所述的方法，其特征在于，所述用户组的成员信息包括：所述用户组的成员的数目N；或者，N个标识，所述标识用于区分所述用户组的不同成员。
  24. 如权利要求23所述的方法，其特征在于，所述开放功能实体根据所述成员信息，确定所述用户组的所有成员的监控事件报告是否完成，包括：
    若所述第一消息用于配置对所述用户组进行一次监控请求，则所述开放功能实体在接收到N个所述成员的监控事件报告时，确定所述用户组的所有成员的监控事件报告已完成。
  25. 如权利要求23所述的方法，其特征在于，所述开放功能实体根据所述成员信息，确定所述用户组的所有成员的监控事件报告是否完成，包括：
    若所述第一消息用于配置对所述用户组进行一次监控请求，且所述第一消息用于配置针对所述用户组的监控事件的数量为多个，则所述开放功能实体在针对N个所述成员的每 一个成员，均接收到所述多个监控事件中的每一个监控事件的监控事件报告时，确定所述用户组的所有成员的监控事件报告已完成。
  26. 如权利要求24或25所述的方法，其特征在于，所述方法还包括：
    若所述第一消息中不包括最大报告次数、且不包括持续时间，则所述开放功能实体确定所述第一消息用于配置对所述用户组进行一次监控请求；或者，
    若所述第一消息中包括第一最大报告次数、且所述第一最大报告次数为1，则所述开放功能实体确定所述第一消息用于配置对所述用户组进行一次监控请求。
  27. 如权利要求23所述的方法，其特征在于，所述开放功能实体根据所述成员信息，确定所述用户组内所有成员的监控事件报告是否完成，包括：
    若所述第一消息中包括第二最大报告次数，则所述开放功能实体针对N个所述成员的每一个成员，接收到的监控事件报告的次数均达到所述第二最大报告次数时，确定所述成员组的所有成员的监控事件报告已完成。
  28. 如权利要求23所述的方法，其特征在于，所述开放功能实体根据所述成员信息，确定所述用户组内所有成员的监控事件报告是否完成，包括：
    若所述第一消息中包括第二最大报告次数，且所述第一消息用于配置针对所述用户组的监控事件的数量为多个，则所述开放功能实体在针对N个所述成员的每一个成员，接收到所述多个监控事件中的每一个监控事件的监控事件报告次数均达到第二最大报告次数时，确定所述用户组的所有成员的监控事件报告已完成。
  29. 如权利要求23～28任一项所述的方法，其特征在于，所述方法还包括：
    若所述用户组的成员信息包括所述N个标识，则所述开放功能实体每接收到一个监控事件报告，判断所述一个监控事件报告是否为所述成员的监控事件报告，获得判断结果，所述判断结果用于确定所述用户组内所有成员的监控事件报告是否完成。
  30. 如权利要求21～29任一项所述的方法，其特征在于，若所述开放功能实体根据所述成员信息确定所述用户组的所有成员的监控事件报告已完成，所述方法还包括，
    所述开放功能实体删除针对所述用户组的监控事件的配置或停止向第三方应用实体发送所述监控事件报告。
  31. 如权利要求30所述的方法，其特征在于，所述开放功能实体删除针对所述用户组的监控事件的配置，包括以下至少一项：
    所述开放功能实体删除本地存储的针对所述用户组的监控事件的配置；
    所述开放功能实体向所述第三方应用实体发送第三消息，所述第三消息用于指示所述第三方应用实体删除针对所述用户组的监控事件的配置。
  32. 如权利要求30所述的方法，其特征在于，所述方法还包括：
    所述开放功能实体向用户数据管理实体发送第二消息，所述第二消息用于指示所述用户数据管理实体删除针对所述用户组的监控事件的配置；或者，
    所述开放功能实体向用户数据管理实体发送第四消息，所述第四消息用于指示所述用户数据管理实体删除针对所述用户组的一个或多个成员的监控事件的配置。
  33. 如权利要求32所述的方法，其特征在于，所述开放功能实体向用户数据管理实体发送第四消息，包括：
    所述开放功能实体确定所述一个或多个成员的监控事件报告已完成，则所述开放功能实体向所述用户数据管理实体发送所述第四消息。
  34. 一种事件监控装置，其特征在于，包括：
    接收单元，用于接收第一消息，所述第一消息用于配置针对一个用户组的监控事件；
    处理单元，用于获取所述用户组的成员信息；
    所述处理单元，用于根据所述成员信息，确定所述用户组的所有成员的监控事件报告是否完成。
  35. 如权利要求34所述的装置，其特征在于，所述处理单元具体用于：
    所述第一消息中携带所述用户组的成员信息，从所述第一消息中获取所述成员信息；或者，
    从用户数据管理实体获取所述用户组的成员信息。
  36. 如权利要求34或35所述的装置，其特征在于，所述用户组的成员信息包括：所述用户组的成员的数目N；或者，N个标识，所述标识用于区分所述用户组的不同成员。
  37. 如权利要求35所述的装置，其特征在于，所述处理单元具体用于：
    若所述第一消息用于配置对所述用户组进行一次监控请求，则在接收到N个所述成员的监控事件报告时，确定所述用户组的所有成员的监控事件报告已完成。
  38. 如权利要求35所述的装置，其特征在于，所述处理单元具体用于：
    若所述第一消息用于配置对所述用户组进行一次监控请求，且所述第一消息用于配置针对所述用户组的监控事件的数量为多个，则所述开放功能实体在针对N个所述成员的每一个成员，均接收到所述多个监控事件中的每一个监控事件的监控事件报告时，确定所述用户组的所有成员的监控事件报告已完成。
  39. 如权利要求37或38所述的装置，其特征在于，所述处理单元还用于：
    若所述第一消息中不包括最大报告次数、且不包括持续时间，则确定所述第一消息用于配置对所述用户组进行一次监控请求；或者，
    若所述第一消息中包括第一最大报告次数、且所述第一最大报告次数为1，则确定所述第一消息用于配置对所述用户组进行一次监控请求。
  40. 如权利要求36所述的装置，其特征在于，所述处理单元具体用于：
    若所述第一消息中包括第二最大报告次数，则针对N个所述成员的每一个成员，接收到的监控事件报告的次数均达到所述第二最大报告次数时，确定所述成员组的所有成员的监控事件报告已完成。
  41. 如权利要求36所述的装置，其特征在于，所述处理单元具体用于：
    若所述第一消息中包括第二最大报告次数，且所述第一消息用于配置针对所述用户组的监控事件的数量为多个，则在针对N个所述成员的每一个成员，接收到所述多个监控事件中的每一个监控事件的监控事件报告次数均达到第二最大报告次数时，确定所述用户组的所有成员的监控事件报告已完成。
  42. 如权利要求36～41任一项所述的装置，其特征在于，所述处理单元还用于：
    若所述用户组的成员信息包括所述N个标识，则每接收到一个监控事件报告，判断所述一个监控事件报告是否为所述成员的监控事件报告，获得判断结果，所述判断结果用于 确定所述用户组的所有成员的监控事件报告是否完成。
  43. 如权利要求34～42任一项所述的装置，其特征在于，所述处理单元在确定所述用户组的所有成员的监控事件报告已完成时，删除针对所述用户组的监控事件的配置或停止向第三方应用发送所述监控事件报告。
  44. 如权利要求43所述的装置，其特征在于，所述处理单元在删除针对所述用户组的监控事件的配置时，具体执行以下至少一项操作：
    删除本地存储的针对所述用户组的监控事件的配置；
    向所述第三方应用实体发送第三消息，所述第三消息用于指示所述第三方应用实体删除针对所述用户组的监控事件的配置。
  45. 如权利要求43所述的装置，其特征在于，所述处理单元在删除针对所述用户组的监控事件的配置时，还用于：
    向用户数据管理实体发送第二消息，所述第二消息用于指示所述用户数据管理实体删除针对所述用户组的监控事件的配置；或者，
    向用户数据管理实体发送第四消息，所述第四消息用于指示所述用户数据管理实体删除针对所述用户组的一个或多个成员的监控事件的配置。
  46. 如权利要求45所述的装置，其特征在于，所述处理单元具体用于：
    确定所述一个或多个成员的监控事件报告已完成，向所述用户数据管理实体发送所述第四消息。
  47. 一种计算机可读存储介质，其特征在于，所述计算机存储介质中存储有计算机可读指令，当计算机读取并执行所述计算机可读指令时，使得计算机执行如权利要求1-10和21～33任意一项所述的方法。
  48. 一种计算机程序产品，其特征在于，当计算机读取并执行所述计算机程序产品时，使得计算机执行如权利要求1-10和21～33任意一项所述的方法。
  49. 一种芯片，其特征在于，所述芯片与存储器相连或者所述芯片包括所述存储器，用于读取并执行所述存储器中存储的软件程序，以实现如权利要求1-10和21～33任意一项所述的方法。
PCT/CN2019/081696 2018-04-09 2019-04-08 一种事件监控方法及装置 WO2019196773A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
KR1020207030612A KR102517686B1 (ko) 2018-04-09 2019-04-08 이벤트 모니터링 방법 및 장치
BR112020020432-3A BR112020020432A2 (pt) 2018-04-09 2019-04-08 Método de monitoramento de eventos e aparelho
JP2020552193A JP7130767B2 (ja) 2018-04-09 2019-04-08 イベント監視方法および装置
EP19785187.6A EP3764680B1 (en) 2018-04-09 2019-04-08 Event monitoring method and apparatus
US17/066,914 US11425538B2 (en) 2018-04-09 2020-10-09 Event monitoring method and apparatus

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201810312936 2018-04-09
CN201810312936.6 2018-04-09
CN201810349848.3A CN110366199B (zh) 2018-04-09 2018-04-18 一种事件监控方法及装置
CN201810349848.3 2018-04-18

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/066,914 Continuation US11425538B2 (en) 2018-04-09 2020-10-09 Event monitoring method and apparatus

Publications (1)

Publication Number Publication Date
WO2019196773A1 true WO2019196773A1 (zh) 2019-10-17

Family

ID=68163905

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/081696 WO2019196773A1 (zh) 2018-04-09 2019-04-08 一种事件监控方法及装置

Country Status (1)

Country Link
WO (1) WO2019196773A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105657686A (zh) * 2014-11-17 2016-06-08 中兴通讯股份有限公司 优化用户设备跟踪可靠性的方法及装置
WO2016180961A1 (en) * 2015-05-14 2016-11-17 Telefonaktiebolaget Lm Ericsson (Publ) System and methods for providing monitoring services
CN106454878A (zh) * 2015-08-12 2017-02-22 中兴通讯股份有限公司 一种更新监控任务的方法和装置
CN107438996A (zh) * 2015-03-31 2017-12-05 日本电气株式会社 用于接收通信参数集的通信系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105657686A (zh) * 2014-11-17 2016-06-08 中兴通讯股份有限公司 优化用户设备跟踪可靠性的方法及装置
CN107438996A (zh) * 2015-03-31 2017-12-05 日本电气株式会社 用于接收通信参数集的通信系统
WO2016180961A1 (en) * 2015-05-14 2016-11-17 Telefonaktiebolaget Lm Ericsson (Publ) System and methods for providing monitoring services
CN106454878A (zh) * 2015-08-12 2017-02-22 中兴通讯股份有限公司 一种更新监控任务的方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3764680A4 *

Similar Documents

Publication Publication Date Title
KR102517686B1 (ko) 이벤트 모니터링 방법 및 장치
US10812609B2 (en) Service subscription method and system for reporting service change in communications system
JP5982018B2 (ja) 非アクセス層（ｎａｓ）信号を使用するネットワークでのマシン・タイプ通信（ｍｔｃ）
WO2020224596A1 (zh) 通信方法及装置
WO2018205114A1 (zh) 一种状态切换方法及装置
EP3911010A1 (en) Event monitoring method and device
US20240155316A1 (en) Method and apparatus for event monitoring
CN110121859A (zh) 一种信息验证方法及相关设备
WO2019024102A1 (zh) 无线通信中的会话处理方法及终端设备
KR101261358B1 (ko) 가입자 데이터베이스에 대한 방법 및 장치
WO2020052463A1 (zh) 通信方法和网元
WO2019196773A1 (zh) 一种事件监控方法及装置
WO2021115464A1 (zh) 一种网络切片选择方法及相关装置
CN107113597B (zh) 在多个设备sim卡上提供服务许可聚合的系统和方法
CN113056928B (zh) 用于事件监视的方法和装置
US20220150111A1 (en) Method and apparatus for managing a parameter in a time sensitive network
EP4309335A1 (en) Data management in a network function
WO2011157122A2 (zh) 终端配置方法和设备

Legal Events

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

Ref document number: 19785187

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020552193

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019785187

Country of ref document: EP

Effective date: 20201007

Ref document number: 20207030612

Country of ref document: KR

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112020020432

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112020020432

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20201005