WO2021227843A1

WO2021227843A1 - Event subscription management method and device

Info

Publication number: WO2021227843A1
Application number: PCT/CN2021/089592
Authority: WO
Inventors: 周晓云; 阎亚丽
Original assignee: 华为技术有限公司
Priority date: 2020-05-13
Filing date: 2021-04-25
Publication date: 2021-11-18
Also published as: CN113841361B; EP4138341A1; CN113841361A; US20230060429A1; EP4138341A4

Abstract

Embodiments of the present application provide an event subscription management method and device. The method comprises: receiving an instruction message, the instruction message comprising identifier information of an event subscription, identifier information of a user, and instruction information, the identifier information of an event subscription being used for indicating a first event subscription of a user group to which the user belongs, and the instruction information being used for instructing to cancel event detection of the user in the first event subscription; determining information of the first event subscription according to the instruction message, wherein the information of the first event subscription comprises at least one of the following: information of members of a user group and information of the number of event reports of a user; and sending a delete message to a second network element to instruct the second network element to delete the first event subscription, wherein the delete message is sent to the second network element after determining, on the basis of the information of the first event subscription, that the report of the first event subscription is completed. The present application can implement event subscription management with a user as a granularity.

Description

Event subscription management method and device

This application claims the priority of the Chinese patent application filed with the State Intellectual Property Office of China with application number 202010404076.6 on May 13, 2020, the entire content of which is incorporated into this application by reference.

Technical field

The embodiments of the present application relate to the field of communications, and in particular, to an event subscription management method and device.

Background technique

At present, the Service Capability Exposure (SCE) architecture can provide third-party service providers with service capabilities, such as event monitoring capabilities. The SCE architecture can perform events on each user in the user group based on instructions issued by the third party. Monitoring (Event Monitoring).

However, the 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.

Summary of the invention

This application provides an event monitoring management method, device, and system, which can implement event monitoring management with user-based granularity.

In order to achieve the above objectives, this application adopts the following technical solutions:

In the first aspect, 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.

Based on the above method, it is realized to provide a more flexible management method, when the user's event monitoring is managed, it will not affect the event monitoring of other users, so as to realize the management of event monitoring based on the granularity of the user.

In a possible implementation manner, 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.

Based on the above method, 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.

In a possible implementation manner, 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.

Based on the above method, by modifying the number of group members of the user group, the purpose of eliminating users to be cancelled can be achieved.

In a possible implementation manner, 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.

Based on the above method, by modifying the group member list of the user group, the purpose of removing users to be cancelled can be achieved.

In a possible implementation manner, 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.

Based on the above method, the users who need to be cancelled are marked to achieve the purpose of eliminating users to be cancelled.

In a possible implementation manner, 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

Based on the above method, by modifying the number of group members of the user group and deleting the received user report, the purpose of eliminating the user to be cancelled can be achieved.

In a possible implementation manner, 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.

Based on the above method, by deleting the received user's report, combined with the method of marking the user, the purpose of eliminating the user to be cancelled can be achieved.

In a possible implementation manner, 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.

Based on the above method, by combining the deletion of the received user report and the modification of the group member list of the user group, the purpose of eliminating the user to be cancelled can be achieved.

In a possible implementation manner, 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.

Based on the above method, 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.

In a possible implementation manner, 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.

In a possible implementation manner, 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.

In a possible implementation manner, 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.

In a second aspect, 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.

In a possible implementation manner, 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.

In a possible implementation manner, 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.

In a possible implementation manner, 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.

In a possible implementation, 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.

In a possible implementation manner, 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 When a report is configured for a monitoring event, the monitoring event report corresponding to the user is excluded.

In a possible implementation manner, 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.

In a possible implementation manner, 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.

In a possible implementation manner, 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.

In a possible implementation manner, 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.

In a possible implementation manner, 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.

In a possible implementation manner, 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.

In a third aspect, 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.

In a possible implementation manner, the instruction message further includes the event monitoring type, and 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.

In a possible implementation manner, 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.

Based on the above method, 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.

In a possible implementation manner, 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.

In a fourth aspect, 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.

In a possible implementation manner, the instruction information is used to indicate the deletion of the user from the user group, and 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;

In a possible implementation manner, the indication information is used to indicate that a user is added to the user group, and the method further includes: updating the user's context, and the updated user's context indicates that the user belongs to the user group.

In a fifth aspect, 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.

In a possible implementation manner, if the instruction information is to delete a user from a user group, the group member update information is identification information of the user.

In a possible implementation manner, if the instruction information is to add a user to a user group, the group member update information is identification information of the user or the number of users in the user group.

In a possible implementation manner, if the instruction information is to delete a user from a 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.

In a possible implementation manner, if the instruction information is to delete a user from a 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 set includes the user group.

In a sixth aspect, 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.

In a possible implementation manner, when the program instructions are executed by the processor, 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.

In a possible implementation manner, when the program instructions are executed by the processor, 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.

In a possible implementation manner, when the program instructions are executed by the processor, 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.

In a possible implementation manner, when the program instructions are executed by the processor, 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.

In a seventh aspect, 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. ; 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; 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.

In a possible implementation manner, when the program instructions are executed by the processor, the device executes the following steps: the user's monitoring event report times are identified as the maximum report times.

In a possible implementation manner, 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.

In an eighth aspect, 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.

In a possible implementation manner, the indication message also includes the event monitoring type. When the program instruction is executed by the processor, the device executes the following steps: cancel the event monitoring of the user's event monitoring type in the first monitoring event configuration.

In a possible implementation manner, when the program instructions are executed by the processor, 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.

In a possible implementation manner, when the program instructions are executed by the processor, 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.

In a ninth aspect, 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. 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, 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. User; if the instruction information is used to instruct to delete a 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 instruct to add a user to the user group, start to add a user to the user group Event monitoring is performed on users in the monitoring event configuration.

