WO2020073960A1 - Procédé et appareil de notification de message, élément de réseau, système et support de stockage - Google Patents

Procédé et appareil de notification de message, élément de réseau, système et support de stockage Download PDF

Info

Publication number
WO2020073960A1
WO2020073960A1 PCT/CN2019/110392 CN2019110392W WO2020073960A1 WO 2020073960 A1 WO2020073960 A1 WO 2020073960A1 CN 2019110392 W CN2019110392 W CN 2019110392W WO 2020073960 A1 WO2020073960 A1 WO 2020073960A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
notification
event
application
request
Prior art date
Application number
PCT/CN2019/110392
Other languages
English (en)
Chinese (zh)
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
Priority claimed from CN201811341759.0A external-priority patent/CN111031517A/zh
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2020073960A1 publication Critical patent/WO2020073960A1/fr

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

Definitions

  • This application relates to the field of communication technology, and in particular, to a message notification method, device, network element, system, and storage medium.
  • AF Application Function
  • 3rd Generation Partnership Project 3rd Generation Partnership Project
  • the data sent to the UE is downlink data (DownLink data or DL data) transmission.
  • DownLink data or DL data Downlink data
  • the UE is not always connected.
  • AF does not know.
  • DDN failed event also called UE reachable event or UE reachable state after downlink data notification failure
  • Subscription event hereinafter referred to as the UE reachable event after the failure of downlink data
  • an AF sends downlink data
  • the UPF User Plane Function
  • AMF Access Management Function
  • the network element sends a DDN (Downlink Data Notify) message to notify the AMF that the downlink data needs to wake the UE.
  • DDN Downlink Data Notify
  • the AMF If the AMF cannot wake the UE, it returns a DDN failure response; when the UE status is never reachable (unreachability) ) When it becomes reachable (availability), the AMF will directly send a UE reachability notification message to all AFs that have subscribed to the downlink data after the failure of the UE reachability event.
  • the AMF will directly send a UE reachability notification message to all AFs that have subscribed to the downlink data after the failure of the UE reachability event.
  • not all AFs subscribed to the UE reachability subscription event need to receive the notification message that the UE is reachable. For example, in an example case, only the AF that sent the downlink data service requirement needs to receive the notification message that the UE is reachable. Therefore, it is not necessary to send a notification message of UE reachability to all AFs that have subscribed to the UE reachability event after the failure of the downlink data subscription, and it also wastes network resources.
  • a message notification method, device, network element, system, and storage medium provided by embodiments of the present invention mainly solve the problem of sending UE reachable notification messages in the related art directly to all UE reachable events after subscribing to downlink data fails
  • the AF sends a notification message that the UE is reachable.
  • An embodiment of the present invention provides a message notification method, including:
  • the UE reachability notification is sent to the NEF network element according to the first subscription event, after the downlink data failure.
  • An embodiment of the present invention also provides a message notification device, including:
  • a third event subscription processing module configured to receive a first request for a UE reachable event after failing to subscribe to downlink data, and generate a first subscription event for the UE reachable after failed downlink data according to the first request, in the first request Including the associated AF application ID, NEF network element ID NEF ID and event reference ID of the first subscription event;
  • a fifth notification sending module configured to receive the UE reachability notification after the downlink data of the target UE corresponding to the application identifier fails, and send the UE reachability notification after the downlink data fails to the UE according to the first subscription event NEF network element.
  • An embodiment of the present invention also provides a message notification method, including:
  • Session Management Function Session Management Function
  • the UE After the downlink data fails to be sent to the AF corresponding to the application identifier included in the application identifier list, the UE is reachable notification.
  • An embodiment of the present invention also provides a message notification method, including:
  • An embodiment of the present invention also provides a message notification device, including:
  • the second request receiving module is used to receive the request sent by the AF for the UE reachable event after subscribing to the downlink data fails;
  • the second event subscription request module is used to send a first request to the AMF network element after the UE fails to subscribe to the downlink data according to the request, and send a second request to the SMF network element to subscribe to the application data detection event;
  • a second notification receiving module configured to receive an application data detection notification sent by the SMF network element, store the application identifier in the application data detection notification in an application identifier list; and receive downlink data sent by the AMF network element Notification of UE reachability after failure;
  • the second notification sending module is configured to send the UE reachable notification after the downlink data fails to be sent to the AF corresponding to the application identifier included in the application identifier list.
  • An embodiment of the present invention also provides a message notification device, including:
  • a fourth request receiving module configured to receive a second request sent by the NEF network element to subscribe to the application data detection event, where the second request includes the AF application identification and the NEF network element identification NEFID;
  • a second event subscription processing module configured to generate a second subscription event for application data detection according to the second request, and request the UPF network element to activate the application data of the AF corresponding to the application identifier according to the second subscription event Detection
  • a fourth notification sending module configured to receive an application data detection notification sent by the UPF network element, where the application data detection notification includes an application identifier that detects the AF that has sent downlink data, and sends the application data detection notification to The NEF network element.
  • An embodiment of the present invention also provides a message notification method, including:
  • the target network element Receiving the UE reachability notification after the failure of the downlink data sent by the target network element, where the UE reachability notification after the failure of the downlink data includes the application identification of the AF corresponding to the UE that becomes unreachable;
  • An embodiment of the present invention also provides a message notification device, including:
  • the first request receiving module is used to receive the request sent by the AF for the UE reachable event after the subscription of the downlink data fails;
  • the first event subscription request module is used to send a first request for a UE reachable event after a failure to subscribe to downlink data to the target network element according to the request, the first request includes a network open function NEF network element identifier NEFID and The application identification of the AF;
  • the first notification receiving module is configured to receive the UE reachability notification after the downlink data sent by the target network element fails, and the UE reachability notification after the downlink data fails includes the AF corresponding to the UE that becomes unreachable Application identification
  • the first notification sending module is configured to send the UE reachability notification after the downlink data fails to the AF corresponding to the application identifier included in the UE reachability notification after the downlink data failure.
  • An embodiment of the present invention also provides an SMF network element, including a first processor, a first memory, and a first communication bus;
  • the first communication bus is used to connect the first processor and the first memory
  • the first processor is used to execute the first computer program stored in the first memory to implement the message notification method as described above;
  • the first processor is used to execute the second computer program stored in the first memory to implement the message notification method as described above.
  • An embodiment of the present invention further provides an NEF network element, including a second processor, a second memory, and a second communication bus;
  • the second communication bus is used to connect the second processor and the second memory
  • the second processor is used to execute a third computer program stored in the second memory to implement the message notification method as described above;
  • the second processor is used to execute the fourth computer program stored in the second memory to implement the message notification method as described above.
  • An embodiment of the present invention also provides a communication system, the communication system includes a target network element and a NEF network element;
  • the target network element is used to receive a first request for a UE reachability event after failing to subscribe to downlink data, and generate a first subscription event for the UE reachability after downlink data failure according to the first request, the first request includes AF
  • the UE reachability notification After the downlink data fails, the UE reachability notification, according to the first subscription event, send the UE reachability notification to the NEF network element after the downlink data fails;
  • the NEF network element is used to send the UE reachability notification after the downlink data fails to the AF corresponding to the application identifier included in the UE reachability notification after the downlink data fails.
  • An embodiment of the present invention further provides a computer-readable storage medium for storing one or more first computer programs, and the one or more first computer programs may be processed by one or more To execute the message notification method as described above;
  • the computer-readable storage medium is used to store one or more second computer programs, and the one or more second computer programs may be executed by one or more processors to implement the message notification method as described above ;
  • the computer-readable storage medium is used to store one or more third computer programs, and the one or more third computer programs may be executed by one or more processors to implement the message notification method as described above ;
  • the computer-readable storage medium is used to store one or more fourth computer programs, and the one or more fourth computer programs may be executed by one or more processors to implement the message notification method as described above .
  • the request after receiving the request sent by the AF for the UE reachable event after the failure to subscribe to the downlink data, the request is sent to the target network element according to the request
  • the first request for the UE reachable event after subscribing to the downlink data fails.
  • the first request includes the NEF ID of the NEF network element and the Application ID of the AF, so that the target network element fails to generate the downlink data corresponding to the AF.
  • Messages (such as UE reachability notification after downlink data failure), instead of directly sending to all AFs that have subscribed to the UE reachability event after downlink data failure, so the targetedness of UE reachability notification messages can be improved and network resource utilization can be improved .
  • FIG. 1 is a schematic flowchart of a message notification method according to Embodiment 1 of the present invention.
  • FIG. 2 is a schematic diagram of a basic network architecture according to Embodiment 2 of the present invention.
  • FIG. 3 is a schematic diagram of a subscription event process according to Embodiment 2 of the present invention.
  • FIG. 4 is a schematic diagram of a subscription event process according to Embodiment 3 of the present invention.
  • FIG. 5 is a schematic diagram of a notification flow of a UE reachability notification message according to Embodiment 4 of the present invention.
  • FIG. 6 is a schematic structural diagram of a message notification device according to Embodiment 5 of the present invention.
  • FIG. 7 is a schematic flowchart of a message notification method on a NEF network element side according to Embodiment 6 of the present invention.
  • FIG. 8 is a schematic flowchart of clearing an application identifier according to Embodiment 6 of the present invention.
  • FIG. 9 is a schematic flowchart of an identification process according to Embodiment 6 of the present invention.
  • FIG. 10 is a schematic structural diagram of a message notification device on a NEF network element side according to Embodiment 6 of the present invention.
  • FIG. 11 is a schematic flowchart of a message notification method on an AMF network element side according to Embodiment 6 of the present invention.
  • FIG. 12 is a schematic diagram of a third subscription event processing flow on the AMF network element side according to Embodiment 6 of the present invention.
  • FIG. 13 is a schematic structural diagram of a message notification device on an AMF network element side according to Embodiment 6 of the present invention.
  • FIG. 14 is a schematic flowchart of a message notification method on an SMF network element side according to Embodiment 6 of the present invention.
  • FIG. 15 is a schematic structural diagram of a message notification device on an SMF network element side according to Embodiment 6 of the present invention.
  • FIG. 16 is a schematic diagram 1 of a subscription event process according to Embodiment 7 of the present invention.
  • FIG. 17 is a second schematic diagram of a subscription event process according to Embodiment 7 of the present invention.
  • FIG. 18 is a schematic diagram of a notification process of a UE reachable notification message according to Embodiment 7 of the present invention.
  • FIG. 19 is a schematic flowchart of a message notification method on an NEF network element side according to Embodiment 8 of the present invention.
  • FIG. 20 is a schematic flowchart of a message notification method on a target network element side according to Embodiment 8 of the present invention.
  • FIG. 21 is a schematic structural diagram of a message notification device according to Embodiment 8 of the present invention.
  • FIG. 22 is a schematic structural diagram of an SMF network element according to Embodiment 9 of the present invention.
  • FIG. 23 is a schematic structural diagram of a NEF network element according to Embodiment 9 of the present invention.
  • FIG. 24 is a schematic structural diagram of an AMF network element according to Embodiment 9 of the present invention.
  • This embodiment provides a message notification method.
  • the target network element fails to generate downlink data according to the first request, the first subscription event and the first subscription event of the UE reachability event (that is, UE availability after DDN failed event) after the downlink data generation fails
  • the application ID of the AF in the first request that is, Application ID, and it should be understood that the application ID in this embodiment may be a unique identifier / any information that identifies AF) is associated;
  • the target network element detects a subscription
  • the target UE reachability notification that is, a UE reachability notification message
  • the NEF network element can send the UE reachability notification message to the AF corresponding to the application identifier in a targeted manner; improve the rationality of sending UE reachability notification messages and Network resource utilization
  • This embodiment takes the target network element as the SMF network element as an example, and provides a message notification method.
  • the SMF network element generates a first subscription event that the UE can reach after the downlink data fails according to the first request.
  • the first request includes the mutual The associated AF application ID, NEF network element ID NEF ID and event reference ID of the first subscription event, the generated first subscription event can be associated with the event reference ID; in this way, after SMF subsequently fails to receive the downlink data, the UE
  • the UE reachability notification (that is, a UE reachability notification message) can be sent to the NEF network element corresponding to the NEF ID after the downlink data fails according to the first subscription event generated before to pass the NEF network element
  • Sending AF to Application ID Application ID included in UE reachability notification after downlink data failure
  • the message notification method provided in this embodiment includes a first subscription event generation process and a notification process of UE reachability notification after downlink data failure.
  • An example message notification method is shown in FIG. 1 and includes:
  • S101 Receive a first request for a UE reachable event after a failure to subscribe to downlink data, and generate a first subscription event for a UE reachable after a failed downlink data according to the first request.
  • the first request includes an AF application identifier and an NEF network element identifier The NEF ID and the event reference identifier of the first subscription event.
  • the first subscription event may be associated with the event reference identifier.
  • the first request includes the event reference identifier of the associated first subscription event, the application ID of the third-party application AF, and the NEF ID of the network open function NEF network element.
  • the target UE is the AF in the first request.
  • the corresponding target UE that is, the target receiving object of the downlink data delivered by the AF.
  • the first subscription event generated in S101 is associated with the event reference identifier of the first subscription event in the first request. And optionally, S101 may be performed by an SMF network element.
  • the NEF network element may trigger, according to a request of the third-party application AF, to send a first request to the session management function SMF network element to generate the UE reachable event after the failure of the downlink data for SMF
  • the network element generates a first subscription event that monitors the reachability of the UE.
  • the event reference identifier of the first subscription event included in the first request may be generated by the NEF network element.
  • the request sent by the NEF network element may include, but is not limited to, the following request: an event open subscription request from AF, for example, including but not limited to an event exposure subscription request (Event Exposure_Subscribe request).
  • an event open subscription request from AF for example, including but not limited to an event exposure subscription request (Event Exposure_Subscribe request).
  • the first request may include but is not limited to at least one of the following requests: an event open subscription request from a unified data management (Unified Data Management (UDM) network element, such as but not limited to Event Exposure_Subscribe request: Session policy control update notification request from a policy control function (Policy Control Function, PCF) network element, including, but not limited to, session management (Session Management, SM) policy control update notification request (Policy Control_Update Notify request).
  • UDM Unified Data Management
  • PCF Policy Control Function
  • S102 Receive the UE reachability notification after the downlink data of the target UE corresponding to the application identifier fails, and send the UE reachability notification to the NEF network element after the downlink data fails according to the first subscription event.
  • the UPF network element may also be configured to perform AF application packet detection, that is, send a message to the UPF to activate the application data corresponding to the above Application ID Detection function.
  • the SMF network element can deliver the PFD (Packet Flow Description) corresponding to the Application ID to the UPF network element.
  • the SMF network element can also deliver the Application ID to the UPF.
  • the UPF network element can perform application packet detection based on the locally configured PFD corresponding to the Application ID.
  • the SMF network element may control whether the first subscription event needs to report the downlink data after the failure of reporting the downlink data through the first notification identifier. Therefore, in an example of this embodiment, the SMF network element generates the first subscription event, it may further include: generating a first notification identifier, including but not limited to a notification flag (notification flag), and setting the generated first notification identifier and the first subscription in the first request The event reference identifier of the event is associated.
  • the value of the first notification identifier can be set to a first preset value, it can be characterized that the first subscription event associated with the event reference identifier of the first subscription event associated with the first notification identifier needs to report downlink data after the failure UE reachable notification.
  • the UE can be notified.
  • the specific value of the first preset value in this embodiment can be flexibly set, for example, can be set to "1" or “Yes", or can be set to other values, as long as the first notification identifier can be characterized
  • the first subscription event associated with the event reference identifier of the associated first subscription event needs to be notified that the UE is reachable after failure to report downlink data.
  • the value of the generated first notification identifier may not be set for the SMF network element, or the default setting is directly set to the first preset value. It can also be flexibly set according to specific application scenarios.
  • the SMF network element may set the value of the first notification identifier in but not limited to the following example manner. For example, before the SMF network element receives the reachability notification, the SMF network element receives the application data detection notification including the corresponding Application ID sent by the UPF, and determines that the target UE to be delivered by the AF corresponding to the Application ID is currently unreachable, The notification flag corresponding to the Application ID can be set as the first preset value.
  • the application data detection notification in this embodiment includes but is not limited to: at least one of an N4 report (Report) message and a data notification (Data Notification) message. Moreover, in this embodiment, the N4 Report message and Data Notification message can be sent to the SMF network element through, but not limited to, the UPF.
  • the method may further include: determining a first notification identifier (the first notification identifier Is the first notification identifier corresponding to the event reference identifier of the first subscription event associated with the NEF in S102) is currently the first preset value, and if so, the UE reachable notification is sent to the NEF ID after the downlink data fails
  • the corresponding NEF network element is for the NEF network element to send the UE reachable notification to the AF corresponding to the Application ID after the downlink data fails according to the association relationship between the Application ID and the event reference identifier of the first subscription event.
  • the SMF network element obtains the UE reachability notification after the downlink data fails by requesting a subscription to the UE reachability event from the AMF network element, and the AMF network element receives the SMF network element request After the first subscription event, the notification flag is set to control whether the UE reachability notification needs to be sent to the SMF network element.
  • the AMF network element may set a second notification identifier associated with the SMF network element when paging the UE according to the request of the SMF network element, such as, but not limited to, the UE reachability notification SMF identifier (UE Availability A Notify SMF flag) ,
  • the value of the second notification identifier can also be set to the first preset value, indicating that the associated SMF needs to be reported, that is, indicating that the state of the target UE changes from unreachable unreachability to reachable and the associated SMF needs to be notified .
  • the UE reachability notification is that the AMF network element detects that the state of the target UE changes from unreachable unreachability to reachable availability, and is associated with the SMF network element.
  • the AMF sends it to the SMF.
  • the second notification identifier is set after the AMF network element detects that the status of the target UE is unreachable and reaches the SMF event subscription message.
  • an example of a setting process may include but is not limited to: when the SMF network element receives the application data detection notification including the Application ID from the UPF network element, and the SMF network element learns that the user is currently unreachable, the application ID is set The corresponding first notification identifier is the first preset value; if the SMF network element learns that the user is currently unreachable and has not subscribed to the AMF network element for the user reachability status notification at that time, the SMF subscribes to the AMF network element for the UE reachability status notification event When the AMF network element receives the subscription UE reachable status notification request from the SMF network element, it sets the value of the second notification identifier associated with the above SMF network element as the first preset value to characterize the AMF network element When detecting that the state of the target UE changes from unreachable to reachable, a message notification needs to be sent to the SMF network element.
  • the UE reachability notification after the downlink data fails can be sent only to the AF that sent the downlink data service demand, rather than to all those who have subscribed to the first subscription event of the UE reachability status AF improves the pertinence and intelligence of UE reachability notification after downlink data failure, and improves network resource utilization.
  • next-generation wireless access network In order to maintain the competitiveness of the third-generation mobile communication system in the field of communication, provide users with faster speed, lower latency, and more personalized mobile communication services, and at the same time, reduce the operating costs of operators, 3GPP (3rd Generation Partnership) Project , The Third Generation Partnership Project) Standards Working Group is dedicated to the research of next-generation wireless mobile access networks.
  • the next-generation wireless access network In the next-generation wireless access network, it supports multiple wireless networks to access a unified core network, and it is hoped that the wireless access network (Radio Access Network, RAN) and core network (Core Network, CN) will minimize the coupling relationship, that is, regardless of The terminal can access the unified CN through any RAN access technology.
  • the core network functions of the next-generation network include an example of the basic network architecture shown in Figure 2.
  • the main network functions Networkworks, Funtions, NFs
  • AMF belongs to the public control plane function in the core network and terminates NAS (Non-Access Stratum, non-access) messages between all users and the network.
  • a UE can have only one AMF, which is responsible for user mobility management, UE status (such as reachability) management, and so on.
  • SMF is responsible for, but not limited to, session establishment, modification, deletion, control of PCF charging and policy enforcement.
  • the PCF is responsible for, but not limited to, formulating strategies for the terminal based on the user's subscription, the UE's current location, and application-related information, including routing strategies, quality of service strategies, and charging strategies.
  • UDM has a unified data management function, which can be used for but not limited to the permanent storage of user contracted data and other functions.
  • UDR Unified Data Repository
  • UDM User Data Repository
  • UPF a function of the user plane in the core network, is the anchor point of the user plane of the core network, is the interface with the external network (DN, Data) Network data transmission, and executes the execution of PCF policy rules in the user plane;
  • NEF (not shown in the figure) is used to expose the capabilities and events of 3GPP NFs to other NFs or AFs, provide AF pre-configured 3GPP NFs capabilities, and implement 3GPP network and external network information mapping.
  • AF refers to a third-party application other than 3GPP
  • DN refers to an external network other than 3GPP
  • the fifth generation mobile communication system (the 5th Generation mobile communication system, 5G) -Access Network (AN) refers to 5G access Into the network.
  • 5G 5th Generation mobile communication system
  • AN Access Network
  • this embodiment is based on the foregoing second embodiment, and based on the network basic architecture application scenario shown in FIG. 2, a first subscription event is generated on the SMF network element and a UPF is developed to perform AF application packet detection
  • Figure 3 including:
  • Each AF can subscribe to the notification event (that is, subscribe to the UE's availability after DDN failed event) through the NEF network element.
  • the AF can send a Nnef_Event Exposure_Subscribe request to subscribe to the availability of the target UE corresponding to the AF. May include instructions to subscribe to the Availability DDN failure event, and the Application ID that includes the AF.
  • the message also includes a target UE identity, which may indicate a single user or a group of users.
  • the target UE identity may also include an IP address.
  • the NEF network element may generate the event reference identifier NEF_reference_ID1 of the first subscription event.
  • the event reference identifier of the first subscription event is associated with the Application ID in the Nnef_Event Exposure_Subscribe request.
  • the NEF network element sends a first request to the UDM network element.
  • the NEF network element sends a Nudm_Event Exposure_Subscribe request (that is, a first request) to the UDM network element.
  • the Nudm_Event Exposure_Subscribe request may include an instruction to subscribe to the Availability after DDN failure event, AF's Application ID, NEF_reference_ID1.
  • the Nudm_Event Exposure_Subscribe request may also include the NEF ID of the NEF network element.
  • the UDM network element finds the context related to the user according to the target UE ID, selects the appropriate SMF network element within the user context, and then goes to the SMF network element to subscribe to the UE's availability after DDN failed event.
  • the UDM network element may send an Nsmf_Event Exposure_Subscribe request to the SMF network element.
  • the Nsmf_Event Exposure_Subscribe request may include an instruction to subscribe to the Availability after DDN failure event, Application ID, NEF ID, NEF_reference_ID1.
  • the SMF generates a first subscription event that monitors the reachability of the UE.
  • the SMF may set whether to send the first notification identifier notification flag that starts monitoring (if the notification flag is "No", the UE reachable notification will not be sent after the downlink data of the first subscription event fails, if the notification flag If it is "Yes” (that is, the first preset value), the UE can reach the notification after the downlink data of the first subscription event fails to be sent).
  • the SMF network element configures the UPF network element to perform AF application packet inspection.
  • the SMF network element activates the application packet detection for the Application ID on the UPF network element according to the subscription request (ie, second request) of the UDM network element.
  • the SMF network element can send an N4 Session Establishment (Establishment) / Modification Request (Application ID (PFD) to the UPF network element.
  • the SMF network element can associate the PFD corresponding to the Application ID Issued to UPF.
  • the SMF can also send the Application ID to the UPF.
  • the UPF performs application packet inspection based on the locally configured PFD corresponding to the Application ID.
  • S305 The SMF network element sends a response message to the UDM network element, for example, Nsmf_EventExposure_Subscribe responses.
  • the UDM network element sends a response message to the NEF network element, for example, Nudm_EventExposure_Subscribe responses.
  • the NEF network element sends a response message to the AF, for example, Nnef_EventExposure_Subscribe responses.
  • steps S306 and S307 may also be sent before step S303.
  • the first subscription event can be generated on the SMF network element and the UPF can be configured to perform AF application packet detection.
  • this embodiment uses a method for generating a first subscription event on an SMF network element and formulating a UPF for AF application packet detection as an example. See FIG. 4, including :
  • Each AF can subscribe to the notification event (that is, subscribe to the UE availability and after DDN failed event) through the NEF network element.
  • the AF can send a Nnef_Event Exposure_Subscribe request to subscribe to the availability of the target UE corresponding to the AF. May include instructions to subscribe to the Availability DDN failure event, and the Application ID that includes the AF.
  • the NEF finds the corresponding PCF network element according to the target UE identifier and other information, and the PCF network element generates the relevant first subscription event; for example, the NEF network element may send Npcf_PolicyAuthorization_Create (that is, an exemplary first request) to the PCF network element.
  • the Npcf_PolicyAuthorization_Create may include an instruction to subscribe to Availability after DDN failure event, AF Application ID, NEF_reference_ID1.
  • the Npcf_PolicyAuthorization_Create may also include the NEF ID of the NEF network element.
  • the PCF network element finds the user-related context and related session according to the target UE identifier and other information, and then subscribes to the Availability DDN failure event (ie, UE validity monitoring event) on the SMF network element of the session.
  • the PCF network element may send Npcf_SMPolicyControl_UpdateNotify to the SMF network element, and the Npcf_SMPolicyControl_UpdateNotify may include an instruction to subscribe to the Availability after DDN failure event, Application ID, NEF ID, NEF_reference_ID1.
  • the SMF generates a first subscription event that monitors the reachability of the UE.
  • the SMF may set whether to send the first notification identifier notification flag that starts monitoring (if the notification flag is "No", the UE reachable notification will not be sent after the downlink data of the first subscription event fails, if the notification flag If it is "Yes” (that is, the first preset value), the UE can reach the notification after the downlink data of the first subscription event fails to be sent).
  • the SMF network element configures the UPF network element to perform AF application packet inspection.
  • the SMF network element activates the application packet detection for the Application ID on the UPF network element according to the subscription request of the PCF network element. For example, the SMF network element may send N4 Session / Establishment / Modification Request (Application ID, PFD) to the UPF network element. In the N4 Session / Establishment / Modification Request, the SMF network element may send the PFD corresponding to the Application ID to the UPF. The SMF can also send the Application ID to the UPF. At this time, the UPF performs application packet inspection based on the locally configured PFD corresponding to the Application ID.
  • N4 Session / Establishment / Modification Request Application ID
  • PFD Application ID
  • the SMF network element may send the PFD corresponding to the Application ID to the UPF.
  • the SMF can also send the Application ID to the UPF.
  • the UPF performs application packet inspection based on the locally configured PFD corresponding to the Application ID.
  • S405 The SMF network element sends a response message to the PCF network element, for example, Npcf_SMPolicyControl_UpdateNotify.
  • the PCF network element sends a response message to the NEF network element, for example, Npcf_EventExposure_Subscribe responses.
  • the NEF network element sends a response message to the AF, for example, Npcf_PolicyAuthorization_Create response.
  • steps S406 and S407 can also be sent before step S403.
  • the first subscription event can be generated on the SMF network element and the UPF can be configured to detect AF application data packets in the manner shown in FIG. 4.
  • this embodiment provides a method for the UPF network element to send a notification to the SMF network element after detecting the AF application data packet, and the SMF network element to report the UE availability notification message to the AF,
  • This embodiment uses the process of the method as an example for description, as shown in FIG. 5, which includes:
  • S501 The AF sends downlink data, and the UE in FIG. 5 is the target UE corresponding to the AF.
  • the UPF network element sends a downlink data notification (Downlink Data Notification) to the SMF network element.
  • Downlink Data Notification may carry but is not limited to at least one of quality of service (Quality of Service Flow, QoS), ARP (Allocation and Retention Priority) and other information.
  • QoS Quality of Service Flow
  • ARP Allocation and Retention Priority
  • the UPF network element also detects that the AF is sending downlink data according to the application data packet, so it sends an N4 Report message to the SMF network element to report the detected Application ID (of course, in one example, the UPF network element can pass directly Data Notification reports the detected Application ID to SMF).
  • the SMF network element After the SMF network element receives the N4 Report message or Data Notification message, if the SMF network element already knows that the target UE corresponding to the AF corresponding to the Application ID is in an unreachable state, the SMF network element sets the notification flag of the AF to yes, Among them, the notification flag and NEF_reference_ID1 are associated. If the SMF network element already knows that the target UE corresponding to the AF corresponding to the Application ID is in a reachable state, the notification flag of the AF may be set to no. And optionally, the SMF network element can also clear the Application ID.
  • S503 If the SMF network element does not know that the user is in an unreachable state, the SMF network element requests the AMF network element to instruct the AMF network element to page the target UE (see, for example, S5031 in FIG. 5, at this time DDN failure).
  • the AMF network element determines that the paging target UE has no response or fails, and the AMF network element sends a DDN failure response to the SMF network element.
  • S505 SMF learns that the user is currently unreachable, and then sends a message to AMF to request the subscription of user reachability notification. After AMF receives it, it sets a second notification identifier UEAvailabilityNotifySMFflag associated with the SMF network element in S503. "Yes" is used to indicate that the SMF network element needs to be notified when the target UE status becomes available. In another example, the subscription request may also be carried in step S503, so that the SMF does not need to resend the subscription message to the AMF.
  • S506 In S5061, the AMF network element detects that the state of the target UE becomes available, and the AMF network element sends a UE status reachable notification message to the SMF network element according to the second notification identifier UE, Availability, Notify, SMF, flag set in S505.
  • the SMF network element determines the AF to be notified according to the first notification identifier notification flag, and sends the UE status reachable notification message to the NEF network corresponding to the NEF ID according to the event reference identifiers NEF_Reference_ID1 and NEFID of the first subscription event
  • the SMF network element may be implemented by sending Nsmf_EventExposure_Notify to the NEF network element.
  • the NEF network element sends the UE reachability notification to the AF corresponding to the Application ID after the received downlink data fails.
  • the NEF network element may be implemented by sending Nnef_EventExposure_Notify to the AF.
  • This embodiment also provides a message notification device, which can be set in an SMF network element, as shown in FIG. 6, which includes:
  • the third event subscription processing module 601 receives the first request for generating a first subscription event that monitors the reachability of the target UE, and generates a first subscription event that monitors the reachability of the target UE, that is, the UE that subscribes to the target UE. DDN failed event.
  • the first request includes the event reference identifier of the associated first subscription event, the application ID of the third-party application AF, and the NEF ID of the network open function NEF network element.
  • the third event subscription processing module 601 generates The first subscription event of is associated with the event reference identifier of the first subscription event in the first request.
  • the NEF network element may trigger a first request for generating a first subscription event for monitoring the reachability state of the user equipment UE to the session management function SMF network element according to the request of the third-party application AF, In order for the SMF network element to generate the first subscription event for monitoring the reachability of the UE.
  • the event reference identifier of the first subscription event included in the first request may be generated by the NEF network element.
  • the request sent by the NEF network element may include, but is not limited to, the following request: an event open subscription request from AF, such as, but not limited to, Event Exposure_Subscribe request.
  • the first request received by the third event subscription processing module 601 includes at least one of the following requests:
  • Event open subscription requests from UDM Unified Data Management
  • UDM Unified Data Management
  • Session policy control update notification request from PCF Policy Control Function
  • PCF Policy Control Function
  • the fifth notification sending module 602 is used to receive the UE reachability notification after the downlink data of the target UE fails. According to the first subscription event generated by the third event subscription processing module 601, the UE reachability notification is sent to the first after the downlink data fails.
  • the NEF network element corresponding to the NEF ID associated with a subscription event for the NEF network element to send to the AF corresponding to the Application ID according to the association relationship between the Application ID and the event reference identifier of the first subscription event.
  • the UPF network element may also be configured to perform application packet detection, that is, the application ID is activated on the UPF network element Application packet inspection.
  • the third event subscription processing module 601 may deliver the PFD (Packet Flow Description) corresponding to the Application ID to the UPF network element.
  • the third event subscription processing module 601 may also deliver the Application ID to the UPF network element.
  • the UPF network element may perform application packet detection according to the locally configured PFD corresponding to the Application ID.
  • the third event subscription processing module 601 can use the first notification identifier to control whether each first subscription event needs to report downlink data after the UE fails to be notified. Therefore, in this embodiment, in one example, when the third event subscription processing module 601 generates a first subscription event that monitors the reachability of the UE, it further includes: generating a first notification identifier, such as notification flag, and setting the generated first notification identifier and first request The event reference identifier association of the first subscription event in.
  • a first notification identifier such as notification flag
  • the value of the first notification identifier when the value of the first notification identifier can be set to a first preset value, it can be characterized that the first subscription event associated with the event reference identifier of the first subscription event associated with the first notification identifier needs to report downlink data after the failure UE reachable notification. And optionally, when the value of the first notification identifier is not the first preset value, the first subscription event associated with the event reference identifier of the first subscription event associated with the first notification identifier does not need to be reported After the downlink data fails, the UE can be notified.
  • the third event subscription processing module 601 may not temporarily set the value for the generated first notification identifier, or directly default to the first preset value . It can also be flexibly set according to specific application scenarios.
  • the third event subscription processing module 601 may set the value of notification flag in but not limited to the following example manner. For example, before the third event subscription processing module 601 receives the reachable notification, the third event subscription processing module 601 receives the application data detection notification including the corresponding Application ID sent by the UPF network element, and determines that the AF corresponding to the Application ID is required When the delivered target UE is currently unreachable, the first notification identifier corresponding to the Application ID may be set as the first preset value.
  • the downlink application data detection notification in this embodiment includes but is not limited to: at least one of the N4 Report message and the Data Notification message.
  • the fifth notification sending module 602 before the fifth notification sending module 602 sends the UE reachable notification after the downlink data fails to the NEF network element corresponding to the NEF ID, it can also be used to determine whether the first notification identifier is currently The first preset value, if so, sends the UE reachability notification to the NEF network element corresponding to the NEF ID after the downlink data fails, for the NEF network element to associate the relationship between the application ID and the event reference identifier of the first subscription event, After the downlink data fails, the UE reachability notification is sent to the AF corresponding to the Application ID.
  • the AMF network element may also control whether it is necessary to send a reachable notification to the third event subscription processing module 601 by setting a notification identifier. For example, when the AMF network element pages the UE according to the request of the SMF network element, if the user is unreachable and a subscription request for the user reachability notification of the SMF network element is received, a second associated with the SMF network element may be set.
  • the notification identifier UE, Availability, Notify, SMF, flag, and the value of the UE, Availability, Notify, SMF, flag can also be set as the first preset value, indicating that it needs to be reported to the associated SMF, that is, indicating that the target UE's status changes from unreachable unreachability When the availability is reached, the associated SMF needs to be notified.
  • the reachability notification received by the fifth notification sending module 602 may be that the AMF network element detects that the state of the target UE changes from unreachable unreachability to reachable availability.
  • the second notification identifier such as UE Availability Notify SMF flag, when the current value is the first preset value, the AMF sends it to the SMF.
  • the second notification identifier UE, Availability, Notify, SMF, flag is set after the AMF network element detects that the state of the target UE is unreachable and receives the SMF event subscription message.
  • the functions of the third event subscription processing module 601 and the fifth notification sending module 602 can be implemented by, but not limited to, the processor or controller of the SMF network element.
  • the message notification device provided in this embodiment, the downlink data After the failure, the UE reachability notification is only sent to the AF that sent the downlink data service demand, rather than to all AFs that have subscribed to the first subscription event of the UE reachability state, which improves the targetedness of the UE reachability notification after the downlink data fails And intelligence, as well as improved network resource utilization.
  • the message notification method provided in this embodiment, on the NEF network element side, as shown in FIG. 7, may include but not limited to the following steps:
  • S701 Receive a request sent by the AF for a UE reachable event (that is, UE availability after DDN failure) after a failure to subscribe to downlink data.
  • the request message may include a target UE ID and an application ID Application ID.
  • the AF may also send a request for a UE reachable event after subscribing to downlink data fails through various interactive messages with the NEF network element.
  • S702 According to the received request, send a first request to the AMF network element for the UE reachable event after subscribing to the downlink data fails, and send a second request to the SMF network element for the subscription application data detection event (that is, the downlink data packet detection event) .
  • the execution order of the NEF network element sending the first request to the AMF network element and the second request sending to the SMF network element is not strictly limited, the two can be executed in parallel, or the first request can be sent to the AMF network element first , And then send the second request to the SMF network element; or send the second request to the SMF network element first, and then send the first request to the AMF network element.
  • the first request may include, but is not limited to, the application ID of the AF and the NEF ID of the NEF network element. Their functions are as shown above, and will not be repeated here.
  • the second request may also include the AF application identification and the NEF network element identification NEF ID, so that the second subscription event detected by the SMF network element based on the application data generated by the second request can be related to the AF application identification and NEF network element Identify the NEF ID association, so that the SMF network element can instruct the UPF network element to activate the application data detection (ie, downlink data packet detection) of the AF corresponding to the corresponding application identifier according to the second subscription event; and upon receiving the detection sent by the UPF
  • the corresponding second subscription event is determined according to the application identifier in the notification and the above-mentioned association relationship, so that the corresponding NEF ID is sent to the corresponding second subscription event according to the determined second subscription event and the above-mentioned association relationship
  • the first request for the UE reachable event after failure to subscribe to the downlink data to the AMF network element may include, but is not limited to, the following method: through UDM (Unified Data Management) event opening subscription request to the network element
  • UDM Unified Data Management
  • sending the second request for subscription application data detection to the SMF network element may include but is not limited to at least one of the following ways: sending the second request to the SMF network element through the event open subscription request of the UDM network element;
  • the policy control function PCF network element's session policy control update notification request sends a second request to the SMF network element.
  • S703 Receive the application data detection notification sent by the SMF network element, and store the application identifier in the application data detection notification in the application identifier list.
  • this embodiment is not limited to storing / caching the application identification in the application data detection notification (that is, the application identification of each AF that has sent the downlink data) through the application identification list.
  • the application identification list may use various lists that can be used to store identification information.
  • S704 The UE reachable notification after receiving the downlink data sent by the AMF network element fails.
  • the UE reachability notification after the failure of the downlink data may include the application identification of the AF corresponding to the UE that becomes unreachable and becomes reachable.
  • S705 The UE reaches the notification after sending downlink data to the AF corresponding to the application identifier included in the application identifier list.
  • the UE reachability notification after failure to send downlink data to the AF corresponding to the application identifier included in the application identifier list includes but is not limited to one of the following:
  • the application identifier list may be cleared after transmission.
  • the corresponding target UE may be reachable by itself when it sends downlink data.
  • the UE will not be reachable after sending downlink data to the UE.
  • a clearing mechanism may be used to clear its application identifier from the above-mentioned application identifier list.
  • the application data detection notification sent by the SMF network element it may further include but not limited to:
  • S801 Send a third request to subscribe to the UE reachable event to the AMF network element.
  • the UE reachable event in this embodiment refers to one of two methods: Method 1: When detecting whether the UE is currently reachable, the UE does not care about its previous state. That is, before detecting whether the UE corresponding to the application identifier in the application data detection notification is reachable, the UE may be in a reachable state or may be in an unreachable state, and during the detection or after the detection is started, The UE is changed from unreachable to reachable; no matter what the situation is, as long as the UE is detected as reachable, the UE reachability notification is fed back.
  • Method 1 When detecting whether the UE is currently reachable, the UE does not care about its previous state. That is, before detecting whether the UE corresponding to the application identifier in the application data detection notification is reachable, the UE may be in a reachable state or may be in an unreachable state, and during the detection or after the detection is started, The UE is changed from unreachable to reachable; no matter what the situation
  • Method 2 When the UE detects whether the current state is reachable, if the current state of the UE is reachable, the UE is notified of the reachability notification; if the current state of the UE is unreachable, the UE is notified of the unreachability notification.
  • clearing the application identification list includes but is not limited to one of the following:
  • the UE reachability notification sent by an AMF network element to a certain UE may be sent when the UE changes from unreachable to reachable, or it may be that the UE itself is in Sent when reachable (that is, no DDN failure event occurs). Therefore, in order to avoid erroneously clearing the AF corresponding to the UE from the unreachable state to the reachable state, this embodiment may also adopt an identification mechanism to avoid the above-mentioned situation. For example, as shown in FIG. 9 for an identification process, after receiving the UE reachability notification sent by the AMF network element, before clearing the application identifier included in the application identifier list, it may further include:
  • S901 Time starts when the UE reachability notification is received.
  • the NEF network element may set a timer, and the timer is used for timing.
  • the UE reachability notification after the failure of the downlink data is sent to the AF corresponding to the application identifier included in the application identifier list.
  • This embodiment also provides a message notification device that can be installed in the NEF network element. Of course, it can also be installed in other network elements that can communicate with the AF.
  • the modules included in the message notification device can be implemented but are not limited to the above
  • the corresponding functions in the method, and the functions of each module may be implemented by, but not limited to, a processor or controller of a network element.
  • the message notification device in this embodiment includes but is not limited to:
  • the second request receiving module 1001 is configured to receive a request sent by the AF for a UE reachable event after failing to subscribe to downlink data.
  • the second event subscription request module 1002 is used to send the first request for the UE reachable event to the AMF network element according to the request received by the second request receiving module 1001 and fails to send the subscription application data detection event to the SMF network element Second request.
  • the second notification receiving module 1003 is used to receive the application data detection notification sent by the SMF network element, store the application identifier in the application data detection notification in the application identifier list; and used to receive the downlink data sent by the AMF network element after failure UE reachable notification.
  • the second notification sending module 1004 is configured to send a notification that the UE is reachable after the downlink data fails to the AF corresponding to the application identifier included in the application identifier list. Optionally, it may be further used to clear the application identifier list.
  • the second event subscription request module 1002 may also be used to send a third request to subscribe to the UE reachable event to the AMF network element.
  • the second notification receiving module 1003 can also be used to clear the application identifier included in the application identifier list when receiving the UE reachable notification sent by the AMF network element.
  • the second notification receiving module 1003 may be further configured to, after receiving the UE reachability notification sent by the AMF network element, clear the application ID included in the application ID list, and receive the UE The timer starts when the notification is reached.
  • the second notification receiving module 1003 can also be used to clear the application identifier included in the application identifier list if the UE reaches the notification after the failure of receiving the downlink data when the timing value reaches the set time value; if the downlink data is received After the failure, the UE reachability notification may be sent to the AF corresponding to the application identifier through the second notification sending module 1004 after the downlink data fails to be sent.
  • the message notification method provided in this embodiment, on the AMF network element side, as shown in FIG. 11, may include but not limited to the following steps:
  • S1101 Receive a first request sent by an NEF network element for a UE reachable event after a failure to subscribe to downlink data, and generate a first subscription event for the UE reachable after a downlink data failure according to the first request.
  • the first request may include the application ID of the AF and the NEF ID of the NEF network element
  • the first subscription event may be associated with the application ID of the AF in the first request and the NEF ID of the NEF network element
  • an associated event reference identifier of the first subscription event may also be generated for the first subscription event, so as to facilitate management of each first subscription event.
  • the UE reachability notification may also include the event reference identifier of the corresponding first subscription event after the downlink data sent fails, so that the receiver can The event reference identifier of a subscription event identifies that the received notification corresponds to the notification corresponding to the first subscription event.
  • the UE reachability notification is sent to the NEF network element after the downlink data fails, and the UE reachability notification may include an application identifier after the downlink data fails.
  • the AMF network element may, according to the first subscription event, when detecting that the target UE corresponding to the first subscription event changes from unreachable to reachable, send the corresponding message to the NEF ID corresponding to the first subscription event.
  • the UE reachability notification may be included.
  • the UE reachability notification may include the application identifier corresponding to the first subscription event.
  • the message notification method provided in this embodiment is shown in FIG. 12, and may also include but not limited to the following steps:
  • S1201 Receive a third request for subscription to the UE reachability event sent by the NEF network element, and generate a third subscription event for the UE reachability according to the third request.
  • the third request may include an application identifier in the application data detection notification.
  • S1202 When detecting that the target UE in the third request is reachable according to the third subscription event, send a UE reachability notification to the NEF network element.
  • the AMF network element detects that the UE is reachable.
  • the UE may change from unreachable to reachable, or the UE may itself be reachable when the corresponding AF sends downlink data.
  • an event reference identifier of the associated third subscription event may also be generated for the third subscription event, so as to facilitate management of each third subscription event.
  • the sent UE reachability notification may include the event reference identifier of the corresponding third subscription event, so that the receiver can use the event reference of the third subscription event. The identifier recognizes that the received notification corresponds to the notification corresponding to the third subscription event.
  • This embodiment also provides a message notification device that can be installed in an AMF network element. Of course, it can also be installed in other network elements that can directly or indirectly detect the reachability state of the UE.
  • Each module included in the message notification device can Realize but not limited to the corresponding function in the above method, and the function of each module can be realized by but not limited to the processor or controller of the network element. Referring to FIG. 13, the message notification device in this embodiment includes but is not limited to:
  • the third request receiving module 1301 is configured to receive a first request sent by a NEF network element for a UE reachable event after a failure to subscribe to downlink data.
  • the first request includes an AF application identifier and the NEF network element identifier NEF ID.
  • the first event subscription processing module 1302 is configured to generate a first subscription event that the UE can reach after the downlink data fails according to the first request received by the third request receiving module 1301.
  • the third notification sending module 1303 is configured to send the UE reachable notification after the downlink data fails to the NEF network element when it detects that the UE corresponding to the application identifier changes from unreachable to reachable according to the first subscription event.
  • the UE reachability notification includes the application identifier.
  • the third request receiving module 1301 may be further configured to receive a third request sent by the NEF network element to subscribe to the UE reachability event; the third request includes the application identifier in the application data detection notification.
  • the first event subscription processing module 1302 may also be used to generate a third subscription event reachable by the UE according to the third request.
  • the third notification sending module 1303 may be further configured to send a UE reachable notification to the NEF network element when detecting that the UE corresponding to the application identifier in the third request is reachable according to the third subscription event.
  • the message notification method provided in this embodiment, on the SMF network element side, as shown in FIG. 14, may include but not limited to the following steps:
  • S1401 Receive a second request for subscription application data detection event sent by the NEF network element, and generate a second subscription event for application data detection according to the second request.
  • the second request includes the AF application ID and the NEF network element ID NEF ID .
  • an associated event reference identifier of the second subscription event may also be generated for the second subscription event to facilitate management of each second subscription event.
  • the subsequent application data detection notification may include the event reference identifier of the corresponding second subscription event, so that the receiver can use the event reference identifier of the second subscription event It is recognized that the received notification is a notification corresponding to the second subscription event.
  • S1402 Instruct the UPF network element to activate the application data detection of the AF corresponding to the application identifier according to the second subscription event.
  • the UPF network element can perform application data detection on the corresponding AF according to the instruction, that is, downlink data packet detection.
  • S1403 Receive an application data detection notification sent by the UPF network element, where the application data detection notification includes the application identification of the AF that detects that the downlink data has been sent.
  • S1404 Send the received application data detection notification to the NEF network element.
  • This embodiment also provides a message notification device that can be installed in an SMF network element. Of course, it can also be installed in other network elements that can directly or indirectly detect AF downlink data.
  • the modules included in the message notification device can be Realize but not limited to the corresponding function in the above method, and the function of each module can be realized by but not limited to the processor or controller of the network element.
  • the message notification device in this embodiment includes but is not limited to:
  • the fourth request receiving module 1501 is configured to receive a second request sent by the NEF network element to subscribe to the application data detection event, where the second request includes the AF application ID and the NEF ID of the NEF network element.
  • the second event subscription processing module 1502 is used to generate a second subscription event for application data detection according to the second request, and to instruct the UPF network element to activate the application data detection corresponding to the AF corresponding to the application identifier according to the second subscription event.
  • the fourth notification sending module 1503 is configured to receive the application data detection notification sent by the UPF network element, and send the application data detection notification to the corresponding NEF network element (that is, the NEF network element corresponding to the application identifier in the notification), application data
  • the detection notification includes the application identification of the AF that has detected the downlink data.
  • this embodiment uses a UE reachable event (that is, UE availability after DDN failed event) and an AF application data activated to the SMF network element after subscribing to downlink data on the AMF network element fails
  • UE reachable event that is, UE availability after DDN failed event
  • the method of packet inspection is illustrated as an example.
  • FIG. 16 an example is shown in FIG. 16 and includes:
  • Each AF can subscribe to the UE availability event after sending a request to the NEF network element (hereinafter referred to as an event subscription request). For example, the AF can send a Nnef_EventExposure_Subscribe request to subscribe to the UE ’s UE corresponding to the AF.
  • the availability of the DDN failure event which The Nnef_EventExposure_Subscribe request may include an indication of subscribing to the UE, Availability, After DDN failure event, and AF application identification.
  • the Nnef_EventExposure_Subscribe request may also include the target UE identification corresponding to the AF.
  • the target UE identifier may indicate a single user or a group of users.
  • the target UE identity may include an IP address.
  • the AF application identification refers to information that can be used to characterize the identity of the AF, such as Application ID, port information, and IP address information.
  • the NEF network element After receiving the Nnef_EventExposure_Subscribe request of each AF, the NEF network element can generate an event reference identifier NEF_reference_ID, which can be associated with the Application ID in the Nnef_EventExposure_Subscribe request.
  • the NEF network element finds the UDM network element according to the target UE identifier in the event subscription request, and generates a subscription event to the UDM network element; for example, the NEF network element may send a Nudm_EventExposure_Subscribe request (that is, an example first request) to the UDM network element.
  • the Nudm_EventExposure_Subscribe request may include an instruction to subscribe to the Availability after DDN failure event, AF Application ID, NEF_reference_ID, and optionally, the Nudm_EventExposure_Subscribe request may also include the NEF ID of the NEF network element.
  • the UDM network element finds the corresponding AMF network element and subscribes to the UE's availability after DDN failure event. For example, the UDM network element may send a Namf_EventExposure_Subscribe request (that is, an exemplary first request sending method) to the AMF network element.
  • UE availability indication after DDN failure event Application ID, NEF ID, NEF_reference_ID (that is, the event reference identifier of the first subscription event); the AMF network element can generate the first subscription event according to the Namf_EventExposure_Subscribe request.
  • the UDM network element finds the user-related session context according to the target UE ID, finds the user-registered SMF (home network roaming situation, hSMF or home SMF) network element within the user context, and then applies to the SMF network element Data detection event subscription.
  • the UDM network element may send an Nsmf_EventExposure_Subscribe request (that is, an example second request) to the SMF network element.
  • the Nsmf_EventExposure_Subscribe request may include an indication of a subscription application data detection event, Application ID, NEF ID, NEF_reference_ID (that is, the second subscription event Event reference identifier), the SMF network element generates a second subscription event according to Nsmf_EventExposure_Subscribe request.
  • the SMF network element is configured with UPF (in the home network roaming scenario, that is, hUPF or home UPF).
  • UPF in the home network roaming scenario, that is, hUPF or home UPF.
  • the network element performs AF packet detection corresponding to the Application ID.
  • the SMF network element activates the downlink packet detection for the Application ID on the UPF network element according to the Nsmf_EventExposure_Subscribe request of the UDM network element.
  • the SMF network element can send an N4 Session / Establishment / Modification Request (Application ID, PFD) to the UPF network element.
  • N4 Session Establishment / Modification Request the SMF network element can associate the PFD (Packet Flow Description) corresponding to the Application ID with the packet flow description. ) Issued to UPF.
  • the SMF can also send the Application ID to the UPF.
  • the UPF performs packet inspection according to the locally configured PFD corresponding to the Application ID.
  • S1606 The SMF network element sends a response message to the UDM network element, for example, Nsmf_EventExposure_Subscribe responses.
  • the UDM network element sends a response message to the NEF network element, such as Nudm_EventExposure_Subscribe responses.
  • NEF network element sends a response message to the AF, for example, Nnef_EventExposure_Subscribe responses.
  • the second subscription event for detecting the application packet generated in the SMF network element may also be implemented, including:
  • Each AF can subscribe to an event by sending a request to NEF network elements (hereinafter referred to as an event subscription request), for example, the AF can send a Nnef_EventExposure_Subscribe request to subscribe to the application data detection event corresponding to the AF, and the Nnef_EventExposure_Subscribe request can include the AF application identification Application ID and corresponding UE information (for example, including but not limited to the IP address of the UE).
  • the NEF network element After receiving the Nnef_EventExposure_Subscribe request of each AF, the NEF network element can generate an event reference identifier NEF_reference_ID, which can be associated with the Application ID in the Nnef_EventExposure_Subscribe request.
  • the NEF network element finds the IP address of the UE in the event subscription request, or the information of DNN (Data Network Name) and S-NSSAI (subscribed-Network Slice Selection Assistance Information, signed network slice selection auxiliary information) information.
  • the PCF network element of the PDU session related to the UE requests an application data detection event subscription from the PCF network element.
  • NEF may send a Npcf_PolicyAuthorization_Subscribe subscription request, and the request message carries the event reference identifier, application identifier Application ID, and NEF network element identifier.
  • the NEF network element If the NEF network element does not find the PCF network element of the user ’s UE-related session, the NEF saves the subscription event in the UDR (Unified Data Repository, unified data storage). When the user creates a PDU session, the PCF network element will then remove the UDF from the UDR Receive the subscription event.
  • UDR Unified Data Repository, unified data storage
  • the PCF network element issues a policy control and charging rule (PCC rule) to the SMF network element, requesting to report an application data detection event, and the PCC rule contains the Application ID, event reference identifier, and NEF network element identifier that need to be detected.
  • PCC rule policy control and charging rule
  • the session policy control update notification request message Npcf_SMPolicyControl_UpdateNotify sends the PCC rule to the SMF network element.
  • the SMF network element creates application data to detect a subscription event (that is, the second subscription event), and the event includes the event reference identifier of the second subscription event and the NEF network element identifier; at the same time, the SMF network element sends a UPF to the UPF
  • the network element performs application data detection for the AF corresponding to the Application ID.
  • the SMF network element can send an N4 Session / Establishment / Modification Request (Application ID, PFD) to the UPF network element.
  • the SMF network element can describe the PFD (Packet Flow Description) corresponding to the Application ID in the packet flow ) Issued to UPF.
  • SMF can also send the Application ID to UPF.
  • UPF performs packet inspection according to the locally configured PFD corresponding to the Application ID
  • FIG. 18 a schematic diagram of a notification flow of a UE reachability notification message, as shown in FIG. 18, including:
  • the hUPF network element (hUPF for short) performs application data detection according to the PDF.
  • S1801 The AF sends downlink data to the hUPF network element.
  • the hUPF network element detects the downlink data sent by the AF corresponding to the Application ID, and sends an N4 report or Data Notification message to notify the hSMF network element.
  • NEF NEF network element
  • Nsmf_EventExposure_Notify Application ID
  • NEF saves the Application ID to Application ID list corresponding to the detected AF. If NEF receives hSMF notification including multiple Application IDs, it can be directly saved to the Application ID list. If subsequent hSMF continues to report the detected Application ID, NEF The network element adds the subsequent Application ID to the above Application ID list.
  • the NEF generates a new NEF_Reference_ID (that is, the event reference event identifier of the third subscription event), and sends a UE reachable monitoring subscription event request to the UDM network element (hereinafter referred to as UDM).
  • NEF_Reference_ID that is, the event reference event identifier of the third subscription event
  • the UDM receives the NEF request message, and sends a request to the AMF to subscribe to the UE reachable status event Namf_EventExposure_subscribe (UE reachability (reachability status), NEF ID, NEF_Reference_ID), which is the third subscription event.
  • Namf_EventExposure_subscribe UE reachability (reachability status), NEF ID, NEF_Reference_ID
  • vUPF caches downlink data, and sends data notification Data to Notification to visit SMF (vSMF or visit SMF), then vSMF sends data notification to AMF.
  • S1809 AMF paging (targeting UE).
  • AMF sends a UE reachable notification message to NEF Namf_EventExposure_notify.
  • NEF receives the UE reachable notification of the third subscription event, indicating that the user is currently reachable, and all downlink data can be sent to the UE without DDN Failure, so there is no need to notify AF, so NEF clears the Application in S1804 ID list.
  • NEF when receiving the notification message of the third subscription event, NEF cannot determine whether it is the message received by S1812 or S1816, so when the NEF network element receives the third subscription
  • the event message can be the same as S1816.
  • Set a timer locally Before the timer times out, if the notification of the first subscription event is not received, clear the Application ID list in S1804; if the timer receives the first (Subscribe to event notification, it will be processed according to S1816).
  • vSMF may instruct vUPF to discard or save downstream data.
  • the AMF detects that the UE is reachable.
  • the AMF sends a UE reachability notification message Namf_EventExposure_notify (UE reachability) to the NEF according to the third subscription event.
  • AMF judges that the user is currently UE availability after DDN Failure, AMF sends UE Availablility after DDN Failure to NEF Namf_EventExposure_notify (UE availability after DDN failure) according to the first subscription event.
  • S1816 If the NEF network element receives the first available subscription event UE availability after DDN failure, the NEF sends the UE availability availability after DDN failure event to the corresponding AF in the Application ID list saved in S1804. Because S1814 and S1815 may be sent from the AMF at the same time, if NEF first receives the user reachable notification of the third subscription event, NEF can set a timer locally, before the timer expires, if the event of the first subscription event is received If the notification is sent to the AF, the UE availability after DDN failure event is sent; if the notification of the first subscription event is not received before the timer times out, it means that the notification of S1812 is received and it is handled in accordance with S1812.
  • NEF sends UE availability after DDN failure notification message to AF.
  • This embodiment provides a message notification method.
  • the target network element fails to generate downlink data according to the first request, the first subscription event and the first subscription event of the UE reachability event (that is, UE availability after DDN failed event) after the downlink data generation fails
  • the application ID of the AF in the first request that is, Application ID, and it should be understood that the application ID in this embodiment may be a unique identifier / any information that identifies AF) is associated;
  • the target network element detects a subscription
  • the target UE reachability notification that is, a UE reachability notification message
  • the NEF network element can send the UE reachability notification message to the AF corresponding to the application identifier in a targeted manner; improve the rationality of sending UE reachability notification messages and Network resource utilization
  • this embodiment is described in conjunction with the flow of a message notification method as an example.
  • the method flow on the NEF network element side is used for description.
  • the following method steps are not limited to NEF network elements, but can also be performed by other network elements that can communicate with AF.
  • the message notification method in this example is shown in FIG. 19, and may include but not limited to:
  • S1901 Receive a request sent by the AF for a UE reachable event (UE availability after DDN failed event) after a failure to subscribe to downlink data.
  • the AF may send a request for a UE reachable event after subscribing to downlink data fails through various interactive messages (including signaling) with the NEF network element, such as but not limited to Nnef_Event Exposure_Subscribe request.
  • the request sent by the AF for the UE reachable event after failing to subscribe to the downlink data may include the application ID of the AF, or may not include the application ID of the AF, and after the NEF network element receives the request, according to the The sender of the request extracts the application ID of the AF.
  • S1902 According to the request received in S1901, send a first request to the target network element after the UE fails to subscribe to the downlink data, and the first request includes the NEF ID of the NEF network element (it should be understood that in this embodiment
  • the NEF ID can be any information that uniquely identifies / identifies NEF network elements) and the application identification of AF.
  • the first subscription event is associated with the NEF ID of the NEF network element and the application ID of the AF; when the subsequent target network element detects that a UE changes from unreachable to reachable, it can use the corresponding association relationship
  • the application ID of the AF corresponding to the UE and the NEF ID corresponding to the application ID of the AF are determined, thereby determining the NEF network element to which the AF is connected, so that the UE reachability notification is sent to the corresponding after the downlink data of the UE fails On the NEF network element.
  • the target network element may include but is not limited to at least one of an AMF network element and an SMF (Session Management Function) session element.
  • the target network element may also be another network connection capable of detecting the UE reachability state or communicating with the network element capable of detecting the UE reachability state.
  • Any network element such as UDM (Unified Data Management) network element, PCF (Policy Control Function, policy control function) network element, etc.
  • the UE reachability notification after the failure of receiving the downlink data sent by the target network element includes the application identification of the AF corresponding to the UE that becomes unreachable.
  • the UE reachability notification after the failure of the downlink data is sent when the target network element detects that the target UE corresponding to an AF subscribed to the first subscription event changes from unreachable to reachable.
  • the reachable state of the UE may be directly detected by the target network element, or may be detected by other network elements, and the detection result is sent to the target network element, so that the target network element determines the reachable state of the UE according to the detection result.
  • S1904 Send the UE reachability notification after the downlink data fails to the AF corresponding to the application identifier included in the UE reachability notification after the received downlink data fails; for other AFs, the UE reachability notification after the downlink data failure is not sent, thereby It can not only meet the communication needs, but also improve the utilization rate of network resources.
  • FIG. 20 On the target network element side, the flow of the message notification method is shown in FIG. 20, which may include but is not limited to:
  • S2001 Receive a first request sent by a NEF network element for a UE reachable event after a failure to subscribe to downlink data, and generate a first subscription event for the UE reachable after a downlink data failure according to the first request.
  • the first request includes the application ID of the AF and the NEF ID of the NEF network element
  • the first subscription event may be associated with the application ID of the AF and the NEF ID of the NEF network element in the first request.
  • the target network element may, according to the first subscription event, detect that the UE corresponding to the application identifier corresponding to the first subscription event changes from unreachable to reachable, and then report to the NEF corresponding to the first subscription event
  • the NEF network element corresponding to the ID fails to send the downlink data after the downlink data is sent, and the UE reachable notification after the sent downlink data fails includes the application identifier corresponding to the first subscription event.
  • the target network element in this embodiment may include but is not limited to at least one of an AMF network element and an SMF network element. And in some examples, UDM network elements, PCF network elements, etc. may also be used, but not limited to.
  • This embodiment also provides a message notification device, which can be installed in the NEF network element or other network elements that can communicate with the AF.
  • the modules included in the message notification device can be implemented but not limited to the above
  • the corresponding functions in the method, and the functions of each module may be implemented by, but not limited to, a processor or controller of a network element. As shown in FIG.
  • the message notification device in this embodiment includes, but is not limited to: a first request receiving module 2101, configured to receive a request sent by the AF for a UE reachable event after failing to subscribe to downlink data; a first event subscription
  • the request module 2102 is configured to send a first request for a UE reachable event after a failure to subscribe to downlink data to the target network element according to the request received by the first request receiving module 2101, the first request includes an identifier NEF of the network open function NEF network element ID and the application identification of the AF;
  • the first notification receiving module 2103 is used to receive the UE reachability notification after the downlink data sent by the target network element fails, and the UE reachability notification after the downlink data fails includes the change from unreachable to reachable
  • the first notification sending module 2104 is used for the UE reachable notification after the AF corresponding to the application ID included in the UE reachable notification after the downlink
  • a notification message of UE reachability can be sent to the AF in a targeted manner.
  • all AFs that have reached the UE reachability event after failing to subscribe to downlink data are sent directly to the AF.
  • Notification messages can improve communication accuracy, reliability, and network resource utilization.
  • This embodiment also provides an SMF network element, as shown in FIG. 22, including a first processor 2201, a first memory 2202, and a first communication bus 2203; the first communication bus 2203 is used to connect the first processor 2201 and The first memory 2202 is connected; the first processor 2201 is used to execute the first computer program stored in the first memory 2202 to implement but is not limited to the message notification method shown in the first embodiment; or, the first processor 2201 is used Execute the second computer program stored in the first memory 2202 to implement but not limited to the message notification method as shown in the eighth embodiment above.
  • This embodiment also provides an NEF network element, as shown in FIG. 23, including a second processor 2301, a second memory 2302, and a second communication bus 2303; the second communication bus 2303 is used to connect the second processor 2301 and The second memory 2302 is connected; the second processor 2301 is used to execute a third computer program stored in the second memory 2302 to implement but is not limited to the message notification methods shown in Embodiments 6 to 7 above; or, The second processor is used to execute the fourth computer program stored in the second memory to implement the message notification method as shown in the eighth embodiment.
  • This embodiment also provides an AMF network element, as shown in FIG. 24, including a third processor 2401, a third memory 2402, and a third communication bus 2403; the third communication bus 2403 is used to connect the third processor 2401 and The third memory 2402 is connected; the third processor 2401 is used to execute the fifth computer program stored in the third memory 2402 to implement but is not limited to the message notification methods shown in Embodiment 6 to Embodiment 7 above; or, the first The three-processor 2401 is used to execute the sixth computer program stored in the third memory 2402 to implement but not limited to the steps of the message notification method as shown in the eighth embodiment above.
  • This embodiment also provides a communication system, including a target network element and a NEF network element; the target network element may be an AMF network element or an SMF network element.
  • the target network element is used to receive the first request of the UE reachability event after failing to subscribe to the downlink data, and generate a first subscription event of the UE reachability after the failure of the downlink data according to the first request.
  • the first request includes the AF application ID and the NEF network
  • the element ID NEF and the event reference ID of the first subscription event, the first subscription event is associated with the event reference ID of the first subscription event; and the UE reachability notification after receiving the downlink data of the target UE corresponding to the application ID fails,
  • the UE reachability notification is sent to the NEF network element after the downlink data fails; the NEF network element is used to send the downlink data to the AF corresponding to the application ID included in the UE reachability notification after the downlink data fails. Notice.
  • This embodiment also provides a computer-readable storage medium that is implemented in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules, or other data) Volatile or non-volatile, removable or non-removable media.
  • Computer-readable storage media include but are not limited to RAM (Random Access Memory, random access memory), ROM (Read-Only Memory, read-only memory), EEPROM (Electrically Erasable Programmable read only memory, live erasable programmable read-only memory ), Flash memory or other memory technologies, CD-ROM (Compact Disc Read-Only Memory, CD-ROM), digital versatile disk (DVD) or other optical disk storage, magnetic box, magnetic tape, magnetic disk storage or other magnetic storage devices, Or any other medium that can be used to store desired information and can be accessed by a computer.
  • the computer-readable storage medium in this embodiment is used to store one or more first computer programs, and the one or more first computer programs may be executed by one or more processors to implement, for example, The message notification method in Embodiment 1 above; or, the computer-readable storage medium is used to store one or more second computer programs, and the one or more second computer programs may be executed by one or more processors to implement but not Limited to the message notification method shown in the eighth embodiment above; or, the computer-readable storage medium is used to store one or more third computer programs, and the one or more third computer programs may be executed by one or more processors to Implement, but not limited to, the message notification methods shown in the sixth to seventh embodiments above; or, the computer-readable storage medium is used to store one or more fourth computer programs, and one or more fourth computer programs may be used by one or more The processor executes to implement but is not limited to the message notification method shown in the eighth embodiment above; or, the computer-readable storage The medium is used to store one or more fifth computer programs, and the one or more fifth computer programs may be
  • This embodiment also provides a computer program (or computer software), which can be distributed on a computer-readable medium and executed by a computable device to implement at least the message notification method shown in the above embodiments One step; and in some cases, at least one step shown or described may be performed in an order different from that described in the above embodiment.
  • a computer program or computer software
  • This embodiment also provides a computer program product, which includes a computer-readable device, and the computer program as shown above is stored on the computer-readable device.
  • the computer-readable device may include the computer-readable storage medium shown above.
  • communication media generally contains computer readable instructions, data structures, computer program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery medium. Therefore, this application is not limited to any specific combination of hardware and software.

