WO2020098622A1

WO2020098622A1 - Message notification method, apparatus, network element and system and storage medium

Info

Publication number: WO2020098622A1
Application number: PCT/CN2019/117385
Authority: WO
Inventors: 洪英杰
Original assignee: 中兴通讯股份有限公司
Priority date: 2018-10-10
Filing date: 2019-11-12
Publication date: 2020-05-22
Also published as: CN111031517A

Abstract

Provided in the embodiments of the present invention are a message notification method, apparatus, network element, system and a storage medium. The message notification method comprises: receiving a first request for subscribing to a user equipment (UE) availability after downlink data failure event, and generating a first subscription event of UE availability after downlink data failure according to the first request, wherein the first request comprises an application identifier of a third application (AF), an identifier NEF ID of a network exposure function (NEF) network element and an event reference identifier of the first subscription event, which are associated; and receiving a UE availability after downlink data failure notification of a target UE corresponding to the application identifier, and sending the UE availability after downlink data failure notification to the NEF network element according to the first subscription event.

Description

Message notification method, device, network element, system and storage medium

Technical field

The present disclosure relates to the field of communication technology.

Background technique

AF (Application Function) refers to a non-3GPP third-party application that sends data to the UE (User Equipment) for downlink data (DownLink data or DL data) transmission. For reasons such as power saving, the UE is not always connected. As for the state of the UE, AF does not know. Therefore, in order to effectively carry out DL data transmission, the following methods are generally used: Assume that all AF subscribes to UE availability after DDN failed event (also called UE reachable event or UE reachable state subscription event after downlink data failure, hereinafter collectively referred to as This is the UE reachable event after the downlink data fails); at a certain time, an AF sends downlink data, and the UPF (User Plane Function) user element will go to the AMF (Access Management Function) network after receiving it. Yuan sends a DDN (Downlink Data Notify) message to notify the AMF that the downlink data needs to wake the UE. If the AMF cannot wake the UE, it returns a DDN failure response; when the UE status changes from unreachable (unreachability) to reachable ( availability), the AMF will directly send a notification message of UE reachability to all AFs that have subscribed to a downlink data failure after a UE reachability event. However, not all AFs subscribed to the UE reachable status subscription event need to receive the notification message that the UE is reachable. For example, in an example case, only the AF that sends the downlink data service requirement needs to receive the notification message that the UE is reachable. Therefore, it is not necessary to send a notification message of UE reachability to all AFs that have subscribed to the UE reachability event after the downlink data fails, and it also wastes network resources.

Summary of the invention

An aspect of the present disclosure provides a message notification method, including: receiving a first request of a user equipment (UE) reachable event after a failure to subscribe to downlink data, and generating a first UE reachable after a downlink data failure according to the first request Subscription event, the first request includes the application identifier of the associated third-party application (AF), the NEF ID of the network open function (NEF) network element, and the event reference identifier of the first subscription event; After the downlink data of the target UE corresponding to the application identifier fails, the UE reachability notification is sent to the NEF network element according to the first subscription event, after the downlink data fails.

Another aspect of the present disclosure provides a message notification device, including: a third event subscription processing module, configured to receive a first request for a UE reachable event after a failure to subscribe for downlink data, and generate a downlink data according to the first request after a failure For the first subscription event reachable by the UE, the first request includes the associated AF application ID, NEF network element ID NEF ID, and the event reference ID of the first subscription event; the fifth notification sending module uses After receiving the downlink data failure of the target UE corresponding to the application identifier, the UE reachability notification is sent to the NEF network element according to the first subscription event, after the downlink data failure.

Another aspect of the present disclosure provides a message notification method, including: receiving a request sent by an AF for a UE reachable event after failing to subscribe to downlink data; sending a first UE reachable event after failing to subscribe to downlink data to an AMF network element Request, and send a second request to subscribe to the application data detection event to the session management function (SMF) network element; receive the application data detection notification sent by the SMF network element, and store the application identifier in the application data detection notification in the application In the identification list; the UE reachability notification after receiving the downlink data sent by the AMF network element fails; and sending the UE reachability notification after the downlink data failure to the AF corresponding to the application identification included in the application identification list.

Another aspect of the present disclosure provides a message notification method, including: receiving a second request for a subscription application data detection event sent by a NEF network element, and generating a second subscription event for application data detection according to the second request, the first The second request includes the application ID of the AF and the NEF ID of the NEF network element; requests the UPF network element to activate the application data detection of the AF corresponding to the application ID; receives the application data detection notification sent by the UPF network element, The application data detection notification includes the application identification of the AF that has detected the downlink data; the application data detection notification is sent to the NEF network element.

Another aspect of the present disclosure provides a message notification device, including: a second request receiving module for receiving a request sent by an AF for a UE reachable event after a failure to subscribe to downlink data; a second event subscription request module for According to the request, send a first request to the AMF network element after the UE fails to subscribe to the downlink data, and send a second request to the SMF network element to subscribe to the application data detection event; a second notification receiving module is used to receive the The application data detection notification sent by the SMF network element, storing the application identifier in the application data detection notification in the application identifier list; and the UE reachability notification after receiving the downlink data sent by the AMF network element fails; second The notification sending module is configured to send the UE reachable notification after the downlink data fails to be sent to the AF corresponding to the application identifier included in the application identifier list.

Another aspect of the present disclosure provides a message notification device, including: a fourth request receiving module, configured to receive a second request sent by a NEF network element to subscribe to an application data detection event, where the second request includes an AF application identification And the NEF ID of the NEF network element; a second event subscription processing module, configured to generate a second subscription event for application data detection according to the second request, and to request a UPF network element according to the second subscription event Activate application data detection of the AF corresponding to the application identifier; a fourth notification sending module, configured to receive an application data detection notification sent by the UPF network element, where the application data detection notification includes the detection that downlink data has been sent The AF application identifier sends the application data detection notification to the NEF network element.

Another aspect of the present disclosure provides a message notification method, including: receiving a request sent by an AF for a UE reachable event after a failure to subscribe to downlink data; sending a UE reachable after a failed subscription to a target network element according to the request The first request of the event, the first request includes the NEF ID of the NEF network element and the application ID of the AF; after receiving the downlink data sent by the target network element, the UE is reachable and the downlink data fails The post-UE reachability notification includes the application ID of the AF corresponding to the UE that has become unreachable; after sending the downlink data to the AF corresponding to the application ID included in the UE reachability notification after the downlink data fails, the UE may Notice.

Another aspect of the present disclosure provides a message notification device, including: a first request receiving module for receiving a request sent by an AF for a UE reachable event after failing to subscribe to downlink data; a first event subscription request module for Sending a first request to the target network element according to the request to the UE reachable event after subscribing to downlink data fails, the first request includes the NEF network element identifier NEF ID and the AF application identifier; the first notification receiving module , Used to receive the UE reachability notification after the downlink data sent by the target network element fails, and the UE reachability notification after the downlink data failure includes the application ID of the AF corresponding to the UE that becomes unreachable; first The notification sending module is configured to send the UE reachability notification after the downlink data failure to the AF corresponding to the application identifier included in the UE reachability notification after the downlink data failure.

Another aspect of the present disclosure provides an SMF network element, including a first processor, a first memory, and a first communication bus; the first communication bus is used to connect the first processor and the first memory; The first processor is used to execute the computer program stored in the first memory to implement the message notification method as described above.

Another aspect of the present disclosure provides an NEF network element, including a second processor, a second memory, and a second communication bus; the second communication bus is used to connect the second processor and the second memory; The second processor is used to execute the computer program stored in the second memory to implement the message notification method as described above.

Another aspect of the present disclosure provides a communication system, including a target network element and a NEF network element; the target network element is used to receive a first request for a UE reachable event after failing to subscribe to downlink data, and is generated according to the first request The first subscription event reachable by the UE after the downlink data fails, the first request includes the application ID of the AF, the NEF ID of the NEF network element, and the event reference identifier of the first subscription event. An event reference identifier association of the first subscription event; and for receiving a UE reachability notification after a downlink data failure of the target UE corresponding to the application identifier, according to the first subscription event, the UE may A notification is sent to the NEF network element; the NEF network element is used to send the UE reachability notification after the downlink data fails to the AF corresponding to the application identifier included in the UE reachability notification after the downlink data failure.

Another aspect of the present disclosure provides a computer-readable storage medium for storing one or more computer programs, the one or more computer programs can be executed by one or more processors, To realize the message notification method as described above.

BRIEF DESCRIPTION

FIG. 1 is a flowchart of a message notification method according to an embodiment of the present disclosure;

2 is a schematic diagram of a basic network architecture according to an embodiment of the present disclosure;

3 is a flowchart of a subscription event according to an embodiment of the present disclosure;

4 is a flowchart of a subscription event according to another embodiment of the present disclosure;

5 is a flowchart of notification of a UE reachability notification message according to an embodiment of the present disclosure;

6 is a schematic structural diagram of a message notification device according to an embodiment of the present disclosure;

7 is a flowchart of a message notification method on the NEF network element side according to an embodiment of the present disclosure;

8 is a flowchart of clearing application identification according to an embodiment of the present disclosure;

9 is a flowchart of an identification process according to an embodiment of the present disclosure;

10 is a schematic structural diagram of a message notification device on the NEF network element side according to an embodiment of the present disclosure;

11 is a flowchart of a message notification method on the AMF network element side according to an embodiment of the present disclosure;

12 is a flowchart of a third subscription event processing on the AMF network element side according to an embodiment of the present disclosure;

13 is a schematic structural diagram of a message notification device on an AMF network element side according to an embodiment of the present disclosure;

14 is a flowchart of a message notification method on the SMF network element side according to an embodiment of the present disclosure;

15 is a schematic structural diagram of a message notification device on an SMF network element side according to an embodiment of the present disclosure;

16 is a flowchart of a subscription event according to another embodiment of the present disclosure;

17 is a flowchart of a subscription event according to another embodiment of the present disclosure;

18 is a flowchart of notification of a UE reachability notification message according to another embodiment of the present disclosure;

19 is a flowchart of a message notification method on the NEF network element side according to another embodiment of the present disclosure;

20 is a flowchart of a message notification method on a target network element side according to an embodiment of the present disclosure;

21 is a schematic structural diagram of a message notification device according to another embodiment of the present disclosure;

22 is a schematic structural diagram of an SMF network element according to an embodiment of the present disclosure;

23 is a schematic structural diagram of a NEF network element according to an embodiment of the present disclosure;

24 is a schematic structural diagram of an AMF network element according to an embodiment of the present disclosure.

detailed description

