WO2020192787A1 - 事件通知方法、装置及存储介质 - Google Patents

事件通知方法、装置及存储介质 Download PDF

Info

Publication number
WO2020192787A1
WO2020192787A1 PCT/CN2020/082036 CN2020082036W WO2020192787A1 WO 2020192787 A1 WO2020192787 A1 WO 2020192787A1 CN 2020082036 W CN2020082036 W CN 2020082036W WO 2020192787 A1 WO2020192787 A1 WO 2020192787A1
Authority
WO
WIPO (PCT)
Prior art keywords
event
notification
downlink data
subscription
nef
Prior art date
Application number
PCT/CN2020/082036
Other languages
English (en)
French (fr)
Inventor
洪英杰
朱进国
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to KR1020237037105A priority Critical patent/KR20230152838A/ko
Priority to EP20779067.6A priority patent/EP3952367A4/en
Priority to KR1020217034595A priority patent/KR102596924B1/ko
Priority to US17/599,191 priority patent/US20220191665A1/en
Publication of WO2020192787A1 publication Critical patent/WO2020192787A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • This application relates to wireless communication technology, for example, to an event notification method, device, and storage medium.
  • UE User Equipment
  • the application function (AF, Application Function) does not know the status of the UE. Therefore, in order to effectively allow the AF to send downlink data (DownLink data or DL data) to the UE, the AF will access the management function (AMF, Access Management Function)
  • AMF Access Management Function
  • Network Exposure Function sends a UE reachable notification message to all AFs that have subscribed to the UE availability after DDN failed event, so as to ensure that the AF can then deliver data to the UE when it knows that the UE is reachable.
  • the general process includes:
  • the user plane function (UPF, User Plane Function) will send a Downlink Data Notify (DDN) message to the AMF after receiving it to notify the AMF that there is downlink data to send and need to be awakened UE; if AMF cannot wake up the UE, it will return a downlink data notification failure (DDN failure) response; and when the UE status changes from unreachability to availability, AMF will give all the UEs that have subscribed to the above availability after DDN failed The AF of the event sends a notification message that the UE is reachable.
  • DDN Downlink Data Notify
  • AMF when the UE status changes from unreachable to reachable, AMF will send a UE reachable notification message to all AFs that have subscribed to the aforementioned UE availability after DDN failed event. However, not all AFs need to receive the notification message that the UE is reachable. Therefore, the UE-reachable event notification method in the related technology causes a waste of network resources.
  • the present application provides an event notification method, device and storage medium, which can avoid the waste of network resources.
  • This application provides an event notification method, including:
  • the network exposure function NEF obtains the application function AF information that sends the downlink data according to the second event notification from the session management function SMF;
  • NEF receives the first event notification from the access management function AMF, and sends the first event notification to the AF that sends the downlink data according to the obtained AF information for sending the downlink data;
  • the second event is an event that monitors whether the AF sends downlink data
  • the first event is an event that the UE is reachable after the downlink data notification fails.
  • the acquiring AF information for sending downlink data includes:
  • the NEF receives the second event notification from the SMF that carries the AF identifier or the identifier associated with the AF;
  • the NEF sets the UE reachable message notification Notify-on-available-after-DDN-failure identifier according to the received AF identifier or the identifier associated with the AF after the downlink data notification associated with the AF fails.
  • the method before the acquiring AF information for sending downlink data, the method further includes:
  • the NEF receives the event subscription request sent from the AF, and the NEF generates a subscription event identifier NEF reference ID, where the NEF reference ID is associated with the AF identifier;
  • the NEF sends an event subscription request to the unified data management function UDM.
  • the information carried in the event subscription request from the AF includes: subscription event type 1, AF identification, and UE identification;
  • the information carried in the event subscription request sent by the NEF to the UDM includes: the NEF reference ID of the subscription event, the subscription event type 1, and event notification object information.
  • the method before the acquiring AF information for sending downlink data, the method further includes:
  • the NEF receives the event subscription request from the AF that carries the subscription event type 1 and the AF identifier, or the NEF receives the event subscription request from the AF that carries the subscription event type 2 and the AF identifier;
  • the NEF generates a subscription event ID NEF reference ID, where the NEF reference ID is associated with the AF ID;
  • the NEF sends an event subscription request to the policy control function PCF.
  • the information carried in the event subscription request sent by the NEF to the PCF includes:
  • the subscription event type one includes: UE reachability after DDN failure type after downlink data notification fails;
  • the second type of subscription event includes: a downlink data delivery status type.
  • This application provides a computer-readable storage medium that stores computer-executable instructions, and the computer-executable instructions are used to execute an event notification method described in any one of the above.
  • the present application provides a device for implementing event notification, including a processor and a memory; wherein a computer program that can be run on the processor is stored in the memory for executing an event notification method described in any one of the above.
  • This application provides another event notification method, including:
  • the access management function AMF obtains the application function AF information that sends the downlink data according to the second event notification from the session management function SMF;
  • the AMF sends the first event notification to the AF sending the downlink data via the network exposure function NEF according to the obtained AF information for sending the downlink data;
  • the second event is an event that monitors whether the AF sends downlink data
  • the first event is an event that the UE is reachable after the downlink data notification fails.
  • the acquiring AF information for sending downlink data includes:
  • the AMF receives the second event notification from the SMF that carries the AF identifier or the identifier associated with the AF;
  • the AMF sets the UE reachable message notification Notify-on-available-after-DDN-failure identifier according to the received AF identifier or the identifier associated with the AF after the downlink data notification associated with the AF fails.
  • the AMF sending the first event notification to the AF sending the downlink data via the NEF includes:
  • the AMF When the AMF detects that the UE status changes from unreachable to reachable, the AMF notifies the Notify-on-available-after-DDN-failure identifier of the UE reachable message according to the downlink data notification failure, via the NEF Send the first event notification to the AF that sends the downlink data.
  • the method before the acquiring AF information for sending downlink data, the method further includes:
  • the AMF receives the first event subscription request for subscribing to the first event from the unified data management function UDM, and completes the subscription of the first event;
  • the information carried in the first event subscription request includes: NEF reference ID NEF reference ID, subscription event type 1, event notification object information, and event monitoring object information.
  • the present application provides a computer-readable storage medium that stores computer-executable instructions, and the computer-executable instructions are used to execute another event notification method described in any one of the above.
  • This application provides a device for implementing event notification, including a processor and a memory; wherein a computer program that can be run on the processor is stored in the memory: for executing another event notification method described in any one of the above .
  • This application provides an event notification device, including: an association module and a first notification module; wherein,
  • the association module is used to obtain the AF information of the application function sending the downlink data according to the second event notification from the session management function SMF; where the second event is an event that monitors whether the AF sends the downlink data; the first event is the failure of the downlink data notification Later UE reachable event;
  • the first notification module is configured to send a first event notification to the AF sending the downlink data according to the obtained AF information for sending the downlink data.
  • the acquiring AF information for sending downlink data in the association module includes:
  • the UE can set the downlink data notification associated with the AF after the failure Notify-on-available-after-DDN-failure identification is notified by the arrival message.
  • the event notification device is set in the network exposure function NEF, or the event notification device is NEF.
  • the first notification module is configured to: receive the first event notification from the access management function AMF, and send the first event notification to the AF sending the downlink data according to the AF information for sending the downlink data. Event notification.
  • the event notification device is provided in AMF, or the event notification device is AMF.
  • the first notification module is configured to: according to the obtained AF information for sending downlink data, send the first event notification to the AF sending the downlink data via a network exposure function NEF.
  • This application provides yet another event notification method, including:
  • the session management function SMF receives the second event subscription request and completes the second event subscription; where the second event is an event that monitors whether the AF sends a downlink data;
  • the SMF sends a second event notification to the network exposure function NEF or the access management function AMF;
  • the second event notification is used to notify NEF or AMF to issue AF information of downlink data.
  • the SMF receiving the second event subscription request and completing the second event subscription includes:
  • the SMF receives the second event subscription request from the unified data management function UDM, and completes the second event subscription; wherein, the information carried in the second event subscription request includes: subscription event type one, event notification set to NEF related address Object information, AF logo.
  • the SMF receiving the second event subscription request and completing the second event subscription includes:
  • the SMF receives the second event subscription request from the AMF, and completes the second event subscription; wherein, the information carried in the second event subscription request includes: subscription event type 1 or subscription event type 2, set as AMF related address
  • the SMF receiving the second event subscription request and completing the second event subscription includes:
  • the SMF receives the second event subscription request from the policy control function PCF, and completes the second event subscription; wherein, the information carried in the second event subscription request includes: subscription event type two, event notification object set as the NEF related address Information, AF logo.
  • the subscription event type one includes: UE reachability after DDN failure type after downlink data notification fails;
  • the second type of subscription event includes: a downlink data delivery status type.
  • the SMF sending the second event notification to NEF or AMF includes:
  • the SMF learns that the UE is currently unreachable and receives downlink data detection information from the user plane function UPF, the SMF obtains the subscription event associated with the AF ID according to the AF ID contained in the downlink data detection information; The SMF sends to the NEF or the AMF the second event notification carrying the AF identifier or the identifier associated with the AF according to the notification object information of the subscription event associated with the AF identifier; or,
  • the SMF detects that the downlink data status of the AF is in the cache state, the SMF obtains the subscription event associated with the AF identifier according to the AF identifier; the SMF sends the notification object information of the subscription event associated with the AF identifier to the The NEF or the AMF sends a second event notification that carries an AF identifier or an identifier associated with the AF.
  • the method before the SMF sends the second event notification to NEF or AMF, the method further includes:
  • the SMF requests the UPF to send downlink data detection information including the AF identifier; or,
  • the SMF notifies the UPF to perform downlink data buffering.
  • This application provides a computer-readable storage medium that stores computer-executable instructions, and the computer-executable instructions are used to execute yet another event notification method described in any one of the above.
  • This application provides a device for implementing event notification, including a processor and a memory; wherein a computer program that can be run on the processor is stored in the memory: for executing another event notification method described in any one of the above .
  • This application provides an event notification device, including: a processing module and a second notification module; wherein,
  • the processing module is configured to receive the second event subscription request and complete the subscription of the second event; where the second event is an event that monitors whether the AF sends a downlink data;
  • the second notification module is used to send a second event notification to the exposed function NEF or the access management function AMF when the application function AF sends downlink data to the UE but the UE status is unreachable; wherein the second event notification is used to notify the NEF Or AMF sends the AF information of downlink data.
  • the event notification device is set in a session management function SMF, or the event notification device is an SMF.
  • the processing module is specifically configured to:
  • the information carried in the second event subscription request includes: subscription event type one, event notification object information set as the NEF related address, AF logo; or,
  • Second event subscription request from the AMF, and complete the second event subscription; where the information carried in the second event subscription request includes: subscription event type one or subscription event type two, event notification set as AMF related address Object information, AF logo.
  • the second notification module is specifically configured to:
  • the subscription event associated with the AF ID is obtained according to the AF ID contained in the downlink data detection information; the subscription event associated with the AF ID is obtained
  • the notification object information of the subscribed event sends the second event notification carrying the AF identifier or the identifier associated with the AF to the NEF or the AMF; or,
  • the notification object information of the subscription event associated with the AF identifier is sent to the NEF or the AMF with The second event notification of the AF identifier or the identifier associated with the AF.
  • the second notification module is further configured to: request the UPF to send downlink data detection information including the AF identifier; or, notify the UPF to perform downlink data buffering.
  • An event notification method provided by the present application includes: NEF obtains AF information for sending downlink data according to a second event notification from SMF; wherein, the second event is an event that monitors whether the AF sends downlink data; and the first event is downlink data.
  • the UE reachable event after the notification fails; NEF receives the first event notification from the AMF, and sends the first event notification to the AF that sends the downlink data according to the obtained AF information for sending the downlink data.
  • the present application learns the AF information for sending downlink data through the second event notification, thereby ensuring that the first event notification is sent to the required AF and avoiding the waste of network resources.
  • Another event notification method provided by this application includes: AMF obtains AF information for sending downlink data according to a second event notification from SMF; wherein the second event is an event that monitors whether the AF sends downlink data; and the first event is a downlink The UE reachable event after the data notification fails; the AMF sends the first event notification to the AF sending the downlink data via the NEF according to the obtained AF information for sending the downlink data.
  • the present application learns the AF information for sending downlink data through the second event notification, thereby ensuring that the first event notification is sent to the required AF and avoiding the waste of network resources.
  • Another event notification method provided by this application includes: SMF receives a second event subscription request and completes the subscription of the second event; where the second event is to monitor whether the AF sends a downlink data event; when the AF sends a downlink data event to the UE When data but the UE status is unreachable, SMF sends a second event notification to NEF or AMF.
  • This application learns the AF information for sending the downlink data through the second event notification, thereby ensuring that the subsequent first event notification is sent to the required AF and avoiding the waste of network resources.
  • Figure 1 is a schematic diagram of the composition architecture of the next-generation wireless access network in related technologies
  • FIG. 2 is a schematic flowchart of an event notification method provided by an embodiment of this application.
  • FIG. 3 is a schematic flowchart of another event notification method provided by an embodiment of this application.
  • FIG. 4 is a schematic diagram of the composition structure of an event notification device provided by an embodiment of the application.
  • FIG. 5 is a schematic flowchart of another event notification method provided by an embodiment of this application.
  • FIG. 6 is a schematic diagram of the composition structure of another event notification device provided by an embodiment of the application.
  • FIG. 7 is a schematic diagram of a flow of subscribing to a first event and a second event according to an embodiment of the application;
  • FIG. 8 is a schematic diagram of another flow of subscribing to the first event and the second event provided by an embodiment of the application;
  • FIG. 9 is a schematic flowchart of a second event notification provided by an embodiment of this application.
  • FIG. 10 is a schematic diagram of another flow of subscribing to the first event and the second event provided by an embodiment of the application;
  • FIG. 11 is a schematic flowchart of another second event notification provided by an embodiment of this application.
  • the computing device includes one or more central processing units (CPU), input/output interfaces, network interfaces, and memory.
  • CPU central processing units
  • input/output interfaces input/output interfaces
  • network interfaces network interfaces
  • memory volatile and non-volatile memory
  • Memory may include non-permanent memory in computer readable media, random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). Memory is an example of computer readable media.
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash memory
  • Computer-readable media include permanent and non-permanent, removable and non-removable media, and information storage can be realized by any method or technology.
  • the information can be computer-readable instructions, data structures, program modules, or other data.
  • Examples of computer storage media include, but are not limited to, phase change RAM (PRAM), static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), and other types of random access memory.
  • RAM random access memory
  • ROM read-only memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • flash memory or other memory technologies
  • read-only CD-ROM Compact Disc-ROM, CD-ROM
  • Digital Video Disc DVD or other optical storage
  • magnetic cassettes magnetic tape storage or other magnetic storage devices or any other non-transmission media that can be used for storage Information that can be accessed by computing devices.
  • computer-readable media does not include non-transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.
  • next-generation wireless mobile access network supports multiple wireless networks to access a unified core network, and it is hoped that the radio access network (RAN, Radio Access Network) and the core network (CN, Core Network) will minimize the coupling relationship, that is, no matter what the terminal is from The RAN access of the access technology can all be connected to the unified CN.
  • the core network function of the next-generation wireless access network supports a service-based interface in order to support more flexible deployment methods.
  • Figure 1 is a schematic diagram of the structure of the next-generation wireless access network in related technologies. As shown in Figure 1, the main network functions (NF, Network Funtion) are introduced as follows:
  • Access Management Function is a common control plane function in the core network, terminating all non-access stratum (NAS) messages between users and the network.
  • a user UE has only one AMF, which is used to implement user mobility management and UE status (such as reachability) management.
  • Session Management Function (SMF, Session Management Function), used for session establishment, modification, deletion, policy control function (PCF, Policy Control Function) charging and policy execution functions.
  • PCF is used to formulate policies for the terminal according to the user's subscription, the current location of the UE, and application-related information, including routing policies, service quality policies, and charging policies.
  • the unified data management function (UDM, Unified Data Management) can be used for unified data management functions such as permanent storage of user subscription data.
  • Unified Data Repository (UDR, Unified Data Repository) is mainly used to store user subscription data and policy data managed by UDM and PCF.
  • the user plane function (UPF, User Plane Function) in the core network is the anchor point of the user plane of the core network, is the interface for data transmission with the external data network (DN, Data Network), and executes the execution of the user plane part of the PCF policy rules, etc. .
  • Network Exposure Function (NEF, Network Exposure Function) is used to expose 3GPP NFs capabilities and events to other NFs or external application functions (AF, Application Function), provide AF pre-configured 3GPP NFs capabilities, and realize 3GPP network and external network information mapping, etc. .
  • AF refers to applications that access 3GPP
  • DN refers to data networks that access 3GPP.
  • FIG 2 is a schematic flowchart of an event notification method provided by this application, as shown in Figure 2, including:
  • Step 200 NEF obtains AF information for sending downlink data according to the second event notification from SMF; wherein, the second event is an event that monitors whether the AF sends downlink data; the first event is that the UE is reachable after the downlink data notification fails (UE availability after DDN failed) event.
  • the second event is an event that monitors whether the AF sends downlink data
  • the first event is that the UE is reachable after the downlink data notification fails (UE availability after DDN failed) event.
  • the SMF when the AF sends downlink data to the UE but the UE status is unreachable, the SMF will send a second event notification to the NEF to notify the NEF to compare the first event with the AF that needs to receive the first event notification. Correlation between them is to determine which AF needs to receive the first event notification.
  • acquiring AF information for sending downlink data in this step includes:
  • NEF receives the second event notification from SMF that carries the AF identifier or the identifier associated with the AF; NEF sets the UE reachable message after the failure of the downlink data notification associated with the AF identifier according to the received AF identifier or the identifier associated with the AF
  • the notification (Notify-on-available-after-DDN-failure) identifier that is, the Notify-on-available-after-DDN-failure identifier is associated with the AF.
  • the Notify-on-available-after-DDN-failure flag is associated with the first event.
  • the Notify-on-available-after-DDN-failure flag is set, it means the first event of the subsequent first event The notification needs to be sent to the associated AF.
  • this step it may further include:
  • NEF receives event subscription requests from AF such as Nnef_EventExposure_Subscribe request, NEF generates subscription event identifier (NEF reference identifier (NEF reference ID)), NEF reference ID and AF identifier are associated; among them, the event subscription from AF
  • the information carried in the request includes, for example: subscription event type 1 (the UE can reach "availability after DDN failure" after the following data notification fails), information used to identify AF (for example: traffic descriptor), internet communication Protocol filter information (Internet Protocol filter information, IP filter information), AF ID and other information that can uniquely identify the AF identity in the entire system, such information can also be referred to as AF identity in this article), UE identity and other information .
  • NEF sends an event subscription request such as Nudm_EventExposure_subscribe request to UDM.
  • the information carried in the event subscription request from NEF includes: NEF reference ID, subscription event type information (such as event identifier Event ID, subscription event type "availability after DDN failure", etc. ), event notification endpoint information (such as related information such as the address where NEF receives event notifications).
  • this step it may further include:
  • NEF receives the event subscription request sent from AF such as Nnef_EventExposure_Subscribe request, where the information carried in the event subscription request from AF includes, for example: subscription event type one (for example, UE can reach the "availability after DDN failure" type after DDN failure), Information that identifies the AF (such as traffic descriptor, IP filter information, AF ID, etc.) that can uniquely identify the AF identity in the entire system, such information may also be referred to as the AF identity in this document), UE identity and other information; or , NEF receives the event subscription request sent from AF such as Nnef_EventExposure_Subscribe request, where the information carried in the event subscription request from AF includes, for example: subscription event type two (the data transmission status "Downlink data delivery status" type in the following row), Information identifying the AF (for example: traffic descriptor, IP filter information, AF ID, etc.) can uniquely identify the AF identity in the entire system, such information may also be
  • NEF generates a subscription event identifier (NEF reference ID), and the NEF reference ID is associated with the AF identifier.
  • NEF sends an event subscription request such as Npcf_EventExposure_subscribe request to the PCF.
  • the information carried in the event subscription request from NEF includes such as: NEF reference ID, subscription event type information (such as event ID Event ID, subscription event type two "Downlink data delivery status", etc. ), event notification endpoint information (such as related information such as the address where NEF receives event notifications).
  • NEF can receive event subscription responses from PCF.
  • NEF returns an event subscription response to AF.
  • Step 201 NEF receives the first event notification from the AMF, and sends the first event notification to the AF that sends the downlink data according to the obtained AF information for sending the downlink data.
  • the AMF when the AMF detects that the UE status changes from unreachable to reachable, it will send a first event notification to the NEF.
  • An embodiment of the present invention also provides a computer-readable storage medium that stores computer-executable instructions, and the computer-executable instructions are used to execute the event notification method described in any of the above-mentioned embodiments related to FIG. 2.
  • An embodiment of the present invention also provides a device for implementing event notification, including a processor and a memory; wherein a computer program that can run on the processor is stored in the memory: for executing any of the above-mentioned embodiments related to FIG. 2 The steps of the item event notification method.
  • FIG 3 is a schematic flow diagram of another event notification method provided by this application, as shown in Figure 3, including:
  • Step 300 The AMF obtains the AF information for sending the downlink data according to the second event notification from the SMF; where the second event is an event that monitors whether the AF sends the downlink data; the first event is that the UE is reachable after the downlink data notification fails (UE availability after DDN failed) event.
  • the SMF when the AF sends downlink data to the UE but the UE status is unreachable, the SMF will send a second event notification to the AMF to notify the AMF to compare the first event with the AF that needs to receive the first event notification. Correlation between them is to determine which AF needs to receive the first event notification.
  • the acquiring AF for sending downlink data in this step includes:
  • the AMF receives the second event notification from the SMF that carries the AF identifier or the identifier associated with the AF; the AMF sets the UE reachable message after the failure of the downlink data notification associated with the AF according to the received AF identifier or the identifier associated with the AF Notification (Notify-on-available-after-DDN-failure) identification.
  • the Notify-on-available-after-DDN-failure flag is associated with the first event.
  • the Notify-on-available-after-DDN-failure flag is set, it means the first event of the subsequent first event The notification needs to be sent to the associated AF.
  • this step it may further include:
  • the AMF receives the request from the SMF to page the UE and page the UE (Namf_CommunicationN1N2MessageTransfer request); when the UE status is unreachable, the AMF feeds back to the SMF the response message (Namf_CommunicationN1N2MessageTransfer response) that the UE is currently in the unreachable state.
  • this step further includes:
  • AMF receives the first event subscription request from UDM, and completes the first event subscription.
  • the information carried in the first event subscription request includes, for example: NEF reference ID (NEF reference ID), subscription event type information (such as event ID (Event ID), subscription event type such as "availability after DDN failure", etc.), events Notification endpoint information (such as related information such as the address of the NEF receiving the first event notification), event monitoring object information (such as UE identification information) and other information.
  • AMF may return the first event subscription response to UDM.
  • Step 301 The AMF sends a first event notification to the AF sending the downlink data via the NEF according to the obtained AF information for sending the downlink data.
  • this step may include:
  • the AMF uses the set Notify-on-available-after-DDN-failure identifier to associate with the Notify-on-available-after-DDN-failure identifier via NEF.
  • AF sends the first event notification.
  • An embodiment of the present invention also provides a computer-readable storage medium that stores computer-executable instructions, and the computer-executable instructions are used to execute the event notification method described in any of the above-mentioned embodiments related to FIG. 3.
  • An embodiment of the present invention also provides a device for implementing event notification, including a processor and a memory; wherein a computer program that can be run on the processor is stored in the memory: it is used to execute any of the above-mentioned embodiments related to FIG. 3 The steps of the item event notification method.
  • FIG. 4 is a schematic diagram of the composition structure of an event notification device provided by this application. As shown in FIG. 4, it includes at least an association module and a first notification module; wherein,
  • the association module is used to obtain the AF information for sending downlink data according to the second event notification from the SMF; where the second event is an event that monitors whether the AF sends the downlink data; the first event is the UE reachable after the downlink data notification fails ( UE availability after DDN failed) event; the first notification module is configured to send a first event notification to the AF sending downlink data according to the obtained AF information for sending downlink data.
  • the acquiring AF information for sending downlink data in the association module includes:
  • the event notification device of this application can be set in NEF or can be NEF. In this case:
  • the first notification module is configured to: receive the first event notification from the AMF, and send the first event notification to the AF sending the downlink data according to the AF information for sending the downlink data.
  • the event notification device of this application can be set in AMF or can be AMF. In this case:
  • the first notification module is configured to: send a first event notification to the AF sending the downlink data via the NEF according to the AF information for sending the downlink data.
  • FIG. 5 is a schematic flowchart of another event notification method provided by this application, as shown in Figure 5, including:
  • Step 500 The SMF receives the second event subscription request, and completes the subscription of the second event; where the second event is an event that monitors whether the AF sends a downlink data.
  • this step may include:
  • the SMF receives the second event subscription request from UDM, and the information carried in the second event subscription request includes, for example, subscription event type information (for example: event ID (Event ID), subscription event type "availability after DDN failure", etc.) , Event notification endpoint information (for example, related information such as the address of the NEF receiving the second event notification), AF identification and other information.
  • subscription event type information for example: event ID (Event ID), subscription event type "availability after DDN failure", etc.
  • Event notification endpoint information for example, related information such as the address of the NEF receiving the second event notification
  • AF identification AF identification
  • the second event subscription request also carries: NEF reference ID (NEF reference ID).
  • this step may include:
  • the SMF receives the second event subscription request from AMF, and the information carried in the second event subscription request includes, for example, subscription event type information (for example: Event ID), subscription event type “availability after DDN failure” or subscription Event type two "Downlink data delivery status", etc.), event notification endpoint information (for example, related information such as the address of the AMF receiving the second event notification), AF identification and other information.
  • subscription event type information for example: Event ID
  • event notification endpoint information for example, related information such as the address of the AMF receiving the second event notification
  • AF identification for example, AF identification and other information.
  • this step may include:
  • the SMF receives the second event subscription request from the PCF, and the information carried in the second event subscription request includes, for example, subscription event type information (for example: event ID (Event ID), subscription event type two "Downlink data delivery status", etc.) , Event notification endpoint information (for example, related information such as the address of the NEF receiving the second event notification), AF identification and other information.
  • subscription event type information for example: event ID (Event ID), subscription event type two "Downlink data delivery status", etc.
  • Event notification endpoint information for example, related information such as the address of the NEF receiving the second event notification
  • AF identification for example, AF identification and other information.
  • Step 501 When the AF sends downlink data to the UE but the UE status is unreachable, the SMF sends a second event notification to the NEF or AMF.
  • the second event notification is used to notify the NEF or AMF to issue the AF information of the downlink data, that is, to determine which AF needs to receive the first event notification.
  • this step may include:
  • Nsmf_EventExposure_Notify When SMF learns that the current status of the UE is unreachable and receives downlink data detection information from UPF, SMF obtains the subscription event associated with the AF identifier according to the AF identifier contained in the downlink data detection information; SMF obtains the subscription event associated with the AF identifier according to the AF identifier Send a second event (such as "availability after DDN failure") notification to NEF, such as Nsmf_EventExposure_Notify.
  • the information carried in Nsmf_EventExposure_Notify includes: AF identifier, or information associated with the AF identifier, such as NEF reference ID; or ,
  • SMF detects that the downlink data status of the AF is in the cached state, SMF obtains the subscription event associated with the AF identifier according to the AF identifier; SMF sends a second event (such as "Downlink") to NEF according to the notification object information of the subscription event associated with the AF identifier data delivery status”) notifications, such as Nsmf_EventExposure_Notify, the information carried in Nsmf_EventExposure_Notify includes, for example, the AF identifier, or information associated with the AF identifier, such as NEF reference ID.
  • this step may include:
  • Nsmf_EventExposure_Notify the information carried in Nsmf_EventExposure_Notify includes such as: AF identifier, or information associated with the AF identifier such as NEF reference ID and other information; or,
  • the SMF detects that the downlink data status of the AF is in the cached state, the SMF obtains the subscription event associated with the AF identifier according to the AF identifier; the SMF sends a second event to the AMF according to the notification object information of the subscription event associated with the AF identifier (eg "Downlink data delivery status") notifications, such as Nsmf_EventExposure_Notify, carry information such as AF identification or AF identification related information such as NEF reference ID and other information in Nsmf_EventExposure_Notify.
  • Nsmf_EventExposure_Notify carry information such as AF identification or AF identification related information such as NEF reference ID and other information in Nsmf_EventExposure_Notify.
  • this step may also include:
  • the SMF sends a UE request (Namf_CommunicationN1N2MessageTransferrequest) to page the user to the AMF to page the UE; the AMF receives a response message (Namf_CommunicationN1N2MessageTransfer response) from the SMF that the UE is currently in an unreachable state.
  • this step may also include:
  • the SMF requests the UPF to send downlink data detection information including the AF identifier; or, the SMF notifies the UPF to buffer the downlink data.
  • the SMF request to send the downlink data detection information including the AF identifier to the UPF includes:
  • SMF sends a downlink data detection information request to UPF; SMF receives a downlink data detection information response from UPF.
  • the downlink data detection information response may be, for example, Downlink Data Notification, or Sx Report, or N4Report.
  • the UPF After the UPF receives the downlink data sent from the AF, it will detect the downlink data, such as detecting the downlink data from which AF, that is to say, it can detect the AF ID of the AF sending the downlink data.
  • An embodiment of the present invention also provides a computer-readable storage medium that stores computer-executable instructions, and the computer-executable instructions are used to execute the event notification method described in any one of the foregoing embodiments related to FIG. 5.
  • An embodiment of the present invention also provides a device for implementing event notification, including a processor and a memory; wherein a computer program that can be run on the processor is stored in the memory: it is used to execute any of the above-mentioned embodiments related to FIG. 5 The steps of the item event notification method.
  • FIG. 6 is a schematic diagram of the composition structure of another event notification device provided by this application. As shown in FIG. 6, it at least includes: a processing module and a second notification module; wherein,
  • the processing module is used to receive the second event subscription request and complete the subscription of the second event; where the second event is monitoring whether the AF sends a downlink data event; the second notification module is used when the AF sends downlink data to the UE but When the UE status is unreachable, a second event notification is sent to NEF or AMF; wherein, the second event notification is used to notify NEF or AMF to issue AF information of downlink data.
  • the event notification device of this application can be set in the SMF or can be an SMF.
  • the second notification module is specifically used for:
  • a second event notification is sent to NEF.
  • the information carried in the second event notification includes, for example, the AF identifier or the identifier associated with the AF identifier such as NEF reference ID and other information; or,
  • the information carried in the second event notification includes the AF identifier, or the identifier associated with the AF, such as NEF reference ID.
  • the second notification module is specifically used for:
  • the second event notification is sent to the AMF.
  • the information carried in the second event notification includes: the AF ID or the ID associated with the AF such as NEF reference ID Wait for information; or,
  • the information carried in the second event notification includes information such as an AF identifier, or an identifier associated with the AF, such as NEF reference ID.
  • the second notification module is also used to:
  • Fig. 7 is a schematic diagram of the flow of subscribing to the first event and the second event provided by this application, as shown in Fig. 7, including:
  • Step 700 AF sends an event subscription request such as Nnef_EventExposure_Subscribe request to NEF.
  • Nnef_EventExposure_Subscribe request carries such as: event type (such as "availability after DDN failure"), information used to identify AF (such as traffic descriptor, IP filter information, AF ID, etc.) that can uniquely identify the AF identity in the entire system. In this article It can be called AF identification), UE identification and other information.
  • event type such as "availability after DDN failure”
  • information used to identify AF such as traffic descriptor, IP filter information, AF ID, etc.
  • Step 701 NEF receives an event subscription request from AF, and generates a subscription event identifier (NEF reference ID), and the NEF reference ID is associated with the AF identifier; NEF sends an event subscription request such as Nudm_EventExposure_subscribe request to UDM.
  • NEF reference ID a subscription event identifier
  • NEF sends an event subscription request such as Nudm_EventExposure_subscribe request to UDM.
  • Nudm_EventExposure_subscribe request carries such as: NEF reference ID, subscription event type information (such as event identifier Event ID, event type "availability after DDN failure", etc.), event notification endpoint information (notification endpoint information) (such as the address where NEF receives event notifications, etc.) Related information) and other information.
  • subscription event type information such as event identifier Event ID, event type "availability after DDN failure", etc.
  • event notification endpoint information notification endpoint information
  • Notification endpoint information such as the address where NEF receives event notifications, etc.
  • Steps 702 to 703 UDM sends a first event subscription request such as Namf_EventExposure_subscribe request to AMF, AMF completes the first event subscription, and returns a first event subscription response such as Namf_EventExposure_subscribe response to UDM.
  • a first event subscription request such as Namf_EventExposure_subscribe request
  • AMF completes the first event subscription
  • a first event subscription response such as Namf_EventExposure_subscribe response to UDM.
  • the first event subscription request carries such as: NEF reference ID, subscription event type information (such as event identifier Event ID, subscription event type "availability after DDN failure", etc.), event notification endpoint information (such as NEF receiving Event notification address and other relevant information), event monitoring object information (such as UE identification information) and other information.
  • subscription event type information such as event identifier Event ID, subscription event type "availability after DDN failure", etc.
  • event notification endpoint information such as NEF receiving Event notification address and other relevant information
  • event monitoring object information such as UE identification information
  • Steps 704 to 705 If the UDM receives the NEF subscription event request message carrying the subscription event type "availability after DDN failure" and the AF identifier, UDM sends a second event subscription request such as Nsmf_EventExposure_subscribe request to the SMF, and the SMF completes the second event subscription , Return a second event subscription response such as Nsmf_EventExposure_subscribe response to UDM.
  • a second event subscription request such as Nsmf_EventExposure_subscribe request to the SMF.
  • the second event subscription request carries such as: NEF reference ID, subscription event type information (such as event identifier Event ID, subscription event type "availability after DDN failure", etc.), event notification endpoint information (such as NEF receiving Event notification address and other related information), AF identification and other information.
  • subscription event type information such as event identifier Event ID, subscription event type "availability after DDN failure", etc.
  • event notification endpoint information such as NEF receiving Event notification address and other related information
  • AF identification and other information carries such as: NEF reference ID, subscription event type information (such as event identifier Event ID, subscription event type "availability after DDN failure", etc.), event notification endpoint information (such as NEF receiving Event notification address and other related information), AF identification and other information.
  • Steps 706 to 707 UDM returns an event subscription response such as Nudm_EventExposure_subscribe response to NEF; NEF returns an event subscription response such as Nnef_EventExposure_subscribe response to AF.
  • the first event and the second event are associated through information such as NEF reference ID, AF identification, and UE identification.
  • FIG. 7 is only an example and is not used to limit the protection scope of the present application.
  • Fig. 8 is a schematic diagram of another flow of subscribing to the first event and the second event provided by this application, as shown in Fig. 8, including:
  • Step 800 AF sends an event subscription request such as Nnef_EventExposure_Subscribe request to NEF.
  • the Nnef_EventExposure_Subscribe request carries information such as: subscription event type one (such as "availability after DDN failure"), information used to identify AF (such as traffic descriptor, IP filter information, AF ID, etc.) that can uniquely identify the AF identity in the entire system. This may be referred to as AF identity), UE identity and other information.
  • subscription event type one such as "availability after DDN failure”
  • information used to identify AF such as traffic descriptor, IP filter information, AF ID, etc.
  • AF identity such as traffic descriptor, IP filter information, AF ID, etc.
  • the AF also needs to send an event subscription request to the NEF, as shown in step 800a: the AF sends an event subscription request to the NEF such as Nnef_EventExposure_Subscribe request, and the Nnef_EventExposure_Subscribe request carries such as: Subscription event type two (such as "Downlink data Delivery status"), information used to identify the AF (such as traffic descriptor, IP filter information, AF ID and other information that can uniquely identify the AF identity in the entire system, which may be referred to as the AF identity in this article) and other information.
  • Subscription event type two such as "Downlink data Delivery status”
  • information used to identify the AF such as traffic descriptor, IP filter information, AF ID and other information that can uniquely identify the AF identity in the entire system, which may be referred to as the AF identity in this article
  • Step 801 If NEF receives the event subscription request shown in step 800, NEF generates a subscription event identifier (NEF reference ID), and the NEF reference ID is associated with the AF identifier; NEF sends an event subscription request such as Nudm_EventExposure_subscribe request to UDM.
  • NEF reference ID a subscription event identifier
  • NEF sends an event subscription request such as Nudm_EventExposure_subscribe request to UDM.
  • Nudm_EventExposure_subscribe request carries such as: NEF reference ID, subscription event type information (such as event identifier Event ID, subscription event type "availability after DDN failure", etc.), event notification endpoint information (such as NEF receiving event notifications) Address and other related information) and other information.
  • subscription event type information such as event identifier Event ID, subscription event type "availability after DDN failure", etc.
  • event notification endpoint information such as NEF receiving event notifications
  • Address and other related information and other information.
  • NEF receives the event subscription request in step 800 and the subscription event type carried in the event subscription request is subscription event type one "availability after DDN failure" and the AF identifier, or the received step 800a
  • the NEF performs step 801a: NEF sends an event subscription request such as Npcf_EventExposure_subscribe request to the PCF.
  • Npcf_EventExposure_subscribe request carries such as: NEF reference ID, subscription event type information (such as event identifier Event ID, subscription event type two "Downlink data delivery status", etc.), event notification endpoint information (notification endpoint information) (such as NEF receiving event notifications) Address and other related information) and other information.
  • subscription event type information such as event identifier Event ID, subscription event type two "Downlink data delivery status", etc.
  • event notification endpoint information notification endpoint information
  • Address and other related information carries such as: NEF reference ID, subscription event type information (such as event identifier Event ID, subscription event type two "Downlink data delivery status", etc.), event notification endpoint information (notification endpoint information) (such as NEF receiving event notifications) Address and other related information) and other information.
  • Step 802 UDM sends a first event subscription request such as Namf_EventExposure_subscribe request to AMF, AMF completes the first event subscription, and returns a first event subscription response such as Namf_EventExposure_subscribe response to UDM.
  • a first event subscription request such as Namf_EventExposure_subscribe request
  • AMF completes the first event subscription
  • a first event subscription response such as Namf_EventExposure_subscribe response to UDM.
  • the first event subscription request carries such as: NEF reference ID, subscription event type information (such as event ID Event ID, event type "availability after DDN failure", etc.), event notification endpoint information (such as NEF receiving event notifications) Information such as the address and other related information), event monitoring object information (such as UE identification information) and other information.
  • subscription event type information such as event ID Event ID, event type "availability after DDN failure", etc.
  • event notification endpoint information such as NEF receiving event notifications
  • Information such as the address and other related information
  • event monitoring object information such as UE identification information
  • Step 803 The PCF sends a second event subscription request such as Nsmf_EventExposure_subscribe request to the SMF, the SMF completes the second event subscription, and returns a second event subscription response such as Nsmf_EventExposure_subscribe response to the UDM.
  • a second event subscription request such as Nsmf_EventExposure_subscribe request
  • the SMF completes the second event subscription
  • a second event subscription response such as Nsmf_EventExposure_subscribe response to the UDM.
  • the second event subscription request carries such as: NEF reference ID, subscription event type information (such as event identifier Event ID, subscription event type two "Downlink data delivery status", etc.), event notification endpoint information (such as NEF receiving Event notification address and other related information), AF identification and other information.
  • subscription event type information such as event identifier Event ID, subscription event type two "Downlink data delivery status", etc.
  • event notification endpoint information such as NEF receiving Event notification address and other related information
  • AF identification and other information carries such as: NEF reference ID, subscription event type information (such as event identifier Event ID, subscription event type two "Downlink data delivery status", etc.), event notification endpoint information (such as NEF receiving Event notification address and other related information), AF identification and other information.
  • Step 804 NEF returns an event subscription response such as Npcf_EventExposure_subscribe response to PCF.
  • Step 805 NEF returns an event subscription response such as Nudm_EventExposure_subscribe response to UDM.
  • Step 806 NEF returns an event subscription response such as Nnef_EventExposure_subscribe response to AF.
  • the first event and the second event are associated through information such as NEF reference ID, AF identification, and UE identification.
  • FIG. 7 is only an example and is not used to limit the protection scope of the present application.
  • FIG. 9 is a schematic flowchart of a second event notification provided by this application, as shown in FIG. 9, including:
  • Step 900 AF sends downlink data to UPF.
  • Step 901 UPF receives downlink data and performs data detection on the downlink data, such as which AF sent it; UPF sends a downlink data detection notification to SMF, and the downlink data detection notification can be the following data notification (Downlink Data Notification) or Sx report (Sx Report) or N4 report (N4Report).
  • Downlink Data Notification Downlink Data Notification
  • Sx Report Sx Report
  • N4Report N4 report
  • the detected AF identifier is also carried in the downlink data detection notification.
  • step 902 may also be included: the SMF requests the AMF to page the UE of the user, where the request message may be such as Namf_CommunicationN1N2MessageTransfer request.
  • Step 903 The UE is in an unreachable state, and the paging of the UE fails, that is, downlink data notification failure (DDN failure).
  • DDN failure downlink data notification failure
  • step 904 may be further included:
  • AMF reports to SMF that the UE is currently in an unreachable state, and the feedback message can be as follows: Namf_CommunicationN1N2MessageTransfer response.
  • step 905 may also be included:
  • the SMF requests the UPF to send downlink data detection information including the AF identifier; or, the SMF notifies the UPF to buffer the downlink data.
  • Step 906 When the SMF learns that the current status of the UE is unreachable, and receives the downlink data detection information from the UPF, it sends a second event (such as "availability after DDN failure") to the NEF through the NEF reference ID associated with the AF identifier, the second event
  • the notification can be like Nsmf_EventExposure_Notify, and the information carried in Nsmf_EventExposure_Notify includes: AF identification, or related information with AF identification such as NEF reference ID and other information; or, SMF detects that the downlink data status is cached, and SMF associates NEF reference ID through AF identification.
  • the second event notification may be Nsmf_EventExposure_Notify, and the information carried in Nsmf_EventExposure_Notify includes: AF identification, or related information with AF identification such as NEF reference ID and other information
  • NEF receives the second event notification from the SMF that carries the AF identifier or the associated information with the AF identifier, such as NEF reference ID, and sets the UE reachable message notification after the failure of the downlink data notification associated with the AF identifier (Notify-on-available-after -DDN-failure) identification, that is, to obtain AF information for sending downlink data.
  • the AF identifier Notify-on-available-after -DDN-failure
  • the Notify-on-available-after-DDN-failure flag is associated with the first event. In other words, if the Notify-on-available-after-DDN-failure flag is set, it means that the first event notification for the subsequent first event is required Sent to the associated AF.
  • Step 907 The UE status changes from unreachable to reachable.
  • Step 908 The AMF learns that the UE is reachable, and the AMF sends the first event notification to the NEF, such as Namf_EventExposure_Notify, which carries information such as NEF reference ID.
  • NEF such as Namf_EventExposure_Notify
  • Step 909 The NEF receives the first event notification from the AMF, and sends the first event notification to the associated AF, that is, the AF that sends the downlink data according to the set Notify-on-available-after-DDN-failure identifier.
  • Fig. 10 is a schematic diagram of another flow of subscribing to the first event and the second event provided by this application, as shown in Fig. 10, including:
  • Step 1000 AF sends an event subscription request such as Nnef_EventExposure_Subscribe request to NEF.
  • the Nnef_EventExposure_Subscribe request carries information such as: subscription event type one (such as "availability after DDN failure"), information used to identify AF (such as traffic descriptor, IP filter information, AF ID, etc.) that can uniquely identify the AF identity in the entire system. This may be referred to as AF identity), UE identity and other information.
  • subscription event type one such as "availability after DDN failure”
  • information used to identify AF such as traffic descriptor, IP filter information, AF ID, etc.
  • AF identity such as traffic descriptor, IP filter information, AF ID, etc.
  • Step 1001 NEF receives the event subscription request from the AF, and generates a subscription event identifier (NEF reference ID).
  • the NEF reference ID is associated with the AF identifier; NEF sends an event subscription request such as Nudm_EventExposure_subscribe request to UDM.
  • Nudm_EventExposure_subscribe request carries such as: NEF reference ID, subscription event type information (such as event identifier Event ID, subscription event type "availability after DDN failure", etc.), event notification endpoint information (such as NEF receiving event notifications) Address and other related information) and other information.
  • subscription event type information such as event identifier Event ID, subscription event type "availability after DDN failure", etc.
  • event notification endpoint information such as NEF receiving event notifications
  • Address and other related information and other information.
  • Steps 1002 to 1003 UDM sends a first event subscription request such as Namf_EventExposure_subscribe request to AMF, AMF completes the first event subscription, and returns a first event subscription response such as Namf_EventExposure_subscribe response to UDM.
  • a first event subscription request such as Namf_EventExposure_subscribe request
  • AMF completes the first event subscription
  • a first event subscription response such as Namf_EventExposure_subscribe response to UDM.
  • the first event subscription request carries such as: NEF reference ID, subscription event type information (such as event identifier Event ID, subscription event type "availability after DDN failure", etc.), event notification endpoint information (such as NEF receiving Event notification address and other relevant information), event monitoring object information (such as UE identification information) and other information.
  • subscription event type information such as event identifier Event ID, subscription event type "availability after DDN failure", etc.
  • event notification endpoint information such as NEF receiving Event notification address and other relevant information
  • event monitoring object information such as UE identification information
  • Step 1004 AMF sends a second event subscription request such as Nsmf_EventExposure_subscribe request to SMF, SMF completes the first event subscription, and returns a first event subscription response such as Nsmf_EventExposure_subscribe response to AMF.
  • a second event subscription request such as Nsmf_EventExposure_subscribe request
  • SMF completes the first event subscription
  • returns a first event subscription response such as Nsmf_EventExposure_subscribe response to AMF.
  • the second event subscription request carries such as: NEF reference ID, subscription event type information (such as event ID Event ID, subscription event type is subscription event type one "availability after DDN failure" or subscription event type two "Downlink data delivery status", etc. ), event notification endpoint information (such as related information such as the address at which the AMF receives event notifications), AF identification and other information.
  • subscription event type information such as event ID Event ID, subscription event type is subscription event type one "availability after DDN failure" or subscription event type two "Downlink data delivery status", etc.
  • event notification endpoint information such as related information such as the address at which the AMF receives event notifications
  • AF identification AF identification
  • FIG. 7 is only an example and is not used to limit the protection scope of the present application.
  • Fig. 11 is a schematic flowchart of another second event notification provided by this application, as shown in Fig. 11, including:
  • Step 1100 AF sends downlink data to UPF.
  • Step 1101 UPF receives the downlink data and performs data detection on the downlink data, such as which AF sent it; UPF sends a downlink data detection notification to SMF, and the downlink data detection notification can be the following data notification (Downlink Data Notification) or Sx report (Sx Report) or N4 report (N4Report).
  • the downlink data detection notification can be the following data notification (Downlink Data Notification) or Sx report (Sx Report) or N4 report (N4Report).
  • the detected AF identifier is also carried in the downlink data detection notification.
  • step 1102 may also be included: the SMF requests the AMF to page the UE of the user, where the request message may be such as: Namf_CommunicationN1N2MessageTransfer request.
  • Step 1103 The UE is in an unreachable state, and the paging of the UE fails, that is, the downlink data notification failure (DDN failure).
  • DDN failure downlink data notification failure
  • step 1104 may be further included:
  • AMF reports to SMF that the UE is currently in an unreachable state, and the feedback message can be as follows: Namf_CommunicationN1N2MessageTransfer response.
  • step 1105 may also be included:
  • the SMF requests the UPF to send downlink data detection information including the AF identifier; or, the SMF notifies the UPF to buffer the downlink data.
  • Step 1106 When the SMF learns that the current state of the UE is unreachable and receives the downlink data detection information from the UPF, the SMF sends a second event (such as "availability after DDN failure") notification to the AMF.
  • a second event such as "availability after DDN failure"
  • the second event notification can be Nsmf_EventExposure_Notify, Nsmf_EventExposure_Notify
  • the information carried in it includes: AF identification, or related information with AF identification such as NEF Reference ID; or SMF detects that the downlink data status is cached, SMF sends a second event (such as "Downlink data delivery status") to AMF Notification, the second event notification can be Nsmf_EventExposure_Notify, and Nsmf_EventExposure_Notify carries information such as an AF identifier.
  • the AMF receives the second event notification carrying the AF identifier from the SMF, and sets the UE reachable message notification (Notify-on-available-after-DDN-failure) identifier after the downlink data notification associated with the AF identifier fails, that is, Acquire AF information for sending downlink data.
  • the Notify-on-available-after-DDN-failure flag is associated with the first event. In other words, if the Notify-on-available-after-DDN-failure flag is set, it means that the first event notification for the subsequent first event is required Sent to the associated AF.
  • Step 1107 The UE status changes from unreachable to reachable.
  • Step 1108 The AMF learns that the UE is reachable, and the AMF sends the associated AF to the NEF according to the set Notify-on-available-after-DDN-failure flag, the first event notification of the AF that sends the downlink data, such as Namf_EventExposure_Notify, which carries NEF reference ID and other information.
  • the AMF learns that the UE is reachable, and the AMF sends the associated AF to the NEF according to the set Notify-on-available-after-DDN-failure flag, the first event notification of the AF that sends the downlink data, such as Namf_EventExposure_Notify, which carries NEF reference ID and other information.
  • Step 1109 NEF receives the first event notification from AMF, and forwards the first event notification to AF.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Computer And Data Communications (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Traffic Control Systems (AREA)
  • Debugging And Monitoring (AREA)
  • Computer Security & Cryptography (AREA)

Abstract

本文公开了一种事件通知方法、装置及存储介质。该方法包括：NEF根据来自SMF的第二事件通知，获取发送下行数据的AF信息；其中，第二事件为监控AF是否下发下行数据事件；第一事件为下行数据通知失败后UE可达事件；NEF接收来自AMF的第一事件通知，根据获得的发送下行数据的AF信息向发送下行数据的AF发送第一事件通知。

Description

事件通知方法、装置及存储介质
本申请要求在2019年03月28日提交中国专利局、申请号为201910241964.8的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信技术，例如涉及一种事件通知方法、装置及存储介质。
背景技术
通常，为了省电等原因，用户设备(User Equipment，UE)不会一直处于连接状态。应用功能(AF，Application Function)是不知道UE所处的状态如何的，因此，为了能有效地让AF向UE发送下行数据(DownLink data或DL data)，AF会在接入管理功能(AMF，Access Management Function)订阅下行数据通知失败后UE可达(UE availability after DDN failed)事件，这样，当UE状态从不可达(unreachability)变为可达(availability)时，AMF会经由网络暴露功能(NEF，Network Exposure Function)给所有订阅了上述UE availability after DDN failed事件的AF发送UE可达的通知消息，从而保证了AF在获知UE可达的情况下再向UE下发数据。大致过程包括：
假设一时刻一个AF发送DL data业务需求，用户面功能(UPF，User Plane Function)收到后会向AMF发送下行数据通知(DDN，Downlink Data Notify)消息，通知AMF有下行数据要发送，需要唤醒UE；如果AMF无法唤醒UE，则返回下行数据通知失败(DDN failure)响应；而当UE状态从不可达(unreachability)变为可达(availability)，AMF会给所有订阅了上述UE availability after DDN failed事件的AF发送UE可达的通知消息。
从相关技术提供的事件通知实现方式来看，当UE状态从不可达变为可达，AMF会给所有订阅了上述UE availability after DDN failed事件的AF发送UE可达的通知消息。但是，并不是所有AF都需要收到该UE可达的通知消息，因此，相关技术中的UE可达的事件通知方式造成了网络资源的浪费。
发明内容
本申请提供一种事件通知方法、装置及存储介质，能够避免对网络资源的浪费。
本申请提供了一种事件通知方法，包括：
网络暴露功能NEF根据来自会话管理功能SMF的第二事件通知，获取发送下行数据的应用功能AF信息；
NEF接收来自接入管理功能AMF的第一事件通知，根据获得的发送下行数据的AF信息向发送下行数据的AF发送第一事件通知；
其中，第二事件为监控AF是否下发下行数据事件；第一事件为下行数据通知失败后UE可达事件。
在一种示例性实例中，所述获取发送下行数据的AF信息，包括：
所述NEF接收来自所述SMF的携带有AF标识或与AF关联的标识的所述第二事件通知；
所述NEF根据收到的AF标识或与AF关联的标识，设置与该AF关联的下行数据通知失败后UE可达消息通知Notify-on-available-after-DDN-failure标识。
在一种示例性实例中，所述获取发送下行数据的AF信息之前，还包括：
所述NEF接收来自AF发送的事件订阅请求，所述NEF生成订阅事件标识NEF reference ID，其中，NEF reference ID与AF标识关联；
所述NEF向统一数据管理功能UDM发送事件订阅请求。
在一种示例性实例中，所述来自AF的事件订阅请求中携带的信息包括：订阅事件类型一、AF标识、UE标识；
所述NEF向UDM发送事件订阅请求中携带的信息包括：所述订阅事件标识NEF reference ID、订阅事件类型一、事件通知对象信息。
在一种示例性实例中，所述获取发送下行数据的AF信息之前，还包括：
所述NEF接收来自AF的携带有订阅事件类型一和AF标识的事件订阅请求，或者，所述NEF接收来自AF的携带有订阅事件类型二和AF标识的事件订阅请求；
所述NEF生成订阅事件标识NEF reference ID，其中，NEF reference ID与AF标识关联；
所述NEF向策略控制功能PCF发送事件订阅请求。
在一种示例性实例中，所述NEF向PCF发送的事件订阅请求中携带的信息包括：
所述订阅事件标识NEF reference ID、订阅事件类型二、事件通知对象信息。
在一种示例性实例中，所述订阅事件类型一包括：下行数据通知失败后UE可达性availability after DDN failure类型；
所述订阅事件类型二包括：下行数据传输状态downlink data delivery status类型。
本申请提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行上述任一项所述的一种事件通知方法。
本申请提供了一种实现事件通知的装置，包括处理器、存储器；其中，存储器上存储有可在处理器上运行的计算机程序：用于执行上述任一项所述的一种事件通知方法。
本申请提供了另一种事件通知方法，包括：
接入管理功能AMF根据来自会话管理功能SMF的第二事件通知，获取发送下行数据的应用功能AF信息；
AMF根据获得的发送下行数据的AF信息，经由网络暴露功能NEF向发送下行数据的AF发送第一事件通知；
其中，第二事件为监控AF是否下发下行数据事件；第一事件为下行数据通知失败后UE可达事件。
在一种示例性实例中，所述获取发送下行数据的AF信息，包括：
所述AMF接收来自所述SMF的携带有AF标识或与AF关联的标识的所述第二事件通知；
所述AMF根据收到的AF标识或与AF关联的标识，设置与该AF关联的下行数据通知失败后UE可达消息通知Notify-on-available-after-DDN-failure标识。
在一种示例性实例中，所述AMF经由NEF向发送下行数据的AF发送第一事件通知，包括：
当所述AMF检测到UE状态从不可达变为可达时，所述AMF根据所述下行数据通知失败后UE可达消息通知Notify-on-available-after-DDN-failure标识，经由所述NEF向发送下行数据的AF发送所述第一事件通知。
在一种示例性实例中，所述获取发送下行数据的AF信息之前，还包括：
所述AMF接收来自统一数据管理功能UDM的订阅所述第一事件的订阅第一事件请求，完成第一事件的订阅；
其中，订阅第一事件请求中携带的信息包括：NEF参考标识NEF reference ID、订阅事件类型一、事件通知对象信息、事件监控对象信息。
本申请提供了一种计算机可读存储介质，存储有计算机可执行指令，所述 计算机可执行指令用于执行上述任一项所述的另一种事件通知方法。
本申请提供了一种实现事件通知的装置，包括处理器、存储器；其中，存储器上存储有可在处理器上运行的计算机程序：用于执行上述任一项所述的另一种事件通知方法。
本申请提供了一种事件通知装置，包括：关联模块、第一通知模块；其中，
关联模块，用于根据来自会话管理功能SMF的第二事件通知，获取发送下行数据的应用功能AF信息；其中，第二事件为监控AF是否下发下行数据事件；第一事件为下行数据通知失败后UE可达事件；
第一通知模块，用于根据获得的发送下行数据的AF信息向发送下行数据的AF发送第一事件通知。
在一种示例性实例中，所述关联模块中的获取发送下行数据的AF信息，包括：
接收来自所述SMF的携带有AF标识或与AF关联的标识的所述第二事件通知；根据收到的AF标识或与AF关联的标识，设置与该AF关联的下行数据通知失败后UE可达消息通知Notify-on-available-after-DDN-failure标识。
在一种示例性实例中，所述事件通知装置设置在网络暴露功能NEF中，或者所述事件通知装置为NEF。
在一种示例性实例中，所述第一通知模块用于：接收来自接入管理功能AMF的第一事件通知，根据所述发送下行数据的AF信息向发送下行数据的AF发送所述第一事件通知。
在一种示例性实例中，所述事件通知装置设置在AMF中，或者所述事件通知装置为AMF。
在一种示例性实例中，所述第一通知模块用于：根据获得的发送下行数据的AF信息，经由网络暴露功能NEF向发送下行数据的AF发送所述第一事件通知。
本申请提供了又一种事件通知方法，包括：
会话管理功能SMF接收到第二事件订阅请求，完成第二事件的订阅；其中，第二事件为监控AF是否下发下行数据事件；
当应用功能AF向UE发送下行数据但UE状态为不可达时，SMF向网络暴露功能NEF或接入管理功能AMF发送第二事件通知；
其中，第二事件通知用于通知NEF或AMF下发下行数据的AF信息。
在一种示例性实例中，所述SMF接收到第二事件订阅请求，完成第二事件的订阅，包括：
所述SMF接收来自统一数据管理功能UDM的第二事件订阅请求，完成第二事件的订阅；其中，第二事件订阅请求中携带的信息包括：订阅事件类型一、设置为NEF相关地址的事件通知对象信息、AF标识。
在一种示例性实例中，所述SMF接收到第二事件订阅请求，完成第二事件的订阅，包括：
所述SMF接收来自所述AMF的第二事件订阅请求，完成第二事件的订阅；其中，第二事件订阅请求中携带的信息包括：订阅事件类型一或订阅事件类型二、设置为AMF相关地址的事件通知对象信息、AF标识。
在一种示例性实例中，所述SMF接收到第二事件订阅请求，完成第二事件的订阅，包括：
所述SMF接收来自策略控制功能PCF的第二事件订阅请求，完成第二事件的订阅；其中，第二事件订阅请求中携带的信息包括：订阅事件类型二、设置为NEF相关地址的事件通知对象信息、AF标识。
在一种示例性实例中，所述订阅事件类型一包括：下行数据通知失败后UE可达性availability after DDN failure类型；
所述订阅事件类型二包括：下行数据传输状态downlink data delivery status类型。
在一种示例性实例中，所述SMF向NEF或AMF发送第二事件通知，包括：
当所述SMF获知UE当前状态不可达，并收到来自用户面功能UPF的下行数据检测信息，所述SMF根据所述下行数据检测信息包含的AF标识获取所述AF标识关联的订阅事件；所述SMF根据AF标识关联的订阅事件的通知对象信息向所述NEF或所述AMF发送携带有AF标识或与AF关联的标识的第二事件通知；或者，
所述SMF检测到所述AF的下行数据状态为缓存状态，所述SMF根据所述AF标识获取所述AF标识关联的订阅事件；所述SMF根据AF标识关联的订阅事件的通知对象信息向所述NEF或所述AMF发送携带有AF标识或与AF关联的标识的第二事件通知。
在一种示例性实例中，所述SMF向NEF或AMF发送第二事件通知之前，还包括：
所述SMF向UPF请求发送包括AF标识的下行数据检测信息；或者，
所述SMF通知UPF进行下行数据缓存。
本申请提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行上述任一项所述的又一种事件通知方法。
本申请提供了一种实现事件通知的装置，包括处理器、存储器；其中，存储器上存储有可在处理器上运行的计算机程序：用于执行上述任一项所述的又一种事件通知方法。
本申请提供了一种事件通知装置，包括：处理模块、第二通知模块；其中，
处理模块，用于接收到第二事件订阅请求，完成第二事件的订阅；其中，第二事件为监控AF是否下发下行数据事件；
第二通知模块，用于当应用功能AF向UE发送下行数据但UE状态为不可达时，向暴露功能NEF或接入管理功能AMF发送第二事件通知；其中，第二事件通知用于通知NEF或AMF下发下行数据的AF信息。
在一种示例性实例中，所述事件通知装置设置在会话管理功能SMF中，或者所述事件通知装置为SMF。
在一种示例性实例中，所述处理模块具体用于：
接收来自统一数据管理功能UDM的第二事件订阅请求，完成第二事件的订阅；其中，第二事件订阅请求中携带的信息包括：订阅事件类型一、设置为NEF相关地址的事件通知对象信息、AF标识；或者，
接收来自所述AMF的第二事件订阅请求，完成第二事件的订阅；其中，第二事件订阅请求中携带的信息包括：订阅事件类型一或订阅事件类型二、设置为AMF相关地址的事件通知对象信息、AF标识。
在一种示例性实例中，所述第二通知模块具体用于：
当获知所述UE当前状态不可达，并收到来自用户面功能UPF的下行数据检测信息，根据所述下行数据检测信息包含的AF标识获取所述AF标识关联的订阅事件；根据AF标识关联的订阅事件的通知对象信息向所述NEF或所述AMF发送携带有AF标识或与AF关联的标识的第二事件通知；或者，
检测到所述AF的下行数据状态为缓存状态，通过所述AF标识获取所述AF标识关联的订阅事件；根据AF标识关联的订阅事件的通知对象信息向所述NEF或所述AMF发送携带有AF标识或与AF关联的标识的所述第二事件通知。
在一种示例性实例中，所述第二通知模块还用于：向UPF请求发送包括AF标识的下行数据检测信息；或者，通知UPF进行下行数据缓存。
本申请提供的一种事件通知方法包括：NEF根据来自SMF的第二事件通知， 获取发送下行数据的AF信息；其中，第二事件为监控AF是否下发下行数据事件；第一事件为下行数据通知失败后UE可达事件；NEF接收来自AMF的第一事件通知，根据获得的发送下行数据的AF信息向发送下行数据的AF发送第一事件通知。本申请通过第二事件通知获知发送下行数据的AF信息，从而确保了第一事件通知发送给了需要的AF，避免了对网络资源的浪费。
本申请提供的另一种事件通知方法包括：AMF根据来自SMF的第二事件通知，获取发送下行数据的AF信息；其中，第二事件为监控AF是否下发下行数据事件；第一事件为下行数据通知失败后UE可达事件；AMF根据获得的发送下行数据的AF信息，经由NEF向发送下行数据的AF发送第一事件通知。本申请通过第二事件通知获知发送下行数据的AF信息，从而确保了第一事件通知发送给了需要的AF，避免了对网络资源的浪费。
本申请提供的又一种事件通知方法包括：SMF接收到第二事件订阅请求，完成第二事件的订阅；其中，第二事件为为监控AF是否下发下行数据事件；当AF向UE发送下行数据但UE状态为不可达时，SMF向NEF或AMF发送第二事件通知。本申请通过第二事件通知获知发送下行数据的AF信息，从而确保了后续第一事件通知发送给了需要的AF，避免了对网络资源的浪费。
附图说明
图1为相关技术中下一代无线接入网络的组成架构示意图；
图2为本申请一实施例提供的一种事件通知方法的流程示意图；
图3为本申请一实施例提供的另一种事件通知方法的流程示意图；
图4为本申请一实施例提供的一种事件通知装置的组成结构示意图；
图5为本申请一实施例提供的又一种事件通知方法的流程示意图；
图6为本申请一实施例提供的另一种事件通知装置的组成结构示意图；
图7为本申请一实施例提供的一种订阅第一事件和第二事件的流程示意图；
图8为本申请一实施例提供的另一种订阅第一事件和第二事件的流程示意图；
图9为本申请一实施例提供的一种第二事件通知的流程示意图；
图10为本申请一实施例提供的又一种订阅第一事件和第二事件的流程示意图；
图11为本申请一实施例提供的另一种第二事件通知的流程示意图。
具体实施方式
在本申请的实施方式中，计算设备包括一个或多个中央处理器(Central Processing Unit，CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(Random Access Memory，RAM)和/或非易失性内存等形式，如只读存储器(Read-Only Memory，ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(Phase Change RAM，PRAM)、静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(Compact Disc-ROM，CD-ROM)、数字多功能光盘(Digital Video Disc，DVD)或其他光学存储、磁盒式磁带，磁带磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括非暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
下文中将结合附图对本申请的实施例进行说明。
为了保持第三代移动通信系统在通信领域的竞争力，为用户提供速率更快、时延更低、更加个性化的移动通信服务，同时，降低运营商的运营成本，第三代合作伙伴计划(3GPP，3rd Generation Partnership Project)标准工作组正致力于下一代无线移动接入网络的研究。下一代无线接入网络支持多种无线网络接入统一的核心网，并且希望无线接入网(RAN，Radio Access Network)和核心网(CN，Core Network)尽量减少耦合关系，即不管终端从什么接入技术的RAN接入，都可以接入到统一的CN中。下一代无线接入网络的核心网功能为了支持更加灵活的部署方式，支持基于服务的接口。图1为相关技术中下一代无线接入网络的组成架构示意图，如图1所示，主要的网络功能(NF，Network Funtion)介绍如下：
接入管理功能(AMF，Access Management Function)属于核心网内的公共控制面功能，终结所有用户与网络之间的非接入层(Non-Access Stratum，NAS)消息。一个用户UE只有一个AMF，用于实现用户移动性管理、UE状态(如可达性)管理等。会话管理功能(SMF，Session Management Function)，用于会 话建立、修改、删除，策略控制功能(PCF，Policy Control Function)收费和策略的执行等功能。PCF，用于根据用户的签约、UE当前的位置、应用相关的信息为终端制定策略，包括路由策略、服务质量策略、计费策略等。统一数据管理功能(UDM，Unified Data Management)可以用于如用户签约数据的永久存放等数据统一管理的功能。统一数据存储(UDR，Unified Data Repository)，主要用于存储UDM和PCF管理的用户签约数据、策略数据等。核心网内的用户面功能(UPF，User Plane Function)是核心网用户面的锚点，是与外部数据网络(DN，Data Network)进行数据传输的接口，执行用户面部分PCF策略规则的执行等。网络暴露功能(NEF，Network Exposure Function)用于暴露3GPP NFs的能力和事件给其他NF或者外部应用功能(AF，Application Function)，提供AF预配置3GPP NFs能力，实现3GPP网络和外部网络信息映射等。其中，AF指接入3GPP的应用，DN指接入3GPP的数据网络。
图2为本申请提供的一种事件通知方法的流程示意图，如图2所示，包括：
步骤200：NEF根据来自SMF的第二事件通知，获取发送下行数据的AF信息；其中，第二事件为监控AF是否下发下行数据事件；第一事件为下行数据通知失败后UE可达(UE availability after DDN failed)事件。
在一种示例性实例中，当AF向UE发送下行数据但UE状态为不可达时，SMF会向NEF发送第二事件通知，以通知NEF将第一事件和与需要接收第一事件通知的AF之间关联起来，即确定哪些AF需要接收第一事件通知。
在一种示例性实例中，本步骤中的获取发送下行数据的AF信息，包括：
NEF接收来自SMF的携带有AF标识或与AF关联的标识的第二事件通知；NEF根据收到的AF标识或与AF关联的标识，设置与AF标识关联的下行数据通知失败后UE可达消息通知(Notify-on-available-after-DDN-failure)标识，也就是说，Notify-on-available-after-DDN-failure标识与所述AF是关联的。
这里，Notify-on-available-after-DDN-failure标识与第一事件关联，换句话说，如果设置了Notify-on-available-after-DDN-failure标识，则表示后续第一事件的第一事件通知需要发送给关联的AF。
在一种示例性实例中，本步骤之前还可以包括：
NEF接收来自AF发送的事件订阅请求如Nnef_EventExposure_Subscribe request，NEF生成订阅事件标识(NEF参考标识(NEF reference Identifier，NEF reference ID))，NEF reference ID与AF标识是关联的；其中，来自AF的事件订阅请求中携带的信息包括如：订阅事件类型一(如下行数据通知失败后UE可达“availability after DDN failure”)、用于标识AF的信息(比如：通信量描 述符(traffic descriptor)、网际互连协议协议筛选器信息(Internet Protocol filter information，IP filter information)、AF ID等可以在整个系统中唯一标识AF身份的信息，这样的信息在本文中也可以称为AF标识)、UE标识等信息。
NEF向UDM发送事件订阅请求如Nudm_EventExposure_subscribe request，来自NEF的事件订阅请求中携带的信息包括如：NEF reference ID、订阅事件类型信息(比如事件标识Event ID、订阅事件类型一“availability after DDN failure”等)、事件通知对象信息(notification endpoint information)(比如NEF接收事件通知的地址等相关信息)等信息。
在一种示例性实例中，本步骤之前还可以包括：
NEF接收来自AF发送的事件订阅请求如Nnef_EventExposure_Subscribe request，其中，来自AF的事件订阅请求中携带的信息包括如：订阅事件类型一(如DDN失败后UE可达“availability after DDN failure”类型)、用于标识AF的信息(比如：traffic descriptor、IP filter information、AF ID等可以在整个系统中唯一标识AF身份的信息，这样的信息在本文中也可以称为AF标识)、UE标识等信息；或者，NEF接收来自AF发送的事件订阅请求如Nnef_EventExposure_Subscribe request，其中，来自AF的事件订阅请求中携带的信息包括如：订阅事件类型二(如下行数据传输状态“Downlink data delivery status”类型)、用于标识AF的信息(比如：traffic descriptor、IP filter information、AF ID等可以在整个系统中唯一标识AF身份的信息，这样的信息在本文中也可以称为AF标识)、UE标识等信息。
NEF生成订阅事件标识(NEF reference ID)，NEF reference ID与AF标识关联。
NEF向PCF发送事件订阅请求如Npcf_EventExposure_subscribe request，来自NEF的事件订阅请求中携带的信息包括如：NEF reference ID、订阅事件类型信息(比如事件标识Event ID、订阅事件类型二“Downlink data delivery status”等)、事件通知对象信息(notification endpoint information)(比如NEF接收事件通知的地址等相关信息)等信息。
NEF可以接收来自PCF的事件订阅响应。
在一种示例性实例中，NEF向AF返回事件订阅响应。
不同的订阅事件类型执行不同的动作。
步骤201：NEF接收来自AMF的第一事件通知，根据获得的发送下行数据的AF信息向发送下行数据的AF发送第一事件通知。
在一种示例性实例中，当AMF检测到UE状态从不可达变为可达时，会向 NEF发送第一事件通知。
本发明实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行与上述图2相关实施例的任一项所述的事件通知方法。
本发明实施例还提供一种实现事件通知的装置，包括处理器、存储器；其中，存储器上存储有可在处理器上运行的计算机程序：用于执行上述与上述图2相关实施例的任一项事件通知方法的步骤。
图3为本申请提供的另一种事件通知方法的流程示意图，如图3所示，包括：
步骤300：AMF根据来自SMF的第二事件通知，获取发送下行数据的AF信息；其中，第二事件为监控AF是否下发下行数据事件；第一事件为下行数据通知失败后UE可达(UE availability after DDN failed)事件。
在一种示例性实例中，当AF向UE发送下行数据但UE状态为不可达时，SMF会向AMF发送第二事件通知，以通知AMF将第一事件和与需要接收第一事件通知的AF之间关联起来，即确定哪些AF需要接收第一事件通知。
在一种示例性实例中，本步骤中的获取发送下行数据的AF，包括：
AMF接收来自SMF的携带有AF标识或与AF关联的标识的第二事件通知；AMF根据收到的AF标识或与AF关联的标识，设置与该AF关联的下行数据通知失败后UE可达消息通知(Notify-on-available-after-DDN-failure)标识。
这里，Notify-on-available-after-DDN-failure标识与第一事件关联，换句话说，如果设置了Notify-on-available-after-DDN-failure标识，则表示后续第一事件的第一事件通知需要发送给关联的AF。
在一种示例性实例中，本步骤之前还可以包括：
AMF接收来自SMF的寻呼UE的请求并对UE进行寻呼(Namf_CommunicationN1N2MessageTransfer request)；在UE状态为不可达时，AMF向SMF反馈UE当前处于不可达状态的响应消息(Namf_CommunicationN1N2MessageTransfer response)。
在一种示例性实例中，本步骤之前还包括：
AMF接收来自UDM的订阅第一事件请求，完成第一事件的订阅。订阅第一事件请求中携带的信息包括如：NEF参考标识(NEF reference ID)、订阅事件类型信息(比如：事件标识(Event ID)、订阅事件类型一如“availability after DDN failure”等)、事件通知对象信息(notification endpoint information)(比 如接收第一事件通知的NEF的地址等相关信息)、事件监控对象信息(比如UE标识信息)等信息。
AMF可以向UDM返回第一事件订阅响应。
步骤301：AMF根据获得的发送下行数据的AF信息，经由NEF向发送下行数据的AF发送第一事件通知。
在一种示例性实例中，本步骤可以包括：
当AMF检测到UE状态从不可达变为可达时，AMF根据设置的Notify-on-available-after-DDN-failure标识，经由NEF向与Notify-on-available-after-DDN-failure标识关联的AF发送第一事件通知。
本发明实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行与上述图3相关实施例的任一项所述的事件通知方法。
本发明实施例还提供一种实现事件通知的装置，包括处理器、存储器；其中，存储器上存储有可在处理器上运行的计算机程序：用于执行上述与上述图3相关实施例的任一项事件通知方法的步骤。
图4为本申请提供的一种事件通知装置的组成结构示意图，如图4所示，至少包括关联模块、第一通知模块；其中，
关联模块，用于根据来自SMF的第二事件通知，获取发送下行数据的AF信息；其中，第二事件为监控AF是否下发下行数据事件；第一事件为下行数据通知失败后UE可达(UE availability after DDN failed)事件；第一通知模块，用于根据获得的发送下行数据的AF信息向发送下行数据的AF发送第一事件通知。
在一种示例性实例中，关联模块中的获取发送下行数据的AF信息，包括：
接收来自SMF的携带有AF标识或与AF关联的标识的第二事件通知；根据收到的AF标识或与AF关联的标识，设置与该AF关联的下行数据通知失败后UE可达消息通知(Notify-on-available-after-DDN-failure)标识。
本申请事件通知装置可以设置在NEF中或者可以为NEF，这种情况下：
在一种示例性实例中，第一通知模块用于：接收来自AMF的第一事件通知，根据所述发送下行数据的AF信息向发送下行数据的AF发送第一事件通知。
本申请事件通知装置可以设置在AMF中或者可以为AMF，这种情况下：
在一种示例性实例中，第一通知模块用于：根据所述发送下行数据的AF信息经由NEF向发送下行数据的AF发送第一事件通知。
图5为本申请提供的又一种事件通知方法的流程示意图，如图5所示，包括：
步骤500：SMF接收到第二事件订阅请求，完成第二事件的订阅；其中，第二事件为监控AF是否下发下行数据事件。
在一种示例性实例中，本步骤可以包括：
SMF接收来自UDM的第二事件订阅请求，在第二事件订阅请求中携带的信息包括如：订阅事件类型信息(比如：事件标识(Event ID)、订阅事件类型一“availability after DDN failure”等)、事件通知对象信息(notification endpoint information)(比如：接收第二事件通知的NEF的地址等相关信息)、AF标识等信息。第二事件订阅请求中还携带有：NEF参考标识(NEF reference ID)。
在一种示例性实例中，本步骤可以包括：
SMF接收来自AMF的第二事件订阅请求，在第二事件订阅请求中携带的信息包括如：订阅事件类型信息(比如：事件标识(Event ID)、订阅事件类型一“availability after DDN failure”或订阅事件类型二“Downlink data delivery status”等)、事件通知对象信息(notification endpoint information)(比如：接收第二事件通知的AMF的地址等相关信息)、AF标识等信息。
在一种示例性实例中，本步骤可以包括：
SMF接收来自PCF的第二事件订阅请求，在第二事件订阅请求中携带的信息包括如：订阅事件类型信息(比如：事件标识(Event ID)、订阅事件类型二“Downlink data delivery status”等)、事件通知对象信息(notification endpoint information)(比如：接收第二事件通知的NEF的地址等相关信息)、AF标识等信息。
步骤501：当AF向UE发送下行数据但UE状态为不可达时，SMF向NEF或AMF发送第二事件通知。
第二事件通知，用于通知NEF或AMF下发下行数据的AF信息，即确定哪些AF需要接收第一事件通知。
在一种示例性实例中，本步骤可以包括：
当SMF获知UE当前状态不可达，并收到来自UPF的下行数据检测信息，SMF根据所述下行数据检测信息包含的AF标识获取所述AF标识关联的订阅事件；SMF根据AF标识关联的订阅事件的通知对象信息向NEF发送第二事件(如“availability after DDN failure”)通知，如Nsmf_EventExposure_Notify，在Nsmf_EventExposure_Notify中携带的信息包括：AF标识，或与AF标识关联的 信息如NEF reference ID等信息；或者，
SMF检测到所述AF的下行数据状态为缓存状态，SMF根据AF标识获取所述AF标识关联的订阅事件；SMF根据AF标识关联的订阅事件的通知对象信息向NEF发送第二事件(如“Downlink data delivery status”)通知，如Nsmf_EventExposure_Notify，在Nsmf_EventExposure_Notify中携带的信息包括如：AF标识，或与AF标识关联的信息如NEF reference ID等信息。
在一种示例性实例中，本步骤可以包括：
当SMF获知UE当前状态不可达，并收到UPF发送的下行数据检测信息，SMF根据所述下行数据检测信息包含的AF标识获取所述AF标识关联的订阅事件；SMF根据AF标识关联的订阅事件的通知对象信息向AMF发送第二事件(如“availability after DDN failure”)通知，如Nsmf_EventExposure_Notify，在Nsmf_EventExposure_Notify中携带的信息包括如：AF标识，或与AF标识关联的信息如NEF reference ID等信息；或者，
SMF检测到所述AF的下行数据状态为缓存状态，SMF根据所述AF标识获取所述AF标识关联的订阅事件；SMF根据AF标识关联的订阅事件的通知对象信息向AMF发送第二事件(如“Downlink data delivery status”)通知，如Nsmf_EventExposure_Notify，在Nsmf_EventExposure_Notify中携带有如AF标识或AF标识关联的信息如NEF reference ID等信息。
在一种示例性实例中，如果SMF不知道该用户处于不可达状态，那么，本步骤之前还可以包括：
SMF向AMF发送寻呼该用户的UE请求(Namf_CommunicationN1N2MessageTransfer request)以寻呼该UE；AMF接收来自SMF的UE当前处于不可达状态的响应消息(Namf_CommunicationN1N2MessageTransfer response)。
在一种示例性实例中，如果SMF知道UE当前状态不可达，但是UPF没有告知SMF当前发送下行数据的AF标识，那么，本步骤之前还可以包括：
SMF向UPF请求发送包括AF标识的下行数据检测信息；或者，SMF通知UPF进行下行数据缓存。
在一种示例性实例中，SMF向UPF请求发送包括AF标识的下行数据检测信息，包括：
SMF向UPF发送下行数据检测信息请求；SMF接收来自UPF的下行数据检测信息响应，下行数据检测信息响应可以为如：下行数据通知(Downlink Data Notification)、或Sx Report、或N4Report。
UPF在接收到来自AF下发的下行数据后，会进行下行数据进行检测，比如检测是来自于哪个AF的下行数据，也就是说可以检测出发送下行数据的AF的AF标识。
本发明实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行与上述图5相关实施例的任一项所述的事件通知方法。
本发明实施例还提供一种实现事件通知的装置，包括处理器、存储器；其中，存储器上存储有可在处理器上运行的计算机程序：用于执行上述与上述图5相关实施例的任一项事件通知方法的步骤。
图6为本申请提供的另一种事件通知装置的组成结构示意图，如图6所示，至少包括：处理模块、第二通知模块；其中，
处理模块，用于接收到第二事件订阅请求，完成第二事件的订阅；其中，第二事件为监控AF是否下发下行数据事件；第二通知模块，用于当AF向UE发送下行数据但UE状态为不可达时，向NEF或AMF发送第二事件通知；其中，第二事件通知用于通知NEF或AMF下发下行数据的AF信息。
本申请事件通知装置可以设置在SMF中或者可以为SMF。
在一种示例性实例中，第二通知模块具体用于：
当获知UE当前状态不可达，并收到来自UPF的下行数据检测信息，向NEF发送第二事件通知，第二事件通知中携带的信息包括如：AF标识、或与AF标识关联的标识如NEF reference ID等信息；或者，
检测到下行数据状态为缓存状态，向NEF发送第二事件通知，第二事件通知中携带的信息包括：AF标识、或与AF关联的标识如NEF reference ID等信息。
在一种示例性实例中，第二通知模块具体用于：
当获知UE当前状态不可达，并收到UPF发送的下行数据检测信息，向AMF发送第二事件通知，第二事件通知中携带的信息包括：AF标识、或与AF关联的标识如NEF reference ID等信息；或者，
检测到下行数据状态为缓存状态，向AMF发送第二事件通知，第二事件通知中携带的信息包括：AF标识、或与AF关联的标识如NEF reference ID等信息。
在一种示例性实例中，如果SMF知道UE当前状态不可达，但是UPF没有告知SMF当前发送下行数据的AF标识，第二通知模块还用于：
向UPF请求发送包括AF标识的下行数据检测信息；或者，通知UPF进行下行数据缓存。
下面结合具体实施例对本申请进行描述。
图7为本申请提供的一种订阅第一事件和第二事件的流程示意图，如图7所示，包括：
步骤700：AF向NEF发送事件订阅请求如Nnef_EventExposure_Subscribe request。
Nnef_EventExposure_Subscribe request中携带有如：事件类型(如“availability after DDN failure”)、用于标识AF的信息(如traffic descriptor、IP filter information、AF ID等可以在整个系统中唯一标识AF身份的信息，在本文可以称为AF标识)、UE标识等信息。
步骤701：NEF收到来自AF的事件订阅请求，生成订阅事件标识(NEF reference ID)，该NEF reference ID与AF标识关联；NEF向UDM发送事件订阅请求如Nudm_EventExposure_subscribe request。
Nudm_EventExposure_subscribe request中携带有如：NEF reference ID、订阅事件类型信息(如事件标识Event ID、事件类型“availability after DDN failure”等)、事件通知对象信息(notification endpoint information)(如NEF接收事件通知的地址等相关信息)等信息。
步骤702～步骤703：UDM向AMF发送第一事件订阅请求如Namf_EventExposure_subscribe request，AMF完成第一事件订阅，向UDM返回第一事件订阅响应如Namf_EventExposure_subscribe reponse。
第一事件订阅请求中携带有如：NEF reference ID、订阅事件类型信息(如事件标识Event ID、订阅事件类型一“availability after DDN failure”等)、事件通知对象信息(notification endpoint information)(如NEF接收事件通知的地址等相关信息)、事件监控对象信息(如UE标识信息)等信息。
步骤704～步骤705：如果UDM收到NEF的订阅事件请求消息携带订阅事件类型一“availability after DDN failure”和AF标识，UDM向SMF发送第二事件订阅请求如Nsmf_EventExposure_subscribe request，SMF完成第二事件订阅，向UDM返回第二事件订阅响应如Nsmf_EventExposure_subscribe reponse。
第二事件订阅请求中携带有如：NEF reference ID、订阅事件类型信息(如事件标识Event ID、订阅事件类型一“availability after DDN failure”等)、事件通知对象信息(notification endpoint information)(如NEF接收事件通知的地址等相关信息)、AF标识等信息。
步骤706～步骤707：UDM向NEF返回事件订阅响应如Nudm_EventExposure_subscribe response；NEF向AF返回事件订阅响应如Nnef_EventExposure_subscribe response。
本实施例中所示的第一事件和第二事件的订阅过程，通过如NEF reference ID、AF标识、UE标识等信息，将第一事件和第二事件关联了起来。
第一事件的订阅和第二事件的订阅没有严格的先后顺序，图7中仅仅是一个示例，并不用于限定本申请的保护范围。
实施例中去订阅(unsubscribe)或者修改订阅的过程，与上述订阅(subscribe)的过程类似，这里不再赘述。
图8为本申请提供的另一种订阅第一事件和第二事件的流程示意图，如图8所示，包括：
步骤800：AF向NEF发送事件订阅请求如Nnef_EventExposure_Subscribe request。
Nnef_EventExposure_Subscribe request中携带有如：订阅事件类型一(如“availability after DDN failure”)、用于标识AF的信息(如traffic descriptor、IP filter information、AF ID等可以在整个系统中唯一标识AF身份的信息，在本文可以称为AF标识)、UE标识等信息。
在一种示例性实例中，AF还需要向NEF发送事件订阅请求，如步骤800a所示：AF向NEF发送事件订阅请求如Nnef_EventExposure_Subscribe request，Nnef_EventExposure_Subscribe request中携带有如：订阅事件类型二(如“Downlink data delivery status”)、用于标识AF的信息(如traffic descriptor、IP filter information、AF ID等可以在整个系统中唯一标识AF身份的信息，在本文可以称为AF标识)等信息。
步骤801：如果NEF收到步骤800所示的事件订阅请求，NEF生成订阅事件标识(NEF reference ID)，该NEF reference ID与AF标识关联；NEF向UDM发送事件订阅请求如Nudm_EventExposure_subscribe request。
Nudm_EventExposure_subscribe request中携带有如：NEF reference ID、订阅事件类型信息(如事件标识Event ID、订阅事件类型一“availability after DDN failure”等)、事件通知对象信息(notification endpoint information)(如NEF接收事件通知的地址等相关信息)等信息。
在一种示例性实例中，如果NEF收到步骤800的事件订阅请求且事件订阅请求中携带的订阅事件类型为订阅事件类型一“availability after DDN failure”和AF标识，或收到步骤800a所示的事件订阅请求，则NEF执行步骤801a：NEF 向PCF发送事件订阅请求如Npcf_EventExposure_subscribe request。
Npcf_EventExposure_subscribe request中携带如：NEF reference ID、订阅事件类型信息(如事件标识Event ID、订阅事件类型二“Downlink data delivery status”等)、事件通知对象信息(notification endpoint information)(如NEF接收事件通知的地址等相关信息)等信息。
步骤802：UDM向AMF发送第一事件订阅请求如Namf_EventExposure_subscribe request，AMF完成第一事件订阅，向UDM返回第一事件订阅响应如Namf_EventExposure_subscribe reponse。
第一事件订阅请求中携带有如：NEF reference ID、订阅事件类型信息(如事件标识Event ID、事件类型“availability after DDN failure”等)、事件通知对象信息(notification endpoint information)(如NEF接收事件通知的地址等相关信息)、事件监控对象信息(如UE标识信息)等信息。
步骤803：PCF向SMF发送第二事件订阅请求如Nsmf_EventExposure_subscribe request，SMF完成第二事件订阅，向UDM返回第二事件订阅响应如Nsmf_EventExposure_subscribe reponse。
第二事件订阅请求中携带有如：NEF reference ID、订阅事件类型信息(如事件标识Event ID、订阅事件类型二“Downlink data delivery status”等)、事件通知对象信息(notification endpoint information)(如NEF接收事件通知的地址等相关信息)、AF标识等信息。
步骤804：NEF向PCF返回事件订阅响应如Npcf_EventExposure_subscribe response。
步骤805：NEF向UDM返回事件订阅响应如Nudm_EventExposure_subscribe response。
步骤806：NEF向AF返回事件订阅响应如Nnef_EventExposure_subscribe response。
本实施例中所示的第一事件和第二事件的订阅过程，通过如NEF reference ID、AF标识、UE标识等信息，将第一事件和第二事件关联了起来。
第一事件的订阅和第二事件的订阅没有严格的先后顺序，图7中仅仅是一个示例，并不用于限定本申请的保护范围。
实施例中去订阅(unsubscribe)或者修改订阅的过程，与上述订阅(subscribe)的过程类似，这里不再赘述。
图9为本申请提供的一种第二事件通知的流程示意图，如图9所示，包括：
步骤900：AF发送下行数据到UPF。
步骤901：UPF收到下行数据，对下行数据进行数据检测，比如检测是哪个AF发送的等；UPF向SMF发送下行数据检测通知，下行数据检测通知可以为如下行数据通知(Downlink Data Notification)或Sx报告(Sx Report)或N4报告(N4Report)。
在一种示例性实例中，在下行数据检测通知中还携带有检测出的AF标识。
在一种示例性实例中，如果SMF不知道该用户处于不可达状态，还可以包括步骤902：SMF请求AMF寻呼该用户的UE，其中，请求消息可以如：Namf_CommunicationN1N2MessageTransfer request。
步骤903：UE处于不可达状态，对UE的寻呼失败，即下行数据通知失败(DDN failure)。
在一种示例性实例中，还可以包括步骤904：
AMF向SMF反馈UE当前处于不可达状态，反馈消息可以如：Namf_CommunicationN1N2MessageTransfer response。
在一种示例性实例中，如果SMF知道UE当前状态不可达，但是UPF没有告知SMF当前发送下行数据的AF标识，还可以包括步骤905：
SMF向UPF请求发送包括AF标识的下行数据检测信息；或者，SMF通知UPF进行下行数据缓存。
步骤906：当SMF获知UE当前状态不可达，并收到来自UPF的下行数据检测信息，通过AF标识关联的NEF reference ID向NEF发送第二事件(如“availability after DDN failure”)，第二事件通知可以如Nsmf_EventExposure_Notify，Nsmf_EventExposure_Notify中携带的信息包括：AF标识，或与AF标识的关联信息如NEF reference ID等信息；或者，SMF检测到下行数据状态为缓存状态，SMF通过AF标识关联的NEF reference ID向NEF发送第二事件(如“Downlink data delivery status”)通知，第二事件通知可以如Nsmf_EventExposure_Notify，Nsmf_EventExposure_Notify中携带的信息包括：AF标识、或与AF标识的关联信息如NEF reference ID等信息；
NEF接收来自SMF的携带有AF标识或与AF标识的关联信息如NEF reference ID的第二事件通知，设置与AF标识关联的下行数据通知失败后UE可达消息通知(Notify-on-available-after-DDN-failure)标识，也就是说，获取发送下行数据的AF信息。
Notify-on-available-after-DDN-failure标识与第一事件关联，换句话说，如果 设置了Notify-on-available-after-DDN-failure标识，则表示后续第一事件的第一事件通知需要发送给关联的AF。
步骤907：UE状态由不可达变为可达。
步骤908：AMF获知UE可达，AMF向NEF发送第一事件通知，如Namf_EventExposure_Notify，其中携带有NEF reference ID等信息。
步骤909：NEF收到AMF的第一事件通知，根据设置的Notify-on-available-after-DDN-failure标识，向与关联的AF即发送下行数据的AF发送第一事件通知。
图10为本申请提供的又一种订阅第一事件和第二事件的流程示意图，如图10所示，包括：
步骤1000：AF向NEF发送事件订阅请求如Nnef_EventExposure_Subscribe request。
Nnef_EventExposure_Subscribe request中携带有如：订阅事件类型一(如“availability after DDN failure”)、用于标识AF的信息(如traffic descriptor、IP filter information、AF ID等可以在整个系统中唯一标识AF身份的信息，在本文可以称为AF标识)、UE标识等信息。
步骤1001：NEF收到来自AF的事件订阅请求，生成订阅事件标识(NEF reference ID)，该NEF reference ID与AF标识关联；NEF向UDM发送事件订阅请求如Nudm_EventExposure_subscribe request。
Nudm_EventExposure_subscribe request中携带有如：NEF reference ID、订阅事件类型信息(如事件标识Event ID、订阅事件类型一“availability after DDN failure”等)、事件通知对象信息(notification endpoint information)(如NEF接收事件通知的地址等相关信息)等信息。
步骤1002～步骤1003：UDM向AMF发送第一事件订阅请求如Namf_EventExposure_subscribe request，AMF完成第一事件订阅，向UDM返回第一事件订阅响应如Namf_EventExposure_subscribe reponse。
第一事件订阅请求中携带有如：NEF reference ID、订阅事件类型信息(如事件标识Event ID、订阅事件类型一“availability after DDN failure”等)、事件通知对象信息(notification endpoint information)(如NEF接收事件通知的地址等相关信息)、事件监控对象信息(如UE标识信息)等信息。
步骤1004：AMF向SMF发送第二事件订阅请求如Nsmf_EventExposure_subscribe request，SMF完成第一事件订阅，向AMF返回 第一事件订阅响应如Nsmf_EventExposure_subscribe reponse。
第二事件订阅请求中携带有如：NEF reference ID、订阅事件类型信息(如事件标识Event ID、订阅事件类型为订阅事件类型一“availability after DDN failure”或订阅事件类型二“Downlink data delivery status”等)、事件通知对象信息(notification endpoint information)(如AMF接收事件通知的地址等相关信息)、AF标识等信息。
第一事件的订阅和第二事件的订阅没有严格的先后顺序，图7中仅仅是一个示例，并不用于限定本申请的保护范围。
实施例中去订阅(unsubscribe)或者修改订阅的过程，与上述订阅(subscribe)的过程类似，这里不再赘述。
图11为本申请提供的另一种第二事件通知的流程示意图，如图11所示，包括：
步骤1100：AF发送下行数据到UPF。
步骤1101：UPF收到下行数据，对下行数据进行数据检测，比如检测是哪个AF发送的等；UPF向SMF发送下行数据检测通知，下行数据检测通知可以为如下行数据通知(Downlink Data Notification)或Sx报告(Sx Report)或N4报告(N4Report)。
在一种示例性实例中，在下行数据检测通知中还携带有检测出的AF标识。
在一种示例性实例中，如果SMF不知道该用户处于不可达状态，还可以包括步骤1102：SMF请求AMF寻呼该用户的UE，其中，请求消息可以如：Namf_CommunicationN1N2MessageTransfer request。
步骤1103：UE处于不可达状态，对UE的寻呼失败，即下行数据通知失败(DDN failure)。
在一种示例性实例中，还可以包括步骤1104：
AMF向SMF反馈UE当前处于不可达状态，反馈消息可以如：Namf_CommunicationN1N2MessageTransfer response。
在一种示例性实例中，如果SMF知道UE当前状态不可达，但是UPF没有告知SMF当前发送下行数据的AF标识，还可以包括步骤1105：
SMF向UPF请求发送包括AF标识的下行数据检测信息；或者，SMF通知UPF进行下行数据缓存。
步骤1106：当SMF获知UE当前状态不可达，并收到来自UPF的下行数据检测信息，SMF向AMF发送第二事件(如“availability after DDN failure”) 通知，第二事件通知可以如Nsmf_EventExposure_Notify，Nsmf_EventExposure_Notify中携带的信息包括：AF标识、或与AF标识的关联信息如NEF Reference ID等信息；或SMF检测到下行数据状态是缓存状态，SMF向AMF发送第二事件(如“Downlink data delivery status”)通知，第二事件通知可以Nsmf_EventExposure_Notify，在Nsmf_EventExposure_Notify中携带有如AF标识等信息。
AMF接收来自SMF的携带有AF标识的第二事件通知，设置与AF标识关联的下行数据通知失败后UE可达消息通知(Notify-on-available-after-DDN-failure)标识，也就是说，获取发送下行数据的AF信息。
Notify-on-available-after-DDN-failure标识与第一事件关联，换句话说，如果设置了Notify-on-available-after-DDN-failure标识，则表示后续第一事件的第一事件通知需要发送给关联的AF。
步骤1107：UE状态由不可达变为可达。
步骤1108：AMF获知UE可达，AMF根据设置的Notify-on-available-after-DDN-failure标识，向NEF发送关联的AF即发送下行数据的AF的第一事件通知，如Namf_EventExposure_Notify，其中携带有NEF reference ID等信息。
步骤1109：NEF接收到来自AMF的第一事件通知，将第一事件通知转发给AF。

Claims (35)

  1. 一种事件通知方法，包括：
    网络暴露功能NEF根据来自会话管理功能SMF的第二事件通知，获取发送下行数据的应用功能AF信息；
    所述NEF接收来自接入管理功能AMF的第一事件通知，根据获得的发送下行数据的AF信息向发送下行数据的AF发送第一事件通知；
    其中，所述第二事件为监控AF是否下发下行数据事件；所述第一事件为下行数据通知失败后用户设备UE可达事件。
  2. 根据权利要求1所述的方法，其中，所述NEF根据来自SMF的第二事件通知，获取发送下行数据的AF信息，包括：
    所述NEF接收来自所述SMF的携带有AF标识或与AF关联的标识的所述第二事件通知；
    所述NEF根据收到的AF标识或与AF关联的标识，设置与所述AF关联的下行数据通知失败后UE可达消息通知Notify-on-available-after-DDN-failure标识。
  3. 根据权利要求1所述的方法，在所述获取发送下行数据的AF信息之前，还包括：
    所述NEF接收来自AF发送的事件订阅请求，所述NEF生成订阅事件标识NEF reference ID，其中，所述NEF reference ID与AF标识关联；
    所述NEF向统一数据管理功能UDM发送事件订阅请求。
  4. 根据权利要求3所述的方法，其中，
    所述来自AF的事件订阅请求中携带的信息包括：订阅事件类型一、AF标识、UE标识；
    所述NEF向所述UDM发送的事件订阅请求中携带的信息包括：所述NEF reference ID、订阅事件类型一、事件通知对象信息。
  5. 根据权利要求1所述的方法，在所述获取发送下行数据的AF信息之前，还包括：
    所述NEF接收来自AF的携带有订阅事件类型一和AF标识的事件订阅请求，或者，所述NEF接收来自AF的携带有订阅事件类型二和AF标识的事件订阅请求；
    所述NEF生成NEF reference ID，其中，所述NEF reference ID与AF标识关联；
    所述NEF向策略控制功能PCF发送事件订阅请求。
  6. 根据权利要求5所述的方法，其中，所述NEF向所述PCF发送的事件订阅请求中携带的信息包括：所述NEF reference ID、订阅事件类型二、事件通知对象信息。
  7. 根据权利要求4、5或6所述的方法，其中，
    所述订阅事件类型一包括：下行数据通知失败后UE可达性UE availability after DDN failure类型；
    所述订阅事件类型二包括：下行数据传输状态downlink data delivery status类型。
  8. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1～7中任一项所述的事件通知方法。
  9. 一种实现事件通知的装置，包括处理器、存储器；其中，所述存储器上存储有可在所述处理器上运行的计算机程序，所述计算机程序用于执行权利要求1～7中任一项所述的事件通知方法。
  10. 一种事件通知方法，包括：
    接入管理功能AMF根据来自会话管理功能SMF的第二事件通知，获取发送下行数据的应用功能AF信息；
    所述AMF根据获得的发送下行数据的AF信息，经由网络暴露功能NEF向发送下行数据的AF发送第一事件通知；
    其中，所述第二事件为监控AF是否下发下行数据事件；所述第一事件为下行数据通知失败后用户设备UE可达事件。
  11. 根据权利要求10所述的方法，其中，所述AMF根据来SMF的第二事件通知，获取发送下行数据的AF信息，包括：
    所述AMF接收来自所述SMF的携带有AF标识或与AF关联的标识的所述第二事件通知；
    所述AMF根据收到的AF标识或与AF关联的标识，设置与所述AF关联的下行数据通知失败后UE可达消息通知Notify-on-available-after-DDN-failure标识。
  12. 根据权利要求10所述的方法，其中，所述AMF经由NEF向发送下行数据的AF发送第一事件通知，包括：
    在所述AMF检测到UE状态从不可达变为可达的情况下，所述AMF根据 所述Notify-on-available-after-DDN-failure标识，经由所述NEF向发送下行数据的AF发送所述第一事件通知。
  13. 根据权利要求10、11或12所述的方法，在所述获取发送下行数据的AF信息之前，还包括：
    所述AMF接收来自统一数据管理功能UDM的订阅所述第一事件的订阅第一事件请求，完成第一事件的订阅；
    其中，所述订阅第一事件请求中携带的信息包括：NEF参考标识NEF reference ID、订阅事件类型一、事件通知对象信息、事件监控对象信息。
  14. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求10～13中任一项所述的事件通知方法。
  15. 一种实现事件通知的装置，包括处理器、存储器；其中，所述存储器上存储有可在所述处理器上运行的计算机程序，所述计算机程序用于执行权利要求10～13中任一项所述的事件通知方法的步骤。
  16. 一种事件通知装置，包括：
    关联模块，设置为根据来自会话管理功能SMF的第二事件通知，获取发送下行数据的应用功能AF信息；
    第一通知模块，设置为根据获得的发送下行数据的AF信息向发送下行数据的AF发送第一事件通知；
    其中，所述第二事件为监控AF是否下发下行数据事件；所述第一事件为下行数据通知失败后用户设备UE可达事件。
  17. 根据权利要求16所述的装置，其中，所述关联模块是设置为：
    接收来自所述SMF的携带有AF标识或与AF关联的标识的所述第二事件通知；根据收到的AF标识或与AF关联的标识，设置与所述AF关联的下行数据通知失败后UE可达消息通知Notify-on-available-after-DDN-failure标识。
  18. 根据权利要求16或17所述的装置，其中，所述事件通知装置设置在网络暴露功能NEF中，或者所述事件通知装置为NEF。
  19. 根据权利要求18所述的装置，其中，所述第一通知模块还设置为：接收来自接入管理功能AMF的第一事件通知。
  20. 根据权利要求16或17所述的装置，其中，所述事件通知装置设置在AMF中，或者所述事件通知装置为AMF。
  21. 根据权利要求20所述的装置，其中，所述第一通知模块是设置为：根 据获得的发送下行数据的AF信息，经由NEF向发送下行数据的AF发送所述第一事件通知。
  22. 一种事件通知方法，包括：
    会话管理功能SMF接收到第二事件订阅请求，完成第二事件的订阅；其中，所述第二事件为监控应用功能AF是否下发下行数据事件；
    在AF向用户设备UE发送下行数据但UE状态为不可达的情况下，所述SMF向网络暴露功能NEF或接入管理功能AMF发送第二事件通知；
    其中，所述第二事件通知用于通知所述NEF或所述AMF下发下行数据的AF信息。
  23. 根据权利要求22所述的方法，其中，所述SMF接收到第二事件订阅请求，完成第二事件的订阅，包括：
    所述SMF接收来自统一数据管理功能UDM的第二事件订阅请求，完成第二事件的订阅；其中，所述第二事件订阅请求中携带的信息包括：订阅事件类型一、设置为NEF相关地址的事件通知对象信息、AF标识。
  24. 根据权利要求22所述的方法，其中，所述SMF接收到第二事件订阅请求，完成第二事件的订阅，包括：
    所述SMF接收来自所述AMF的第二事件订阅请求，完成第二事件的订阅；其中，所述第二事件订阅请求中携带的信息包括：订阅事件类型一或订阅事件类型二、设置为AMF相关地址的事件通知对象信息、AF标识。
  25. 根据权利要求22所述的方法，其中，所述SMF接收到第二事件订阅请求，完成第二事件的订阅，包括：
    所述SMF接收来自策略控制功能PCF的第二事件订阅请求，完成第二事件的订阅；其中，所述第二事件订阅请求中携带的信息包括：订阅事件类型二、设置为NEF相关地址的事件通知对象信息、AF标识。
  26. 根据权利要求23、24或25所述的方法，其中，
    所述订阅事件类型一包括：下行数据通知失败后UE可达性UE availability after DDN failure类型；
    所述订阅事件类型二包括：下行数据传输状态downlink data delivery status类型。
  27. 根据权利要求22所述的方法，其中，所述SMF向所述NEF或所述AMF发送第二事件通知，包括：
    在所述SMF获知UE当前状态不可达，并收到来自用户面功能UPF的下行数据检测信息的情况下，所述SMF根据所述下行数据检测信息包含的AF标识获取所述AF标识关联的订阅事件；所述SMF根据AF标识关联的订阅事件的通知对象信息向所述NEF或所述AMF发送携带有AF标识或与AF关联的标识的第二事件通知；或者，
    所述SMF检测到所述AF的下行数据状态为缓存状态，所述SMF根据所述AF标识获取所述AF标识关联的订阅事件；所述SMF根据AF标识关联的订阅事件的通知对象信息向所述NEF或所述AMF发送携带有AF标识或与AF关联的标识的第二事件通知。
  28. 根据权利要求22或27所述的方法，在所述SMF向所述NEF或所述AMF发送第二事件通知之前，还包括：
    所述SMF向UPF请求发送包括AF标识的下行数据检测信息；或者，
    所述SMF通知UPF进行下行数据缓存。
  29. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求22～28中任一项所述的事件通知方法。
  30. 一种实现事件通知的装置，包括处理器、存储器；其中，所述存储器上存储有可在所述处理器上运行的计算机程序，所述计算机程序用于执行权利要求22～28中任一项所述的事件通知方法。
  31. 一种事件通知装置，包括：
    处理模块，设置为接收到第二事件订阅请求，完成第二事件的订阅；其中，所述第二事件为监控应用功能AF是否下发下行数据事件；
    第二通知模块，设置为在应用功能AF向用户设备UE发送下行数据但UE状态为不可达的情况下，向网络暴露功能NEF或接入管理功能AMF发送第二事件通知；其中，所述第二事件通知用于通知所述NEF或所述AMF下发下行数据的AF信息。
  32. 根据权利要求31所述的装置，其中，所述事件通知装置设置在会话管理功能SMF中，或者所述事件通知装置为SMF。
  33. 根据权利要求31所述的装置，其中，所述处理模块是设置为：
    接收来自统一数据管理功能UDM的第二事件订阅请求，完成第二事件的订阅；其中，所述第二事件订阅请求中携带的信息包括：订阅事件类型一、设置为NEF相关地址的事件通知对象信息、AF标识；或者，
    接收来自所述AMF的第二事件订阅请求，完成第二事件的订阅；其中，所 述第二事件订阅请求中携带的信息包括：订阅事件类型一或订阅事件类型二、设置为AMF相关地址的事件通知对象信息、AF标识。
  34. 根据权利要求32所述的装置，其中，所述第二通知模块是设置为：
    在获知所述UE当前状态不可达，并收到来自用户面功能UPF的下行数据检测信息的情况下，根据所述下行数据检测信息包含的AF标识获取所述AF标识关联的订阅事件；根据AF标识关联的订阅事件的通知对象信息向所述NEF或所述AMF发送携带有AF标识或与AF关联的标识的第二事件通知；或者，
    检测到所述AF的下行数据状态为缓存状态，通过所述AF标识获取所述AF标识关联的订阅事件；根据AF标识关联的订阅事件的通知对象信息向所述NEF或所述AMF发送携带有AF标识或与AF关联的标识的所述第二事件通知。
  35. 根据权利要求32或34所述的装置，其中，所述第二通知模块还设置为：
    向UPF请求发送包括AF标识的下行数据检测信息；或者，通知UPF进行下行数据缓存。
PCT/CN2020/082036 2019-03-28 2020-03-30 事件通知方法、装置及存储介质 WO2020192787A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR1020237037105A KR20230152838A (ko) 2019-03-28 2020-03-30 이벤트 통지 방법, 장치 및 저장매체
EP20779067.6A EP3952367A4 (en) 2019-03-28 2020-03-30 EVENT NOTIFICATION METHOD AND DEVICE AND STORAGE MEDIA
KR1020217034595A KR102596924B1 (ko) 2019-03-28 2020-03-30 이벤트 통지 방법, 장치 및 저장매체
US17/599,191 US20220191665A1 (en) 2019-03-28 2020-05-30 Event notification method, apparatus and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910241964.8 2019-03-28
CN201910241964.8A CN110536282B (zh) 2019-03-28 2019-03-28 一种事件通知方法及装置

Publications (1)

Publication Number Publication Date
WO2020192787A1 true WO2020192787A1 (zh) 2020-10-01

Family

ID=68659185

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/082036 WO2020192787A1 (zh) 2019-03-28 2020-03-30 事件通知方法、装置及存储介质

Country Status (5)

Country Link
US (1) US20220191665A1 (zh)
EP (1) EP3952367A4 (zh)
KR (2) KR20230152838A (zh)
CN (1) CN110536282B (zh)
WO (1) WO2020192787A1 (zh)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110536282B (zh) * 2019-03-28 2023-03-21 中兴通讯股份有限公司 一种事件通知方法及装置
CN110621032B (zh) * 2019-09-27 2021-06-15 腾讯科技（深圳）有限公司 一种通信的方法、相关装置及设备
CN113038467B (zh) * 2019-12-06 2022-12-02 华为技术有限公司 一种事件信息上报方法及通信装置
WO2021093147A1 (en) * 2020-01-06 2021-05-20 Zte Corporation Method, system and apparatus for i-smf event subscription and notification
CN113498051B (zh) * 2020-03-18 2023-01-03 维沃移动通信有限公司 一种订阅网络事件的方法和网络功能
EP4154562A4 (en) * 2020-05-22 2024-02-21 Zte Corp METHOD FOR EXPOSING INFORMATION OF A RADIO ACCESS NETWORK
CN113973322A (zh) * 2020-07-24 2022-01-25 华为技术有限公司 一种通信方法及装置
CN114143185A (zh) * 2020-08-13 2022-03-04 阿里巴巴集团控股有限公司 一种网络通信的方法及装置、电子设备、存储介质
CN114339643B (zh) * 2020-09-29 2023-09-22 华为技术有限公司 策略规则的提供方法及会话管理网元
JP7460853B2 (ja) * 2021-01-15 2024-04-02 華為技術有限公司 イベント登録方法、機器、及びシステム

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018127148A1 (en) * 2017-01-05 2018-07-12 Huawei Technologies Co., Ltd. Systems and methods for application-friendly protocol data unit (pdu) session management
US20180270778A1 (en) * 2017-03-17 2018-09-20 Samsung Electronics Co., Ltd. Af influenced pdu session management and subscription procedures
CN109417534A (zh) * 2016-05-02 2019-03-01 华为技术有限公司 通信网络服务质量能力开放方法和装置
CN109413619A (zh) * 2017-08-14 2019-03-01 中兴通讯股份有限公司 信息发送、操作执行方法及装置、会话管理功能实体
CN110536282A (zh) * 2019-03-28 2019-12-03 中兴通讯股份有限公司 一种事件通知方法及装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102546554B (zh) * 2010-12-27 2015-01-28 中兴通讯股份有限公司 一种ip多媒体子系统及其恢复用户订阅关系的方法
KR102149263B1 (ko) * 2017-05-09 2020-08-28 후아웨이 테크놀러지 컴퍼니 리미티드 세션 관리 방법 및 세션 관리 기능 네트워크 엘리먼트

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109417534A (zh) * 2016-05-02 2019-03-01 华为技术有限公司 通信网络服务质量能力开放方法和装置
WO2018127148A1 (en) * 2017-01-05 2018-07-12 Huawei Technologies Co., Ltd. Systems and methods for application-friendly protocol data unit (pdu) session management
US20180270778A1 (en) * 2017-03-17 2018-09-20 Samsung Electronics Co., Ltd. Af influenced pdu session management and subscription procedures
CN109413619A (zh) * 2017-08-14 2019-03-01 中兴通讯股份有限公司 信息发送、操作执行方法及装置、会话管理功能实体
CN110536282A (zh) * 2019-03-28 2019-12-03 中兴通讯股份有限公司 一种事件通知方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "Procedure of availability after DDN failure notification for multiple AFs", 3GPP TSG-SA2 MEETING #131 S2-1902136, 1 March 2019 (2019-03-01), XP051610697, DOI: 20200616112746X *
See also references of EP3952367A4 *

Also Published As

Publication number Publication date
EP3952367A4 (en) 2022-12-28
CN110536282B (zh) 2023-03-21
EP3952367A1 (en) 2022-02-09
KR20210142719A (ko) 2021-11-25
KR20230152838A (ko) 2023-11-03
US20220191665A1 (en) 2022-06-16
CN110536282A (zh) 2019-12-03
KR102596924B1 (ko) 2023-11-01

Similar Documents

Publication Publication Date Title
WO2020192787A1 (zh) 事件通知方法、装置及存储介质
US11523268B2 (en) Communications method and apparatus
US11116039B2 (en) Method and apparatus for supporting user's mobility over a local area data network
US11438860B2 (en) Event subscription method, apparatus, and system
US11856469B2 (en) Communication method, communications apparatus, and communications system
JP2021518075A (ja) サービス加入方法および装置
CN110535676B (zh) Smf动态容灾的实现方法、装置、设备及存储介质
US11563649B2 (en) NF service consumer restart detection using direct signaling between NFs
US11251981B2 (en) Communication method and apparatus
WO2021109824A1 (zh) 会话创建方法和装置、会话创建的控制方法和装置、会话创建系统、网元及存储介质
WO2019096306A1 (zh) 一种处理请求的方法以及相应实体
WO2021164763A1 (zh) 模式切换的方法及设备
WO2021164471A1 (zh) 拥塞控制方法、装置、设备、介质及系统
US20210329504A1 (en) Communication method and apparatus
KR20220158018A (ko) 접속 수립 방법, 통신 장치, 및 시스템
JP2020508610A (ja) 情報処理方法、装置、コンピュータ読み取り可能な記憶媒体および電子機器
KR20180107763A (ko) 사용자 트래픽 연결 관리 방법
WO2019223638A1 (zh) 一种api信息传输方法及装置
US9167543B2 (en) Synchronization of mobile client multicast
US20230269627A1 (en) Method and System for Adjusting Service Priority of User, and Storage Medium
JP2023528138A (ja) セッション処理方法、デバイス及び記憶媒体
WO2023098718A1 (en) Method and apparatus for context resumption
CN116321110B (zh) 服务订阅方法、装置、服务提供网元及存储介质
US11395215B2 (en) Systems and methods for detecting and remediating excessive messaging by wireless telecommunications devices
US20240015483A1 (en) Procedure to join a multicast session

Legal Events

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

Ref document number: 20779067

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20217034595

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020779067

Country of ref document: EP

Effective date: 20211028