In a possible implementation, the instruction information is used to indicate the deletion of a user from the user group. When the program instruction is executed by the processor, 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;

In a possible implementation manner, the indication information is used to indicate the addition of users to the user group. When the program instructions are executed by the processor, the device executes the following steps: update the user context, and the updated user context indicates that the user belongs to the user Group.

In a tenth aspect, 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. Delete the user in the user group, or add the user to the user group; based on the first indication message, send a second indication message to the first network element, where the second indication message includes the identifier of the monitoring event configuration Information and group member information of the user group, and the identification information of the monitoring event is used to indicate the configuration of the monitoring event of the user group.

In a possible implementation manner, if the instruction information is to delete a user from the user group, when the program instruction is executed by the processor, 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.

In a possible implementation manner, if the instruction information is to delete a user from the user group, when the program instruction is executed by the processor, 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.

In an eleventh aspect, 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 event is completed.

In a twelfth aspect, 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.

In a thirteenth aspect, 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.

In a fourteenth aspect, 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.

In a fifteenth aspect, 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.

In a sixteenth aspect, 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. Event monitoring of users in the 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.

In a seventeenth aspect, 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 used to instruct adding users to the user group, start monitoring the user in the monitoring event configuration corresponding to the user group Event monitoring; the first network element is also used to 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 to determine that the event monitoring report is complete Sent back to the second network element.

In an eighteenth aspect, 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.

In a nineteenth aspect, 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.

In a twentieth aspect, an embodiment of the present application provides a chip, which includes a processing circuit and transceiver pins. Wherein, 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.

Description of the drawings

In order to explain the technical solutions of the embodiments of the present application more clearly, the following will briefly introduce the drawings that need to be used in the description of the embodiments of the present application. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative labor.

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.

Detailed ways

The technical solutions in the embodiments of the present application will be described clearly and completely in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of them. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this application.

The term "and/or" in this article is only an association relationship describing the associated objects, which means that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, exist alone B these three situations.

The terms "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. For example, the 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.

In the embodiments of the present application, 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.

In the description of the embodiments of the present application, unless otherwise specified, the meaning of "plurality" means two or more. For example, 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. With the development of wireless communication technology, 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.

In order to enable those skilled in the art to better understand the technical solutions of the present application, the following briefly introduces the background technologies that may be involved.

1) SCE architecture

Figure 1 shows the architecture diagram of service capability opening in the 4th generation mobile communication technology (4G) network. Referring to Figure 1, 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).

Specifically, a service capability server (Services Capability Server, SCS)/application server (AS) can be regarded as a third-party service provider. 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.

Figure 2 shows the architecture diagram of service capability opening in the 5th generation mobile communication technology (5G) network. Referring to Figure 2, 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).

Among them, 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.

2) Event monitoring process

The following is a detailed description of the configuration process and monitoring process of monitoring events in the above two business capability open architectures:

a. Monitoring Event Configuration process based on the business capability open architecture of the 4G network.

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.

Specifically, 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.

Exemplarily, 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.

Specifically, 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. Optionally, 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. For example, 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.

It should be noted that the correspondence between users, user groups and monitoring event configuration can be understood as: a user can belong to different user groups, a single user group can correspond to one or more monitoring event configurations, and each monitoring event configuration can be Correspond to one or more event monitoring types. For example, 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; User group 1 also corresponds to monitoring event configuration 2 (TLTRI2), which is configured to monitor UE reachability monitoring events of user group 1, that is, the event monitoring type of monitoring event configuration 2 is UE reachability. User group 2 corresponds to monitoring event configuration 3 (TLTRI13), which is configured to monitor the Loss of connectivity monitoring event of user group 2, that is, the event monitoring type of event financial control configuration 3 is Loss of connectivity.

Optionally, the monitoring request message may also include at least one of the following: the maximum number of reports and the monitoring duration. Exemplarily, 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. Exemplarily, 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. For example: User group 1 includes 3 users. When the number of reports for each user saved by SCEF corresponding to the specified monitoring event configuration reaches the maximum number of reports, it can be determined that the report of the monitoring event configuration is completed. In addition, 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.

It should be noted that, as described above, 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.

It should be further noted that if 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.

Specifically, 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.

Among them, 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.

Specifically, 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.

Exemplarily, the monitoring request message includes but is not limited to: External Group ID, SCEF identification information, SCEF Reference ID, and Monitoring Type. Optionally, 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.

Specifically, 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).

Specifically, 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. Exemplarily, the HSS stores subscription information, and 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).

Optionally, the HSS also saves the correspondence between each user and the MME. Specifically, 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.

Specifically, 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.

Specifically, after SCEF receives the confirmation message sent by HSS, SCEF creates monitoring event configuration (that is, information for determining monitoring event configuration). 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.

Then, 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.

Optionally, 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.

Specifically, as described in step 104, 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.

Specifically, 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. Exemplarily, 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.

In step 108, the MME/SGSN performs event monitoring.

Specifically, the MME/SGSN receives the subscriber data insertion request message sent by the HSS, and obtains the parameters carried by it. Exemplarily, 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.

After the HSS requests the MME/SGSN to perform event monitoring for each user in the user group, 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.

As mentioned above, 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.

Specifically, 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.

It should be noted that 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.

b. The reporting process of monitoring events based on the business capability open architecture of the 4G network.

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.

Specifically, as described above, the MME/SGSN performs event monitoring on the user in the monitoring event configuration. In this embodiment, the MME/SGSN detects the user's monitoring event.

Step 202: The MME/SGSN sends a monitoring indication message to the SCEF.

Specifically, 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.

Exemplarily, 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.

For example: 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.

As mentioned above, 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.

In a possible implementation manner, if the monitoring event is configured as one-time event monitoring, after the MME/SGSN sends a monitoring indication message to the SCEF, the user's monitoring event configuration information is deleted.

Step 203, SCEF processing.

Specifically, after receiving the monitoring instruction message, the SCEF saves the number of reported events corresponding to the user.

