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

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

Info

Publication number
WO2020098622A1
WO2020098622A1 PCT/CN2019/117385 CN2019117385W WO2020098622A1 WO 2020098622 A1 WO2020098622 A1 WO 2020098622A1 CN 2019117385 W CN2019117385 W CN 2019117385W WO 2020098622 A1 WO2020098622 A1 WO 2020098622A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
notification
event
request
application
Prior art date
Application number
PCT/CN2019/117385
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
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2020098622A1 publication Critical patent/WO2020098622A1/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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail

Definitions

  • the present disclosure relates to the field of communication technology.
  • AF Application Function
  • UE User Equipment
  • 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 subscription event after downlink data failure, hereinafter collectively referred to as This is the UE reachable event after the downlink data fails
  • an AF sends downlink data
  • the UPF User Plane Function
  • AMF Access Management Function
  • Yuan 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 changes from unreachable (unreachability) to reachable ( availability), the AMF will directly send a notification message of UE reachability to all AFs that have subscribed to a downlink data failure after a UE reachability event.
  • the AMF will directly send a notification message of UE reachability to all AFs that have subscribed to a downlink data failure after a UE reachability event.
  • not all AFs subscribed to the UE reachable status subscription event need to receive the notification message that the UE is reachable.
  • only the AF that sends the downlink data service requirement needs to receive the notification message that the UE is reachable. Therefore, it is not necessary to send a notification message of UE reachability to all AFs that have subscribed to the UE reachability event after the downlink data fails, and it also wastes network resources.
  • An aspect of the present disclosure provides a message notification method, including: receiving a first request of a user equipment (UE) reachable event after a failure to subscribe to downlink data, and generating a first UE reachable after a downlink data failure according to the first request Subscription event, the first request includes the application identifier of the associated third-party application (AF), the NEF ID of the network open function (NEF) network element, and the event reference identifier of the first subscription event; After the downlink data of the target UE corresponding to the application identifier fails, the UE reachability notification is sent to the NEF network element according to the first subscription event, after the downlink data fails.
  • AF application AF
  • NEF network open function
  • a message notification device including: a third event subscription processing module, configured to receive a first request for a UE reachable event after a failure to subscribe for downlink data, and generate a downlink data according to the first request after a failure
  • the first request includes the associated AF application ID, NEF network element ID NEF ID, and the event reference ID of the first subscription event
  • the fifth notification sending module uses After receiving the downlink data failure of the target UE corresponding to the application identifier, the UE reachability notification is sent to the NEF network element according to the first subscription event, after the downlink data failure.
  • Another aspect of the present disclosure provides a message notification method, including: receiving a request sent by an AF for a UE reachable event after failing to subscribe to downlink data; sending a first UE reachable event after failing to subscribe to downlink data to an AMF network element Request, and send a second request to subscribe to the application data detection event to the session management function (SMF) network element; receive the application data detection notification sent by the SMF network element, and store the application identifier in the application data detection notification in the application In the identification list; the UE reachability notification after receiving the downlink data sent by the AMF network element fails; and sending the UE reachability notification after the downlink data failure to the AF corresponding to the application identification included in the application identification list.
  • SMS session management function
  • Another aspect of the present disclosure provides a message notification method, including: receiving a second request for a subscription application data detection event sent by a NEF network element, and generating a second subscription event for application data detection according to the second request, the first
  • the second request includes the application ID of the AF and the NEF ID of the NEF network element; requests the UPF network element to activate the application data detection of the AF corresponding to the application ID; receives the application data detection notification sent by the UPF network element,
  • the application data detection notification includes the application identification of the AF that has detected the downlink data; the application data detection notification is sent to the NEF network element.
  • a message notification device including: a second request receiving module for receiving a request sent by an AF for a UE reachable event after a failure to subscribe to downlink data; a second event subscription request module for According to the request, send a first request to the AMF network element after the UE fails to subscribe to the downlink data, and send a second request to the SMF network element to subscribe to the application data detection event; a second notification receiving module is used to receive the The application data detection notification sent by the SMF network element, storing the application identifier in the application data detection notification in the application identifier list; and the UE reachability notification after receiving the downlink data sent by the AMF network element fails; second The notification sending module is configured to send the UE reachable notification after the downlink data fails to be sent to the AF corresponding to the application identifier included in the application identifier list.
  • a message notification device including: a fourth request receiving module, configured to receive a second request sent by a NEF network element to subscribe to an application data detection event, where the second request includes an AF application identification And the NEF ID of the NEF network element; a second event subscription processing module, configured to generate a second subscription event for application data detection according to the second request, and to request a UPF network element according to the second subscription event Activate application data detection of the AF corresponding to the application identifier; a fourth notification sending module, configured to receive an application data detection notification sent by the UPF network element, where the application data detection notification includes the detection that downlink data has been sent The AF application identifier sends the application data detection notification to the NEF network element.
  • Another aspect of the present disclosure provides a message notification method, including: receiving a request sent by an AF for a UE reachable event after a failure to subscribe to downlink data; sending a UE reachable after a failed subscription to a target network element according to the request
  • the first request of the event, the first request includes the NEF ID of the NEF network element and the application ID of the AF; after receiving the downlink data sent by the target network element, the UE is reachable and the downlink data fails
  • the post-UE reachability notification includes the application ID of the AF corresponding to the UE that has become unreachable; after sending the downlink data to the AF corresponding to the application ID included in the UE reachability notification after the downlink data fails, the UE may Notice.
  • a message notification device including: a first request receiving module for receiving a request sent by an AF for a UE reachable event after failing to subscribe to downlink data; a first event subscription request module for Sending a first request to the target network element according to the request to the UE reachable event after subscribing to downlink data fails, the first request includes the NEF network element identifier NEF ID and the AF application identifier; the first notification receiving module , Used to receive the UE reachability notification after the downlink data sent by the target network element fails, and the UE reachability notification after the downlink data failure includes the application ID of the AF corresponding to the UE that becomes unreachable; first The notification sending module is configured to send the UE reachability notification after the downlink data failure to the AF corresponding to the application identifier included in the UE reachability notification after the downlink data failure.
  • an SMF network element including a first processor, a first memory, and a first communication bus; the first communication bus is used to connect the first processor and the first memory; The first processor is used to execute the computer program stored in the first memory to implement the message notification method as described above.
  • NEF network element including a second processor, a second memory, and a second communication bus; the second communication bus is used to connect the second processor and the second memory; The second processor is used to execute the computer program stored in the second memory to implement the message notification method as described above.
  • Another aspect of the present disclosure provides a communication system, including a target network element and a NEF network element; the target network element is used to receive a first request for a UE reachable event after failing to subscribe to downlink data, and is generated according to the first request
  • the first subscription event reachable by the UE after the downlink data fails, the first request includes the application ID of the AF, the NEF ID of the NEF network element, and the event reference identifier of the first subscription event.
  • Another aspect of the present disclosure provides a computer-readable storage medium for storing one or more computer programs, the one or more computer programs can be executed by one or more processors, To realize the message notification method as described above.
  • FIG. 1 is a flowchart of a message notification method according to an embodiment of the present disclosure
  • FIG. 2 is a schematic diagram of a basic network architecture according to an embodiment of the present disclosure
  • FIG. 3 is a flowchart of a subscription event according to an embodiment of the present disclosure.
  • FIG. 4 is a flowchart of a subscription event according to another embodiment of the present disclosure.
  • FIG. 5 is a flowchart of notification of a UE reachability notification message according to an embodiment of the present disclosure
  • FIG. 6 is a schematic structural diagram of a message notification device according to an embodiment of the present disclosure.
  • FIG. 7 is a flowchart of a message notification method on the NEF network element side according to an embodiment of the present disclosure
  • FIG. 9 is a flowchart of an identification process according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of a message notification device on the NEF network element side according to an embodiment of the present disclosure
  • FIG. 11 is a flowchart of a message notification method on the AMF network element side according to an embodiment of the present disclosure
  • FIG. 12 is a flowchart of a third subscription event processing on the AMF network element side according to an embodiment of the present disclosure
  • FIG. 13 is a schematic structural diagram of a message notification device on an AMF network element side according to an embodiment of the present disclosure
  • 15 is a schematic structural diagram of a message notification device on an SMF network element side according to an embodiment of the present disclosure
  • 16 is a flowchart of a subscription event according to another embodiment of the present disclosure.
  • FIG. 17 is a flowchart of a subscription event according to another embodiment of the present disclosure.
  • 19 is a flowchart of a message notification method on the NEF network element side according to another embodiment of the present disclosure.
  • 20 is a flowchart of a message notification method on a target network element side according to an embodiment of the present disclosure
  • 21 is a schematic structural diagram of a message notification device according to another embodiment of the present disclosure.
  • FIG. 22 is a schematic structural diagram of an SMF network element according to an embodiment of the present disclosure.
  • FIG. 23 is a schematic structural diagram of a NEF network element according to an embodiment of the present disclosure.
  • FIG. 24 is a schematic structural diagram of an AMF network element according to an embodiment of the present disclosure.
  • FIG. 1 is a flowchart of a message notification method according to an embodiment of the present disclosure.
  • the UE User Equipment
  • the DDN fails.
  • the first subscription event and the application identifier (that is, Application ID) of the AF (Application, Function, non-3GPP third-party application) in the first request, and it should be understood that the application identifier in this embodiment may be a unique identifier / Any information identifying the AF) association; when the target network element detects that the target UE corresponding to the AF subscribed to the first subscription event changes from unreachable to reachable, the UE reaches a notification after the downlink data sent fails (i.e. A notification message for UE reachability) includes the application identifier of the AF; in this way, the NEF (Network Exposure) function can be based on the application identifier in the UE reachability notification after the failure of the downlink data.
  • the AF corresponding to the application identifier sends a notification message that the UE is reachable; improves the rationality of sending notification messages that the UE is reachable and network resource utilization.
  • the target network element as an SMF (Session Management Function) session element
  • SMF Session Management Function
  • the UE may The first subscription event reached, the first request includes the associated AF application identifier, NEF network element identifier NEF ID and event reference identifier of the first subscription event, the generated first subscription event can be associated with the event reference identifier Association; in this way, when SMF subsequently receives the UE reachability notification after receiving the downlink data failure, it can send the UE reachability notification (ie, a UE reachability notification message) after the downlink data fails according to the first subscription event generated before
  • the NEF network element corresponding to the NEF ID is sent to the AF corresponding to the Application ID (the Application ID included in the UE reachability notification after the downlink data failure) through the NEF network element, which can improve the UE reachability notification sent after the downlink data failure.
  • SMF Session Management Function
  • the message notification method according to an embodiment of the present disclosure includes the first subscription event generation process and the notification process of the UE reachability notification after the downlink data fails.
  • the message notification method according to the embodiment of the present disclosure includes steps S101 and S102.
  • step S101 receive a first request for a UE reachable event after failing to subscribe to downlink data, and generate a first subscription event for the UE reachable after failed downlink data according to the first request.
  • the first request includes an AF application identifier and an NEF network element The NEF ID and the event reference identifier of the first subscription event.
  • the first subscription event may be associated with the event reference identifier.
  • the first request includes the event reference identifier of the first subscription event that is related to each other, the application ID of the third-party application AF, and the NEF ID of the network open function NEF network element.
  • the target UE corresponding to the medium AF that is, the target receiving object of the downlink data delivered by the AF.
  • the first subscription event generated in S101 is associated with the event reference identifier of the first subscription event in the first request.
  • S101 may be performed by an SMF network element.
  • the NEF network element may trigger the first request for the UE reachable event after the failure to generate the downlink data to the session management function SMF network element according to the request of the third-party application AF for the SMF network element to generate The first subscription event that monitors the reachability of the UE.
  • the event reference identifier of the first subscription event included in the first request may be generated by the NEF network element.
  • the request of the AF may include, but is not limited to: an event open subscription request from the AF, for example, including but not limited to Event Exposure_Subscribe request.
  • the first request may include but is not limited to at least one of the following requests: an event open subscription request from a UDM (Unified Data Management) network element, such as, but not limited to, Event Exposure_Subscribe request ; Session policy control update notification request from PCF (Policy Control Function) policy element, including but not limited to SM Policy_Control_Update Notify request.
  • UDM Unified Data Management
  • PCF Policy Control Function
  • step S102 receiving the UE reachability notification after the downlink data of the target UE corresponding to the application identifier fails, and according to the first subscription event, send the UE reachability notification after the downlink data fails to the NEF network element.
  • the UPF User Plane Function
  • the UPF network element can also be configured to perform AF packet detection, that is, send a message to the UPF network element, activate and Application data detection function corresponding to the above Application ID.
  • the SMF network element can send the PFD (Packet Flow Description) corresponding to the Application ID to the UPF network element; according to the embodiment of the present disclosure, the SMF network element can also send the Application ID to the UPF.
  • the UPF The network element can perform packet inspection 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, when the SMF network element generates the first subscription event, it may also: Generate a first notification identifier, such as, but not limited to, a notification flag, and set the generated first notification identifier to be associated with the event reference identifier of the first subscription event in the first request.
  • a first notification identifier such as, but not limited to, a notification flag
  • the UE when the value of the first notification identifier is set as the first preset value, it may be characterized that the first subscription event associated with the event reference identifier of the first subscription event associated with the first notification identifier needs to be reported After the downlink data fails, the UE can reach the notification; when the value of the first notification identifier is not the first preset value, it can characterize the first subscription event associated with the event reference identifier of the first subscription event associated with the first notification identifier There is no need for UE reachability notification after failure to report downlink data.
  • the specific value of the first preset value in this embodiment can be flexibly set, for example, can be set to "1" or “Yes”, or can be set to other values, as long as it can characterize the first
  • the first subscription event associated with the notification identifier and the first subscription event associated with the event reference identifier need to report that the UE is reachable after the downlink data fails to be reported.
  • the SMF network element may not set the value for the generated first notification identifier temporarily, or directly set the default value as the first preset value. It can also be set flexibly according to specific application scenarios.
  • the SMF network element may set the value of the first notification identifier in but not limited to the following example manner. For example, before the SMF network element receives the reachability notification, the SMF network element receives the application data detection notification including the corresponding Application ID sent by the UPF network element, and determines that the target UE to be delivered by the AF corresponding to the Application ID is currently unavailable When it arrives, the notification flag corresponding to the Application ID can be set as the first preset value.
  • the application data detection notification in this embodiment includes but is not limited to at least one of the N4 Report message and the Data Notification message.
  • the N4Report message and the Data Notification message in this embodiment may be sent to the SMF network element through but not limited to the UPF network element.
  • the method may further include: determining a first notification identifier (the first notification identifier is the same as S102 Whether the first notification identifier corresponding to the event reference identifier of the first subscription event associated with the NEF in the ID) is currently the first preset value, and if so, the UE reachability notification will be sent to the NEF ID after the downlink data fails NEF network element for the NEF network element to send to the AF corresponding to the Application ID according to the association relationship between the Application ID and the event reference identifier of the first subscription event.
  • the SMF network element obtains the downlink reachability notification after the failure of the downlink data by requesting to subscribe to the UE reachability event (AMF (Access Management Function)) access to the UE, and the AMF network element receives the SMF After the first subscription event requested by the network element, a notification flag is set to control whether the UE reachability notification needs to be sent to the SMF network element.
  • AMF Access Management Function
  • the AMF network element may set a second notification flag associated with the SMF network element, including but not limited to UE Availability, Notify, SMF flag, and setting the second notification
  • the value of the flag is the first preset value, it indicates that the associated SMF needs to be reported, that is, when the state of the target UE changes from unreachable unreachability to reachable availability, the associated SMF network element needs to be notified.
  • the UE reachability notification changes from the unreachable unreachability to the availability of the target UE when the AMF network element detects the target UE, and the second associated with the SMF network element
  • the AMF sends it to the SMF.
  • the second notification identifier UE is set after the AMF network element detects that the status of the target UE is unreachable and reaches the SMF event subscription message.
  • an example of a setting process may include, but is not limited to: when the SMF network element receives the application data detection notification including the Application ID from the UPF network element, and the SMF network element learns that the user is currently unreachable, the setting with the Application ID
  • the corresponding first notification identifier is the first preset value; when the SMF network element learns that the user is currently unreachable, if the AMF network element has not subscribed to the user reachability status notification, the SMF network element subscribes to the AMF network element for the UE reachability status Notification event; when the AMF network element receives the subscription UE reachable status notification request from the SMF network element, the value of the second notification identifier associated with the above SMF network element is set as the first preset value to characterize the AMF network element When detecting that the state of the target UE changes from unreachable to reachable, a message notification needs to be sent to the SMF network element.
  • the UE reachability notification after the downlink data fails can be sent only to the AF that sent the downlink data service demand, rather than to all the first users who have subscribed to the UE reachability AF for subscribing to events improves the pertinence and intelligence of UE reachability notification after downlink data failure, and improves network resource utilization.
  • FIG. 2 is a schematic diagram of a basic network architecture according to an embodiment of the present disclosure.
  • next-generation wireless mobile 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.
  • 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 wireless access network Radio Access Network, RAN
  • core network Core Network
  • the core network functions of the next-generation network include an example of the basic network architecture shown in Figure 2.
  • the main NFs include but are not limited to the following : AMF network element, which belongs to the public control plane function in the core network and terminates NAS messages between all users and the network.
  • a UE can have only one AMF network element, responsible for user mobility management, UE status (such as reachability) management, etc .; SMF network element, responsible for but not limited to session establishment, modification, deletion, control PCF network element charging and policy execution PCF network element, responsible for but not limited to formulating strategies for the terminal based on the user's subscription, UE's current location, application-related information, including routing strategy, quality of service strategy, charging strategy, etc .; UDM network element, with unified data Management function, which can be used for but not limited to the permanent storage of user contract data and other functions; UDR (Unified Data Repository, unified data storage) network element can be used for but not limited to storing user contract data and policies managed by UDM network elements and PCF network elements Data, etc .; UPF network element, which belongs to the function of the user plane in the core network, is the anchor point of the user plane of the core network, is the interface with the external network (DN, Data) Network data transmission, and executes the execution of PCF policy rules in the
  • NEF network element (not shown in the figure), used to expose the capabilities and events of 3GPP NFs to other NF or third-party application AF, provide AF pre-configured 3GPP NFs capabilities, and realize the mapping of 3GPP network and external network information.
  • AF refers to a third-party application other than 3GPP
  • DN (Data) Network refers to a non-3GPP external network
  • 5G-AN (Access Network) refers to a 5G access network.
  • FIG. 3 is a flowchart of a subscription event according to an embodiment of the present disclosure.
  • the subscription event includes steps S301 to S307.
  • 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.
  • Exposure_Subscribe request may include instructions for subscribing to the Availability after DDN failure event, and the Application ID including the AF.
  • the Nnef_Event Exposure_Subscribe request also includes a target UE identifier, which may indicate a single user or a group of users.
  • the target UE identity may optionally also include an IP address.
  • 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 generates a first subscription event on the UDM network element according to the target UE identifier; for example, the NEF network element may send a Nudm_Event Exposure_Subscribe request (that is, a first request) to the UDM network element, and the Nudm_Event Exposure_Subscribe request may include a subscription Availability indication of DDN failure event, AF Application ID, NEF_reference_ID1, and optionally, NEF ID of NEF network element.
  • the UDM network element finds the user-related context according to the target UE ID, selects the appropriate SMF network element within the user context, and then goes to the SMF network element to subscribe to the UE's availability after DDN failed event.
  • the UDM network element may send a Nsmf_Event Exposure_Subscribe request to the SMF network element.
  • the Nudm_Event Exposure_Subscribe request may include an instruction to subscribe to the Availability after DDN failure event, Application ID, NEF ID, NEF_reference_ID1.
  • the SMF network element generates a first subscription event that monitors the reachability of the UE, and optionally can set whether to send a notification flag to start monitoring the first notification, (if the notification flag is "no", the downlink data of the first subscription event After the failure, the UE reachability notification is not sent. If the notification flag is "Yes” (that is, the first preset value), the UE reachability notification is sent after the downlink data of the first subscription event fails.
  • the SMF network element configures the UPF network element to perform AF packet inspection.
  • the SMF network element activates the application package detection for the Application ID on the UPF network element according to the subscription request (ie, the second request) of the UDM network element.
  • the SMF network element can send an N4 Session / Establishment / Modification Request (Application ID, PFD) to the UPF network element.
  • N4Session Establishment / Modification Request the SMF network element can describe the PFD (Packet Flow) Description corresponding to the Application ID in the packet flow description. ) Delivered to the UPF network element.
  • the SMF network element can also deliver the Application ID to the UPF network element.
  • the UPF network element performs packet inspection according to the locally configured PFD corresponding to the Application ID.
  • 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.
  • the NEF network element sends a response message to the AF, such as Nnef_EventExposure_Subscribe responses.
  • steps S306 and S307 may also be performed 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.
  • the following uses an example of a first subscription event on an SMF network element and a method of formulating a UPF for AF application packet detection.
  • FIG. 4 is a flowchart of a subscription event according to another embodiment of the present disclosure.
  • the subscription event includes steps S401 to S407.
  • 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 DDN failure event
  • the Nnef_Event Exposure_Subscribe request may include instructions for subscribing to the Availability after DDN failure event, and the Application ID including the AF.
  • the NEF network element finds the corresponding PCF network element according to the target UE identifier and other information, and the PCF network element generates the relevant first subscription event; for example, the NEF network element may send Npcf_PolicyAuthorization_Create (that is, an example of the first Request), the Npcf_PolicyAuthorization_Create may include an indication to subscribe to the Availability after DDN failure event, AF ’s Application ID, NEF_reference_ID1, and according to an embodiment of the present disclosure, it may also include the NEF ID of the NEF network element.
  • Npcf_PolicyAuthorization_Create that is, an example of the first Request
  • the Npcf_PolicyAuthorization_Create may include an indication to subscribe to the Availability after DDN failure event, AF ’s Application ID, NEF_reference_ID1, and according to an embodiment of the present disclosure, it may also include the NEF ID of the NEF network element.
  • the PCF network element finds the context and related session related to the user according to the target UE identifier and other information, and then subscribes to the Availability DDN failure event (ie, UE validity monitoring event) on the SMF network element of the session.
  • 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 network element generates a first subscription event that monitors the reachability of the UE, and optionally can set whether to send a notification flag to start monitoring the first notification, (if the notification flag is "no", the downlink data of the first subscription event After the failure, the UE reachability notification is not sent. If the notification flag is "Yes” (that is, the first preset value), the UE reachability notification is sent after the downlink data of the first subscription event fails.
  • the SMF network element configures the UPF network element to perform AF packet inspection.
  • the SMF network element activates the application package detection for the Application ID on the UPF network element according to the subscription request of the UDM network element.
  • the SMF network element can send an N4SessionEstablishment / ModificationRequest (ApplicationID, PFD) to the UPF network element.
  • N4SessionEstablishment / ModificationRequest the SMF network element can associate the PFD (PacketFlowDescription, packet flow description) corresponding to the ApplicationID Delivered to the UPF network element.
  • the SMF network element can also deliver the Application ID to the UPF network element.
  • the UPF network element performs packet inspection according to the locally configured PFD corresponding to the Application ID.
  • 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, such as Nudm_EventExposure_Subscribe responses.
  • the NEF network element sends a response message to the AF, for example, Npcf_PolicyAuthorization_Create response.
  • steps S406 and S407 may also be performed before step S403.
  • the first subscription event can be generated on the SMF network element and the UPF can be configured to detect AF application data packets in the manner shown in FIG. 4.
  • a process of providing a method in which a UPF network element detects that an AF application data packet delivers a notification to an SMF network element, and the SMF network element reports a UE availability notification message to the AF is performed as an example. Instructions.
  • FIG. 5 is a flowchart of notification of a UE reachability notification message according to an embodiment of the present disclosure.
  • the notification of the UE reachability notification message includes steps S501 to S508.
  • the AF sends downlink data
  • 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 can carry but is not limited to QoS flow, ARP (Allocation and Retention Priority, allocation and retention priority), etc. At least one of the information.
  • the UPF network element detects that the AF is sending downlink data according to the data packet, so it sends an N4Report message to the SMF network element to report the detected Application ID (of course, in one example, the UPF network element can directly pass the Data Notification Report the detected Application ID to the SMF network element).
  • the SMF network element After the SMF network element receives the N4Report message or the Data Notification message, if the SMF network element already knows that the target UE corresponding to the AF corresponding to the Application ID is unreachable, the SMF network element sets the notification flag of the AF to yes, The notification flag and NEF_reference_ID1 are associated. If the SMF network element already knows that the target UE corresponding to the AF corresponding to the Application ID is in a reachable state, the notification flag of the AF may be set to No; according to the embodiment of the present disclosure, the Application ID may also be cleared.
  • 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.
  • the SMF network element learns that the user is currently unreachable, sends a message to the AMF network element, requests to subscribe to the user reachability notification, and after receiving the AMF network element, sets a second notification identifier UEAvailability associated with the SMF network element in S503
  • the value of Notify SMF flag is "Yes", which is used to indicate that the SMF network element needs to be notified when the status of the target UE becomes available.
  • the subscription request can also be carried in step S503, so that the SMF network element does not need to resend the subscription message to the AMF network element.
  • the AMF network element detects that the target UE state becomes available, and the AMF network element sends a UE status reachable notification message to the SMF network element according to the second notification flag UE Availability Availability SMF flag set in S505.
  • the SMF network element determines the AF to be notified according to the first notification flag notification flag, and sends the UE status reachable notification message to the corresponding NEF ID according to the event reference identifiers NEF_Reference_ID1, NEFID of the first subscription event NEF network element; for example, in one example, the SMF network element may be implemented by sending Nsmf_EventExposure_Notify to the NEF network element.
  • the NEF network element notifies the AF corresponding to the Application ID that the UE is reachable after the received downlink data fails.
  • the NEF network element may be implemented by sending Nnef_EventExposure_Notify to the AF.
  • the message notification device may be installed in an SMF network element.
  • the message notification device includes a third event subscription processing module 601 and a fifth notification sending module 602.
  • the third event subscription processing module 601 receives a first request for generating a first subscription event that monitors the reachability status of the target UE, and generates a first subscription event that monitors the reachability status of the target UE, that is, a UE that subscribes to the target UE after DDN failed event.
  • the first request includes the event reference identifier of the first subscription event associated with each other, the application ID of the third-party application AF, and the NEF identifier NEF of the NEF network element, and the third event subscription processing module 601 generates The first subscription event of is associated with the event reference identifier of the first subscription event in the first request.
  • the NEF network element may trigger the first request to generate the first subscription event for monitoring the reachability status of the UE to the SMF network element according to the second request of the third-party application AF for the SMF network element Generate a first subscription event that monitors the reachability of the UE.
  • the event reference identifier of the first subscription event included in the first request may be generated by the NEF network element.
  • the second request may include, but is not limited to, an event open subscription request from AF, such as, but not limited to, Event Exposure_Subscribe request.
  • the first request received by the third event subscription processing module 601 includes at least one of the following requests: event open subscription requests from UDM network elements, such as but not limited to Event Exposure_Subscribe request; from the PCF network Meta session policy control update notification request, for example, including but not limited to SMPolicyControl_UpdateNotifyrequest.
  • the fifth notification sending module 602 is used to receive the UE reachability notification after the downlink data of the target UE fails, and according to the first subscription event generated by the third event subscription processing module 601, send the UE reachability notification after the downlink data fails to the UE
  • the NEF network element corresponding to the NEF ID associated with the first subscription event is for the NEF network element to send to the AF corresponding to the Application ID according to the association relationship between the Application ID and the event reference identifier of the first subscription event.
  • the UPF network element may also be configured to perform data packet detection, that is, the application packet detection for the Application ID is activated on the UPF network element.
  • the third event subscription processing module 601 can deliver the PFD (Packet Flow Description) corresponding to the Application ID to the UPF network element; according to an embodiment of the present disclosure, the third event subscription processing module 601 can also send the Application ID It is delivered to the UPF network element.
  • the UPF network element can perform packet inspection based on the locally configured PFD corresponding to the Application ID.
  • the third event subscription processing module 601 can control whether the first subscription event needs to report the downlink data after the failure of reporting the downlink data through the first notification identifier. Therefore, according to the implementation of the present disclosure For example, when the third event subscription processing module 601 generates a first subscription event that monitors the reachability of the UE, it further includes: generating a first notification identifier, such as notification flag, and setting the generated first notification identifier and the first request in the first request An event reference identifier association for a subscribed event.
  • a first notification identifier such as notification flag
  • the UE when the value of the first notification identifier is set as the first preset value, it may be characterized that the first subscription event associated with the event reference identifier of the first subscription event associated with the first notification identifier needs to be reported After the downlink data fails, the UE can reach the notification; when the value of the first notification identifier is not the first preset value, it can characterize the first subscription event associated with the event reference identifier of the first subscription event associated with the first notification identifier There is no need for UE reachability notification after failure to report downlink data.
  • the third event subscription processing module 601 may not temporarily set the value for the generated first notification identifier, or directly set the default to the first preset value. It can also be set flexibly according to specific application scenarios.
  • the third event subscription processing module 601 may set the value of notification flag in but not limited to the following example manner. For example, before the third event subscription processing module 601 receives the reachable notification, the third event subscription processing module 601 receives the application data detection notification including the corresponding Application ID sent by the UPF network element, and determines the AF corresponding to the Application ID When the target UE to be delivered is currently unreachable, the first notification identifier corresponding to the Application ID may be set as a first preset value.
  • the downlink application data detection notification in this embodiment includes but is not limited to at least one of the N4Report message and the Data Notification message.
  • the fifth notification sending module 602 can also be used to determine whether the first notification identifier is currently the first before the UE reachable notification after the downlink data fails is sent to the NEF network element corresponding to the NEF ID
  • the preset value if so, only sends the UE reachable notification after the failure of the downlink data to the NEF network element corresponding to the NEF ID for the association relationship between the NEF network element according to the Application ID and the event reference identifier of the first subscription event, Send to AF corresponding to Application ID.
  • the AMF network element may also control whether it is necessary to send a reachable notification to the third event subscription processing module 601 by setting a notification identifier. For example, when the AMF network element pages the UE according to the request of the SMF network element, if the user is unreachable and a subscription request for the user reachability notification of the SMF network element is received, a second associated with the SMF network element may be set.
  • the notification flag UEAvailabilityNotifySMFflag, and the value of the UEAvailabilityNotifySMFflag can also be set as the first preset value, indicating that it needs to be reported to the associated SMF network element, which indicates that when the state of the target UE changes from unreachable unreachability To reach availability, the associated SMF network element needs to be notified.
  • the reachability notification received by the fifth notification sending module 602 can be changed from unreachable unreachability to reachable availability when the AMF network element detects the target UE, and the second notification identifier ( For example, when the current value of UE Availability (Notify SMF) is the first preset value, the AMF network element sends it to the SMF network element.
  • the second notification identifier UE, Availability, Notify, SMF, flag is set after the AMF network element detects that the status of the target UE is unreachable and receives the event subscription message of the SMF network element.
  • the functions of the third event subscription processing module 601 and the fifth notification sending module 602 can be implemented by, but not limited to, the processor or controller of the SMF network element.
  • the UE can send downlink data after failure
  • the reach notification is only sent to the AF that sent the downlink data service requirement, not to the AF that subscribes to the first subscription event of the UE reachability state, which improves the targeted and intelligent sending of the UE reachability notification after the downlink data fails , And improved network resource utilization.
  • FIG. 7 is a flowchart of a message notification method on the NEF network element side according to an embodiment of the present disclosure.
  • the message notification method on the NEF network element side may include but not limited to steps S701 to S705.
  • receiving a request sent by the AF for a UE reachable event ie, UE availability after DDN failure
  • the request 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 failing to subscribe to downlink data through various interaction messages with the NEF network element.
  • the first request for the UE reachable event is sent to the AMF network element after subscribing to the downlink data fails, and the second request for the subscription application data detection event (that is, the downlink data packet detection event) is sent to the SMF network element request.
  • the execution order of the first request sent by the NEF network element to the AMF network element and the second request sent to the SMF network element is not strictly limited, and the two can be executed in parallel, or the first request can be sent to the AMF network element first.
  • the first request may include, but is not limited to, the application identification of the AF and the NEF ID of the NEF network element, and their functions are as shown above and will not be repeated here.
  • the second request may also include the AF application ID and the NEF network element ID NEF ID, so that the second subscription event detected by the SMF network element according to the application data generated by the second request can be related to the AF application ID and NEF network element Identify the NEF ID association, so that the SMF network element can instruct the UPF network element to activate the application data detection (ie, downlink data packet detection) of the AF corresponding to the corresponding application identifier according to the second subscription event; and upon receiving the detection sent by the UPF
  • the corresponding second subscription event is determined according to the application identifier in the notification and the above-mentioned association relationship, and from the determined second subscription event and the above-mentioned association relationship to the corresponding NEF ID
  • the first request for the UE reachable event after failure to send the downlink data subscription to the AMF network element may include, but is not limited to: sending the first request to the AMF network element through the event open subscription request of the UDM network element.
  • sending the second request for subscription application data detection to the SMF network element may include but is not limited to at least one of the following ways: sending the first request to the SMF network element through the event open subscription request of the UDM network element Send a first request to the SMF network element through the PCF network element's session policy control update notification request.
  • 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.
  • 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.
  • the UE reaches the notification after the downlink data fails to be sent to the AF corresponding to the application identifier included in the application identifier list.
  • the UE reachability notification after failure to send downlink data to the AF corresponding to the application identifier included in the application identifier list includes, but is not limited to, one of the following: Direct failure to send downlink data to the AF corresponding to the application identifier included in the application identifier list
  • the application identification list can be cleared after sending; the UE after sending the downlink data fails to send to the AF corresponding to the application identification included in the UE reachability notification after the downlink data failure in the application identification list Reachable notification; for example, when the application identifier is extracted from the UE reachable notification after the received downlink data fails, and then the application identifier that is the same as the application identifier is selected from the application identifier list, it is sent to the AF corresponding to the application identifier After the downlink data fails, the UE can be notified.
  • the corresponding target UE may itself be reachable when it sends downlink data.
  • the UE may not send downlink data to it.
  • a clearing mechanism may be used to clear its application identifier from the above-mentioned application identifier list.
  • FIG. 8 is a flowchart of clearing an application identifier according to an embodiment of the present disclosure.
  • the SMF network element After receiving the application data detection notification sent by the SMF network element, it may also include but not limited to steps S801 and S802.
  • a third request to subscribe to the UE reachable event is sent to the AMF network element.
  • the UE reachable event refers to one of two methods: Method 1: The UE detects whether it is currently reachable and does not care about its previous state. That is, before detecting whether the UE corresponding to the application identifier in the application data detection notification is reachable, the UE may be in a reachable state or may be in an unreachable state, and the detection may be initiated during the detection After that, the UE changes from unreachable to reachable; in either case, as long as the UE is detected as reachable, the UE reachability notification is fed back.
  • Method 2 The UE detects whether the current state is reachable. If the current state of the UE is reachable, the UE is notified of the reachability notification; if the current state of the UE is unreachable, the UE is notified of the unreachability notification.
  • sending the third request to subscribe to the UE reachable event to the AMF network element includes but is not limited to: sending the third request to the AMF network element through the event open subscription request of the UDM network element.
  • the application identifier included in the application identifier list is cleared.
  • clearing the application identification list includes but is not limited to one of the following: clearing all application identifications in the application identification list; clearing the application identifications in the application list that are the same as the application identifications included in the UE reachability notification.
  • the UE reachability notification sent by an AMF network element to a certain UE may be sent when the UE changes from unreachable to reachable, or it may be that the UE itself is in Sent when reachable (that is, no DDN failure event occurs). Therefore, in order to avoid erroneously clearing the AF corresponding to the UE from the unreachable state to the reachable state, this embodiment may also adopt an identification mechanism to avoid the above situation.
  • FIG. 9 is a flowchart of the recognition process according to an embodiment of the present disclosure.
  • the timer starts when the UE reachability notification is received.
  • the NEF network element may set a timer through which time counting is performed.
  • the UE reachability notification after the failure of the downlink data is sent to the AF corresponding to the application identifier included in the application identifier list.
  • the present disclosure also provides a message notification device that can be set in the NEF network element, and of course, can also be set in other network elements that can communicate with the AF.
  • Each module included in the message notification device can be implemented but is not limited to the above method Corresponding functions in, and the functions of each module can be realized by but not limited to the processor or controller of the network element.
  • the message notification device includes, but is not limited to, a second request receiving module 1001, a second event subscription request module 1002, a second notification receiving module 1003, and a second notification sending module 1004.
  • the second request receiving module 1001 is configured to receive a request sent by the AF for a UE reachable event after subscribing to downlink data fails.
  • the second event subscription request module 1002 is used to send the first request for the UE reachable event to the AMF network element after the subscription downlink data fails according to the request received by the second request receiving module 1001, and send the subscription application data detection event to the SMF network element Second request.
  • the second notification receiving module 1003 is used to receive the application data detection notification sent by the SMF network element, store the application identifier in the application data detection notification in the application identifier list; and used to receive the downlink data sent by the AMF network element after failure UE reachable notification.
  • the second notification sending module 1004 is configured to send the UE reachable notification after the downlink data fails to the AF corresponding to the application identifier included in the application identifier list. According to the embodiment of the present disclosure, it may be further used to clear the application identifier list.
  • 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 also be used to, after receiving the UE reachability notification sent by the AMF network element, before clearing the application identifier contained in the application identifier list, since receiving the UE reachability notification start the timer.
  • the second notification receiving module 1003 can also be used to clear the application identification included in the application identification list if the UE fails to receive the downlink data notification when the timing value reaches the set time value; if the downlink data is received After the failure, the UE reachability notification may be sent to the AF corresponding to the application identifier through the second notification sending module 1004 after the downlink data fails.
  • steps S1101 and S1102 may be included, but not limited to.
  • a first request sent by a NEF network element for a UE reachable event after a failure to subscribe to downlink data is received, and according to the first request, a first subscription event for a UE reachable after a downlink data failure is generated.
  • 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 is a notification corresponding to the corresponding first subscription event.
  • the UE reachable notification is sent to the NEF network element after the downlink data fails, and the UE reachable notification may include an application identifier after the downlink data fails .
  • the AMF network element may, according to the first subscription event, when it detects that the target UE corresponding to the first subscription event changes from unreachable to reachable, notify the NEF ID corresponding to the first subscription event.
  • the UE reachability notification may be included.
  • the UE reachability notification may include an application identification application identifier corresponding to the first subscription event.
  • the message notification method according to an embodiment of the present disclosure may further include but not limited to steps S1201 and S1202.
  • a third request for subscription to a UE reachable event sent by an NEF network element is received, and a third subscription event for UE reachability is generated according to the third request, and the third request may include an application identifier in an application data detection notification.
  • a UE reachability notification is sent 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 an 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 refer to the event reference of the third subscription event.
  • the identifier recognizes that the received notification is a notification corresponding to the corresponding third subscription event.
  • the present disclosure also provides a message notification device that can be set in an AMF network element. Of course, it can also be set in other network elements that can directly or indirectly detect the reachability state of the UE.
  • the modules included in the message notification device can be implemented However, it is not limited to the corresponding function in the above method, and the function of each module may be implemented by, but not limited to, the processor or controller of the network element.
  • the message notification device includes but is not limited to a third request receiving module 1301, a first event subscription processing module 1302, and a third notification sending module 1303.
  • the third request receiving module 1301 is configured to receive a first request sent by a NEF network element for a UE reachable event after a failure to subscribe to downlink data.
  • the first request includes an AF application identifier and the NEF network element identifier NEF ID.
  • the first event subscription processing module 1302 is configured to generate a first subscription event that is reachable by the UE after the downlink data fails according to the first request received by the third request receiving module 1301.
  • the third notification sending module 1303 is configured to send the UE reachable notification after the downlink data fails to the NEF network element after detecting that the UE corresponding to the application identifier changes from unreachable to reachable according to the first subscription event.
  • the UE reachability notification includes the application identifier.
  • the third request receiving module 1301 may also be used to receive a third request sent by the NEF network element to subscribe to the UE reachability event; the third request includes the application identifier in the application data detection notification.
  • the first event subscription processing module 1302 may also be used to generate a third subscription event reachable by the UE according to the third request.
  • the third notification sending module 1303 may be further configured to send a UE reachable notification to the NEF network element when detecting that the UE corresponding to the application identifier in the third request is reachable according to the third subscription event.
  • steps S1401 to S1404 may be included, but not limited to.
  • a second request for subscription to the application data detection event sent by the NEF network element is received, and a second subscription event for application data detection is generated according to the second request.
  • the second request includes the AF application identification and the NEF network element identification NEF ID.
  • an event reference identifier of an associated second subscription event may also be generated for the second subscription event, so as to facilitate management of each second subscription event.
  • the subsequent application data detection notification may include the event reference identifier of the corresponding second subscription event, so that the receiver can use the event reference identifier of the second subscription event It is recognized that the received notification is a notification corresponding to the corresponding second subscription event.
  • the UPF network element is instructed to activate the application data detection of the AF corresponding to the application identifier according to the second subscription event.
  • the UPF network element can perform application data detection on the corresponding AF according to the instruction, that is, downlink data packet detection.
  • an application data detection notification sent by a UPF network element is received, and the application data detection notification includes an application identification of an AF that detects that downlink data has been sent.
  • the received application data detection notification is sent to the NEF network element.
  • This embodiment also provides a message notification device that can be installed in an SMF network element. Of course, it can also be installed in other network elements that can directly detect or indirectly detect AF downlink data.
  • Each module included in the message notification device can Realize but not limited to the corresponding function in the above method, and the function of each module can be realized by but not limited to the processor or controller of the network element.
  • the message notification device in this embodiment includes but is not limited to a fourth request receiving module 1501, a second event subscription processing module 1502, and a fourth notification sending module 1503.
  • the fourth request receiving module 1501 is configured to receive a second request sent by the NEF network element to subscribe to the application data detection event, where the second request includes the AF application identification and the NEF network element identification NEFID.
  • the second event subscription processing module 1502 is configured to generate a second subscription event for application data detection according to the second request, and to instruct the UPF network element to activate the application data detection corresponding to the AF corresponding to the application identifier according to the second subscription event.
  • the fourth notification sending module 1503 is configured to receive the application data detection notification sent by the UPF network element, and send the application data detection notification to the corresponding NEF network element (that is, the NEF network element corresponding to the application identifier in the notification), application data
  • the detection notification includes the application identification of the AF that detected that the downlink data has been sent.
  • a UE reachable event that is, UE availability after DDN failed event
  • an AF application to an SMF network element are activated after a failure to subscribe to downstream data on an AMF network element
  • FIG. 16 is a flowchart of a subscription event according to another embodiment of the present disclosure.
  • the subscription event includes steps S1601 to S1608.
  • each AF can subscribe to the UE's availability by sending a request to NEF network elements (hereinafter referred to as an event subscription request).
  • the AF can send Nnef_EventExposure_Subscribe request to subscribe to the UE's UEAvailability after DDN failure event corresponding to the AF
  • the Nnef_EventExposure_Subscribe request may include an indication of subscribing to the UE, Availability after DDN failure event, and an AF application identifier.
  • it may also include a target UE identifier corresponding to the AF.
  • the target UE identifier may indicate a single user or a group of users.
  • the target UE identity may optionally include an IP address.
  • AF application identification refers to information that can be used to characterize the identity of AF, such as application identification Application ID, port information, IP address information, etc.
  • 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, the Application ID of the AF, the NEF_reference_ID, and according to the embodiments of the present disclosure, the NEF ID of the NEF network element.
  • the UDM network element to the AMF network element to subscribe UE availability event after DDN failure event may send a Namf_EventExposure_Subscribe request to the AMF network element (that is, an exemplary first request sending method), the request may include a subscription UE availability indication after DDN failure event, Application ID, NEF ID, NEF_reference_ID (that is, the event reference identifier of the first subscription event); the AMF network element can generate the first subscription event according to the Namf_EventExposure_Subscribe request.
  • the UDM network element finds the user-related session context according to the target UE ID, finds the user-registered SMF (hSMF or home SMF in the home network roaming) network element in the user context, and then goes to the SMF network element Application data detection event subscription.
  • the UDM network element may send an Nsmf_EventExposure_Subscribe request (that is, an example second request) to the SMF network element.
  • the Nsmf_EventExposure_Subscribe request may include an indication of a subscription application data detection event, Application ID, NEF ID, and NEF_reference_ID (that is, the second subscription event Event reference identifier), the SMF network element generates a second subscription event according to Nsmf_EventExposure_Subscribe request.
  • the SMF network element configures the UPF (hUPF or home UPF in the home network roaming scenario) network element to perform AF packet detection corresponding to the Application ID.
  • the SMF network element activates the downlink packet detection for the Application ID on the UPF network element according to the Nsmf_EventExposure_Subscribe request of the UDM network element.
  • the SMF network element can send an N4 Session / Establishment / Modification Request (Application ID, PFD) to the UPF network element.
  • N4Session Establishment / Modification Request the SMF network element can describe the PFD (Packet Flow) Description corresponding to the Application ID in the packet flow description. ) Issued to UPF.
  • the SMF network element can also deliver the Application ID to the UPF network element.
  • the UPF network element performs packet inspection based on the locally configured PFD corresponding to the Application ID.
  • 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.
  • the NEF network element sends a response message to the AF, for example, Nnef_EventExposure_Subscribe responses.
  • FIG. 17 is a flowchart of a subscription event according to another embodiment of the present disclosure.
  • a second subscription event detected by an application data packet generated at an SMF network element may also be implemented.
  • the subscription event includes steps S1701 to S1704.
  • each AF may subscribe to events by sending a request to NEF network elements (hereinafter referred to as an event subscription request).
  • the AF may send a Nnef_EventExposure_Subscribe request to subscribe to the application data detection event corresponding to the AF.
  • the Nnef_EventExposure_Subscribe request may include the AF application Identify the Application ID and corresponding UE information (for example, including but not limited to the IP address of the UE).
  • 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 according to the IP address of the UE in the event subscription request, or DNN (Data, Network Name, Data Network Name) and S-NSSAI (subscribed-Network, Slice Selection, Assistance, Information for contracted network slice selection), If you can find the PCF network element of the PDU session related to the user UE, request an application data detection event subscription from the PCF network element.
  • the NEF network element can send a Npcf_PolicyAuthorization_Subscribe subscription request.
  • the request message carries the event reference identifier, application identifier Application ID, NEF Network element identification.
  • 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 retrieve the UDR 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 ID, and NEF network element ID 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 reports
  • the UPF network element sends and executes the application data detection for the AF identified by 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 associate the PFD (Packet Flow Description) corresponding to the Application ID with the packet flow Description) issued to UPF.
  • the SMF network element can also deliver the Application ID to the UPF.
  • the UPF network element performs packet inspection according to the locally configured PFD corresponding to the Application ID.
  • FIG. 18 is a flowchart of notification of a UE reachability notification message according to another embodiment of the present disclosure.
  • the notification of the UE reachability notification message includes steps S1800 to S1817.
  • the hUPF network element performs application data detection according to the PDF.
  • the AF sends downlink data to the hUPF network element.
  • the hUPF network element detects the downlink data sent by the AF identified by the Application ID, and sends an N4 report or Data Notification (Data Notification) message to notify the hSMF network element.
  • Data Notification Data Notification
  • the hSMF network element notifies the NEF network element (hereinafter referred to as NEF) according to the AF's second subscription event that it detects that the AF has sent data Nsmf_EventExposure_Notify (Application ID), and this message carries the application ID of the AF.
  • NEF NEF network element
  • the NEF network element saves the AF detected Application ID to Application ID list. If the NEF network element receives multiple Application IDs in the notification of the hSMF network element, it can be directly saved to the Application ID list. If the subsequent hSMF After the NE continues to report the detected Application ID, the NEF NE adds the subsequent Application ID to the aforementioned Application ID list.
  • the NEF network element In S1805, the NEF network element generates a new NEF_Reference_ID (that is, the event reference event identifier of the third subscription event), and sends a UE reachable monitoring subscription event request to the UDM network element (hereinafter referred to as UDM).
  • NEF_Reference_ID that is, the event reference event identifier of the third subscription event
  • the UDM network element receives the NEF network element request message, it sends a request to the AMF network element to subscribe to the UE reachable status event Namf_EventExposure_subscribe (UE reachability status, NEF ID, NEF_Reference_ID), which is the third subscription event.
  • Namf_EventExposure_subscribe UE reachability status, NEF ID, NEF_Reference_ID
  • the hUPF network element sends downlink data to the visiting UPF (vUPF or visit UPF) network element.
  • the vUPF network element caches the downlink data, and sends a data notification Data to the visiting SMF (vSMF or visit SMF) network element, and then vSMF sends the data to the AMF network element.
  • the AMF network element pages the target UE.
  • steps S1807 to S1809 can be performed in parallel with steps S1802 to S1806.
  • step S1810 if the AMF network element paging is successful or the AMF network element knows that the UE status is reachable, steps S1811 and S1812 are executed; otherwise, step S1813 is skipped.
  • the AMF network element sends a UE reachable notification message Namf_EventExposure_notify to the NEF network element.
  • the NEF network element receives the UE reachable notification of the third subscription event, indicating that the user is currently reachable, and all downlink data can be sent to the UE without DDN Failure, so there is no need to notify AF, so the NEF network element Clear the Application ID list in S1804.
  • 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 first subscription event notification is not received, clear the Application ID list in S1804; if the timer receives the first To subscribe to the event notification, it will be processed according to S1816).
  • vSMF may instruct vUPF to discard or save downstream data.
  • the AMF network element detects that the UE is reachable.
  • the AMF network element sends a UE reachable notification message Namf_EventExposure_notify (UE reachability) to the NEF network element according to the third subscription event.
  • the AMF determines that the user is currently the UE availability after DDN Failure, the AMF sends UE Availablility after DDN Failure to the NEF network element Namf_EventExposure_notify (UE availability after DDN failure) according to the first subscription event.
  • the NEF network element if the NEF network element receives the UE availability after DDN failure of the first subscription event, the NEF network element sends the UE availability availability after DDN failure event to the corresponding AF in the Application ID list saved in S1804. Because S1814 and S1815 may be sent from the AMF network element at the same time, if the NEF network element receives the user reachable notification of the third subscription event first, the NEF network element can set a timer locally before the timer expires.
  • the UE When the event notification of the first subscription event is reached, the UE is sent the AF availability event after DDN failure event; if the notification of the first subscription event is not received before the timer expires, it means that the notification of S1812 is received, and it is processed according to S1812.
  • the NEF network element sends a UE availability after DDN failure notification message to the AF.
  • the present disclosure provides a message notification method.
  • a target network element fails to generate downlink data according to a first request, a first subscription event that is reachable by the UE (that is, UE available after DDN failed), compares the first subscription event with the first The application ID of the AF in the request (that is, Application ID, and it should be understood that the application ID in this embodiment may be a unique identifier / any information that identifies AF) is associated; the target network element detects that it has subscribed to the first subscription
  • the UE reachability notification that is, a UE reachability notification message
  • the sending of downlink data fails includes the application identification of the AF; thus the NEF network element is According to the application identifier in the UE reachability notification after the failure of the downlink data, the UE-reachable notification message can be sent to the AF corresponding to the application identifier in a targeted manner; the rationality of sending the
  • FIG. 19 is a flowchart of a message notification method on the NEF network element side according to another embodiment of the present disclosure.
  • the message notification method on the NEF network element side may include but not limited to steps S1901 to S1904.
  • a request sent by the AF for a UE reachable event (UE availability after DDN failed event) after a failure to subscribe to downlink data is received.
  • 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 the request is received by the NEF network element After that, the application identifier of the AF is extracted according to the sender of the request.
  • the first request for the UE reachable event after the failure to subscribe to the downlink data is sent to the target network element.
  • the first request includes the NEF ID of the NEF network element (it should be understood that this embodiment
  • the NEF in the ID can be any information that uniquely identifies / identifies the NEF network element) and the application ID of the AF.
  • the first subscription event reachable by the UE may be generated
  • the first subscription event is associated with the NEF ID of the NEF network element and the application ID of the AF; when the subsequent target network element detects that a certain UE changes from unreachable to reachable, it can use the corresponding association relationship
  • the application ID of the AF corresponding to the UE and the NEF ID corresponding to the application ID of the AF are determined, thereby determining the NEF network element to which the AF is connected, so that the UE reachability notification is sent to the UE after the downlink data of the UE fails On the corresponding NEF network element.
  • the target network element may include but is not limited to at least one of an AMF network element and an SMF network element.
  • the target network element may also be another network connection capable of detecting the UE reachability state or communicating with a network element capable of detecting the UE reachability state. Any network element, such as UDM network element, PCF network element, etc.
  • 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 by the target network element when it detects that the target UE corresponding to the AF subscribed to the first subscription event changes from unreachable to reachable.
  • 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.
  • the UE reachability notification after the downlink data failure is sent to the AF corresponding to the application identifier included in the UE reachability notification after the received downlink data failure; for other AF, the UE reachability notification after the downlink data failure is not sent, It can not only meet the communication needs, but also improve the utilization rate of network resources.
  • FIG. 20 is a flowchart of a message notification method on the target network element side according to an embodiment of the present disclosure.
  • the message notification method on the target network element side may include but is not limited to step S2001 and S2002.
  • 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 UE when it is detected that the UE corresponding to the corresponding application identifier changes from unreachable to reachable according to the first subscription event, the UE reaches the corresponding NEF network element after the downlink data fails to be notified, and after the downlink data fails, the UE
  • the reachable notification includes the application identification.
  • the target network element may correspond to the first subscription event when detecting that the UE corresponding to the application identifier corresponding to the first subscription event changes from unreachable to reachable according to the first subscription event
  • the NEF network element corresponding to the NEF ID of the UE fails to send the downlink data after sending the downlink data, and the UE reachable notification after the sent downlink data fails includes the application ID and the application ID corresponding to the first subscription event.
  • the target network element may include but is not limited to at least one of an AMF network element and an SMF network element. And in some examples, UDM network elements, PCF network elements, etc. may also be used, but not limited to.
  • the present disclosure also provides a message notification device, which can be installed in a NEF network element or other network elements that can communicate with AF.
  • a message notification device which can be installed in a NEF network element or other network elements that can communicate with AF.
  • Each module included in the message notification device can be implemented but is not limited to the above method
  • Corresponding functions in, and the functions of each module can be realized by but not limited to the processor or controller of the network element.
  • the message notification device in this embodiment includes but is not limited to a first request receiving module 2101, a first event subscription request module 2102, a first notification receiving module 2103, and a first notification sending module 2104.
  • the first request receiving module 2101 is configured to receive a request sent by the AF for a UE reachable event after failing to subscribe to downlink data.
  • the first event subscription request module 2102 is configured to send a first request for a UE reachable event after subscribing to downlink data fails to the target network element according to the request received by the first request receiving module 2101.
  • the first request includes a network open function NEF network The NEF ID of the meta and the application ID of the AF.
  • the first notification receiving module 2103 is configured to receive the UE reachability notification after the downlink data sent by the target network element fails, and the UE reachability notification after the downlink data fails includes the application ID of the AF corresponding to the unreachable UE .
  • the first notification sending module 2104 is used for the UE reachability notification after the AF corresponding to the application identifier included in the UE reachability notification after the downlink data failure fails to send the downlink data.
  • the UE reachable notification message can be sent to the AF in a targeted manner, as opposed to directly sending the UE reachable to all AFs that have subscribed to the downlink data after the UE reachability event fails
  • Notification messages can improve communication accuracy, reliability, and network resource utilization.
  • the SMF network element includes a first processor 2201, a first memory 2202, and a first communication bus 2203.
  • the first communication bus 2203 is used to connect the first processor 2201 and the first memory 2202.
  • the first processor 2201 is used to execute the computer program stored in the first memory 2202 to implement but not limited to the steps of the message notification method as described above.
  • FIG. 23 is a schematic structural diagram of an NEF network element according to an embodiment of the present disclosure.
  • the NEF network element includes a second processor 2301, a second memory 2302, and a second communication bus 2303.
  • the second communication bus 2303 is used to connect the second processor 2301 and the second memory 2302.
  • the second processor 2301 is used to execute the computer program stored in the second memory 2302 to implement but not limited to the steps of the message notification method as described above.
  • the AMF network element includes a third processor 2401, a third memory 2402, and a third communication bus 2403.
  • the third communication bus 2403 is used to connect the third processor 2401 and the third memory 2402.
  • the third processor 2401 is used to execute the computer program stored in the third memory 2402 to implement but not limited to the steps of the message notification method as described above.
  • the present disclosure also provides a communication system, including a target network element and a NEF network element; the target network element may be an AMF network element or an SMF network element.
  • the target network element is used to receive a first request for a UE reachable event after failing to subscribe to downlink data, and to generate a first subscription event for the UE reachable after failed downlink data according to the first request.
  • the element ID NEF and the event reference ID of the first subscription event, the first subscription event is associated with the event reference ID of the first subscription event; and the UE reachability notification after receiving the downlink data of the target UE corresponding to the application ID fails, According to the first subscription event, the UE reachability notification is sent to the NEF network element after the downlink data fails.
  • the NEF network element is used for the UE reachability notification after the AF corresponding to the application identifier included in the UE reachability notification after the downlink data failure fails to send the downlink data.
  • This embodiment also provides a computer-readable storage medium, which is implemented in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules, or other data) Volatile or non-volatile, removable or non-removable media.
  • Computer-readable storage media include but are not limited to RAM (Random Access Memory, random access memory), ROM (Read-Only Memory, read-only memory), EEPROM (Electrically Erasable Programmable read only memory, live erasable programmable read-only memory ), Flash memory or other memory technology, CD-ROM (Compact Disc Read-Only Memory, CD-ROM), digital versatile disk (DVD) or other optical disk storage, magnetic box, magnetic tape, magnetic disk storage or other magnetic storage devices, Or any other medium that can be used to store desired information and can be accessed by a computer.
  • RAM Random Access Memory
  • ROM Read-Only Memory
  • EEPROM Electrically Erasable Programmable read only memory
  • live erasable programmable read-only memory Flash
  • a computer-readable storage medium is used to store one or more computer programs, which may be executed by one or more processors to implement the message notification method as described above.
  • the present disclosure also provides a computer program (or computer software) that can be distributed on a computer-readable medium and executed by a computable device to implement at least one step of the message notification method as described above; and In some cases, at least one step shown or described may be performed in an order different from that described in the above embodiment.
  • the present disclosure also provides a computer program product, including a computer readable device on which the computer program shown above is stored.
  • the computer-readable device may include the computer-readable storage medium as described 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, the present invention is not limited to any specific combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne, selon des modes de réalisation, un procédé, un appareil, un élément réseau et un système de notification de message et un support de stockage. Le procédé de notification de message comprend les étapes consistant à : recevoir une première demande d'abonnement à une disponibilité d'équipement utilisateur (UE) après un événement de défaillance de données de liaison descendante, et générer un premier événement d'abonnement de disponibilité d'UE après une défaillance de données de liaison descendante selon la première demande, la première demande comprenant un identifiant d'application d'une troisième application (AF), un identifiant ID NEF d'un élément réseau de fonction d'exposition de réseau (NEF) et un identifiant de référence d'événement du premier événement d'abonnement, qui sont associés ; et recevoir une disponibilité d'UE après une notification de défaillance de données de liaison descendante d'un UE cible correspondant à l'identifiant d'application, et envoyer la disponibilité d'UE après notification de défaillance de données de liaison descendante à l'élément de réseau NEF selon le premier événement d'abonnement.