Abstract

Selon les modes de réalisation, la présente invention concerne un procédé et un appareil de notification de message, un élément de réseau, un système et un support de stockage. Le procédé de notification de message consiste à : recevoir une demande, envoyée par une fonction d'application (AF), d'abonnement à une disponibilité d'équipement d'utilisateur (UE) après un évènement d'échec de données de liaison descendante ; envoyer, à un élément de réseau de fonction de gestion d'accès (AMF) et selon la demande, une première demande d'abonnement à la disponibilité d'UE après l'évènement d'échec de données de liaison descendante, et envoyer, à un élément de réseau de fonction de gestion de session (SMF), une deuxième demande d'abonnement à un évènement de détection de données d'application ; recevoir une notification de détection de données d'application envoyée par l'élément de réseau de SMF, et stocker un identifiant d'application, dans la notification de détection de données d'application, dans une liste d'identifiants d'application ; recevoir une disponibilité d'UE après une notification d'échec de données de liaison descendante envoyée par l'élément de réseau d'AMF ; et envoyer, à une AF correspondant à l'identifiant d'application inclus dans la liste d'identifiants d'application, la disponibilité d'UE après la notification d'échec de données de liaison descendante.
PCT/CN2019/110392 2018-10-10 2019-10-10 Procédé et appareil de notification de message, élément de réseau, système et support de stockage WO2020073960A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201811178829 2018-10-10
CN201811178829.5 2018-10-10
CN201811341759.0 2018-11-12
CN201811341759.0A CN111031517A (zh) 2018-10-10 2018-11-12 消息通知方法、装置、网元、系统及存储介质