In an example, if the number of reported events of each user in the user group reaches the maximum number of reports, 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.

In another example, if the number of reported events of each monitoring type of each user in the user group reaches the maximum number of reported events, 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.

Specifically, the SCEF sends a monitoring indication message to the SCS/AS to indicate that the user has a monitoring event.

Exemplarily, the message includes but is not limited to: TLTRI, monitoring event report, and user identification information. Among them, TLTRI is found by SCEF based on SCEF Reference ID.

Optionally, 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.

c. The configuration process of monitoring events based on the business capability opening architecture of the 5G network. In this process, the monitoring event configuration 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.

Specifically, 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). Exemplarily, the monitoring event subscription request message includes but is not limited to: AF notification endpoint, event identifier, and External Group ID.

Wherein, 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. Exemplarily, the notification endpoint of the AF may be target notification address information, or target notification address information and notification association identification information.

Optionally, there may be one or more event identifiers carried in the message, that is, a single monitoring event subscription may correspond to one or more event identifiers.

Optionally, 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.

For other details, 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.

Specifically, the monitoring event subscription is authorized, and the parameters in the monitoring event subscription request message are saved.

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.

Specifically, NEF sends a monitoring event subscription request message to UDM for monitoring event subscription.

Exemplarily, the monitoring event subscription request message includes but is not limited to: External Group ID, event identifier, NEF notification endpoint, etc. Optionally, the message may also include some or all of the parameters in step 301. For details, reference may be made to the prior art, which is not limited in this application.

Among them, 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.

In step 304, the UDM creates a monitoring event subscription based on the monitoring event subscription request message.

Specifically, 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.

Exemplarily, 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.

In step 305a, the UDM sends the AMF monitoring event subscription request message.

Specifically, 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.

Exemplarily, 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. For details, refer to the prior art, which is not limited in this application.

In step 306a, the AMF returns a confirmation message.

Specifically, 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.

Exemplarily, 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.

Optionally, 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.

It should be noted that the correspondence between users and user groups has been pre-stored in each network element.

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. Correspondingly, 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.

It is similar to step 305a and will not be repeated here.

In step 306b, the SMF returns a confirmation message.

Specifically, the SMF determines the monitoring event subscription information based on the parameters in the monitoring event subscription request message.

Exemplarily, 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. Wherein, 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. Correspondingly, UDM writes the SMF subscription association representation into the user's monitoring event subscription information.

Other details are similar to step 306a, and will not be repeated here.

Step 307: UDM sends a confirmation message to NEF.

Exemplarily, after UDM determines that the AMF or SMF of all service user groups has completed the monitoring event subscription, 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.

For other details, please refer to step 105, which will not be repeated here.

Step 308: NEF sends a confirmation message to SCS/AS.

Specifically, after receiving the confirmation message sent by the UDM, 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. Exemplarily, 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.

Exemplarily, 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.

d. The report process of monitoring events based on the business capability open architecture of the 5G network.

Fig. 6 is a schematic diagram of an exemplary monitoring process of event monitoring, referring to Fig. 6, specifically:

In step 401a, the AMF detects a monitoring event.

The specific details are similar to step 201, and will not be repeated here.

Step 402a: AMF sends an event notification message to NEF.

Specifically, 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. In addition, the AMF subtracts 1 from the remaining number of reports in the information subscribed to by the user's monitoring event.

Other details are similar to step 202, and will not be repeated here.

Step 403a, NEF sends a confirmation message to AMF.

Specifically, the NEF sends a confirmation message to the AMF to indicate that the event notification message sent by the AMF is received.

In step 401b, the SMF detects a monitoring event.

The specific details are similar to step 201, and will not be repeated here.

Step 402b, SMF sends an event notification message to NEF.

Specifically, 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. In addition, SMF subtracts 1 from the remaining number of reports in the information subscribed to by the user's monitoring event.

Other details are similar to step 202, and will not be repeated here.

Step 403b, NEF sends a confirmation message to SMF.

Specifically, 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.

Specifically, after receiving the AMF or SMF event notification message, the NEF saves the number of reported events corresponding to the user.

In an example, if the number of reported events of each user in the user group corresponding to the monitoring event subscription reaches the maximum number of reports, 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.

In another example, if the number of reported events identified by each event of each user in the user group reaches the maximum number of reports, 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.

In step 405, the NEF sends an event notification message to the AF.

Specifically, 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.

For other details, please refer to step 204, which will not be repeated here.

Step 406: AF returns a confirmation message to NEF.

3) Incident monitoring management

The following is a detailed description of the monitoring event configuration management methods in the 4G/5G service capability open architecture:

a. The management process of monitoring event configuration based on the business capability open architecture of the 4G network.

Fig. 7 is a schematic diagram of an exemplary management process of event monitoring, referring to Fig. 7, specifically:

In step 501, the SCS/AS sends a monitoring request message to the SCEF.

Specifically, 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.

In step 502, the SCEF sends a monitoring request message to the HSS.

Specifically, 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.

Specifically, as described above, 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.

Specifically, 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.

Specifically, 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.

Specifically, after 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.

In step 507, the MME/SGSN deletes the information of monitoring event configuration according to the request message for inserting subscriber data.

Specifically, 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.

In step 508, the MME/SGSN sends a subscriber data insertion response message to the HSS.

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.

b. The management process of monitoring event subscription based on the business capability open architecture of the 5G network.

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.

Specifically, 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.

Specifically, 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.

In step 603a, the UDM sends a monitoring event subscription request message to the AMF.

Specifically, as described above, 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, and steps 603b to 605b are executed for each SMF.

Specifically, 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.

In step 604a, the AMF deletes the information of the monitoring event subscription according to the monitoring event subscription request message.

Specifically, 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.

In step 603b, the UDM sends a monitoring event subscription request message to the SMF.

Specifically, 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.

In step 604b, the SMF deletes the information of the monitoring event subscription according to the monitoring event subscription request message.