In order to make the objectives, technical solutions and advantages of the present invention clearer, the embodiments of the present invention will be further described in detail below through specific implementations in conjunction with the accompanying drawings. It should be understood that the specific embodiments described herein are only used to explain the present invention, and are not intended to limit the present invention.

FIG. 1 is a flowchart of a message notification method according to an embodiment of the present disclosure. Through the message notification method according to the embodiment of the present disclosure, after the target network element fails to generate downlink data according to the first request, the UE (User Equipment) can reach the first subscription event of the UE (User Equipment) after the DDN fails. The first subscription event and the application identifier (that is, Application ID) of the AF (Application, Function, non-3GPP third-party application) in the first request, and it should be understood that the application identifier in this embodiment may be a unique identifier / Any information identifying the AF) association; when the target network element detects that the target UE corresponding to the AF subscribed to the first subscription event changes from unreachable to reachable, the UE reaches a notification after the downlink data sent fails (i.e. A notification message for UE reachability) includes the application identifier of the AF; in this way, the NEF (Network Exposure) function can be based on the application identifier in the UE reachability notification after the failure of the downlink data. The AF corresponding to the application identifier sends a notification message that the UE is reachable; improves the rationality of sending notification messages that the UE is reachable and network resource utilization.

According to an embodiment of the present disclosure, taking the target network element as an SMF (Session Management Function) session element as an example, a method for notification according to a message is provided. After the SMF network element fails to generate downlink data according to the first request, the UE may The first subscription event reached, the first request includes the associated AF application identifier, NEF network element identifier NEF ID and event reference identifier of the first subscription event, the generated first subscription event can be associated with the event reference identifier Association; in this way, when SMF subsequently receives the UE reachability notification after receiving the downlink data failure, it can send the UE reachability notification (ie, a UE reachability notification message) after the downlink data fails according to the first subscription event generated before The NEF network element corresponding to the NEF ID is sent to the AF corresponding to the Application ID (the Application ID included in the UE reachability notification after the downlink data failure) through the NEF network element, which can improve the UE reachability notification sent after the downlink data failure. Targeted to improve network resource utilization.

The message notification method according to an embodiment of the present disclosure includes the first subscription event generation process and the notification process of the UE reachability notification after the downlink data fails. Referring to FIG. 1, the message notification method according to the embodiment of the present disclosure includes steps S101 and S102.

In step S101, receive a first request for a UE reachable event after failing to subscribe to downlink data, and generate a first subscription event for the UE reachable after failed downlink data according to the first request. The first request includes an AF application identifier and an NEF network element The NEF ID and the event reference identifier of the first subscription event. The first subscription event may be associated with the event reference identifier.

According to an embodiment of the present disclosure, the first request includes the event reference identifier of the first subscription event that is related to each other, the application ID of the third-party application AF, and the NEF ID of the network open function NEF network element. The target UE corresponding to the medium AF, that is, the target receiving object of the downlink data delivered by the AF. The first subscription event generated in S101 is associated with the event reference identifier of the first subscription event in the first request. According to an embodiment of the present disclosure, S101 may be performed by an SMF network element.

According to an embodiment of the present disclosure, the NEF network element may trigger the first request for the UE reachable event after the failure to generate the downlink data to the session management function SMF network element according to the request of the third-party application AF for the SMF network element to generate The first subscription event that monitors the reachability of the UE. According to an embodiment of the present disclosure, the event reference identifier of the first subscription event included in the first request may be generated by the NEF network element.

According to an embodiment of the present disclosure, the request of the AF may include, but is not limited to: an event open subscription request from the AF, for example, including but not limited to Event Exposure_Subscribe request.

According to an embodiment of the present disclosure, the first request may include but is not limited to at least one of the following requests: an event open subscription request from a UDM (Unified Data Management) network element, such as, but not limited to, Event Exposure_Subscribe request ; Session policy control update notification request from PCF (Policy Control Function) policy element, including but not limited to SM Policy_Control_Update Notify request.

In step S102: receiving the UE reachability notification after the downlink data of the target UE corresponding to the application identifier fails, and according to the first subscription event, send the UE reachability notification after the downlink data fails to the NEF network element.

According to an embodiment of the present disclosure, during the generation of the first subscription event by the SMF network element, the UPF (User Plane Function) user element can also be configured to perform AF packet detection, that is, send a message to the UPF network element, activate and Application data detection function corresponding to the above Application ID. The SMF network element can send the PFD (Packet Flow Description) corresponding to the Application ID to the UPF network element; according to the embodiment of the present disclosure, the SMF network element can also send the Application ID to the UPF. At this time, the UPF The network element can perform packet inspection based on the locally configured PFD corresponding to the Application ID.

According to an embodiment of the present disclosure, the SMF network element may control whether the first subscription event needs to report the downlink data after the failure of reporting the downlink data through the first notification identifier. Therefore, when the SMF network element generates the first subscription event, it may also: Generate a first notification identifier, such as, but not limited to, a notification flag, and set the generated first notification identifier to be associated with the event reference identifier of the first subscription event in the first request. According to an embodiment of the present disclosure, when the value of the first notification identifier is set as the first preset value, it may be characterized that the first subscription event associated with the event reference identifier of the first subscription event associated with the first notification identifier needs to be reported After the downlink data fails, the UE can reach the notification; when the value of the first notification identifier is not the first preset value, it can characterize the first subscription event associated with the event reference identifier of the first subscription event associated with the first notification identifier There is no need for UE reachability notification after failure to report downlink data. And it should be understood that the specific value of the first preset value in this embodiment can be flexibly set, for example, can be set to "1" or "Yes", or can be set to other values, as long as it can characterize the first The first subscription event associated with the notification identifier and the first subscription event associated with the event reference identifier need to report that the UE is reachable after the downlink data fails to be reported.

According to an embodiment of the present disclosure, during the process of generating the first subscription event, the SMF network element may not set the value for the generated first notification identifier temporarily, or directly set the default value as the first preset value. It can also be set flexibly according to specific application scenarios.

According to an embodiment of the present disclosure, the SMF network element may set the value of the first notification identifier in but not limited to the following example manner. For example, before the SMF network element receives the reachability notification, the SMF network element receives the application data detection notification including the corresponding Application ID sent by the UPF network element, and determines that the target UE to be delivered by the AF corresponding to the Application ID is currently unavailable When it arrives, the notification flag corresponding to the Application ID can be set as the first preset value. The application data detection notification in this embodiment includes but is not limited to at least one of the N4 Report message and the Data Notification message. In addition, the N4Report message and the Data Notification message in this embodiment may be sent to the SMF network element through but not limited to the UPF network element.

Therefore, according to an embodiment of the present disclosure, before sending the UE reachability notification to the NEF network element corresponding to the NEF ID after the downlink data fails in S102, the method may further include: determining a first notification identifier (the first notification identifier is the same as S102 Whether the first notification identifier corresponding to the event reference identifier of the first subscription event associated with the NEF in the ID) is currently the first preset value, and if so, the UE reachability notification will be sent to the NEF ID after the downlink data fails NEF network element for the NEF network element to send to the AF corresponding to the Application ID according to the association relationship between the Application ID and the event reference identifier of the first subscription event.

According to an embodiment of the present disclosure, the SMF network element obtains the downlink reachability notification after the failure of the downlink data by requesting to subscribe to the UE reachability event (AMF (Access Management Function)) access to the UE, and the AMF network element receives the SMF After the first subscription event requested by the network element, a notification flag is set to control whether the UE reachability notification needs to be sent to the SMF network element. For example, when the AMF network element pages the UE according to the request of the SMF network element, it may set a second notification flag associated with the SMF network element, including but not limited to UE Availability, Notify, SMF flag, and setting the second notification When the value of the flag is the first preset value, it indicates that the associated SMF needs to be reported, that is, when the state of the target UE changes from unreachable unreachability to reachable availability, the associated SMF network element needs to be notified. Therefore, according to an embodiment of the present disclosure, after the downlink data in S102 fails, the UE reachability notification changes from the unreachable unreachability to the availability of the target UE when the AMF network element detects the target UE, and the second associated with the SMF network element When the current value of the notification identifier is the first preset value, the AMF sends it to the SMF. The second notification identifier UE is set after the AMF network element detects that the status of the target UE is unreachable and reaches the SMF event subscription message. For example, an example of a setting process may include, but is not limited to: when the SMF network element receives the application data detection notification including the Application ID from the UPF network element, and the SMF network element learns that the user is currently unreachable, the setting with the Application ID The corresponding first notification identifier is the first preset value; when the SMF network element learns that the user is currently unreachable, if the AMF network element has not subscribed to the user reachability status notification, the SMF network element subscribes to the AMF network element for the UE reachability status Notification event; when the AMF network element receives the subscription UE reachable status notification request from the SMF network element, the value of the second notification identifier associated with the above SMF network element is set as the first preset value to characterize the AMF network element When detecting that the state of the target UE changes from unreachable to reachable, a message notification needs to be sent to the SMF network element.

It can be seen that through the message notification method according to the embodiment of the present disclosure, the UE reachability notification after the downlink data fails can be sent only to the AF that sent the downlink data service demand, rather than to all the first users who have subscribed to the UE reachability AF for subscribing to events improves the pertinence and intelligence of UE reachability notification after downlink data failure, and improves network resource utilization.

2 is a schematic diagram of a basic network architecture according to an embodiment of the present disclosure.

For ease of understanding, a specific network architecture diagram application scenario is used as an example for description.

In order to maintain the competitiveness of the third-generation mobile communication system in the field of communication, provide users with faster speed, lower latency, and more personalized mobile communication services, and at the same time, reduce the operating costs of operators, 3GPP (3rd Generation Partnership) Project , The Third Generation Partnership Project) Standards Working Group is dedicated to the research of next-generation wireless mobile access networks. In the next-generation wireless access network, it supports multiple wireless networks to access a unified core network, and it is hoped that the wireless access network (Radio Access Network, RAN) and core network (Core Network, CN) will minimize the coupling relationship, that is, regardless of The terminal can access the unified CN through any RAN access technology. In order to support more flexible deployment methods and service-based interfaces, the core network functions of the next-generation network include an example of the basic network architecture shown in Figure 2. The main NFs (Network) include but are not limited to the following : AMF network element, which belongs to the public control plane function in the core network and terminates NAS messages between all users and the network. A UE can have only one AMF network element, responsible for user mobility management, UE status (such as reachability) management, etc .; SMF network element, responsible for but not limited to session establishment, modification, deletion, control PCF network element charging and policy execution PCF network element, responsible for but not limited to formulating strategies for the terminal based on the user's subscription, UE's current location, application-related information, including routing strategy, quality of service strategy, charging strategy, etc .; UDM network element, with unified data Management function, which can be used for but not limited to the permanent storage of user contract data and other functions; UDR (Unified Data Repository, unified data storage) network element can be used for but not limited to storing user contract data and policies managed by UDM network elements and PCF network elements Data, etc .; UPF network element, which belongs to the function of the user plane in the core network, is the anchor point of the user plane of the core network, is the interface with the external network (DN, Data) Network data transmission, and executes the execution of PCF policy rules in the user plane. ; NEF network element (not shown in the figure), used to expose the capabilities and events of 3GPP NFs to other NF or third-party application AF, provide AF pre-configured 3GPP NFs capabilities, and realize the mapping of 3GPP network and external network information. In this example, AF refers to a third-party application other than 3GPP; DN (Data) Network refers to a non-3GPP external network; 5G-AN (Access Network) refers to a 5G access network.

