Event subscription notification method and device, communication equipment, storage medium and program product

Abstract

The invention discloses an event subscription notification method and device, communication equipment, a storage medium and a program product. The method comprises the following steps: a first network element receives a first subscription message sent by a second network element; the first subscription message carries a first event identifier; the first network element sends a second subscription message to N network elements; n is a positive integer, the second subscription message carries the first event identifier, and the N network elements are network elements supporting the first event notification; the first network element receives a second notification message sent by a part or all of the N network elements, wherein the second notification message carries event information related to the first event; the first network element sends a first notification message to the second network element; the first notification message carries the gathered event information.

Description

Technical Field

[0001] The present application relates to the field of core network technology, and in particular to an event subscription notification method and device, communication equipment, storage medium, and program product. Background Art

[0002] The 5G network architecture natively supports network capability exposure, which can open 5G network data and functions such as user status information, location information, Quality of Service (QoS) control capabilities, and session routing management capabilities to applications (including applications provided by operators and third-party applications), enabling applications to obtain network information and adjust network bearer resources according to business needs.

[0003] In some research works, the capability of opening event subscription and notification for IP Multimedia Subsystem (IMS) network is proposed, which allows third-party application platforms to subscribe to events related to IMS sessions and IMS data channels (IMSDC) to IMS networks (such as IMS network elements), including event subscription for specific users and event subscription for non-specific users. Event subscription for specific users refers to subscription to events related to a specific user or a group of specific users; event subscription for non-specific users refers to subscription to some business-related or statistics-related events. For event subscription for non-specific users, since the scope of subscription is not for specific users, the existing subscription notification mechanism is not applicable to this scenario. Summary of the invention

[0004] To solve the above technical problems, the present application provides an event subscription notification method and apparatus, communication equipment, computer storage medium, and computer program product.

[0005] The event subscription notification method provided by this application includes:

[0006] The first network element receives a first subscription message sent by the second network element; the first subscription message carries a first event identifier, and the first event identifier is used to identify a subscribed first event;

[0007] The first network element sends a second subscription message to N network elements; N is a positive integer, the second subscription message carries the first event identifier, and the N network elements are network elements that support notification of the first event;

[0008] The first network element receives a second notification message sent by some or all network elements of the N network elements, where the second notification message carries event information related to the first event;

[0009] The first network element sends a first notification message to the second network element; the first notification message carries aggregated event information, and the aggregated event information is obtained by aggregating event information of some or all of the network elements.

[0010] The event subscription notification method provided by this application includes:

[0011] The second network element sends a first subscription message to the first network element; the first subscription message carries a first event identifier, and the first event identifier is used to identify the subscribed first event;

[0012] The second network element receives a first notification message sent by the first network element; the first notification message carries aggregated event information, and the aggregated event information is obtained based on the event information of some or all of N network elements, and the N network elements are network elements that support the first event notification.

[0013] The event subscription notification method provided by this application includes:

[0014] The third network element receives a registration request message sent by the network element; the registration request message carries first capability information, and the first capability information is used to indicate that the network element supports subscription and notification capabilities of a first event.

[0015] The event subscription notification device provided in the present application is applied to a first network element, and the device includes:

[0016] A first receiving unit, configured to receive a first subscription message sent by a second network element; the first subscription message carries a first event identifier, and the first event identifier is used to identify a subscribed first event;

[0017] A first sending unit, configured to send a second subscription message to N network elements; N is a positive integer, the second subscription message carries the first event identifier, and the N network elements are network elements that support notification of the first event;

[0018] The first receiving unit is further configured to receive a second notification message sent by some or all of the N network elements, where the second notification message carries event information related to the first event;

[0019] The first sending unit is further used to send a first notification message to the second network element; the first notification message carries aggregated event information, and the aggregated event information is obtained by aggregating event information of some or all of the network elements.

[0020] The event subscription notification device provided by the present application is applied to a second network element, and the device includes:

[0021] A second sending unit is used to send a first subscription message to the first network element; the first subscription message carries a first event identifier, and the first event identifier is used to identify a subscribed first event;

[0022] The second receiving unit is used to receive a first notification message sent by the first network element; the first notification message carries aggregated event information, and the aggregated event information is obtained by aggregating event information of some or all of N network elements, and the N network elements are network elements that support the first event notification.

[0023] The event subscription notification device provided by the present application is applied to a third network element, and the device includes:

[0024] The third receiving unit is used to receive a registration request message sent by a network element; the registration request message carries first capability information, and the first capability information is used to indicate that the network element supports subscription and notification capabilities of a first event.

[0025] The communication device provided in the present application includes: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute any one of the above-mentioned event subscription notification methods.

[0026] The computer-readable storage medium provided in the present application is used to store a computer program, and the computer program enables a computer to execute any one of the above-mentioned event subscription notification methods.

[0027] The computer program product provided in the present application includes computer program instructions, which enable a computer to execute any one of the above-mentioned event subscription notification methods.

[0028] The technical solution of the present application proposes a new event subscription notification mechanism, through which event subscription that is not oriented to specific users can be realized, thus filling the technical gap for event subscription that is not oriented to specific users. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 This is a schematic diagram of the 5G network capability exposure architecture;

