WO2021227843A1 - 事件订阅管理方法及装置 - Google Patents

事件订阅管理方法及装置 Download PDF

Info

Publication number
WO2021227843A1
WO2021227843A1 PCT/CN2021/089592 CN2021089592W WO2021227843A1 WO 2021227843 A1 WO2021227843 A1 WO 2021227843A1 CN 2021089592 W CN2021089592 W CN 2021089592W WO 2021227843 A1 WO2021227843 A1 WO 2021227843A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
monitoring
information
event
group
Prior art date
Application number
PCT/CN2021/089592
Other languages
English (en)
French (fr)
Inventor
周晓云
阎亚丽
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN202180003358.8A priority Critical patent/CN113841361B/zh
Priority to EP21804508.6A priority patent/EP4138341A4/en
Publication of WO2021227843A1 publication Critical patent/WO2021227843A1/zh
Priority to US17/984,588 priority patent/US20230060429A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/186—Processing of subscriber group data

Definitions

  • the embodiments of the present application relate to the field of communications, and in particular, to an event subscription management method and device.
  • the Service Capability Exposure (SCE) architecture can provide third-party service providers with service capabilities, such as event monitoring capabilities.
  • SCE architecture can perform events on each user in the user group based on instructions issued by the third party. Monitoring (Event Monitoring).
  • event monitoring management in the prior art can only achieve group-based management, such as canceling event monitoring of user groups, or deleting user groups, or adding user groups, but cannot achieve user-based granularity. Management of event monitoring.
  • This application provides an event monitoring management method, device, and system, which can implement event monitoring management with user-based granularity.
  • an embodiment of the present application provides an event monitoring management method, including: receiving an indication message, the indication message includes the identification information of the monitoring event configuration, the identification information of the user, and the indication information, and the identification information of the monitoring event configuration is used to instruct the user
  • the first monitoring event configuration of the user group to which it belongs, the indication information is used to instruct to cancel the event monitoring of the user in the first monitoring event configuration; according to the indication message, the information of the first monitoring event configuration is determined, where the information of the first monitoring event configuration includes At least one of the following: group member information of the user group, user monitoring event report times information; sending a delete message to the second network element for instructing the second network element to delete the first monitoring event configuration, where the delete message is based on the first monitoring event configuration
  • a monitoring event configuration information, which is sent to the second network element after the first event monitoring report is determined to be completed.
  • the information of the first monitoring event configuration indicates that the monitoring event report corresponding to the user should be excluded when the report of the first monitoring event configuration of the user group is counted.
  • the specific execution method of the user who wants to cancel the event monitoring is realized, that is, the monitoring event report of the user is eliminated, thereby realizing the user-granularity management method.
  • the group member information of the user group includes: the number of group members of the user group is the difference between the number of group members of the currently saved user group and the number of users.
  • the group member information of the user group includes: a member user of the user group deletes the user for a currently saved member user of the user group.
  • the group member information of the user group includes identification information and tag information of the user, and the tag information is used to indicate that when the report of the first monitoring event configuration of the user group is counted, the monitoring corresponding to the user should be excluded. Incident report.
  • the users who need to be cancelled are marked to achieve the purpose of eliminating users to be cancelled.
  • determining the information of the first monitoring event configuration includes: deleting the number of saved user monitoring event reports, and the number of group members of the user group is the number of group members and users of the currently saved user group The difference between the number of
  • determining the information of the first monitoring event configuration includes: deleting the saved user's monitoring event report times, and the group member information of the user group includes the identification information and tag information of the user, and the tag The information is used to indicate that when the report configured for the first monitoring event of the user group is counted, the monitoring event report corresponding to the user is excluded.
  • determining the information of the first monitoring event configuration includes: deleting the saved user's monitoring event report times, and the member user of the user group is the member user of the currently saved user group Delete the user.
  • determining the information of the first monitoring event configuration includes: setting the user's monitoring event report times to the maximum report times, that is, by default, the user's report has been completed.
  • setting the number of monitoring event reports of users whose event monitoring to be canceled is set to the maximum value can also achieve the purpose of eliminating users to be canceled.
  • the indication message further includes event monitoring type information, and the indication information is used to instruct to cancel the first event monitoring of the user in the first event monitoring configuration, wherein the event monitoring type information Indicates the event monitoring type of the first event monitoring.
  • the information of the first monitoring event configuration indicates that when the report of the first monitoring event configuration of the user group is counted, the monitoring event report of the first event monitoring corresponding to the user is excluded.
  • determining the information of the first monitoring event configuration includes: setting the user's monitoring event report times to the maximum report times, that is, by default, the user's report has been completed.
  • the indication message further includes validity indication information, which is used to indicate that the content indicated by the indication information continues to take effect.
  • an embodiment of the present application provides an event monitoring management method, including: receiving an indication message, the indication message includes the identification information of the user group, the identification information of the user, and the indication information, and the identification information of the user group is used to indicate the user to which the user belongs Group, the instruction information is used to instruct to delete users from the user group, or to add users to the user group; according to the instruction message, determine the monitoring event configuration information corresponding to the user group, where the monitoring event configuration information includes at least one of the following : Group member information of the user group, user monitoring event report times information; send a delete message to the second network element to instruct the second network element to delete the monitoring event configuration, where the delete message is information based on the monitoring event configuration, confirm After the event monitoring report is completed, it is sent to the second network element.
  • the indication information is used to indicate the deletion of a user from the user group, and the information of the monitoring event configuration indicates that when the report of the monitoring event configuration of the user group is counted, the report of the monitoring event corresponding to the user is excluded.
  • the instruction information is used to indicate the deletion of the user from the user group, and the number of group members of the user group is the difference between the number of group members of the currently saved user group and the number of users.
  • the instruction information is used to instruct to delete a user from a user group, and a member user of the user group is a member user of the currently saved user group to delete the user.
  • determining the monitoring event configuration information corresponding to the user group includes: deleting the number of saved user monitoring event reports, and the number of group members of the user group is the number of group members of the currently saved user group The difference with the number of users.
  • the information for determining the monitoring event configuration corresponding to the user group includes: group member information of the user group includes identification information and tag information of the user, and the tag information is used to indicate that the user group is in the statistics
  • group member information of the user group includes identification information and tag information of the user
  • tag information is used to indicate that the user group is in the statistics
  • determining the information of the monitoring event configuration corresponding to the user group includes: deleting the saved monitoring event report times of the user, and the group member information of the user group includes the identification information and tag information of the user ,
  • the marking information is used to indicate that the monitoring event report corresponding to the user should be excluded when the report of the first monitoring event configuration of the user group is counted.
  • determining the monitoring event configuration information corresponding to the user group includes: deleting the number of saved user monitoring event reports, and the member users of the user group are those of the currently saved user group The member user deletes the user.
  • determining the information of the monitoring event configuration corresponding to the user group includes: identifying the number of monitoring event reports of the user as the maximum number of reports.
  • the indication information is used to add users to the user group, and the information of the monitoring event configuration indicates the number of times of reporting the monitoring event corresponding to the user.
  • the instruction information is used to add users to the user group, and the number of group members of the user group is the sum of the number of group members of the currently saved user group and the number of users.
  • the instruction information is used to instruct to add users from a user group, and the member users of the user group add the users to the currently saved member users of the user group.
  • the indication message further includes validity indication information, which is used to indicate that the content indicated by the indication information continues to take effect.
  • an embodiment of the present application provides an event monitoring management method, including: receiving an indication message, the indication message includes the identification information of the monitoring event configuration, the identification information of the user, and the indication information, and the identification information of the monitoring event configuration is used to instruct the user For the first monitoring event configuration of the user group to which it belongs, the indication information is used to instruct to cancel the event monitoring of the user in the first monitoring event configuration; according to the indication message, cancel the event monitoring of the user in the first monitoring event configuration.
  • the instruction message further includes the event monitoring type
  • canceling the event monitoring of the user in the first monitoring event configuration includes: canceling the event monitoring of the user's event monitoring type in the first monitoring event configuration.
  • the method further includes: determining the context of the user according to the indication message, and the context of the user instructs to cancel event monitoring of the user in the first monitoring event configuration.
  • the user is marked, so that after the user is migrated to another network element, the other network element can continue to perform the management of the user's event monitoring based on the mark.
  • the method further includes: sending the user context to the fourth network element for instructing the fourth network element to cancel event monitoring of the user in the first monitoring event configuration.
  • an embodiment of the present application provides an event monitoring management method, including: receiving an indication message, the indication message includes user group identification information, user identification information and indication information, and the user group identification information is used to indicate the user group,
  • the instruction information is used to instruct to delete a user from the user group, or to instruct to add a user to the user group; if the instruction information is to instruct to delete a user from the user group, cancel the monitoring event configuration corresponding to the user group.
  • Event monitoring if the instruction information is used to indicate that users are added to the user group, start event monitoring of users in the monitoring event configuration corresponding to the user group.
  • the instruction information is used to indicate the deletion of the user from the user group
  • the method further includes: updating the user's context, and the updated user's context indicates that the user does not belong to the user group;
  • the user is marked, so that after the user is migrated to another network element, the other network element can continue to perform the management of the user's event monitoring based on the mark.
  • the indication information is used to indicate that a user is added to the user group
  • the method further includes: updating the user's context, and the updated user's context indicates that the user belongs to the user group.
  • an embodiment of the present application provides an event monitoring management method, including: receiving a first indication message, the first indication message including user group identification information, user identification information and indication information, The identification information is used to indicate the user group to which the user belongs, and the indication information is used to indicate that the user is deleted from the user group, or the user is added to the user group; based on the first indication message , Sending a second indication message to the first network element, where the second indication message includes the identification information of the monitoring event configuration and the group member information of the user group, and the identification information of the monitoring event is used to indicate the status of the user group Monitoring event configuration.
  • the group member update information is identification information of the user.
  • the group member update information is identification information of the user or the number of users in the user group.
  • the method further includes: sending a third instruction message to a third network element, where the third instruction message includes the user to which the user belongs The user group set, where the user group is not included in the user group set.
  • the method further includes: sending a third instruction message to a third network element, where the third instruction message includes the user to which the user belongs The user group set, where the user group set includes the user group.
  • an embodiment of the present application provides a device, including: a memory and a processor, the memory and the processor are coupled, the memory stores program instructions, and when the program instructions are executed by the processor, the device executes the following steps: receiving an instruction message,
  • the indication message includes the identification information of the monitoring event configuration, the identification information of the user, and the indication information.
  • the identification information of the monitoring event configuration is used to indicate the first monitoring event configuration of the user group to which the user belongs, and the indication information is used to indicate the cancellation of the first monitoring event configuration.
  • User event monitoring determine the information of the first monitoring event configuration according to the instruction message, where the information of the first monitoring event configuration includes at least one of the following: group member information of the user group, information about the number of times the user’s monitoring event is reported;
  • the second network element sends a delete message to instruct the second network element to delete the first monitoring event configuration, where the delete message is information based on the configuration of the first monitoring event, and it is determined that the first event monitoring report is completed and sent to the second network element of.
  • the information of the first monitoring event configuration indicates that the monitoring event report corresponding to the user should be excluded when the report of the first monitoring event configuration of the user group is counted.
  • the group member information of the user group includes: the number of group members of the user group is the difference between the number of group members of the currently saved user group and the number of users.
  • the group member information of the user group includes: a member user of the user group deletes the user for a currently saved member user of the user group.
  • the group member information of the user group includes identification information and tag information of the user, and the tag information is used to indicate that when the report of the first monitoring event configuration of the user group is counted, the monitoring corresponding to the user should be excluded. Incident report.
  • the device executes the following steps: delete the number of saved user monitoring event reports, and the number of group members of the user group is the group members of the currently saved user group The difference between the number and the number of users.
  • the device executes the following steps: delete the saved user's monitoring event report times, and the group member information of the user group includes the user's identification information and mark Information, marking information is used to indicate that when the report of the first monitoring event configuration of the user group is counted, the monitoring event report corresponding to the user is excluded.
  • the device executes the following steps: delete the saved user's monitoring event report times, and the member users of the user group are the currently saved user group The member user of deletes the user.
  • the device executes the following steps: the user's monitoring event report times are set to the maximum report times, that is, the user's report is completed by default.
  • the indication message further includes event monitoring type information, and the indication information is used to instruct to cancel the first event monitoring of the user in the first event monitoring configuration, wherein the event monitoring type information Indicates the event monitoring type of the first event monitoring.
  • the information of the first monitoring event configuration indicates that when the report of the first monitoring event configuration of the user group is counted, the monitoring event report of the first event monitoring corresponding to the user is excluded.
  • the device executes the following steps: the user's monitoring event report times are set to the maximum report times, that is, the user's report is completed by default.
  • the indication message further includes validity indication information, which is used to indicate that the content indicated by the indication information continues to take effect.
  • an embodiment of the present application provides a device including: a memory and a processor, the memory and the processor are coupled, the memory stores program instructions, and when the program instructions are executed by the processor, the device executes the following steps: receiving an instruction message,
  • the instruction message includes the identification information of the user group, the identification information of the user, and the instruction information.
  • the identification information of the user group is used to indicate the user group to which the user belongs, and the instruction information is used to indicate the deletion of the user from the user group or the addition of the user to the user group.
  • the instruction message determine the monitoring event configuration information corresponding to the user group, where the monitoring event configuration information includes at least one of the following: group member information of the user group, user monitoring event report times information; sending to the second network element
  • the delete message is used to instruct the second network element to delete the monitoring event configuration, where the delete message is information based on the monitoring event configuration and is sent to the second network element after the event monitoring report is determined to be completed.
  • the indication information is used to indicate the deletion of a user from the user group, and the information of the monitoring event configuration indicates that when the report of the monitoring event configuration of the user group is counted, the report of the monitoring event corresponding to the user is excluded.
  • the instruction information is used to indicate the deletion of the user from the user group, and the number of group members of the user group is the difference between the number of group members of the currently saved user group and the number of users.
  • the instruction information is used to instruct to delete a user from a user group, and a member user of the user group is a member user of the currently saved user group to delete the user.
  • the device executes the following steps: delete the number of saved user monitoring event reports, and the number of group members of the user group is the group members of the currently saved user group The difference between the number and the number of users.
  • the group member information of the user group includes identification information and tag information of the user, and the tag information is used to indicate that when the report of the first monitoring event configuration of the user group is counted, the monitoring corresponding to the user should be excluded. Incident report.
  • the device executes the following steps: delete the saved user's monitoring event report times, and the group member information of the user group includes the user's identification information and mark Information, marking information is used to indicate that when the report of the first monitoring event configuration of the user group is counted, the monitoring event report corresponding to the user is excluded.
  • the device executes the following steps: delete the saved user's monitoring event report times, and the member users of the user group are the currently saved user group The member user of deletes the user.
  • the device executes the following steps: the user's monitoring event report times are identified as the maximum report times.
  • the indication information is used to add users to the user group, and the information of the monitoring event configuration indicates the number of times of reporting the monitoring event corresponding to the user.
  • the instruction information is used to add users to the user group, and the number of group members of the user group is the sum of the number of group members of the currently saved user group and the number of users.
  • the instruction information is used to add users to the user group, and the member users of the user group add the users to the currently saved member users of the user group.
  • the indication message further includes validity indication information, which is used to indicate that the content indicated by the indication information continues to take effect.
  • an embodiment of the present application provides a device, including: a memory and a processor, the memory and the processor are coupled, the memory stores program instructions, and when the program instructions are executed by the processor, the device executes the following steps: receiving an instruction message,
  • the indication message includes the identification information of the monitoring event configuration, the identification information of the user, and the indication information.
  • the identification information of the monitoring event configuration is used to indicate the first monitoring event configuration of the user group to which the user belongs, and the indication information is used to indicate the cancellation of the first monitoring event configuration.
  • User's event monitoring according to the instruction message, cancel the user's event monitoring in the first monitoring event configuration.
  • the indication message also includes the event monitoring type.
  • the device executes the following steps: cancel the event monitoring of the user's event monitoring type in the first monitoring event configuration.
  • the device executes the following steps: determining the user's context according to the instruction message, and the user's context instructs to cancel the event monitoring of the user in the first monitoring event configuration.
  • the device executes the following steps: sending the user's context to the fourth network element for instructing the fourth network element to cancel the configuration of the first monitoring event for the user Event monitoring.
  • an embodiment of the present application provides a device, including: a memory and a processor, the memory and the processor are coupled, and the memory stores program instructions.
  • the device executes the following steps: receiving an instruction message,
  • the instruction message includes the identification information of the user group, the identification information of the user, and the instruction information.
  • the identification information of the user group is used to indicate the user group, and the instruction information is used to indicate to delete the user from the user group, or to indicate to add to the user group.
  • the instruction information is used to indicate the deletion of a user from the user group.
  • the device executes the following steps: update the user's context, and the updated user's context indicates that the user does not belong to user group;
  • the indication information is used to indicate the addition of users to the user group.
  • the device executes the following steps: update the user context, and the updated user context indicates that the user belongs to the user Group.
  • an embodiment of the present application provides a device, a memory and a processor, the memory and the processor are coupled, the memory stores program instructions, and when the program instructions are executed by the processor, the device executes the following steps: receiving a first instruction message,
  • the first indication message includes identification information of the user group, identification information of the user, and indication information.
  • the identification information of the user group is used to indicate the user group to which the user belongs, and the indication information is used to indicate that the user group is from the user group.
  • the group member update information is identification information of the user.
  • the group member update information is identification information of the user or the number of users in the user group.
  • the device executes the following steps: sending a third instruction message to a third network element, and the first The third indication message includes the user group set to which the user belongs, wherein the user group is not included in the user group set.
  • the device executes the following steps: sending a third instruction message to a third network element, and the first The third indication message includes the user group set to which the user belongs, wherein the user group set includes the user group.
  • an embodiment of the present application provides a device that includes a transceiver module, a processing module, and a transceiver module for receiving an indication message, the indication message including the identification information of the monitoring event configuration, the identification information of the user, and the indication information
  • the identification information of the monitoring event configuration is used to indicate the first monitoring event configuration of the user group to which the user belongs, and the indication information is used to instruct to cancel the event monitoring of the user in the first monitoring event configuration
  • processing module Configured to determine information about the configuration of the first monitoring event according to the instruction message, where the information about the configuration of the first monitoring event includes at least one of the following: group member information of the user group, and information about the user Information about the number of monitoring event reports
  • the transceiver module is also used to send a delete message to the second network element for instructing the second network element to delete the first monitoring event configuration, wherein the delete message is based on the first monitoring event configuration
  • a monitoring event configuration information is sent to the second network element after it is determined that the monitoring report of the first
  • an embodiment of the present application provides a device that includes: a transceiver module, a processing module, and a transceiver module for receiving an instruction message, the instruction message including user group identification information, user identification information, and instruction information,
  • the identification information of the user group is used to indicate the user group to which the user belongs, and the indication information is used to indicate that the user is deleted from the user group, or the user is added to the user group;
  • processing module Used to determine the monitoring event configuration information corresponding to the user group according to the instruction message, wherein the monitoring event configuration information includes at least one of the following: group member information of the user group, and information about the user Information on the number of monitoring event reports;
  • the transceiver module is also used to send a delete message to the second network element for instructing the second network element to delete the monitoring event configuration, wherein the delete message is based on the monitoring event configuration The information is determined to be sent to the second network element after the event monitoring report is completed.
  • an embodiment of the present application provides a device that includes: a transceiver module, a processing module, and a transceiver module for receiving an indication message, the indication message including identification information for monitoring event configuration, user identification information, and indication information
  • the identification information of the monitoring event configuration is used to indicate the first monitoring event configuration of the user group to which the user belongs, and the indication information is used to instruct to cancel the event monitoring of the user in the first monitoring event configuration; processing module , Used to cancel the user's event in the first monitoring event configuration according to the instruction message.
  • an embodiment of the present application provides a device, including: a transceiver module, a processing module, and a transceiver module for receiving an instruction message, the instruction message including user group identification information, user identification information, and instruction information,
  • the identification information of the user group is used to indicate a user group, and the indication information is used to indicate to delete the user from the user group, or to indicate to add the user to the user group;
  • a processing module If the instruction information is used to instruct to delete the user from the user group, cancel the event monitoring of the user in the monitoring event configuration corresponding to the user group; if the instruction information is used to indicate that the user is in The user is added to the user group, and event monitoring of the user is started in the monitoring event configuration corresponding to the user group.
  • an embodiment of the present application provides a device, including a transceiver module, configured to receive a first indication message, where the first indication message includes identification information of a user group, identification information of a user, and indication information, and the user
  • the group identification information is used to indicate the user group to which the user belongs, and the indication information is used to indicate that the user is deleted from the user group, or the user is added to the user group;
  • the transceiver module also uses Based on the first indication message, sending a second indication message to the first network element, where the second indication message includes the identification information of the monitoring event configuration and the group member information of the user group, and the identification information of the monitoring event Used to indicate the monitoring event configuration of the user group.
  • an embodiment of the present application provides an event monitoring management system, including an application server, a first network element, a second network element, and a third network element; the application server is used to send a first instruction to the first network element
  • the first indication message includes the identification information of the monitoring event configuration, the identification information of the user, and the indication information.
  • the identification information of the monitoring event configuration is used to indicate the first monitoring event configuration of the user group to which the user belongs, and the indication information is used to instruct to cancel the first monitoring event configuration.
  • the first network element is used to determine the information of the first monitoring event configuration based on the first indication message, where the information of the first monitoring event configuration includes at least one of the following: user group group Member information, information on the number of times the user’s monitoring event is reported; the first network element is used to send a second indication message to the second network element, the second indication message including the identification information of the monitoring event configuration, the user’s identification information and the indication information; The second network element is used to send a second indication message to the third network element, which is used to instruct the third network element to cancel the event monitoring of the user in the first monitoring event configuration; the third network element is used to cancel the event monitoring based on the second indication message The user’s event monitoring in the first monitoring event configuration; the first network element is also used to send a delete message to the second network element for instructing the second network element to delete the first monitoring event configuration, where the delete message is based on the first Monitoring event configuration information is determined to be sent to the second network element after the first event monitoring report is completed
  • an embodiment of the present application provides an event monitoring management system, which is characterized in that it includes an application server, a first network element, a second network element, and a third network element; Send a first instruction message, the first instruction message includes the identification information of the user group, the identification information of the user, and the instruction information.
  • the identification information of the user group is used to indicate the user group to which the user belongs, and the instruction information is used to indicate the deletion of the user from the user group, Or, add users to the user group;
  • the first network element is used to determine the monitoring event configuration information corresponding to the user group according to the first indication message, where the monitoring event configuration information includes at least one of the following: the group of the user group Member information, user monitoring event reporting times information;
  • the first network element is used to send a second indication message to the second network element, the second indication message includes the identification information of the user group, the identification information of the user and the indication information;
  • the second The network element is used to send a second indication message to the third network element, which is used to indicate to delete a user from the user group, or to indicate to add a user to the user group;
  • the third network element is used to indicate if the indication information is used Instruct to delete a user from the user group and cancel the event monitoring of the user in the monitoring event configuration corresponding to the user group; if the instruction information is
  • an embodiment of the present application provides a computer-readable medium for storing a computer program, and the computer program includes instructions for executing the method in any one of the first to fifth aspects.
  • an embodiment of the present application provides a computer program, which includes instructions for executing the method in any one of the first to fifth aspects.
  • an embodiment of the present application provides a chip, which includes a processing circuit and transceiver pins.
  • the transceiver pin and the processing circuit communicate with each other through an internal connection path, and the processing circuit executes the method in any one of the first aspect to the fifth aspect to control the receiving pin to receive signals, and to control the transmitting tube The pin sends a signal.
  • Fig. 1 is a schematic structural diagram showing an exemplary service capability opening
  • Fig. 2 is a schematic structural diagram showing an exemplary service capability opening
  • Fig. 3 is a schematic diagram of a configuration flow diagram of a monitoring event shown by way of example
  • FIG. 4 is a schematic diagram of a monitoring process of a monitoring event shown by way of example
  • FIG. 5 is a schematic diagram of a configuration flow diagram of a monitoring event shown by way of example
  • FIG. 6 is a schematic diagram of a monitoring process of a monitoring event shown by way of example
  • FIG. 7 is a schematic diagram of an exemplary management process of monitoring events
  • FIG. 8 is a schematic diagram of an exemplary management process of monitoring events
  • FIG. 9 is a schematic flowchart of an event monitoring management method provided by an embodiment of the present application.
  • FIG. 10 is a schematic flowchart of an event monitoring management method provided by an embodiment of the present application.
  • FIG. 11 is a schematic flowchart of an event monitoring management method provided by an embodiment of the present application.
  • FIG. 12 is a schematic flowchart of an event monitoring management method provided by an embodiment of the present application.
  • FIG. 13 is a schematic flowchart of an event monitoring management method provided by an embodiment of the present application.
  • FIG. 14 is a schematic flowchart of an event monitoring and management method provided by an embodiment of the present application.
  • FIG. 15 is a schematic structural diagram of a network element provided by an embodiment of the present application.
  • FIG. 16 is a schematic structural diagram of a device provided by an embodiment of the present application.
  • first and second in the description and claims of the embodiments of the present application are used to distinguish different objects, rather than to describe a specific order of objects.
  • first target object and the second target object are used to distinguish different target objects, rather than to describe the specific order of the target objects.
  • words such as “exemplary” or “for example” are used as examples, illustrations, or illustrations. Any embodiment or design solution described as “exemplary” or “for example” in the embodiments of the present application should not be construed as being more preferable or advantageous than other embodiments or design solutions. To be precise, words such as “exemplary” or “for example” are used to present related concepts in a specific manner.
  • multiple processing units refer to two or more processing units; multiple systems refer to two or more systems.
  • the users involved in the embodiments of this application may also be referred to as user equipment (UE) or terminal, and may also be referred to as mobile station, subscriber unit, station, terminal equipment ( terminal equipment, TE), etc.
  • the terminal can be a cellular phone, a personal digital assistant (PDA), a wireless modem (modem), a handheld device, a laptop computer, a cordless phone, and a wireless Local loop (wireless local loop, WLL) station, tablet computer (pad), etc.
  • PDA personal digital assistant
  • modem wireless modem
  • WLL wireless Local loop station
  • pad tablet computer
  • devices that can access the communication system, communicate with the network side of the communication system, or communicate with other objects through the communication system can all be the users in the embodiments of the present application, for example, intelligent transportation Terminals and cars in smart homes, household equipment in smart homes, power meter reading equipment in smart grids, voltage monitoring equipment, environmental monitoring equipment, video monitoring equipment in smart security networks, cash registers, etc.
  • FIG. 1 shows the architecture diagram of service capability opening in the 4th generation mobile communication technology (4G) network.
  • the architecture includes a service capability server (Services Capability Server, SCS)/ Application Server (AS), Service Capability Exposure Function (SCEF), Home Subscriber Server (HSS), Mobile Management Entity (MME) and Serving GPRS Support Node (Serving) GPRS (General Packet Radio Service, General Packet Radio Service) Support Node, SGSN).
  • SCS Service Capability Server
  • AS Service Capability Exposure Function
  • HSS Home Subscriber Server
  • MME Mobile Management Entity
  • Serving GPRS Support Node Serving GPRS Support Node
  • GPRS General Packet Radio Service, General Packet Radio Service
  • SGSN Serving GPRS Support Node
  • a service capability server Service Capability Server, SCS
  • AS application server
  • SCEF is the core network element in this architecture, which enables the network to safely provide service capabilities to SCS/AS.
  • HSS is the home user subscription server, which is used to save the user's subscription information.
  • the MME and the SGSN are network elements responsible for the mobility management of the UE.
  • SCS/AS calls the service capabilities provided by SCEF through the T8 API interface.
  • FIG 2 shows the architecture diagram of service capability opening in the 5th generation mobile communication technology (5G) network.
  • the architecture includes application functions (AF) and network opening Functions (Network Exposure Function, NEF) Unified Data Management (Unified Data Management, UDM), Core Access and Mobility Management Function (AMF), Session Management Function (SMF).
  • AF application functions
  • NEF Network Exposure Function
  • UDM Unified Data Management
  • AMF Core Access and Mobility Management Function
  • SMF Session Management Function
  • NEF is similar to the function of SCEF in 4G, and can provide necessary services and capabilities to AF.
  • UDM is similar to the function of HSS and can provide related services and capabilities to NEF.
  • AMF/SMF is similar to the functions of MME/SGSN and can provide supported services and capabilities to NEF.
  • Fig. 3 is a schematic diagram of the configuration process of the monitoring event shown by way of example. With reference to Fig. 3, the details are as follows:
  • Step 101 SCS/AS sends a monitoring request message to SCEF.
  • the SCS/AS sends a monitoring request message to the SCEF, which is used to instruct the SCEF to configure event monitoring of the user group.
  • the monitoring request message includes but is not limited to: monitoring Type information, External Group ID, T8 Long Term Transaction Reference ID (TLTRI), SCS/AS Identification information, T8 destination address information.
  • monitoring Type information External Group ID
  • T8 Long Term Transaction Reference ID T8
  • SCS/AS Identification information T8 destination address information.
  • the monitoring type information may also be referred to as event monitoring type information, which refers to the type of event monitoring that needs to be performed on the user group, and can also be understood as the specific type of event monitoring performed on the user group.
  • the monitoring request message may carry one or more event monitoring type information, which is used to indicate to monitor one or more specified types of monitoring events of the user group.
  • the event monitoring type can be Loss of Connectivity and UE reachability.
  • the External Group ID is used to indicate the user group, and the SCS/AS and SCEF can identify the corresponding user group based on the ID. It should be noted that the user group has been configured in advance, and the user group may include one or more users. The specific configuration process will not be repeated in this application.
  • TLTRI is used to indicate the monitoring event configuration
  • SCS/AS and SCEF can query the corresponding monitoring event configuration based on TLTRI.
  • UE1 belongs to user group 1 and user group 2, and user group 1 corresponds to monitoring event configuration 1 (TLTRI1), which is configured to monitor the Loss of connectivity monitoring event of user group 1, that is, the event monitoring type of monitoring event configuration 1 is Loss of connectivity;
  • TLTRI2 monitoring event configuration 2
  • TLTRI13 monitoring event configuration 3
  • TLTRI13 monitoring event configuration 3
  • the monitoring request message may also include at least one of the following: the maximum number of reports and the monitoring duration.
  • the monitoring duration is used to indicate the monitoring duration of event monitoring by the user group, that is, when the monitoring duration is reached, it can be determined that the report of the monitoring event configuration is completed, and the network will no longer perform the corresponding monitoring event configuration. monitor.
  • the maximum number of reports is used to indicate the maximum number of reports that each user in the monitoring event configuration can report, that is, when each user in the user group has a report corresponding to the monitoring event configuration reaches the maximum report If the number of times, it is determined that the report of the monitoring event configuration is completed, and the monitoring of the monitoring event configuration is no longer monitored.
  • User group 1 includes 3 users.
  • the maximum number of reports can also be used to indicate the maximum number of reports that can be reported for each monitoring type of each user in the monitoring event configuration. That is to say, in a monitoring event configuration, when each user in the user group When each monitoring type report reaches the maximum number of reports, it is determined that the report of the monitoring event configuration is completed, and the monitoring event configuration is no longer monitored.
  • a single user group can correspond to multiple monitoring event configurations. Therefore, the configuration parameters carried in the monitoring request message are only valid for the monitoring event configuration indicated this time.
  • the monitoring request message neither carries the maximum number of reports nor the monitoring duration, it means that the monitoring request is a monitoring request, or can be understood as a temporary monitoring request.
  • Step 102 The SCEF determines the information of the monitoring event configuration based on the monitoring request.
  • the SCEF after receiving the monitoring request, the SCEF obtains and saves the parameters carried in it. And, SCEF authorizes the monitoring request based on various parameters, and authorization can be understood as confirming whether the monitoring request is valid, that is, whether the operator's strategy and contract are satisfied.
  • SCEF Reference ID is the identification information allocated by SCEF for the monitoring event configuration based on TLTRI.
  • SCEF saves the correspondence between SCEF Reference ID and TLTRI.
  • Step 103 The SCEF sends a monitoring request message to the HSS.
  • the SCEF sends a monitoring request message to the HSS, which is used to instruct the HSS to configure the monitoring event configuration accordingly, which can also be understood as information instructing the HSS to determine the monitoring event configuration.
  • the monitoring request message includes but is not limited to: External Group ID, SCEF identification information, SCEF Reference ID, and Monitoring Type.
  • the monitoring request message may also include some or all of the parameters in the monitoring request message in step 101, for example, it may include SCS/AS identification information, T8 destination address information, etc., which is not limited in this application.
  • Step 104 The HSS determines the information of the monitoring event configuration based on the monitoring request message.
  • the HSS receives the monitoring request message and obtains the parameters carried in the monitoring request message. Based on the acquired parameters, the HSS checks whether the monitoring request message meets the network policy, and after checking that the monitoring request message meets the network policy, saves the monitoring request message For each parameter in, create the monitoring event configuration (that is, the information that determines the monitoring event configuration).
  • the HSS stores the subscription information, and the HSS can match the subscription information based on the External Group ID, and determine the corresponding user group and the group members included in it.
  • the HSS stores subscription information
  • the subscription information includes, but is not limited to: the correspondence between users and user groups.
  • HSS can retrieve the corresponding user group based on the External Group ID, and obtain multiple users in the user group. Specifically, it obtains the user identification information corresponding to each user.
  • the user identification information can be the user's external identification or mobile User International Integrated Services Digital Network Number (Mobile Subscriber International ISDN number, MSISDN).
  • the HSS also saves the correspondence between each user and the MME.
  • the architecture may include multiple MMEs, and the MME corresponding to each user in the user group may be the same or different, which is not limited in this application.
  • Step 105 HSS sends a confirmation message to SCEF.
  • the HSS sends a confirmation message to the SCEF, and the message carries the SCEF Reference ID, acceptance indication information, and the number of group members in the user group or the user identification information of the group members in the user group.
  • the acceptance indication information is used to instruct the HSS to accept the monitoring request message carrying the SCEF Reference ID sent by the SCEF, and it can also be understood that the HSS has completed the configuration of event monitoring corresponding to the SCEF Reference ID.
  • Step 106 SCEF sends a confirmation message to SCS/AS.
  • the monitoring event configuration information may include the monitoring event configuration information of the user group and the monitoring event of the group member user.
  • Configuration information among them, the monitoring event configuration information of the user group includes event monitoring type, External Group ID, SCS/AS identification information, T8 destination address information, SCEF Reference ID and TLTRI, and group member user monitoring event configuration
  • the information includes the group member information of the user group (for example, the number of group members or the group member identification list) and the subsequent reported times of each group member user.
  • the monitoring event configuration information of the user group also includes but is not limited to at least one of the following: maximum number of reports, monitoring duration, etc.
  • SCEF sends a confirmation message to SCS/AS, the message includes but is not limited to: acceptance indication information and TLTRI.
  • the acceptance indication information is used to indicate that SCEF has completed the configuration of event monitoring corresponding to TLTRI.
  • step 105 to step 106 can also be performed after step 109, which is not limited in this application.
  • Step 107 The HSS sends a request message for inserting subscriber data to the MME/SGSN.
  • the HSS may obtain the users in the user group and their corresponding user identification information.
  • the HSS sends an Insert Subscriber Data Request (Insert Subscriber Data Request) message to the MME/SGSN corresponding to the user for each user, that is, for each user in the user group, the HSS repeats step 107 to step 109.
  • Insert Subscriber Data Request Insert Subscriber Data Request
  • the HSS sends a subscriber data insertion request message to the MME/SGSN corresponding to the user for a single user, which is used to instruct the MME/SGSN to perform event monitoring on the user.
  • the message includes but is not limited to: Monitoring type, SCEF identification information, SCEF Reference ID, maximum number of reports and/or monitoring duration, user's external identification or MSISDN.
  • step 108 the MME/SGSN performs event monitoring.
  • the MME/SGSN receives the subscriber data insertion request message sent by the HSS, and obtains the parameters carried by it.
  • MME/SGSN determines the user's monitoring event configuration information, including: SCEF identification information, SCEF Reference ID, Monitoring type, user's external identification or MSISDN, maximum number of reports and/or monitoring duration.
  • each MME/SGSN can perform event monitoring on each user in the monitoring event configuration corresponding to the user group according to the inserted subscriber data request message.
  • each user can correspond to a different user group, and each user group can correspond to a different monitoring event configuration. That is to say, if you want to configure different monitoring events for the user group, repeat steps 101 to 108 That is, different event monitoring of the same user group corresponds to different monitoring event configuration information, for example: corresponding to different TLTRI and SCEF Reference ID.
  • Step 109 The MME/SGSN sends a subscriber data insertion response message to the HSS.
  • the MME/SGSN After the MME/SGSN successfully configures the monitoring event, it sends an insert subscriber data response message to the HHS.
  • the message carries the acceptance indication information, which is used to indicate that the MME/SGSN successfully performs the monitoring event configuration.
  • the HSS is executed for each user from step 107 to step 109. Therefore, the insert subscriber data response message sent by the MME/SGSN may not carry the user identification information, and the HSS can learn the currently received insert subscriber subscription The data response message is for the current user.
  • Fig. 4 is a schematic diagram of the reporting process of an exemplary monitoring event, referring to Fig. 4, specifically:
  • Step 201 MME/SGSN detects a monitoring event.
  • the MME/SGSN performs event monitoring on the user in the monitoring event configuration.
  • the MME/SGSN detects the user's monitoring event.
  • Step 202 The MME/SGSN sends a monitoring indication message to the SCEF.
  • the MME/SGSN after detecting the monitoring event of the user, the MME/SGSN sends a monitoring indication message to the SCEF to indicate that the user has a monitoring event.
  • the message includes but is not limited to: SCEF Reference ID, monitoring event report, and user identification information, which are used to indicate that in the monitoring event configuration corresponding to the SCEF Reference ID, the user corresponding to the user identification information has a monitoring event.
  • Event reports include, but are not limited to, the types of monitoring events.
  • MME/SGSN detects that user 1 has a Loss of connectivity monitoring event, MME/SGSN sends a monitoring indication message to SCEF, the message carries user 1’s user identification information, for example, user 1’s user external identity, and also carries SCEF Reference ID1 corresponding to monitoring event configuration 1, and monitoring event report.
  • the MME/SGSN may store the remaining report times corresponding to the monitoring event configuration, that is, when the monitoring event configuration is successful, the remaining report times are set to the value of the maximum report times. If the MME/SGSN reports once To monitor event reports, reduce the number of remaining reports by 1. Exemplarily, if the number of remaining reports is 0, the MME/SGSN deletes the locally stored information about the user's monitoring event configuration, that is, the MME/SGSN stops performing event monitoring on the user in the monitoring event configuration.
  • the monitoring event is configured as one-time event monitoring
  • the MME/SGSN sends a monitoring indication message to the SCEF
  • the user's monitoring event configuration information is deleted.
  • Step 203 SCEF processing.
  • the SCEF saves the number of reported events corresponding to the user.
  • SCEF determines that the reporting of the monitoring event configuration is complete, and deletes the monitoring event corresponding to the user group that has reached the maximum number of monitoring times Configure and instruct HSS to delete the monitoring event configuration.
  • SCEF determines that the reporting of the monitoring event configuration is complete, and deletes the corresponding maximum number of events for the user group.
  • the monitoring event configuration corresponding to the monitoring times, and instructing the HSS to delete the monitoring event configuration.
  • Step 204 SCEF sends a monitoring instruction message to SCS/AS.
  • the SCEF sends a monitoring indication message to the SCS/AS to indicate that the user has a monitoring event.
  • the message includes but is not limited to: TLTRI, monitoring event report, and user identification information.
  • TLTRI is found by SCEF based on SCEF Reference ID.
  • SCEF may aggregate multiple event reports from MME/SGSN, SCEF may carry an event report list in a monitoring indication message, and the list includes the correspondence between TLTRI, monitoring event report, and user identification information.
  • Step 205 SCS/AS returns a confirmation message to SCEF.
  • the configuration process of monitoring events based on the business capability opening architecture of the 5G network is also called the monitoring event subscription (Monitoring Event Subscription) process, and the monitoring request is also called the monitoring event subscription request (Event Subscription Request). ), the monitoring type information is also called Event Id.
  • Fig. 5 is a schematic diagram of an exemplary subscription process of monitoring events, referring to Fig. 5, specifically:
  • Step 301 AF sends a monitoring event subscription request message to NEF.
  • the AF sends a monitoring event subscription request message to the NEF, which is used to instruct to configure the monitoring event of the user group (also referred to as performing monitoring event subscription).
  • the monitoring event subscription request message includes but is not limited to: AF notification endpoint, event identifier, and External Group ID.
  • the notification endpoint of the AF is the identification information allocated by the AF for the monitoring event subscription, and the subsequent NEF sends an event report to the AF to carry the notification endpoint for the associated monitoring event subscription.
  • the notification endpoint of the AF may be target notification address information, or target notification address information and notification association identification information.
  • event identifiers carried in the message may correspond to one or more event identifiers.
  • the monitoring event subscription message may also carry a monitoring event report mode, which is used to indicate the maximum number of reports of the monitoring event, the periodic reporting mode, or the monitoring duration.
  • a monitoring event report mode which is used to indicate the maximum number of reports of the monitoring event, the periodic reporting mode, or the monitoring duration.
  • step 101 please refer to step 101, which will not be repeated here.
  • Step 302 NEF determines monitoring event subscription information based on the monitoring event subscription request message.
  • the monitoring event subscription is authorized, and the parameters in the monitoring event subscription request message are saved.
  • step 102 Other details are similar to step 102, and will not be repeated here.
  • Step 303 NEF sends a monitoring event subscription request message to UDM.
  • NEF sends a monitoring event subscription request message to UDM for monitoring event subscription.
  • the monitoring event subscription request message includes but is not limited to: External Group ID, event identifier, NEF notification endpoint, etc.
  • the message may also include some or all of the parameters in step 301.
  • the notification endpoint of the NEF is the identification information allocated by the NEF for the event monitoring configuration and the subsequent event report is sent to the NEF to carry the notification endpoint for the associated monitoring event subscription.
  • step 304 the UDM creates a monitoring event subscription based on the monitoring event subscription request message.
  • UDM checks whether the monitoring event subscription request message sent by NEF meets the network policy, and after checking that the monitoring event subscription request message meets the network policy, saves the parameters in the monitoring event subscription request message to create a monitoring event subscription. It is understood as the information that determines the monitoring event subscription, where the monitoring event subscription information is the saved parameters, including but not limited to: External Group ID, event identifier, NEF notification endpoint, etc.
  • the UDM can find the internal group ID corresponding to the External Group ID based on the locally stored subscription information, and find the corresponding group member and the external ID or MSISDN of the user of each group member based on the internal group ID. And, the UDM determines the AMF or SMF corresponding to the user in the serving user group, and the UDM performs step 305a or step 305b to the AMF or SMF of each user in the serving user group.
  • step 305a the UDM sends the AMF monitoring event subscription request message.
  • the UDM sends a monitoring event subscription request message to the AMF, which is used to instruct the AMF to perform event monitoring on the member users of the user group.
  • the message may include NEF notification endpoint, internal group identification information, and event identification.
  • the message may also include some optional parameters in step 301.
  • NEF notification endpoint NEF notification endpoint
  • internal group identification information NEF notification endpoint
  • event identification NEF notification endpoint
  • the message may also include some optional parameters in step 301.
  • step 306a the AMF returns a confirmation message.
  • the AMF determines the monitoring event subscription information based on the parameters in the monitoring event subscription request message.
  • the monitoring event subscription information may include the monitoring event subscription information of the user group and the monitoring event subscription information of each group member user.
  • the monitoring event subscription information of the user group includes: AMF subscription associated identification, NEF notification endpoint, event monitoring mode, event monitoring type information, etc.
  • the information of the monitoring event subscription of the group member users includes: the remaining number of reports (the initial value is set according to the maximum number of reports) and so on.
  • the monitoring event subscription information of the user group can be written into the context of the user group, and the user monitoring event subscription information can be written into the user's context.
  • AMF Based on the information of the monitoring event subscription, AMF performs event monitoring on the user and sends a confirmation message to UDM.
  • the message includes the AMF subscription associated identifier.
  • UDM writes the AMF subscription association representation into the information of the monitoring event subscription.
  • Step 305b UDM sends a monitoring event subscription request message to SMF.
  • step 305a It is similar to step 305a and will not be repeated here.
  • step 306b the SMF returns a confirmation message.
  • the SMF determines the monitoring event subscription information based on the parameters in the monitoring event subscription request message.
  • the information for monitoring event subscriptions includes but is not limited to: event monitoring mode, SMF subscription correlation identification, NEF notification endpoint, event monitoring type information, etc.
  • the SMF subscription association identifier is the identifier allocated by the SMF for the monitoring event subscription.
  • SMF performs event monitoring on users and sends a confirmation message to UDM.
  • the message includes the SMF subscription association identifier.
  • UDM writes the SMF subscription association representation into the user's monitoring event subscription information.
  • step 306a Other details are similar to step 306a, and will not be repeated here.
  • Step 307 UDM sends a confirmation message to NEF.
  • UDM sends a confirmation message to NEF.
  • the confirmation message includes but is not limited to: acceptance instruction information, UDM subscription association identification, user group The number of member users or a list of identities of group member users.
  • step 105 please refer to step 105, which will not be repeated here.
  • Step 308 NEF sends a confirmation message to SCS/AS.
  • the NEF determines the information of the monitoring event subscription based on the confirmation message.
  • the monitoring event subscription information may include, but is not limited to: user group monitoring event subscription information and member user monitoring event subscription information.
  • the monitoring event subscription information of the user group includes AF notification endpoints, event identifiers, External Group ID, NEF notification endpoints, UDM subscription correlation identifiers, and event monitoring report mode.
  • Group member users’ monitoring event subscription information includes Group member information (such as the number of group members or a list of group member identifications) and the subsequent reported times of each group member user.
  • the monitoring event configuration information of the user group also includes but is not limited to at least one of the following: maximum number of reports, monitoring duration, etc.
  • the NEF sends a confirmation message to the SCS/AS, and the message carries the acceptance indication information and the NEF subscription association identifier to instruct the NEF to complete the monitoring event subscription.
  • Fig. 6 is a schematic diagram of an exemplary monitoring process of event monitoring, referring to Fig. 6, specifically:
  • step 401a the AMF detects a monitoring event.
  • step 201 The specific details are similar to step 201, and will not be repeated here.
  • Step 402a AMF sends an event notification message to NEF.
  • the AMF After the AMF detects the monitoring event, it sends an event notification message to the NEF.
  • the message includes the notification endpoint of the NEF, the monitoring event report, and the user's external identification information.
  • the AMF subtracts 1 from the remaining number of reports in the information subscribed to by the user's monitoring event.
  • step 202 Other details are similar to step 202, and will not be repeated here.
  • Step 403a NEF sends a confirmation message to AMF.
  • the NEF sends a confirmation message to the AMF to indicate that the event notification message sent by the AMF is received.
  • step 401b the SMF detects a monitoring event.
  • step 201 The specific details are similar to step 201, and will not be repeated here.
  • Step 402b SMF sends an event notification message to NEF.
  • the SMF after detecting the monitoring event, the SMF sends an event notification message to the NEF.
  • the message includes the notification endpoint of the NEF, the monitoring event report, and the user's external identification information.
  • SMF subtracts 1 from the remaining number of reports in the information subscribed to by the user's monitoring event.
  • step 202 Other details are similar to step 202, and will not be repeated here.
  • Step 403b NEF sends a confirmation message to SMF.
  • the NEF sends a confirmation message to the SMF to indicate that the monitoring instruction message sent by the SMF is received.
  • Step 404 NEF processing.
  • the NEF after receiving the AMF or SMF event notification message, the NEF saves the number of reported events corresponding to the user.
  • NEF determines that the report of the monitoring event subscription is completed, deletes the monitoring event subscription, and instructs UDM to delete the Monitor event subscriptions.
  • NEF determines that the report of the monitoring event subscription is completed, deletes the monitoring event subscription, and instructs UDM Delete the monitoring event subscription.
  • step 405 the NEF sends an event notification message to the AF.
  • the NEF sends an event notification message to the AF to indicate that the user has a monitoring event.
  • the message carries the AF notification endpoint, monitoring event report, and the user's external identification information.
  • step 204 please refer to step 204, which will not be repeated here.
  • Step 406 AF returns a confirmation message to NEF.
  • Fig. 7 is a schematic diagram of an exemplary management process of event monitoring, referring to Fig. 7, specifically:
  • step 501 the SCS/AS sends a monitoring request message to the SCEF.
  • SCE/AS sends a monitoring request message to SCEF.
  • the message carries TLTRI and delete indication information, which is used to instruct to cancel (delete) the monitoring event configuration corresponding to TLTRI. It can also be understood as one or more corresponding user groups.
  • the monitoring event configuration corresponding to TLTRI in the monitoring event configuration is deleted, that is, the user group is no longer monitored for the monitoring event configuration.
  • step 502 the SCEF sends a monitoring request message to the HSS.
  • the SCEF can determine the corresponding SCEF Reference ID based on TLTRI, and the SCEF sends a monitoring request message to the HSS, and the message carries the SCEF Reference ID and deletion indication information.
  • Step 503 The HSS determines the monitoring event configuration that needs to be deleted according to the SCEF Reference ID.
  • the HSS stores one or more monitoring event configuration information, and the HSS can find the corresponding monitoring event configuration information based on the SCEF Reference ID, and obtain the users in the corresponding user group.
  • Step 504 HSS sends a confirmation message to SCEF.
  • the HSS sends a confirmation message to the SCEF to indicate that the monitoring request message sent by the SCEF has been received.
  • Step 505 SCEF sends a confirmation message to SCS/AS.
  • the SCEF sends a confirmation message to the SCS/AS to indicate that the monitoring request message sent by the SCS/AS has been received.
  • Step 506 The HSS sends a request message for inserting subscriber data to the MME/SGSN.
  • the HSS determines the user corresponding to the monitoring event configuration, it repeats step 506 for each user, where the request message for inserting subscriber data includes, but is not limited to: SCEF Reference ID, user identification information (for example, the user’s external Identification information) and delete instruction information.
  • step 507 the MME/SGSN deletes the information of monitoring event configuration according to the request message for inserting subscriber data.
  • the MME/SGSN determines the monitoring event configuration according to the SCEF Reference ID inserted in the subscriber data request message, and deletes the monitoring event configuration of the user corresponding to the user identification information in the monitoring event configuration.
  • step 508 the MME/SGSN sends a subscriber data insertion response message to the HSS.
  • the MME/SGSN After the MME/SGSN performs the operation of deleting the monitoring event configuration on the user, it sends an insert subscriber data response message to the HSS to indicate that the delete operation corresponding to the user has been completed.
  • the HSS repeats steps 506 to 508 for other users in the monitoring event configuration until all users corresponding to the monitoring event configuration complete the operation of deleting the monitoring event configuration.
  • FIG. 8 is a schematic diagram of an exemplary management process of event monitoring, referring to FIG. 8, specifically:
  • Step 601 AF sends an event subscription request message to NEF.
  • the AF sends a monitoring event subscription request message to the NEF, and the message carries the NEF subscription association identifier and deletion instruction information.
  • Step 602 NEF sends a monitoring event subscription request message to UDM.
  • the NEF may determine the corresponding UDM subscription association identifier based on the NEF subscription association identifier, and the NEF sends a monitoring event subscription request message, which carries the UDM subscription association identifier and deletion indication information.
  • step 603a the UDM sends a monitoring event subscription request message to the AMF.
  • UDM stores monitoring event subscription information
  • UDM can find the corresponding monitoring event subscription information based on the UDM subscription association identifier, and obtain the corresponding AMF subscription association identifier or SMF subscription association identifier.
  • Steps 603a to 605a are executed for each AMF
  • steps 603b to 605b are executed for each SMF.
  • the UDM sends a monitoring event subscription request message to the AMF, and the message includes the AMF subscription association identifier and deletion instruction information.
  • step 604a the AMF deletes the information of the monitoring event subscription according to the monitoring event subscription request message.
  • the AMF determines the monitoring event subscription according to the AMF subscription association identifier in the monitoring event subscription request message, and deletes the monitoring event subscription.
  • Step 605a AMF sends a confirmation message to UDM.
  • step 603b the UDM sends a monitoring event subscription request message to the SMF.
  • the UDM sends a monitoring event subscription request message to the SMF, and the message includes the SMF subscription association identifier and deletion instruction information.
  • step 604b the SMF deletes the information of the monitoring event subscription according to the monitoring event subscription request message.
  • the SMF determines the monitoring event subscription according to the SMF subscription association identifier in the monitoring event subscription request message, and deletes the monitoring event subscription information.
  • Step 605b SMF sends a confirmation message to UDM.
  • Step 606 UDM sends a confirmation message to NEF.
  • the UDM deletes the monitoring event subscription and sends a confirmation message to the NEF, which carries the UDM acceptance instruction information.
  • step 607 the NEF sends a confirmation message to the AF.
  • the NEF deletes the monitoring event subscription, and sends a confirmation message to the AF, and the message carries the acceptance instruction information.
  • monitoring event configuration also called monitoring event subscription in 5G
  • 5G monitoring event subscription
  • the management of monitoring event configuration is for user groups. For example, if you need to delete the monitoring event configuration, you need to correspond to the monitoring event configuration
  • the monitoring event configuration of all users in the user group is deleted, and the existing technology cannot currently add or delete users in the user group corresponding to the monitoring event configuration. That is to say, the existing technology cannot execute events at the user granularity. Monitoring management.
  • This application proposes an event monitoring and management method, which can overcome the shortcomings of the prior art.
  • the event monitoring management method of this application can be applied to 4G networks and 5G networks.
  • the monitoring management method of this application will be described in detail below in combination with different application scenarios.
  • this application can implement monitoring event configuration for users.
  • Scenario 1 is a specific embodiment of canceling the monitoring event configuration of users in the 4G network.
  • Scenario 2 is adding or deleting users in the user group in the 4G network.
  • scenario three is a specific embodiment of canceling the user's monitoring event configuration in a 5G network
  • scenario four is a specific embodiment of adding or deleting a user's monitoring event configuration in a 5G network.
  • FIG. 9 is a schematic flowchart of an event monitoring management method in an embodiment of the application, and in FIG. 9:
  • the configuration of event monitoring and the monitoring process can refer to the embodiments shown in FIG. 3 and FIG. 4, which will not be repeated here.
  • Step 701 SCS/AS sends a monitoring request message to SCEF.
  • the SCS/AS sends a monitoring request message to the SCEF, which is used to instruct to cancel the event monitoring of the user in the monitoring event configuration.
  • the message includes but is not limited to: identification information of the monitoring event configuration, user identification information, and cancellation instruction information.
  • the identification information of the monitoring event configuration is used to indicate the corresponding monitoring event configuration.
  • the identification information of the monitoring event configuration may be TLTRI.
  • the user's identification information is used to identify the corresponding user.
  • the user's identification information may be the user's external identification information or MSIMSN.
  • the cancel instruction information is used to instruct to cancel the event monitoring of the specified user in the specified monitoring event configuration.
  • the designated monitoring event configuration refers to the monitoring event configuration identified by the identification information of the monitoring event configuration
  • the designated user refers to one or more users in the user group corresponding to the monitoring event configuration, that is, the user's identification information.
  • the corresponding user the monitoring request message may carry identification information of one or more users, that is, the SCS/AS may instruct to cancel the event monitoring of one or more users in the specified monitoring event configuration.
  • the monitoring request message may also include one or more event monitoring type information.
  • a single monitoring event configuration can correspond to one or more event monitoring types
  • SCS/AS can instruct to cancel the event monitoring corresponding to one or more event monitoring types of the specified user in the monitoring event configuration.
  • monitoring event configuration 1 corresponds to monitoring event type 1 and monitoring event type 2.
  • SCS/AS can instruct to cancel the event monitoring corresponding to the event monitoring type 1 corresponding to user 1 of the monitoring event configuration 1, that is, only stop (or cancel) the specified event of user 1 in the monitoring event configuration 1
  • the monitoring of the monitoring type will continue to monitor the configuration of other monitoring events of user 1.
  • the monitoring request message sent by the SCS/AS to the SCEF includes: the identification information of the monitoring event configuration 1 (for example, TLTRI1), the identification information of the user 1, the event monitoring type 1, and the cancellation instruction information.
  • step 702 the SCEF determines the information of the monitoring event configuration according to the monitoring request message.
  • the SCEF receives the monitoring request message sent by the SCS/AS, obtains the parameters it carries, and based on the obtained parameters, updates the information of the monitoring event configuration.
  • the purpose of updating the monitoring event configuration in this step is to When the statistical monitoring event configures the report of the corresponding user group member user, the report of the user (specifically refers to the user who needs to cancel the monitoring) is excluded.
  • SCEF can query the corresponding monitoring event configuration information based on the identification information of the monitoring event configuration.
  • the monitoring event configuration information includes but is not limited to at least one of the following: the number of group members or group members of the user group The user identification list, the reported times of each member user, the maximum report times, the identification information of the user group, the identification information of the monitoring event configuration, etc.
  • the information update mode configured for monitoring events may include at least one of the following:
  • Method 1 SCEF records the identification information and marking information of the user, where the marking information is used to indicate that the user is a excluded user.
  • Method 2 SCEF sets the user's report times as the maximum report times, that is, SCEF defaults to the completion of the user's report.
  • Method 3 SCEF subtracts the number of users that need to be eliminated from the number of group members in the user group corresponding to the monitoring event configuration.
  • Method 4 SCEF deletes the user from the saved user list of the user group.
  • the premise of this method is that SCEF saves the user ID list of the user group.
  • Mode 6 SCEF deletes the received report of the user, and SCEF records the user's identification information and marking information.
  • Mode 5 the prerequisite for the execution of Mode 5 to Mode 7 is that the user's report has been received.
  • the updated monitoring event configuration includes the corresponding relationship between the user’s identification information and the tag information.
  • the tag information can be written into the user’s monitoring event configuration information.
  • SCEF is in the user group configured for the monitoring event.
  • the SCEF defaults to the completion of the user's report.
  • SCEF when SCEF detects whether the report configured by monitoring events is complete, it specifically counts whether the number of users who have reached the maximum number of reports is equal to the number of group members in the user group configured for monitoring events. The number of group members minus the number of users that need to be eliminated, SCEF only needs to detect whether the number of users that have reached the maximum number of reports is equal to the number of updated user group members.
  • SCEF determines that the event monitoring of user 1 needs to cancel monitoring event configuration 1 based on the instruction, and SCEF can configure monitoring event configuration 1 corresponding to user group 1
  • the number of group members of is updated to 2, that is, as long as the statistics of the reports of 2 users reach the maximum number of monitoring times, it can be determined that the report of monitoring event configuration 1 is completed.
  • SCEF saves the user ID list of the user group, SCEF deletes the user from the user ID list, and when SCEF counts the monitoring event report of the user group, it only deals with the user ID list of the user identified in the user ID list. The number of monitoring event reports is counted, so as to achieve the purpose of eliminating users.
  • the user’s monitoring event configuration information may also include reported reports.
  • SCEF deletes the user’s report in the monitoring event configuration.
  • methods one, three and four can be combined. So as to achieve the purpose of eliminating users.
  • method three can also be combined with method one to prevent statistical errors caused by signal transmission delays.
  • the MME/SGSN will be instructed to cancel event monitoring for the user, and correspondingly , The MME will no longer report the user’s report.
  • the MME may report the user’s report before receiving the SCEF instruction. Report, then there will be an error in the SCEF statistical report. Therefore, SCEF can combine Mode 3 and Mode 1 to mark users and update the number of group members in the user group.
  • the updated monitoring event configuration information can be used to instruct SCEF to exclude the user's report when collecting statistics on monitoring event configuration reports.
  • SCEF counts whether the report of the monitoring event configuration is completed, it is based on whether the report of the maximum number of reports of all users corresponding to the monitoring event configuration is received.
  • SCEF ignores the user's report when counting event monitoring reports, that is, only counts the reports of users other than the user.
  • step 703 is executed.
  • the monitoring request message can also include one or more event monitoring type information, in order to achieve the purpose of eliminating the user’s report, the information update mode for the monitoring event configuration can include At least one of the following:
  • Method 1 SCEF records the user's identification information, monitoring type information, and marking information, where the marking information is used to indicate that the user is a excluded user, and the monitoring type information is the monitoring type that needs to be eliminated.
  • the updated monitoring event configuration information can be used to instruct SCEF to exclude the user's need to cancel the monitoring event type report when statistical monitoring event configuration reports.
  • SCEF counts whether the report of the monitoring event configuration is completed, it is based on whether the report of the maximum number of reports of all users corresponding to the monitoring event configuration is received.
  • SCEF ignores the user's specific monitoring event type report when counting the event monitoring report, that is, only statistics Reports of users other than the user and reports of the user's specific monitoring event types.
  • the SCEF determines that the event report of the monitoring event configuration is completed after updating the information of the monitoring event configuration, it immediately sends the monitoring request indication information to the HSS, and the message includes the SCEF Reference ID and deletion indication information carried in the message.
  • the HSS determines the monitoring event configuration that needs to be deleted according to the SCEF Reference ID; otherwise, after receiving the subsequent monitoring event report, it determines that the event report of the monitoring event configuration is completed, and sends the monitoring request instruction information to the HSS to request the deletion of the monitoring event report.
  • Step 703 The SCEF sends a monitoring instruction message to the HSS.
  • the SCEF sends a monitoring request message to the HSS, and the monitoring request message includes the identification information of the monitoring event configuration, the identification information of the user, and the cancellation instruction information.
  • the identification information of the monitoring event configuration in the monitoring request message may be the SCEF Reference ID.
  • the SCEF may determine the corresponding SCEF Reference ID based on TLTRI, and carry it in the monitoring request message and send it to the HSS.
  • the monitoring request message may also carry one or more event monitoring type information, which is used to instruct to cancel the specified type of event monitoring of the user in the monitoring event configuration.
  • the monitoring request message may also carry effective indication information, which is used to indicate that the cancel operation is always effective, that is, after the monitoring event configuration is deleted, the cancel operation is still effective.
  • effective indication information is used to indicate that the cancel operation is always effective, that is, after the monitoring event configuration is deleted, the cancel operation is still effective.
  • the HSS removes the user when sending the user information of the user group members to the SCEF according to the effective instruction information, and instructs the MME/SGSN not to perform event monitoring on the user.
  • the effective indication information may include at least one of the following: user identification information, event monitoring type, and SCS/AS identification information.
  • Step 704 HSS processing.
  • the HSS After the HSS receives the monitoring instruction message, it saves the parameters carried in the monitoring instruction message. In addition, the HSS searches for the MME/SGSN corresponding to the user based on the user's identification information.
  • Step 705 HSS returns a confirmation message to SCEF.
  • the HSS sends a confirmation message to the SCEF, and the message may include acceptance indication information to indicate that the HSS has accepted the monitoring indication message sent by the SCEF.
  • Step 706 SCEF returns a confirmation message to SCS/AS.
  • the SCEF sends a confirmation message to the SCS/AS, and the message may include acceptance indication information to indicate that the SCEF has accepted the monitoring indication message sent by the SCS/AS.
  • Step 707 The HSS sends a request message for inserting subscriber data to the MME/SGSN.
  • the HSS After the HSS finds the MME/SGSN corresponding to the user, it sends a subscriber insertion request message to the MME/SGSN.
  • the message includes, but is not limited to: user identification information, monitoring event configuration identification information, and cancellation instruction information.
  • the user identification information inserted in the subscriber request message may be the user's internal identification information.
  • the HSS can find the user's internal identification information corresponding to the user's external identification from the subscription information, and carry it in the subscription insertion request message and send it to the MME/SGSN.
  • the monitoring event configuration information inserted into the subscriber data request message sent by the HSS to the MME/SGSN may be the SCEF Reference ID.
  • the message may also carry event monitoring type information, which is used to instruct the MME/SGSN to cancel the user's specified type of event monitoring in the monitoring event configuration.
  • step 708 the MME/SGSN cancels the event monitoring of the user configured for the monitoring event.
  • the MME/SGSN receives the subscriber insertion request message, and based on the subscriber insertion request message, executes the cancel operation of the event monitoring of the user configured for the monitoring event.
  • the MME/SGSN monitors each user in the user group based on the monitoring event configuration.
  • the monitoring event configuration includes but is not limited to: monitoring event configuration identification information, event monitoring type information, and user identification information , Maximum number of reports, etc.
  • the MME/SGSN can find the corresponding monitoring event configuration and its information based on the identification information of the event configuration inserted in the subscriber request message, and find the user who needs to cancel monitoring in the monitoring event configuration based on the user's identification information.
  • the MME/SGSN cancels the event monitoring of the user configured for the monitoring event, and deletes the user's monitoring event configuration information, which specifically refers to deleting the user's information corresponding to the monitoring event configuration that needs to be cancelled.
  • the MME/SGSN cancels the event of the user in the monitoring event configuration. Event monitoring corresponding to the monitoring type, and continuing the event monitoring of other event monitoring types of the user, and the MME/SGSN deletes the monitoring event configuration corresponding to the event monitoring type that needs to be cancelled in the monitoring event configuration of the user.
  • monitoring event configuration 1 includes event monitoring type 1 and event monitoring type 2.
  • the context of the user 1 includes the information corresponding to the monitoring event configuration 1 and the information of the monitoring event configuration 2, for example, the MME/SGSN according to the instructions , Cancel the event monitoring of the event monitoring type 1 of user 1 in the monitoring event configuration 1, and the MME/SGSN continues to maintain the event monitoring of the event monitoring type 2 of the user 1 of the monitoring event configuration 1, and the event monitoring of the monitoring event configuration 2 Event monitoring of user 1.
  • the maximum number of reports is the granularity of each monitoring type per user.
  • user 1 belongs to user group 1, and user group 1 corresponds to monitoring event configuration 1 and monitoring event configuration 2.
  • monitoring event configuration 1 includes event monitoring type 1 and event Monitoring type 2.
  • the context of user 1 includes information corresponding to monitoring event configuration 1 and monitoring event configuration 2, for example, monitoring event configuration
  • the information of 1 includes the remaining report times of event monitoring type 1 is 3, the remaining report times of event monitoring type 2 is 1, and the information of monitoring event configuration 2 includes the remaining report times of 2.
  • MME/SGSN cancels the configuration of monitoring events according to the instructions Event monitoring of event monitoring type 1 of user 1 in 1 and deleting the remaining report times of event monitoring type 1 in the user's context or setting the remaining report times to 0, and the MME/SGSN continues to maintain the monitoring event configuration 1 Event monitoring for user 1 of type 2 event monitoring, and event monitoring for user 1 of monitoring event configuration 2.
  • step 709 the MME/SGSN sends a subscriber data insertion response message to the HSS.
  • the MME/SGSN after canceling the event monitoring of the user, the MME/SGSN sends an insert subscriber data response message to the HSS to indicate that the MME/SGSN has performed the cancel operation on the current user.
  • the HSS executes steps 707 to 709 for each user that needs to be canceled, that is, the HSS receives the inserted subscriber data response returned by the MME After the message is received, steps 707 to 709 are executed for another user until all users who need to cancel are executed.
  • the HSS decides to cancel the event monitoring of the user in the monitoring event configuration according to the subscription information or the operator's policy.
  • the specific process is that step 701-step 703 are not executed, and step 704-step 709 are executed. The difference is:
  • Step 704 The HSS decides to cancel the event monitoring of the user in the monitoring event configuration according to the contract information or the operator's strategy;
  • Step 705 HSS sends a monitoring instruction message to SCEF
  • Step 706 SCEF sends a monitoring instruction message to SCS/AS.
  • the SCEF determines that the report for the user group has been completed after updating the information of the monitoring event configuration, the SCEF sends a request message for unsubscription to the HSS, and the HSS further sends a request message for unsubscription to the MME/SGSN.
  • FIG. 10 is a schematic flowchart of an event monitoring management method in an embodiment of the application, and in FIG. 10:
  • the configuration of event monitoring and the monitoring process can refer to the embodiments shown in FIG. 3 and FIG. 4, which will not be repeated here.
  • step 801 the SCS/AS sends a group user configuration management request message to the SCEF.
  • the SCS/AS sends a monitoring request message to the SCEF, which is used to instruct the SCEF to delete the user from the user group, or to add the user to the user group.
  • the SCEF Different from the event monitoring of users who canceled the monitoring event configuration in scenario 1, in scenario one is to operate the event monitoring of the user in the specified monitoring event configuration, while in this scenario, it is for all monitoring events of the user in the user group to which the user belongs Configuration operation.
  • the message includes but is not limited to: identification information of the user group, identification information of the user, and instruction information.
  • the instruction information may be deletion instruction information, which is used to instruct to delete the user from the user group.
  • the instruction information may be adding instruction information, which is used to instruct to add users to the user group.
  • the identification information of the user group may be the external identification information of the user group, and the identification information of the user may be the external identification information of the user.
  • the user identification information in the message may be one or more, which is used to instruct to delete one or more users from the user group, or add one or more users.
  • step 802 the SCEF sends a group user management request message to the HSS.
  • the SCEF sends a user management request message to the HSS to instruct the HSS to update the subscription information.
  • the message includes but is not limited to: identification information of the user group, identification information of the user, and indication information.
  • identification information of the user group For example: the external identification information of the user group, the external identification information of the user and the instruction information.
  • Step 803 The HSS updates the subscription information based on the group user management request message.
  • the HSS stores subscription information.
  • the HSS updates the subscription information accordingly.
  • the HSS can search for the corresponding user group based on the external identification information of the user group, specifically searching for the internal identification information of the corresponding user group, to determine the user group and its corresponding user group list.
  • the user group list includes one or Internal identification information of users corresponding to multiple users.
  • the HSS determines the user's internal identity based on the user's external identity, matches the user's internal identity with the user group list, and deletes the successfully matched user's identity from the user group list. Internal identification information.
  • the HSS determines the user's internal identification based on the user's external identification, and adds the user's internal identification information to the user group list.
  • step 804 the HSS sends a confirmation message to the SCEF.
  • the HSS after the HSS updates the subscription information, it sends a confirmation message to the SCEF to indicate that the HSS has completed the update of the subscription information.
  • the message includes but is not limited to: user group identification information.
  • Step 805 The SCEF determines the information of the monitoring event configuration corresponding to the user group.
  • the SCEF determines that the HSS has completed the update of the subscription information, and the SCEF can update the information of the monitoring event configuration corresponding to the user group.
  • the SCEF may determine the user group and its corresponding monitoring event configuration based on the user group identification information sent by the SCS/AS, specifically referring to all monitoring event configurations corresponding to the user group.
  • the SCEF determines to exclude the user's report when counting all the event monitoring reports of the user group. Refer to step 702 for the culling method, which will not be repeated here.
  • the SCEF determines that when counting all event monitoring reports of the user group, the user report of the user is counted. Specifically, SCEF adds the number of group members recorded in the information configuration of each monitoring event of the user group to the number of added users.
  • step 805 may also be performed before step 802, which is not limited in this application.
  • Step 806 SCEF sends a confirmation message to SCS/AS.
  • SCEF sends a confirmation message to SCS/AS to instruct SCEF to complete relevant configuration.
  • the message can carry user group identification information.
  • step 807 the HSS sends a request message for inserting subscriber data to the MME/SGSN.
  • the HSS sends a subscriber insertion request message to the MME/SGSN, which is used to instruct the MME/SGSN to delete the monitoring event configuration.
  • the request message for inserting a subscriber includes but is not limited to: identification information of one or more monitoring event configurations corresponding to the user group, identification information of the user, and indication information.
  • a user group corresponds to one or more monitoring event configurations. If a user is added or deleted in a user group, it is necessary to update all monitoring event configuration information corresponding to the user group.
  • the HSS has one or more monitoring event configuration identification information corresponding to the user group in the configuration process, which can be carried in the subscriber insertion request message and sent to the MME/SGSN.
  • the identification information of the monitoring event configuration of the user group may be the SCEF Reference ID.
  • the HSS can find the corresponding user group and its corresponding one or more monitoring event configuration identifiers based on the external identification information of the user group information.
  • the user's identification information may be the user's internal identification information.
  • the message also includes related parameters for monitoring event configuration.
  • related parameters include but are not limited to: maximum number of reports, etc., To instruct the MME/SGSN to determine the user's monitoring event configuration based on the related parameters of the monitoring event configuration.
  • step 808 the MME/SGSN starts or cancels event monitoring of the user based on the insert subscriber request message.
  • the MMS/SGSN determines one or more monitoring event configurations corresponding to the user in the user group based on the identification information of one or more monitoring event configurations corresponding to the user group.
  • the MME/SGSN deletes one or more monitoring event configurations corresponding to the user in the user group.
  • the monitoring event configuration identifier is SCEF Reference ID1 and monitoring event configuration 2
  • the monitoring event configuration identifier is SCEF Reference ID2
  • the user Group 2 corresponds to monitoring event configuration 3 and monitoring event configuration 4.
  • MME/SGSN deletes the corresponding monitoring event configuration based on user 1’s identification information and SCEF Reference ID1, based on user 1’s identification Information and SCEF Reference ID2, delete the corresponding monitoring event configuration.
  • the MME/SGSN can configure and monitor the event monitoring of the user based on the relevant parameters of the received monitoring event configuration. For example: MME/SGSN receives the relevant parameters of monitoring event configuration 1, for example, the maximum number of reports is 3. MME/SGSN writes the relevant parameters of monitoring event configuration 1 into the context of user 1, and based on the updated user context The information of monitoring event configuration 1 is used to monitor users. That is to say, when the MME/SGSN performs event monitoring on monitoring event configuration 1, except for the group members in user group 1 corresponding to the pre-configured monitoring event configuration 1. In addition to monitoring, user 1 event monitoring is also required.
  • step 809 the MME/SGSN sends a confirmation message to the HSS.
  • the HSS repeats step 807 to step 809 for each user who needs to be added or deleted from the user group, until all users who need to be added or deleted from the user group are executed.
  • the HSS decides to delete the user from the user group or add the user to the user group according to the subscription information or the operator’s policy.
  • the specific process is: step 801-step 802 is not executed, and step 803-step is executed. 809, the difference lies in:
  • Step 803 The HSS decides to delete the user from the user group or add the user to the user group according to the contract information or the operator's policy;
  • Step 804 HSS sends a group user management request message to SCEF;
  • Step 805 SCEF sends a group user management request message to SCS/AS.
  • the SCEF determines that the report for the user group has been completed after updating the information of the monitoring event configuration, the SCEF sends a request message for unsubscription to the HSS, and the HSS further sends a request message for unsubscription to the MME/SGSN.
  • FIG. 11 is a schematic flowchart of an event monitoring management method in an embodiment of the application, and in FIG. 11:
  • the configuration of event monitoring and the monitoring process can refer to the embodiments shown in FIG. 3 and FIG. 4, which will not be repeated here.
  • Step 901 The SCS/AS sends a group user configuration management request message to the SCEF.
  • step 801 For specific details, refer to step 801, which will not be repeated here.
  • Step 902 SCEF sends a group user management request message to HSS
  • step 802 please refer to step 802, which will not be repeated here.
  • Step 903 The HSS updates the subscription information based on the group user management request message.
  • step 803 For specific details, refer to step 803, which will not be repeated here.
  • Step 904 the HSS sends a confirmation message to the SCEF.
  • step 804 please refer to step 804, which will not be repeated here.
  • Step 905 SCEF sends a confirmation message to SCS/AS.
  • the SCEF sends a confirmation message to the SCE/AS to indicate that the SCEF successfully receives the group user configuration management request message sent by the SCS/AS.
  • step 906 the HSS sends a monitoring instruction message to the SCEF.
  • the HSS sends a monitoring instruction message to the SCEF to instruct the SCEF to update the information of the monitoring event configuration, which can also be understood as an instruction to delete or add users to the user group.
  • the monitoring instruction message sent by HSS to SCEF includes but is not limited to: identification information of one or more monitoring event configurations corresponding to the user group, and user information Identification information.
  • the user's identification information may be the user's external identification information.
  • the monitoring indication message sent by HSS to SCEF includes but is not limited to: identification information and requirements of one or more monitoring event configurations corresponding to the user group The number of added users, or the identification information of one or more monitoring event configurations corresponding to the user group and the number of group members of the user group that needs to be updated, where the number of group members of the user group that needs to be updated is the current user group The sum of the number of group members and the number of users that need to be added.
  • step 907 the SCEF determines the monitoring event configuration information corresponding to the user group.
  • SCEF can update all monitoring event configuration information corresponding to the user group based on the monitoring instruction message sent by the HSS.
  • step 805 For specific details, please refer to step 805, which will not be repeated here.
  • step 908 the HSS sends a request message for inserting subscriber data to the MME/SGSN.
  • step 909 the MME/SGSN starts or cancels event monitoring of the subscriber based on the insert subscriber request message.
  • step 910 the MME/SGSN sends a confirmation message to the HSS.
  • Step 908 to step 910 can refer to step 807 to step 809, which will not be repeated here.
  • the HSS decides to delete the user from the user group or add the user to the user group according to the subscription information or the operator’s policy.
  • the specific process is: Step 901-Step 905 is not executed, and Step 906-Step is executed 919
  • the SCEF determines that the report for the user group has been completed after updating the information of the monitoring event configuration, the SCEF sends a request message for unsubscription to the HSS, and the HSS further sends a request message for unsubscription to the MME/SGSN.
  • FIG. 12 is a schematic flowchart of a monitoring event subscription management method in an embodiment of the application.
  • FIG. 12 is a schematic flowchart of a monitoring event subscription management method in an embodiment of the application.
  • monitoring event subscription and the event reporting process can refer to the embodiments shown in FIG. 5 and FIG. 6, which will not be repeated here.
  • Step 1001 AF sends a monitoring event subscription request message to NEF.
  • the AF sends a monitoring event subscription request message to the NEF, which is used to instruct to cancel the event monitoring of the user in the monitoring event subscription.
  • the message includes but is not limited to: monitoring event subscription identification information, user identification information, and cancellation instruction information.
  • the identification information of the monitoring event subscription is used to indicate the corresponding monitoring event subscription.
  • the identification information of the monitoring event subscription may be an NEF subscription associated identification.
  • the user identification information is used to identify the corresponding user.
  • the user identification information may be the user's external identification information, such as GPIS (Generic Public Subscription Identifier).
  • the cancellation instruction information is used to instruct to cancel the event monitoring of the specified user in the monitoring event subscription corresponding to the NEF subscription associated identification, and the specified use refers to the user corresponding to the user's identification information.
  • the monitoring request message may also include one or more event identifiers.
  • a single monitoring event subscription may correspond to one or more event monitoring types.
  • the AF may instruct to cancel the event monitoring corresponding to one or more event identifiers of the specified user in the monitoring event subscription.
  • step 701 For other details, please refer to step 701, which will not be repeated here.
  • Step 1002 NEF sends a monitoring instruction message to UDM.
  • the NEF sends a monitoring event subscription request message to the UDM, and the monitoring event subscription request message includes the identification information of the monitoring event subscription, the identification information of the user, and the cancellation instruction information.
  • the identification information of the monitoring event subscription in the monitoring request message may be a UDM subscription associated identification
  • the identification information of the user may be the external identification information of the user.
  • the monitoring request message may also carry one or more event identifiers, which are used to instruct to cancel the event monitoring of the specified event identifier of the user in the monitoring event subscription.
  • the monitoring event subscription request message may also carry effective indication information, which is used to indicate that the cancel operation is always effective, that is, after the monitoring event subscription is deleted, the cancel operation is still effective.
  • the effective indication information may include at least one of the following: user identification information, event identification, AF identification information, and monitoring cancellation instruction.
  • the UDM saves the effective instruction information to the UDR.
  • the subsequent AF re-executes the event subscription for this user group
  • the UDM will remove the user when sending the user information of the user group members to the NEF according to the effective instruction information obtained from the UDR, and instruct the AMF or SMF not to perform the subscription for the user. Event monitoring.
  • the UDM after the UDM receives the monitoring instruction message, it saves the parameters carried in the monitoring instruction message. Moreover, UDM can search for the AMF or SMF corresponding to the user based on the user's identification information.
  • Step 1003a UDM sends a monitoring event subscription request message to AMF.
  • the UDM After the UDM finds the AMF corresponding to the user, it sends a monitoring event subscription request message to the AMF.
  • the message includes, but is not limited to: user identification information, monitoring event subscription identification information, and cancellation instruction information.
  • the user identification information in the monitoring event subscription request message may be the user's internal identification information.
  • the UDM can find the user's internal identification information corresponding to the user's external identification from the subscription information, and carry it in the monitoring event subscription request message and send it to the AMF.
  • the monitoring event subscription identification information in the monitoring event subscription request message sent by the UDM to the AMF may be the AMF subscription association identification.
  • the message may also carry event identification information, which is used to instruct the AMF to cancel the event monitoring of the specified event identifier of the user in the monitoring event subscription.
  • step 1004a the AMF cancels the event monitoring of the user in the monitoring event subscription based on the monitoring event subscription request message.
  • the AMF receives the monitoring event subscription request message, and based on the monitoring event subscription request message, executes the cancel operation of the event monitoring of the user configured for the event monitoring.
  • the monitoring event subscription request message carries user identification information, monitoring event subscription identification information, and cancellation indication information, which are used to instruct to cancel the monitoring event Event monitoring of users in subscription.
  • AMF cancels the event monitoring of the user in the monitoring event subscription, and deletes the user's information corresponding to the monitoring event subscription.
  • the user context includes one or more monitoring event subscription information, and the AMF may delete the information corresponding to the monitoring event subscription that needs to be cancelled in the user context, such as the number of remaining reports.
  • AMF adds a cancellation mark in the context of the user to indicate the cancellation of the event monitoring of the user in the monitoring event subscription.
  • the application is not limited), or set the remaining number of reports to 0 in the corresponding monitoring event subscription information in the user's context. In other words, if the user moves to another AMF, the other AMF may not perform event monitoring for users who need to cancel the monitoring event subscription based on the user's context. .
  • the monitoring event subscription request message carries user identification information, monitoring event subscription identification information, event identification and cancellation indication information.
  • the AMF adds a cancellation mark in the context of the user to indicate the cancellation of the event monitoring of the specified event identifier of the user in the event monitoring configuration. That is to say, if the user moves to another AMF, the other AMF can determine that the event monitoring of the user's designated event identifier in the event subscription needs to be cancelled based on the user's context.
  • the monitoring event subscription request message carries the identification information of the user, the identification information of the monitoring event subscription, the event identification, and the cancellation instruction information.
  • AMF cancels the event monitoring of the user's specific event identifier in the monitoring event subscription.
  • the user's context includes one or more monitoring event subscription information, and the AMF may delete the information corresponding to the specific event identifier in the monitoring event subscription that needs to be cancelled, such as the remaining number of reports, in the user's context.
  • AMF adds a cancellation mark in the context of the user to indicate the cancellation of the event monitoring of the user's specific event identifier in the monitoring event subscription.
  • the cancellation mark can be the notification endpoint of UDM or NEF notification endpoint and the corresponding Event identification and cancellation instructions are not limited in this application, or set the remaining number of reports of a specific event identification to 0 in the corresponding monitoring event subscription information in the user's context. That is to say, if the user moves to another AMF, the other AMF may not perform event monitoring on the specific event identifier of the user who needs to cancel the monitoring event subscription based on the user's context.
  • Step 1005a AMF sends a confirmation message to UDM.
  • the AMF sends a confirmation message to the UDM to indicate that the AMF has completed the relevant configuration.
  • step 1003b the UDM sends an insert monitoring event subscription request message to the SMF.
  • step 1003a which will not be repeated here.
  • step 1004b the SMF cancels the event monitoring of the user in the monitoring event subscription based on the monitoring event subscription request message.
  • step 1004a which will not be repeated here.
  • Step 1005b SMF sends a confirmation message to UDM.
  • the UDM performs steps 1003a to 1005a or steps 1003b to 1005b for each user who needs to cancel, that is, UDM receives AMF/ After the monitoring event subscription response message returned by the SMF, step 1003a to step 1005a or step 1003b to step 1005b are executed for another user until all users who need to cancel are executed.
  • Step 1006 UDM sends a confirmation message to NEF.
  • the UDM sends a confirmation message to the NEF to indicate that the relevant configuration has been completed.
  • Step 1007 NEF determines the information of monitoring event subscription.
  • step 702 The specific details are similar to step 702, and will not be repeated here.
  • step 1007 can also be performed before step 1002, that is, by default, UDM can successfully perform related configuration.
  • Step 1008 NEF sends a confirmation message to AF.
  • the NEF sends a confirmation message to the AF to indicate that the NEF has completed the relevant configuration, and the message can carry the identification information of the event monitoring configuration.
  • the UDM decides to cancel the event monitoring of the user in the event subscription according to the subscription information or the operator's policy.
  • the specific process is that step 1001-step 1002 is not executed, and step 1003a-step 1008 is executed. The difference is:
  • Step 1006 UDM sends an event subscription notification message to NEF;
  • Step 1007 NEF sends event subscription notification to AF.
  • the NEF determines that the report for the user group has been completed after updating the information of the monitoring event configuration, the NEF sends an unsubscribe request message to the UDM, and the UDM further sends an unsubscribe request message to the AMF.
  • FIG. 13 is a schematic flowchart of the event subscription management method in an embodiment of the application.
  • FIG. 13 :
  • monitoring event subscription and the event reporting process can refer to the embodiments shown in FIG. 5 and FIG. 6, which will not be repeated here.
  • Step 1101 The AF sends a group user configuration management request message to the NEF.
  • the AF sends a group user configuration management request message to the NEF, which is used to instruct to delete a user from the user group, or add a user to the user group.
  • the message includes but is not limited to: identification information of the user group, identification information of the user, and instruction information.
  • the instruction information may be deletion instruction information, which is used to instruct to delete the user from the user group.
  • the instruction information may be adding instruction information, which is used to instruct to add users to the user group.
  • the identification information of the user group may be the external identification information of the user group, and the identification information of the user may be the external identification information of the user.
  • the user identification information in the message may be one or more, which is used to instruct to delete one or more users from the user group, or add one or more users.
  • Step 1102 NEF sends a group user management request message to UDM.
  • NEF sends a user management request message to UDM, which is used to instruct UDM to update subscription information.
  • the message includes but is not limited to: identification information of the user group, identification information of the user, and indication information.
  • identification information of the user group For example: the external identification information of the user group, the external identification information of the user and the instruction information.
  • Step 1103 UDM updates the subscription information based on the group user management request message.
  • step 803 For specific details, refer to step 803, which will not be repeated here.
  • Step 1104a UDM sends a user data management notification request message to AMF.
  • the UDM sends a user data management notification request message to the AMF corresponding to the user, which is used to instruct the AMF to delete or add users to the user group.
  • the user data management notification request message includes, but is not limited to: a user's internal group identification list, which is used to indicate one or more user groups to which the user belongs.
  • a user's internal group identification list which is used to indicate one or more user groups to which the user belongs.
  • the identification information of one or more user groups in the user's internal group identification list does not include the identification information of the user group.
  • the identification information of one or more user groups in the user's internal group identification list includes identification information specifying the user group.
  • the monitoring event subscription information of the user group saved by AMF/SMF is the group subscription information, that is, it includes all event monitoring corresponding to the user group
  • the configured configuration parameters can also be understood as that AMF can determine the event monitoring configuration parameters required by each group member in the user group based on the group subscription information. Therefore, the user data management notification request message sent by UDM does not need to carry the user group The identification information of the corresponding one or more event monitoring configurations.
  • Step 1105a Based on the user data management notification request message, the AMF starts or cancels event monitoring of the user.
  • the AMF determines that the user no longer belongs to the specified user group based on the user's internal group identification list.
  • AMF can determine one or more monitoring event subscriptions corresponding to the user group based on the identification information of the user group, or it can be understood as group subscription information, then AMF will stop deleting users in one or more monitoring event subscriptions corresponding to the user group Event monitoring, and delete the user's one or more monitoring event subscription information corresponding to the user group.
  • step 1004a which will not be repeated here.
  • the AMF determines that the user belongs to the specified user group based on the user's internal group identification list.
  • AMF can determine one or more monitoring event subscriptions corresponding to the user group based on the identification information of the user group, or it can be understood as group subscription information, then AMF starts to add users to the one or more monitoring event subscriptions corresponding to the user group Event monitoring.
  • the UDM instructs to add users from the user group, but there is no user group monitoring event subscription information on the AMF, that is, the group subscription information of the user group is not stored on the AMF, Then the UDM also sends the monitoring event subscription request message to the AMF, including the event subscription information of the user group, so that the AMF can perform event monitoring on the added users based on the information of the event monitoring configuration of the user group.
  • Step 1106a AMF sends a confirmation message to UDM.
  • Step 1104b UDM sends a user data management notification request message to SMF.
  • Step 1105b the SMF starts or cancels event monitoring of the user based on the user data management notification request message.
  • Step 1106b SMF sends a confirmation message to UDM.
  • Step 1104b to step 1106b can refer to step 1104a to step 1106a, which will not be repeated here.
  • UDM repeats step 1104a to step 1106a or step 1104b to step 1106b until the user group needs to be added or deleted.
  • Step 1107 UDM sends a confirmation message to NEF.
  • Step 1108 NEF determines the monitoring event subscription information corresponding to the user group.
  • step 805 For specific details, please refer to step 805, which will not be repeated here.
  • step 1108 can be executed before step 1102, which is not limited in this application.
  • Step 1109 NEF sends a confirmation message to AF.
  • UDM decides to delete the user from the user group or add the user to the user group according to the subscription information or the operator's policy.
  • the specific process is: Step 1101-Step 1103 are not executed, and Step 1104a-Step 1109, the difference is:
  • Step 1107 UDM sends a group user management request message to NEF;
  • Step 1109 NEF sends a group user management request message to AF.
  • the NEF determines that the report for the user group has been completed after updating the information of the monitoring event configuration, the NEF sends an unsubscribe request message to the UDM, and the UDM further sends an unsubscribe request message to the AMF.
  • FIG. 14 is a schematic flowchart of the event monitoring management method in an embodiment of the application, and in FIG. 14:
  • the configuration of event monitoring and the monitoring process can refer to the embodiments shown in FIG. 5 and FIG. 6, which will not be repeated here.
  • Step 1201 The AF sends a group user configuration management request message to the NEF.
  • Step 1202 NEF sends a group user management request message to UDM
  • Step 1203 UDM updates the subscription information based on the group user management request message.
  • Step 1204a UDM sends a user data management notification request message to AMF.
  • step 1205a the AMF starts or cancels event monitoring of the user based on the user data management notification request message.
  • Step 1206a AMF sends a confirmation message to UDM.
  • Step 1204b UDM sends a user data management notification request message to SMF.
  • step 1205b the SMF starts or cancels event monitoring of the user based on the user data management notification request message.
  • Step 1206b SMF sends a confirmation message to UDM.
  • Steps 1201 to 1206 can refer to steps 1101 to 1106, which will not be repeated here.
  • Step 1207 UDM sends a user group management confirmation message to NEF.
  • step 1208 the NEF sends a user group management confirmation message to the AF.
  • Step 1209 UDM sends an event notification message to NEF.
  • UDM sends an event notification message to NEF to instruct NEF to update event subscription information, which can also be understood as an instruction to delete or add users to the user group.
  • the event notification message sent by UDM to NEF includes but is not limited to: identification information of one or more event monitoring event subscriptions corresponding to the user group, user ⁇ identification information.
  • the identification information of the event notification may be the notification endpoint of the NEF, and the identification information of the user may be the external identification information of the user.
  • the event notification message sent by UDM to NEF includes but is not limited to: the identification information of one or more event notifications corresponding to the user group and the need to add The number of users or the added user identification list, or the identification information of one or more monitoring event subscriptions corresponding to the user group and the number of group members of the user group that needs to be updated or the user identification list of new members of the user group, where, The number of group members of the user group that needs to be updated is the sum of the current number of group members of the user group and the number of users that need to be added.
  • Step 1210 NEF determines the monitoring event subscription information corresponding to the user group.
  • NEF can update all event subscription information corresponding to the user group based on the event notification message sent by UDM.
  • step 805 For specific details, please refer to step 805, which will not be repeated here.
  • UDM decides to delete the user from the user group or add the user to the user group according to the subscription information or the operator’s policy.
  • the specific process is: Step 1201-Step 1303 are not executed, and Step 1204a-Step 1209.
  • the NEF determines that the report for the user group has been completed after updating the information of the monitoring event configuration, the NEF sends an unsubscribe request message to the UDM, and the UDM further sends an unsubscribe request message to the AMF.
  • each network element includes a hardware structure and/or software module corresponding to each function.
  • the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • the embodiment of the present application may divide the function modules of each network element according to the foregoing method examples.
  • each function module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 15 shows a schematic diagram of a possible structure of the network element 100 involved in the foregoing embodiment, such as As shown in FIG. 15, the network element 100 may include: a transceiver module 101 and a processing module 102.
  • the transceiver module 101 is configured to receive an indication message.
  • the indication message includes the identification information of the monitoring event configuration, the identification information of the user, and the indication information.
  • the identification information of the monitoring event configuration is used to indicate the first monitoring event of the user group to which the user belongs Configuration, the indication information is used to instruct to cancel the event monitoring of the user in the first monitoring event configuration.
  • the processing module 102 is configured to determine information about the configuration of the first monitoring event according to the indication message, where the information about the configuration of the first monitoring event includes at least one of the following: group member information of the user group, and information about the number of times the user has reported the monitoring event.
  • the transceiver module 101 is configured to send a delete message to the second network element to instruct the second network element to delete the first monitoring event configuration, where the delete message is information based on the first monitoring event configuration to determine the report of the first event monitoring Sent to the second network element after completion.
  • the information of the first monitoring event configuration indicates that the monitoring event report corresponding to the user should be excluded when the report of the first monitoring event configuration of the user group is counted.
  • the group member information of the user group includes: the number of group members of the user group is the difference between the number of group members of the currently saved user group and the number of users; or, the member users of the user group Delete users as members of the currently saved user group.
  • the processing module 102 is configured to delete the saved user's monitoring event report times.
  • the processing module 102 is configured to set the number of monitoring event reports of the user as the maximum number of reports, that is, by default, the user's report has been completed.
  • the transceiver module 101 is configured to receive an instruction message.
  • the instruction message includes user group identification information, user identification information, and instruction information.
  • the user group identification information is used to indicate the user group the user belongs to, and the instruction information is used to indicate Delete users from the user group, or add users to the user group;
  • the processing module 102 is configured to determine the monitoring event configuration information corresponding to the user group according to the instruction message, where the monitoring event configuration information includes at least one of the following: The group member information of the user group and the user’s monitoring event report times information;
  • the transceiver module 101 is used to send a delete message to the second network element for instructing the second network element to delete the monitoring event configuration, where the delete message is based on the monitoring event
  • the configured information is sent to the second network element after the completion of the event monitoring report.
  • the indication information is used to indicate the deletion of a user from the user group, and the information of the monitoring event configuration indicates that when the report of the monitoring event configuration of the user group is counted, the report of the monitoring event corresponding to the user is excluded.
  • the instruction information is used to indicate the deletion of the user from the user group, and the number of group members of the user group is the difference between the number of group members of the currently saved user group and the number of users.
  • the processing module 102 is configured to delete the saved user's monitoring event report times.
  • the processing module 102 is configured to identify the number of monitoring event reports of the user as the maximum number of reports.
  • the indication information is used to add users to the user group, and the information of the monitoring event configuration indicates the number of times of reporting the monitoring event corresponding to the user.
  • the instruction information is used to add users to the user group, and the number of group members of the user group is the sum of the number of group members of the currently saved user group and the number of users.
  • the transceiver module 101 is configured to receive an indication message.
  • the indication message includes the identification information of the monitoring event configuration, the identification information of the user, and the indication information.
  • the identification information of the monitoring event configuration is used to indicate the first monitoring of the user group to which the user belongs.
  • Event configuration the indication information is used to instruct to cancel the event monitoring of the user in the first monitoring event configuration;
  • the processing module 102 is used to cancel the event monitoring of the user in the first monitoring event configuration according to the instruction message.
  • the indication message further includes an event monitoring type
  • the processing module 102 is configured to cancel the event monitoring of the user's event monitoring type in the first monitoring event configuration.
  • the indication message also includes an event monitoring type
  • the processing module 102 is configured to determine the user's context according to the indication message, and the user's context instructs to cancel the event monitoring of the user in the first monitoring event configuration.
  • the indication message also includes the event monitoring type, and the transceiver module 101 is used to send the user context to the fourth network element for instructing the fourth network element to cancel the configuration of the first monitoring event for the user. Event monitoring.
  • the transceiver module 101 is configured to receive an instruction message.
  • the instruction message includes user group identification information, user identification information, and instruction information.
  • the user group identification information is used to indicate the user group, and the instruction information is used to indicate the slave user Delete users from the group, or instruct to add users to the user group; the processing module 102, if the instruction information is used to instruct the user to be deleted from the user group, cancel the event to the user in the monitoring event configuration corresponding to the user group Monitoring; if the instruction information is used to indicate to add a user to the user group, start event monitoring of the user in the monitoring event configuration corresponding to the user group.
  • the instruction information is used to indicate to delete a user from the user group, and the processing module 102 is also used to update the user's context, and the updated user's context indicates that the user does not belong to the user group;
  • the instruction information is used to indicate that a user is added to the user group, and the processing module 102 is also used to update the user's context, and the updated user's context indicates that the user belongs to the user group.
  • FIG. 16 shows a schematic block diagram of an apparatus 200 according to an embodiment of the present application.
  • the apparatus 200 may include a processor 201 and a transceiver/transceiving pin 202, and optionally, a memory 203.
  • the processor 201 can be used to execute the steps performed by any network element in the methods of the foregoing embodiments, and control the receiving pin to receive signals, and the sending pin to send signals.
  • bus system 204 includes a power bus, a control bus, and a status signal bus in addition to a data bus.
  • various buses are marked as the bus system 204 in the figure.
  • the memory 203 may be used for storing instructions in the foregoing method embodiments.
  • the device 200 may correspond to any network element in the various methods of the foregoing embodiments, and the foregoing and other management operations and/or functions of each element in the device 200 are used to implement the foregoing various management operations and/or functions. For the sake of brevity, the corresponding steps of the method will not be repeated here.
  • the embodiments of the present application also provide a computer-readable storage medium, the computer-readable storage medium stores a computer program, the computer program includes at least a piece of code, the at least one piece of code can be executed by the device to control the device Used to implement the above method embodiments.
  • the embodiments of the present application also provide a computer program, which is used to implement the foregoing method embodiments when the computer program is executed by a device.
  • the program may be stored in whole or in part on a storage medium packaged with the processor, and may also be stored in part or in a memory not packaged with the processor.
  • an embodiment of the present application further provides a processor, which is configured to implement the foregoing method embodiment.
  • the above-mentioned processor may be a chip.
  • an embodiment of the present application also provides a system including each network element in the foregoing method embodiment.
  • the steps of the method or algorithm described in combination with the disclosure of the embodiments of the present application may be implemented in a hardware manner, or may be implemented in a manner in which a processor executes software instructions.
  • Software instructions can be composed of corresponding software modules, which can be stored in random access memory (Random Access Memory, RAM), flash memory, read-only memory (Read Only Memory, ROM), and erasable programmable read-only memory ( Erasable Programmable ROM (EPROM), Electrically Erasable Programmable Read-Only Memory (Electrically EPROM, EEPROM), register, hard disk, mobile hard disk, CD-ROM or any other form of storage medium known in the art.
  • RAM Random Access Memory
  • ROM read-only memory
  • EPROM Erasable Programmable ROM
  • EPROM Electrically Erasable Programmable Read-Only Memory
  • register hard disk, mobile hard disk, CD-ROM or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and write information to the storage medium.
  • the storage medium may also be an integral part of the processor.
  • the processor and the storage medium may be located in the ASIC.
  • the ASIC may be located in a network device.
  • the processor and the storage medium may also exist as discrete components in the network device.
  • the functions described in the embodiments of the present application can be implemented by hardware, software, firmware, or any combination thereof.
  • these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on the computer-readable medium.
  • the computer-readable medium includes a computer storage medium and a communication medium, where the communication medium includes any medium that facilitates the transfer of a computer program from one place to another.
  • the storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Computer And Data Communications (AREA)
  • Information Transfer Between Computers (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本申请实施例提供了一种事件订阅的管理方法及装置，该方法包括：接收指示消息，指示消息包括事件订阅的标识信息、用户的标识信息和指示信息，事件订阅的标识信息用于指示用户所属用户组的第一事件订阅，指示信息用于指示取消第一事件订阅中用户的事件检测；根据指示消息，确定第一事件订阅的信息，其中，第一事件订阅的信息包括以下至少之一：用户组的组成员信息、用户的事件报告次数信息；向第二网元发送删除消息，用于指示第二网元删除第一事件订阅，其中，删除消息为基于第一事件订阅的信息，确定第一事件订阅的报告完成后向第二网元发送的。本申请可实现以用户为粒度的事件订阅管理。

Description

事件订阅管理方法及装置
本申请要求于2020年5月13日提交中国国家知识产权局、申请号为202010404076.6的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，尤其涉及一种事件订阅管理方法及装置。
背景技术
目前，业务能力开放(Service Capability Exposure，SCE)架构可向第三方的业务提供者提供业务能力，例如，事件监控能力，SCE架构可基于第三方发布的指令，对用户组中的各用户进行事件监控(Event Monitoring)。
但是，已有技术中的事件监控管理只能实现以组为单位的管理，例如：取消对用户组的事件监控，或者，删除用户组，或者，增加用户组，而无法实现以用户为粒度的事件监控的管理。
发明内容
本申请提供一种事件监控管理方法、装置及系统，能够在实现以用户为粒度的事件监控的管理。
为达到上述目的，本申请采用如下技术方案：
第一方面，本申请实施例提供一种事件监控管理方法，包括：接收指示消息，指示消息包括监控事件配置的标识信息、用户的标识信息和指示信息，监控事件配置的标识信息用于指示用户所属用户组的第一监控事件配置，指示信息用于指示取消第一监控事件配置中用户的事件监控；根据指示消息，确定第一监控事件配置的信息，其中，第一监控事件配置的信息包括以下至少之一：用户组的组成员信息、用户的监控事件报告次数信息；向第二网元发送删除消息，用于指示第二网元删除第一监控事件配置，其中，删除消息为基于第一监控事件配置的信息，确定第一事件监控的报告完成后向第二网元发送的。
基于上述方式，实现了提供一种更加灵活的管理方式，在对用户的事件监控进行管理时，不会影响其它用户的事件监控，从而实现基于用户为粒度的事件监控的管理。
在一种可能的实现方式中，第一监控事件配置的信息指示在统计用户组的第一监控事件配置的报告时，剔除用户对应的监控事件报告。
基于上述方式，实现了对待取消事件监控的用户的具体执行方式，即为剔除该用户的监控事件报告，从而实现用户粒度的管理方式。
在一种可能的实现方式中，用户组的组成员信息包括：用户组的组成员数量为当前 保存的用户组的组成员数量与用户的数量之间的差值。
基于上述方式，通过对用户组的组成员数量的修改，可实现剔除待取消用户的目的。
在一种可能的实现方式中，用户组的组成员信息包括：所述用户组的成员用户为当前保存的所述用户组的成员用户删除所述用户。
基于上述方式，通过对用户组的组成员列表的修改，可实现剔除待取消用户的目的。
在一种可能的实现方式中，用户组的组成员信息包括所述用户的标识信息和标记信息，标记信息用于指示在统计用户组的第一监控事件配置的报告时，剔除用户对应的监控事件报告。
基于上述方式，通过对需要取消的用户进行标记，以实现剔除待取消用户的目的。
在一种可能的实现方式中，确定第一监控事件配置的信息，包括：删除保存的用户的监控事件报告次数，并且，用户组的组成员数量为当前保存的用户组的组成员数量与用户的数量之间的差值。
基于上述方式，通过对用户组的组成员数量的修改以及已接收到的用户的报告的删除，可实现剔除待取消用户的目的。
在一种可能的实现方式中，确定第一监控事件配置的信息，包括：删除保存的用户的监控事件报告次数，并且，用户组的组成员信息包括所述用户的标识信息和标记信息，标记信息用于指示在统计用户组的第一监控事件配置的报告时，剔除用户对应的监控事件报告。
基于上述方式，通过对已接收到的用户的报告的删除，并结合对用户进行标记的方式，可实现剔除待取消用户的目的。
在一种可能的实现方式中，确定第一监控事件配置的信息，包括：删除保存的用户的监控事件报告次数，并且，所述用户组的成员用户为当前保存的所述用户组的成员用户删除所述用户。
基于上述方式，通过结合对已接收到的用户的报告的删除以及对用户组的组成员列表的修改，可实现剔除待取消用户的目的。
在一种可能的实现方式中，确定第一监控事件配置的信息，包括：将用户的监控事件报告次数设置为最大报告次数，即默认为该用户的报告已完成。
基于上述方式，将待取消的事件监控的用户的监控事件报告次数设置为最大值，同样可实现剔除待取消用户的目的。
在一种可能的实现方式中，指示消息还包括事件监控类型信息，所述指示信息用于指示取消第一事件监控配置中的所述用户的第一事件监控，其中，所述事件监控类型信 息指示第一事件监控的事件监控类型。
在一种可能的实现方式中，第一监控事件配置的信息指示在统计用户组的第一监控事件配置的报告时，剔除用户对应的第一事件监控的监控事件报告。
在一种可能的实现方式中，确定第一监控事件配置的信息，包括：将用户的监控事件报告次数设置为最大报告次数，即默认为该用户的报告已完成。
在一种可能的实现方式中，指示消息还包括生效指示信息，用于指示所述指示信息所指示的内容持续生效。
第二方面，本申请实施例提供一种事件监控管理方法，包括：接收指示消息，指示消息包括用户组的标识信息、用户的标识信息和指示信息，用户组的标识信息用于指示用户所属用户组，指示信息用于指示从用户组中删除用户，或者，在用户组中增加用户；根据指示消息，确定用户组对应的监控事件配置的信息，其中，监控事件配置的信息包括以下至少之一：用户组的组成员信息、用户的监控事件报告次数信息；向第二网元发送删除消息，用于指示第二网元删除监控事件配置，其中，删除消息为基于监控事件配置的信息，确定事件监控的报告完成后向第二网元发送的。
基于上述方式，实现了提供一种更加灵活的管理方式，在对用户的事件监控进行管理时，不会影响其它用户的事件监控，从而实现基于用户为粒度的事件监控的管理。
在一种可能的实现方式中，指示信息用于指示从用户组中删除用户，监控事件配置的信息指示在统计用户组的监控事件配置的报告时，剔除用户对应的监控事件的报告。
在一种可能的实现方式中，指示信息用于指示从用户组中删除用户，用户组的组成员数量为当前保存的用户组的组成员数量与用户的数量之间的差值。
在一种可能的实现方式中，指示信息用于指示从用户组中删除用户，所述用户组的成员用户为当前保存的所述用户组的成员用户删除所述用户。
在一种可能的实现方式中，确定用户组对应的监控事件配置的信息，包括：删除保存的用户的监控事件报告次数，并且，用户组的组成员数量为当前保存的用户组的组成员数量与用户的数量之间的差值。
在一种可能的实现方式中，确定用户组对应的监控事件配置的信息，包括：用户组的组成员信息包括所述用户的标识信息和标记信息，标记信息用于指示在统计用户组的第一监控事件配置的报告时，剔除用户对应的监控事件报告。
在一种可能的实现方式中，确定用户组对应的监控事件配置的信息，包括：删除保存的用户的监控事件报告次数，并且，用户组的组成员信息包括所述用户的标识信息和标记信息，标记信息用于指示在统计用户组的第一监控事件配置的报告时，剔除用户对应的监控事件报告。
在一种可能的实现方式中，确定用户组对应的监控事件配置的信息，包括：删除保存的用户的监控事件报告次数，并且，所述用户组的成员用户为当前保存的所述用户组的成员用户删除所述用户。
在一种可能的实现方式中，确定用户组对应的监控事件配置的信息，包括：将用户的监控事件报告次数标识为最大报告次数。
在一种可能的实现方式中，指示信息用于在用户组中增加用户，监控事件配置的信息指示统计用户对应的监控事件的报告次数。
在一种可能的实现方式中，指示信息用于在用户组中增加用户，用户组的组成员数量为当前保存的用户组的组成员数量与用户的数量的和。
在一种可能的实现方式中，指示信息用于指示从用户组中增加用户，所述用户组的成员用户为当前保存的所述用户组的成员用户增加所述用户。
在一种可能的实现方式中，指示消息还包括生效指示信息，用于指示所述指示信息所指示的内容持续生效。
第三方面，本申请实施例提供一种事件监控管理方法，包括：接收指示消息，指示消息包括监控事件配置的标识信息、用户的标识信息和指示信息，监控事件配置的标识信息用于指示用户所属用户组的第一监控事件配置，指示信息用于指示取消第一监控事件配置中用户的事件监控；根据指示消息，取消第一监控事件配置中用户的事件监控。
基于上述方式，实现了提供一种更加灵活的管理方式，在对用户的事件监控进行管理时，不会影响其它用户的事件监控，从而实现基于用户为粒度的事件监控的管理。
在一种可能的实现方式中，指示消息还包括事件监控类型，取消第一监控事件配置中用户的事件监控，包括：取消第一监控事件配置中用户的事件监控类型的事件监控。
在一种可能的实现方式中，方法还包括：根据指示消息，确定用户的上下文，用户的上下文指示取消第一监控事件配置中对用户的事件监控。
基于上述方式，实现了对用户进行标记，以使用户迁移到其它网元后，其它网元能够继续依据该标记，执行对用户的事件监控的管理。
在一种可能的实现方式中，方法还包括：向第四网元发送用户的上下文，用于指示第四网元取消第一监控事件配置中对用户的事件监控。
第四方面，本申请实施例提供一种事件监控管理方法，包括：接收指示消息，指示消息包括用户组的标识信息、用户的标识信息和指示信息，用户组的标识信息用于指示用户组，指示信息用于指示从用户组中删除用户，或者，用于指示在用户组中增加用户；若指示信息用于指示从用户组中删除用户，取消在用户组对应的监控事件配置中对用户的事件监控；若指示信息用于指示在用户组中增加用户，开始在用户组对应的监控事件配置中对用户进行事件监控。
基于上述方式，实现了提供一种更加灵活的管理方式，在对用户的事件监控进行管理时，不会影响其它用户的事件监控，从而实现基于用户为粒度的事件监控的管理。
在一种可能的实现方式中，指示信息用于指示从用户组中删除用户，方法还包括：更新用户的上下文，更新后的用户的上下文指示用户不属于用户组；
基于上述方式，实现了对用户进行标记，以使用户迁移到其它网元后，其它网元能够继续依据该标记，执行对用户的事件监控的管理。
在一种可能的实现方式中，指示信息用于指示在用户组中增加用户，方法还包括：更新用户的上下文，更新后的用户的上下文指示用户属于用户组。
第五方面，本申请实施例提供一种事件监控管理方法，包括：接收第一指示消息，所述第一指示消息包括用户组的标识信息、用户的标识信息和指示信息，所述用户组的标识信息用于指示所述用户所属用户组，所述指示信息用于指示从所述用户组中删除所述用户，或者，在所述用户组中增加所述用户；基于所述第一指示消息，向第一网元发送第二指示消息，所述第二指示消息包括监控事件配置的标识信息和所述用户组的组成员信息，所述监控事件的标识信息用于指示所述用户组的监控事件配置。
在一种可能的实现方式中，若所述指示信息为从用户组中删除用户，所述组成员更新信息为所述用户的标识信息。
在一种可能的实现方式中，若所述指示信息为在用户组中增加用户，所述组成员更新信息为所述用户的标识信息或所述用户组的用户的数量。
在一种可能的实现方式中，若所述指示信息为从用户组中删除用户，方法还包括：向第三网元发送第三指示消息，所述第三指示消息中包括所述用户所属的用户组集合，其中，用户组集合中不包括所述用户组。
在一种可能的实现方式中，若所述指示信息为从用户组中删除用户，方法还包括：向第三网元发送第三指示消息，所述第三指示消息中包括所述用户所属的用户组集合，其中，用户组集合中包括所述用户组。
第六方面，本申请实施例提供一种装置，包括：存储器和处理器，存储器和处理器耦合，存储器存储有程序指令，程序指令被处理器运行时，使得装置执行如下步骤：接收指示消息，指示消息包括监控事件配置的标识信息、用户的标识信息和指示信息，监控事件配置的标识信息用于指示用户所属用户组的第一监控事件配置，指示信息用于指示取消第一监控事件配置中用户的事件监控；根据指示消息，确定第一监控事件配置的信息，其中，第一监控事件配置的信息包括以下至少之一：用户组的组成员信息、用户的监控事件报告次数信息；向第二网元发送删除消息，用于指示第二网元删除第一监控事件配置，其中，删除消息为基于第一监控事件配置的信息，确定第一事件监控的报告完成后向第二网元发送的。
在一种可能的实现方式中，第一监控事件配置的信息指示在统计用户组的第一监控事件配置的报告时，剔除用户对应的监控事件报告。
在一种可能的实现方式中，用户组的组成员信息包括：用户组的组成员数量为当前保存的用户组的组成员数量与用户的数量之间的差值。
在一种可能的实现方式中，用户组的组成员信息包括：所述用户组的成员用户为当前保存的所述用户组的成员用户删除所述用户。
在一种可能的实现方式中，用户组的组成员信息包括所述用户的标识信息和标记信息，标记信息用于指示在统计用户组的第一监控事件配置的报告时，剔除用户对应的监控事件报告。
在一种可能的实现方式中，程序指令被处理器运行时，使得装置执行如下步骤：删除保存的用户的监控事件报告次数，并且，用户组的组成员数量为当前保存的用户组的组成员数量与用户的数量之间的差值。
在一种可能的实现方式中，程序指令被处理器运行时，使得装置执行如下步骤：删除保存的用户的监控事件报告次数，并且，用户组的组成员信息包括所述用户的标识信息和标记信息，标记信息用于指示在统计用户组的第一监控事件配置的报告时，剔除用户对应的监控事件报告。
在一种可能的实现方式中，程序指令被处理器运行时，使得装置执行如下步骤：删除保存的用户的监控事件报告次数，并且，所述用户组的成员用户为当前保存的所述用 户组的成员用户删除所述用户。
在一种可能的实现方式中，程序指令被处理器运行时，使得装置执行如下步骤：将用户的监控事件报告次数设置为最大报告次数，即默认为该用户的报告已完成。
在一种可能的实现方式中，指示消息还包括事件监控类型信息，所述指示信息用于指示取消第一事件监控配置中的所述用户的第一事件监控，其中，所述事件监控类型信息指示第一事件监控的事件监控类型。
在一种可能的实现方式中，第一监控事件配置的信息指示在统计用户组的第一监控事件配置的报告时，剔除用户对应的第一事件监控的监控事件报告。
在一种可能的实现方式中，程序指令被处理器运行时，使得装置执行如下步骤：将用户的监控事件报告次数设置为最大报告次数，即默认为该用户的报告已完成。
在一种可能的实现方式中，指示消息还包括生效指示信息，用于指示所述指示信息所指示的内容持续生效。
第七方面，本申请实施例提供一种装置，包括：存储器和处理器，存储器和处理器耦合，存储器存储有程序指令，程序指令被处理器运行时，使得装置执行如下步骤：接收指示消息，指示消息包括用户组的标识信息、用户的标识信息和指示信息，用户组的标识信息用于指示用户所属用户组，指示信息用于指示从用户组中删除用户，或者，在用户组中增加用户；根据指示消息，确定用户组对应的监控事件配置的信息，其中，监控事件配置的信息包括以下至少之一：用户组的组成员信息、用户的监控事件报告次数信息；向第二网元发送删除消息，用于指示第二网元删除监控事件配置，其中，删除消息为基于监控事件配置的信息，确定事件监控的报告完成后向第二网元发送的。
在一种可能的实现方式中，指示信息用于指示从用户组中删除用户，监控事件配置的信息指示在统计用户组的监控事件配置的报告时，剔除用户对应的监控事件的报告。
在一种可能的实现方式中，指示信息用于指示从用户组中删除用户，用户组的组成员数量为当前保存的用户组的组成员数量与用户的数量之间的差值。
在一种可能的实现方式中，指示信息用于指示从用户组中删除用户，所述用户组的成员用户为当前保存的所述用户组的成员用户删除所述用户。
在一种可能的实现方式中，程序指令被处理器运行时，使得装置执行如下步骤：删除保存的用户的监控事件报告次数，并且，用户组的组成员数量为当前保存的用户组的 组成员数量与用户的数量之间的差值。
在一种可能的实现方式中，用户组的组成员信息包括所述用户的标识信息和标记信息，标记信息用于指示在统计用户组的第一监控事件配置的报告时，剔除用户对应的监控事件报告。
在一种可能的实现方式中，程序指令被处理器运行时，使得装置执行如下步骤：删除保存的用户的监控事件报告次数，并且，用户组的组成员信息包括所述用户的标识信息和标记信息，标记信息用于指示在统计用户组的第一监控事件配置的报告时，剔除用户对应的监控事件报告。
在一种可能的实现方式中，程序指令被处理器运行时，使得装置执行如下步骤：删除保存的用户的监控事件报告次数，并且，所述用户组的成员用户为当前保存的所述用户组的成员用户删除所述用户。
在一种可能的实现方式中，程序指令被处理器运行时，使得装置执行如下步骤：将用户的监控事件报告次数标识为最大报告次数。
在一种可能的实现方式中，指示信息用于在用户组中增加用户，监控事件配置的信息指示统计用户对应的监控事件的报告次数。
在一种可能的实现方式中，指示信息用于在用户组中增加用户，用户组的组成员数量为当前保存的用户组的组成员数量与用户的数量的和。
在一种可能的实现方式中，指示信息用于在用户组中增加用户，所述用户组的成员用户为当前保存的所述用户组的成员用户增加所述用户。
在一种可能的实现方式中，指示消息还包括生效指示信息，用于指示所述指示信息所指示的内容持续生效。
第八方面，本申请实施例提供一种装置，包括：存储器和处理器，存储器和处理器耦合，存储器存储有程序指令，程序指令被处理器运行时，使得装置执行如下步骤：接收指示消息，指示消息包括监控事件配置的标识信息、用户的标识信息和指示信息，监控事件配置的标识信息用于指示用户所属用户组的第一监控事件配置，指示信息用于指示取消第一监控事件配置中用户的事件监控；根据指示消息，取消第一监控事件配置中用户的事件监控。
在一种可能的实现方式中，指示消息还包括事件监控类型，程序指令被处理器运行 时，使得装置执行如下步骤：取消第一监控事件配置中用户的事件监控类型的事件监控。
在一种可能的实现方式中，程序指令被处理器运行时，使得装置执行如下步骤：根据指示消息，确定用户的上下文，用户的上下文指示取消第一监控事件配置中对用户的事件监控。
在一种可能的实现方式中，程序指令被处理器运行时，使得装置执行如下步骤：将用户的上下文发送给第四网元，用于指示第四网元取消第一监控事件配置中对用户的事件监控。
第九方面，本申请实施例提供一种装置，包括：存储器和处理器，存储器和处理器耦合，存储器存储有程序指令，程序指令被处理器运行时，使得装置执行如下步骤：接收指示消息，指示消息包括用户组的标识信息、用户的标识信息和指示信息，用户组的标识信息用于指示用户组，指示信息用于指示从用户组中删除用户，或者，用于指示在用户组中增加用户；若指示信息用于指示从用户组中删除用户，取消在用户组对应的监控事件配置中对用户的事件监控；若指示信息用于指示在用户组中增加用户，开始在用户组对应的监控事件配置中对用户进行事件监控。
在一种可能的实现方式中，指示信息用于指示从用户组中删除用户，程序指令被处理器运行时，使得装置执行如下步骤：更新用户的上下文，更新后的用户的上下文指示用户不属于用户组；
在一种可能的实现方式中，指示信息用于指示在用户组中增加用户，程序指令被处理器运行时，使得装置执行如下步骤：更新用户的上下文，更新后的用户的上下文指示用户属于用户组。
第十方面，本申请实施例提供一种装置，存储器和处理器，存储器和处理器耦合，存储器存储有程序指令，程序指令被处理器运行时，使得装置执行如下步骤：接收第一指示消息，所述第一指示消息包括用户组的标识信息、用户的标识信息和指示信息，所述用户组的标识信息用于指示所述用户所属用户组，所述指示信息用于指示从所述用户组中删除所述用户，或者，在所述用户组中增加所述用户；基于所述第一指示消息，向第一网元发送第二指示消息，所述第二指示消息包括监控事件配置的标识信息和所述用户组的组成员信息，所述监控事件的标识信息用于指示所述用户组的监控事件配置。
在一种可能的实现方式中，若所述指示信息为从用户组中删除用户，所述组成员更新信息为所述用户的标识信息。
在一种可能的实现方式中，若所述指示信息为在用户组中增加用户，所述组成员更 新信息为所述用户的标识信息或所述用户组的用户的数量。
在一种可能的实现方式中，若所述指示信息为从用户组中删除用户，程序指令被处理器运行时，使得装置执行如下步骤：向第三网元发送第三指示消息，所述第三指示消息中包括所述用户所属的用户组集合，其中，用户组集合中不包括所述用户组。
在一种可能的实现方式中，若所述指示信息为从用户组中删除用户，程序指令被处理器运行时，使得装置执行如下步骤：向第三网元发送第三指示消息，所述第三指示消息中包括所述用户所属的用户组集合，其中，用户组集合中包括所述用户组。
第十一方面，本申请实施例提供了一种装置，包括收发模块、处理模块，收发模块，用于接收指示消息，所述指示消息包括监控事件配置的标识信息、用户的标识信息和指示信息，所述监控事件配置的标识信息用于指示所述用户所属用户组的第一监控事件配置，所述指示信息用于指示取消所述第一监控事件配置中所述用户的事件监控；处理模块，用于根据所述指示消息，确定所述第一监控事件配置的信息，其中，所述第一监控事件配置的信息包括以下至少之一：所述用户组的组成员信息、所述用户的监控事件报告次数信息；收发模块，还用于向第二网元发送删除消息，用于指示所述第二网元删除所述第一监控事件配置，其中，所述删除消息为基于所述第一监控事件配置的信息，确定所述第一事件监控的报告完成后向所述第二网元发送的。
第十二方面，本申请实施例提供一种装置，包括：收发模块、处理模块，收发模块，用于接收指示消息，所述指示消息包括用户组的标识信息、用户的标识信息和指示信息，所述用户组的标识信息用于指示所述用户所属用户组，所述指示信息用于指示从所述用户组中删除所述用户，或者，在所述用户组中增加所述用户；处理模块，用于根据所述指示消息，确定所述用户组对应的监控事件配置的信息，其中，所述监控事件配置的信息包括以下至少之一：所述用户组的组成员信息、所述用户的监控事件报告次数信息；收发模块，还用于向第二网元发送删除消息，用于指示所述第二网元删除所述监控事件配置，其中，所述删除消息为基于所述监控事件配置的信息，确定所述事件监控的报告完成后向所述第二网元发送的。
第十三方面，本申请实施例提供一种装置，包括：收发模块、处理模块，收发模块，用于接收指示消息，所述指示消息包括监控事件配置的标识信息、用户的标识信息和指示信息，所述监控事件配置的标识信息用于指示所述用户所属用户组的第一监控事件配置，所述指示信息用于指示取消所述第一监控事件配置中所述用户的事件监控；处理模块，用于根据所述指示消息，取消所述第一监控事件配置中所述用户的事件。
第十四方面，本申请实施例提供一种装置，包括：收发模块、处理模块，收发模块，用于接收指示消息，所述指示消息包括用户组的标识信息、用户的标识信息和指示信息， 所述用户组的标识信息用于指示用户组，所述指示信息用于指示从所述用户组中删除所述用户，或者，用于指示在所述用户组中增加所述用户；处理模块，用于若所述指示信息用于指示从所述用户组中删除所述用户，取消在所述用户组对应的监控事件配置中对所述用户的事件监控；若所述指示信息用于指示在所述用户组中增加所述用户，开始在所述用户组对应的监控事件配置中对所述用户进行事件监控。
第十五方面，本申请实施例提供一种装置，包括收发模块，用于接收第一指示消息，所述第一指示消息包括用户组的标识信息、用户的标识信息和指示信息，所述用户组的标识信息用于指示所述用户所属用户组，所述指示信息用于指示从所述用户组中删除所述用户，或者，在所述用户组中增加所述用户；收发模块，还用于基于所述第一指示消息，向第一网元发送第二指示消息，所述第二指示消息包括监控事件配置的标识信息和所述用户组的组成员信息，所述监控事件的标识信息用于指示所述用户组的监控事件配置。
第十六方面，本申请实施例提供一种事件监控管理系统，包括应用服务器、第一网元、第二网元和第三网元；应用服务器，用于向第一网元发送第一指示消息，第一指示消息包括监控事件配置的标识信息、用户的标识信息和指示信息，监控事件配置的标识信息用于指示用户所属用户组的第一监控事件配置，指示信息用于指示取消第一监控事件配置中用户的事件监控；第一网元，用于基于第一指示消息，确定第一监控事件配置的信息，其中，第一监控事件配置的信息包括以下至少之一：用户组的组成员信息、用户的监控事件报告次数信息；第一网元，用于向第二网元发送第二指示消息，第二指示消息包括监控事件配置的标识信息、用户的标识信息和指示信息；第二网元，用于向第三网元发送第二指示消息，用于指示第三网元取消第一监控事件配置中用户的事件监控；第三网元，用于基于第二指示消息，取消第一监控事件配置中用户的事件监控；第一网元，还用于向第二网元发送删除消息，用于指示第二网元删除第一监控事件配置，其中，删除消息为基于第一监控事件配置的信息，确定第一事件监控的报告完成后向第二网元发送的。
第十七方面，本申请实施例提供一种事件监控管理系统，其特征在于，包括应用服务器、第一网元、第二网元和第三网元；应用服务器，用于向第一网元发送第一指示消息，第一指示消息包括用户组的标识信息、用户的标识信息和指示信息，用户组的标识信息用于指示用户所属用户组，指示信息用于指示从用户组中删除用户，或者，在用户组中增加用户；第一网元，用于根据第一指示消息，确定用户组对应的监控事件配置的信息，其中，监控事件配置的信息包括以下至少之一：用户组的组成员信息、用户的监控事件报告次数信息；第一网元，用于向第二网元发送第二指示消息，第二指示消息包括用户组的标识信息、用户的标识信息和指示信息；第二网元，用于向第三网元发送第二指示消息，用于指示从用户组中删除用户，或者，用于指示在用户组中增加用户；第三网元，用于若指示信息用于指示从用户组中删除用户，取消在用户组对应的监控事件 配置中对用户的事件监控；若指示信息用于指示在用户组中增加用户，开始在用户组对应的监控事件配置中对用户进行事件监控；第一网元，还用于向第二网元发送删除消息，用于指示第二网元删除监控事件配置，其中，删除消息为基于监控事件配置的信息，确定事件监控的报告完成后向第二网元发送的。
第十八方面，本申请实施例提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第一方面至第五方面中的任一方面中的方法的指令。
第十九方面，本申请实施例提供了一种计算机程序，该计算机程序包括用于执行第一方面至第五方面中的任一方面中的方法的指令。
第二十方面，本申请实施例提供了一种芯片，该芯片包括处理电路、收发管脚。其中，该收发管脚、和该处理电路通过内部连接通路互相通信，该处理电路执行第一方面至第五方面中的任一方面中的方法，以控制接收管脚接收信号，以控制发送管脚发送信号。
附图说明
为了更清楚地说明本申请实施例的技术方案，下面将对本申请实施例的描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是示例性示出的一种业务能力开放的结构示意图；
图2是示例性示出的一种业务能力开放的结构示意图；
图3是示例性示出的监控事件的配置流程示意图；
图4是示例性示出的监控事件的监控流程示意图；
图5是示例性示出的监控事件的配置流程示意图；
图6是示例性示出的监控事件的监控流程示意图；
图7是示例性示出的监控事件的管理流程示意图；
图8是示例性示出的监控事件的管理流程示意图；
图9是本申请实施例提供的一种事件监控管理方法的流程示意图；
图10是本申请实施例提供的一种事件监控管理方法的流程示意图；
图11是本申请实施例提供的一种事件监控管理方法的流程示意图；
图12是本申请实施例提供的一种事件监控管理方法的流程示意图；
图13是本申请实施例提供的一种事件监控管理方法的流程示意图；
图14是本申请实施例提供的一种事件监控管理方法的流程示意图；
图15是本申请实施例提供的一种网元的结构示意图；
图16是本申请实施例提供的一种装置的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。
本申请实施例的说明书和权利要求书中的术语“第一”和“第二”等是用于区别不同的对象，而不是用于描述对象的特定顺序。例如，第一目标对象和第二目标对象等是用于区别不同的目标对象，而不是用于描述目标对象的特定顺序。
在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
在本申请实施例的描述中，除非另有说明，“多个”的含义是指两个或两个以上。例如，多个处理单元是指两个或两个以上的处理单元；多个系统是指两个或两个以上的系统。
本申请实施例所涉及的用户，也可以称为用户设备(User Equipment，UE)或者终端，还可以称为移动台(mobile station)，用户单元(subscriber unit)，站台(station)，终端设备(terminal equipment，TE)等。终端可以为蜂窝电话(cellular phone)，个人数字助理(personal digital assistant，PDA)，无线调制解调器(modem)，手持设备(handheld)，膝上型电脑(laptop computer)，无绳电话(cordless phone)，无线本地环路(wireless local loop，WLL)台，平板电脑(pad)等。随着无线通信技术的发展，可以接入通信系统、可以与通信系统的网络侧进行通信，或者通过通信系统与其它物体进行通信的设备都可以是本申请实施例中的用户，譬如，智能交通中的终端和汽车、智能家居中的家用设备、智能电网中的电力抄表仪器、电压监测仪器、环境监测仪器、智能安全网络中的视频监控仪器、收款机等等。
为使本领域人员更好地理解本申请的技术方案，下面对可能涉及到的背景技术进行简单介绍。
1)SCE架构
如图1所示为第四代移动通信技术(the 4th generation mobile communication technology，4G)网络中的业务能力开放的架构图，参照图1，架构中包括业务能力服务器(Services Capability Server，SCS)/应用服务器(Application Server，AS)、业务能力开放功能(Service Capability Exposure Function，SCEF)、归属用户服务器(Home Subscriber Server，HSS)、移动管理实体(Mobile Management Entity，MME)和服务GPRS支持节点(Serving GPRS(General packet radio service，通用无线分组业务)Support Node，SGSN)。
具体的，业务能力服务器(Services Capability Server，SCS)/应用服务器(Application  Server，AS)可看作为第三方业务提供者。SCEF为该架构中的核心网元，使得网络能够安全地向SCS/AS提供业务能力。HSS为归属用户签约服务器，用于保存用户的签约信息。MME和SGSN为负责对UE进行移动性管理的网元。SCS/AS通过T8的API接口调用SCEF提供的业务能力。
如图2所示为第五代移动通信技术(the 5th generation mobile communication technology，5G)网络中的业务能力开放的架构图，参照图2，架构中包括应用功能(Application Function，AF)、网络开放功能(Network Exposure Function，NEF)统一数据管理(Unified Data Management，UDM)、核心网接入和移动性管理功能(Core Access and Mobility Management Function，AMF)、会话管理功能(Session Management Function，SMF)。
其中，NEF类似于4G中的SCEF的功能，可通过向AF提供所需的业务和能力。UDM类似于HSS的功能，可向NEF提供相关的业务和能力。AMF/SMF类似于MME/SGSN的功能，可向NEF提供支持的业务和能力。
2)事件监控流程
下面分别对上述两种业务能力开放架构中的监控事件的配置流程和监控流程进行详细说明：
a.基于4G网络的业务能力开放架构的监控事件配置(Monitoring Event Configuration)流程。
如图3所示为示例性示出的监控事件的配置流程示意图，参照图3，具体的：
步骤101，SCS/AS向SCEF发送监控请求消息。
具体的，SCS/AS向SCEF发送监控请求消息，用于指示SCEF配置用户组的事件监控。
示例性的，监控请求消息中包括但不限于：监控类型(Monitoring Type)信息、外部组标识(External Group ID)、T8接口长期交互参考标识(T8Long Term Transaction Reference ID，TLTRI)、SCS/AS的标识信息、T8的目的地址信息。
具体的，监控类型信息也可以称为事件监控类型信息，是指需要对用户组进行事件监控的类型，也可以理解为对用户组进行指定类型的事件监控。可选地，监控请求消息中可携带一个或多个事件监控类型信息，用于指示对用户组的一个或多个指定类型的监控事件进行监控。例如，事件监控类型可以为连接丢失(Loss of connectivity)和用户设备可达(UE reachability)等。
External Group ID用于指示用户组，SCS/AS和SCEF可基于该标识识别到对应的用户组。需要说明的是，用户组均已提前配置完成，用户组可以包括一个或多个用户，具体配置过程本申请不再赘述。
TLTRI用于指示监控事件配置，SCS/AS和SCEF可基于TLTRI查询到对应的监控事件配置。
需要说明的是，用户、用户组与监控事件配置之间的对应关系可以理解为：一个用户可以属于不同的用户组，单一用户组可以对应一个或多个监控事件配置，每个监控事件配置可以对应一个或多个事件监控类型。举例说明，UE1属于用户组1和用户组2， 用户组1对应监控事件配置1(TLTRI1)，被配置为监控用户组1的Loss of connectivity监控事件，即监控事件配置1的事件监控类型为Loss of connectivity；用户组1还对应监控事件配置2(TLTRI2)，被配置为监控用户组1的UE reachability监控事件，即监控事件配置2的事件监控类型为UE reachability。用户组2对应监控事件配置3(TLTRI13)，被配置为监控用户组2的Loss of connectivity监控事件，即事件金控配置3的事件监控类型为Loss of connectivity。
可选地，监控请求消息中还可以包括以下至少之一：最大报告次数、监控持续时间。示例性的，监控持续时间用于指示用户组进行事件监控的监控时长，也就是说，当监控持续时间到达时，可确定该监控事件配置的报告完成，网络不再对对应的监控事件配置进行监控。示例性的，最大报告次数用于指示该监控事件配置中的每个用户可上报报告的最大次数，也就是说，当用户组内的每个用户对应于该监控事件配置的报告均达到最大报告次数，则确定监控事件配置的报告完成，不再对该监控事件配置进行监控。举例说明：用户组1包括3个用户，当SCEF保存的每个用户对应于指定监控事件配置的报告次数均达到最大报告次数时，可确定该监控事件配置的报告完成。此外，最大报告次数还可以用于指示该监控事件配置中的每个用户的每一个监控类型可上报报告的最大次数，也就是说，一个监控事件配置中，当用户组内的每个用户的每一个监控类型的报告均达到最大报告次数，则确定监控事件配置的报告完成，不再对该监控事件配置进行监控。
需要说明的是，如上文所述，单一用户组可以对应多个监控事件配置，因此，监控请求消息中所携带的各配置参数只针对本次指示的监控事件配置有效。
进一步需要说明的是，若监控请求消息中既不携带最大报告次数也不携带监控持续时间，则表示监控请求为一次监控请求，或者可以理解为临时监控请求。
步骤102，SCEF基于监控请求，确定监控事件配置的信息。
具体的，SCEF接收到监控请求后，获取并保存其中携带的参数。以及，SCEF基于各参数，对监控请求进行授权，授权可以理解为确认监控请求是否有效，即，是否满足运营商的策略和签约。
其中，SCEF Reference ID是SCEF基于TLTRI为该监控事件配置分配的标识信息。SCEF保存SCEF Reference ID和TLTRI的对应关系。
步骤103，SCEF向HSS发送监控请求消息。
具体的，SCEF向HSS发送监控请求消息，用于指示HSS对监控事件配置进行相应配置，也可以理解为指示HSS确定监控事件配置的信息。
示例性的，监控请求消息中包括但不限于：External Group ID、SCEF的标识信息、SCEF Reference ID、Monitoring Type。可选地，监控请求消息中还可以包括步骤101中的监控请求消息中的部分或全部参数，例如可以包括SCS/AS的标识信息、T8的目的地址信息等，本申请不做限定。
步骤104，HSS基于监控请求消息，确定监控事件配置的信息。
具体的，HSS接收监控请求消息，获取监控请求消息中携带的参数，HSS基于获取到的各参数，检查监控请求消息是否满足网络策略，并在检查监控请求消息满足网络策 略后，保存监控请求消息中的各参数，创建监控事件配置(即确定监控事件配置的信息)。
具体的，HSS保存有签约信息，HSS可基于External Group ID对签约信息进行匹配，确定对应的用户组及其包括的组成员。示例性的，HSS存储有签约信息，签约信息包括但不限于：用户和用户组的对应关系。HSS可基于External Group ID，检索到对应的用户组，并获取到用户组中的多个用户，具体为获取到各用户对应的用户的标识信息，用户的标识信息可以为用户外部标识或者是移动用户国际综合业务数字网号码(Mobile Subscriber International ISDN number，MSISDN)。
可选地，HSS还保存各用户与MME的对应关系。具体的，架构中可包括多个MME，用户组内的各用户对应的MME可以相同，也可以不同，本申请不做限定。
步骤105，HSS向SCEF发送确认消息。
具体的，HSS向SCEF发送确认消息，消息中携带SCEF Reference ID、接受指示信息以及用户组中的组成员数量或者用户组中的组成员的用户标识信息。其中，接受指示信息用于指示HSS接受SCEF发送的携带SCEF Reference ID的监控请求消息，也可以理解为，HSS已完成SCEF Reference ID对应的事件监控的配置。
步骤106，SCEF向SCS/AS发送确认消息。
具体的，SCEF接收到HSS发送的确认消息后，SCEF创建监控事件配置(即确定监控事件配置的信息)，监控事件配置的信息可包括用户组的监控事件配置的信息和组成员用户的监控事件配置的信息，其中，用户组的监控事件配置的信息包括事件监控类型、External Group ID、SCS/AS的标识信息、T8的目的地址信息、SCEF Reference ID和TLTRI，组成员用户的监控事件配置的信息包括用户组的组成员信息(例如组成员的数量或者组成员标识列表)以及后续的每个组成员用户的已报告次数。用户组的监控事件配置信息还包括但不限于以下至少之一：最大报告次数、监控持续时间等。
接着，SCEF向SCS/AS发送确认消息，消息中包括但不限于：接受指示信息和TLTRI，接受指示信息用于指示SCEF已完成与TLTRI对应的事件监控的配置。
可选地，步骤105至步骤106也可以在步骤109之后执行，本申请不做限定。
步骤107，HSS向MME/SGSN发送插入签约用户数据请求消息。
具体的，如步骤104所述，HSS可获取到用户组中的用户及其对应的用户标识信息。HSS针对每个用户向该用户对应的MME/SGSN发送插入签约用户数据请求(Insert Subscriber Data Request)消息，也就是说，针对用户组中的每个用户，HSS重复步骤107至步骤109。
具体的，HSS为单一用户向该用户对应的MME/SGSN发送插入签约用户数据请求消息，用于指示MME/SGSN对该用户进行事件监控。示例性的，消息中包括但不限于：Monitoring type，SCEF的标识信息、SCEF Reference ID、最大报告次数和/或监控持续时间、用户的外部标识或MSISDN。
步骤108，MME/SGSN执行事件监控。
具体的，MME/SGSN接收HSS发送的插入签约用户数据请求消息，并获取其携带的各参数。示例性的，MME/SGSN确定用户的监控事件配置的信息，包括：SCEF的标识信息、SCEF Reference ID、Monitoring type、用户的外部标识或MSISDN、最大报告次 数和/或监控持续时间。
HSS针对用户组中的每个用户请求MME/SGSN进行事件监控后，各个MME/SGSN可根据插入签约用户数据请求消息，对用户组对应的监控事件配置中的各用户进行事件监控。
如上文所述，每个用户可对应不同的用户组，每个用户组可对应不同的监控事件配置，也就是说，如果要对用户组配置不同的监控事件，则重复执行步骤101至步骤108，即，同一个用户组的不同事件监控对应有不同的监控事件配置的信息，例如：对应有不同的TLTRI和SCEF Reference ID。
步骤109，MME/SGSN向HSS发送插入签约用户数据响应消息。
具体的，MME/SGSN对监控事件配置成功后，向HHS发送插入签约用户数据响应消息，消息中携带接受指示信息，用于指示MME/SGSN成功执行了监控事件配置。
需要说明的是HSS是针对每一个用户执行的步骤107至步骤109，因此，MME/SGSN发送的插入签约用户数据响应消息可以不携带用户的标识信息，HSS可获知当前接收到的插入签约用户签约数据响应消息是针对当前用户的。
b.基于4G网络的业务能力开放架构的监控事件的报告流程。
如图4所示为示例性示出的监控事件的报告流程示意图，参照图4，具体的：
步骤201，MME/SGSN检测到监控事件。
具体的，如上文所述，MME/SGSN对监控事件配置中的用户进行事件监控，在本实施例中，MME/SGSN检测到用户的监控事件。
步骤202，MME/SGSN向SCEF发送监控指示消息。
具体的，MME/SGSN检测到用户的监控事件后，向SCEF发送监控指示消息，用于指示用户存在监控事件。
示例性的，消息中包括但不限于：SCEF Reference ID、监控事件报告和用户的标识信息，用于指示SCEF Reference ID对应的监控事件配置中，该用户的标识信息对应的用户存在监控事件，监控事件报告包括但不限于监控事件的类型。
举例说明：MME/SGSN检测到用户1存在Loss of connectivity监控事件，MME/SGSN向SCEF发送监控指示消息，消息中携带用户1的用户的标识信息，例如用户1的用户的外部标识，还携带有监控事件配置1对应的SCEF Reference ID1，以及监控事件报告。
如上文所述，MME/SGSN可能会存储有对应于该监控事件配置的剩余报告次数，即在监控事件配置成功时，将剩余报告次数设置为最大报告次数的取值，MME/SGSN若上报一次监控事件报告，则将剩余报告次数减1。示例性的，若剩余报告次数为0，则MME/SGSN删除本地存储的该用户的监控事件配置的信息，也就是说，MME/SGSN停止对监控事件配置中的该用户进行事件监控。
在一种可能的实现方式中，若监控事件配置为一次事件监控，则MME/SGSN向SCEF发送监控指示消息后，删除该用户的监控事件配置的信息。
步骤203，SCEF处理。
具体的，SCEF接收到监控指示消息后，保存该用户对应的已报告事件的次数。
一个示例中，若用户组中的各用户的已报告事件的次数均达到最大报告次数，则SCEF确定该监控事件配置的报告完成，并删除该用户组对应的已达到最大监控次数对应的监控事件配置，以及指示HSS删除该监控事件配置。
另一个实例中，若用户组中的各用户的每一个监控类型的已报告事件的次数均达到最大报告次数，则SCEF确定该监控事件配置的报告完成，并删除该用户组对应的已达到最大监控次数对应的监控事件配置，以及指示HSS删除该监控事件配置。
步骤204，SCEF向SCS/AS发送监控指示消息。
具体的，SCEF向SCS/AS发送监控指示消息，用于指示用户存在监控事件。
示例性的，消息中包括但不限于：TLTRI、监控事件报告和用户的标识信息。其中，TLTRI是SCEF基于SCEF Reference ID查找到的。
可选地，SCEF可能会汇聚多个来自MME/SGSN的事件报告，SCEF可在一条监控指示消息中携带事件报告列表，列表中包括TLTRI、监控事件报告、用户的标识信息的对应关系。
步骤205，SCS/AS向SCEF返回确认消息。
c.基于5G网络的业务能力开放架构的监控事件的配置流程，该流程中监控事件配置也称为监控事件订阅(Monitoring Event Subscription)流程，而监控请求也称为监控事件订阅请求(Event Subscription Request)，监控类型信息也称为事件标识(Event Id)。
如图5所示为示例性示出的监控事件的订阅流程示意图，参照图5，具体的：
步骤301，AF向NEF发送监控事件订阅请求消息。
具体的，AF向NEF发送监控事件订阅请求消息，用于指示配置用户组的监控事件(也称为进行监控事件订阅)。示例性的，监控事件订阅请求消息中包括但不限于：AF的通知端点、事件标识、External Group ID。
其中，AF的通知端点为AF为该监控事件订阅分配的标识信息，在后续NEF向AF发送事件报告是携带该通知端点，用于关联监控事件订阅。示例性的，AF的通知端点可以为目标通知地址信息，或者，目标通知地址信息和通知关联标识信息。
可选地，消息中携带的事件标识可以为一个或多个，也就是说，单一监控事件订阅可以对应一个或多个事件标识。
可选地，监控事件订阅消息中还可以携带监控事件报告模式，用于指示监控事件的最大报告次数、周期性报告方式或监控持续时长等。
其他细节可参照步骤101，此处不赘述。
步骤302，NEF基于监控事件订阅请求消息，确定监控事件订阅的信息。
具体的，对监控事件订阅授权，并保存监控事件订阅请求消息中的各参数。
其他细节与步骤102类似，此处不赘述。
步骤303，NEF向UDM发送监控事件订阅请求消息。
具体的，NEF向UDM发送监控事件订阅请求消息，用于进行监控事件订阅。
示例性的，监控事件订阅请求消息中包括但不限于：External Group ID、事件标识、NEF的通知端点等。可选地，消息中还可以包括步骤301中的部分或全部参数，具体可 参照已有技术，本申请不做限定。
其中，NEF的通知端点，是NEF为该事件监控配置分配的标识信息在后续向NEF发送事件报告是携带该通知端点，用于关联监控事件订阅。
步骤304，UDM基于监控事件订阅请求消息，创建监控事件订阅。
具体的，UDM检查NEF发送的监控事件订阅请求消息是否满足网络策略，并在检查监控事件订阅请求消息满足网络策略后，保存监控事件订阅请求消息中的各参数，以创建监控事件订阅，也可以理解为确定监控事件订阅的信息，其中监控事件订阅的信息即为保存的各参数，包括但不限于：External Group ID、事件标识、NEF的通知端点等。
示例性的，UDM可基于本地存储的签约信息，查找到与External Group ID对应的内部组标识，并基于内部组标识查找到对应的组成员及各组成员的用户的外部标识或MSISDN。以及，UDM确定正在服务用户组中的用户对应的AMF或SMF，UDM向每一个服务用户组用户的AMF或SMF执行步骤305a或步骤305b。
步骤305a，UDM向AMF监控事件订阅请求消息。
具体的，UDM向AMF发送监控事件订阅请求消息，用于指示AMF对该用户组的成员用户进行事件监控。
示例性的，消息中可包括NEF通知端点、内部组标识信息，以及事件标识。消息中还可以包括步骤301中的部分可选参数，具体可参照已有技术，本申请不做限定。
步骤306a，AMF返回确认消息。
具体的，AMF基于监控事件订阅请求消息中的各参数，确定监控事件订阅的信息，其中，监控事件订阅的信息可以包括用户组的监控事件订阅的信息和各个组成员用户的监控事件订阅信息。
示例性的，用户组的监控事件订阅的信息包括：AMF订阅关联标识、NEF通知端点、事件监控模式、事件监控类型信息等。组成员用户的监控事件订阅的信息包括：剩余报告次数(初始值根据最大报告次数设置)等。
可选地，用户组的监控事件订阅的信息可以写入用户组的上下文中，用户的监控事件订阅的信息可以写入用户的上下文中。
需要说明的是，用户与用户组的对应关系已预先存储在各网元中。
AMF基于监控事件订阅的信息，对用户执行事件监控，并向UDM发送确认消息，消息中包括AMF订阅关联标识。相应的，UDM将AMF订阅关联表示写入该监控事件订阅的信息中。
步骤305b，UDM向SMF发送监控事件订阅请求消息。
与步骤305a类似，此处不赘述。
步骤306b，SMF返回确认消息。
具体的，SMF基于监控事件订阅请求消息中的各参数，确定监控事件订阅的信息。
示例性的，监控事件订阅的信息包括但不限于：事件监控模式、SMF订阅关联标识、NEF通知端点和事件监控类型信息等。其中，SMF订阅关联标识为SMF为该监控事件订阅分配的标识。
SMF对用户执行事件监控，并向UDM发送确认消息，消息中包括SMF订阅关联标 识。相应的，UDM将SMF订阅关联表示写入用户的监控事件订阅的信息中。
其他细节与步骤306a类似，此处不赘述。
步骤307，UDM向NEF发送确认消息。
示例性的，UDM确定向所有服务用户组的AMF或SMF均已完成监控事件订阅后，UDM向NEF发送确认消息，确认消息中包括但不限于：接受指示信息、UDM订阅关联标识、用户组的成员用户数量或组成员用户的标识列表。
其它细节可参照步骤105，此处不赘述。
步骤308，NEF向SCS/AS发送确认消息。
具体地，NEF接收到UDM发送的确认消息后，基于确认消息，确定监控事件订阅的信息。监控事件订阅的信息可以包括但不限于：用户组的监控事件订阅的信息和成员用户的监控事件订阅的信息。示例性的，用户组的监控事件订阅的信息包括AF的通知端点、事件标识、External Group ID、NEF的通知端点、UDM的订阅关联标识以及事件监控报告模式，组成员用户的监控事件订阅信息包括组成员信息(例如组成员的数量或者组成员标识列表)以及后续的每个组成员用户的已报告次数。用户组的监控事件配置信息还包括但不限于以下至少之一：最大报告次数、监控持续时间等。
示例性的，NEF向SCS/AS发送确认消息，消息中携带接受指示信息和NEF订阅关联标识，以指示NEF完成监控事件的订阅。
d.基于5G网络的业务能力开放架构的监控事件的报告流程。
如图6所示为示例性示出的事件监控的监控流程示意图，参照图6，具体的：
步骤401a，AMF检测到监控事件。
具体细节与步骤201类似，此处不赘述。
步骤402a，AMF向NEF发送事件通知消息。
具体的，AMF检测到监控事件后，向NEF发送事件通知消息，消息中包括NEF的通知端点、监控事件报告和用户的外部标识信息。并且，AMF将用户的监控事件订阅的信息中的剩余报告次数减1。
其他细节与步骤202类似，此处不赘述。
步骤403a，NEF向AMF发送确认消息。
具体的，NEF向AMF发送确认消息，以指示接收到AMF发送的事件通知消息。
步骤401b，SMF检测到监控事件。
具体细节与步骤201类似，此处不赘述。
步骤402b，SMF向NEF发送事件通知消息。
具体的，SMF检测到监控事件后，向NEF发送事件通知消息，消息中包括NEF的通知端点、监控事件报告和用户的外部标识信息。并且，SMF将用户的监控事件订阅的信息中的剩余报告次数减1。
其他细节与步骤202类似，此处不赘述。
步骤403b，NEF向SMF发送确认消息。
具体的，NEF向SMF发送确认消息，以指示接收到SMF发送的监控指示消息。
步骤404，NEF处理。
具体的，NEF接收到AMF或SMF的事件通知消息后，保存该用户对应的已报告事件的次数。
一个示例中，若监控事件订阅对应的用户组中的各用户的已报告事件的次数均达到最大报告次数，则NEF确定监控事件订阅的报告完成，并删除该监控事件订阅，以及指示UDM删除该监控事件订阅。
另一个示例中，若用户组中的各用户的每一个事件标识的已报告事件的次数均达到最大报告次数，则NEF确定该监控事件订阅的报告完成，并删除该监控事件订阅，以及指示UDM删除该监控事件订阅。
步骤405，NEF向AF发送事件通知消息。
具体的，NEF向AF发送事件通知消息，用于指示用户存在监控事件。消息中携带AF的通知端点、监控事件报告和用户的外部标识信息。
其他细节可参照步骤204，此处不赘述。
步骤406，AF向NEF返回确认消息。
3)事件监控管理
下面分别对4G/5G业务能力开放架构中的监控事件配置管理方法进行详细说明：
a.基于4G网络的业务能力开放架构的监控事件配置的管理流程。
如图7所示为示例性示出的事件监控的管理流程示意图，参照图7，具体的：
步骤501，SCS/AS向SCEF发送监控请求消息。
具体的，SCE/AS向SCEF发送监控请求消息，消息中携带TLTRI和删除指示信息，用于指示取消(删除)TLTRI对应的监控事件配置，也可以理解为，将用户组对应的一个或多个监控事件配置中与TLTRI对应的监控事件配置删除，即，不再针对该监控事件配置对用户组进行监控。
步骤502，SCEF向HSS发送监控请求消息。
具体的，SCEF基于TLTRI可确定对应的SCEF Reference ID，SCEF向HSS发送监控请求消息，消息中携带SCEF Reference ID和删除指示信息。
步骤503，HSS根据SCEF Reference ID确定需要删除的监控事件配置。
具体的，如上文所述，HSS存储有一个或多个监控事件配置的信息，HSS可基于SCEF Reference ID查找到对应的监控事件配置的信息，并获取对应的用户组中的用户。
步骤504，HSS向SCEF发送确认消息。
具体的，HSS向SCEF发送确认消息，用于指示已接收到SCEF发送的监控请求消息。
步骤505，SCEF向SCS/AS发送确认消息。
具体的，SCEF向SCS/AS发送确认消息，用于指示已接收到SCS/AS发送的监控请求消息。
步骤506，HSS向MME/SGSN发送插入签约用户数据请求消息。
具体的，HSS确定该监控事件配置对应的用户后，针对每个用户重复执行步骤506， 其中，插入签约用户数据请求消息中包括但不限于：SCEF Reference ID、用户的标识信息(例如用户的外部标识信息)和删除指示信息。
步骤507，MME/SGSN根据插入签约用户数据请求消息，删除监控事件配置的信息。
具体的，MME/SGSN根据插入签约用户数据请求消息中的SCEF Reference ID确定监控事件配置，并删除该监控事件配置中所述用户的标识信息对应的用户的监控事件配置。
步骤508，MME/SGSN向HSS发送插入签约用户数据响应消息。
MME/SGSN对用户执行删除监控事件配置的操作后，向HSS发送插入签约用户数据响应消息，以指示对应于该用户的删除操作已完成。
HSS针对监控事件配置中的其它用户重复执行步骤506～步骤508，直至监控事件配置对应的所有用户完成删除监控事件配置的操作。
b.基于5G网络的业务能力开放架构的监控事件订阅的管理流程。
如图8所示为示例性示出的事件监控的管理流程示意图，参照图8，具体的：
步骤601，AF向NEF发送事件订阅请求消息。
具体的，AF向NEF发送监控事件订阅请求消息，消息中携带NEF订阅关联标识和删除指示信息。
步骤602，NEF向UDM发送监控事件订阅请求消息。
具体的，NEF基于NEF订阅关联标识可确定对应的UDM订阅关联标识，NEF向发送监控事件订阅请求消息，消息中携带UDM订阅关联标识和删除指示信息。
步骤603a，UDM向AMF发送监控事件订阅请求消息。
具体的，如上文所述，UDM存储有监控事件订阅的信息，UDM可基于UDM订阅关联标识查找到对应的监控事件订阅的信息，并获取对应AMF订阅关联标识或SMF订阅关联标识。对每一个AMF执行步骤603a～步骤605a，对每一个SMF执行步骤603b～步骤605b。
具体的，UDM向AMF发送监控事件订阅请求消息，消息中包括AMF订阅关联标识和删除指示信息。
步骤604a，AMF根据监控事件订阅请求消息，删除监控事件订阅的信息。
具体的，AMF根据监控事件订阅请求消息中的AMF订阅关联标识确定监控事件订阅，并删除该监控事件订阅。
步骤605a，AMF向UDM发送确认消息。
步骤603b，UDM向SMF发送监控事件订阅请求消息。
具体的，UDM向SMF发送监控事件订阅请求消息，消息中包括SMF订阅关联标识和删除指示信息。
步骤604b，SMF根据监控事件订阅请求消息，删除监控事件订阅的信息。
具体的，SMF根据监控事件订阅请求消息中的SMF订阅关联标识确定监控事件订阅，并删除该监控事件订阅的信息。
步骤605b，SMF向UDM发送确认消息。
步骤606，UDM向NEF发送确认消息。
具体的，UDM确定监控事件订阅对应的所有AMF/SMF执行监控事件订阅删除后，UDM删除监控事件订阅，并向NEF发送确认消息，消息中携带UDM接受指示信息。
步骤607，NEF向AF发送确认消息。
具体的，NEF删除监控事件订阅，并向AF发送确认消息，消息中携带接受指示信息。
由上文可知，在已有技术中，对于监控事件配置(在5G中也称监控事件订阅)的管理均是针对用户组的，例如，如果需要删除监控事件配置，则需要将监控事件配置对应的用户组的所有用户的监控事件配置均删除，并且，已有技术目前无法实现在监控事件配置对应的用户组中添加或者删除用户，也就是说，已有技术中无法以用户为粒度执行事件监控的管理。
本申请提出一种事件监控管理方法，能够克服已有技术存在的缺陷。具体的，本申请的事件监控管理方法能够应用于4G网络和5G网络，下面结合不同的应用场景对本申请中的监控管理方法进行详细说明，具体的，本申请中可实现针对用户的监控事件配置的取消操作，以及，在用户组中增加用户和删除用户的管理方式，场景一为4G网络中的取消用户的监控事件配置的具体实施例，场景二为4G网络中在用户组中增加或删除用户的具体实施例，场景三为5G网络中的取消用户的监控事件配置的具体实施例，场景四为5G网络中的增加或删除用户的监控事件配置的具体实施例。
场景一
结合图1，如图9所示为本申请实施例中的事件监控管理方法的流程示意图，在图9中：
具体的，事件监控的配置以及监控流程均可参照图3和图4所示的实施例，此处不赘述。
步骤701，SCS/AS向SCEF发送监控请求消息。
具体的，SCS/AS向SCEF发送监控请求消息，用于指示取消监控事件配置中的用户的事件监控。
示例性的，消息中包括但不限于：监控事件配置的标识信息、用户的标识信息和取消指示信息。
其中，监控事件配置的标识信息用于指示对应的监控事件配置，示例性的，监控事件配置的标识信息可以为TLTRI。
用户的标识信息用于标识对应的用户，示例性的，用户的标识信息可以为用户的外部标识信息或者是MSIMSN。
取消指示信息用于指示取消指定监控事件配置中的指定用户的事件监控。需要说明的是，指定监控事件配置是指监控事件配置的标识信息所标识的监控事件配置，指定用户是指监控事件配置对应的用户组中的一个或多个用户，也就是用户的标识信息所对应的用户。可选地，监控请求消息中可携带一个或多个用户的标识信息，也就是说，SCS/AS 可以指示取消指定监控事件配置中的一个或多个用户的事件监控。
在一种可能的实现方式中，监控请求消息中还可以包括一个或多个事件监控类型信息，如上文所述，在监控事件配置过程中，单一监控事件配置可以对应一个或多个事件监控类型，在本申请中，SCS/AS可以指示取消监控事件配置中的指定用户的一个或多个事件监控类型对应的事件监控。
举例说明：用户1属于用户组1，用户组1对应监控事件配置1和监控事件配置2，其中，监控事件配置1对应监控事件类型1和监控事件类型2。示例性的，SCS/AS可指示取消监控事件配置1的用户1对应的事件监控类型1对应的事件监控，也就是说，只停止(或取消)对监控事件配置1中的用户1的指定事件监控类型的监控，对于用户1的其它监控事件配置继续进行监控。示例性的，SCS/AS向SCEF发送的监控请求消息中包括：监控事件配置1的标识信息(例如TLTRI1)、用户1的标识信息、事件监控类型1和取消指示信息。
步骤702，SCEF根据监控请求消息，确定监控事件配置的信息。
具体的，SCEF接收SCS/AS发送的监控请求消息，并获取其携带的参数，并基于获取到的参数，对监控事件配置的信息进行更新，本步骤中对监控事件配置的更新的目的为在统计监控事件配置对应的用户组成员用户的报告时，剔除用户(具体是指需要进行取消监控的用户)的报告。
具体的，SCEF可基于监控事件配置的标识信息，查询对应的监控事件配置的信息，如上文所述，监控事件配置的信息包括但不限于以下至少之一：用户组的组成员数量或组成员用户的标识列表、各成员用户的已报告次数、最大报告次数、用户组的标识信息、监控事件配置的标识信息等。
在监控事件配置对应的用户组中的各用户的已报告事件的次数均达到最大报告次数时(即不区分监控类型)表示监控事件配置的报告完成的情况下(即最大报告次数是每用户粒度)，在本申请中，为实现剔除用户的报告的目的，对监控事件配置的信息更新的方式可以包括以下至少之一：
方式一：SCEF记录用户的标识信息和标记信息，其中，标记信息用于指示该用户为被剔除用户。
方式二：SCEF将该用户的报告次数设置为最大报告次数，即SCEF默认为该用户的报告已完成。
方式三：SCEF将监控事件配置对应的用户组的组成员数量减去需要剔除的用户的数量。
方式四：SCEF从保存的用户组的用户列表中删除该用户，该方式的前提是SCEF保存了用户组的用户标识列表。
方式五：SCEF将已接收到的该用户的报告删除，并且对应的用户组的组成员数量减去需要剔除的用户的数量。
方式六：SCEF将已接收到的该用户的报告删除，并且SCEF记录用户的标识信息和标记信息。
方式七：SCEF将已接收到的该用户的报告删除，并且SCEF从保存的用户组的用户 列表中删除该用户。
需要说明的是，方式五至方式七的执行的前提是已经接收到该用户的报告。
下面对上述几种方式进行说明：
针对方式一，更新后的监控事件配置包括用户的标识信息和标记信息的对应关系，示例性的，标记信息可写入用户的监控事件配置的信息中，SCEF在对该监控事件配置的用户组的报告进行统计时，可根据标记信息，确定在该监控事件配置中，忽略(或剔除)该用户的报告。
针对方式二，通过将待取消用户的报告设置为最大报告次数，即SCEF默认为该用户的报告已完成。
针对方式三，如上文所述，SCEF在检测监控事件配置的报告是否完成时，具体是统计达到最大报告次数的用户的数量是否等于监控事件配置的用户组的组成员数量，SCEF将用户组的组成员数量减去需要剔除的用户的数量，则SCEF在统计时，只需要检测达到最大报告次数的用户的数量是否等于已更新后的用户组组成员数量即可。举例说明：若监控事件配置1对应的用户组1的组成员数量为3个，SCEF基于指示确定需要取消监控事件配置1的用户1的事件监控，SCEF可将监控事件配置1对应的用户组1的组成员数量更新为2个，即只要统计到有2个用户的报告达到最大监控次数，可确定监控事件配置1的报告完成。
针对方式四，如上文所述，SCEF保存有用户组的用户标识列表，SCEF将用户从用户标识列表中删除，SCEF在统计用户组的监控事件报告时，只对用户标识列表中标识的用户的监控事件报告的次数进行统计，从而实现剔除用户的目的。
针对方式五至方式七，在SCEF上，用户的监控事件配置的信息可能还包括已上报的报告，SCEF将监控事件配置中该用户的报告删除，同时可结合方式一、方式三和方式四，从而实现剔除用户的目的。
在一种可能的实现方式中，方式三还可以结合方式一，以防止信号传输时延造成的统计错误，具体的，SCEF处理之后，会指示MME/SGSN取消对该用户的事件监控，相应的，MME将不会再上报该用户的报告，但是，由于信号的时延或设备的处理能力的限制或者是时间上的误差，可能会导致MME在接收到SCEF的指示之前，就上报了用户的报告，则SCEF统计报告时，会出现错误。因此，SCEF可结合方式三和方式一，将用户进行标记，并更新用户组的组成员数量。
综上，更新后的监控事件配置的信息可用于指示SCEF在统计监控事件配置的报告时，剔除该用户的报告。如上文所述，SCEF在统计监控事件配置的报告是否完成时，是基于是否接收到该监控事件配置对应的所有用户的最大报告次数的报告。在本申请中，若取消对监控事件配置的用户的监控，则SCEF在统计事件监控的报告时，忽略该用户的报告，也就是说，只统计除该用户以外的其他用户的报告。
需要说明的是，若SCS/AS请求消息的是取消用户的部分事件监控，也就是说，步骤701中的监控请求消息中携带有事件监控类型信息，则SCEF无需执行上述步骤，也就是说，SCEF接收到监控请求消息后，执行步骤703。
在监控事件配置对应的用户组中的各用户的每一个监控类型已报告事件的次数均达到最大报告次数时(即区分监控类型)表示监控事件配置的报告完成的情况下(即最大报告次数是每用户每监控类型粒度)，在本申请中，若监控请求消息中还可以包括一个或多个事件监控类型信息，为实现剔除用户的报告的目的，对监控事件配置的信息更新的方式可以包括以下至少之一：
方式一：SCEF记录用户的标识信息、监控类型信息和标记信息，其中，标记信息用于指示该用户为被剔除用户、监控类型信息为需要被剔除的监控类型。
方式二：SCEF将该用户的每一个监控类型的报告次数设置为最大报告次数，即SCEF默认为该用户的报告已完成。
综上，更新后的监控事件配置的信息可用于指示SCEF在统计监控事件配置的报告时，剔除该用户需要取消监控事件类型的报告。如上文所述，SCEF在统计监控事件配置的报告是否完成时，是基于是否接收到该监控事件配置对应的所有用户的最大报告次数的报告。在本申请中，若取消对监控事件配置的用户的需要取消的监控事件类型的监控，则SCEF在统计事件监控的报告时，忽略该用户的特定监控事件类型的报告，也就是说，只统计除该用户以外的其他用户的报告以及该用户特定监控事件类型以为的报告。
需要说明的是，若SCEF在更新监控事件配置的信息后判断该监控事件配置的事件报告完成，则立即向HSS发送请求监控指示信息，消息中包括消息中携带SCEF Reference ID和删除指示信息。HSS根据SCEF Reference ID确定需要删除的监控事件配置；否则当接收到后续的监控事件报告后，判断监控事件配置的事件报告完成，向HSS发送请求监控指示信息，请求删除该监控事件报告。
步骤703，SCEF向HSS发送监控指示消息。
具体的，SCEF向HSS发送监控请求消息，监控请求消息中包括监控事件配置的标识信息、用户的标识信息和取消指示信息。
示例性的，该监控请求消息中的监控事件配置的标识信息可以为SCEF Reference ID，具体的，SCEF可基于TLTRI，确定对应的SCEF Reference ID，并携带在监控请求消息中发送给HSS。
可选地，监控请求消息中还可以携带一个或多个事件监控类型信息，用于指示取消监控事件配置中的该用户的指定类型的事件监控。
可选地，监控请求消息中还可以携带生效指示信息，用于指示该取消操作一直生效，也就是说，当该监控事件配置被删除后，取消操作仍然生效。当后续SCS/AS重新针对这个用户组执行监控事件配置后，HSS根据生效指示信息，在发送给SCEF的用户组成员用户信息时，剔除该用户，并且指示MME/SGSN不对该用户进行事件监控。示例性的，生效指示信息可以包括以下至少之一：用户的标识信息、事件监控类型、SCS/AS的标识信息。
步骤704，HSS处理。
具体的，HSS接收到监控指示消息后，保存监控指示消息中携带的各参数。并且，HSS基于用户的标识信息，查找用户对应的MME/SGSN。
步骤705，HSS向SCEF返回确认消息。
具体的，HSS向SCEF发送确认消息，消息中可包括接受指示信息，以指示HSS已接受SCEF发送的监控指示消息。
步骤706，SCEF向SCS/AS返回确认消息。
具体的，SCEF向SCS/AS发送确认消息，消息中可包括接受指示信息，以指示SCEF已接受SCS/AS发送的监控指示消息。
步骤707，HSS向MME/SGSN发送插入签约用户数据请求消息。
具体的，HSS查询到用户对应的MME/SGSN后，向该MME/SGSN发送插入签约用户请求消息，消息中包括但不限于：用户的标识信息、监控事件配置的标识信息和取消指示信息。
示例性的，该插入签约用户请求消息中的用户的标识信息可以为用户的内部标识信息。具体的，HSS可从签约信息中查找到与用户的外部标识对应的用户的内部标识信息，并携带在插入签约用户请求消息中发送给MME/SGSN。
示例性的，HSS向MME/SGSN发送的插入签约用户数据请求消息中的监控事件配置信息可以为SCEF Reference ID。
可选地，消息中还可以携带事件监控类型信息，用于指示MME/SGSN取消监控事件配置中的用户的指定类型的事件监控。
步骤708，MME/SGSN取消监控事件配置的用户的事件监控。
具体的，MME/SGSN接收到插入签约用户请求消息，基于插入签约用户请求消息，执行对监控事件配置的用户的事件监控的取消操作。
具体的，如上文所述，MME/SGSN是基于监控事件配置对用户组的各用户执行监控的，监控事件配置包括但不限于：监控事件配置的标识信息、事件监控类型信息、用户的标识信息、最大报告次数等。在本申请中，MME/SGSN可基于插入签约用户请求消息中的事件配置的标识信息查找到对应监控事件配置及其信息，并基于用户的标识信息查找到监控事件配置中需要取消监控的用户，MME/SGSN取消对该监控事件配置的用户的事件监控，并删除用户的监控事件配置的信息，具体是指删除用户的需要取消的监控事件配置对应的信息。
在一种可能的实现方式中，若需要取消的是监控事件配置中的用户的部分事件监控，即，插入签约用户请求消息包括事件监控类型信息，则MME/SGSN取消监控事件配置的用户的事件监控类型对应的事件监控，并继续对该用户的其它事件监控类型的事件监控，以及，MME/SGSN删除用户的监控事件配置中与需要取消的事件监控类型对应的监控事件配置。
最大报告次数是每用户粒度时，举例说明如下：用户1属于用户组1，用户组1对应监控事件配置1和监控事件配置2，其中，监控事件配置1中包括事件监控类型1和事件监控类型2，本实施例中需要取消监控事件配置1中的用户的事件监控类型1，用户1的上下文中包括对应于监控事件配置1的信息和监控事件配置2的信息，例如，MME/SGSN根据指示，取消对监控事件配置1中的用户1的事件监控类型1的事件监控，并且MME/SGSN继续保持对监控事件配置1的用户1的事件监控类型2的事件监控，以及对监控事件配置2的用户1的事件监控。
最大报告次数是每用户每监控类型粒度时，举例说明：用户1属于用户组1，用户组1对应监控事件配置1和监控事件配置2，其中，监控事件配置1中包括事件监控类型1和事件监控类型2，本实施例中需要取消监控事件配置1中的用户的事件监控类型1，用户1的上下文中包括对应于监控事件配置1的信息和监控事件配置2的信息，例如，监控事件配置1的信息包括事件监控类型1的剩余报告次数为3，事件监控类型2的剩余报告次数为1，监控事件配置2的信息包括剩余报告次数为2，MME/SGSN根据指示，取消对监控事件配置1中的用户1的事件监控类型1的事件监控，并且删除用户的上下文中的事件监控类型1的剩余报告次数或将剩余报告次数设为0，以及，MME/SGSN继续保持对监控事件配置1的用户1的事件监控类型2的事件监控，以及对监控事件配置2的用户1的事件监控。
步骤709，MME/SGSN向HSS发送插入签约用户数据响应消息。
具体的，MME/SGSN取消用户的事件监控后，向HSS发送插入签约用户数据响应消息，用于指示MME/SGSN已对当前用户执行取消操作。
需要说明的是，如果取消监控事件配置中的多个用户的事件监控，则HSS针对每一个需要取消的用户执行步骤707至步骤709，也就是说，HSS接收到MME返回的插入签约用户数据响应消息后，再针对另一个用户执行步骤707至步骤709，直至所有需要取消的用户均执行完毕。
在其他优选实施例中，HSS根据签约信息或运营商的策略决定取消监控事件配置中用户的事件监控，具体流程为步骤701-步骤703不执行，执行步骤704-步骤709，不同之处在于：
步骤704：HSS根据签约信息或运营商的策略决定取消监控事件配置中该用户的事件监控；
步骤705：HSS向SCEF发送监控指示消息；
步骤706：SCEF向SCS/AS发送监控指示消息。
在上述实施例中，若SCEF在更新监控事件配置的信息后判断针对该用户组的报告已经完成，则SCEF向HSS发送取消订阅的请求消息，HSS进一步向MME/SGSN发送取消订阅的请求消息。
场景二
结合图1，如图10所示为本申请实施例中的事件监控管理方法的流程示意图，在图10中：
具体的，事件监控的配置以及监控流程均可参照图3和图4所示的实施例，此处不赘述。
步骤801，SCS/AS向SCEF发送组用户配置管理请求消息。
具体的，SCS/AS向SCEF发送监控请求消息，用于指示SCEF从用户组中删除用户，或者，在用户组中增加用户。与场景一中取消监控事件配置的用户的事件监控不同，场景一中是指针对指定监控事件配置中的用户的事件监控进行操作，而本场景中是针对用户在其所属用户组的所有监控事件配置的操作。
示例性的，消息中包括但不限于：用户组的标识信息、用户的标识信息和指示信息， 指示信息可以为删除指示信息，用于指示从用户组中删除用户。指示信息可以为增加指示信息，用于指示在用户组中增加用户。
示例性的，用户组的标识信息可以为用户组的外部标识信息，用户的标识信息可以为用户的外部标识信息。
可选地，消息中的用户的标识信息可以为一个或多个，用于指示在用户组中删除一个或多个用户，或者增加一个或多个用户。
步骤802，SCEF向HSS发送组用户管理请求消息。
具体的，SCEF向HSS发送用户管理请求消息，用于指示HSS更新签约信息。
示例性的，消息中包括但不限于：用户组的标识信息、用户的标识信息和指示信息。例如：用户组的外部标识信息、用户的外部标识信息和指示信息。
步骤803，HSS基于组用户管理请求消息，更新签约信息。
具体的，如上文所述，HSS保存有签约信息，在本实施例中，若需要在用户组中增加或者删除用户，则HSS对应更新签约信息。
具体的，HSS可基于用户组的外部标识信息，查找对应的用户组，具体为查找对应的用户组的内部标识信息，以确定用户组及其对应的用户组列表，用户组列表中包括一个或多个用户对应的用户的内部标识信息。
一个示例中，若指示信息为删除指示信息，则HSS基于用户的外部标识确定用户的内部标识，并将用户的内部标识与用户组列表进行匹配，并从用户组列表中删除匹配成功的用户的内部标识信息。
另一个示例中，若指示信息为增加指示信息，则HSS基于用户的外部标识确定用户的内部标识，并在用户组列表中增加该用户的内部标识信息。
步骤804，HSS向SCEF发送确认消息。
具体的，HSS更新签约信息后，向SCEF发送确认消息，用于指示HSS已完成签约信息的更新，消息中包括但不限于：用户组的标识信息。
步骤805，SCEF确定所述用户组对应的监控事件配置的信息。
具体的，SCEF接收到HSS的确认消息后，确定HSS已完成签约信息的更新，SCEF可对用户组对应的监控事件配置的信息进行更新。
具体的，SCEF可基于SCS/AS发送的用户组的标识信息，确定用户组及其对应的监控事件配置，具体是指用户组对应的所有监控事件配置。
一个示例中，若指示信息为删除指示信息，即在用户组中删除用户，则SCEF确定在统计用户组的所有事件监控的报告时，剔除该用户的报告。剔除方式可参照步骤702，此处不赘述。
另一个示例中，若指示信息为增加指示信息，即在用户组中增加用户，则SCEF确定在统计用户组的所有事件监控的报告时，统计该用户的用户报告。具体的，SCEF将用户组的每一个监控事件配置的信息记录的组成员数量加上增加的用户的数量。
在一种可能的实现方式中，步骤805也可以在步骤802之前执行，本申请不做限定。
步骤806，SCEF向SCS/AS发送确认消息。
具体的，SCEF向SCS/AS发送确认消息，以指示SCEF完成相关配置，消息中可携 带用户组的标识信息。
步骤807，HSS向MME/SGSN发送插入签约用户数据请求消息。
具体的，HSS向MME/SGSN发送插入签约用户请求消息，用于指示MME/SGSN删除监控事件配置。
具体的，插入签约用户请求消息中包括但不限于：用户组对应的一个或多个监控事件配置的标识信息、用户的标识信息和指示信息。
具体的，如上文所述，用户组对应有一个或多个监控事件配置，如果在一个用户组中增加或者删除用户，则需要对用户组对应的所有监控事件配置的信息进行更新。HSS在配置流程中有用户组对应的一个或多个监控事件配置的标识信息，并可携带在插入签约用户请求消息中发送给MME/SGSN。示例性的，用户组的监控事件配置的标识信息可以为SCEF Reference ID，具体的，HSS可基于用户组的外部标识信息查找到对应的用户组及其对应的一个或多个监控事件配置的标识信息。
示例性的，用户的标识信息可以为用户的内部标识信息。
在一种可能的实现方式中，若指示信息用于指示在用户组中增加用户，则消息中还包括监控事件配置的相关参数，示例性的，相关参数包括但不限于：最大报告次数等，以指示MME/SGSN基于监控事件配置的相关参数，确定用户的监控事件配置。
步骤808，MME/SGSN基于插入签约用户请求消息，开始或取消对所述用户的事件监控。
具体的，MMS/SGSN基于用户组对应的一个或多个监控事件配置的标识信息，确定用户在该用户组中对应的一个或多个监控事件配置。
一个示例中，若指示信息为删除指示信息，则MME/SGSN删除该用户在该用户组中对应的一个或多个监控事件配置。举例说明：假设用户1属于用户组1和用户组2，用户组1对应监控事件配置1，其中监控事件配置标识为SCEF Reference ID1和监控事件配置2，其中监控事件配置标识为SCEF Reference ID2，用户组2对应监控事件配置3和监控事件配置4，若要从用户组1中删除用户1，则MME/SGSN基于用户1的标识信息和SCEF Reference ID1删除对应的监控事件配置，基于用户1的标识信息和SCEF Reference ID2，删除对应的监控事件配置。
另一个示例中，若指示信息为增加指示信息，则MME/SGSN可基于接收到监控事件配置的相关参数，对用户的事件监控进行配置及监控。举例说明：MME/SGSN接收到监控事件配置1的相关参数，例如最大报告次数为3，MME/SGSN将监控事件配置1的相关参数写入用户1的上下文，并基于更新后的用户的上下文中的监控事件配置1的信息，对用户进行事件监控，也就是说，MME/SGSN对监控事件配置1进行事件监控时，除对预先配置的监控事件配置1对应的用户组1中的组成员进行监控外，还需要对用户1进行事件监控。
步骤809，MME/SGSN向HSS发送确认消息。
具体的，HSS针对需要在用户组中增加或删除的每个用户重复执行步骤807至步骤809，直至用户组中需要增加或删除的用户均执行完毕。
在其他优选实施例中，HSS根据签约信息或运营商的策略决定从用户组中删除该用 户或在用户组中增加该用户，具体流程为：步骤801-步骤802不执行，执行步骤803-步骤809，不同之处在于：
步骤803：HSS根据签约信息或运营商的策略决定从用户组中删除该用户或在用户组中增加该用户；
步骤804：HSS向SCEF发送组用户管理请求消息；
步骤805：SCEF向SCS/AS发送组用户管理请求消息。
在上述实施例中，若SCEF在更新监控事件配置的信息后判断针对该用户组的报告已经完成，则SCEF向HSS发送取消订阅的请求消息，HSS进一步向MME/SGSN发送取消订阅的请求消息。
结合图1，如图11所示为本申请实施例中的事件监控管理方法的流程示意图，在图11中：
具体的，事件监控的配置以及监控流程均可参照图3和图4所示的实施例，此处不赘述。
步骤901，SCS/AS向SCEF发送组用户配置管理请求消息。
具体细节可参照步骤801，此处不赘述。
步骤902，SCEF向HSS发送组用户管理请求消息，
具体细节可参照步骤802，此处不赘述。
步骤903，HSS基于组用户管理请求消息，更新签约信息。
具体细节可参照步骤803，此处不赘述。
步骤904，HSS向SCEF发送确认消息。
具体细节可参照步骤804，此处不赘述。
步骤905，SCEF向SCS/AS发送确认消息。
具体的，SCEF向SCE/AS发送确认消息，以指示SCEF成功接收SCS/AS发送的组用户配置管理请求消息。
步骤906，HSS向SCEF发送监控指示消息。
具体的，HSS向SCEF发送监控指示消息，以指示SCEF更新监控事件配置的信息，也可以理解为，指示在用户组中删除或增加用户。
在一种可能的实现方式中，若需要在用户组中删除用户，则HSS向SCEF发送的监控指示消息中包括但不限于：用户组对应的一个或多个监控事件配置的标识信息、用户的标识信息。示例性的，用户的标识信息可以为用户的外部标识信息。
在另一种可能的实现方式中，若需要在用户组中增加用户，则HSS向SCEF发送的监控指示消息中包括但不限于：用户组对应的一个或多个监控事件配置的标识信息和需要增加的用户的数量，或者，用户组对应的一个或多个监控事件配置的标识信息和需要更新的用户组的组成员数量，其中，需要更新的用户组的组成员数量即为用户组当前的组成员数量与需要增加的用户的数量之和。
步骤907，SCEF确定所述用户组对应的监控事件配置的信息。
具体的，SCEF可基于HSS发送的监控指示消息，更新用户组对应的所有监控事件 配置的信息，
具体细节可参照步骤805，此处不赘述。
步骤908，HSS向MME/SGSN发送插入签约用户数据请求消息。
步骤909，MME/SGSN基于插入签约用户请求消息，开始或取消对所述用户的事件监控。
步骤910，MME/SGSN向HSS发送确认消息。
步骤908至步骤910可参照步骤807至步骤809，此处不赘述。
在其他优选实施例中，HSS根据签约信息或运营商的策略决定从用户组中删除该用户或在用户组中增加该用户，具体流程为：步骤901-步骤905不执行，执行步骤906-步骤919
在上述实施例中，若SCEF在更新监控事件配置的信息后判断针对该用户组的报告已经完成，则SCEF向HSS发送取消订阅的请求消息，HSS进一步向MME/SGSN发送取消订阅的请求消息。
场景三
结合图2，如图12所示为本申请实施例中的监控事件订阅管理方法的流程示意图，在图12中：
具体的，监控事件订阅以及事件报告流程均可参照图5和图6所示的实施例，此处不赘述。
步骤1001，AF向NEF发送监控事件订阅请求消息。
具体的，AF向NEF发送监控事件订阅请求消息，用于指示取消监控事件订阅中的用户的事件监控。
示例性的，消息中包括但不限于：监控事件订阅的标识信息、用户的标识信息和取消指示信息。
其中，监控事件订阅的标识信息用于指示对应的监控事件订阅，示例性的，监控事件订阅的标识信息可以为NEF订阅关联标识。
用户的标识信息用于标识对应的用户，示例性的，用户的标识信息可以为用户的外部标识信息，如GPIS(Generic Public Subscription Identifier)。
取消指示信息用于指示取消NEF订阅关联标识对应的监控事件订阅中指定用户的事件监控，指定用于是指用户的标识信息对应的用户。
在一种可能的实现方式中，监控请求消息中还可以包括一个或多个事件标识，如上文所述，在监控事件订阅过程中，单一监控事件订阅可以对应一个或多个事件监控类型，在本申请中，AF可以指示取消监控事件订阅中的指定用户的一个或多个事件标识对应的事件监控。
其他细节可参照步骤701，此处不赘述。
步骤1002，NEF向UDM发送监控指示消息。
具体的，NEF向UDM发送监控事件订阅请求消息，监控事件订阅请求消息中包括监控事件订阅的标识信息、用户的标识信息和取消指示信息。
示例性的，该监控请求消息中的监控事件订阅的标识信息可以为UDM订阅关联标 识，用户的标识信息可以为用户的外部标识信息。
可选地，监控请求消息中还可以携带一个或多个事件标识，用于指示取消监控事件订阅中的该用户的指定事件标识的事件监控。
可选地，监控事件订阅请求消息中还可以携带生效指示信息，用于指示该取消操作一直生效，也就是说，当该监控事件订阅被删除后，取消操作仍然生效。示例性的，生效指示信息可以包括以下至少之一：用户的标识信息、事件标识、AF的标识信息、取消监控指示。UDM将生效指示信息保存到UDR中。当后续AF重新针对这个用户组执行事件订阅时后，UDM根据从UDR中获取的生效指示信息，在发送给NEF的用户组成员用户信息时，剔除该用户，并且指示AMF或SMF不对该用户进行事件监控。
具体的，UDM接收到监控指示消息后，保存监控指示消息中携带的各参数。并且，UDM可基于用户的标识信息，查找用户对应的AMF或SMF。
步骤1003a，UDM向AMF发送监控事件订阅请求消息。
具体的，UDM查询到用户对应的AMF后，向该AMF发送监控事件订阅请求消息，消息中包括但不限于：用户的标识信息、监控事件订阅的标识信息和取消指示信息。
示例性的，该监控事件订阅请求消息中的用户的标识信息可以为用户的内部标识信息。具体的，UDM可从签约信息中查找到与用户的外部标识对应的用户的内部标识信息，并携带在监控事件订阅请求消息中发送给AMF。
示例性的，UDM向AMF发送的监控事件订阅请求消息中的监控事件订阅标识信息可以为AMF订阅关联标识。
可选地，消息中还可以携带事件标识信息，用于指示AMF取消监控事件订阅中的用户的指定事件标识的事件监控。
步骤1004a，AMF基于监控事件订阅请求消息，取消监控事件订阅中的用户的事件监控。
具体的，AMF接收到监控事件订阅请求消息，基于监控事件订阅请求消息，执行对事件监控配置的用户的事件监控的取消操作。
在一种可能的实现方式中，若最大报告次数是每用户粒度，示例性的，监控事件订阅请求消息携带用户的标识信息、监控事件订阅的标识信息和取消指示信息，用于指示取消监控事件订阅中的用户的事件监控。AMF基于该监控事件订阅请求消息，取消监控事件订阅中用户的事件监控，并删除用户对应于监控事件订阅的信息。示例性的，用户的上下文中包括一个或多个监控事件订阅的信息，AMF可删除用户的上下文中对应于需要取消的监控事件订阅的信息，例如剩余报告次数等。并且，AMF在用户的上下文中增加取消标记，用于指示取消监控事件订阅中该用户的事件监控，(示例性的，取消标记可以为UDM的通知端点或NEF通知端点以及对应的取消指示，本申请不做限定)，或是在用户的上下文中对应的监控事件订阅的信息中将剩余报告次数设置为0。也就是说，若用户移动到其他AMF上后，其他AMF可基于用户的上下文，对需要取消监控事件订阅的用户不进行事件监控。。
在一种可能的实现方式中，若最大报告次数是每用户粒度，示例性的，监控事件订阅请求消息携带用户的标识信息、监控事件订阅的标识信息、事件标识和取消指示信息。 示例性的，AMF在用户的上下文中增加取消标记，用于指示取消事件监控配置中该用户的指定事件标识的事件监控。也就是说，若用户移动到其他AMF上后，其他AMF可基于用户的上下文，确定需要取消事件订阅中的用户的指定事件标识的事件监控。
在一种可能的实现方式中，若最大报告次数是每用户每事件标识的粒度，示例性的，，监控事件订阅请求消息携带用户的标识信息、监控事件订阅的标识信息、事件标识和取消指示信息。AMF基于该监控事件订阅请求消息，取消监控事件订阅中用户的特定事件标识的事件监控。示例性的，用户的上下文中包括一个或多个监控事件订阅的信息，AMF可删除用户的上下文中对应于需要取消的监控事件订阅中特定事件标识的信息，例如剩余报告次数等。并且，AMF在用户的上下文中增加取消标记，用于指示取消监控事件订阅中该用户的特定事件标识的事件监控，(示例性的，取消标记可以为UDM的通知端点或NEF通知端点以及对应的事件标识、取消指示，本申请不做限定)，或是在用户的上下文中对应的监控事件订阅的信息中将特定事件标识的剩余报告次数设置为0。也就是说，若用户移动到其他AMF上后，其他AMF可基于用户的上下文，对需要取消监控事件订阅的用户的特定事件标识不进行事件监控。
步骤1005a，AMF向UDM发送确认消息。
具体的，AMF向UDM发送确认消息，以指示AMF已完成相关配置。
步骤1003b，UDM向SMF发送插入监控事件订阅请求消息。
可参照步骤1003a，此处不赘述。
步骤1004b，SMF基于监控事件订阅请求消息，取消监控事件订阅中的用户的事件监控。
可参照步骤1004a，此处不赘述。
步骤1005b，SMF向UDM发送确认消息。
需要说明的是，如果取消监控事件订阅中的多个用户的事件监控，则UDM针对每一个需要取消的用户执行步骤1003a至步骤1005a或者步骤1003b至步骤1005b，也就是说，UDM接收到AMF/SMF返回的监控事件订阅响应消息后，再针对另一个用户执行步骤1003a至步骤1005a或者步骤1003b至步骤1005b，直至所有需要取消的用户均执行完毕。
步骤1006，UDM向NEF发送确认消息。
具体的，UDM向NEF发送确认消息，用于指示已完成相关配置。
步骤1007，NEF确定监控事件订阅的信息。
具体细节与步骤702类似，此处不赘述。
需要说明的是，步骤1007也可以在步骤1002之前执行，即默认为UDM可成功执行相关配置。
步骤1008，NEF向AF发送确认消息。
具体的，NEF向AF发送确认消息，以指示NEF已完成相关配置，消息中可携带事件监控配置的标识信息。
在其他优选实施例中，UDM根据签约信息或运营商的策略决定取消事件订阅中用户的事件监控，具体流程为步骤1001-步骤1002不执行，执行步骤1003a-步骤1008，不同 之处在于：
步骤1006：UDM向NEF发送事件订阅通知消息；
步骤1007：NEF向AF发送事件订阅通知。
在上述实施例中，若NEF在更新监控事件配置的信息后判断针对该用户组的报告已经完成，则NEF向UDM发送取消订阅的请求消息，UDM进一步向AMF发送取消订阅的请求消息。
场景四
结合图2，如图13所示为本申请实施例中的事件订阅管理方法的流程示意图，在图13中：
具体的，监控事件订阅以及事件报告流程均可参照图5和图6所示的实施例，此处不赘述。
步骤1101，AF向NEF发送组用户配置管理请求消息。
具体的，AF向NEF发送组用户配置管理请求消息，用于指示从用户组中删除用户，或者，在用户组中增加用户。
示例性的，消息中包括但不限于：用户组的标识信息、用户的标识信息和指示信息，指示信息可以为删除指示信息，用于指示从用户组中删除用户。指示信息可以为增加指示信息，用于指示在用户组中增加用户。
示例性的，用户组的标识信息可以为用户组的外部标识信息，用户的标识信息可以为用户的外部标识信息。
可选地，消息中的用户的标识信息可以为一个或多个，用于指示在用户组中删除一个或多个用户，或者增加一个或多个用户。
步骤1102，NEF向UDM发送组用户管理请求消息。
具体的，NEF向UDM发送用户管理请求消息，用于指示UDM更新签约信息。
示例性的，消息中包括但不限于：用户组的标识信息、用户的标识信息和指示信息。例如：用户组的外部标识信息、用户的外部标识信息和指示信息。
步骤1103，UDM基于组用户管理请求消息，更新签约信息。
具体细节可参照步骤803，此处不赘述。
步骤1104a，UDM向AMF发送用户数据管理通知请求消息。
具体的，UDM向用户对应的AMF发送用户数据管理通知请求消息，用于指示AMF在用户组中删除或增加用户。
示例性的，用户数据管理通知请求消息中包括但不限于：用户的内部组标识列表，用于指示用户所属的一个或多个用户组。一个示例中，若指示信息指示从用户组中删除用户，则用户的内部组标识列表中的一个或多个用户组的标识信息中不包括该用户组的标识信息。
另一个示例中，若指示信息指示在用户组中增加用户，则用户的内部组标识列表中的一个或多个用户组的标识信息中包括指定该用户组的标识信息。
需要说明的是，如上文所述，在5G网络中的配置流程中，AMF/SMF保存的用户组的监控事件订阅的信息为组订阅信息，也就是说，包括该用户组对应的所有事件监控配 置的配置参数，也可以理解为，AMF基于组订阅信息，即可确定该用户组中各组成员所需要的事件监控配置的参数，因此，UDM发送的用户数据管理通知请求消息无需携带用户组对应的一个或多个事件监控配置的标识信息。
步骤1105a，AMF基于用户数据管理通知请求消息，开始或取消对所述用户的事件监控。
一个示例中，若UDM指示从用户组内删除用户，则AMF基于用户的内部组标识列表，确定用户不再属于指定的用户组。AMF可基于用户组的标识信息，确定用户组对应的一个或多个监控事件订阅，也可以理解为组订阅信息，则AMF停止对用户组对应的一个或多个监控事件订阅中的需要删除用户的事件监控，并删除用户对应于该用户组的一个或多个监控事件订阅的信息。具体细节可参照步骤1004a，此处不赘述。
另一个示例中，若UDM指示从用户组内增加用户，则AMF基于用户的内部组标识列表，确定用户属于指定的用户组。AMF可基于用户组的标识信息，确定用户组对应的一个或多个监控事件订阅，也可以理解为组订阅信息，则AMF开始对用户组对应的一个或多个监控事件订阅中的需要增加用户的事件监控。
在一种可能的实现方式中，若UDM指示从用户组内增加用户，但是该AMF上不存在用户组的监控事件订阅的信息，也就是说，AMF上未存储有用户组的组订阅信息，则UDM还向AMF发送的监控事件订阅请求消息中，包括用户组的事件订阅的信息，以使AMF可基于该用户组的事件监控配置的信息，对增加的用户进行事件监控。
步骤1106a，AMF向UDM发送确认消息。
步骤1104b，UDM向SMF发送用户数据管理通知请求消息。
步骤1105b，SMF基于用户数据管理通知请求消息，开始或取消对所述用户的事件监控。
步骤1106b，SMF向UDM发送确认消息。
步骤1104b至步骤1106b可参照步骤1104a至步骤1106a，此处不赘述。
需要说明的是，UDM针对每一个需要增加或者删除的用户，重复执行步骤1104a至步骤1106a或者步骤1104b至步骤1106b，直至用户组需要增加或删除的用户执行完毕。
步骤1107，UDM向NEF发送确认消息。
步骤1108，NEF确定所述用户组对应的监控事件订阅的信息。
具体细节可参照步骤805，此处不赘述。
需要说明的是，步骤1108可在步骤1102之前执行，本申请不做限定。
步骤1109，NEF向AF发送确认消息。
在其他优选实施例中，UDM根据签约信息或运营商的策略决定从用户组中删除该用户或在用户组中增加该用户，具体流程为：步骤1101-步骤1103不执行，执行步骤1104a-步骤1109，不同之处在于：
步骤1107：UDM向NEF发送组用户管理请求消息；
步骤1109：NEF向AF发送组用户管理请求消息。
在上述实施例中，若NEF在更新监控事件配置的信息后判断针对该用户组的报告已经完成，则NEF向UDM发送取消订阅的请求消息，UDM进一步向AMF发送取消订阅 的请求消息。
结合图2，如图14所示为本申请实施例中的事件监控管理方法的流程示意图，在图14中：
具体的，事件监控的配置以及监控流程均可参照图5和图6所示的实施例，此处不赘述。
步骤1201，AF向NEF发送组用户配置管理请求消息。
步骤1202，NEF向UDM发送组用户管理请求消息，
步骤1203，UDM基于组用户管理请求消息，更新签约信息。
步骤1204a，UDM向AMF发送用户数据管理通知请求消息。
步骤1205a，AMF基于用户数据管理通知请求消息，开始或取消对所述用户的事件监控。
步骤1206a，AMF向UDM发送确认消息。
步骤1204b，UDM向SMF发送用户数据管理通知请求消息。
步骤1205b，SMF基于用户数据管理通知请求消息，开始或取消对所述用户的事件监控。
步骤1206b，SMF向UDM发送确认消息。
步骤1201至步骤1206可参照步骤1101至步骤1106，此处不赘述。
步骤1207，UDM向NEF发送用户组管理确认消息。
步骤1208，NEF向AF发送用户组管理确认消息。
步骤1209，UDM向NEF发送事件通知消息。
具体的，UDM向NEF发送事件通知消息，以指示NEF更新事件订阅的信息，也可以理解为，指示在用户组中删除或增加用户。
在一种可能的实现方式中，若需要在用户组中删除用户，则UDM向NEF发送的事件通知消息中包括但不限于：用户组对应的一个或多个事件监控事件订阅的标识信息、用户的标识信息。示例性的，事件通知的标识信息可以为NEF的通知端点，用户的标识信息可以为用户的外部标识信息。
在另一种可能的实现方式中，若需要在用户组中增加用户，则UDM向NEF发送的事件通知消息中包括但不限于：用户组对应的一个或多个事件通知的标识信息和需要增加的用户的数量或增加的用户的标识列表，或者，用户组对应的一个或多个监控事件订阅的标识信息和需要更新的用户组的组成员数量或者用户组新的成员用户标识列表，其中，需要更新的用户组的组成员数量即为用户组当前的组成员数量与需要增加的用户的数量之和。
步骤1210，NEF确定所述用户组对应的监控事件订阅的信息。
具体的，NEF可基于UDM发送的事件通知消息，更新用户组对应的所有事件订阅的信息，
具体细节可参照步骤805，此处不赘述。
在其他优选实施例中，UDM根据签约信息或运营商的策略决定从用户组中删除该用 户或在用户组中增加该用户，具体流程为：步骤1201-步骤1303不执行，执行步骤1204a-步骤1209。
在上述实施例中，若NEF在更新监控事件配置的信息后判断针对该用户组的报告已经完成，则NEF向UDM发送取消订阅的请求消息，UDM进一步向AMF发送取消订阅的请求消息。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各网元为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对各网元进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下，在采用对应各个功能划分各个功能模块的情况下，图15示出了上述实施例中所涉及的网元100的一种可能的结构示意图，如图15所示，网元100可以包括：收发模块101和处理模块102。
一个示例中，收发模块101，用于接收指示消息，指示消息包括监控事件配置的标识信息、用户的标识信息和指示信息，监控事件配置的标识信息用于指示用户所属用户组的第一监控事件配置，指示信息用于指示取消第一监控事件配置中用户的事件监控。处理模块102，用于根据指示消息，确定第一监控事件配置的信息，其中，第一监控事件配置的信息包括以下至少之一：用户组的组成员信息、用户的监控事件报告次数信息。收发模块101，用于向第二网元发送删除消息，用于指示第二网元删除第一监控事件配置，其中，删除消息为基于第一监控事件配置的信息，确定第一事件监控的报告完成后向第二网元发送的。
在一种可能的实现方式中，第一监控事件配置的信息指示在统计用户组的第一监控事件配置的报告时，剔除用户对应的监控事件报告。
在一种可能的实现方式中，用户组的组成员信息包括：用户组的组成员数量为当前保存的用户组的组成员数量与用户的数量之间的差值；或者，用户组的成员用户为当前保存的用户组的成员用户删除用户。
在一种可能的实现方式中，处理模块102，用于删除保存的用户的监控事件报告次数。
在一种可能的实现方式中，处理模块102，用于将用户的监控事件报告次数设置为最大报告次数，即默认为该用户的报告已完成。
另一个示例中，收发模块101，用于接收指示消息，指示消息包括用户组的标识信息、用户的标识信息和指示信息，用户组的标识信息用于指示用户所属用户组，指示信息用于指示从用户组中删除用户，或者，在用户组中增加用户；处理模块102，用于根据指示消息，确定用户组对应的监控事件配置的信息，其中，监控事件配置的信息包括以下至少之一：用户组的组成员信息、用户的监控事件报告次数信息；收发模块101，用于向第二网元发送删除消息，用于指示第二网元删除监控事件配置，其中，删除消息为基于监控事件配置的信息，确定事件监控的报告完成后向第二网元发送的。
在一种可能的实现方式中，指示信息用于指示从用户组中删除用户，监控事件配置的信息指示在统计用户组的监控事件配置的报告时，剔除用户对应的监控事件的报告。
在一种可能的实现方式中，指示信息用于指示从用户组中删除用户，用户组的组成员数量为当前保存的用户组的组成员数量与用户的数量之间的差值。
在一种可能的实现方式中，处理模块102，用于删除保存的用户的监控事件报告次数。
在一种可能的实现方式中，处理模块102，用于将用户的监控事件报告次数标识为最大报告次数。
在一种可能的实现方式中，指示信息用于在用户组中增加用户，监控事件配置的信息指示统计用户对应的监控事件的报告次数。
在一种可能的实现方式中，指示信息用于在用户组中增加用户，用户组的组成员数量为当前保存的用户组的组成员数量与用户的数量的和。
另一个示例中，收发模块101，用于接收指示消息，指示消息包括监控事件配置的标识信息、用户的标识信息和指示信息，监控事件配置的标识信息用于指示用户所属用户组的第一监控事件配置，指示信息用于指示取消第一监控事件配置中用户的事件监控；处理模块102，用于根据指示消息，取消第一监控事件配置中用户的事件监控。
在一种可能的实现方式中，指示消息还包括事件监控类型，处理模块102，用于取消第一监控事件配置中用户的事件监控类型的事件监控。
在一种可能的实现方式中，指示消息还包括事件监控类型，处理模块102，用于根据指示消息，确定用户的上下文，用户的上下文指示取消第一监控事件配置中对用户的事件监控。
在一种可能的实现方式中，指示消息还包括事件监控类型，收发模块101，用于向第四网元发送用户的上下文，用于指示第四网元取消第一监控事件配置中对用户的事件监控。
另一个示例中，收发模块101，用于接收指示消息，指示消息包括用户组的标识信息、用户的标识信息和指示信息，用户组的标识信息用于指示用户组，指示信息用于指示从用户组中删除用户，或者，用于指示在用户组中增加用户；处理模块102，用于若指示信息用于指示从用户组中删除用户，取消在用户组对应的监控事件配置中对用户的事件监控；若指示信息用于指示在用户组中增加用户，开始在用户组对应的监控事件配置中对用户进行事件监控。
在一种可能的实现方式中，指示信息用于指示从用户组中删除用户，处理模块102， 还用于更新用户的上下文，更新后的用户的上下文指示用户不属于用户组；
在一种可能的实现方式中，指示信息用于指示在用户组中增加用户，处理模块102，还用于更新用户的上下文，更新后的用户的上下文指示用户属于用户组。
另一个示例中，图16示出了本申请实施例的一种装置200的示意性框图，装置200可以包括：处理器201和收发器/收发管脚202，可选地，还包括存储器203。该处理器201可用于执行前述的实施例的各方法中的任一网元所执行的步骤，并控制接收管脚接收信号，以及控制发送管脚发送信号。
装置200的各个组件通过总线204耦合在一起，其中总线系统204除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图中将各种总线都标为总线系统204。
可选地，存储器203可以用于前述方法实施例中的存储指令。
应理解，根据本申请实施例的装置200可对应于前述的实施例的各方法中的任一网元，并且装置200中的各个元件的上述和其它管理操作和/或功能分别为了实现前述各个方法的相应步骤，为了简洁，在此不再赘述。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
基于相同的技术构思，本申请实施例还提供一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，该计算机程序包含至少一段代码，该至少一段代码可由装置执行，以控制装置用以实现上述方法实施例。
基于相同的技术构思，本申请实施例还提供一种计算机程序，当该计算机程序被装置执行时，用以实现上述方法实施例。
所述程序可以全部或者部分存储在与处理器封装在一起的存储介质上，也可以部分或者全部存储在不与处理器封装在一起的存储器上。
基于相同的技术构思，本申请实施例还提供一种处理器，该处理器用以实现上述方法实施例。上述处理器可以为芯片。
基于相同的技术构思，本申请实施例还提供一种系统，包括上述方法实施例中的各网元。
结合本申请实施例公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read Only Memory，ROM)、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、电可擦可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于网络设备中。当然，处理器和存储介质也可以作为分立组件存在于网络设备中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请实施例所描述 的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (44)

  1. 一种事件订阅管理方法，其特征在于，包括：
    接收指示消息，所述指示消息包括监控事件配置的标识信息、用户的标识信息和指示信息，所述监控事件配置的标识信息用于指示所述用户所属用户组的第一监控事件配置，所述指示信息用于指示取消所述第一监控事件配置中所述用户的事件监控；
    根据所述指示消息，确定所述第一监控事件配置的信息，其中，所述第一监控事件配置的信息包括以下至少之一：所述用户组的组成员信息、所述用户的监控事件报告次数信息；
    向第二网元发送删除消息，用于指示所述第二网元删除所述第一监控事件配置，其中，所述删除消息为基于所述第一监控事件配置的信息，确定所述第一事件监控的报告完成后向所述第二网元发送的。
  2. 根据权利要求1所述的方法，其特征在于，所述第一监控事件配置的信息指示在统计所述用户组的第一监控事件配置的报告时，剔除所述用户对应的监控事件报告。
  3. 根据权利要求1所述的方法，其特征在于，所述第一监控事件配置的信息用于指示所述用户对应的监控事件报告已完成。
  4. 根据权利要求1至3任一项所述的方法，其特征在于，所述用户组的组成员信息包括：
    所述用户组的组成员数量为当前保存的所述用户组的组成员数量与所述用户的数量之间的差值；
    或者，
    所述用户组的成员用户为当前保存的所述用户组的成员用户删除所述用户。
  5. 根据权利要求4所述的方法，其特征在于，所述确定所述第一监控事件配置的信息，包括：
    删除保存的所述用户的监控事件报告次数。
  6. 根据权利要求1至3任一项所述的方法，其特征在于，所述确定所述第一监控事件配置的信息，包括：
    将所述用户的监控事件报告次数设置为最大报告次数。
  7. 一种事件订阅管理方法，其特征在于，包括：
    接收指示消息，所述指示消息包括用户组的标识信息、用户的标识信息和指示信息，所述用户组的标识信息用于指示所述用户所属用户组，所述指示信息用于指示从所述用户组中删除所述用户，或者，在所述用户组中增加所述用户；
    根据所述指示消息，确定所述用户组对应的监控事件配置的信息，其中，所述监控事件配置的信息包括以下至少之一：所述用户组的组成员信息、所述用户的监控事件报告次数信息；
    向第二网元发送删除消息，用于指示所述第二网元删除所述监控事件配置，其中，所述删除消息为基于所述监控事件配置的信息，确定所述事件监控的报告完成后向所述第二网元发送的。
  8. 根据权利要求7所述的方法，其特征在于，所述指示信息用于指示从所述用户组中删除所述用户，所述监控事件配置的信息指示在统计所述用户组的监控事件配置的报告时，剔除所述用户对应的监控事件的报告。
  9. 根据权利要求7或8所述的方法，其特征在于，所述指示信息用于指示从所述用户组中删除所述用户，所述用户组的组成员数量为当前保存的所述用户组的组成员数量与所述用户的数量之间的差值；
    或者，
    所述用户组的成员用户为当前保存的所述用户组的成员用户删除所述用户。。
  10. 根据权利要求9所述的方法，其特征在于，所述确定所述用户组对应的监控事件配置的信息，包括：
    删除保存的所述用户的监控事件报告次数。
  11. 根据权利要求7或8所述的方法，其特征在于，所述确定所述用户组对应的监控事件配置的信息，包括：
    将所述用户的监控事件报告次数标识为最大报告次数。
  12. 根据权利要求8所述的方法，其特征在于，所述指示信息用于在所述用户组中增加所述用户，所述监控事件配置的信息指示统计所述用户对应的监控事件的报告次数。
  13. 根据权利要求7或12所述的方法，其特征在于，所述指示信息用于在所述用户组中增加所述用户，所述用户组的组成员数量为当前保存的所述用户组的组成员数量与所述用户的数量的和；
    或者，
    所述用户组的成员用户为当前保存的所述用户组的成员用户增加所述用户。。
  14. 一种事件订阅管理方法，其特征在于，包括：
    接收指示消息，所述指示消息包括监控事件配置的标识信息、用户的标识信息和指示信息，所述监控事件配置的标识信息用于指示所述用户所属用户组的第一监控事件配置，所述指示信息用于指示取消所述第一监控事件配置中所述用户的事件监控；
    根据所述指示消息，取消所述第一监控事件配置中所述用户的事件监控。
  15. 根据权利要求14所述的方法，其特征在于，所述指示消息还包括事件监控类型，所述取消所述第一监控事件配置中所述用户的事件监控，包括：
    取消所述第一监控事件配置中所述用户的所述事件监控类型的事件监控。
  16. 根据权利要求14所述的方法，其特征在于，所述方法还包括：
    根据所述指示消息，确定所述用户的上下文，所述用户的上下文指示取消所述第一监控事件配置中对所述用户的事件监控。
  17. 根据权利要求16所述的方法，其特征在于，所述方法还包括：
    向第四网元发送所述用户的上下文，用于指示所述第四网元取消所述第一监控事件配置中对所述用户的事件监控。
  18. 一种事件订阅管理方法，其特征在于，包括：
    接收指示消息，所述指示消息包括用户组的标识信息、用户的标识信息和指示信息，所述用户组的标识信息用于指示用户组，所述指示信息用于指示从所述用户组中删除所述用户，或者，用于指示在所述用户组中增加所述用户；
    若所述指示信息用于指示从所述用户组中删除所述用户，取消在所述用户组对应的监控事件配置中对所述用户的事件监控；
    若所述指示信息用于指示在所述用户组中增加所述用户，开始在所述用户组对应的监控事件配置中对所述用户进行事件监控。
  19. 根据权利要求18所述的方法，其特征在于，所述指示信息用于指示从所述用户组中删除所述用户，所述方法还包括：
    更新所述用户的上下文，更新后的所述用户的上下文指示所述用户不属于所述用户组；
  20. 根据权利要求18所述的方法，其特征在于，所述指示信息用于指示在所述用户组中增加所述用户，所述方法还包括：
    更新所述用户的上下文，更新后的所述用户的上下文指示所述用户属于所述用户组。
  21. 一种装置，其特征在于，包括：
    存储器和处理器，所述存储器和处理器耦合，
    所述存储器存储有程序指令，所述程序指令被所述处理器运行时，使得所述装置执行如下步骤：
    接收指示消息，所述指示消息包括监控事件配置的标识信息、用户的标识信息和指示信息，所述监控事件配置的标识信息用于指示所述用户所属用户组的第一监控事件配 置，所述指示信息用于指示取消所述第一监控事件配置中所述用户的事件监控；
    根据所述指示消息，确定所述第一监控事件配置的信息，其中，所述第一监控事件配置的信息包括以下至少之一：所述用户组的组成员信息、所述用户的监控事件报告次数信息；
    向第二网元发送删除消息，，用于指示所述第二网元删除所述第一监控事件配置，其中，所述删除消息为基于所述第一监控事件配置的信息，确定所述第一事件监控的报告完成后向所述第二网元发送的。
  22. 根据权利要求21所述的装置，其特征在于，所述第一监控事件配置的信息指示在统计所述用户组的第一监控事件配置的报告时，剔除所述用户对应的监控事件报告。
  23. 根据权利要求21所述的方法，其特征在于，所述第一监控事件配置的信息用于指示所述用户对应的监控事件报告已完成。
  24. 根据权利要求21至23任一项所述的装置，其特征在于，所述用户组的组成员信息包括：
    所述用户组的组成员数量为当前保存的所述用户组的组成员数量与所述用户的数量之间的差值；或者，
    所述用户组的组成员用户为当前保存的所述用户组的组成员用户删除所述用户。
  25. 根据权利要求24所述的装置，其特征在于，所述程序指令被所述处理器运行时，使得所述装置执行如下步骤：
    删除保存的所述用户的监控事件报告次数。
  26. 根据权利要求21至25任一项所述的装置，其特征在于，所述程序指令被所述处理器运行时，使得所述装置执行如下步骤：
    将所述用户的监控事件报告次数设置为最大报告次数。
  27. 一种装置，其特征在于，包括：
    存储器和处理器，所述存储器和处理器耦合，
    所述存储器存储有程序指令，所述程序指令被所述处理器运行时，使得所述装置执行如下步骤：
    接收指示消息，所述指示消息包括用户组的标识信息、用户的标识信息和指示信息，所述用户组的标识信息用于指示所述用户所属用户组，所述指示信息用于指示从所述用户组中删除所述用户，或者，在所述用户组中增加所述用户；
    根据所述指示消息，确定所述用户组对应的监控事件配置的信息，其中，所述监控事件配置的信息包括以下至少之一：所述用户组的组成员信息、所述用户的监控事件报告次数信息；
    向第二网元发送删除消息，，用于指示所述第二网元删除所述监控事件配置，其中，所述删除消息为基于所述监控事件配置的信息，确定所述事件监控的报告完成后向所述第二网元发送的。
  28. 根据权利要求27所述的装置，其特征在于，所述指示信息用于指示从所述用户组中删除所述用户，所述监控事件配置的信息指示在统计所述用户组的监控事件配置的报告时，剔除所述用户对应的监控事件的报告。
  29. 根据权利要求27或28所述的装置，其特征在于，所述指示信息用于指示从所述用户组中删除所述用户，所述用户组的组成员数量为当前保存的所述用户组的组成员数量与所述用户的数量之间的差值；或者，
    所述用户组的组成员用户为当前保存的所述用户组的组成员用户删除所述用户。
  30. 根据权利要求29所述的装置，其特征在于，所述程序指令被所述处理器运行时，使得所述装置执行如下步骤：
    删除保存的所述用户的监控事件报告次数
  31. 根据权利要求27或28所述的装置，其特征在于，所述程序指令被所述处理器运行时，使得所述装置执行如下步骤：
    将所述用户的监控事件报告次数标识为最大报告次数。
  32. 根据权利要求27所述的装置，其特征在于，所述指示信息用于在所述用户组中增加所述用户，所述监控事件配置的信息指示统计所述用户对应的监控事件的报告次数。
  33. 根据权利要求27或32所述的装置，其特征在于，所述指示信息用于在所述用户组中增加所述用户，所述用户组的组成员数量为当前保存的所述用户组的组成员数量与所述用户的数量的和；
    或者，
    所述用户组的成员用户为当前保存的所述用户组的成员用户增加所述用户。
  34. 一种装置，其特征在于，包括：
    存储器和处理器，所述存储器和处理器耦合，
    所述存储器存储有程序指令，所述程序指令被所述处理器运行时，使得所述装置执行如下步骤：
    接收指示消息，所述指示消息包括监控事件配置的标识信息、用户的标识信息和指示信息，所述监控事件配置的标识信息用于指示所述用户所属用户组的第一监控事件配置，所述指示信息用于指示取消所述第一监控事件配置中所述用户的事件监控；
    根据所述指示消息，取消所述第一监控事件配置中所述用户的事件监控。
  35. 根据权利要求34所述的装置，其特征在于，所述指示消息还包括事件监控类型，所述程序指令被所述处理器运行时，使得所述装置执行如下步骤：
    取消所述第一监控事件配置中所述用户的所述事件监控类型的事件监控。
  36. 根据权利要求35所述的装置，其特征在于，所述程序指令被所述处理器运行时，使得所述装置执行如下步骤：
    根据所述指示消息，确定所述用户的上下文，所述用户的上下文指示取消所述第一监控事件配置中对所述用户的事件监控。
  37. 根据权利要求36所述的装置，其特征在于，所述程序指令被所述处理器运行时，使得所述装置执行如下步骤：
    将所述用户的上下文发送给第四网元，用于指示所述第四网元取消所述第一监控事件配置中对所述用户的事件监控。
  38. 一种装置，其特征在于，包括：
    存储器和处理器，所述存储器和处理器耦合，
    所述存储器存储有程序指令，所述程序指令被所述处理器运行时，使得所述装置执行如下步骤：
    接收指示消息，所述指示消息包括用户组的标识信息、用户的标识信息和指示信息，所述用户组的标识信息用于指示用户组，所述指示信息用于指示从所述用户组中删除所述用户，或者，用于指示在所述用户组中增加所述用户；
    若所述指示信息用于指示从所述用户组中删除所述用户，取消在所述用户组对应的监控事件配置中对所述用户的事件监控；
    若所述指示信息用于指示在所述用户组中增加所述用户，开始在所述用户组对应的监控事件配置中对所述用户进行事件监控。
  39. 根据权利要求38所述的装置，其特征在于，所述指示信息用于指示从所述用户组中删除所述用户，所述程序指令被所述处理器运行时，使得所述装置执行如下步骤：
    更新所述用户的上下文，更新后的所述用户的上下文指示所述用户不属于所述用户组；
  40. 根据权利要求38所述的装置，其特征在于，所述指示信息用于指示在所述用户组中增加所述用户，所述程序指令被所述处理器运行时，使得所述装置执行如下步骤：
    更新所述用户的上下文，更新后的所述用户的上下文指示所述用户属于所述用户组。
  41. 一种事件订阅管理系统，其特征在于，包括应用服务器、第一网元、第二网元和第三网元；
    所述应用服务器，用于向第一网元发送第一指示消息，所述第一指示消息包括监控事件配置的标识信息、用户的标识信息和指示信息，所述监控事件配置的标识信息用于指示所述用户所属用户组的第一监控事件配置，所述指示信息用于指示取消所述第一监控事件配置中所述用户的事件监控；
    所述第一网元，用于基于所述第一指示消息，确定所述第一监控事件配置的信息，其中，所述第一监控事件配置的信息包括以下至少之一：所述用户组的组成员信息、所述用户的监控事件报告次数信息；
    所述第一网元，用于向所述第二网元发送第二指示消息，所述第二指示消息包括所述监控事件配置的标识信息、所述用户的标识信息和所述指示信息；
    所述第二网元，用于向所述第三网元发送所述第二指示消息，用于指示所述第三网元取消所述第一监控事件配置中所述用户的事件监控；
    所述第三网元，用于基于所述第二指示消息，取消所述第一监控事件配置中所述用户的事件监控；
    所述第一网元，还用于向第二网元发送删除消息，用于指示所述第二网元删除所述第一监控事件配置，其中，所述删除消息为基于所述第一监控事件配置的信息，确定所述第一事件监控的报告完成后向所述第二网元发送的。
  42. 一种事件订阅管理系统，其特征在于，包括应用服务器、第一网元、第二网元和第三网元；
    所述应用服务器，用于向第一网元发送第一指示消息，所述第一指示消息包括用户组的标识信息、用户的标识信息和指示信息，所述用户组的标识信息用于指示所述用户所属用户组，所述指示信息用于指示从所述用户组中删除所述用户，或者，在所述用户组中增加所述用户；
    所述第一网元，用于根据所述第一指示消息，确定所述用户组对应的监控事件配置的信息，其中，所述监控事件配置的信息包括以下至少之一：所述用户组的组成员信息、所述用户的监控事件报告次数信息；
    所述第一网元，用于向所述第二网元发送第二指示消息，所述第二指示消息包括所述用户组的标识信息、所述用户的标识信息和所述指示信息；
    所述第二网元，用于向所述第三网元发送所述第二指示消息，用于指示所述从所述用户组中删除所述用户，或者，用于指示在所述用户组中增加所述用户；
    所述第三网元，用于若所述指示信息用于指示从所述用户组中删除所述用户，取消在所述用户组对应的监控事件配置中对所述用户的事件监控；若所述指示信息用于指示在所述用户组中增加所述用户，开始在所述用户组对应的监控事件配置中对所述用户进行事件监控；
    所述第一网元，还用于向第二网元发送删除消息，用于指示所述第二网元删除所述监控事件配置，其中，所述删除消息为基于所述监控事件配置的信息，确定所述事件监控的报告完成后向所述第二网元发送的。
  43. 一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如权利要求1-6任一项所述的方法，或如权利要求7-13任一项所述的方法，或如权利要求14-17任一项所述的方法，或如权利要求18-20任一项所述的方法。
  44. 一种计算机可读存储介质，包括指令，当所述指令在计算机上运行时，使得计算机执行如权利要求1-6任一项所述的方法，或如权利要求7-13任一项所述的方法，或如权利要求14-17任一项所述的方法，或如权利要求18-20任一项所述的方法。