For ease of understanding, on the basis of this embodiment, based on the application scenario of the basic network architecture shown in FIG. 2, a method of performing a first subscription event on an SMF network element and formulating a UPF network element for AF application packet detection is performed. Example description.

FIG. 3 is a flowchart of a subscription event according to an embodiment of the present disclosure. Referring to FIG. 3, the subscription event includes steps S301 to S307.

In S301, each AF can subscribe to the notification event (that is, subscribe to the UE's availability after DDN failed event) through the NEF network element. For example, the AF can send a Nnef_Event Exposure_Subscribe request to subscribe to the availability of the target UE corresponding to the AF. Exposure_Subscribe request may include instructions for subscribing to the Availability after DDN failure event, and the Application ID including the AF. The Nnef_Event Exposure_Subscribe request also includes a target UE identifier, which may indicate a single user or a group of users. The target UE identity may optionally also include an IP address.

After receiving the Nnef_Event Exposure_Subscribe request, the NEF network element may generate the event reference identifier NEF_reference_ID1 of the first subscription event. The event reference identifier of the first subscription event is associated with the Application ID in the Nnef_Event Exposure_Subscribe request.

In S302, the NEF network element generates a first subscription event on the UDM network element according to the target UE identifier; for example, the NEF network element may send a Nudm_Event Exposure_Subscribe request (that is, a first request) to the UDM network element, and the Nudm_Event Exposure_Subscribe request may include a subscription Availability indication of DDN failure event, AF Application ID, NEF_reference_ID1, and optionally, NEF ID of NEF network element.

In S303, the UDM network element finds the user-related context according to the target UE ID, selects the appropriate SMF network element within the user context, and then goes to the SMF network element to subscribe to the UE's availability after DDN failed event. For example, the UDM network element may send a Nsmf_Event Exposure_Subscribe request to the SMF network element. The Nudm_Event Exposure_Subscribe request may include an instruction to subscribe to the Availability after DDN failure event, Application ID, NEF ID, NEF_reference_ID1.

The SMF network element generates a first subscription event that monitors the reachability of the UE, and optionally can set whether to send a notification flag to start monitoring the first notification, (if the notification flag is "no", the downlink data of the first subscription event After the failure, the UE reachability notification is not sent. If the notification flag is "Yes" (that is, the first preset value), the UE reachability notification is sent after the downlink data of the first subscription event fails.

At S304, the SMF network element configures the UPF network element to perform AF packet inspection.

The SMF network element activates the application package detection for the Application ID on the UPF network element according to the subscription request (ie, the second request) of the UDM network element. For example, the SMF network element can send an N4 Session / Establishment / Modification Request (Application ID, PFD) to the UPF network element. In the N4Session Establishment / Modification Request, the SMF network element can describe the PFD (Packet Flow) Description corresponding to the Application ID in the packet flow description. ) Delivered to the UPF network element. The SMF network element can also deliver the Application ID to the UPF network element. At this time, the UPF network element performs packet inspection according to the locally configured PFD corresponding to the Application ID.

In S305, the SMF network element sends a response message to the UDM network element, for example, Nsmf_EventExposure_Subscribe responses.

At S306, the UDM network element sends a response message to the NEF network element, such as Nudm_EventExposure_Subscribe responses.

In S307, the NEF network element sends a response message to the AF, such as Nnef_EventExposure_Subscribe responses.

According to an embodiment of the present disclosure, steps S306 and S307 may also be performed before step S303.

In the manner shown in FIG. 3, the first subscription event can be generated on the SMF network element and the UPF can be configured to perform AF application packet detection.

Based on the application scenario of the basic network architecture shown in FIG. 2, the following uses an example of a first subscription event on an SMF network element and a method of formulating a UPF for AF application packet detection.

FIG. 4 is a flowchart of a subscription event according to another embodiment of the present disclosure. Referring to FIG. 4, the subscription event includes steps S401 to S407.

At S401, each AF can subscribe to the notification event (that is, subscribe to the UE's availability after DDN failed event) through the NEF network element. For example, the AF can send a Nnef_Event Exposure_Subscribe request to subscribe to the availability of the target UE corresponding to the AF DDN failure event, the Nnef_Event Exposure_Subscribe request may include instructions for subscribing to the Availability after DDN failure event, and the Application ID including the AF.

In S402, the NEF network element finds the corresponding PCF network element according to the target UE identifier and other information, and the PCF network element generates the relevant first subscription event; for example, the NEF network element may send Npcf_PolicyAuthorization_Create (that is, an example of the first Request), the Npcf_PolicyAuthorization_Create may include an indication to subscribe to the Availability after DDN failure event, AF ’s Application ID, NEF_reference_ID1, and according to an embodiment of the present disclosure, it may also include the NEF ID of the NEF network element.

At S403, the PCF network element finds the context and related session related to the user according to the target UE identifier and other information, and then subscribes to the Availability DDN failure event (ie, UE validity monitoring event) on the SMF network element of the session. For example, the PCF network element may send Npcf_SMPolicyControl_UpdateNotify to the SMF network element, and the Npcf_SMPolicyControl_UpdateNotify may include an instruction to subscribe to the Availability after DDN failure event, Application ID, NEF ID, NEF_reference_ID1.

At S404, the SMF network element configures the UPF network element to perform AF packet inspection.

The SMF network element activates the application package detection for the Application ID on the UPF network element according to the subscription request of the UDM network element. For example, the SMF network element can send an N4SessionEstablishment / ModificationRequest (ApplicationID, PFD) to the UPF network element. In the N4SessionEstablishment / ModificationRequest, the SMF network element can associate the PFD (PacketFlowDescription, packet flow description) corresponding to the ApplicationID Delivered to the UPF network element. The SMF network element can also deliver the Application ID to the UPF network element. At this time, the UPF network element performs packet inspection according to the locally configured PFD corresponding to the Application ID.

At S405, the SMF network element sends a response message to the PCF network element, for example, Npcf_SMPolicyControl_UpdateNotify.

At S406, the PCF network element sends a response message to the NEF network element, such as Nudm_EventExposure_Subscribe responses.

At S407, the NEF network element sends a response message to the AF, for example, Npcf_PolicyAuthorization_Create response.

According to an embodiment of the present disclosure, steps S406 and S407 may also be performed before step S403.

The first subscription event can be generated on the SMF network element and the UPF can be configured to detect AF application data packets in the manner shown in FIG. 4.

Based on the above embodiments, a process of providing a method in which a UPF network element detects that an AF application data packet delivers a notification to an SMF network element, and the SMF network element reports a UE availability notification message to the AF is performed as an example. Instructions.

FIG. 5 is a flowchart of notification of a UE reachability notification message according to an embodiment of the present disclosure. Referring to FIG. 5, the notification of the UE reachability notification message includes steps S501 to S508.

In S501, the AF sends downlink data, and the UE in FIG. 5 is the target UE corresponding to the AF.

At S502, the UPF network element sends a downlink data notification Downlink Data Notification to the SMF network element. According to an embodiment of the present disclosure, Downlink Data Notification can carry but is not limited to QoS flow, ARP (Allocation and Retention Priority, allocation and retention priority), etc. At least one of the information. At the same time, the UPF network element detects that the AF is sending downlink data according to the data packet, so it sends an N4Report message to the SMF network element to report the detected Application ID (of course, in one example, the UPF network element can directly pass the Data Notification Report the detected Application ID to the SMF network element). After the SMF network element receives the N4Report message or the Data Notification message, if the SMF network element already knows that the target UE corresponding to the AF corresponding to the Application ID is unreachable, the SMF network element sets the notification flag of the AF to yes, The notification flag and NEF_reference_ID1 are associated. If the SMF network element already knows that the target UE corresponding to the AF corresponding to the Application ID is in a reachable state, the notification flag of the AF may be set to No; according to the embodiment of the present disclosure, the Application ID may also be cleared.

At S503, if the SMF network element does not know that the user is in an unreachable state, the SMF network element requests the AMF network element to instruct the AMF network element to page the target UE (see, for example, S5031 in FIG. 5, at this time DDN failure).

At S504, the AMF network element determines that the paging target UE has no response or fails, and the AMF network element sends a DDN failure response to the SMF network element.

At S505, the SMF network element learns that the user is currently unreachable, sends a message to the AMF network element, requests to subscribe to the user reachability notification, and after receiving the AMF network element, sets a second notification identifier UEAvailability associated with the SMF network element in S503 The value of Notify SMF flag is "Yes", which is used to indicate that the SMF network element needs to be notified when the status of the target UE becomes available. According to the embodiment of the present disclosure, the subscription request can also be carried in step S503, so that the SMF network element does not need to resend the subscription message to the AMF network element.

In S506, in S5061, the AMF network element detects that the target UE state becomes available, and the AMF network element sends a UE status reachable notification message to the SMF network element according to the second notification flag UE Availability Availability SMF flag set in S505.

At S507, the SMF network element determines the AF to be notified according to the first notification flag notification flag, and sends the UE status reachable notification message to the corresponding NEF ID according to the event reference identifiers NEF_Reference_ID1, NEFID of the first subscription event NEF network element; for example, in one example, the SMF network element may be implemented by sending Nsmf_EventExposure_Notify to the NEF network element.

At S508, the NEF network element notifies the AF corresponding to the Application ID that the UE is reachable after the received downlink data fails. For example, in one example, the NEF network element may be implemented by sending Nnef_EventExposure_Notify to the AF.

6 is a schematic structural diagram of a message notification device according to an embodiment of the present disclosure. The message notification device may be installed in an SMF network element.

As shown in FIG. 6, the message notification device includes a third event subscription processing module 601 and a fifth notification sending module 602.

The third event subscription processing module 601 receives a first request for generating a first subscription event that monitors the reachability status of the target UE, and generates a first subscription event that monitors the reachability status of the target UE, that is, a UE that subscribes to the target UE after DDN failed event.

According to an embodiment of the present disclosure, the first request includes the event reference identifier of the first subscription event associated with each other, the application ID of the third-party application AF, and the NEF identifier NEF of the NEF network element, and the third event subscription processing module 601 generates The first subscription event of is associated with the event reference identifier of the first subscription event in the first request.

According to an embodiment of the present disclosure, the NEF network element may trigger the first request to generate the first subscription event for monitoring the reachability status of the UE to the SMF network element according to the second request of the third-party application AF for the SMF network element Generate a first subscription event that monitors the reachability of the UE. According to an embodiment of the present disclosure, the event reference identifier of the first subscription event included in the first request may be generated by the NEF network element.

For example, according to an embodiment of the present disclosure, the second request may include, but is not limited to, an event open subscription request from AF, such as, but not limited to, Event Exposure_Subscribe request.

According to an embodiment of the present disclosure, the first request received by the third event subscription processing module 601 includes at least one of the following requests: event open subscription requests from UDM network elements, such as but not limited to Event Exposure_Subscribe request; from the PCF network Meta session policy control update notification request, for example, including but not limited to SMPolicyControl_UpdateNotifyrequest.

The fifth notification sending module 602 is used to receive the UE reachability notification after the downlink data of the target UE fails, and according to the first subscription event generated by the third event subscription processing module 601, send the UE reachability notification after the downlink data fails to the UE The NEF network element corresponding to the NEF ID associated with the first subscription event is for the NEF network element to send to the AF corresponding to the Application ID according to the association relationship between the Application ID and the event reference identifier of the first subscription event.

According to an embodiment of the present disclosure, during the process of generating the first subscription event by the third event subscription processing module 601, the UPF network element may also be configured to perform data packet detection, that is, the application packet detection for the Application ID is activated on the UPF network element. The third event subscription processing module 601 can deliver the PFD (Packet Flow Description) corresponding to the Application ID to the UPF network element; according to an embodiment of the present disclosure, the third event subscription processing module 601 can also send the Application ID It is delivered to the UPF network element. At this time, the UPF network element can perform packet inspection based on the locally configured PFD corresponding to the Application ID.

In an example in this embodiment, the third event subscription processing module 601 can control whether the first subscription event needs to report the downlink data after the failure of reporting the downlink data through the first notification identifier. Therefore, according to the implementation of the present disclosure For example, when the third event subscription processing module 601 generates a first subscription event that monitors the reachability of the UE, it further includes: generating a first notification identifier, such as notification flag, and setting the generated first notification identifier and the first request in the first request An event reference identifier association for a subscribed event. According to an embodiment of the present disclosure, when the value of the first notification identifier is set as the first preset value, it may be characterized that the first subscription event associated with the event reference identifier of the first subscription event associated with the first notification identifier needs to be reported After the downlink data fails, the UE can reach the notification; when the value of the first notification identifier is not the first preset value, it can characterize the first subscription event associated with the event reference identifier of the first subscription event associated with the first notification identifier There is no need for UE reachability notification after failure to report downlink data.

According to an embodiment of the present disclosure, during the process of generating the first subscription event, the third event subscription processing module 601 may not temporarily set the value for the generated first notification identifier, or directly set the default to the first preset value. It can also be set flexibly according to specific application scenarios.

According to an embodiment of the present disclosure, the third event subscription processing module 601 may set the value of notification flag in but not limited to the following example manner. For example, before the third event subscription processing module 601 receives the reachable notification, the third event subscription processing module 601 receives the application data detection notification including the corresponding Application ID sent by the UPF network element, and determines the AF corresponding to the Application ID When the target UE to be delivered is currently unreachable, the first notification identifier corresponding to the Application ID may be set as a first preset value. The downlink application data detection notification in this embodiment includes but is not limited to at least one of the N4Report message and the Data Notification message.

Therefore, according to an embodiment of the present disclosure, the fifth notification sending module 602 can also be used to determine whether the first notification identifier is currently the first before the UE reachable notification after the downlink data fails is sent to the NEF network element corresponding to the NEF ID The preset value, if so, only sends the UE reachable notification after the failure of the downlink data to the NEF network element corresponding to the NEF ID for the association relationship between the NEF network element according to the Application ID and the event reference identifier of the first subscription event, Send to AF corresponding to Application ID.

According to an embodiment of the present disclosure, the AMF network element may also control whether it is necessary to send a reachable notification to the third event subscription processing module 601 by setting a notification identifier. For example, when the AMF network element pages the UE according to the request of the SMF network element, if the user is unreachable and a subscription request for the user reachability notification of the SMF network element is received, a second associated with the SMF network element may be set The notification flag UEAvailabilityNotifySMFflag, and the value of the UEAvailabilityNotifySMFflag can also be set as the first preset value, indicating that it needs to be reported to the associated SMF network element, which indicates that when the state of the target UE changes from unreachable unreachability To reach availability, the associated SMF network element needs to be notified. Therefore, according to an embodiment of the present disclosure, the reachability notification received by the fifth notification sending module 602 can be changed from unreachable unreachability to reachable availability when the AMF network element detects the target UE, and the second notification identifier ( For example, when the current value of UE Availability (Notify SMF) is the first preset value, the AMF network element sends it to the SMF network element. The second notification identifier UE, Availability, Notify, SMF, flag is set after the AMF network element detects that the status of the target UE is unreachable and receives the event subscription message of the SMF network element.

The functions of the third event subscription processing module 601 and the fifth notification sending module 602 can be implemented by, but not limited to, the processor or controller of the SMF network element. With the message notification device provided in this embodiment, the UE can send downlink data after failure The reach notification is only sent to the AF that sent the downlink data service requirement, not to the AF that subscribes to the first subscription event of the UE reachability state, which improves the targeted and intelligent sending of the UE reachability notification after the downlink data fails , And improved network resource utilization.

7 is a flowchart of a message notification method on the NEF network element side according to an embodiment of the present disclosure.

As shown in FIG. 7, the message notification method on the NEF network element side may include but not limited to steps S701 to S705.

In S701, receiving a request sent by the AF for a UE reachable event (ie, UE availability after DDN failure) after a failure to subscribe to downlink data. The request may include a target UE ID and an application ID Application ID.

According to an embodiment of the present disclosure, the AF may also send a request for a UE reachable event after failing to subscribe to downlink data through various interaction messages with the NEF network element.

In S702, according to the received request, the first request for the UE reachable event is sent to the AMF network element after subscribing to the downlink data fails, and the second request for the subscription application data detection event (that is, the downlink data packet detection event) is sent to the SMF network element request.

According to an embodiment of the present disclosure, the execution order of the first request sent by the NEF network element to the AMF network element and the second request sent to the SMF network element is not strictly limited, and the two can be executed in parallel, or the first request can be sent to the AMF network element first. After a request, send a second request to the SMF network element; or send a second request to the SMF network element first, and then send the first request to the AMF network element.

According to an embodiment of the present disclosure, the first request may include, but is not limited to, the application identification of the AF and the NEF ID of the NEF network element, and their functions are as shown above and will not be repeated here. The second request may also include the AF application ID and the NEF network element ID NEF ID, so that the second subscription event detected by the SMF network element according to the application data generated by the second request can be related to the AF application ID and NEF network element Identify the NEF ID association, so that the SMF network element can instruct the UPF network element to activate the application data detection (ie, downlink data packet detection) of the AF corresponding to the corresponding application identifier according to the second subscription event; and upon receiving the detection sent by the UPF When a certain AF sends a notification of downlink data, the corresponding second subscription event is determined according to the application identifier in the notification and the above-mentioned association relationship, and from the determined second subscription event and the above-mentioned association relationship to the corresponding NEF ID The corresponding NEF network element sends an application data detection notification, and may include the corresponding application identifier in the sent application data detection notification.

According to an embodiment of the present disclosure, the first request for the UE reachable event after failure to send the downlink data subscription to the AMF network element may include, but is not limited to: sending the first request to the AMF network element through the event open subscription request of the UDM network element.

According to an embodiment of the present disclosure, sending the second request for subscription application data detection to the SMF network element may include but is not limited to at least one of the following ways: sending the first request to the SMF network element through the event open subscription request of the UDM network element Send a first request to the SMF network element through the PCF network element's session policy control update notification request.

At S703, receiving the application data detection notification sent by the SMF network element, and storing the application identifier in the application data detection notification in the application identifier list.

It should be understood that this embodiment is not limited to storing / caching the application identification in the application data detection notification (that is, the application identification of each AF that has sent the downlink data) through the application identification list. In addition, in this embodiment, the application identification list may use various lists that can be used to store identification information.

At S704, the UE reachable notification after receiving the downlink data sent by the AMF network element fails.

As shown above, the UE reachability notification after the failure of the downlink data may include the application identification of the AF corresponding to the UE that becomes unreachable and becomes reachable.

And it should be understood that the execution order of S703 and S704 in this embodiment is not strictly time-limited; and the two may be executed in parallel or non-parallel.

In S705, the UE reaches the notification after the downlink data fails to be sent to the AF corresponding to the application identifier included in the application identifier list.

The UE reachability notification after failure to send downlink data to the AF corresponding to the application identifier included in the application identifier list includes, but is not limited to, one of the following: Direct failure to send downlink data to the AF corresponding to the application identifier included in the application identifier list After the UE reachability notification, according to an embodiment of the present disclosure, the application identification list can be cleared after sending; the UE after sending the downlink data fails to send to the AF corresponding to the application identification included in the UE reachability notification after the downlink data failure in the application identification list Reachable notification; for example, when the application identifier is extracted from the UE reachable notification after the received downlink data fails, and then the application identifier that is the same as the application identifier is selected from the application identifier list, it is sent to the AF corresponding to the application identifier After the downlink data fails, the UE can be notified.

According to an embodiment of the present disclosure, for an AF that has sent downlink data, the corresponding target UE may itself be reachable when it sends downlink data. For such AF, the UE may not send downlink data to it. Notification; therefore, according to the embodiments of the present disclosure, in order to further improve the resource utilization and the accuracy of message notification control, for such AF, a clearing mechanism may be used to clear its application identifier from the above-mentioned application identifier list.

For example, for an exemplary manner, refer to FIG. 8, which is a flowchart of clearing an application identifier according to an embodiment of the present disclosure. After receiving the application data detection notification sent by the SMF network element, it may also include but not limited to steps S801 and S802.

At S801, a third request to subscribe to the UE reachable event is sent to the AMF network element.

The UE reachable event according to an embodiment of the present disclosure refers to one of two methods: Method 1: The UE detects whether it is currently reachable and does not care about its previous state. That is, before detecting whether the UE corresponding to the application identifier in the application data detection notification is reachable, the UE may be in a reachable state or may be in an unreachable state, and the detection may be initiated during the detection After that, the UE changes from unreachable to reachable; in either case, as long as the UE is detected as reachable, the UE reachability notification is fed back. Method 2: The UE detects whether the current state is reachable. If the current state of the UE is reachable, the UE is notified of the reachability notification; if the current state of the UE is unreachable, the UE is notified of the unreachability notification.

In this embodiment, sending the third request to subscribe to the UE reachable event to the AMF network element includes but is not limited to: sending the third request to the AMF network element through the event open subscription request of the UDM network element.

At S802, when receiving the UE reachability notification sent by the AMF network element, the application identifier included in the application identifier list is cleared.

According to an embodiment of the present disclosure, clearing the application identification list includes but is not limited to one of the following: clearing all application identifications in the application identification list; clearing the application identifications in the application list that are the same as the application identifications included in the UE reachability notification.

As shown above, the UE reachability notification sent by an AMF network element to a certain UE may be sent when the UE changes from unreachable to reachable, or it may be that the UE itself is in Sent when reachable (that is, no DDN failure event occurs). Therefore, in order to avoid erroneously clearing the AF corresponding to the UE from the unreachable state to the reachable state, this embodiment may also adopt an identification mechanism to avoid the above situation.

For example, a recognition process is shown in FIG. 9, which is a flowchart of the recognition process according to an embodiment of the present disclosure. After receiving the UE reachability notification sent by the AMF network element, before the application identifier included in the application identifier list is cleared, steps S901 and S902 may be further included.

At S901, the timer starts when the UE reachability notification is received.

According to an embodiment of the present disclosure, the NEF network element may set a timer through which time counting is performed.

In S902, when the timing value reaches the set time value, if the UE is not reachable after receiving the downlink data failure notification, the application identifier included in the application identifier list is cleared.

In this step, if the UE reachability notification is received after the failure of the downlink data, the UE reachability notification after the failure of the downlink data is sent to the AF corresponding to the application identifier included in the application identifier list.

The present disclosure also provides a message notification device that can be set in the NEF network element, and of course, can also be set in other network elements that can communicate with the AF. Each module included in the message notification device can be implemented but is not limited to the above method Corresponding functions in, and the functions of each module can be realized by but not limited to the processor or controller of the network element.

10 is a schematic structural diagram of a message notification device on a NEF network element side according to an embodiment of the present disclosure. As shown in FIG. 10, the message notification device includes, but is not limited to, a second request receiving module 1001, a second event subscription request module 1002, a second notification receiving module 1003, and a second notification sending module 1004.

The second request receiving module 1001 is configured to receive a request sent by the AF for a UE reachable event after subscribing to downlink data fails.

The second event subscription request module 1002 is used to send the first request for the UE reachable event to the AMF network element after the subscription downlink data fails according to the request received by the second request receiving module 1001, and send the subscription application data detection event to the SMF network element Second request.

The second notification receiving module 1003 is used to receive the application data detection notification sent by the SMF network element, store the application identifier in the application data detection notification in the application identifier list; and used to receive the downlink data sent by the AMF network element after failure UE reachable notification.

The second notification sending module 1004 is configured to send the UE reachable notification after the downlink data fails to the AF corresponding to the application identifier included in the application identifier list. According to the embodiment of the present disclosure, it may be further used to clear the application identifier list.

According to an embodiment of the present disclosure, the second event subscription request module 1002 may also be used to send a third request to subscribe to the UE reachable event to the AMF network element.

The second notification receiving module 1003 can also be used to clear the application identifier included in the application identifier list when receiving the UE reachable notification sent by the AMF network element.

According to an embodiment of the present disclosure, the second notification receiving module 1003 may also be used to, after receiving the UE reachability notification sent by the AMF network element, before clearing the application identifier contained in the application identifier list, since receiving the UE reachability notification start the timer. The second notification receiving module 1003 can also be used to clear the application identification included in the application identification list if the UE fails to receive the downlink data notification when the timing value reaches the set time value; if the downlink data is received After the failure, the UE reachability notification may be sent to the AF corresponding to the application identifier through the second notification sending module 1004 after the downlink data fails.

11 is a flowchart of a message notification method on the AMF network element side according to an embodiment of the present disclosure. Referring to FIG. 11, according to the message notification method according to an embodiment of the present disclosure, on the AMF network element side, steps S1101 and S1102 may be included, but not limited to.

At S1101, a first request sent by a NEF network element for a UE reachable event after a failure to subscribe to downlink data is received, and according to the first request, a first subscription event for a UE reachable after a downlink data failure is generated.

As shown above, the first request may include the application ID of the AF and the NEF ID of the NEF network element, and the first subscription event may be associated with the application ID of the AF in the first request and the NEF ID of the NEF network element; In an embodiment of the present disclosure, an associated event reference identifier of the first subscription event may also be generated for the first subscription event, so as to facilitate management of each first subscription event. For example, when a UE detects that it has changed from unreachable to reachable, the UE reachability notification may also include the event reference identifier of the corresponding first subscription event after the downlink data sent fails, so that the receiver can The event reference identifier of a subscription event identifies that the received notification is a notification corresponding to the corresponding first subscription event.

In S1102, according to the first subscription event, when it is detected that the target UE changes from unreachable to reachable, the UE reachable notification is sent to the NEF network element after the downlink data fails, and the UE reachable notification may include an application identifier after the downlink data fails .

That is, in this step, the AMF network element may, according to the first subscription event, when it detects that the target UE corresponding to the first subscription event changes from unreachable to reachable, notify the NEF ID corresponding to the first subscription event. After the corresponding NEF network element fails to send downlink data, the UE reachability notification may be included. After the sent downlink data fails, the UE reachability notification may include an application identification application identifier corresponding to the first subscription event.

12 is a flowchart of a third subscription event processing on the AMF network element side according to an embodiment of the present disclosure. As shown in FIG. 12, on the AMF network element side, the message notification method according to an embodiment of the present disclosure may further include but not limited to steps S1201 and S1202.

At S1201, a third request for subscription to a UE reachable event sent by an NEF network element is received, and a third subscription event for UE reachability is generated according to the third request, and the third request may include an application identifier in an application data detection notification.

In S1202, when it is detected that the target UE in the third request is reachable according to the third subscription event, a UE reachability notification is sent to the NEF network element.

As shown in the above analysis, in this step, the AMF network element detects that the UE is reachable. The UE may change from unreachable to reachable, or the UE may itself be reachable when the corresponding AF sends downlink data.

According to an embodiment of the present disclosure, an event reference identifier of an associated third subscription event may also be generated for the third subscription event, so as to facilitate management of each third subscription event. For example, when the AMF network element determines that a certain UE is reachable according to the third event, the sent UE reachability notification may include the event reference identifier of the corresponding third subscription event, so that the receiver can refer to the event reference of the third subscription event The identifier recognizes that the received notification is a notification corresponding to the corresponding third subscription event.

The present disclosure also provides a message notification device that can be set in an AMF network element. Of course, it can also be set in other network elements that can directly or indirectly detect the reachability state of the UE. The modules included in the message notification device can be implemented However, it is not limited to the corresponding function in the above method, and the function of each module may be implemented by, but not limited to, the processor or controller of the network element.

13 is a schematic structural diagram of a message notification device on an AMF network element side according to an embodiment of the present disclosure. As shown in FIG. 13, the message notification device includes but is not limited to a third request receiving module 1301, a first event subscription processing module 1302, and a third notification sending module 1303.

The third request receiving module 1301 is configured to receive a first request sent by a NEF network element for a UE reachable event after a failure to subscribe to downlink data. The first request includes an AF application identifier and the NEF network element identifier NEF ID.

The first event subscription processing module 1302 is configured to generate a first subscription event that is reachable by the UE after the downlink data fails according to the first request received by the third request receiving module 1301.

The third notification sending module 1303 is configured to send the UE reachable notification after the downlink data fails to the NEF network element after detecting that the UE corresponding to the application identifier changes from unreachable to reachable according to the first subscription event. The UE reachability notification includes the application identifier.

According to an embodiment of the present disclosure, the third request receiving module 1301 may also be used to receive a third request sent by the NEF network element to subscribe to the UE reachability event; the third request includes the application identifier in the application data detection notification.

The first event subscription processing module 1302 may also be used to generate a third subscription event reachable by the UE according to the third request.

The third notification sending module 1303 may be further configured to send a UE reachable notification to the NEF network element when detecting that the UE corresponding to the application identifier in the third request is reachable according to the third subscription event.

14 is a flowchart of a message notification method on the SMF network element side according to an embodiment of the present disclosure. Referring to FIG. 14, according to the message notification method according to an embodiment of the present disclosure, on the SMF network element side, steps S1401 to S1404 may be included, but not limited to.

At S1401, a second request for subscription to the application data detection event sent by the NEF network element is received, and a second subscription event for application data detection is generated according to the second request. The second request includes the AF application identification and the NEF network element identification NEF ID.

According to an embodiment of the present disclosure, an event reference identifier of an associated second subscription event may also be generated for the second subscription event, so as to facilitate management of each second subscription event. For example, when an AF detects that it has sent downlink data, the subsequent application data detection notification may include the event reference identifier of the corresponding second subscription event, so that the receiver can use the event reference identifier of the second subscription event It is recognized that the received notification is a notification corresponding to the corresponding second subscription event.

At S1402, the UPF network element is instructed to activate the application data detection of the AF corresponding to the application identifier according to the second subscription event. The UPF network element can perform application data detection on the corresponding AF according to the instruction, that is, downlink data packet detection.

At S1403, an application data detection notification sent by a UPF network element is received, and the application data detection notification includes an application identification of an AF that detects that downlink data has been sent.

In S1404, the received application data detection notification is sent to the NEF network element.

This embodiment also provides a message notification device that can be installed in an SMF network element. Of course, it can also be installed in other network elements that can directly detect or indirectly detect AF downlink data. Each module included in the message notification device can Realize but not limited to the corresponding function in the above method, and the function of each module can be realized by but not limited to the processor or controller of the network element.

15 is a schematic structural diagram of a message notification device on an SMF network element side according to an embodiment of the present disclosure. Referring to FIG. 15, the message notification device in this embodiment includes but is not limited to a fourth request receiving module 1501, a second event subscription processing module 1502, and a fourth notification sending module 1503.

The fourth request receiving module 1501 is configured to receive a second request sent by the NEF network element to subscribe to the application data detection event, where the second request includes the AF application identification and the NEF network element identification NEFID.

The second event subscription processing module 1502 is configured to generate a second subscription event for application data detection according to the second request, and to instruct the UPF network element to activate the application data detection corresponding to the AF corresponding to the application identifier according to the second subscription event.

The fourth notification sending module 1503 is configured to receive the application data detection notification sent by the UPF network element, and send the application data detection notification to the corresponding NEF network element (that is, the NEF network element corresponding to the application identifier in the notification), application data The detection notification includes the application identification of the AF that detected that the downlink data has been sent.

Based on the application scenario of the basic network architecture shown in FIG. 2, in this embodiment, a UE reachable event (that is, UE availability after DDN failed event) and an AF application to an SMF network element are activated after a failure to subscribe to downstream data on an AMF network element An example of the method of packet inspection.

FIG. 16 is a flowchart of a subscription event according to another embodiment of the present disclosure. Referring to FIG. 16, the subscription event includes steps S1601 to S1608.

At S1601, each AF can subscribe to the UE's availability by sending a request to NEF network elements (hereinafter referred to as an event subscription request). For example, the AF can send Nnef_EventExposure_Subscribe request to subscribe to the UE's UEAvailability after DDN failure event corresponding to the AF The Nnef_EventExposure_Subscribe request may include an indication of subscribing to the UE, Availability after DDN failure event, and an AF application identifier. According to an embodiment of the present disclosure, it may also include a target UE identifier corresponding to the AF. The target UE identifier may indicate a single user or a group of users. The target UE identity may optionally include an IP address. AF application identification refers to information that can be used to characterize the identity of AF, such as application identification Application ID, port information, IP address information, etc.

After receiving the Nnef_EventExposure_Subscribe request of each AF, the NEF network element can generate an event reference identifier NEF_reference_ID, which can be associated with the Application ID in the Nnef_EventExposure_Subscribe request.

In S1602, the NEF network element finds the UDM network element according to the target UE identifier in the event subscription request, and generates a subscription event to the UDM network element; for example, the NEF network element may send a Nudm_EventExposure_Subscribe request (that is, an example first request) to the UDM network element The Nudm_EventExposure_Subscribe request may include an instruction to subscribe to the Availability after DDN failure event, the Application ID of the AF, the NEF_reference_ID, and according to the embodiments of the present disclosure, the NEF ID of the NEF network element.

At S1603, the UDM network element to the AMF network element to subscribe UE availability event after DDN failure event, for example, the UDM network element may send a Namf_EventExposure_Subscribe request to the AMF network element (that is, an exemplary first request sending method), the request may include a subscription UE availability indication after DDN failure event, Application ID, NEF ID, NEF_reference_ID (that is, the event reference identifier of the first subscription event); the AMF network element can generate the first subscription event according to the Namf_EventExposure_Subscribe request.

In S1604, the UDM network element finds the user-related session context according to the target UE ID, finds the user-registered SMF (hSMF or home SMF in the home network roaming) network element in the user context, and then goes to the SMF network element Application data detection event subscription. For example, the UDM network element may send an Nsmf_EventExposure_Subscribe request (that is, an example second request) to the SMF network element. The Nsmf_EventExposure_Subscribe request may include an indication of a subscription application data detection event, Application ID, NEF ID, and NEF_reference_ID (that is, the second subscription event Event reference identifier), the SMF network element generates a second subscription event according to Nsmf_EventExposure_Subscribe request.

At S1605, the SMF network element configures the UPF (hUPF or home UPF in the home network roaming scenario) network element to perform AF packet detection corresponding to the Application ID.

The SMF network element activates the downlink packet detection for the Application ID on the UPF network element according to the Nsmf_EventExposure_Subscribe request of the UDM network element. For example, the SMF network element can send an N4 Session / Establishment / Modification Request (Application ID, PFD) to the UPF network element. In the N4Session Establishment / Modification Request, the SMF network element can describe the PFD (Packet Flow) Description corresponding to the Application ID in the packet flow description. ) Issued to UPF. The SMF network element can also deliver the Application ID to the UPF network element. At this time, the UPF network element performs packet inspection based on the locally configured PFD corresponding to the Application ID.

At S1606, the SMF network element sends a response message to the UDM network element, for example, Nsmf_EventExposure_Subscribe responses.

At S1607, the UDM network element sends a response message to the NEF network element, such as Nudm_EventExposure_Subscribe responses.

At S1608, the NEF network element sends a response message to the AF, for example, Nnef_EventExposure_Subscribe responses.

FIG. 17 is a flowchart of a subscription event according to another embodiment of the present disclosure. Referring to FIG. 17, a second subscription event detected by an application data packet generated at an SMF network element may also be implemented. The subscription event includes steps S1701 to S1704.

At S1701, each AF may subscribe to events by sending a request to NEF network elements (hereinafter referred to as an event subscription request). For example, the AF may send a Nnef_EventExposure_Subscribe request to subscribe to the application data detection event corresponding to the AF. The Nnef_EventExposure_Subscribe request may include the AF application Identify the Application ID and corresponding UE information (for example, including but not limited to the IP address of the UE).

At S1702, the NEF network element according to the IP address of the UE in the event subscription request, or DNN (Data, Network Name, Data Network Name) and S-NSSAI (subscribed-Network, Slice Selection, Assistance, Information for contracted network slice selection), If you can find the PCF network element of the PDU session related to the user UE, request an application data detection event subscription from the PCF network element. For example, the NEF network element can send a Npcf_PolicyAuthorization_Subscribe subscription request. The request message carries the event reference identifier, application identifier Application ID, NEF Network element identification.

If the NEF network element does not find the PCF network element of the user ’s UE-related session, the NEF saves the subscription event in the UDR (Unified Data Repository, unified data storage). When the user creates a PDU session, the PCF network element will then retrieve the UDR from the UDR Receive the subscription event.

At S1703, the PCF network element issues a policy control and charging rule (PCC rule) to the SMF network element, requesting to report an application data detection event, and the PCC rule contains the Application ID, event reference ID, and NEF network element ID to be detected. For example, the session policy control update notification request message Npcf_SMPolicyControl_UpdateNotify sends the PCC rule to the SMF network element.

At S1704, the SMF network element creates application data to detect a subscription event (that is, the second subscription event), and the event includes the event reference identifier of the second subscription event and the NEF network element identifier; at the same time, the SMF network element reports The UPF network element sends and executes the application data detection for the AF identified by the Application ID. For example, the SMF network element can send an N4 Session / Establishment / Modification Request (Application ID, PFD) to the UPF network element. In the N4 Session Establishment / Modification Request, the SMF network element can associate the PFD (Packet Flow Description) corresponding to the Application ID with the packet flow Description) issued to UPF. The SMF network element can also deliver the Application ID to the UPF. At this time, the UPF network element performs packet inspection according to the locally configured PFD corresponding to the Application ID.

For ease of understanding, this embodiment will be described below in conjunction with a notification flow schematic diagram of a UE reachability notification message.

FIG. 18 is a flowchart of notification of a UE reachability notification message according to another embodiment of the present disclosure. Referring to FIG. 18, the notification of the UE reachability notification message includes steps S1800 to S1817.

At S1800, according to the above configuration, the hUPF network element performs application data detection according to the PDF.

At S1801, the AF sends downlink data to the hUPF network element.

At S1802, the hUPF network element detects the downlink data sent by the AF identified by the Application ID, and sends an N4 report or Data Notification (Data Notification) message to notify the hSMF network element.

At S1803, the hSMF network element notifies the NEF network element (hereinafter referred to as NEF) according to the AF's second subscription event that it detects that the AF has sent data Nsmf_EventExposure_Notify (Application ID), and this message carries the application ID of the AF.

In S1804, the NEF network element saves the AF detected Application ID to Application ID list. If the NEF network element receives multiple Application IDs in the notification of the hSMF network element, it can be directly saved to the Application ID list. If the subsequent hSMF After the NE continues to report the detected Application ID, the NEF NE adds the subsequent Application ID to the aforementioned Application ID list.

In S1805, the NEF network element generates a new NEF_Reference_ID (that is, the event reference event identifier of the third subscription event), and sends a UE reachable monitoring subscription event request to the UDM network element (hereinafter referred to as UDM).

At S1806, if the UDM network element receives the NEF network element request message, it sends a request to the AMF network element to subscribe to the UE reachable status event Namf_EventExposure_subscribe (UE reachability status, NEF ID, NEF_Reference_ID), which is the third subscription event.

At S1807, the hUPF network element sends downlink data to the visiting UPF (vUPF or visit UPF) network element.

In S1808, the vUPF network element caches the downlink data, and sends a data notification Data to the visiting SMF (vSMF or visit SMF) network element, and then vSMF sends the data to the AMF network element.

At S1809, the AMF network element pages the target UE.

It should be understood that the above steps S1807 to S1809 can be performed in parallel with steps S1802 to S1806.

At S1810, if the AMF network element paging is successful or the AMF network element knows that the UE status is reachable, steps S1811 and S1812 are executed; otherwise, step S1813 is skipped.

At S1811, according to the third subscription event, the AMF network element sends a UE reachable notification message Namf_EventExposure_notify to the NEF network element.

At S1812, the NEF network element receives the UE reachable notification of the third subscription event, indicating that the user is currently reachable, and all downlink data can be sent to the UE without DDN Failure, so there is no need to notify AF, so the NEF network element Clear the Application ID list in S1804. (As shown in the above embodiments, for the NEF network element, when receiving the notification message of the third subscription event, NEF cannot determine whether it is the message received by S1812 or S1816, so when the NEF network element receives the third subscription The event message can be the same as S1816. Set a timer locally. Before the timer times out, if the first subscription event notification is not received, clear the Application ID list in S1804; if the timer receives the first To subscribe to the event notification, it will be processed according to S1816).

At S1813, if the paging fails, AMF sends DDN failure to vSMF. vSMF may instruct vUPF to discard or save downstream data.

At S1814, when the UE next connects to the network, the AMF network element detects that the UE is reachable. The AMF network element sends a UE reachable notification message Namf_EventExposure_notify (UE reachability) to the NEF network element according to the third subscription event.

At S1815, at the same time, if the AMF determines that the user is currently the UE availability after DDN Failure, the AMF sends UE Availablility after DDN Failure to the NEF network element Namf_EventExposure_notify (UE availability after DDN failure) according to the first subscription event.

In S1816, if the NEF network element receives the UE availability after DDN failure of the first subscription event, the NEF network element sends the UE availability availability after DDN failure event to the corresponding AF in the Application ID list saved in S1804. Because S1814 and S1815 may be sent from the AMF network element at the same time, if the NEF network element receives the user reachable notification of the third subscription event first, the NEF network element can set a timer locally before the timer expires. When the event notification of the first subscription event is reached, the UE is sent the AF availability event after DDN failure event; if the notification of the first subscription event is not received before the timer expires, it means that the notification of S1812 is received, and it is processed according to S1812.

At S1817, the NEF network element sends a UE availability after DDN failure notification message to the AF.

The present disclosure provides a message notification method. When a target network element fails to generate downlink data according to a first request, a first subscription event that is reachable by the UE (that is, UE available after DDN failed), compares the first subscription event with the first The application ID of the AF in the request (that is, Application ID, and it should be understood that the application ID in this embodiment may be a unique identifier / any information that identifies AF) is associated; the target network element detects that it has subscribed to the first subscription When the target UE corresponding to the AF of the event changes from unreachable to reachable, the UE reachability notification (that is, a UE reachability notification message) after the sending of downlink data fails includes the application identification of the AF; thus the NEF network element is According to the application identifier in the UE reachability notification after the failure of the downlink data, the UE-reachable notification message can be sent to the AF corresponding to the application identifier in a targeted manner; the rationality of sending the UE-reachable notification message and the utilization of network resources .

In order to facilitate understanding and understanding, the flow of a message notification method is taken as an example for description. In this embodiment, the method flow of the NEF network element side is used for description. However, it should be understood that the following method steps are not limited to NEF network elements, but can also be performed by other network elements that can communicate with AF. FIG. 19 is a flowchart of a message notification method on the NEF network element side according to another embodiment of the present disclosure. Referring to FIG. 19, the message notification method on the NEF network element side may include but not limited to steps S1901 to S1904.

At S1901, a request sent by the AF for a UE reachable event (UE availability after DDN failed event) after a failure to subscribe to downlink data is received.

According to an embodiment of the present disclosure, the AF may send a request for a UE reachable event after subscribing to downlink data fails through various interactive messages (including signaling) with the NEF network element, such as but not limited to Nnef_Event Exposure_Subscribe request.

According to an embodiment of the present disclosure, the request sent by the AF for the UE reachable event after failing to subscribe to the downlink data may include the application ID of the AF, or may not include the application ID of the AF, and the request is received by the NEF network element After that, the application identifier of the AF is extracted according to the sender of the request.

In S1902, according to the request received in S1901, the first request for the UE reachable event after the failure to subscribe to the downlink data is sent to the target network element. The first request includes the NEF ID of the NEF network element (it should be understood that this embodiment The NEF in the ID can be any information that uniquely identifies / identifies the NEF network element) and the application ID of the AF.

Since the first request sent to the target network element includes the NEF ID of the NEF network element and the application ID of the AF, in this way, when the target network element fails to generate the downlink data according to the first request, the first subscription event reachable by the UE may be generated The first subscription event is associated with the NEF ID of the NEF network element and the application ID of the AF; when the subsequent target network element detects that a certain UE changes from unreachable to reachable, it can use the corresponding association relationship The application ID of the AF corresponding to the UE and the NEF ID corresponding to the application ID of the AF are determined, thereby determining the NEF network element to which the AF is connected, so that the UE reachability notification is sent to the UE after the downlink data of the UE fails On the corresponding NEF network element.

According to an embodiment of the present disclosure, the target network element may include but is not limited to at least one of an AMF network element and an SMF network element. And it should be understood that, in addition to the AMF network element and the SMF network element in the above example, the target network element may also be another network connection capable of detecting the UE reachability state or communicating with a network element capable of detecting the UE reachability state. Any network element, such as UDM network element, PCF network element, etc.

In S1903, the UE reachability notification after the failure of receiving the downlink data sent by the target network element. The UE reachability notification after the failure of the downlink data includes the application identification of the AF corresponding to the UE that becomes unreachable.

According to an embodiment of the present disclosure, the UE reachability notification after the failure of the downlink data is sent by the target network element when it detects that the target UE corresponding to the AF subscribed to the first subscription event changes from unreachable to reachable. Moreover, the reachable state of the UE may be directly detected by the target network element, or may be detected by other network elements, and the detection result is sent to the target network element, so that the target network element determines the reachable state of the UE according to the detection result.

In S1904, the UE reachability notification after the downlink data failure is sent to the AF corresponding to the application identifier included in the UE reachability notification after the received downlink data failure; for other AF, the UE reachability notification after the downlink data failure is not sent, It can not only meet the communication needs, but also improve the utilization rate of network resources.

FIG. 20 is a flowchart of a message notification method on the target network element side according to an embodiment of the present disclosure. Referring to FIG. 20, on the target network element side, the message notification method on the target network element side may include but is not limited to step S2001 and S2002.

In S2001, receiving a first request sent by a NEF network element for a UE reachable event after a failure to subscribe to downlink data, and generating a first subscription event for the UE reachable after a downlink data failure according to the first request.

As shown above, the first request includes the application ID of the AF and the NEF ID of the NEF network element. The first subscription event may be associated with the application ID of the AF and the NEF ID of the NEF network element in the first request.

In S2002, when it is detected that the UE corresponding to the corresponding application identifier changes from unreachable to reachable according to the first subscription event, the UE reaches the corresponding NEF network element after the downlink data fails to be notified, and after the downlink data fails, the UE The reachable notification includes the application identification.

That is, in this step, the target network element may correspond to the first subscription event when detecting that the UE corresponding to the application identifier corresponding to the first subscription event changes from unreachable to reachable according to the first subscription event The NEF network element corresponding to the NEF ID of the UE fails to send the downlink data after sending the downlink data, and the UE reachable notification after the sent downlink data fails includes the application ID and the application ID corresponding to the first subscription event.

As shown above, the target network element may include but is not limited to at least one of an AMF network element and an SMF network element. And in some examples, UDM network elements, PCF network elements, etc. may also be used, but not limited to.

The present disclosure also provides a message notification device, which can be installed in a NEF network element or other network elements that can communicate with AF. Each module included in the message notification device can be implemented but is not limited to the above method Corresponding functions in, and the functions of each module can be realized by but not limited to the processor or controller of the network element.

21 is a schematic structural diagram of a message notification device according to another embodiment of the present disclosure. Referring to FIG. 21, the message notification device in this embodiment includes but is not limited to a first request receiving module 2101, a first event subscription request module 2102, a first notification receiving module 2103, and a first notification sending module 2104.

The first request receiving module 2101 is configured to receive a request sent by the AF for a UE reachable event after failing to subscribe to downlink data.

The first event subscription request module 2102 is configured to send a first request for a UE reachable event after subscribing to downlink data fails to the target network element according to the request received by the first request receiving module 2101. The first request includes a network open function NEF network The NEF ID of the meta and the application ID of the AF.

The first notification receiving module 2103 is configured to receive the UE reachability notification after the downlink data sent by the target network element fails, and the UE reachability notification after the downlink data fails includes the application ID of the AF corresponding to the unreachable UE .

The first notification sending module 2104 is used for the UE reachability notification after the AF corresponding to the application identifier included in the UE reachability notification after the downlink data failure fails to send the downlink data.

With the message notification method and apparatus according to the embodiments of the present disclosure, the UE reachable notification message can be sent to the AF in a targeted manner, as opposed to directly sending the UE reachable to all AFs that have subscribed to the downlink data after the UE reachability event fails Notification messages can improve communication accuracy, reliability, and network resource utilization.

22 is a schematic structural diagram of an SMF network element according to an embodiment of the present disclosure. Referring to FIG. 22, the SMF network element includes a first processor 2201, a first memory 2202, and a first communication bus 2203.

The first communication bus 2203 is used to connect the first processor 2201 and the first memory 2202.

The first processor 2201 is used to execute the computer program stored in the first memory 2202 to implement but not limited to the steps of the message notification method as described above.

FIG. 23 is a schematic structural diagram of an NEF network element according to an embodiment of the present disclosure. Referring to FIG. 23, the NEF network element includes a second processor 2301, a second memory 2302, and a second communication bus 2303.

The second communication bus 2303 is used to connect the second processor 2301 and the second memory 2302.

The second processor 2301 is used to execute the computer program stored in the second memory 2302 to implement but not limited to the steps of the message notification method as described above.

24 is a schematic structural diagram of an AMF network element according to an embodiment of the present disclosure. Referring to FIG. 24, the AMF network element includes a third processor 2401, a third memory 2402, and a third communication bus 2403.

The third communication bus 2403 is used to connect the third processor 2401 and the third memory 2402.

The third processor 2401 is used to execute the computer program stored in the third memory 2402 to implement but not limited to the steps of the message notification method as described above.

The present disclosure also provides a communication system, including a target network element and a NEF network element; the target network element may be an AMF network element or an SMF network element.

The target network element is used to receive a first request for a UE reachable event after failing to subscribe to downlink data, and to generate a first subscription event for the UE reachable after failed downlink data according to the first request. The element ID NEF and the event reference ID of the first subscription event, the first subscription event is associated with the event reference ID of the first subscription event; and the UE reachability notification after receiving the downlink data of the target UE corresponding to the application ID fails, According to the first subscription event, the UE reachability notification is sent to the NEF network element after the downlink data fails.

The NEF network element is used for the UE reachability notification after the AF corresponding to the application identifier included in the UE reachability notification after the downlink data failure fails to send the downlink data.

This embodiment also provides a computer-readable storage medium, which is implemented in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules, or other data) Volatile or non-volatile, removable or non-removable media. Computer-readable storage media include but are not limited to RAM (Random Access Memory, random access memory), ROM (Read-Only Memory, read-only memory), EEPROM (Electrically Erasable Programmable read only memory, live erasable programmable read-only memory ), Flash memory or other memory technology, CD-ROM (Compact Disc Read-Only Memory, CD-ROM), digital versatile disk (DVD) or other optical disk storage, magnetic box, magnetic tape, magnetic disk storage or other magnetic storage devices, Or any other medium that can be used to store desired information and can be accessed by a computer.