[0030] Figure 2 This is a flow diagram of the event subscription notification method provided in the embodiment of the present application. Figure 1 ;

[0031] Figure 3 This is a flow diagram of the event subscription notification method provided in the embodiment of the present application. Figure 2 ;

[0032] Figure 4 This is a flow diagram of the event subscription notification method provided in the embodiment of the present application. Figure 3 ;

[0033] Figure 5 It is a flow chart of application example 1 of this application;

[0034] Figure 6 It is a flow chart of the second application example of this application;

[0035] Figure 7 This is a schematic diagram of the structure of the event subscription notification device provided in the embodiment of the present application. Figure 1 ;

[0036] Figure 8 This is a schematic diagram of the structure of the event subscription notification device provided in the embodiment of the present application. Figure 2 ;

[0037] Fig. 9 This is a schematic diagram of the structure of the event subscription notification device provided in the embodiment of the present application. Figure 3 ;

[0038] Fig.10 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0039] Fig.11 It is a schematic structural diagram of the chip of an embodiment of the present application. DETAILED DESCRIPTION

[0040] It should be noted that the term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the objects associated with each other are in an "or" relationship. It should also be understood that the "indication" mentioned in this article can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B. It should also be understood that the "protocol" mentioned in this article can refer to a standard protocol in the field of communications, such as the NR protocol and related protocols used in future communication systems, and this application does not limit this.

[0041] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application.

[0042] 1. 5G network capability open architecture

[0043] Figure 1 Open architecture for 5G network capabilities, such as Figure 1 As shown in the figure, the 5G network capability exposure architecture includes the following network elements: application function (AF), network exposure function (NEF) and network function (NF).

[0044] AF is usually an application platform (i.e., external application), which provides business requirements and configuration information to the 5G network through NEF, and subscribes to the required information or event notifications from the 5G network. NF is a network element that provides services to external applications (i.e., AF). NEF is a core network element for capability exposure, which is used to isolate external applications (i.e., AF) and 5G networks, and provide secure isolation and adaptation for network capability exposure. In specific implementation, NEF can receive business requests from AF (such as service call requirements, data configuration requests, event subscription requests, etc.), and authenticate the requests. After the authentication is passed, the correct NF is selected to provide services to AF (such as event subscription services). NEF can convert and adapt the interaction information between AF and NF.

[0045] 2. Event subscription notification

[0046] An important aspect of 5G capability opening is the opening of event subscription notification capabilities. 5G networks can open user status information, location information, session status information, etc. in the network to applications through NEF, allowing applications to obtain the required event notifications from the 5G network through event subscription when conditions are met.

[0047] In the basic process of event subscription notification by application, AF calls the service provided by NEF for event subscription, and AF provides the required event ID list and associated user ID or user group ID in the event subscription request. NEF sends the event subscription request to the Unified Data Management (UDM), and UDM finds the 5G network element responsible for subsequent event notification (such as Access and Mobility Management Function (AMF), Session Management Function (SMF), etc.) for event subscription based on the event ID, user ID or user group ID. Subsequent event notifications can be sent directly from the 5G network element to NEF, and then forwarded by NEF to AF.

[0048] In some research works, the capability of opening event subscription and notification to the IMS network is proposed, allowing third-party application platforms to subscribe to events related to IMS sessions and IMSDC to the IMS network (such as IMS network elements), including event subscriptions for specific users and event subscriptions not for specific users. Event subscription for specific users refers to subscribing to events related to a specific user or a group of specific users; event subscription not for specific users refers to subscribing to some business-related or statistics-related events, such as the number of currently registered users, the number of users who dial a certain service number, the number of users currently using IMSDC and their status, etc. For event subscription not for specific users, since the scope of subscription is not for specific users, the existing subscription notification mechanism is not applicable to this scenario. To this end, the following technical solutions of the embodiments of the present application are proposed. The technical solution of the embodiments of the present application proposes an enhanced solution for event subscription notification not for specific users, so as to realize subscription to some business-related or statistics-related events.

[0049] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0050] It should be noted that the first event in the embodiment of the present application refers to an event that is not oriented to a specific user. An event that is not oriented to a specific user refers to an event that is related to a service or statistics, such as the number of currently registered users, the number of users who have dialed a certain service number, the number of users currently using IMSDCs, the number and status of currently established IMSDCs, etc.

[0051] It should be noted that the first network element in the embodiment of the present application refers to the execution network element of event subscription (specifically, the execution network element that is not for event subscription to a specific user), such as an application server (Application Server, AS), NEF, unified data management network element (Unified Data Management, UDM) / home subscription server (Home Subscriber Server, HSS), etc.

[0052] It should be noted that the second network element in the embodiment of the present application refers to the network element that initiates the event subscription request (or the requesting network element for event subscription), such as AS.

[0053] It should be noted that the third network element in the embodiment of the present application refers to a capability registration network element, such as UDM / HSS, network repository function (NRF), etc.