Publications (1)

Publication Number Publication Date
WO2020073960A1 true WO2020073960A1 (fr) 2020-04-16

Family

ID=70164902

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/110392 WO2020073960A1 (fr) 2018-10-10 2019-10-10 Procédé et appareil de notification de message, élément de réseau, système et support de stockage

Country Status (1)

Country Link
WO (1) WO2020073960A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102186162A (zh) * 2011-05-06 2011-09-14 电信科学技术研究院 一种终端可达状态的获取方法和设备
CN107623906A (zh) * 2016-07-13 2018-01-23 中兴通讯股份有限公司 网络系统
WO2018127147A1 (fr) * 2017-01-05 2018-07-12 Huawei Technologies Co., Ltd. Systèmes et procédés de gestion de sessions d'unités de données de protocole (pdu) respectueuse d'applications

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102186162A (zh) * 2011-05-06 2011-09-14 电信科学技术研究院 一种终端可达状态的获取方法和设备
CN107623906A (zh) * 2016-07-13 2018-01-23 中兴通讯股份有限公司 网络系统
WO2018127147A1 (fr) * 2017-01-05 2018-07-12 Huawei Technologies Co., Ltd. Systèmes et procédés de gestion de sessions d'unités de données de protocole (pdu) respectueuse d'applications

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZTE: "Update of Solution 39: UE availability after DDN failure for multiple AFs", SA WG2 MEETING #129, 9 October 2018 (2018-10-09), pages 2 - 1810323, XP051539309 *