PCT/CN2021/089592 2020-05-13 2021-04-25 事件订阅管理方法及装置 WO2021227843A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN202180003358.8A CN113841361B (zh) 2020-05-13 2021-04-25 事件监控管理方法及装置
EP21804508.6A EP4138341A4 (en) 2020-05-13 2021-04-25 METHOD AND APPARATUS FOR MANAGING EVENT SUBSCRIPTIONS
US17/984,588 US20230060429A1 (en) 2020-05-13 2022-11-10 Event subscription management method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010404076.6 2020-05-13
CN202010404076 2020-05-13

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/984,588 Continuation US20230060429A1 (en) 2020-05-13 2022-11-10 Event subscription management method and apparatus

Publications (1)

Publication Number Publication Date
WO2021227843A1 true WO2021227843A1 (zh) 2021-11-18

Family

ID=78526415

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/089592 WO2021227843A1 (zh) 2020-05-13 2021-04-25 事件订阅管理方法及装置

Country Status (4)

Country Link
US (1) US20230060429A1 (zh)
EP (1) EP4138341A4 (zh)
CN (1) CN113841361B (zh)
WO (1) WO2021227843A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024152176A1 (zh) * 2023-01-16 2024-07-25 北京小米移动软件有限公司 事件订阅方法、装置及设备

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102440411B1 (ko) * 2021-08-18 2022-09-02 한국인터넷진흥원 비정상 로밍 요청 탐지 방법 및 장치
CN114615049A (zh) * 2022-03-08 2022-06-10 斑马网络技术有限公司 一种针对事件订阅的权限检查方法及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110139264A (zh) * 2018-02-09 2019-08-16 华为技术有限公司 NB-IoT网络的通信方法、装置及存储介质
CN110366199A (zh) * 2018-04-09 2019-10-22 华为技术有限公司 一种事件监控方法及装置
WO2020103662A1 (en) * 2018-11-19 2020-05-28 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for event monitoring

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10136284B2 (en) * 2014-07-07 2018-11-20 Convida Wireless, Llc Coordinated grouping for machine type communications group based services
EP3278541B1 (en) * 2015-04-02 2023-01-04 InterDigital Patent Holdings, Inc. Managing mbms membership at the service capability exposure function
WO2017078485A1 (ko) * 2015-11-04 2017-05-11 엘지전자(주) 무선 통신 시스템에서 서빙 노드 이전 방법 및 이를 위한 장치
US20190394712A1 (en) * 2018-06-21 2019-12-26 Telefonaktiebolaget Lm Ericsson (Publ) Network event reporting for pdn connectivity
CN110971421B (zh) * 2018-09-30 2021-06-01 华为技术有限公司 订阅更新方法、设备及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110139264A (zh) * 2018-02-09 2019-08-16 华为技术有限公司 NB-IoT网络的通信方法、装置及存储介质
CN110366199A (zh) * 2018-04-09 2019-10-22 华为技术有限公司 一种事件监控方法及装置
WO2020103662A1 (en) * 2018-11-19 2020-05-28 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for event monitoring

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Enhancement of Monitoring Event configuration", 3GPP DRAFT; S2-1905512_ENHANCEMENT OF MONITORING EVENT CONFIGURATION(23.682)_V1.6, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Reno, NV, USA; 20190513 - 20190517, 7 May 2019 (2019-05-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051720995 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024152176A1 (zh) * 2023-01-16 2024-07-25 北京小米移动软件有限公司 事件订阅方法、装置及设备