[0054] It should be noted that the N network elements in the embodiment of the present application refer to service providing network elements for event notification, such as an IMS application server (IMS AS), a data channel signaling function (DCSF), etc.

[0055] Figure 2 This is a flow diagram of the event subscription notification method provided in the embodiment of the present application. Figure 1 ,like Figure 2 The event subscription notification method comprises the following steps:

[0056] Step 201: A first network element receives a first subscription message sent by a second network element; the first subscription message carries a first event identifier, and the first event identifier is used to identify a subscribed first event.

[0057] In the embodiment of the present application, the first network element refers to the execution network element of the event subscription (specifically, the execution network element not for specific user event subscription), such as AS, NEF, UDM / HSS, etc. The second network element refers to the network element that initiates the event subscription request (or the requesting network element of the event subscription), such as AS, etc.

[0058] In the embodiment of the present application, the first subscription message may also be referred to as an event open subscription message, or as a subscription event request message, and the first subscription message is used to request a subscription event.

[0059] In the embodiment of the present application, the network element that initiates the subscription event request (i.e., the second network element) carries a first event identifier in the first subscription message, and the first event identifier is used to identify the subscribed first event. Here, the first event identifier refers to an event identifier that is not oriented to a specific user, and accordingly, the first event refers to an event that is not oriented to a specific user, and an event that is not oriented to a specific user refers to an event that is related to a business or statistics.

[0060] In some embodiments, the first event includes at least one of the following:

[0061] The number of users registered on the network element;

[0062] The number of users using a specific business number;

[0063] Number of users using IMSDC;

[0064] Number of IMSDCs established on the NE.

[0065] It should be noted that the first event identifier described in the implementation of this application may refer to one event identifier, or may refer to multiple event identifiers (i.e., an event identifier list). Similarly, the first event described in the implementation of this application may refer to one event, or may refer to multiple events.

[0066] Step 202: The first network element sends a second subscription message to N network elements; N is a positive integer, the second subscription message carries a first event identifier, and the N network elements are network elements that support first event notification.

[0067] In the embodiment of the present application, N network elements refer to service providing network elements for event notification (also referred to as service providing network elements for short), such as IMS AS, DCSF, etc. Here, N may be 1, or an integer greater than 1.

[0068] In the embodiment of the present application, when the first network element identifies, based on the first event identifier, that the subscribed first event is not an event for a specific user, the first network element queries the third network element for information on a list of network elements that support notification of the first event.

[0069] Here, the first network element identifies that the subscribed first event is not an event for a specific user based on the first event identifier carried in the first subscription message, or identifies that the first subscription message is a subscription request for an event that is not for a specific user, then the first network element queries the network element that supports the first event notification. Here, the network element that supports the first event notification can also be understood as a network element that can provide the first event notification service. In some embodiments, the first network element can query the network element that supports the first event notification in the following manner: the first network element queries the third network element for the list of network elements that support the first event notification; the network element list information includes the addresses of N network elements and / or the identifiers of N network elements. Based on this, the first network element sends a second subscription message to the N network elements based on the queried network element list information.

[0070] In the embodiment of the present application, the third network element refers to a capability registration network element, such as NRF, UDM / HSS, etc. As an implementation method, the first network element queries the NRF for the list of network elements that support the first event notification, and the NRF returns the addresses or identifiers of all network elements that support the first event notification to the first network element (i.e., the addresses of N network elements and / or the identifiers of N network elements). As another implementation method, the first network element queries the UDM / HSS for the list of network elements that support the first event notification, and the UDM / HSS returns the addresses or identifiers of all network elements that support the first event notification to the first network element (i.e., the addresses of N network elements and / or the identifiers of N network elements).

[0071] After querying N network elements that support the first event notification, the first network element sends a second subscription message to the N network elements. The second subscription message can also be called an event open subscription message, or a subscription event request message, and the second subscription message is used to request a subscription event. It should be noted that the difference between the second subscription message and the first subscription message is that the second subscription message is a subscription message sent by the first network element to the service providing network element, and the second subscription message is sent based on the service interface provided by the service providing network element, and the first subscription message is a subscription message sent by the second network element to the first network element, and the first subscription message is sent based on the service interface provided by the first network element.

[0072] In some implementations, after the first network element queries out the N network elements that support the first event notification, the first network element saves the association relationship between the first event and the N network elements. In this way, when the first network element queries for network elements that support the first event notification next time, it can directly obtain the N network elements that support the first event notification from the locally saved association relationship, without having to query the third network element for the network elements that support the first event notification again.

[0073] Step 203: The first network element receives a second notification message sent by some or all network elements among the N network elements, where the second notification message carries event information related to the first event.

[0074] In an embodiment of the present application, after the event notification service providing network element (i.e., the above-mentioned N network elements) receives the second subscription message (i.e., a subscription request not for a specific user event), it returns the corresponding second notification message to the first network element based on the current real-time status. The second notification message carries event information related to the first event (i.e., detailed information of the notification event), and optionally, also carries the first event identifier.