Specifically, 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.

Specifically, after the UDM determines that all AMF/SMFs corresponding to the monitoring event subscription perform the monitoring event subscription deletion, the UDM deletes the monitoring event subscription and sends a confirmation message to the NEF, which carries the UDM acceptance instruction information.

In step 607, the NEF sends a confirmation message to the AF.

Specifically, the NEF deletes the monitoring event subscription, and sends a confirmation message to the AF, and the message carries the acceptance instruction information.

As can be seen from the above, in the prior art, the management of monitoring event configuration (also called monitoring event subscription in 5G) 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. Specifically, 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. Specifically, this application can implement monitoring event configuration for users. The cancellation operation of the user group, and the management method of adding and deleting users in the user group. 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. Specific examples of users, scenario three is a specific embodiment of canceling the user's monitoring event configuration in a 5G network, and scenario four is a specific embodiment of adding or deleting a user's monitoring event configuration in a 5G network.

scene one

In conjunction with FIG. 1, FIG. 9 is a schematic flowchart of an event monitoring management method in an embodiment of the application, and in FIG. 9:

Specifically, 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.

Specifically, 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.

Exemplarily, the message includes but is not limited to: identification information of the monitoring event configuration, user identification information, and cancellation instruction information.

Wherein, the identification information of the monitoring event configuration is used to indicate the corresponding monitoring event configuration. Exemplarily, the identification information of the monitoring event configuration may be TLTRI.

The user's identification information is used to identify the corresponding user. Illustratively, 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. It should be noted that the designated monitoring event configuration refers to the monitoring event configuration identified by the identification information of the monitoring event configuration, and 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. Optionally, 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.

In a possible implementation, the monitoring request message may also include one or more event monitoring type information. As mentioned above, in the monitoring event configuration process, a single monitoring event configuration can correspond to one or more event monitoring types In this application, 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.

For example, user 1 belongs to user group 1, and user group 1 corresponds to monitoring event configuration 1 and monitoring event configuration 2. Among them, monitoring event configuration 1 corresponds to monitoring event type 1 and monitoring event type 2. Exemplarily, 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. Exemplarily, 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.

In step 702, the SCEF determines the information of the monitoring event configuration according to the monitoring request message.

Specifically, 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.

Specifically, SCEF can query the corresponding monitoring event configuration information based on the identification information of the monitoring event configuration. As described above, 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.

When the number of reported events of each user in the user group corresponding to the monitoring event configuration reaches the maximum number of reports (that is, regardless of the monitoring type), it means that the report of the monitoring event configuration is completed (that is, the maximum number of reports is the granularity of each user. ). In this application, in order to achieve the purpose of eliminating user reports, 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.

Manner 5: SCEF deletes the received report of the user, and the number of group members of the corresponding user group minus the number of users that need to be eliminated.

Mode 6: SCEF deletes the received report of the user, and SCEF records the user's identification information and marking information.

Manner 7: SCEF deletes the received report of the user, and SCEF deletes the user from the saved user list of the user group.

It should be noted that the prerequisite for the execution of Mode 5 to Mode 7 is that the user's report has been received.

The following describes the above methods:

For mode 1, the updated monitoring event configuration includes the corresponding relationship between the user’s identification information and the tag information. Illustratively, 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. When performing statistics on the report of the user, you can determine that the user’s report is ignored (or excluded) in the monitoring event configuration according to the marked information.

For the second method, by setting the report of the user to be cancelled as the maximum number of reports, the SCEF defaults to the completion of the user's report.

For mode three, as described above, 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. For example: if the number of group members of user group 1 corresponding to monitoring event configuration 1 is 3, 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.

Regarding method four, as mentioned above, 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.

Regarding methods five to seven, on SCEF, the user’s monitoring event configuration information may also include reported reports. SCEF deletes the user’s report in the monitoring event configuration. At the same time, methods one, three and four can be combined. So as to achieve the purpose of eliminating users.

In a possible implementation manner, method three can also be combined with method one to prevent statistical errors caused by signal transmission delays. Specifically, after SCEF processing, 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. However, due to signal delay or equipment processing capacity limitations or time errors, 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.

In summary, 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. As mentioned above, when the 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. In this application, if the monitoring of a user configured for monitoring events is canceled, SCEF ignores the user's report when counting event monitoring reports, that is, only counts the reports of users other than the user.

It should be noted that if the SCS/AS request message is to cancel partial event monitoring of the user, that is, the monitoring request message in step 701 carries event monitoring type information, then SCEF does not need to perform the above steps, that is, After the SCEF receives the monitoring request message, step 703 is executed.

When the number of reported events of each monitoring type of each user in the user group corresponding to the monitoring event configuration reaches the maximum number of reports (that is, the monitoring type is distinguished), it means that the report of the monitoring event configuration is completed (that is, the maximum number of reports is Per user per monitoring type granularity), in this application, if 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.

Manner 2: SCEF sets the number of reports for each monitoring type of the user as the maximum number of reports, that is, SCEF defaults to the completion of the user's report.

In summary, 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. As mentioned above, when the 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. In this application, if the monitoring of the monitoring event type that needs to be canceled by the user who configures the monitoring event is canceled, 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.

It should be noted that if 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.

Specifically, 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.

Exemplarily, the identification information of the monitoring event configuration in the monitoring request message may be the SCEF Reference ID. Specifically, 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.

Optionally, 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.

Optionally, 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. When the subsequent SCS/AS re-executes the monitoring event configuration for this user group, 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. Exemplarily, 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.

Specifically, 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.

Specifically, 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.

Specifically, 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.

Specifically, 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.

Exemplarily, the user identification information inserted in the subscriber request message may be the user's internal identification information. Specifically, 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.

Exemplarily, 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.

Optionally, 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.

In step 708, the MME/SGSN cancels the event monitoring of the user configured for the monitoring event.

Specifically, 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.

Specifically, as mentioned above, 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. In this application, 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.