PCT/CN2019/117385 2018-10-10 2019-11-12 Procédé, appareil, élément réseau et système de notification de message et support de stockage WO2020098622A1 (fr)

Applications Claiming Priority (3)

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

Publications (1)

Publication Number Publication Date
WO2020098622A1 true WO2020098622A1 (fr) 2020-05-22

Family

ID=70192789

Family Applications (1)

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

Country Status (2)

Country Link
CN (1) CN111031517A (fr)
WO (1) WO2020098622A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023016153A1 (fr) * 2021-08-10 2023-02-16 Telefonaktiebolaget Lm Ericsson (Publ) Amélioration de l'exposition à la surveillance d'événements

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114071448B (zh) * 2020-08-07 2023-03-28 中国移动通信有限公司研究院 一种数据传输方法、相关网络节点和存储介质
CN114143185A (zh) * 2020-08-13 2022-03-04 阿里巴巴集团控股有限公司 一种网络通信的方法及装置、电子设备、存储介质
CN114339643B (zh) * 2020-09-29 2023-09-22 华为技术有限公司 策略规则的提供方法及会话管理网元
JP7460853B2 (ja) * 2021-01-15 2024-04-02 華為技術有限公司 イベント登録方法、機器、及びシステム
WO2023213286A1 (fr) * 2022-05-05 2023-11-09 维沃移动通信有限公司 Procédé et appareil de gestion d'identifiant de modèle, et support de stockage

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107005792A (zh) * 2014-09-26 2017-08-01 阿尔卡特朗讯公司 在移动系统中移动终止应用服务的支持
CN108337705A (zh) * 2018-01-31 2018-07-27 中国联合网络通信集团有限公司 一种用户面重选方法及装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102917342B (zh) * 2008-09-28 2015-11-25 华为技术有限公司 用户设备活动信息通知方法、系统及网元设备、服务器
WO2016106561A1 (fr) * 2014-12-30 2016-07-07 华为技术有限公司 Appareil et procédé de signalisation de message et appareil et procédé d'envoi de données
CN107431918B (zh) * 2015-03-25 2020-09-04 Lg 电子株式会社 在无线通信系统中监测ue可达性的方法及其装置
EP3281366B1 (fr) * 2015-04-07 2020-04-01 Nokia Solutions and Networks Oy Procédé et appareil pour faire face à la consommation énergétique d'un équipement d'utilisateur

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107005792A (zh) * 2014-09-26 2017-08-01 阿尔卡特朗讯公司 在移动系统中移动终止应用服务的支持
CN108337705A (zh) * 2018-01-31 2018-07-27 中国联合网络通信集团有限公司 一种用户面重选方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Solution 7 improvement", 3GPP SA WG2 MEETING #S2-128 S 2-187613, 6 July 2018 (2018-07-06), XP051538961 *
INTEL: "Updates of Solution#2 for Resolving Editor Notes", 3GPP TSG SA WG2 MEETING #127 S 2-184015, 20 April 2018 (2018-04-20), XP051432895 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023016153A1 (fr) * 2021-08-10 2023-02-16 Telefonaktiebolaget Lm Ericsson (Publ) Amélioration de l'exposition à la surveillance d'événements