[0075] In some implementations, when or after the first network element sends the second subscription message to the N network elements, the first network element starts a first timer; if the first timer times out, the first network element aggregates event information of some or all of the N network elements to obtain aggregated event information. Here, the time information of all or some of the N network elements refers to all event information received by the first network element before the first timer times out.

[0076] In some embodiments, when or after the first network element sends a second subscription message to N network elements, the first network element starts a first timer; if before the first timer times out, the first network element receives event information from all network elements in the N network elements, then the first network element aggregates the event information from all network elements in the N network elements to obtain aggregated event information.

[0077] Step 204: the first network element sends a first notification message to the second network element; the first notification message carries the aggregated event information, and the aggregated event information is obtained by aggregating the event information of some or all network elements.

[0078] In an embodiment of the present application, after aggregating event information of some or all network elements in N network elements to obtain aggregated event information, the first network element sends a first notification message to the second network element. The first notification message carries the aggregated event information and, optionally, also carries a first event identifier.

[0079] It should be noted that the difference between the second notification message and the first notification message is that the second notification message is a notification message sent by the service providing network element to the first network element, and the second notification message is sent based on the service interface provided by the service providing network element, and the first notification message is a notification message sent by the first network element to the second network element, and the first notification message is sent based on the service interface provided by the first network element.

[0080] According to the technical solution of the embodiment of the present application, the network element that initiates the event subscription request carries the event identifier (i.e., the first event identifier) ​​that is not oriented to a specific user in the event subscription request (i.e., the first subscription message) when initiating the event subscription request. When the executing network element that does not subscribe to the event for a specific user receives the event subscription request, it identifies that the subscribed event is an event that is not oriented to a specific user based on the event identifier. Further, after the executing network element identifies that the subscribed event is an event that is not oriented to a specific user, it queries the capability registration network element for the service providing network element that currently supports all event notifications of the corresponding event that is not oriented to a specific user. Specifically, the executing network element carries the event identifier that is not oriented to a specific user in the query request, and the capability registration network element returns the address or identifier of all service providing network elements that support the event notification to the executing network element. Further, for each event that is not oriented to a specific user, the executing network element initiates an event subscription request to all service providing network elements that support the event notification, and carries the event identifier of the event in the request. When the executing network element initiates an event subscription request, it starts the timer; after receiving the subscription request for events not oriented to specific users, the service providing network element that does not provide event notifications for specific users returns the corresponding event notification to the executing network element according to the current real-time status, and the event notification carries the event identifier and notification event details. When the executing network element receives event notifications returned by all service providing network elements, or the timer times out, the executing network element aggregates the received event notifications, aggregates the notification event details in all event notifications received for the same event not oriented to specific users, and generates an event notification from the aggregated information, which carries the event identifier and aggregated notification event details, and returns it to the network element that initiated the subscription event notification.

[0081] Figure 3This is a flow diagram of the event subscription notification method provided in the embodiment of the present application. Figure 2 ,like Figure 3 The event subscription notification method comprises the following steps:

[0082] Step 301: The second network element sends a first subscription message to the first network element; the first subscription message carries a first event identifier, and the first event identifier is used to identify a subscribed first event.

[0083] In the embodiment of the present application, the first network element refers to the execution network element of the event subscription (specifically, the execution network element not for specific user event subscription), such as AS, NEF, UDM / HSS, etc. The second network element refers to the network element that initiates the event subscription request (or the requesting network element of the event subscription), such as AS, etc.

[0084] In the embodiment of the present application, the first subscription message may also be referred to as an event open subscription message, or as a subscription event request message, and the first subscription message is used to request a subscription event.

[0085] In the embodiment of the present application, the network element that initiates the subscription event request (i.e., the second network element) carries a first event identifier in the first subscription message, and the first event identifier is used to identify the subscribed first event. Here, the first event identifier refers to an event identifier that is not oriented to a specific user, and accordingly, the first event refers to an event that is not oriented to a specific user, and an event that is not oriented to a specific user refers to an event that is related to a business or statistics.

[0086] In some embodiments, the first event includes at least one of the following:

[0087] The number of users registered on the network element;

[0088] The number of users using a specific business number;

[0089] Number of users using IMSDC;

[0090] Number of IMSDCs established on the NE.

[0091] It should be noted that the first event identifier described in the implementation of this application may refer to one event identifier, or may refer to multiple event identifiers (i.e., an event identifier list). Similarly, the first event described in the implementation of this application may refer to one event, or may refer to multiple events.

[0092] Step 302: The second network element receives a first notification message sent by the first network element; the first notification message carries aggregated event information, the aggregated event information is obtained by aggregating event information of some or all network elements, and the N network elements are network elements that support the first event notification.

[0093] In the embodiment of the present application, after the first network element receives the first subscription message sent by the second network element, the following is executed: Figure 2 Steps 202 and 203 shown are performed to obtain aggregated event information; the first network element sends a first notification message to the second network element, and accordingly, the second network element receives the first notification message sent by the first network element, the first notification message carries the aggregated event information, and optionally, also carries a first event identifier.

[0094] Figure 4 This is a flow diagram of the event subscription notification method provided in the embodiment of the present application. Figure 3 ,like Figure 4 The event subscription notification method comprises the following steps:

[0095] Step 401: The third network element receives a registration request message sent by a network element; the registration request message carries first capability information, and the first capability information is used to indicate that the network element supports subscription and notification capabilities of a first event.

[0096] In the embodiment of the present application, the network element refers to a service providing network element for event notification (also referred to as a service providing network element), such as IMS AS, DCSF, etc. The third network element refers to a capability registration network element, such as NRF, UDM / HSS, etc.

[0097] In the embodiment of the present application, the first event refers to an event that is not oriented to a specific user, and the event that is not oriented to a specific user refers to an event that is related to business or statistics.

[0098] In some embodiments, the first event includes at least one of the following:

[0099] The number of users registered on the network element;

[0100] The number of users using a specific business number;

[0101] Number of users using IMSDC;

[0102] Number of IMSDCs established on the NE.

[0103] In the embodiment of the present application, the network element registers its own event subscription and notification capabilities (ie, the first capability) to the third network element, so that the third network element can subsequently provide the first network element with a network element query service that supports the first event notification.

[0104] In some implementations, the first capability information is used to indicate at least one of the following:

[0105] The NE supports reporting the number of users registered on the NE;

[0106] Service numbers supported by the network element;

[0107] The network element supports reporting the number of users using a specific service number;

[0108] The network element supports reporting the number of users using IMSDC;

[0109] The NE supports reporting the number of IMSDCs established on the NE.

[0110] The technical solution of the embodiment of the present application proposes a solution for network element event subscription and notification capability registration. The event notification service providing network element registers its supported event subscription and notification capabilities that are not for specific users with the capability registration network element.

[0111] The technical solution of the embodiment of the present application is illustrated below with reference to specific application examples.

[0112] Application Example 1

[0113] This application example is an event subscription and notification capability registration process. In this application example, the service providing network element is IMS AS / DCSF as an example, and the third network element is NRF or UDM / HSS as an example for description.

[0114] like Figure 5 As shown, the process includes the following steps:

[0115] Step A1: The IMS AS / DCSF sends an NRF registration request to the NRF. The NRF registration request carries the event subscription and notification capabilities of the IMS AS / DCSF that are not oriented to specific users.

[0116] Step A2: The NRF sends an NRF registration response to the IMS AS / DCSF.

[0117] Step B1: The IMS AS / DCSF sends a NF registration request to the UDM / HSS. The NF registration request carries the event subscription and notification capabilities of the IMS AS / DCSF that are not oriented to a specific user.

[0118] Step B2: UDM / HSS sends NF Registration Response to NRF.

[0119] Through the above steps A1 to A2, the IMS AS / DCSF registers its event subscription and notification capabilities that are not oriented to specific users with the NRF, and the IMS AS / DCSF carries the event identifiers that are not oriented to specific users that it supports in the registration request. For example, the IMS AS registers the service numbers that it supports with the NRF, and the DCSF registers the number of DCSFs that it supports with the NRF.

[0120] Through the above steps B1 to B2, IMS AS / DCSF registers its own NF address with UDM / HSS, and also registers its event subscription and notification capabilities that are not oriented to specific users. IMS AS / DCSF carries the event identifiers that are not oriented to specific users that it supports in the registration request. For example, IMS AS registers the service numbers that it supports with UDM / HSS, and DCSF registers the number of DCSFs that it supports with UDM / HSS.

[0121] It should be noted that the relationship between the above-mentioned steps A1 to A2 and steps B1 to B2 is a parallel relationship. In this application example, only the above-mentioned steps A1 to A2 may be executed, or only the above-mentioned steps B1 to B2 may be executed, or the above-mentioned steps A1 to A2 and steps B1 to B2 may be executed simultaneously.

[0122] Application Example 2

[0123] This application example is an event subscription and notification process. In this application example, three service providing network elements (DCSF, IMS AS1, and IMS AS2) are used as examples. The third network element is NRF or UDM / HSS, the second network element is AS, and the first network element is NEF. Figure 6 As shown, the process includes the following steps:

[0124] Step 601: AS sends an Nnef_EventExposure_Subscribe message to NEF, where the message carries an event identifier that is not intended for a specific user.

[0125] Here, the Nnef_EventExposure_Subscribe message corresponds to the first subscription message described above. The AS calls the Nnef_EventExposure_Subscribe service to subscribe to events that are not oriented to a specific user, and carries the event identifier to be subscribed in the Nnef_EventExposure_Subscribe message.

[0126] Step 602: NEF identifies, based on the event identifier, that the subscribed event is not an event for a specific user.

[0127] Step 603a: NEF sends a Nnrf_NFDiscovery message to NRF, which carries an event identifier not intended for a specific user, to query the NF address / identifier related to the event notification not intended for a specific user. NRF sends a Nnrf_NFDiscovery_response message to NEF, which carries an event identifier not intended for a specific user and a NF address / identifier list.

[0128] Here, the NRF carries all NF addresses / identities related to non-user-specific event notifications in the Nnrf_NFDiscovery_response message and sends it to the NEF.