In a possible implementation, if it is necessary to cancel part of the event monitoring of the user in the monitoring event configuration, that is, if the subscription user request message includes event monitoring type information, 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.

When the maximum number of reports is per user granularity, an example is as follows: User 1 belongs to user group 1, and user group 1 corresponds to monitoring event configuration 1 and monitoring event configuration 2. Among them, monitoring event configuration 1 includes event monitoring type 1 and event monitoring type 2. In this embodiment, it is necessary to cancel the event monitoring type 1 of the user in the monitoring event configuration 1. 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. For example, user 1 belongs to user group 1, and user group 1 corresponds to monitoring event configuration 1 and monitoring event configuration 2. Among them, monitoring event configuration 1 includes event monitoring type 1 and event Monitoring type 2. In this embodiment, you need to cancel the user's event monitoring type 1 in monitoring event configuration 1. 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.

In step 709, the MME/SGSN sends a subscriber data insertion response message to the HSS.

Specifically, 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.

It should be noted that if the event monitoring of multiple users in the monitoring event configuration is canceled, 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.

In other preferred embodiments, 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.

In the above embodiment, if 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.

Scene two

In conjunction with FIG. 1, FIG. 10 is a schematic flowchart of an event monitoring management method in an embodiment of the application, and in FIG. 10:

In step 801, the SCS/AS sends a group user configuration management request message to the SCEF.

Specifically, 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. 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.

Exemplarily, 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.

Exemplarily, 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.

Optionally, 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.

In step 802, the SCEF sends a group user management request message to the HSS.

Specifically, the SCEF sends a user management request message to the HSS to instruct the HSS to update the subscription information.

Exemplarily, the message includes but is not limited to: identification information of the user group, identification information of the user, and indication information. 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.

Specifically, as described above, the HSS stores subscription information. In this embodiment, if users need to be added or deleted from the user group, the HSS updates the subscription information accordingly.

Specifically, 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.

In an example, if the instruction information is the deletion instruction information, 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.

In another example, if the instruction information is adding instruction 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.

In step 804, the HSS sends a confirmation message to the SCEF.

Specifically, 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.

Specifically, after receiving the confirmation message from the HSS, 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.

Specifically, 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.

In an example, if the instruction information is the deletion instruction information, that is, the user is deleted from 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.

In another example, if the instruction information is adding instruction information, that is, adding a user to the user group, 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.

In a possible implementation manner, 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.

Specifically, SCEF sends a confirmation message to SCS/AS to instruct SCEF to complete relevant configuration. The message can carry user group identification information.

In step 807, the HSS sends a request message for inserting subscriber data to the MME/SGSN.

Specifically, 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.

Specifically, 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.

Specifically, as described above, 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. Exemplarily, the identification information of the monitoring event configuration of the user group may be the SCEF Reference ID. Specifically, 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.

Exemplarily, the user's identification information may be the user's internal identification information.

In a possible implementation, if the indication information is used to indicate the addition of users to the user group, the message also includes related parameters for monitoring event configuration. Illustratively, 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.

In step 808, the MME/SGSN starts or cancels event monitoring of the user based on the insert subscriber request message.

Specifically, 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.

In an example, if the indication information is deletion indication information, the MME/SGSN deletes one or more monitoring event configurations corresponding to the user in the user group. Example: Suppose user 1 belongs to user group 1 and user group 2, user group 1 corresponds to monitoring event configuration 1, where the monitoring event configuration identifier is SCEF Reference ID1 and monitoring event configuration 2, where the monitoring event configuration identifier is SCEF Reference ID2, and the user Group 2 corresponds to monitoring event configuration 3 and monitoring event configuration 4. To delete user 1 from user group 1, 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.

In another example, if the indication information is adding indication information, 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.

In step 809, the MME/SGSN sends a confirmation message to the HSS.

Specifically, 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.

In other preferred embodiments, 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.

In conjunction with FIG. 1, FIG. 11 is a schematic flowchart of an event monitoring management method in an embodiment of the application, and in FIG. 11:

Step 901: The SCS/AS sends a group user configuration management request message to the SCEF.

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,

For specific details, 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.

For specific details, refer to step 803, which will not be repeated here.

Step 904, the HSS sends a confirmation message to the SCEF.

For specific details, please refer to step 804, which will not be repeated here.

Step 905: SCEF sends a confirmation message to SCS/AS.

Specifically, 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.

In step 906, the HSS sends a monitoring instruction message to the SCEF.

Specifically, 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.

In a possible implementation, if a user needs to be deleted from a 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. Exemplarily, the user's identification information may be the user's external identification information.

In another possible implementation, if users need to be added to the user group, 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.

In step 907, the SCEF determines the monitoring event configuration information corresponding to the user group.

Specifically, SCEF can update all monitoring event configuration information corresponding to the user group based on the monitoring instruction message sent by the HSS.

For specific details, please refer to step 805, which will not be repeated here.

In step 908, the HSS sends a request message for inserting subscriber data to the MME/SGSN.

In step 909, the MME/SGSN starts or cancels event monitoring of the subscriber based on the insert subscriber request message.

In 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.

In other preferred embodiments, 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

Scene three

With reference to FIG. 2, FIG. 12 is a schematic flowchart of a monitoring event subscription management method in an embodiment of the application. In FIG. 12:

Specifically, the 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.

Specifically, 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.

Exemplarily, 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. Illustratively, 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. For example, 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.

In a possible implementation, the monitoring request message may also include one or more event identifiers. As described above, in the monitoring event subscription process, a single monitoring event subscription may correspond to one or more event monitoring types. In this application, 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.

For other details, please refer to step 701, which will not be repeated here.

Step 1002: NEF sends a monitoring instruction message to UDM.

Specifically, 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.

Exemplarily, the identification information of the monitoring event subscription in the monitoring request message may be a UDM subscription associated identification, and the identification information of the user may be the external identification information of the user.

Optionally, 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.