Also Published As

Publication number Publication date
CN111031517A (zh) 2020-04-17

Similar Documents

Publication Publication Date Title
WO2020098622A1 (fr) Procédé, appareil, élément réseau et système de notification de message et support de stockage
US11523268B2 (en) Communications method and apparatus
US11330069B2 (en) Service subscription method and system for reporting service change in communication system
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
EP3952367A1 (fr) Procédé et dispositif de notification d'événement, et support d'informations
US9125003B2 (en) Machine to machine service management device, network device, and method processing service system
WO2017079906A1 (fr) Procédé de sélection d'un réseau de service, équipement de réseau et équipement de gestion
US11856469B2 (en) Communication method, communications apparatus, and communications system
EP2861000B1 (fr) Procédé et dispositif permettant de transmettre des données en liaison descendante
JP2019521593A (ja) データ伝送方法、装置及び記憶媒体
EP3496432B1 (fr) Transmission multicast efficace
WO2019047913A1 (fr) Procédé de communication, dispositif associé, et système
WO2022052875A1 (fr) Procédé de communication inter-région de terminal, dispositif d'élément de réseau, et support de stockage
US10129079B2 (en) Telecommunications system and method
WO2021109134A1 (fr) Procédé d'acquisition et de transmission d'informations mbms, dispositif terminal et dispositif d'élément de réseau
JP2016502825A (ja) アクセス制御方法及び装置
WO2020073960A1 (fr) Procédé et appareil de notification de message, élément de réseau, système et support de stockage
KR20230133884A (ko) 코어 네트워크에서 서빙 네트워크 노드를 동적으로검색하는 방법, 네트워크 노드 및 컴퓨터 판독 가능 매체
WO2020156460A1 (fr) Procédés et nœuds de surveillance d'événements d'ue à ue
WO2019154048A1 (fr) Procédé de communication dans un réseau nb-iot, appareil, et support de stockage
CN106714199B (zh) 获取承载网的网络状态信息的方法及装置
CN107786954B (zh) 一种无线传输中的方法和装置
EP4366344A1 (fr) Procédé et appareil de sélection d'entité de service d'adresse, et dispositif électronique et support de stockage lisible
WO2022022345A1 (fr) Procédé, appareil et système de notification d'événement

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19883431

Country of ref document: EP

Kind code of ref document: A1

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 15/09/2021)

122 Ep: pct application non-entry in european phase

Ref document number: 19883431

Country of ref document: EP

Kind code of ref document: A1