[0129] Step 603b: NEF sends an NF query request message to UDM / HSS, which carries an event identifier that is not intended for a specific user, to query the NF address / identifier related to the event notification that is not intended for a specific user. UDM / HSS sends an NF query request response message to NEF, which carries the event identifier that is not intended for a specific user and a NF address / identifier list.

[0130] Here, the UDM / HSS carries all NF addresses / identities related to event notifications not oriented to specific users in the NF query request response message and sends it to the NEF.

[0131] It should be noted that the above step 603a and step 603b may be performed either alone or both.

[0132] Step 604a: NEF sends an Ndcsf_EventExposure_Subscribe message to DCSF, where the message carries an event identifier that is not intended for a specific user.

[0133] Here, the Ndcsf_EventExposure_Subscribe message corresponds to the second subscription message described above.

[0134] Step 604b: NEF sends a Nimsas_EventExposure_Subscribe message to IMS AS1, where the message carries an event identifier that is not intended for a specific user.

[0135] Here, the Nimsas_EventExposure_Subscribe message corresponds to the second subscription message described above.

[0136] Step 604c: NEF sends a Nimsas_EventExposure_Subscribe message to IMS AS2, where the message carries an event identifier that is not intended for a specific user.

[0137] Here, the Nimsas_EventExposure_Subscribe message corresponds to the second subscription message described above.

[0138] In the above steps 604a-604c, the NEF sends corresponding event subscription requests (ie, second subscription messages) to all NFs (ie, DCSF, IMS AS1, IMS AS2) according to the received NF address / identity list.

[0139] Step 605: NEF starts the timer.

[0140] Step 606: NEF sends a Nnef_EventExposure_Subscribe response message to AS.

[0141] Step 607a: DCSF sends an Ndcsf_EventExposure_Notify message to NEF, which carries the event information of DCSF.

[0142] Step 607b: IMS AS1 sends a Nimsas_EventExposure_Notify message to NEF, which carries the event information of IMS AS1.

[0143] Step 607c: IMS AS2 sends a Nimsas_EventExposure_Notify message to NEF, which carries the event information of IMS AS2.

[0144] Step 608: The NEF determines that the timer has timed out.

[0145] Step 609: NEF summarizes the received multiple event information.

[0146] Step 610: NEF sends an Nnef_EventExposure_Notify message to AS, which carries the aggregated event information.

[0147] Figure 7 This is a schematic diagram of the structure of the event subscription notification device provided in the embodiment of the present application. Figure 1 , applied to the first network element, such as Figure 7 As shown, the event subscription notification device includes:

[0148] The first receiving unit 701 is used to receive a first subscription message sent by a second network element; the first subscription message carries a first event identifier, the first event identifier is used to identify a first event subscribed to, and the first event is not an event for a specific user;

[0149] The first sending unit 702 is configured to send a second subscription message to N network elements; N is a positive integer, the second subscription message carries the first event identifier, and the N network elements are network elements that support notification of the first event;

[0150] The first receiving unit 701 is further configured to receive a second notification message sent by some or all of the N network elements, where the second notification message carries event information related to the first event;

[0151] The first sending unit 702 is further used to send a first notification message to the second network element; the first notification message carries aggregated event information, and the aggregated event information is obtained by aggregating event information of some or all network elements.

[0152] In some implementations, the apparatus further includes: a query unit, configured to query a third network element for network element list information supporting the first event notification; the network element list information includes addresses of the N network elements and / or identifiers of the N network elements;

[0153] The first sending unit 702 is configured to enable the first network element to send a second subscription message to the N network elements according to the network element list information.

[0154] In some implementations, when the first network element identifies, based on the first event identifier, that the subscribed first event is not an event for a specific user, the query unit queries a third network element for information on a list of network elements that support notification of the first event.

[0155] In some embodiments, the device also includes: a processing unit, configured to start a first timer when or after sending a second subscription message; if the first timer times out, aggregating event information of all or part of the network elements to obtain the aggregated event information.

[0156] In some embodiments, the first event includes at least one of the following:

[0157] The number of users registered on the network element;

[0158] The number of users using a specific business number;

[0159] Number of users using IMSDC;

[0160] Number of IMSDCs established on the NE.

[0161] In some implementations, the device further includes: a storage unit, configured to store an association relationship between the first event and the N network elements.

[0162] Those skilled in the art should understand that Figure 7 The implementation functions of each unit in the event subscription notification device shown can be understood by referring to the relevant description of the aforementioned method. Figure 7 The functions of each unit in the event subscription notification device shown can be implemented by a program running on a processor, or by a specific logic circuit.

[0163] Figure 8 This is a schematic diagram of the structure of the event subscription notification device provided in the embodiment of the present application. Figure 2, applied to the second network element, such as Figure 8 As shown, the event subscription notification device includes:

[0164] The second sending unit 801 is used to send a first subscription message to the first network element; the first subscription message carries a first event identifier, the first event identifier is used to identify a first event subscribed to, and the first event is not an event for a specific user;

[0165] The second receiving unit 802 is used to receive a first notification message sent by the first network element; the first notification message carries aggregated event information, and the aggregated event information is obtained based on aggregating event information of some or all of N network elements, and the N network elements are network elements that support the first event notification.