Also Published As

Publication number Publication date
EP4138341A4 (en) 2023-10-18
CN113841361A (zh) 2021-12-24
CN113841361B (zh) 2023-06-20
US20230060429A1 (en) 2023-03-02
EP4138341A1 (en) 2023-02-22

Similar Documents

Publication Publication Date Title
WO2021227843A1 (zh) 事件订阅管理方法及装置
US12035197B2 (en) Communication method, network device, and terminal
CN109167847B (zh) 一种IPv6地址的生成方法及SMF、通信系统
US11425538B2 (en) Event monitoring method and apparatus
US10609533B2 (en) Method and device for trigger management of a common service entity (CSE) and a network element of bearer network
WO2021037069A1 (zh) 传输控制方法及装置
EP4175333A1 (en) Information collection method and apparatus, storage medium, and electronic apparatus
EP3759955A1 (en) Methods, devices, and computer programs for provisioning or controlling operator profiles in terminals
CN113300910B (zh) 获取使用速率的方法和系统、终端、接入点、mec服务器
CN102984739A (zh) 故障信息处理方法及装置
CN112584423B (zh) 网络api能力上报方法、装置及系统
US20230021904A1 (en) Method and Apparatus for Signaling Session Terminations in a Communication Network
US20220385589A1 (en) Data transmission method and apparatus
CN114554538B (zh) 流量统计方法、装置、电子设备及存储介质
CN111885613B (zh) 基于sig mesh的组网方法、节点设备以及计算机设备
CN114691734A (zh) 缓存管控方法、装置、计算机可读介质及电子设备
CN101820615B (zh) 通用集成电路卡多应用下的个人标识号的管理方法及系统
CN113811022A (zh) 异常终端拒绝方法、系统、装置及存储介质
WO2023230960A1 (zh) 测量信息的上报方法、接收方法、装置、设备及存储介质
WO2024174880A1 (zh) 一种数据统计方法及装置
WO2023016103A1 (zh) 集成接入和回传节点的管理方法及装置
CN110830279A (zh) 管理服务的管理方法及装置
WO2024164640A1 (zh) 一种通信方法、通信装置及通信系统
WO2023019589A1 (zh) 载波选取方法、装置、设备及存储介质
CN115065995B (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: 21804508

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021804508

Country of ref document: EP

Effective date: 20221117

NENP Non-entry into the national phase

Ref country code: DE