According to an embodiment of the present disclosure, a computer-readable storage medium is used to store one or more computer programs, which may be executed by one or more processors to implement the message notification method as described above.

The present disclosure also provides a computer program (or computer software) that can be distributed on a computer-readable medium and executed by a computable device to implement at least one step of the message notification method as described above; and In some cases, at least one step shown or described may be performed in an order different from that described in the above embodiment.

The present disclosure also provides a computer program product, including a computer readable device on which the computer program shown above is stored. In this embodiment, the computer-readable device may include the computer-readable storage medium as described above.

It can be seen that those skilled in the art should understand that all or some of the steps, systems, and functional modules / units in the method disclosed above can be implemented as software (which can be implemented by computer program code executable by a computing device) ), Firmware, hardware and their appropriate combinations. In a hardware implementation, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be composed of several physical The components are executed in cooperation. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit .

In addition, it is well known to those of ordinary skill in the art that communication media generally contains computer readable instructions, data structures, computer program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery medium. Therefore, the present invention is not limited to any specific combination of hardware and software.

The above is a further detailed description of the embodiments of the present invention in conjunction with specific implementations, and it cannot be assumed that the specific implementation of the present invention is limited to these descriptions. For a person of ordinary skill in the technical field to which the present invention belongs, without deviating from the concept of the present invention, several simple deductions or replacements can be made, which should be regarded as falling within the protection scope of the present invention.