[0166] In some embodiments, the first event includes at least one of the following:

[0167] The number of users registered on the network element;

[0168] The number of users using a specific business number;

[0169] Number of users using IMSDC;

[0170] Number of IMSDCs established on the NE.

[0171] Those skilled in the art should understand that Figure 8 The implementation functions of each unit in the event subscription notification device shown can be understood by referring to the relevant description of the aforementioned method. Figure 8 The functions of each unit in the event subscription notification device shown can be implemented by a program running on a processor, or by a specific logic circuit.

[0172] Fig. 9 This is a schematic diagram of the structure of the event subscription notification device provided in the embodiment of the present application. Figure 3 , applied to the third network element, such as Fig. 9 As shown, the event subscription notification device includes:

[0173] The third receiving unit 901 is used to receive a registration request message sent by a network element; the registration request message carries first capability information, and the first capability information is used to indicate that the network element supports subscription and notification capabilities of a first event.

[0174] In some embodiments, the first event includes at least one of the following:

[0175] The number of users registered on the network element;

[0176] The number of users using a specific business number;

[0177] Number of users using IMSDC;

[0178] Number of IMSDCs established on the NE.

[0179] In some implementations, the first capability information is used to indicate at least one of the following:

[0180] The network element supports reporting the number of users registered on the network element;

[0181] The service number supported by the network element;

[0182] The network element supports reporting the number of users using a specific service number;

[0183] The network element supports reporting the number of users using IMSDC;

[0184] The network element supports reporting the number of IMSDCs established on the network element.

[0185] Those skilled in the art should understand that Fig. 9 The implementation functions of each unit in the event subscription notification device shown can be understood by referring to the relevant description of the aforementioned method. Fig. 9 The functions of each unit in the event subscription notification device shown can be implemented by a program running on a processor, or by a specific logic circuit.

[0186] Fig.10 It is a schematic structural diagram of a communication device 1000 provided in an embodiment of the present application. Fig.10 The communication device 1000 shown includes a processor 1010, and the processor 1010 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0187] Alternatively, if Fig.10 As shown, the communication device 1000 may further include a memory 1020. The processor 1010 may call and run a computer program from the memory 1020 to implement the method in the embodiment of the present application.

[0188] The memory 1020 may be a separate device independent of the processor 1010 , or may be integrated into the processor 1010 .

[0189] Alternatively, if Fig.10 As shown, the communication device 1000 may further include a transceiver 1030, and the processor 1010 may control the transceiver 1030 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

[0190] The transceiver 1030 may include a transmitter and a receiver. The transceiver 1030 may further include an antenna, and the number of antennas may be one or more.

[0191] Optionally, the communication device 1000 may specifically be the first network element of the embodiment of the present application, and the communication device 1000 may implement the corresponding processes implemented by the first network element in each method of the embodiment of the present application, which will not be described again for the sake of brevity.

[0192] Optionally, the communication device 1000 may specifically be the second network element of the embodiment of the present application, and the communication device 1000 may implement the corresponding processes implemented by the second network element in each method of the embodiment of the present application, which will not be described again for the sake of brevity.

[0193] Optionally, the communication device 1000 may specifically be a third network element of an embodiment of the present application, and the communication device 1000 may implement the corresponding processes implemented by the third network element in each method of the embodiment of the present application, which will not be described again for the sake of brevity.

[0194] Fig.11 It is a schematic structural diagram of the chip of an embodiment of the present application. Fig.11 The chip 1100 shown includes a processor 1110, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0195] Alternatively, if Fig.11 As shown, the chip 1100 may further include a memory 1120. The processor 1110 may call and run a computer program from the memory 1120 to implement the method in the embodiment of the present application.

[0196] The memory 1120 may be a separate device independent of the processor 1110 , or may be integrated into the processor 1110 .

[0197] Optionally, the chip 1100 may further include an input interface 1130. The processor 1110 may control the input interface 1130 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0198] Optionally, the chip 1100 may further include an output interface 1140. The processor 1110 may control the output interface 1140 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0199] Optionally, the chip can be applied to the first network element in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the first network element in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0200] Optionally, the chip can be applied to the second network element in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the second network element in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0201] Optionally, the chip can be applied to the third network element in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the third network element in the various methods of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0202] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0203] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0204] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0205] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

[0206] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0207] Optionally, the computer-readable storage medium can be applied to the first network element in the embodiment of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the first network element in the various methods of the embodiment of the present application. For the sake of brevity, they are not repeated here.

[0208] Optionally, the computer-readable storage medium can be applied to the second network element in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the second network element in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0209] Optionally, the computer-readable storage medium can be applied to the third network element in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the third network element in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0210] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0211] Optionally, the computer program product can be applied to the first network element in the embodiment of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the first network element in the various methods of the embodiment of the present application. For the sake of brevity, they are not repeated here.

[0212] Optionally, the computer program product can be applied to the second network element in the embodiment of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the second network element in the various methods of the embodiment of the present application. For the sake of brevity, they are not repeated here.