Similar Documents

Publication Publication Date Title
US11523268B2 (en) Communications method and apparatus
WO2020098622A1 (fr) Procédé, appareil, élément réseau et système de notification de message et support de stockage
US11224084B2 (en) Method for registering terminal in wireless communication system and apparatus therefor
EP3860189B1 (fr) Procédé de migration d'ue, appareil, système et support d'informations
US9565634B2 (en) Data transmission method, apparatus, and system, network side device, and terminal device
US9125003B2 (en) Machine to machine service management device, network device, and method processing service system
KR102596924B1 (ko) 이벤트 통지 방법, 장치 및 저장매체
US11856469B2 (en) Communication method, communications apparatus, and communications system
WO2017079906A1 (fr) Procédé de sélection d'un réseau de service, équipement de réseau et équipement de gestion
EP2861000B1 (fr) Procédé et dispositif permettant de transmettre des données en liaison descendante
WO2019137286A1 (fr) Procédé et appareil d'indication pour un réseau de données local
WO2017173259A1 (fr) Procédés et fonction ngef pour la divulgation de services par tranche de réseau
JP2019521593A (ja) データ伝送方法、装置及び記憶媒体
EP3496432A1 (fr) Procédé et dispositif de communication
WO2020103403A1 (fr) Procédé et appareil pour la configuration de paramètres
US20130150008A1 (en) Method and apparatus for signaling trace
US10129079B2 (en) Telecommunications system and method
WO2011134370A1 (fr) Procédé de rapport d'événement de communication de type machine et système associé
WO2020073960A1 (fr) Procédé et appareil de notification de message, élément de réseau, système et support de stockage
US20220141648A1 (en) Methods and nodes for ue-to-ue event monitoring
WO2019154048A1 (fr) Procédé de communication dans un réseau nb-iot, appareil, et support de stockage
EP3895501A1 (fr) Double connectivité destinée à un ue
EP3547723B1 (fr) Procédé de transmission d'informations et sélecteur d'élément de réseau

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: 19871083

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 06.08.2021)

122 Ep: pct application non-entry in european phase

Ref document number: 19871083

Country of ref document: EP

Kind code of ref document: A1