Claims

A message notification method, including:

Receiving a first request for a user equipment (UE) reachability event after failing to subscribe to downlink data, and generating a first subscription event for UE reachability after downlink data failure according to the first request, where the first request includes interrelated first The application identification of the three-party application (AF), the NEF identification of the network open function (NEF) network element, and the event reference identification of the first subscription event;

After receiving the downlink data failure of the target UE corresponding to the application identifier, the UE reachability notification is sent to the NEF network element according to the first subscription event, after the downlink data failure.
The message notification method according to claim 1, wherein when generating a first subscription event that is reachable by the UE after a failure of downlink data, a first notification identifier is further generated, the first notification identifier and the first subscription event Event reference identifier association. When the value of the first notification identifier is a first preset value, it indicates that the first subscription event associated with the event reference identifier of the first subscription event needs to report that the downlink data fails. The UE is reachable Notice.
The message notification method according to claim 2, wherein, after the downlink data fails, the UE reachability notification is that the access management function (AMF) network element detects that the state of the target UE changes from unreachable to reachable, And the current value of the second notification identifier corresponding to the first subscription event is sent when the first preset value.
The message notification method according to claim 3, wherein before the UE reachability notification after receiving the downlink data fails, further comprising:

Send a message to a user plane function (UPF) network element to activate the application data detection function corresponding to the application identifier.
The message notification method according to claim 4, wherein before the UE reachability notification after failure to receive the downlink data, further comprising:

Receiving an application data detection notification including the application identifier from the UPF network element, and if it is determined that the target UE to be delivered by the AF corresponding to the application identifier is currently unreachable, set a first subscription associated with the application identifier The first notification identifier corresponding to the event reference identifier of the event is the first preset value.
The message notification method according to claim 5, wherein before the UE reachability notification after receiving the downlink data fails, further comprising:

When it is determined that the target UE to be delivered by the AF corresponding to the application identifier is currently unreachable, a message is sent to the AMF network element to subscribe to the reachable state event of the target UE.
The message notification method according to any one of claims 2-6, wherein before sending the UE reachability notification after the failure of the downlink data to the NEF network element, further comprising:

It is determined whether the first notification identifier is currently the first preset value.
The message notification method according to any one of claims 1 to 6, wherein the first request includes at least one of the following requests:

Event open subscription request from a unified data management (UDM) network element;

Session policy control update notification request from the policy control function (PCF) network element.
A message notification device, including:

A third event subscription processing module, configured to receive a first request for a UE reachable event after failing to subscribe to downlink data, and generate a first subscription event for the UE reachable after failed downlink data according to the first request, in the first request Including an associated AF application ID, NEF network element ID NEF ID and the event reference ID of the first subscription event;

The fifth notification sending module is configured to receive the UE reachability notification after the downlink data of the target UE corresponding to the application identifier fails, and send the UE reachability notification after the downlink data failure to the institute according to the first subscription event Describe the NEF network element.
The message notification apparatus according to claim 9, wherein the third event subscription processing module is further used to: when generating the first subscription event reachable by the UE after the failure of the downlink data:

Generate a first notification identifier, the first notification identifier is associated with an event reference identifier of the first subscription event, and when the value of the first notification identifier is a first preset value, characterize The first subscription event associated with the event reference identifier needs to be notified of UE reachability after failure to report the downlink data.
A message notification method, including:

Receive the request sent by the AF for the UE reachable event after subscribing to the downlink data fails;

Send a first request to the AMF network element after the UE fails to subscribe to the downlink data, and send a second request to the session management function (SMF) network element to subscribe to the application data detection event;

Receiving an application data detection notification sent by the SMF network element, and storing the application identifier in the application data detection notification in an application identifier list;

UE reachability notification after failure to receive the downlink data sent by the AMF network element;

Sending the UE reachable notification after the failure of the downlink data to the AF corresponding to the application identifier included in the application identifier list.
The message notification method according to claim 11, wherein after receiving the application data detection notification sent by the SMF network element, the method further comprises:

Send a third request to subscribe to the UE reachable event to the AMF network element;

When receiving the UE reachability notification sent by the AMF network element, the application identification list is cleared.
The message notification method according to claim 12, wherein before the application identification list is cleared, further comprising:

Start timing when the UE reachable notification is received;

When the timing value reaches the set time value, if the UE is not reachable after receiving the downlink data failure, the application identification list is cleared.
The message notification method according to claim 12, wherein clearing the application identification list includes one of the following:

Clear all application identifiers in the application identifier list;

Clear the application identifier in the application list that is the same as the application identifier included in the UE reachability notification.
The message notification method according to any one of claims 11-14, wherein the UE reachability notification after the failure of sending the downlink data to the AF corresponding to the application identifier included in the application identifier list includes one of the following:

Sending the UE reachability notification after the downlink data fails to the AF corresponding to all application identifiers included in the application identifier list;

Sending the UE reachability notification after the downlink data fails to the AF corresponding to the application identifier included in the UE reachability notification after the downlink data failure in the application identification list.
The message notification method according to any one of claims 11 to 14, wherein the first request or the third request for sending a subscription to the AMF network element includes at least one of the following:

Send the first request or the third request to the AMF network element through the event open subscription request of the UDM network element.
The message notification method according to any one of claims 11-14, wherein the second request for sending a subscription to the SMF network element includes at least one of the following:

Send a second request to the SMF network element through the event open subscription request of the UDM network element;

Send a second request to the SMF network element through the session policy control update notification request of the PCF network element.
A message notification method, including:

Receiving a second request sent by the NEF network element to subscribe to the application data detection event, and generating a second subscription event detected by the application data according to the second request, where the second request includes the AF application identifier and the NEF network element's Identify NEF ID;

Request the UPF network element to activate the application data detection of the AF corresponding to the application identifier;

Receiving an application data detection notification sent by the UPF network element, where the application data detection notification includes an application identification of an AF that detects that downlink data has been sent;

Sending the application data detection notification to the NEF network element.
The message notification method according to claim 18, wherein the second request to receive the subscription application data detection event sent by the NEF network element includes at least one of the following:

Receiving the second request through an event open subscription request of a UDM network element;

The second request is received through a session policy control update notification request of the PCF network element.
A message notification device, including:

The second request receiving module is used to receive the request sent by the AF for the UE reachable event after subscribing to the downlink data fails;

The second event subscription request module is used to send a first request to the AMF network element that the UE can reach the event after subscribing to the downlink data according to the request, and send a second request to the SMF network element to subscribe to the application data detection event;

A second notification receiving module, configured to receive the application data detection notification sent by the SMF network element, store the application identification in the application data detection notification in the application identification list; and receive the AMF network element to send the notification UE reachable notification after downlink data failure;

The second notification sending module is configured to send the UE reachability notification after the downlink data fails to the AF corresponding to the application identifier included in the application identifier list.
The message notification device according to claim 20, wherein

The second event subscription request module is also used to send a third request to subscribe to the UE reachable event to the AMF network element;

The second notification receiving module is further configured to clear the application identification list when receiving the UE reachable notification sent by the AMF network element.
A message notification device, including:

The fourth request receiving module is configured to receive a second request sent by the NEF network element to subscribe to the application data detection event, where the second request includes the AF application ID and the NEF ID NEF ID;

A second event subscription processing module, configured to generate a second subscription event detected by application data according to the second request, and to request an UPF network element to activate an AF application corresponding to the application identifier according to the second subscription event Data detection

A fourth notification sending module, configured to receive an application data detection notification sent by the UPF network element, where the application data detection notification includes an application identifier that detects the AF that has sent the downlink data, and sends the application data detection notification to The NEF network element.
A message notification method, including:

Receive the request sent by the AF for the UE reachable event after subscribing to the downlink data fails;

Sending, according to the request, to the target network element a first request for a UE reachable event after a failure to subscribe for downlink data, the first request includes an NEF network element identifier NEF ID and the AF application identifier;

Receiving the UE reachability notification after the failure of the downlink data sent by the target network element, where the UE reachability notification after the failure of the downlink data includes the application identification of the AF corresponding to the unreachable UE;

Sending the UE reachability notification after the downlink data failure to the AF corresponding to the application identifier included in the UE reachability notification after the downlink data failure.
The message notification method according to claim 23, wherein the target network element includes at least one of the following:

AMF network element;

SMF network element.
A message notification device, including:

The first request receiving module is used to receive the request sent by the AF for the UE reachable event after the subscription of the downlink data fails;

The first event subscription request module is configured to send a first request for a UE reachable event after a failure to subscribe to downlink data to the target network element according to the request, the first request includes an NEF network element identifier NEF ID and the AF Application identification;

The first notification receiving module is configured to receive the UE reachability notification after the downlink data sent by the target network element fails, and the UE reachability notification after the downlink data fails includes the AF corresponding to the UE that becomes unreachable and becomes reachable Application identification

The first notification sending module is configured to send the UE reachability notification after the downlink data failure to the AF corresponding to the application identifier included in the UE reachability notification after the downlink data failure.
An SMF network element includes a first processor, a first memory, and a first communication bus;

The first communication bus is used to connect the first processor and the first memory;

The first processor is used to execute a computer program stored in the first memory to implement the message notification method according to any one of claims 1-8 or the message according to any one of claims 17-18 Notification method.
An NEF network element, including a second processor, a second memory, and a second communication bus;

The second communication bus is used to connect the second processor and the second memory;

The second processor is used to execute a computer program stored in the second memory to implement the message notification method according to any one of claims 11-16 or the message notification method according to any one of claims 22 or 23.
A communication system, including target network element and NEF network element;

The target network element is used to receive a first request for a UE reachability event after failing to subscribe to downlink data, and generate a first subscription event for the UE reachability after downlink data failure according to the first request, where the first request includes AF The application ID of NEF, the NEF ID of the NEF network element, and the event reference ID of the first subscription event, the first subscription event is associated with the event reference ID of the first subscription event; and the corresponding ID for receiving the application ID After the downlink data of the target UE fails, the UE reachability notification is sent to the NEF network element according to the first subscription event, after the downlink data fails.

The NEF network element is used to send the UE reachability notification after the downlink data fails to the AF corresponding to the application identifier included in the UE reachability notification after the downlink data failure.
A computer-readable storage medium for storing one or more computer programs, the one or more computer programs can be executed by one or more processors to implement claims 1- The message notification method according to any one of 8, the message notification method according to any of claims 17 or 18, the message notification method according to any of claims 11 to 16, or the message according to claim 22 or 23 Notification method.