[0213] Optionally, the computer program product can be applied to the third network element in the embodiment of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the third network element in the various methods of the embodiment of the present application. For the sake of brevity, they are not repeated here.

[0214] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0215] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0216] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0217] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0218] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0219] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0220] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. An event subscription notification method, characterized in that: The method comprises: The first network element receives a first subscription message sent by the second network element; the first subscription message carries a first event identifier, and the first event identifier is used to identify a subscribed first event; The first network element sends a second subscription message to N network elements; N is a positive integer, the second subscription message carries the first event identifier, and the N network elements are network elements that support notification of the first event; The first network element receives a second notification message sent by some or all network elements of the N network elements, where the second notification message carries event information related to the first event; The first network element sends a first notification message to the second network element; the first notification message carries aggregated event information, and the aggregated event information is obtained by aggregating event information of some or all of the network elements.

2. The method according to claim 1, characterized in that The method further comprises: The first network element queries the third network element for network element list information supporting the first event notification; the network element list information includes addresses of the N network elements and / or identifiers of the N network elements; The first network element sends a second subscription message to N network elements, including: The first network element sends a second subscription message to the N network elements according to the network element list information.

3. The method according to claim 1, characterized in that: The first network element queries the third network element for network element list information that supports the first event notification, including: When the first network element identifies, according to the first event identifier, that the subscribed first event is not an event for a specific user, the first network element queries a third network element for information on a list of network elements that support notification of the first event.

4. The method according to any one of claims 1 to 3, characterized in that When or after the first network element sends the second subscription message to the N network elements, the method further includes: The first network element starts a first timer; If the first timer times out, the first network element aggregates the event information of all or part of the network elements to obtain the aggregated event information.

5. The method according to any one of claims 1 to 3, characterized in that The first event includes at least one of the following: The number of users registered on the network element; The number of users using a specific business number; The number of users using the IP Multimedia Subsystem Data Channel IMSDC; Number of IMSDCs established on the NE.

6. The method according to any one of claims 1 to 3, characterized in that The method further comprises: The first network element stores the association relationship between the first event and the N network elements.

7. An event subscription notification method, characterized in that: The method comprises: The second network element sends a first subscription message to the first network element; the first subscription message carries a first event identifier, and the first event identifier is used to identify the subscribed first event; The second network element receives a first notification message sent by the first network element; the first notification message carries aggregated event information, and the aggregated event information is obtained based on the event information of some or all of the N network elements, and the N network elements are network elements that support the first event notification.

8. The method according to claim 7, characterized in that The first event includes at least one of the following: The number of users registered on the network element; The number of users using a specific business number; Number of users using IMSDC; Number of IMSDCs established on the NE.

9. An event subscription notification method, characterized in that: The method comprises: The third network element receives a registration request message sent by the network element; the registration request message carries first capability information, and the first capability information is used to indicate that the network element supports subscription and notification capabilities of a first event.

10. The method according to claim 9, characterized in that The first event includes at least one of the following: The number of users registered on the network element; The number of users using a specific business number; Number of users using IMSDC; Number of IMSDCs established on the NE.

11. The method according to claim 9, characterized in that The first capability information is used to indicate at least one of the following: The network element supports reporting the number of users registered on the network element; The service number supported by the network element; The network element supports reporting the number of users using a specific service number; The network element supports reporting the number of users using IMSDC; The network element supports reporting the number of IMSDCs established on the network element.

12. An event subscription notification device, characterized in that: Applied to a first network element, the device includes: A first receiving unit, configured to receive a first subscription message sent by a second network element; the first subscription message carries a first event identifier, the first event identifier is used to identify a first event subscribed to, and the first event is not an event for a specific user; A first sending unit, configured to send a second subscription message to N network elements; N is a positive integer, the second subscription message carries the first event identifier, and the N network elements are network elements that support notification of the first event; The first receiving unit is further configured to receive a second notification message sent by some or all of the N network elements, where the second notification message carries event information related to the first event; The first sending unit is further used to send a first notification message to the second network element; the first notification message carries aggregated event information, and the aggregated event information is obtained by aggregating event information of some or all of the network elements.

13. An event subscription notification device, characterized in that: Applied to a second network element, the device comprises: A second sending unit is used to send a first subscription message to the first network element; the first subscription message carries a first event identifier, the first event identifier is used to identify a first event subscribed to, and the first event is not an event for a specific user; The second receiving unit is used to receive a first notification message sent by the first network element; the first notification message carries aggregated event information, and the aggregated event information is obtained by aggregating event information of some or all of N network elements, and the N network elements are network elements that support the first event notification.

14. An event subscription notification device, characterized in that: Applied to a third network element, the device includes: The third receiving unit is used to receive a registration request message sent by a network element; the registration request message carries first capability information, and the first capability information is used to indicate that the network element supports subscription and notification capabilities of a first event.

15. A communication device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 11.

16. A computer-readable storage medium, characterized in that: Used to store a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 11.

17. A computer program product, characterized in that The method comprises computer program instructions which cause a computer to execute the method as claimed in any one of claims 1 to 11.

Images