Optionally, 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. Exemplarily, 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. When 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.

Specifically, 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.

Specifically, 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.

Exemplarily, the user identification information in the monitoring event subscription request message may be the user's internal identification information. Specifically, 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.

Exemplarily, 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.

Optionally, 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.

In step 1004a, the AMF cancels the event monitoring of the user in the monitoring event subscription based on the monitoring event subscription request message.

Specifically, 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.

In a possible implementation, if the maximum number of reports is per user granularity, for example, 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. Based on the monitoring event subscription request message, 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. Exemplarily, 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. In addition, 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. .

In a possible implementation, if the maximum number of reports is per user granularity, for example, the monitoring event subscription request message carries user identification information, monitoring event subscription identification information, event identification and cancellation indication information. Exemplarily, 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.

In a possible implementation, if the maximum number of reports is the granularity of each event identification per user, for example, 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. Based on the monitoring event subscription request message, AMF cancels the event monitoring of the user's specific event identifier in the monitoring event subscription. Exemplarily, 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. In addition, 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. (Exemplarily, 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.

Specifically, the AMF sends a confirmation message to the UDM to indicate that the AMF has completed the relevant configuration.

In step 1003b, the UDM sends an insert monitoring event subscription request message to the SMF.

Refer to step 1003a, which will not be repeated here.

In step 1004b, the SMF cancels the event monitoring of the user in the monitoring event subscription based on the monitoring event subscription request message.

Refer to step 1004a, which will not be repeated here.

Step 1005b, SMF sends a confirmation message to UDM.

It should be noted that if the event monitoring of multiple users in the monitoring event subscription is canceled, 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.

Specifically, 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.

The specific details are similar to step 702, and will not be repeated here.

It should be noted that 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.

Specifically, 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.

In other preferred embodiments, 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.

In the foregoing embodiment, if 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.

Scene four

In conjunction with FIG. 2, FIG. 13 is a schematic flowchart of the event subscription management method in an embodiment of the application. In FIG. 13:

Step 1101: The AF sends a group user configuration management request message to the NEF.

Specifically, 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.

Step 1102: NEF sends a group user management request message to UDM.

Specifically, NEF sends a user management request message to UDM, which is used to instruct UDM to update subscription information.

Step 1103: UDM updates the subscription information based on the group user management request message.

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.

Specifically, 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.

Exemplarily, 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. In an example, if the instruction information indicates that the user is to be deleted from the user group, 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.

In another example, if the indication information indicates that a user is added to 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.

It should be noted that, as mentioned above, in the configuration process of the 5G network, 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.

In an example, if the UDM instructs to delete the user from the user group, 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. For specific details, please refer to step 1004a, which will not be repeated here.

In another example, if the UDM instructs to add a user from the user group, 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.

In a possible implementation, if 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.

It should be noted that, for each user that needs to be added or deleted, 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.

It should be noted that step 1108 can be executed before step 1102, which is not limited in this application.

Step 1109: NEF sends a confirmation message to AF.

In other preferred embodiments, 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.

In the above embodiment, if 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.

With reference to FIG. 2, FIG. 14 is a schematic flowchart of the event monitoring management method in an embodiment of the application, and in FIG. 14:

Specifically, 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.

In 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.

In 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.

In step 1208, the NEF sends a user group management confirmation message to the AF.

Step 1209: UDM sends an event notification message to NEF.

Specifically, 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.

In a possible implementation, if a user needs to be deleted from a 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. Exemplarily, 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.

In another possible implementation, if users need to be added to the user group, 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.

Specifically, NEF can update all event subscription information corresponding to the user group based on the event notification message sent by UDM.

In other preferred embodiments, 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 foregoing mainly introduces the solutions provided by the embodiments of the present application from the perspective of interaction between various network elements. It can be understood that, in order to realize the above-mentioned functions, each network element includes a hardware structure and/or software module corresponding to each function. Those skilled in the art should easily realize that in combination with the units and algorithm steps of the examples described in the embodiments disclosed herein, 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. For example, 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.

In the case of dividing each functional module corresponding to each function, and in the case of dividing each functional module corresponding to each function, 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.

In an example, 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.

In a possible implementation manner, 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.

In a possible implementation manner, the processing module 102 is configured to delete the saved user's monitoring event report times.

In a possible implementation manner, 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.

In another example, 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.

In a possible implementation manner, the processing module 102 is configured to identify the number of monitoring event reports of the user as the maximum number of reports.

In another example, 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.

In a possible implementation manner, the indication message further includes an event monitoring type, and the processing module 102 is configured to cancel the event monitoring of the user's event monitoring type in the first monitoring event configuration.

In a possible implementation, the indication message also includes an event monitoring type, and 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.

In a possible implementation manner, 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.

In another example, 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.

In a possible implementation manner, 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;

In a possible implementation manner, 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.

In another example, 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.

The components of the device 200 are coupled together through a bus 204, where the bus system 204 includes a power bus, a control bus, and a status signal bus in addition to a data bus. However, for clear description, various buses are marked as the bus system 204 in the figure.

Optionally, the memory 203 may be used for storing instructions in the foregoing method embodiments.

It should be understood that the device 200 according to the embodiment of the present application 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.

Among them, all relevant content of the steps involved in the above method embodiments can be cited in the functional description of the corresponding functional module, which will not be repeated here.

Based on the same technical concept, 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.

Based on the same technical concept, 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.

Based on the same technical concept, 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.

Based on the same technical concept, 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. 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. Of course, the storage medium may also be an integral part of the processor. The processor and the storage medium may be located in the ASIC. In addition, the ASIC may be located in a network device. Of course, the processor and the storage medium may also exist as discrete components in the network device.

Those skilled in the art should be aware that, in one or more of the foregoing examples, the functions described in the embodiments of the present application can be implemented by hardware, software, firmware, or any combination thereof. When implemented by software, 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.

The embodiments of the application are described above with reference to the accompanying drawings, but the application is not limited to the above-mentioned specific embodiments. The above-mentioned specific embodiments are only illustrative and not restrictive. Those of ordinary skill in the art are Under the enlightenment of this application, many forms can be made without departing from the purpose of this application and the scope of protection of the claims, all of which fall within the protection of this application.

Claims

An event subscription management method, characterized in that it comprises:

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, the The indication information is used to instruct to cancel the event monitoring of the user in the first monitoring event configuration;

According to the instruction message, determine the information of the first monitoring event configuration, where the information of the first monitoring event configuration includes at least one of the following: group member information of the user group, and monitoring event report of the user Times information;

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 first After the event monitoring report is completed, it is sent to the second network element.
The method according to claim 1, wherein the information of the first monitoring event configuration indicates that the monitoring event report corresponding to the user is excluded when the report of the first monitoring event configuration of the user group is counted.
The method according to claim 1, wherein the information of the first monitoring event configuration is used to indicate that the monitoring event report corresponding to the user has been completed.
The method according to any one of claims 1 to 3, wherein the group member information of the user group comprises:

The number of group members of the user group is the difference between the number of group members of the user group currently saved and the number of users;

or,

The member user of the user group deletes the user as a member user of the currently saved user group.
The method according to claim 4, wherein the determining the information of the configuration of the first monitoring event comprises:

Delete the saved monitoring event report times of the user.
The method according to any one of claims 1 to 3, wherein the determining the information for the configuration of the first monitoring event comprises:

The number of monitoring event reports of the user is set to the maximum number of reports.
An event subscription management method, characterized in that it comprises:

Receive an instruction message, where the instruction message includes user group identification information, user identification information, and instruction information, where the user group identification information is used to indicate the user group to which the user belongs, and the instruction information is used to instruct the user Delete the user from the user group, or add the user 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, and monitoring event report of the user 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, after it is determined that the event monitoring report is completed Sent to the second network element.
The method according to claim 7, wherein the indication information is used to indicate that the user is deleted from the user group, and the information of the monitoring event configuration indicates that the monitoring event configuration of the user group is calculated When reporting, the report of the monitoring event corresponding to the user is excluded.
The method according to claim 7 or 8, wherein the instruction information is used to instruct to delete the user from the user group, and the number of group members of the user group is that of the currently saved user group The difference between the number of group members and the number of users;

or,

The member user of the user group deletes the user as a member user of the currently saved user group. .
The method according to claim 9, wherein the determining information of the monitoring event configuration corresponding to the user group comprises:

Delete the saved monitoring event report times of the user.
The method according to claim 7 or 8, wherein the determining information of the monitoring event configuration corresponding to the user group comprises:

The user's monitoring event report times are identified as the maximum report times.
The method according to claim 8, wherein the indication information is used to add the user 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 method according to claim 7 or 12, wherein the instruction information is used to add the user to the user group, and the number of group members of the user group is the currently saved group of the user group The sum of the number of members and the number of said users;

or,

The member users of the user group add the users to the currently saved member users of the user group. .
An event subscription management method, characterized in that it comprises:

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, the The indication information is used to instruct to cancel the event monitoring of the user in the first monitoring event configuration;

According to the instruction message, cancel event monitoring of the user in the first monitoring event configuration.
The method according to claim 14, wherein the indication message further includes an event monitoring type, and the canceling the event monitoring of the user in the first monitoring event configuration includes:

Cancel the event monitoring of the event monitoring type of the user in the first monitoring event configuration.
The method according to claim 14, wherein the method further comprises:

According to the instruction message, the context of the user is determined, and the context of the user instructs to cancel event monitoring of the user in the first monitoring event configuration.
The method according to claim 16, wherein the method further comprises:

Sending the context of the user to the fourth network element is used to instruct the fourth network element to cancel event monitoring of the user in the first monitoring event configuration.
An event subscription management method, characterized in that it comprises:

An instruction message is received, 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 deletion from the user group The user, or, is used to instruct to add the user to the user group;

If the instruction information is used to instruct to delete the user from the user group, cancel event monitoring of the user in the monitoring event configuration corresponding to the user group;

If the indication information is used to indicate that the user is added to the user group, start event monitoring of the user in the monitoring event configuration corresponding to the user group.
The method according to claim 18, wherein the instruction information is used to instruct to delete the user from the user group, and the method further comprises:

Updating the context of the user, and the updated context of the user indicates that the user does not belong to the user group;
The method according to claim 18, wherein the indication information is used to indicate to add the user to the user group, and the method further comprises:

The context of the user is updated, and the updated context of the user indicates that the user belongs to the user group.
A device, characterized in that it comprises:

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 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, the The indication information is used to instruct to cancel the event monitoring of the user in the first monitoring event configuration;

According to the instruction message, determine the information of the first monitoring event configuration, where the information of the first monitoring event configuration includes at least one of the following: group member information of the user group, and monitoring event report of the user Times information;

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 first monitoring event configuration. After an event monitoring report is completed, it is sent to the second network element.
22. The device according to claim 21, wherein 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 method according to claim 21, wherein the information of the first monitoring event configuration is used to indicate that the monitoring event report corresponding to the user has been completed.
The device according to any one of claims 21 to 23, wherein the group member information of the user group comprises:

The number of group members of the user group is the difference between the number of group members of the user group currently saved and the number of users; or,

The group member user of the user group deletes the user for the group member user of the currently saved user group.
The device according to claim 24, wherein when the program instructions are executed by the processor, the device executes the following steps:

Delete the saved monitoring event report times of the user.
The device according to any one of claims 21 to 25, wherein when the program instructions are executed by the processor, the device executes the following steps:

The number of monitoring event reports of the user is set to the maximum number of reports.
A device, characterized in that it comprises:

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:

Receive an instruction message, where the instruction message includes user group identification information, user identification information, and instruction information, where the user group identification information is used to indicate the user group to which the user belongs, and the instruction information is used to instruct the user Delete the user from the user group, or add the user 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, and monitoring event report of the user Times information;

Sending 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, and it is determined that the event monitoring report is completed Sent to the second network element backward.
The apparatus according to claim 27, wherein the indication information is used to indicate that the user is deleted from the user group, and the information of the monitoring event configuration indicates that the monitoring event configuration of the user group is calculated When reporting, the report of the monitoring event corresponding to the user is excluded.
The device according to claim 27 or 28, wherein the instruction information is used to instruct to delete the user from the user group, and the number of group members of the user group is that of the currently saved user group The difference between the number of group members and the number of users; or,

The group member user of the user group deletes the user for the group member user of the currently saved user group.
The device according to claim 29, wherein when the program instructions are executed by the processor, the device executes the following steps:

Delete the saved monitoring event report times of the said user
The device according to claim 27 or 28, wherein when the program instructions are executed by the processor, the device executes the following steps:

The user's monitoring event report times are identified as the maximum report times.
The device according to claim 27, wherein the indication information is used to add the user to the user group, and the information of the monitoring event configuration indicates the number of times of reporting a monitoring event corresponding to the user.
The device according to claim 27 or 32, wherein the instruction information is used to add the user to the user group, and the number of group members of the user group is the currently saved group of the user group The sum of the number of members and the number of said users;

or,

The member users of the user group add the users to the currently saved member users of the user group.
A device, characterized in that it comprises:

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 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, the The indication information is used to instruct to cancel the event monitoring of the user in the first monitoring event configuration;

According to the instruction message, cancel event monitoring of the user in the first monitoring event configuration.
The device according to claim 34, wherein the instruction message further includes an event monitoring type, and when the program instruction is executed by the processor, the device executes the following steps:

Cancel the event monitoring of the event monitoring type of the user in the first monitoring event configuration.
The device according to claim 35, wherein when the program instructions are executed by the processor, the device executes the following steps:

According to the instruction message, the context of the user is determined, and the context of the user instructs to cancel event monitoring of the user in the first monitoring event configuration.
The device according to claim 36, wherein when the program instructions are executed by the processor, the device executes the following steps:

Sending the context of the user to the fourth network element is used to instruct the fourth network element to cancel event monitoring of the user in the first monitoring event configuration.
A device, characterized in that it comprises:

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:

An instruction message is received, 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 deletion from the user group The user, or, is used to instruct to add the user to the user group;

If the instruction information is used to instruct to delete the user from the user group, cancel event monitoring of the user in the monitoring event configuration corresponding to the user group;

If the indication information is used to indicate that the user is added to the user group, start event monitoring of the user in the monitoring event configuration corresponding to the user group.
The device according to claim 38, wherein the instruction information is used to instruct to delete the user from the user group, and when the program instruction is executed by the processor, the device executes the following steps :

Updating the context of the user, and the updated context of the user indicates that the user does not belong to the user group;
The device according to claim 38, wherein the instruction information is used to instruct to add the user to the user group, and when the program instruction is executed by the processor, the device executes the following steps :

The context of the user is updated, and the updated context of the user indicates that the user belongs to the user group.
An event subscription management system, which is characterized by comprising an application server, a first network element, a second network element, and a third network element;

The application server is configured to send a first indication message to a first network element, where the first 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 for Indicating a first monitoring event configuration of a user group to which the user belongs, where the indication information is used to instruct to cancel event monitoring of the user in the first monitoring event configuration;

The first network element is configured to determine information about the first monitoring event configuration based on the first indication message, where the information about the first monitoring event configuration includes at least one of the following: Group member information, and information about the number of times that the user has reported monitoring events;

The first network element is configured to send a second indication message to the second network element, where the second indication message includes identification information of the monitoring event configuration, identification information of the user, and the indication information;

The second network element is configured to send the 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 configured to cancel event monitoring of the user in the first monitoring event configuration based on the second instruction message;

The first network element is further configured to send a delete message to a second network element, which is used to instruct the second network element to delete the first monitoring event configuration, wherein the delete message is based on the first monitoring event configuration. The event configuration information is sent to the second network element after the first event monitoring report is determined to be completed.
An event subscription management system, which is characterized by comprising an application server, a first network element, a second network element, and a third network element;

The application server is configured to send a first indication message to a first network element, where the first indication message includes identification information of a user group, identification information of a user, and indication information, and the identification information of the user group is used to indicate all The user group to which the user belongs, and the instruction information is used to instruct to delete the user from the user group, or to add the user to the user group;

The first network element is configured to determine the monitoring event configuration information corresponding to the user group according to the first indication message, wherein the monitoring event configuration information includes at least one of the following: Group member information, and information about the number of times that the user has reported monitoring events;

The first network element is configured to send a second indication message to the second network element, where the second indication message includes the identification information of the user group, the identification information of the user, and the indication information;

The second network element is configured to send the second indication message to the third network element, which is used to instruct the deletion of the user from the user group, or to indicate that the user is in the user group Add said users in;

The third network element is configured to, if the instruction information is used to instruct to delete the user from the user group, cancel event monitoring of the user in the monitoring event configuration corresponding to the user group; The instruction information is used to instruct to add the user to the user group and start event monitoring of the user in the monitoring event configuration corresponding to the user group;

The first network element is further configured to send a delete message to a second network element for instructing the second network element to delete the monitoring event configuration, wherein the delete message is information based on the monitoring event configuration , After determining that the event monitoring report is completed and sent to the second network element.
A computer program product containing instructions that, when run on a computer, causes the computer to execute the method according to any one of claims 1-6, or the method according to any one of claims 7-13, or The method according to any one of claims 14-17, or the method according to any one of claims 18-20.
A computer-readable storage medium, comprising instructions, which when run on a computer, cause the computer to execute the method according to any one of claims 1-6, or the method according to any one of claims 7-13 The method, or the method according to any one of claims 14-17, or the method according to any one of claims 18-20.